Guidelines for IANA DNS Root Zone Publication List Providers

3.1. Guidelines related to the list of publication points

• the list of publication points must be machine readable¶

• the list of publication points must not be limited to a particular size.¶

• the list of publication points should include publication points hosted from multiple organizations.¶

• the list of publication points should include a service endpoint from IANA itself.¶

• the list of publication points must be verifiable as complete through the use of a cryptographic checksum.¶

• the list of publication points should be cryptographically verifiable as to its origin.¶

• the list of publication points should include multiple protocols that can be used for fetching the IANA root zone data. Specifically the list should include both https and AXFR based sources.¶

• each item in the list of publication points must be individually complete and usable in isolation.¶

• each item in the list of publication points must be a unique URL.¶

• each item in the list of publication points should be routinely verified as to its functioning status or else removed from the list.¶

3.2. Guidelines related to entries in the list of publication points

• each publication point should make use of widely geographically distributed service points.¶

• each publication point must be globally available without imposed source-based or other filtering.¶

• https based publication points should offer service equivalent to existing Content Delivery Networks (CDNs) today.¶

• AXFR, IXFR and XoT publication points should be as robust as the existing DNS root servers that offer similar services today.¶

• each publication point should have a service level agreement, ideally at zero cost, with IANA.¶

6.1. Normative References

[draft-wkumari-dnsop-localroot-bcp]

"Running a Root Server Local to a Resolver", n.d., <draft-hardaker-dnsop-dns-xfr-scheme>.

[RFC2119]

Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/rfc/rfc2119>.

[RFC3986]

Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, <https://www.rfc-editor.org/rfc/rfc3986>.

[RFC4395]

Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", RFC 4395, DOI 10.17487/RFC4395, February 2006, <https://www.rfc-editor.org/rfc/rfc4395>.

[RFC5234]

Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008, <https://www.rfc-editor.org/rfc/rfc5234>.

[RFC5936]

Lewis, E. and A. Hoenes, Ed., "DNS Zone Transfer Protocol (AXFR)", RFC 5936, DOI 10.17487/RFC5936, June 2010, <https://www.rfc-editor.org/rfc/rfc5936>.

[RFC8174]

Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.

[RFC8499]

Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS Terminology", RFC 8499, DOI 10.17487/RFC8499, January 2019, <https://www.rfc-editor.org/rfc/rfc8499>.

[RFC9103]

Toorop, W., Dickinson, S., Sahib, S., Aras, P., and A. Mankin, "DNS Zone Transfer over TLS", RFC 9103, DOI 10.17487/RFC9103, August 2021, <https://www.rfc-editor.org/rfc/rfc9103>.

6.2. Informative References

[draft-hardaker-dnsop-iana-root-zone-publication-points]

"A format for publishing a list of sources of IANA root zone data", n.d., <https://github.com/hardaker/draft-hardaker-dnsop-iana-root-zone-publication-points>.

[RFC7766]

Dickinson, J., Dickinson, S., Bellis, R., Mankin, A., and D. Wessels, "DNS Transport over TCP - Implementation Requirements", RFC 7766, DOI 10.17487/RFC7766, March 2016, <https://www.rfc-editor.org/rfc/rfc7766>.