Analysis of Bidirectional Forwarding Detection (BFD) Security According to the Keying and Authentication for Routing Protocols (KARP) Design Guidelines
RFC 7492

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'Analysis of Bidirectional Forwarding Detection (BFD) Security According to KARP Design Guide' to Informational RFC (draft-ietf-karp-bfd-analysis-08.txt)

The IESG has approved the following document:
- 'Analysis of Bidirectional Forwarding Detection (BFD) Security
   According to KARP Design Guide'
  (draft-ietf-karp-bfd-analysis-08.txt) as Informational RFC

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Adrian Farrel.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-karp-bfd-analysis/

Ballot Text

Technical Summary

  This document analyzes the security mechanisms for BFD, according
  to the guidelines set forth in Section 4.2 of Keying and Authentication
  for Routing Protocols Design Guidelines. In analyzes the current
  security state of BFD, describes gaps, and  discusses work that
  needs to be done to close those gaps.

Working Group Summary

  The KARP Working Group was happy with the document.  There
  was no controversy. A chair of the BFD WG was active in its
  development and review, and the document was shown to the
  BFD WG for review and feedback.

  The KARP WG has now closed, but WG last call completed while
  the group was still active. The draft is being advanced as AD
  Sponsored.

Document Quality

  This document has been reviewed by the KARP Working Group
  and by the KARP chairs.  It does a good job laying out the issues
  with securing BFD.  The level of detail is appropriate to the working
  group goals as laid out in the charter and the guidelines document.

Personnel

  Brian Weis <bew@cisco.com> is the document shepherd.
  Adrian Farrel <adrian@olddog.co.uk> is the responsible AD.

RFC Editor Note