[Last-Call] Re: Last Call: <draft-ietf-bfd-unaffiliated-echo-11.txt> (Unaffiliated BFD Echo) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

thanks for working on this draft!

While I was not aware of the "BBF Technical Report - Subscriber Sessions
Issue 1" (TR-146) from 2013 already mentioning the idea of using BFD Echo
packets without an associated control session before reading this draft,
I realized this possibility when first reading the BFD RFCs in 2017.
In 2019, I mentioned this idea on the "Linux Advanced Routing & Traffic
Control" (LARTC) mailing list <https://lartc.org/#mailinglist>, where
it was not widely known.

The "Unaffiliated Bidirectional Forwarding Detection (BFD) Echo" draft
provides a full specification for how this idea can be realized, including
comprehensive security considerations.  This is a significant improvement
over what TR-146 provides or the discussion on the LARTC mailing list.

Publishing this draft as a Standards Track RFC incentivizes the creation
of conforming implementations, providing a useful function with clearly
described behavior to rely on.

Best regards,
Erik


On Wed, Sep 25, 2024 at 06:54:26AM -0700, The IESG wrote:
> 
> The IESG has received a request from the Bidirectional Forwarding Detection
> WG (bfd) to consider the following document: - 'Unaffiliated BFD Echo'
>   <draft-ietf-bfd-unaffiliated-echo-11.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@xxxxxxxx mailing lists by 2024-10-09. Exceptionally, comments may
> be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    Bidirectional Forwarding Detection (BFD) is a fault detection
>    protocol that can quickly determine a communication failure between
>    two forwarding engines.  This document defines a use of the BFD Echo
>    where the local system supports BFD but the adjacent system does not
>    support BFD.  BFD Control packet and its processing procedures can be
>    executed over the BFD Echo port where the adjacent system only loops
>    packets back to the local system.
> 
>    This document updates RFC 5880.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/
> 
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 
> 
> 

-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux