The ISE started this thread with a discussion that included "Whether that means using TLD labels that begin with _ or whether that means suffixing them with ".ALT", I leave to you experts to sort." There is another forthcoming option that could be used in draft-schanzen-gns, namely the unallocated string that may be chosen as part of the process coming out of SAC113.
SAC113 <https://www.icann.org/en/system/files/files/sac-113-en.pdf>, published by ICANN's Security and Stability Advisory Committee, recommends that the ICANN board to pick a string that will never be put into the DNS root, and thus is usable for systems like GNS. The recommendation is moving forward, as can be seen on the SAC113 line on page 10 of <https://www.icann.org/en/system/files/files/board-advice-status-report-pdf-30jun22-en.pdf>. A string that is guaranteed to never appear in the DNS root can be used as the basis of private-use names, even if that guarantee doesn't come from the DNSOP Working Group. (I was not part of the SAC113 work, but am reporting here so that the ISE and GNS can see that they will have additional options.) --Paul Hoffman
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
