Skip to main content

Meticulous Keyed ISAAC for BFD Optimized Authentication
draft-ietf-bfd-secure-sequence-numbers-27

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: Reshad Rahman <reshad@yahoo.com>, The IESG <iesg@ietf.org>, bfd-chairs@ietf.org, draft-ietf-bfd-secure-sequence-numbers@ietf.org, ketant.ietf@gmail.com, rfc-editor@rfc-editor.org, rrahman@cisco.com, rtg-bfd@ietf.org
Subject: Document Action: 'Meticulous Keyed ISAAC for BFD Optimized Authentication' to Experimental RFC (draft-ietf-bfd-secure-sequence-numbers-27.txt)

The IESG has approved the following document:
- 'Meticulous Keyed ISAAC for BFD Optimized Authentication'
  (draft-ietf-bfd-secure-sequence-numbers-27.txt) as Experimental RFC

This document is the product of the Bidirectional Forwarding Detection
Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and Ketan
Talaulikar.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bfd-secure-sequence-numbers/


Ballot Text

Technical Summary

   This document describes a new BFD Optimized Authentication Mode,
   Meticulous Keyed ISAAC Authentication.  This mode can be used to
   authenticate BFD packets with less CPU time cost than using MD5 or
   SHA1, with the tradeoff of decreased security.  This mechanism cannot
   be used to signal state changes, but it can be used to maintain a
   session in the the Up state.

Working Group Summary

   The WG consensus represents the strong consensus of a few 
   individuals. The document got WG attention during the initial
   phase of progression through the WG and at one point the
   proposal in the document did change significantly (i.e., use
   of the ISAAC mechanism). During the later phases in the WG, the 
   document did not receive further significant inputs/reviews
   due to lack of active implementation interest from major vendors.
   Thereafter, it was picked up for WGLC where it received some 
   further reviews and support for publication as part of the
   set of 3 related documents that extend BFD authentication.
   There were no controversies or threat of appeals.

Document Quality

   There are no known implementations or plans for implementation.
   The work started as Proposed Standard and then was the track
   was changed by the WG to Experimental as the WG believes 
   implementation experience was required to ensure maturity as 
   a Proposed Standard. 
   The document has undergone review from YANG doctors (when the
   module was part of draft-ietf-bfd-optimizing-authentication 
   and a fresh review is requested on this document), as well as 
   early directorate reviews from RTG, SEC and OPS areas.

Personnel

   The Document Shepherd for this document is Reshad Rahman. The
   Responsible Area Director is Ketan Talaulikar.

RFC Editor Note