--- 1/draft-ietf-bfd-optimizing-authentication-06.txt	2018-11-08 01:14:03.177778066 -0800
+++ 2/draft-ietf-bfd-optimizing-authentication-07.txt	2018-11-08 01:14:03.197778555 -0800
@@ -1,23 +1,23 @@
 
 Network Working Group                                    M. Jethanandani
 Internet-Draft                                                    VMware
 Intended status: Standards Track                               A. Mishra
-Expires: April 14, 2019                                     SES Networks
+Expires: May 15, 2019                                       SES Networks
                                                                A. Saxena
                                                        Ciena Corporation
                                                                M. Bhatia
                                                                    Nokia
-                                                        October 11, 2018
+                                                       November 11, 2018
 
                      Optimizing BFD Authentication
-              draft-ietf-bfd-optimizing-authentication-06
+              draft-ietf-bfd-optimizing-authentication-07
 
 Abstract
 
    This document describes an optimization to BFD Authentication as
    described in Section 6.7 of BFD RFC5880.
 
 Requirements Language
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
@@ -33,21 +33,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on April 14, 2019.
+   This Internet-Draft will expire on May 15, 2019.
 
 Copyright Notice
 
    Copyright (c) 2018 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -168,22 +168,24 @@
    logic for sequence number maintenance remains unchanged from
    [RFC5880].  If at a later time, a different scheme is adopted for
    changing sequence number, this method can use the updated scheme
    without any impact.
 
    Most frames transmitted on a BFD session are BFD CC UP frames.
    Authenticating a small subset of these frames, for example, a detect
    multiplier number of packets per configured period, significantly
    reduces the computational demand for the system while maintaining
    security of the session across the configured authentication periods.
-   The configuration of the periodic authentication interval for BFD CC
-   UP frames is an open issue, left for implementations to decide.
+   A minimum of Detect Multiplier packets MUST be transmitted per
+   configured periodic authentication interval.  This ensures that the
+   BFD session should see at least one authenticated packet during that
+   interval.
 
 3.  NULL Auth TLV
 
    This section describes a new Authentication TLV as:
 
         0                   1                   2                   3
         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |   Auth Type   |   Auth Len    |  Auth Key ID  |   Reserved    |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+