--- 1/draft-ietf-idr-bgp-extended-messages-24.txt	2018-05-21 10:13:19.086663073 -0700
+++ 2/draft-ietf-idr-bgp-extended-messages-25.txt	2018-05-21 10:13:19.102663457 -0700
@@ -1,21 +1,21 @@
 
 Network Working Group                                            R. Bush
 Internet-Draft                                 Internet Initiative Japan
 Updates: 4271 (if approved)                                     K. Patel
 Intended status: Standards Track                            Arrcus, Inc.
-Expires: May 23, 2018                                            D. Ward
+Expires: November 22, 2018                                       D. Ward
                                                            Cisco Systems
-                                                       November 19, 2017
+                                                            May 21, 2018
 
                     Extended Message support for BGP
-                draft-ietf-idr-bgp-extended-messages-24
+                draft-ietf-idr-bgp-extended-messages-25
 
 Abstract
 
    The BGP specification mandates a maximum BGP message size of 4096
    octets.  As BGP is extended to support newer AFI/SAFIs and other
    features, there is a need to extend the maximum message size beyond
    4096 octets.  This document updates the BGP specification RFC4271 by
    providing an extension to BGP to extend its current maximum message
    size from 4096 octets to 65535 octets for all except the OPEN
    message.
@@ -36,25 +36,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 23, 2018.
+   This Internet-Draft will expire on November 22, 2018.
 
 Copyright Notice
 
-   Copyright (c) 2017 IETF Trust and the persons identified as the
+   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
    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
@@ -103,25 +103,25 @@
    BGP Extended Messages.
 
    A peer which does not advertise this capability MUST NOT send BGP
    Extended Messages, and BGP Extended Messages MUST NOT be sent to it.
 
    The BGP Extended Message Capability is a new BGP Capability [RFC5492]
    defined with Capability code 6 and Capability length 0.
 
 4.  Operation
 
-   A BGP speaker that is willing to send and receive BGP Extended
-   Messages with a peer SHOULD advertise the BGP Extended Message
-   Capability to the peer using BGP Capabilities Advertisement
-   [RFC5492].  A BGP speaker MAY send Extended Messages to its peer only
-   if it has received the Extended Message Capability from that peer.
+   A BGP speaker that is capable of sending and receiving BGP Extended
+   Messages SHOULD advertise the BGP Extended Message Capability to the
+   peer using BGP Capabilities Advertisement [RFC5492].  A BGP speaker
+   MAY send Extended Messages to its peer only if it has received the
+   Extended Message Capability from that peer.
 
    The Extended Message Capability only applies to all messages except
    for the OPEN message.  This exception is reduce compexity of
    providing backward compatibility
 
    An implementation that advertises support for BGP Extended Messages
    MUST be capable of receiving a message with a length up to and
    including 65535 octets.
 
    Applications generating information which might be encapsulated