> On Sep 29, 2016, at 2:56 AM, hellekin <helle...@gnu.org> wrote: > >> On 09/29/2016 05:42 AM, Edward Lewis wrote: >> >> The one option you have is ".example", unfortunately (and in sympathy) >> I don't have a better suggestion. >> > > .example is for documentation. You can use .invalid for "fake private > TLD", which makes it very clear that it's not a valid TLD. (Sorry for > the tautology.) > > This list of two-letter TLDs sounds like a good candidate for > Special-Use Domain Names. But then, it prompts another question: if, > e.g., XA-XZ are reserved for future use, how to handle their *removal* > from the Special-Use Name Registry once they're assigned again? Which > prompts another question: if a name enters the Special-Use Name > Registry, is it parked (for an indefinite amount of time), or is it > engraved in stone (and won't move from that registry again)? And can > the SUNR hold both types of names (parked and final)?
Good question, not (as far as I know) explicitly addressed in RFC 6761. Because there is no explicit prohibition on removal of a name from the SUNR, publication of an appropriate RFC directing IANA to take such an action would be the appropriate action, at least. In my opinion. The question might actually apply to many IANA registries. Do the "Registration Procedures" apply to "unregistration" as well? I don't know if there is any precedent here. - Ralph > > == > hk > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
