[DNSOP] Re: Updates to Locally Served DNS Zones and IP Special-Purpose Address Space Registries

[Tim Wicinski <[e-mail]>]

Med

Sorry I missed this - I pushed an update earlier this week with some
changes to get all the references in there.
Next steps should be some reviews - there are a couple of sections on
"Initial Registry" that I am not sure if we should point to what exists or
duplicate them.  Operational Considerations I can work on

tim


On Thu, May 7, 2026 at 4:01 AM <[e-mail]> wrote:

> Hi Tim, all,
>
>
>
> Thank you for publishing a new version:
> https://datatracker.ietf.org/doc/draft-dnsop-rfc6303-bis/01/. In your
> opinion, what would be the next step to make some progress here?
>
>
>
> Adding 6man and DNSOP as this touches registries defined by these WGs.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Nick Buraglio <[e-mail]>
> *Envoyé :* mercredi 25 février 2026 17:25
> *À :* Tim Wicinski <[e-mail]>
> *Cc :* BOUCADAIR Mohamed INNOV/NET <[e-mail]>; list <
> [e-mail]>
> *Objet :* Re: [v6ops] Re: Fwd: New Version Notification for
> draft-dnsop-rfc6303-bis-00.txt
>
>
>
>
>
> Hi Tim. We were discussing this as part of the v6ops AD call prior to IETF
> 125 - is there any movement on this draft? What can we help with?
>
>
>
> nb
>
>
>
> On Wed, Dec 3, 2025 at 12:48 PM Tim Wicinski <[e-mail]> wrote:
>
> Med
>
>
>
> Thanks for the suggestions ! I wanted to get something in place and I
> poked Mr Farmer hoping for his insights.
>
>
>
> And I realized after I published the version it's not a -bis also.
>
>
>
> I'll clean this up today/tomorrow.
>
>
>
> tim
>
>
>
>
>
> On Wed, Dec 3, 2025 at 7:53 AM <[e-mail]> wrote:
>
> Hi Tim,
>
>
>
> Thank you for editing the -00.
>
>
>
> I think that the doc should also update RFC6890 per the discussion we had
> with David. The update to 6890 is about adding a new column to indicate
> whether an entry in the registry is eligible to being listed in locally
> served zones. The expert of the locally served zones registry will also
> have the responsibility to validate reverse entries that will be mirrored
> from the special registry.
>
>
>
> Linking both registries will ensure consistency between the two, with the
> special address registry being the main entry point.
>
>
>
> One minor nit, I suspect that the “-bis” in the file name may be
> misleading for some as this is not a bis, but an update.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Tim Wicinski <[e-mail]>
> *Envoyé :* mardi 2 décembre 2025 20:23
> *À :* list <[e-mail]>
> *Objet :* [v6ops] Fwd: New Version Notification for
> draft-dnsop-rfc6303-bis-00.txt
>
>
>
>
>
>
>
> Hi
>
>
>
> Per discussions with Med and Dave Farmer, I submitted a rough draft to
> sketch out the changes for 6303.
>
> Need to work on the Guidance for Expert Reviewers, but wanted to make a
> start of things.
>
>
>
> Feedback Welcome!
>
>
>
> tim
>
>
>
> ---------- Forwarded message ---------
> From: <[e-mail]>
> Date: Tue, Dec 2, 2025 at 2:21 PM
> Subject: New Version Notification for draft-dnsop-rfc6303-bis-00.txt
> To: Tim Wicinski <[e-mail]>
>
>
>
> A new version of Internet-Draft draft-dnsop-rfc6303-bis-00.txt has been
> successfully submitted by Tim Wicinski and posted to the
> IETF repository.
>
> Name:     draft-dnsop-rfc6303-bis
> Revision: 00
> Title:    Revision to Locally Served DNS Zones Registry
> Date:     2025-12-02
> Group:    Individual Submission
> Pages:    4
> URL:      https://www.ietf.org/archive/id/draft-dnsop-rfc6303-bis-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-dnsop-rfc6303-bis/
> HTML:     https://www.ietf.org/archive/id/draft-dnsop-rfc6303-bis-00.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-dnsop-rfc6303-bis
>
>
> 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.
>
> ____________________________________________________________________________________________________________
> 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.
>
>