--- 1/draft-ietf-idr-bgp-ls-segment-routing-msd-07.txt	2019-09-17 14:13:12.179767528 -0700
+++ 2/draft-ietf-idr-bgp-ls-segment-routing-msd-08.txt	2019-09-17 14:13:12.203768135 -0700
@@ -1,26 +1,26 @@
 
 IDR Working Group                                            J. Tantsura
 Internet-Draft                                              Apstra, Inc.
 Intended status: Standards Track                             U. Chunduri
-Expires: March 14, 2020                           Futurewei Technologies
+Expires: March 19, 2020                           Futurewei Technologies
                                                            K. Talaulikar
                                                            Cisco Systems
                                                                G. Mirsky
                                                                ZTE Corp.
                                                         N. Triantafillis
                                                             Apstra, Inc.
-                                                      September 11, 2019
+                                                      September 16, 2019
 
  Signaling MSD (Maximum SID Depth) using Border Gateway Protocol Link-
                                  State
-              draft-ietf-idr-bgp-ls-segment-routing-msd-07
+              draft-ietf-idr-bgp-ls-segment-routing-msd-08
 
 Abstract
 
    This document defines a way for a Border Gateway Protocol Link-State
    (BGP-LS) speaker to advertise multiple types of supported Maximum SID
    Depths (MSDs) at node and/or link granularity.
 
    Such advertisements allow entities (e.g., centralized controllers) to
    determine whether a particular Segment Identifier (SID) stack can be
    supported in a given network.
@@ -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 March 14, 2020.
+   This Internet-Draft will expire on March 19, 2020.
 
 Copyright Notice
 
    Copyright (c) 2019 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
@@ -130,22 +130,22 @@
 
    SR: Segment routing
 
    Label Imposition: Imposition is the act of modifying and/or adding
    labels to the outgoing label stack associated with a packet.  This
    includes:
 
    o  replacing the label at the top of the label stack with a new
       label.
 
-   o  pushing one or more new labels onto the label stack The number of
-      labels imposed is then the sum of the number of labels that are
+   o  pushing one or more new labels onto the label stack.  The number
+      of labels imposed is then the sum of the number of labels that are
       replaced and the number of labels that are pushed.  See [RFC3031]
       for further details.
 
 1.1.2.  Requirements Language
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
    "OPTIONAL" in this document are to be interpreted as described in BCP
    14 [RFC2119] [RFC8174] when, and only when, they appear in all
    capitals, as shown here .