In message <20160928232720.9513.qm...@ary.lan>, "John Levine" writes: > I don't think this has anything to do with RFC 6761, so ... > > For a very long time, two letter TLDs have been assigned to countries > and other geographic entities per the ISO 3166 alpha-2 list. The > earliest mention I can find is in RFC 920 in 1984, and even then the > wording suggests that the usage was well settled. > > The codes AA, QM-QZ, XA-XZ, and ZZ are "user assigned" and will never > be used for countries. Last year Ed Lewis wrote an I-D proposing that > XA-XZ be made private use and the rest future use, but as far as I can > tell it never went anywhere. > > I've been telling people that if they need a fake private TLD for their local > network they should use one of those since it is exceedingly unlikely > ever to collide with a real DNS name. Am I right?
No. Just because countries don't get assigned these values it doesn't mean that they can't be assigned by ICANN or the IETF in consultation with ICANN. And who *needs* a fake tld? As far as I can tell almost no one. None of the companies using .CORP do. You can't use a .corp.example.com or similar? Now it may be nice to have a tld and for somethings you need a well known namespace to play in (.onion, homenet (location TBD)). Mark > R's, > John > > PS: On my lan, I'm using .QY. > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
