Comments made in the chat, about the private-use presentation/draft: Me: One potential approach is to say (in the RFC) that one of the two-letter reserved codes should avoid name collision by putting a collision-resistant second-level label, below .zz and above the private use usage (and use that particular two-letter code in that manner exclusively).
E.g. whatever-i-want.guid-as-label-to-prevent-collisions.zz rather than whatever-i-want.zz Warren: @Brian: Yes, but as you know (being a registrar), people really want semantically meaningful names... People have seen using www.corp, not www.dfads3e4r34324rwefe.corp.. Me: Correct, and I think possibly providing guidance that this private use SHOULD be generally limited to "magic" things like automation or automated/negotiated systems. The UI can/should hide the GUID component and possibly also the zz TLD Ben: That could be $guid.guidspace.arpa, no need for .zz "guidspace.arpa" is not a thing. I'm just suggesting an adjustment to Brian's proposal. Me: That's a good idea, can be pursued independently of the private-use TLDs like .zz (possibly addressing different use cases?) Brian
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
