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

[[e-mail]]

Hi Tim,

Thank you for the update.

For the IANA registrations, you may consider including tables such as:


  *   Request updating IPv6 Special-Purpose Address Space<https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml> as follows (PLEASE DOUBLE CHECK)

Address Block
Name
Eligible to Locally-Served DNS Zones
::1/128
Loopback Address
True
::/128
Unspecified Address
True
::ffff:0:0/96
IPv4-mapped Address
Flase
64:ff9b::/96
IPv4-IPv6 Translat.
False
64:ff9b:1::/48
IPv4-IPv6 Translat.
False
100::/64
Discard-Only Address Block
False
100:0:0:1::/64
Dummy IPv6 Prefix
False
2001::/23
IETF Protocol Assignments
False
2001::/32
TEREDO
False
2001:1::1/128
Port Control Protocol Anycast
False
2001:1::2/128
Traversal Using Relays around NAT Anycast
False
2001:1::3/128
DNS-SD Service Registration Protocol Anycast
False
2001:2::/48
Benchmarking
False
2001:3::/32
AMT
False
2001:4:112::/48
AS112-v6
False
2001:10::/28
Deprecated (previously ORCHID)
2001:20::/28
ORCHIDv2
False
2001:30::/28
Drone Remote ID Protocol Entity Tags (DETs) Prefix
False
2001:db8::/32
Documentation
True
2002::/16 [3<https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml#note3>]
6to4
False
2620:4f:8000::/48
Direct Delegation AS112 Service
False
3fff::/20
Documentation
True
5f00::/16
Segment Routing (SRv6) SIDs
False
fc00::/7
Unique-Local
False
fe80::/10
Link-Local Unicast
True


  *   Request updating IPv4 Special-Purpose Address Space<https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml> as follows (PLEASE DOUBLE CHECK)

Address Block
Name
Eligible to Locally-Served DNS Zones
0.0.0.0/8
"This network"
True
0.0.0.0/32
"This host on this network"
True
10.0.0.0/8
Private-Use
True
100.64.0.0/10
Shared Address Space
False
127.0.0.0/8
Loopback
True
169.254.0.0/16
Link Local
True
172.16.0.0/12
Private-Use
True
192.0.0.0/24 [2<https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml#note2>]
IETF Protocol Assignments
False
192.0.0.0/29
IPv4 Service Continuity Prefix
False
192.0.0.8/32
IPv4 dummy address
False
192.0.0.9/32
Port Control Protocol Anycast
False
192.0.0.10/32
Traversal Using Relays around NAT Anycast
False
192.0.0.170/32, 192.0.0.171/32
NAT64/DNS64 Discovery
False
192.0.2.0/24
Documentation (TEST-NET-1)
True
192.31.196.0/24
AS112-v4
False
192.52.193.0/24
AMT
False
192.88.99.0/24
Deprecated (6to4 Relay Anycast)
192.88.99.2/32
6a44-relay anycast address
False
192.168.0.0/16
Private-Use
True
192.175.48.0/24
Direct Delegation AS112 Service
False
198.18.0.0/15
Benchmarking
False
198.51.100.0/24
Documentation (TEST-NET-2)
True
203.0.113.0/24
Documentation (TEST-NET-3)
True
240.0.0.0/4
Reserved
False
255.255.255.255/32
Limited Broadcast
True

Hope this helps.

Cheers,
Med

De : Tim Wicinski <[e-mail]>
Envoyé : jeudi 21 mai 2026 17:03
À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>
Cc : Nick Buraglio <[e-mail]>; David Farmer <[e-mail]>; list <[e-mail]>; 6MAN <[e-mail]>; dnsop WG <[e-mail]>
Objet : Re: Updates to Locally Served DNS Zones and IP Special-Purpose Address Space Registries


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]<mailto:[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]<mailto:[e-mail]>>
Envoyé : mercredi 25 février 2026 17:25
À : Tim Wicinski <[e-mail]<mailto:[e-mail]>>
Cc : BOUCADAIR Mohamed INNOV/NET <[e-mail]<mailto:[e-mail]>>; list <[e-mail]<mailto:[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]<mailto:[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]<mailto:[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]<mailto:[e-mail]>>
Envoyé : mardi 2 décembre 2025 20:23
À : list <[e-mail]<mailto:[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]<mailto:[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]<mailto:[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.
____________________________________________________________________________________________________________
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.