Hi Jeff, thank you for your kind words. I've read the write-up, and I have several comments:
- For several years I've actively participated in the work at BBF, including the Working Area that published TR-146. I cannot recall that any member company reported TR-146 implementation. Were there any on the BFD mailing list that led to the following summary in the write-up: There are multiple implementations that claim some deployment of BBF TR-146 implementation behavior. - In the course of discussing this draft, I commented many times that the proposed mechanism doesn't require any action from a BFD system outside of a node that transmits and processes a probe. I suggested that, if there's interest in publishing this draft, it be published as Experimental or Informational, but not a Standard track document. I don't find that point of the discussion reflected in the Shepherd write-up, or affecting the intended status. Regards, Greg On Mon, Jan 15, 2024 at 12:57 PM Jeffrey Haas <jh...@pfrc.org> wrote: > With deep apologies to the members of the Working Group for my tardiness, > I've submitted this draft to the IESG. This is after spending the > afternoon > reviewing the discussion to date and verifying the previously raised points > have been addressed. > > Thank you in particular to Greg for your careful review on the draft. The > text benefited greatly from your attention. > > -- Jeff > > > On Mon, Jan 15, 2024 at 12:54:45PM -0800, Jeffrey Haas via Datatracker > wrote: > > -UID: 254690 > > > > Jeffrey Haas has requested publication of > draft-ietf-bfd-unaffiliated-echo-10 as Proposed Standard on behalf of the > BFD working group. > > > > Please verify the document's state at http > >
