Re: [spring] WG adoption call for draft-hegde-spring-node-protection-for-sr-te-paths

[Martin Horneffer <[e-mail]>]

Hi Shraddha, Pushpasis,

it's a very good point to see this interaction being documented. Thank you!
I support it.

Best regards, Martin


Am 04.08.20 um 19:48 schrieb Shraddha Hegde:
>
> Hi Pushpasis,
>
> Thanks for the review and comments.
>
> Pls check if the below text looks good.
>
> “
>
> draft-ietf-spring-mpls-anycast-segments proposes a mechanism to allow 
> the use of anycast SIDs in a network
>
> where all devices do not share a common SRGB.  
> draft-ietf-spring-mpls-anycast-segments utilizes the concept of
>
> a virtual LFIB, which is an application of  the concept of 
> Context-Specific Label Spaces [RFC5331].  The current draft
>
> uses the mechanism of context tables, a different application of 
> Context-Specific Label Spaces, to facilitate node
>
> protection.  The current draft does not make provisions to support the 
> virtual LFIB mechanism together with
>
> node protection context tables.  The use of anycast-SIDs together with 
> anycast-aware TI-LFA provides effective
>
> protection against node failure. Therefore, when SRTE paths are 
> constructed using anycast-SIDs, the anycast-SIDs
>
> may not require node protection via context tables. “
>
> Rgds
>
> Shraddha
>
> Juniper Business Use Only
>
> *From:* Pushpasis Sarkar <[e-mail]>
> *Sent:* Tuesday, August 4, 2020 10:47 AM
> *To:* Bruno Decraene <[e-mail]>
> *Cc:* [e-mail]; 
> [e-mail]
> *Subject:* Re: [spring] WG adoption call for 
> draft-hegde-spring-node-protection-for-sr-te-paths
>
> *[External Email. Be cautious of content]*
>
> Hi WG,
>
> Support the adoption of this draft. However I think some text should 
> be added to explain it's interaction with 
> https://datatracker.ietf.org/doc/draft-ietf-spring-mpls-anycast-segments 
> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-spring-mpls-anycast-segments__;!!NEt6yMaO-gk!WSdKaLoKoizMDGgGGY18Ts9fecEVjMTPM1qV80owypiCqJeM3clobB2odRfosxGC$>. 
>
>
> Authors,
>
> If you prefer, I can provide some text for your perusal.
>
> Thanks and regards,
>
> -Pushpasis
>
> On Thu, Jul 30, 2020 at 5:55 PM <[e-mail] 
> <mailto:[e-mail]>> wrote:
>
>     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!WSdKaLoKoizMDGgGGY18Ts9fecEVjMTPM1qV80owypiCqJeM3clobB2odeRL1YEg$>
>
>     (*) 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
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/spring
>     <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!WSdKaLoKoizMDGgGGY18Ts9fecEVjMTPM1qV80owypiCqJeM3clobB2odX_jSQlh$>
>
>
> _______________________________________________
> spring mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/spring