there is no SUP identifier corresponding to the AP / VE split because it is considered to be backwards-compatible: old clients / hub lists keep working fine, with the exception of that one information that they now get wrong. users can update their client if they want to see accurate information after the AP / VE split; hub lists are assumed to be active so they should update in time as well.
if you believe this is not backwards-compatible enough, and want to add a SUP id for this split, i'd advise moving this discussion to adcportal.
there is no SUP identifier corresponding to the AP / VE split because it is considered to be backwards- compatible: old clients / hub lists keep working fine, with the exception of that one information that they now get wrong. users can update their client if they want to see accurate information after the AP / VE split; hub lists are assumed to be active so they should update in time as well.
if you believe this is not backwards- compatible enough, and want to add a SUP id for this split, i'd advise moving this discussion to adcportal.