Liaison statement
Response to LS/o on the ITU-T Y.2086 (formerly Y.DNI-fr) “Framework and Requirements of Decentralized Trustworthy Network Infrastructure”
Additional information about IETF liaison relationships is available on the
IETF webpage
and the
Internet Architecture Board liaison webpage.
State | Posted |
---|---|
Submitted Date | 2021-09-10 |
From Group | IAB |
From Contact | Mirja Kühlewind |
To Group | ITU-T-SG-13 |
To Contacts | tsbsg13@itu.int zhangy88@chinatelecom.cn |
Cc | The IAB Executive Director <execd@iab.org> The IAB <iab@iab.org> Scott Mansfield <Scott.Mansfield@Ericsson.com> The IAB Chair <iab-chair@iab.org> Warren Kumari (OPS AD) <warren@kumari.net> |
Response Contact | The IAB Chair <iab-chair@iab.org> The IAB Executive Director <execd@iab.org> |
Purpose | In response |
Attachments | (None) |
Liaisons referred by this one |
Response to LS Regarding A Decentralized Architecture for Global IP Network Name Resolution System
LS/o on synchronization of Y.DNI-fr “Framework and Requirements of Decentralized Trustworthy Network Infrastructure” in Q2/13 LS on the ITU-T Y.2086 (formerly Y.DNI-fr) “Framework and Requirements of Decentralized Trustworthy Network Infrastructure” |
Body |
The IETF would like to thank ITU-T SG13 for information about the consent of Y.DNI-fr Framework and Requirements of Decentralized Trustworthy Network Infrastructure. The IETF’s response (https://datatracker.ietf.org/liaison/979/ - 28 Nov 2010) to work on decentralized architecture for global IP network name resolution system is still relevant: From an IETF perspective the liaison from 28 Nov 2010 states: "The IETF maintains change control for the DNS protocol standards and the use of domain names in URIs, URNs, and other IETF protocols that depend on domain names. In particular, the DNS extensions working group (DNSEXT) is where work on the DNS protocol itself is done. That is also where expertise about the DNS exists, and where work that alters the architecture of host identifiers on the Internet should be done. Any protocol modification proposals can be brought to the IETF and are subject to its regular decision process." Since the IETF’s liaison from 2010, the DNSEXT working group has concluded. DNS protocol work is now largely carried out in the Domain Name System Operations (DNSOP) working group https://datatracker.ietf.org/wg/dnsop/charter/. Additionally, the IRTF has a group specifically chartered for research related to Decentralized Internet Infrastructure (DINRG) https://datatracker.ietf.org/rg/dinrg/about/. For BGP protocol work, see the BGP Enabled ServiceS (BESS) working group https://datatracker.ietf.org/wg/bess/about/ and the Inter-Domain Routing Working Group (IDR) https://datatracker.ietf.org/wg/idr/about/. For other aspects of routing see the working groups in the IETF’s Routing Area https://datatracker.ietf.org/group/rtg/about/. BGP deployment and operational issues are discussed outside the IETF in various peering fora, IXP meetings, and network operator user group meetings. The co-ordination and distribution of Internet addresses and autonomous system numbers (ASNs) is handled by the 5 RIRs (https://www.iana.org/numbers) and the IANA (https://www.iana.org/). Proposals to modify these arrangements should be submitted to the relevant RIR’s policy development process. These procedures are open to all. Global coordination of Internet domain names is carried out by ICANN https://www.icann.org/ and top-level domain (TLD) registries (https://www.iana.org/domains/root/db). It is not an IETF responsibility. ICANN and these TLD registries have their own policy-making procedures. These procedures are also open to all. The IETF looks forward to further engagement by ITU-T members in the IETF process to advance work related to the protocol enhancements needed to support a Decentralized Trustworthy Network Infrastructure. Information on the IETF process and how to engage is found https://www.ietf.org/about/participate/get-started/. Regards, Mirja Kühlewind, IAB Chair |