Hi all,
Yes, this is a useful document for telemetry use-cases where no metadata is
carried in the packet.
One comment I have is that the document may add some text on ECMP
considerations.
Happy Holidays!
Thanks,
Rakesh
On Sun, Dec 18, 2022 at 4:09 AM Tianran Zhou wrote:
> Hi Gyan,
>
>
>
>
Hi Bruno,
Pls see inline [SH2]
Juniper Business Use Only
From: bruno.decra...@orange.com
Sent: Thursday, December 1, 2022 10:34 PM
To: Shraddha Hegde
Cc: SPRING WG
Subject: RE: draft-ietf-spring-segment-protection-sr-te-paths
[External Email. Be cautious of content]
Shraddha,
Thanks for t
Xingrong,
Replies inline @ [RP2]
On Sat, Dec 17, 2022 at 1:34 AM Xiejingrong (Jingrong) wrote:
>
>
> Why SRv6 is broken in current proposal IMO:
>
> 1. PE1 allocate VPN SID 1/2/3 from its Locator for each MVPN (say MVPN
> 1/2/3) that want to share a single replication tree.
>
> 2. PE1 encapsula
Hi Huaimo,
Pls see inline [SH2]
Juniper Business Use Only
From: Huaimo Chen
Sent: Monday, December 19, 2022 4:32 AM
To: Shraddha Hegde ; bruno.decra...@orange.com; SPRING WG
Subject: RE: draft-ietf-spring-segment-protection-sr-te-paths
[External Email. Be cautious of content]
Hi Shraddha,
Hi Jingrong, Rishabh,
For the case where a tunnel is used for multiple VPNs, how to demultiplex
traffic at a tunnel leaf is totally independent of replication SID. It's
actually outside the scope of this draft in WGLC.
It's true that we want to make sure that the replication SID will work with
