Forwarding the below email to the SPRING WG as it's very relevant to the WG.
From: Greg Mirsky <gregimir...@gmail.com> Sent: Thursday, September 1, 2022 10:42 PM To: spring-cha...@ietf.org; MPLS Working Group <mpls-cha...@ietf.org> Cc: draft-ietf-spring-...@ietf.org; draft-ietf-mpls-bfd-direc...@ietf.org Subject: Progressing BFD in SR-MPLS work Dear All, I'm reaching out to you on behalf of the authors of two drafts, draft-ietf-spring-bfd and draft-ietf-mpls-bfd-directed. We greatly appreciate your consideration of our proposal, which may help progress both drafts. At this time, draft-ietf-mpls-bfd-directed defines the Reverse Path TLV that, used in combination with the BFD Discriminator TLV, can be used to communicate to the remote BFD peer the identity of the path it is expected to use for the BFD control packets. That optional control is helpful in path-engineered environments, e.g., RSVP-TE LSP. SR-MPLS is another example of path-engineering, and the same method of controlling a BFD session is applicable. To achieve that, draft-ietf-spring-bfd defines a new Non-FEC TLV. Non-FEC TLV allows listing MPLS labels that construct the SR-MPLS path to be used by the remote BFD peer. Obviously, draft-ietf-spring-bfd uses the normative reference to draft-ietf-mpls-bfd-directed. MPLS WG Chairs had discussed options to progress draft-ietf-mpls-bfd-directed. One of the options could be to move the definition of the Reverse Path TLV to draft-ietf-spring-bfd. As a result, draft-ietf-mpls-bfd-directed would be moved to the Informational track, and adding the normative reference to draft-ietf-spring-bfd. We, the authors, believe that that can be accomplished before the IETF-115 and draft-ietf-spring-bfd be well positioned for consideration of the WG LC afterward. We welcome your questions, comments, and suggestions. Kind regards, Greg (on behalf of the authors of both drafts) Orange Restricted _________________________________________________________________________________________________________________________ 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
