Hi Jeff,
One suggestion on the
line requesting feedback: We don't really want any SDO using
the liaison process as a substitute for participation in the
IETF process. Some organizations consider a liaison to carry
the collective weight of the organization and expect technical
comments in the liaison to carry the same weight. (vs individual
comments). Such is not the case in IETF. That said, the
organization is of course free to provide feedback via liaison
response in whatever form they see fit.
It would be good to add
the following
to make it clear that we prefer comments through the IETF
process while still leaving the door open for the SDO (BBF) to
respond as they deem appropriate:
"Those interested in providing detailed feedback and technical comment on the draft are encouraged to participate in the development of the draft in the IETF via the IETF process."
I hope this helps. Please let me know if you have any questions.
Dave
Working Group, The chairs are considering the following text for a liaison statement to the Broadband Forum with regard to draft-ietf-bfd-unaffiliated-echo.We'd like your feedback before we send it out. -- Jeff ------------- >From group: bfd >From Contact: Jeffrey Haas To Group: Broadband-forum To Contacts: (bbf-contacts) Cc: rtg-bfd@ietf.org, rtg-bfd-cha...@ietf.org, rtg-...@ietf.org Response Contact: Jeffrey Haas, Reshad Rahman Body: The IETF Bidirectional Forwarding Detection (BFD) Working Group has begun work on "Unaffiliated BFD Echo Function". This work is happening in the Internet-Draft draft-ietf-bfd-unaffiliated-echo.[1] The BFD protocol (IETF RFC 5880, etc.) is used as a service in routers and other IP gateway devices for testing bi-directional connectivity. Such devices benefit from having BFD as a common interface for monitoring the status of such connectivity. The purpose of this work is to permit an implementation of BFD that supports Echo functionality to be used with a Internet Protocol host that does not support the BFD protocol, but is capable of providing the packet loopback behavior required by the BFD Echo mechanism. The BFD Working Group is aware of an overlapping use case addressed by BBF TR-146. We welcome feedback and further dialog regarding this work. [1] https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/
