--- 1/draft-ietf-idr-bgp-bfd-strict-mode-02.txt	2020-05-07 11:13:17.952317468 -0700
+++ 2/draft-ietf-idr-bgp-bfd-strict-mode-03.txt	2020-05-07 11:13:18.020318373 -0700
@@ -1,23 +1,23 @@
 
 IDR Workgroup                                                   M. Zheng
-Internet-Draft                                    Individual Contributor
+Internet-Draft                                                     Ciena
 Intended status: Standards Track                               A. Lindem
-Expires: May 7, 2020                                       Cisco Systems
+Expires: November 8, 2020                                  Cisco Systems
                                                                  J. Haas
                                                   Juniper Networks, Inc.
                                                                    A. Fu
                                                           Bloomberg L.P.
-                                                        November 4, 2019
+                                                             May 7, 2020
 
                           BGP BFD Strict-Mode
-                 draft-ietf-idr-bgp-bfd-strict-mode-02
+                 draft-ietf-idr-bgp-bfd-strict-mode-03
 
 Abstract
 
    This document specifies extensions to RFC4271 BGP-4 that enable a BGP
    speaker to negotiate additional Bidirectional Forwarding Detection
    (BFD) extensions using a BGP capability.  This BFD capability enables
    a BGP speaker to prevent a BGP session from being established until a
    BFD session is established.  It is referred to as BGP BFD "strict-
    mode".  BGP BFD strict-mode will be supported when both the local
    speaker and its remote peer are BFD strict-mode capable.
@@ -30,25 +30,25 @@
    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 May 7, 2020.
+   This Internet-Draft will expire on November 8, 2020.
 
 Copyright Notice
 
-   Copyright (c) 2019 IETF Trust and the persons identified as the
+   Copyright (c) 2020 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
    carefully, as they describe your rights and restrictions with respect
    to this document.  Code Components extracted from this document must
    include Simplified BSD License text as described in Section 4.e of
    the Trust Legal Provisions and are provided without warranty as
@@ -216,21 +216,24 @@
               DOI 10.17487/RFC5882, June 2010,
               <https://www.rfc-editor.org/info/rfc5882>.
 
    [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
               2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
               May 2017, <https://www.rfc-editor.org/info/rfc8174>.
 
 Authors' Addresses
 
    Mercia Zheng
-   Individual Contributor
+   Ciena
+   3939 N. 1st Street
+   San Jose, CA 95134
+   UNITED STATES
 
    Email: merciaz.ietf@gmail.com
 
    Acee Lindem
    Cisco Systems
    301 Midenhall Way
    GARY, NC 27513
    UNITED STATES
 
    Email: acee@cisco.com