Source len = 0, Source address = 0, Group len = 0, Group address = 0. The receiving PE will pull both IPv4 and IPv6 multicast traffic
This is to say that we want to pull 100% of multicast traffic no matter its IPv4 or IPv6. I do not think we need any version in this case. Mankamana From: Nitsan Dolev <nitsan.do...@rbbn.com> Date: Tuesday, May 27, 2025 at 3:23 AM To: Mankamana Mishra (mankamis) <manka...@cisco.com>, bess@ietf.org <bess@ietf.org>, Ali Sajassi (sajassi) <saja...@cisco.com>, Samir Thoria (sthoria) <stho...@cisco.com>, ke...@arrcus.com <ke...@arrcus.com>, jdr...@juniper.net <jdr...@juniper.net>, w...@juniper.net <w...@juniper.net> Subject: RE: Question about default SMET route RFC9251 Hi Mishra, In fact, I do see one issue that requires clarification in this definition: What shall be the setting of the version flags in the first case? I.e. "Source len = 0, Source address = 0, Group len = 0, Group address = 0. The receiving PE will pull both IPv4 and IPv6 multicast traffic." I would propose to set all three version flags (inherently it is clear that version 3 refers only to IGMP, so it will be ignored for MLD) looking forward to your response, regards, Nitsan Hi Mishra, Thanks for your prompt response. The solution described in https://datatracker.ietf.org/doc/html/draft-sajassi-bess-rfc9251-00#section-9.1.3 properly addresses my question about the default SMET Route. I fully support this solution. Nitsan From: Mankamana Mishra (mankamis) <manka...@cisco.com<mailto:manka...@cisco.com>> Sent: Tuesday, May 27, 2025 1:44 AM To: Nitsan Dolev <nitsan.do...@rbbn.com<mailto:nitsan.do...@rbbn.com>>; bess@ietf.org<mailto:bess@ietf.org>; Ali Sajassi (sajassi) <saja...@cisco.com<mailto:saja...@cisco.com>>; Samir Thoria (sthoria) <stho...@cisco.com<mailto:stho...@cisco.com>>; ke...@arrcus.com<mailto:ke...@arrcus.com>; jdr...@juniper.net<mailto:jdr...@juniper.net>; w...@juniper.net<mailto:w...@juniper.net> Subject: [EXTERNAL] Re: Question about default SMET route RFC9251 Hi Nitsan, This problem being addressed as part of https://datatracker.ietf.org/doc/html/draft-sajassi-bess-rfc9251-00#section-9.1.3 . please let me know your thoughts about new test. Last IETF this draft was presented , and open to get input from working group. Mankamana From: Nitsan Dolev <nitsan.do...@rbbn.com<mailto:nitsan.do...@rbbn.com>> Date: Monday, May 26, 2025 at 5:06 AM To: bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>>, Ali Sajassi (sajassi) <saja...@cisco.com<mailto:saja...@cisco.com>>, Samir Thoria (sthoria) <stho...@cisco.com<mailto:stho...@cisco.com>>, Mankamana Mishra (mankamis) <manka...@cisco.com<mailto:manka...@cisco.com>>, ke...@arrcus.com<mailto:ke...@arrcus.com> <ke...@arrcus.com<mailto:ke...@arrcus.com>>, jdr...@juniper.net<mailto:jdr...@juniper.net> <jdr...@juniper.net<mailto:jdr...@juniper.net>>, w...@juniper.net<mailto:w...@juniper.net> <w...@juniper.net<mailto:w...@juniper.net>> Subject: Question about default SMET route RFC9251 Dear RFC9251 co-authors, Your help with the following question will be appreciated. Regarding https://www.rfc-editor.org/rfc/rfc9251.html#section-9.1.3 Default selective Multicast Route: The text of this section seems to assume that a default SMET can only be created for both IGMP and MLD, I,e, since a * source address is indicated by source address length = 0, while using the same methodology for the Group address would mean that the Group address length should be zero, This means that one cannot distinguish between an IGMP default SMET Route and MLD default SMET route (unless the version flag combination of V 1/2/3 means IGMP and 1/2 means MLD) Alternatively, we may deduce that default SMET route means (*,*) under the specific context, which means that if the related EVPN EVI is IGMP-Proxy enabled but MLD Proxy disabled than the received default SMET route only means that the default SMET Route receiving PE shall send only IPv4 Multicast traffic to the advertising remote PE. (…and vice versa) But if both IGMP Proxy and MLD Proxy are enabled than the default SMET Route receiver shall send all IPv4 and IPv6 Multicast traffic to the default SMET advertising remote PE. Can you please share your thoughts about my interpretation of RFC9251 default SMET route section 9.1.3? Looking forward to getting your response, Regards, Nitsan Dolev Ribbon Communications Disclaimer This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
_______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org
