Hi: See below about issue 1.
- Bernie > On Dec 24, 2025, at 11:39 AM, Megan Ferguson <[email protected]> > wrote: > > Hi Tomek and Bernie (and *AD), > > [*AD - please see *AD in several places in the message below.] > > Thanks for sending along these comments. We have updated the files where we > felt we were confident in the desired change, but had a few further questions > inserted below with [rfced] that could help us in implementing the rest of > the desired updates. > >> >>> 1. Incorrect address in Section 22.4, bullet 2. >>> This is clearly an error. The multicast address starts with ff, not fe. >>> >>> OLD: >>> >>> fe02::1:2 >>> >>> NEW: >>> >>> ff02::1:2 (or better yet, say All_DHCP_Relay_Agents_and_Servers >>> multicast instead) >>> >> bv> yes, this is an error and needs to be corrected. > [rfced] We have updated to “ff02::1:2”. If the possible update to > “All_DHCP_Relay_Agents_and_Servers multicast” ends up being preferred, please > provide further Old/New text as to how you want that to fit into the sentence. I think using the named address is likely better, so: OLD: * For wired networks where clients typically are connected to a switch port, snooping DHCP multicast (or unicast) traffic becomes difficult, as the switches limit the traffic delivered to a port. The client's DHCP multicast messages (with destination address ff02::1:2) are only forwarded to the DHCP server's (or relay's) switch port -- not all ports. Also, the server's (or relay's) unicast replies are only delivered to the target client's port -- not all ports. NEW: * For wired networks where clients typically are connected to a switch port, snooping DHCP multicast (or unicast) traffic becomes difficult, as the switches limit the traffic delivered to a port. The client's DHCP messages (multicast to All_DHCP_Relay_Agents_and_Servers) are only forwarded to the DHCP server's (or relay's) switch port -- not all ports. Also, the server's (or relay's) unicast replies are only delivered to the target client's port -- not all ports. > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
