Doug Ewell wrote: > That's why some of us are watching diligently every time IANA > releases a new version, and scrutinizing the registration > forms with a magnifying glass before they are submitted to > IANA. My (now two) magnifying glasses don't catch unintended cycles. With a rule "pointers only to non-deprecated (sub)tags" they could easily catch such typos. > I'd be interested if somebody could come up with a plausible > scenario that would result in circular P-V assignments. MY reverting to BU, or C? reverting to ZR, that might not work as expected with 4646 rules (too lazy to check). With Martin's proposal it works, the BU -> MY pointer would be replaced by a BU -> BU pointer, and the fine print would say that this should be reduced to no pointer at all. Adding MY -> BU as expected. Frank _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.