Dear Authors, et al., I've read the draft and would appreciate it if the authors can clarify one question:
- What do you consider as the significant advantage of the mechanism defined in your draft compared with the mechanism defined in draft-ietf-spring-segment-protection-sr-te-paths? As I've compared the two solutions, I couldn't find any significant advantage of the proxy forwarding to have two standardized mechanisms for SR path e2e protection. It might be reasonable to have one standard while other proposals get experimental status? Regards, Greg On Thu, Jan 13, 2022 at 2:19 AM <bruno.decra...@orange.com> wrote: > Dear WG, > > > > This message starts a 2 week WG adoption call, ending 27/01/2022, for > draft-hu-spring-segment-routing-proxy-forwarding > > > https://datatracker.ietf.org/doc/draft-hu-spring-segment-routing-proxy-forwarding/ > > > > After review of the document please indicate support (or not) for WG > adoption of the document to the mailing list. > > > > Please also provide comments/reasons for your support (or lack thereof) as > this is a stronger way to indicate your (non) support as this is not a vote. > > > > > If you are willing to work on or review the document, please state this > explicitly. This gives the chairs an indication of the energy level of > people in the working group willing to work on the document. > > > > Thanks! > > Bruno, Jim, Joel > > _________________________________________________________________________________________________________________________ > > 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 > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring >
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
