[DNSOP] Re: [v6ops] Expanded IPv6 Documentation Address Space and the "Locally-Served DNS Zones" registry

[[e-mail]]

Hi Tim,

Thank you for volunteering. Much appreciated!

Unless we need to touch other parts of 6303, I think that a simple draft that updates 6303 (but still fall under BCP 163) and basically includes the following would be sufficient:

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 X.

   6.1. Designated Expert Review Guidance

   TBC.

Would that works for you?

Thank you.

Cheers,
Med

De : Tim Wicinski <[e-mail]>
Envoyé : jeudi 20 novembre 2025 18:50
À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>
Cc : David Farmer <[e-mail]>; V6 Ops List <[e-mail]>; dnsop <[e-mail]>
Objet : Re: [DNSOP] Re: [v6ops] Expanded IPv6 Documentation Address Space and the "Locally-Served DNS Zones" registry


Med

I think you're talking about "rfc6303-bis" with some updates? I'd be willing to give that a go if that pleases you

tim


On Thu, Nov 20, 2025 at 4:24 AM <[e-mail]<mailto:[e-mail]>> wrote:
Hi David, all,
(also adding dnsop)

Adding 3fff::/20 to "Locally-Served DNS Zones" registry makes sense. However, given the registration policy of that registry and lack of a rule that would allow us to automatically add prefixes with similar properties to that registry, I checked with IANA and also consulted with the IESG colleagues about how we better handle this.

Given also that future similar issues may happen (the DNS registry may not be known for other WGs, in particular), the suggested approach is to relax the registration policy of "Locally-Served DNS Zones" registry to “Expert Review” instead of “IETF Review”. This would be similar to the fix in https://datatracker.ietf.org/doc/rfc9650/ but for another registry.

If there is a volunteer to write a short draft to fix this, and there are no objections to relax the registration policy, I think that this is a document that we can fast track in DNSOP (or even as AD sponsored).

Comments are welcome.

Cheers,
Med

De : David Farmer <farmer=[e-mail]<mailto:[e-mail]>>
Envoyé : vendredi 17 octobre 2025 19:33
À : Nick Buraglio <[e-mail]<mailto:[e-mail]>>; Geoff Huston <[e-mail]<mailto:[e-mail]>>; V6Ops Chairs <[e-mail]<mailto:[e-mail]>>
Cc : V6 Ops List <[e-mail]<mailto:[e-mail]>>
Objet : [v6ops] Expanded IPv6 Documentation Address Space and the "Locally-Served DNS Zones" registry


V6ops Chairs and RFC9637 Authors,

I have been reviewing several IANA registries and noticed that the Expanded IPv6 Documentation Address Space 3fff::/20 has not been added to the "Locally-Served DNS Zones" registry.

Given that RFC 9637 updates RFC 3849, and RFC 6303 referenced RFC 3849 and included 2001:db8::/32 (8.B.D.0.1.0.0.2.IP6.ARPA) in the "Locally-Served DNS Zones" registry [1], I believe 3fff::/20 (0.F.F.F.3.IP6.ARPA) should also be added to that registry, but it has not been added.

What is the proper procedure to correct this?

I think, with RFC 9637 and the "IETF Review" registration procedure for that registry, it should simply be a request to the IESG and/or IANA.

Thanks.

[1] https://www.iana.org/assignments/locally-served-dns-zones/locally-served-dns-zones.xhtml#ipv6

--
===============================================
David Farmer               Email:[e-mail]<mailto:[e-mail]>
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: [phone]
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.
_______________________________________________
DNSOP mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.