Hi ketan, Thanks for the review and suggestion.
I'll add a section on B-SID and EPE SID in the next revision. Rgds Shraddha Juniper Business Use Only From: Ketan Talaulikar (ketant) <[email protected]> Sent: Friday, August 14, 2020 5:55 PM To: [email protected]; [email protected] Cc: [email protected] Subject: RE: [spring] WG adoption call for draft-hegde-spring-node-protection-for-sr-te-paths [External Email. Be cautious of content] Hi All, I believe this topic is relevant and something for the WG to adopt and work on. I have some concerns though on it's applicability and more specifically it's implications on existing deployments/use-cases. I've share the same on the thread started by Joel on this specific aspect [1]. Some discussion and clarity on this would help before adoption. One other bit, for the example in Sec 2.3, perhaps some text is required to clarify that this applies only for segments signalled via IGPs and if the 9054 was a BSID or BGP-EPE SID then this approach would not work. May I suggest to add a section 2.4 to capture these aspects (it would be some what on the lines of Sec 3.4 but not related to the context table solution). The document is well-written and detailed. It does a very good job of describing the node protection scenarios and options. Thanks, Ketan [1] https://mailarchive.ietf.org/arch/msg/spring/8UIcjT9HMPc4XUp_WAiClFwpOmM/<https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/spring/8UIcjT9HMPc4XUp_WAiClFwpOmM/__;!!NEt6yMaO-gk!WUff9-QZJE06_mQ6lmrdCs1sBxXTank0sdFrYyQ9cMhWdXeopnx_CGRWmNWJyfqi$> From: spring <[email protected]<mailto:[email protected]>> On Behalf Of [email protected]<mailto:[email protected]> Sent: 30 July 2020 17:55 To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: [spring] WG adoption call for draft-hegde-spring-node-protection-for-sr-te-paths Hi SPRING WG, Authors of draft-hegde-spring-node-protection-for-sr-te-paths [1] have asked for WG adoption. Please indicate your support, comments, or objection, for adopting this draft as a working group item by August 20th 2020. (*) Could those who are willing to work on this document, please notify the list. That gives us an indication of the energy level in the working group to work on this. Thanks, Regards, Bruno, Jim, Joel [1] https://tools.ietf.org/html/draft-hegde-spring-node-protection-for-sr-te-paths-07<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-hegde-spring-node-protection-for-sr-te-paths-07__;!!NEt6yMaO-gk!WUff9-QZJE06_mQ6lmrdCs1sBxXTank0sdFrYyQ9cMhWdXeopnx_CGRWmMlJwq_a$> (*) 3 weeks to account for the IETF meeting week and the august/summer period. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
