Hi all,

I've read the document and believe it is ready for publication.

We have lots of deployments using BFD Echo,such as local protection for faster 
failure dection.
It would be greatly appreciated if this draft could be standardized ASAP!

Best Regards,
Changwang lin



Original
From: JeffreyHaas <[email protected]>
To: [email protected] <[email protected]>;
Date: 2023年03月22日 00:02
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



-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from New H3C, 
which is
intended only for the person or entity whose address is listed above. Any use 
of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender
by phone or email immediately and delete it!

Reply via email to