A related comment on this draft - the pseudo code says:
* S01. If (V bit in End.MVPN = 1) {
* S02. Look up the End.MVPN mapping table according to End.MVPN,
find out the associated RD and the related MFIB(VRF) table T.
* S03. Remove the outer IPv6 header with all its extension headers.
* S04. Set the packet's associated MFIB table to T.
* S05. Submit the packet to the egress MFIB lookup for transmission
to the new multicast downstream.
* S06. } Else {
* S07.Set the packet's associated MFIB table to global MFIB.
* S08. Submit the packet to the egress MFIB lookup for transmission
to the new multicast downstream.
* S09. }
It seems that we don't need a new end behavior at all - the existing End.DT4/6
would just be fine?
Jeffrey
Juniper Business Use Only
From: spring <spring-boun...@ietf.org> On Behalf Of Alexander Vainshtein
Sent: Tuesday, November 8, 2022 11:28 AM
To: draft-wang-spring-multicast-vpn-segm...@ietf.org
Cc: spring@ietf.org; Michael Gorokhovsky <michael.gorokhov...@rbbn.com>; Nitsan
Dolev <nitsan.do...@rbbn.com>; Ron Sdayoor <ron.sday...@rbbn.com>; Dmitry
Valdman <dmitry.vald...@rbbn.com>
Subject: [spring] A question about End.MVPN SID in
draft-wang-spring-multicast-vpn-segment-00
[External Email. Be cautious of content]
Hi,
I have looked up
draft-wang-spring-multicast-vpn-segment-00<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-wang-spring-multicast-vpn-segment-00__;!!NEt6yMaO-gk!GZoIdCznFv8NKmV14Ml0p_jH982hXqRwi6NLU6pVU1v6o3At_UWB2aoVFDZARNYR5z4T4SQYNcsyhc2fLlwLBucE3YE$>
and I think that the End.MVPN behavior in this draft can only be used with
ingress replication as the P-tunneling technology for MVPN.
This is because the End-MVPN SID include the RD of the mVRF in the egress PE
which, in most cases (e.g., with auto-assignment of RD), would be different for
different egress PEs in which the MVPN service instance is instantiated.
What, if anything, did I miss?
Regards, and lots of thaks in advance,
Sasha
Notice: 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.
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
