Hi Greg:
The behavior of PLR encapsulating Mirror Sid is the same as that of SRv6
Ti-LFA。draft-ietf-spring-srv6-network-programming section 5.1 has been
mentioned that H.Encap is used to encapsulate the TiLFA Repair List, so this
behavior will not modify the original SRH header.
Thanks
Zhibo Hu
From: rtgwg [mailto:[email protected]] On Behalf Of Greg Mirsky
Sent: Friday, February 21, 2020 3:49 AM
To: Jeff Tantsura <[email protected]>
Cc: Routing WG <[email protected]>; RTGWG <[email protected]>
Subject: Re: WG adoption for draft-hu-rtgwg-srv6-egress-protection
Dear Authors,
I have got a question about the switchover procedure in the scenario described
in Section 3. As I understand, P1 monitors the path to PE3 using, for example,
BFD. Once it detects the failure, P1 starts using the pre-computed and
pre-signaled path towards PE4. In order to do that, P1 does, as described in
the text:
P1 modifies the packet before sending it to PE4.
I've looked for what are these modifications and, as I understand it, think
that it is an update to SRH, P1 appends the Mirror SID A4:1::3 to the segment
list. Is that correct understanding? If it is, I'm not sure that it is a valid
operation for P1? Have we heard from 6man experts about this?
I'd greatly appreciate your clarification on this as this mechanism, in my
understanding of the document, is the foundation of the proposed solution and
without it it may not be feasible.
Regards,
Greg
On Thu, Feb 20, 2020 at 11:02 AM Jeff Tantsura
<[email protected]<mailto:[email protected]>> wrote:
Dear RTGWG,
The authors have requested RTGWG to adopt draft-hu-rtgwg-srv6-egress-protection
as the working group document.
The draft has received support during IETF106 meeting, authors have addressed
all the comments received, I expect new version that addresses latest comments
from Yimin to be uploaded within few days.
Please indicate support or no-support by April 5, 2020.
If you are listed as a document author or contributor please respond to this
email stating of whether or not you are aware of any relevant IPR.
The response needs to be sent to the RTGWG mailing list. The document will not
advance to the next stage until a response has been received from each
author and each individual that has contributed to the document.
Cheers,
Jeff & Chris
_______________________________________________
rtgwg mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/rtgwg
_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg
