[pim] Re: Erik Kline's Discuss on draft-ietf-pim-zeroconf- mcast-addr-alloc-ps-07: (with DISCUSS)

Erik,

Thanks for your review! We uploaded draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-08 and made changes based on your feedback:

> I struggle to understand the purpose of this document.

It may be helpful to consider the other I-Ds related to this:


  *   draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id<https://datatracker.ietf.org/doc/draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id/>
(Provides foundation for implementing zeroconf IPv6 multicast address allocation protocols)
  *   draft-ietf-pim-ipv6-zeroconf-assignment<https://datatracker.ietf.org/doc/draft-ietf-pim-ipv6-zeroconf-assignment/>
(mDNS-based IPv6 multicast address allocation protocols)
  *   draft-ietf-pim-gaap<https://datatracker.ietf.org/doc/draft-ietf-pim-gaap/>
(a lightweight, decentralized multicast group address allocation protocol)

> Please provide an example of how multicast addresses with T=1 overlap with ff02::1:ffxx:xxxx addresses.

Sure, I will base this example off of the example in RFC 4489 section 4.

Let’s say that a device’s IPv6 link local address is fe80::a12:34ff:fe56:7890. It will use a Solicited-Node multicast address of ff02::1:ff56:7890. It uses RFC 4489 to calculate a link-scoped multicast prefix of ff32:00ff:a12:34ff:fe56:7890::/96. If it chooses 0xff567890 as its group ID (which is compliant with host allocation described in RFC 3307 section 4.3.2), then it will use the IPv6 multicast address ff32:00ff:a12:34ff:fe56:7890:ff56:7890. Both of these IPv6 multicast addresses use Ethernet multicast address 33:33:ff:56:78:90.

If you think this example would be useful to include in the document, how would you feel about updating draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id<https://datatracker.ietf.org/doc/draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id/> to include it? That document is focused specifically on improving the IPv6 multicast address architecture to better accommodate multicast address allocation protocols.

> The document claims to "[describe] the key limitations of current solutions such as MADCAP"…

We added this to the introduction section:

RFC2730 (MADCAP) describes a method for server-based multicast IP address allocation, but this does not suit a zeroconf environment.

Best Regards,

Nate


From: Erik Kline via Datatracker <[email protected]>
Sent: Monday, November 17, 2025 21:27
To: The IESG <[email protected]>
Cc: [email protected]; [email protected]; [email protected]
Subject: [pim] Erik Kline's Discuss on draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-07: (with DISCUSS)

Erik Kline has entered the following ballot position for draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-07: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free


Erik Kline has entered the following ballot position for

draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-07: Discuss



When responding, please keep the subject line intact and reply to all

email addresses included in the To and CC lines. (Feel free to cut this

introductory paragraph, however.)





Please refer to https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!EJc4YC3iFmQ!X2dkC1MGYQlwD2hkYCOm2-gnOiOy-K6XvRHvsQ_C9pve9cS15lnCkNBm7KQqMsIVmrmCwom1e4GRnm-BDw$<https://urldefense.com/v3/__https:/www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!EJc4YC3iFmQ!X2dkC1MGYQlwD2hkYCOm2-gnOiOy-K6XvRHvsQ_C9pve9cS15lnCkNBm7KQqMsIVmrmCwom1e4GRnm-BDw$>

for more information about how to handle DISCUSS and COMMENT positions.





The document, along with other ballot positions, can be found here:

https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-pim-zeroconf-mcast-addr-alloc-ps/__;!!EJc4YC3iFmQ!X2dkC1MGYQlwD2hkYCOm2-gnOiOy-K6XvRHvsQ_C9pve9cS15lnCkNBm7KQqMsIVmrmCwom1e4HFebBwsg$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-pim-zeroconf-mcast-addr-alloc-ps/__;!!EJc4YC3iFmQ!X2dkC1MGYQlwD2hkYCOm2-gnOiOy-K6XvRHvsQ_C9pve9cS15lnCkNBm7KQqMsIVmrmCwom1e4HFebBwsg$>







----------------------------------------------------------------------

DISCUSS:

----------------------------------------------------------------------



# Internet AD comments for draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-07

CC @ekline



* comment syntax:

  - https://urldefense.com/v3/__https://github.com/mnot/ietf-comments/blob/main/format.md__;!!EJc4YC3iFmQ!X2dkC1MGYQlwD2hkYCOm2-gnOiOy-K6XvRHvsQ_C9pve9cS15lnCkNBm7KQqMsIVmrmCwom1e4HeX11aeg$<https://urldefense.com/v3/__https:/github.com/mnot/ietf-comments/blob/main/format.md__;!!EJc4YC3iFmQ!X2dkC1MGYQlwD2hkYCOm2-gnOiOy-K6XvRHvsQ_C9pve9cS15lnCkNBm7KQqMsIVmrmCwom1e4HeX11aeg$>



* "Handling Ballot Positions":

  - https://urldefense.com/v3/__https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!EJc4YC3iFmQ!X2dkC1MGYQlwD2hkYCOm2-gnOiOy-K6XvRHvsQ_C9pve9cS15lnCkNBm7KQqMsIVmrmCwom1e4ELB9zJaw$<https://urldefense.com/v3/__https:/ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!EJc4YC3iFmQ!X2dkC1MGYQlwD2hkYCOm2-gnOiOy-K6XvRHvsQ_C9pve9cS15lnCkNBm7KQqMsIVmrmCwom1e4ELB9zJaw$>



## Discuss



### S4



* Please provide an example of how multicast addresses with T=1 overlap

  with ff02::1:ffxx:xxxx addresses.



### _general_



* I struggle to understand the purpose of this document.



* The document claims to "[describe] the key limitations of current

  solutions such as MADCAP", but I seem to have missed the section where

  MADCAP discussion took place.











_______________________________________________

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]