Hi, On Dec 7, 2013, at 5:59 AM, Tim Wicinski <tim.wicin...@teamaol.com> wrote: > We're kicking off the Working Group Last call on Adding 100.64.0.0/10 > prefixes to IPv4 Locally-Served DNS Zones Registry. The author believe that > this document has addressed all the issues raised on the document. The > latest version of the draft is available at: > > http://www.ietf.org/id/draft-ietf-dnsop-rfc6598-rfc6303-00.txt > http://tools.ietf.org/html/draft-ietf-dnsop-rfc6598-rfc6303-00 > > Because of this last call is surrounded by the upcoming holiday season, we're > making this a four (4) week last call cycle. > Substantive comments and statements of support/opposition for advancing this > document should be directed to the mailing list. Editorial > suggestions can be sent directly to the authors. The chairs will send in > their comments as well during the last call period. This last call will > conclude on January 3rd, 2014.
I've read the document and I think there might be a bit of an issue: It appears we now have multiple registries listing the same information. Specifically: http://www.iana.org/assignments/locally-served-dns-zones/locally-served-dns-zones.xhtml seems to be a subset of http://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml Options to deal with this: 1. revise the IANA considerations section to indicate that both registries need to be updated 2. remove the locally served zones from the special-use-domain-names registry 3. merge the two registries into a single uber-wonky-name registry 4. give up on this DNS thing as it was clearly a mistake and go back to ip address literals While the last option is looking more and more appealing, I'm personally leaning towards option 3, adding a column that says how the name should be dealt with (e.g., "locally served via DNS", "never touch the wire", "non-DNS", etc.). Regards, -drc P.S. There should probably be a better way to find these registries -- I had to resort to Google and clicking around to find both registries.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
