[pim] Re: Last Call: <draft-ietf-pim-updt-ipv6-dyn-mcast -addr-grp-id-07.txt> (Updates to Dynamic IPv6 Multicast Add ress Group IDs) to Proposed Standard

Nate Karstens <[email protected]> Wed, 28 Jan 2026 06:31:35 -0600
Newsgroups gmane.ietf.pim
Message-ID <CAMJr_80VxBAg4cxhDWxS28TkoNx2owuPUZPvbOK=2GCz3UXOsQ@mail.gmail.com>
Gunter,

Sue's observations have not been addressed yet. We're working on scheduling
a call to review her concerns.

Thanks,

Nate

On Wed, Jan 28, 2026 at 3:20 AM Gunter van de Velde (Nokia) <
[email protected]> wrote:

> Hi Authors,
>
> Before moving this to IESG ballot stage I would like to confirm if Sue's
> observations were addressed?
> (I think I missed seeing a response and a diff between the -07 and -09 did
> not reveal me relevant changes).
>
> Please let me know if I missed finding a follow up message?
>
> Be well,
> G/
>
> -----Original Message-----
> From: Gunter van de Velde (Nokia)
> Sent: Wednesday, December 17, 2025 10:32 AM
> To: [email protected]
> Cc: [email protected]; [email protected]; Susan Hares <[email protected]>
> Subject: RE: [pim] Re: Last Call:
> <draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07.txt> (Updates to Dynamic
> IPv6 Multicast Address Group IDs) to Proposed Standard
>
> Hi All,
>
> Many thanks for all the hard work on this document. The document is nearly
> ready to be sent for IESG ballot review.
>
> There was a concern through the Genart review from Sue on the IANA section
> and registry guidelines. For convenience the review from Sue can be found
> here:
> https://mailarchive.ietf.org/arch/msg/pim/LL4tpHoDAGG7qUXrHiCu9E7iS1k/
>
> Once resolved I'll progress the draft in the reviewing pipeline to IESG
> ballot review.
>
> Be well and enjoy the end-of-year celebrations, G/
>
>
>
>
> -----Original Message-----
> From: Gunter van de Velde (Nokia) <gunter.van_de_velde=
> [email protected]>
> Sent: Tuesday, November 18, 2025 12:18 PM
> To: 6man <[email protected]>; [email protected]
> Cc: [email protected];
> [email protected]; [email protected]; [email protected]
> Subject: [pim] Re: Last Call:
> <draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07.txt> (Updates to Dynamic
> IPv6 Multicast Address Group IDs) to Proposed Standard
>
> Hi 6man, mboned,
>
> Putting a IETF LC spotlight on this work at 6man and mboned for review
> feedbacks.
>
> This document updates rfc3307 (Allocation Guidelines for IPv6 Multicast
> Addresses) and setup a new registry in the IPv6 Multicast Address Space
> Registry registry group.
>
> G/
>
>
>
> -----Original Message-----
> From: [email protected] <[email protected]>
> Sent: Friday, November 14, 2025 4:47 PM
> To: IETF-Announce <[email protected]>
> Cc: [email protected];
> [email protected]; [email protected]; [email protected]
> Subject: [pim] Last Call:
> <draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07.txt> (Updates to Dynamic
> IPv6 Multicast Address Group IDs) to Proposed Standard
>
>
> CAUTION: This is an external email. Please be very careful when clicking
> links or opening attachments. See the URL nok.it/ext for additional
> information.
>
>
>
> The IESG has received a request from the Protocols for IP Multicast WG
> (pim) to consider the following document: - 'Updates to Dynamic IPv6
> Multicast Address Group IDs'
>   <draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07.txt> as Proposed
> Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> [email protected] mailing lists by 2025-11-28. Exceptionally, comments
> may be sent to [email protected] instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> 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 file can be obtained via
>
> https://datatracker.ietf.org/doc/draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>
> _______________________________________________
> 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]
>

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