[pim] Re: I-D Action: draft-ietf-pim-updt-ipv6-dyn-mcast-a ddr-grp-id-07.txt

Thanks for reviewing that, Brian!

Replacing RFC 3307 does sound like a good idea. However, there are two drafts (draft-ietf-pim-ipv6-zeroconf-assignment and draft-ietf-pim-gaap) that depend on the work in this draft and we were hoping to publish these soon.

What if we first get everything published and then work on a replacement to RFC 3307? We could replace the reference to ZMAAP (unpublished) with references to the new (published) documents, as well as the registry created by this draft.

Cheers,

Nate

From: Brian Haberman <[email protected]>
Sent: Thursday, September 11, 2025 14:26
To: [email protected]
Subject: [pim] Re: I-D Action: draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07.txt

Stig asked me to look at this draft and provide any feedback. The only suggestion that I have is that this draft should completely replace RFC 3307 rather than just update it. This gives people using the IANA registry one RFC to read. In order


Stig asked me to look at this draft and provide any feedback. The only suggestion that I have is that this draft should completely replace RFC 3307 rather than just update it. This gives people using the IANA registry one RFC to read. In order to do that, this draft should also include the legacy allocations from 3307 that are not being changed (e.g., permanent group IDs).



Regards,

Brian



> On Aug 25, 2025, at 2:22 PM, [email protected]<mailto:[email protected]> wrote:

>

> Internet-Draft draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07.txt is now

> available. It is a work item of the Protocols for IP Multicast (PIM) WG of the

> IETF.

>

>   Title:   Updates to Dynamic IPv6 Multicast Address Group IDs

>   Authors: Nate Karstens

>            Dino Farinacci

>            Mike McBride

>   Name:    draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07.txt

>   Pages:   6

>   Dates:   2025-08-25

>

> Abstract:

>

>   Describes limitations of the existing range of dynamic IPv6 multicast

>   addresses specified in RFC3307.  Recommends replacing these

>   allocations with a new registry in the IPv6 Multicast Address Space

>   Registry registry group.  Suggests initial contents of the new

>   registry: a reduced allocation for MADCAP (RFC2730), a Private Use

>   range, and Solicited-Node multicast addresses (which were not

>   previously noted in RFC3307).

>

> The IETF datatracker status page for this Internet-Draft is:

> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id/__;!!EJc4YC3iFmQ!T8y2jiM96jgvjNcyCgAJbVsAMs61VcwTYig3qnsEJhBit1kOiSsA3go5V6nMozcmzMSrjxyj2r1aiC7u8fdHBg$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id/__;!!EJc4YC3iFmQ!T8y2jiM96jgvjNcyCgAJbVsAMs61VcwTYig3qnsEJhBit1kOiSsA3go5V6nMozcmzMSrjxyj2r1aiC7u8fdHBg$>

>

> There is also an HTMLized version available at:

> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07__;!!EJc4YC3iFmQ!T8y2jiM96jgvjNcyCgAJbVsAMs61VcwTYig3qnsEJhBit1kOiSsA3go5V6nMozcmzMSrjxyj2r1aiC47LBTLrQ$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07__;!!EJc4YC3iFmQ!T8y2jiM96jgvjNcyCgAJbVsAMs61VcwTYig3qnsEJhBit1kOiSsA3go5V6nMozcmzMSrjxyj2r1aiC47LBTLrQ$>

>

> A diff from the previous version is available at:

> https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07__;!!EJc4YC3iFmQ!T8y2jiM96jgvjNcyCgAJbVsAMs61VcwTYig3qnsEJhBit1kOiSsA3go5V6nMozcmzMSrjxyj2r1aiC5MfVHBqA$<https://urldefense.com/v3/__https:/author-tools.ietf.org/iddiff?url2=draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07__;!!EJc4YC3iFmQ!T8y2jiM96jgvjNcyCgAJbVsAMs61VcwTYig3qnsEJhBit1kOiSsA3go5V6nMozcmzMSrjxyj2r1aiC5MfVHBqA$>

>

> Internet-Drafts are also available by rsync at:

> rsync.ietf.org::internet-drafts

>

>

> _______________________________________________

> pim mailing list -- [email protected]<mailto:[email protected]>

> To unsubscribe send an email to [email protected]<mailto:[email protected]>



_______________________________________________

pim mailing list -- [email protected]<mailto:[email protected]>

To unsubscribe send an email to [email protected]<mailto:[email protected]>

________________________________

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be Garmin confidential and/or Garmin legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.

_______________________________________________
pim mailing list -- [email protected]
To unsubscribe send an email to [email protected]