Hi Greg,

I anticipate we will have a more complete charter review in the fairly near 
future, and these questions and comments would be appropriate for that review. 
I request that you defer them until then, if that’s OK.

My intention with this minor recharter is that it be tightly scoped to specific 
items for the adopted WG drafts that weren’t already covered in the charter.

Thanks,

—John

On Oct 18, 2024, at 5:29 PM, Greg Mirsky <[email protected]> wrote:



[External Email. Be cautious of content]


Hi John,
thank you for sharing the updates on the BFD WG charter. I have a few questions:

  *   it seems that in addition to the fault detection in a network, BFD is 
aimed for "liveness detection". While the fault detection is well-known 
process, I cannot find the definition of "liveness detection" or "liveness" in 
IETF documents. Coult it be interpreted as, for example, "path continuity"?
  *   several action points are related to MIB work. How useful is MIB BFD 
these days? Would directing the work on BFD management to the BFD YANG model be 
a better choice?

Regards,
Greg

On Fri, Oct 18, 2024 at 12:35 PM John Scudder via Datatracker 
<[email protected]<mailto:[email protected]>> wrote:
John Scudder has entered the following ballot position for
charter-ietf-bfd-08-00: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-bfd/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/charter-ietf-bfd/__;!!NEt6yMaO-gk!FN9wd521P-SJGMGZNb1dy4BElfEbYGwCpcrc8HIycxZgoqomWXTX1h-SWv-HALSrXTEb4zog3TpAzJBNEQ$>



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I think we can skip external review since this is a minor update, but I forgot
to click the right box. :-(



Reply via email to