Support its forwarding. The implementation and deployment of unaffiliated-echo can extend the BFD based fault detection technology in large scale, because it has no special BFD related requirements to the other side.
>From the description of this document, the state machine of local device is conformed that described in RFC5880, the main standard parts of this document are the contents of related fields within the BFD ECHO Packet. If so, I suggested to point out these fields and its value in more explicit manner, to facilitate the implementation interoperability. Should the section 2(update to RFC5880) be moved afterwards the section 3(Unaffiliated BFD Echo Procedures)? And I am worrying that is it easy for the reader/implementer to keep up with the updated contents in current manner, because they must compare the two documents simultaneously? Is there any other better style to point out the update to RFC5880? Best Regards Aijun Wang China Telecom -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Jeffrey Haas Sent: Wednesday, March 22, 2023 12:02 AM To: [email protected] Subject: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Working Group, https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/05/ The authors of draft-ietf-bfd-unaffiliated-echo have requested WGLC. The draft, in my opinion, is in fairly good shape. However, since it functions via looping packets back to itself and trying to exercise the normal RFC 5880 state machine behaviors to a large extent, the draft could use very high scrutiny for several matters: - Does the state machine behave appropriately at all stages? - Are the descriptions of the values of the BFD fields clear in all cases? Please supply the authors and the Working Group with your feedback. The intended finish date for this WGLC is 7 April, 2023. This is one week after the end of IETF 116. Note that Reshad is an author on the draft, so I'll be handling the full set of review and shepherding work. -- Jeff
