Internet-Draft rfc6303-bis December 2025
Wicinski Expires 5 June 2026 [Page]
Workgroup:
DNSOP
Internet-Draft:
draft-dnsop-rfc6303-bis-00
Updates:
6603 (if approved)
Published:
Intended Status:
Best Current Practice
Expires:
Author:
T. Wicinski, Ed.

Revision to Locally Served DNS Zones Registry

Abstract

RFC 6063, "Locally Served DNS Zones", defines two IANA registries called "IPv4 Locally-Served DNS Zone Registry" and "IPv6 Locally-Served DNS Zone Registry". This document changes the registration procedure for that registry from "IETF Review" to "Expert Review". This document updates RFC 6063.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 5 June 2026.

Table of Contents

1. Introduction

In [RFC6303] "Locally Served DNS Zones", it defines two IANA registries called "IPv4 Locally-Served DNS Zone Registry" and "IPv6 Locally-Served DNS Zone Registry". This document changes the registration procedure for that registry from "IETF Review" to "Expert Review".

PLEASE REMOVE THE FOLLOWING PARAGRAPH BEFORE PUBLISHING: The source for this draft is maintained on GitHub at: https://github.com/moonshiner/draft-dnsop-rfc6303-bis

2. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. DNS terminology is as described in [RFC8499].

2.1. Updates to 6063

Please update Section 8 of [RFC6303] "IANA Considerations" with the following text:

OLD:

This registry can be amended through "IETF Review" as per [RFC5226]. As part of this review process, it should be noted that once a zone is added it is effectively added permanently; once an address range starts being configured as a local zone in systems on the Internet, it will be impossible to reverse those changes.

NEW:

This registry can be amended through "Expert Review" policy (Section 4.5 of [RFC8126]). As part of this review process, it should be noted that once a zone is added it is effectively added permanently; once an address range starts being configured as a local zone in systems on the Internet, it will be impossible to reverse those changes. More guidance for Designated Experts is provided in Section TBD.

2.2. Guidance for Expert Reviews

In changing the approval to "Expert Review", there should be some additional guidance. Here are some examples (not all mandatory) on what the Reviewer should look for:

  1. Should have at least an internet-draft written which can explain the usage.

  2. The various Working Groups in the IETF should have

  3. Must be approved by someone named Tim.

3. References

3.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC6303]
Andrews, M., "Locally Served DNS Zones", BCP 163, RFC 6303, DOI 10.17487/RFC6303, , <https://www.rfc-editor.org/info/rfc6303>.

3.2. Informative References

[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
[RFC8499]
Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS Terminology", RFC 8499, DOI 10.17487/RFC8499, , <https://www.rfc-editor.org/info/rfc8499>.

Appendix A. Appendix

Acknowledgements

Author's Address

Tim Wicinski (editor)
Elkins, WV 26241
United States of America