On Mon, 29 Feb 2016, Tim Wicinski wrote:
There was some good discussion around this draft when it first appeared, and
the initial idea by the author was to run this through the Apps area working
group. The chairs feel it make more sense to run this through DNSOP and we
urged the author to allow us the chance to give the working group a try
before giving up.
*Note: This draft will create an IANA registry for "underscored names". Now
10 years ago, even I would of blanched at such a thought. But there seems to
have come a time where it makes sense to document the
morass of these labels and offers some guidance. The discussion seemed to
bear this out.
I don't like it but it seems we should have one.
This starts a Call for Adoption for "DNS Scoped Data Through '_Underscore'
Attribute Leaves"
The draft is available here:
https://datatracker.ietf.org/doc/draft-crocker-dns-attrleaf/
So I'm in favor of adopting this document.
Some comments so far:
Normally we try to leave "private use" ranges in registries for people
to experiment on. It would be good to have that here as well, or else we
won't be able to differentiate experimentation from standarization. I
suggest reserving the double underscore space (__*) for private use
(provided this isn't already in wide use)
The document should probably explain the RRtype listed in the registry
and interaction/allowance with CNAME/DNAME.
Are there any known already existing conflicts where two protocols use
the same underscore entry. If so, how do we resolve that issue?
What are the requirements for entry into this registry. I would not want
to see a rush of people registering vanity names for pet projects,
taking away all the sensible one word entries. I see _mail is available :)
Paul
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
