Hello Authors, Looks like I've missed the WGLC on this document, but nevertheless would like to share the following comments:
Sec 1 of the document says: Section 5 of [RFC5880 <https://www.ietf.org/archive/id/draft-ietf-bfd-unaffiliated-echo-08.html#RFC5880> ] indicates that the payload of an affiliated BFD Echo packet is a local matter and hence its contents are outside the scope of that specification. This document, on the other hand, specifies the contents of the Unaffiliated BFD Echo packet and what to do with them. However, when I go through the procedures in Section 2, there is no description of the actual construction of the IP packet that A sends out to B - what is the source and destination IP - or MAC addresses for that matter? How is it that B would loop it back? I believe it is important for the document to specify this. Another important part is that normally BFD verifies the bidirectional path, the liveness of the other endpoint, but also validates the presence of a specific IP at that endpoint. Is that still the case when operating in this mode? This question arises since the document talks about liveness to servers - so is it monitoring liveness to the server host or a specific server IP? Finally, is it normal or natural to expect server hosts to be able to "loop them back by normal IP forwarding"? Or does it require some additional/special capabilities to be turned ON those hosts as hosts don't do forwarding by default. It would help if these aspects are clarified in the document. Thanks, Ketan On Thu, Jul 6, 2023 at 7:50 AM <internet-dra...@ietf.org> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This Internet-Draft is a work item of the Bidirectional > Forwarding Detection (BFD) WG of the IETF. > > Title : Unaffiliated BFD Echo > Authors : Weiqiang Cheng > Ruixue Wang > Xiao Min > Reshad Rahman > Raj Chetan Boddireddy > Filename : draft-ietf-bfd-unaffiliated-echo-08.txt > Pages : 12 > Date : 2023-07-05 > > Abstract: > Bidirectional Forwarding Detection (BFD) is a fault detection > protocol that can quickly determine a communication failure between > two forwarding engines. This document proposes a use of the BFD Echo > where the local system supports BFD but the neighboring system does > not support BFD. BFD Control packet and its processing procedures > can be executed over the BFD Echo port where the neighboring system > only loops packets back to the local system. > > This document updates RFC 5880. > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/ > > There is also an htmlized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-bfd-unaffiliated-echo-08 > > A diff from the previous version is available at: > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-bfd-unaffiliated-echo-08 > > Internet-Drafts are also available by rsync at rsync.ietf.org: > :internet-drafts > > >
