Title: For Information TR-146 and draft-ietf-bfd-unaffiliated-echo Submission Date: 2022-01-21 URL of the IETF Web page: https://datatracker.ietf.org/liaison/1775/
From: Dave Sinicrope <[email protected]> To: Jeffrey Haas <[email protected]>,Reshad Rahman <[email protected]> Cc: Alvaro Retana <[email protected]>,John Scudder <[email protected]>,Martin Vigoureux <[email protected]>,Dave Sinicrope <[email protected]>,Jeffrey Haas <[email protected]>,Reshad Rahman <[email protected]>,Bidirectional Forwarding Detection Discussion List <[email protected]> Response Contacts: Technical Contacts: Purpose: For information Body: The BBF thanks the IETF BFD WG for informing us of important work on the BFD Echo. We wanted to clarify the "overlapping use case with TR-146". TR-146 leverages BFD Echo as a connectivity check mechanism. It does so in a manner where the peer does not need a full BFD implementation to echo the packet received. In our opinion, no future standardization is required to support TR-146. There is no current interest in revising TR-146 to leverage the enhancement of the BFD protocol. We noted in the BBF community that those interested in participating should do so in the IETF BFD WG. Sincerely, Lincoln Lavoie, Broadband Forum Technical Committee Chair Attachments: No document has been attached
