On Mon, Jun 15, 2020 at 8:34 AM Tony Finch <[email protected]> wrote: > Tim Wicinski <[email protected]> writes: > > > This starts a Call for Adoption for draft-arends-private-use-tld > > I think this is cute / clever, but a very bad idea. > > Experience from IPv4 and IPv6 private use areas shows that there will be > collisions and they will be painful. > > I think the comparison to v4 private use is flawed, specifically because IPv4 addresses are a fixed quantity.
Private use DNS space is freeform and limited only by the 255 character limit in DNS names. Collisions in private use DNS space can trivially be prevented by use of an in-fix (like a suffix but before the TLD) designed to be unique. E.g. use an FQDN belonging to you (or your company), so the namespace would be example.com.zz under which your private names are instantiated. (That's an example only, any arbitrary string could be used, even a GUID.) Brian
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
