Dave, I think this is much improved :)
A few nits: > Each globally-registered underscore name owns a distinct, subordinate > name space. except when it doesn't (i.e. the SRV transports all share the *same* subordinate name space). - on that note, _sctp and _dccp are missing from the global table. - the table formatting is pretty poor, do we really need any more than just "NAME", "RR" and "REFERENCE"? The ID field just seems to be an alternate mnemonic for the (already unique) underscore label itself - the IANA considerations still refer to the now non-existent common second-level table - it's still only been five years, although it *does* feel like 12 :p Not a nit: - is there a reference for IANA "First Come First Served" rules, and should we perhaps also mandate "specification required" as a pre-condition for registration? We don't want that table filled with any old junk without a stable specification. Ray _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
