Liaison statement
Announcement of IETF Last Call on draft-ietf-dnsop-alt-tld-22
Additional information about IETF liaison relationships is available on the
Internet Architecture Board liaison webpage.
State | Posted |
---|---|
Submitted Date | 2023-03-14 |
From Group | OPS |
From Contact | Robert Wilton |
To Group | ICANN-BOARD-OF-DIRECTORS |
To Contacts | Harald Alvestrand <harald.alvestrand@board.icann.org> |
Cc | Harald Alvestrand <harald@alvestrand.no> Robert Wilton <rwilton@cisco.com> Warren Kumari <warren@kumari.net> The IETF Chair <chair@ietf.org> |
Response Contact | Warren Kumari <warren@kumari.net> Robert Wilton <rwilton@cisco.com> |
Purpose | For information |
Attachments | (None) |
Body |
Dear colleagues, The IETF DNSOP (Domain Name System Operations) working group has recently determined that there is working group consensus to advance draft-ietf-dnsop-alt-tld[1] towards publication as an RFC. This statement serves as notification to the ICANN board of its impending publication. Assuming this document achieves full IETF consensus, and is approved for publication by the Internet Engineering Steering Group (IESG), it will use the RFC6761 - "Special-Use Domain Names"[2] process to add the “.alt” name to the "Special-Use Domain Name" registry[3]. Given that this document has reached a fairly stable state, we would like to provide notification and an opportunity to comment. The IETF-wide request for last-call comments on this document has been started[4] and concludes on 2023-04-10. Generally, any last-call comments are sent as replies to the last-call thread on the last-call@ietf.org mailing list. Exceptionally, last-call comments may also be sent directly to the IESG - iesg@ietf.org. Please note that draft-ietf-dnsop-alt-tld complements, rather than conflicts with, the SSAC recommendation as published in SAC-113[5] that ICANN should set aside a string for use in private DNS contexts. The IETF’s “.alt” name is designed for use by alternate name spaces that are entirely outside the scope of DNS resolution mechanisms. It is thus outside SAC-113’s recommendation to create a name to be used within a DNS context but within a local environment. Publication of either document does not impact or affect the other. Finally, we thank ICANN for their role in the development of this specification by supporting ICANN staff member Paul Hoffman as a listed editor of draft-ietf-dnsop-alt-tld. Regards, Robert Wilton, IETF Operations and Management Area Director, Responsible Area Director for the ALT-TLD document. For background and context, recent liaisons related to the “Special-Use Domain Name” registry: From ICANN: https://www.icann.org/en/system/files/correspondence/marby-to-cooper-kuhlewind-22oct20-en.pdf And the IETF response: https://datatracker.ietf.org/liaison/1706/ Earlier liaisons on a similar topic: https://datatracker.ietf.org/liaison/1351/ References: [1] https://datatracker.ietf.org/doc/draft-ietf-dnsop-alt-tld/ [2] https://datatracker.ietf.org/doc/RFC6761/ [3] https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml [4] https://mailarchive.ietf.org/arch/msg/ietf-announce/-HdQhJF1SUBoruqeV5pIH9nbjr8/ [5] https://www.icann.org/en/system/files/files/sac-113-en.pdf |