Re-chartering BFD – IETF 78 Jeffrey Haas, Dave Ward,

Where do we go from here We have largely accomplished our original charter. Our original charter prohibited taking on new working group items without re-chartering. What kind of work do we want to take on?

The Chairs’ Opinion Provide review and advice for applications of BFD in other working groups. – See, for example, the IDR charter for BGP and its relationship with other working groups. Provide extensions to BFD that cover core use cases requiring changes to the base BFD protocol.

Suggested Criteria for Extensions BFD stands for bi-directional forwarding detection. If a proposed extension or change to a specification doesn’t deal with detecting issues with forwarding, it’s not appropriate for BFD. BFD is often run in line cards and at wire speed. This means that it should be kept simple.

Proposed work item Point to Multi-point BFD. – We have single-hop and multi-hop applications for BFD. – Point to Multi-point applications have become part of critical infrastructure to many customers.

Proposed work item Generic Cryptographic Authentication – The existing authentication mechanism in the core BFD protocol only handles a single key. This provides no ability to do key rotation. – The same draft also recommends HMAC versions of the security ciphers. – Both of the above are consistent with currently recommended protocol security practices.

Other work items Please submit possible working group items to the mailing list. After discussion of new work items, or two weeks after IETF 78 is complete if no new items are submitted, we will send a proposed charter to the mailing list for comment. After achieving consensus, we will submit the charter for approval. Time after the presentations is reserved for open discussion.