A Record of Discussions of Graceful Restart Extensions for Bidirectional Forwarding Detection (BFD)
Draft of message to be sent after approval:
Technical Summary This document is a historical record of discussions about extending the Bidirectional Forwarding Detection (BFD) protocol to provide additional capabilities to handle Graceful Restart. These discussions took place in the context of the IETF's BFD working group, and the consensus in that group was that these extensions should not be made. This document presents a summary of the challenges to BFD in surviving a graceful restart, and outlines a potential protocol solution that was discussed and rejected within the BFD working group. The purpose of this document is to provide a record of the work done so that future effort will not be wasted. This document does not propose or document any extensions to BFD, and there is no intention that it should be implemented in its current form. Working Group Summary The ideas in this I-D were initialy discussed within the BFD WG. That WG rejected the motivation for the work and decided to not expend any further effort on the solution. This document, therefore, does not reflect BFD WG consensus and describes prototcol extensions that are not part of the standards track BFD solution. The BFD WG would have preferred this document to not be published, however, it was brought to the ISE for publication. Document Quality The ISE has worked with the author to present this I-D as Historic rather than related to the Standards Track. Working with the responsible AD, the author has made a number of changes to indicate that the text is: - historic - should not be implemented - without support from the BFD WG - incomplete. There are no implementations of this document. Personnel This document originates from the ISE. Adrian Farrel (firstname.lastname@example.org) has performed the RFC 5742 review. RFC Editor Note After RFC 5742 review, the IESG recommends option 2, viz: 2. The IESG has concluded that this work is related to IETF work done in the BFD WG, but this relationship does not prevent publishing. This document does not require the addition of a further IESG note.