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

Hi Brian and authors

I think it is best to proceed without replacing 3307. Although I see
why it could be worth doing it, it could potentially slow down the
process and we want to get this published soon. If there is a need we
can replace 3307 later, but it is certainly possible that that will
never happen.

Anyone else in the WG have opinions on this? Does anyone prefer we do
as Brian suggests and update this document so it can fully replace
3307?

Thanks,
Stig


On Mon, Sep 15, 2025 at 3:57 PM Brian Haberman <[email protected]> wrote:
>
> Hi Nate,
>      IMO, there is only a few minor edits to this draft in order to make it a full replacement of 3307. If the WG doesn’t want to do a full replacement of 3307, I’m fine with that decision.
>
>      I don’t think it makes sense to publish this document and then turn around and write a new document that obsoletes both 3307 and whatever RFC this draft becomes.
>
> Regards,
> Brian
>
> On Sep 12, 2025, at 3:01 PM, Karstens, Nate <[email protected]> wrote:
>
> 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] 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$
>
> >
>
> > 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$
>
> >
>
> > 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$
>
> >
>
> > Internet-Drafts are also available by rsync at:
>
> > rsync.ietf.org::internet-drafts
>
> >
>
> >
>
> > _______________________________________________
>
> > pim mailing list -- [email protected]
>
> > To unsubscribe send an email to [email protected]
>
>
>
> _______________________________________________
>
> pim mailing list -- [email protected]
>
> To unsubscribe send an email to [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]

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