Re: Seeking clarification of "unregistered packet"
"V, Magesh (Magesh)" <[email protected]> Wed, 20 May 2009 08:40:08 +0530
| Newsgroups | gmane.ietf.magma |
|---|---|
| Message-ID | <05D3B4AA7527D74EBF492123846357530C3D9DF64A@INBANSXCHMBSA2.in.alcatel-lucent.com> |
I think the recommendation holds good for even V3 switches. That is, if its a fully v3 aware switch then (S1,G) traffic should still be considered as unregistered data. On the other hand, if we assume that the presence of (S2,G) join has forced the switch to no more consider (S1,G) data as unregistered then it will start forwarding traffic to the v3 receiver (who sent S2,G join). If such a thing happens then your v3 purpose is defeated. Thanks, Magesh. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of La Monte Yarroll Sent: Wednesday, May 20, 2009 12:20 AM To: [email protected] Cc: Manish Vora; Todd Derr Subject: [magma] Seeking clarification of "unregistered packet" I have a couple questions about the following material from RFC 4541, 2.1.2: > 3) An unregistered packet is defined as an IPv4 multicast packet with > a destination address which does not match any of the groups > announced in earlier IGMP Membership Reports. > > If a switch receives an unregistered packet, it must forward that > packet on all ports to which an IGMP router is attached. A switch > may default to forwarding unregistered packets on all ports. > Switches that do not forward unregistered packets to all ports > must include a configuration option to force the flooding of > unregistered packets on specified ports. Is the ability to "force the flooding of unregistered packets on specified ports" only important on switches which are only processing v1 and v2 packets (or v3 packets ignoring "include source" and "exclude source")? If it is relevant for a switch which processes fully general v3 Joins, the definition of "unregistered packet" seems a little ambiguous. Consider traffic from source S1 to group G which no Joins seen. This traffic (S1,G) is unregistered packets. If we then see a Join for (S2,G), we have now seen the group G mentioned in a Join. How am I supposed to treat the (S1,G) traffic? Is it still unregistered packets? Or am I supposed to stop forwarding that traffic to "specified ports"? My problem may be that I simply do not understand what kinds of devices I might have on "specified ports" that I may need to flood unregistered packets to them. _______________________________________________ magma mailing list [email protected] https://www.ietf.org/mailman/listinfo/magma