Bidirectional Forwarding Detection
charter-ietf-bfd-09

Changed charter milestone "Provide an optimization to BFD authentication to reduce computational demand while still providing desirable security properties.", set due date to June 2025 from December 2025

Added charter milestone "Define a use of the BFD Echo where the local system supports BFD but the adjacent system does not support BFD.", due December 2024

Added charter milestone "Extend BFD to allow it to detect whether a path between two systems is capable of carrying a payload of a particular size.", due December 2024

Added milestone "Submit the cryptographic authentication procedures for BFD to the IESG to be considered as a Proposed Standard", due January 2015, from current group milestones

Added milestone "Submit the generic keying based cryptographic authentication mechanism to the IESG to be considered as a Proposed Standard", due January 2015, from current group milestones

[Ballot comment]
** Please add milestones for the newly added scope

** Are any of the existing work items #1 - 5 done, allowing them to be removed from the charter?  For example:

-- per #1, is there future MIB work planned?

-- per #3 ("Provide an extension to the BFD core protocol in support of point-to-multipoint links and networks"), there is a milestone which says it's done which reads identical to the work item (i.e., "Submit the document on BFD point-to-multipoint support to the IESG to be considered as a Proposed Standard") but not associated document is provided.

Added milestone "Submit the cryptographic authentication procedures for BFD to the IESG to be considered as a Proposed Standard", due January 2015, from current group milestones

Added milestone "Submit a BFD MIB extension in support of the generic keying document to the IESG to be considered as a Proposed Standard", due January 2015, from current group milestones

Added milestone "Submit the generic keying based cryptographic authentication mechanism to the IESG to be considered as a Proposed Standard", due January 2015, from current group milestones

Added milestone "Submit the the document on BFD point-to-multipoint support to the IESG to be considered as a Proposed Standard", due June 2014, from current group milestones

Added milestone "Submit BFD encapsulation and usage profile for multi-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard", due February 2005, from current group milestones

Added milestone "Submit BFD encapsulation and usage profile for MPLS LSPs to the IESG to be considered as a Proposed Standard", due August 2004, from current group milestones

Added milestone "Submit BFD encapsulation and usage profile for single-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard", due August 2004, from current group milestones

[Ballot comment]
This all sounds good.  I am wondering what other close relationships are needed besides MPLS with KARP closing for all the crypto related work?  There may be something in place already that I am not aware of or key participants helping to facilitate this, so it's really just a question for my understanding.  Thanks.

[Ballot comment]
This all sounds good.  I am wondering what other close relationships are needed besides MPLS with KARP closing for all the crypto related work?  There may be something in place already that I am not aware of or key participants helping to faciliate this, so it's really just a question for my understanding.  Thanks.

[Ballot comment]
Hopefully, you can now remove:
  1. Develop the MIB modules for BFD and submit them to the IESG for
  publication as Proposed Standards.

And the famous milestones are absent.

Update to reflect that there are still MIBs that are in-charter that aren't
done, in particular the bfd mpls MIB.  The authentication MIB extension is
still covered by 2b.

Remove the charter item for MPLS-TP.  I believe this work is done, but am
copying the MPLS chairs to confirm.

Remove BFD on LAG.  While there had been some discussion about providing for
bootstrapping mechanisms for it, they have failed to gain traction several
times.  Thus, I think we're done on this.

Add the S-BFD charter item.

[Ballot block]
I have no doubt I will clear on the call because Adrian knows about another conversation we had about this issue:

I just want to make sure that "possibly truncated to a smaller integrity check value" doesn't mean truncating it something really small like down to 8-bits.  I mean you're talking about truncating it down to nothing smaller than 80 bits most likely 96 - right?  How about something like:

(possibly truncated to a smaller integrity check value but not beyond commonly accepted lengths)

[Ballot block]
I have no doubt I will clear on the call because Adrian knows about another conversation we had about this issue:

I just want to make sure that "possibly truncated to a smaller integrity check value" doesn't mean truncating it something really small like down to 8-bits.  I mean you're talking about truncating it down to nothing smaller than 80 bits most likely 96 - right?

Added milestone "Submit the cryptographic authentication procedures for BFD to the IESG to be considered as a Proposed Standard", due January 2015, from current group milestones

Added milestone "Submit a BFD MIB extension in support of the generic keying document to the IESG to be considered as a Proposed Standard", due January 2015, from current group milestones

Added milestone "Submit the generic keying based cryptographic authentication mechanism to the IESG to be considered as a Proposed Standard", due January 2015, from current group milestones

Added milestone "Submit the the document on BFD point-to-multipoint support to the IESG to be considered as a Proposed Standard", due June 2014, from current group milestones

Added milestone "Submit BFD encapsulation and usage profile for multi-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard", due February 2005, from current group milestones

Added milestone "Submit BFD encapsulation and usage profile for MPLS LSPs to the IESG to be considered as a Proposed Standard", due August 2004, from current group milestones

Added milestone "Submit BFD encapsulation and usage profile for single-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard", due August 2004, from current group milestones