--- 1/draft-ietf-idr-bgp-extended-messages-16.txt	2017-02-10 15:13:40.705158039 -0800
+++ 2/draft-ietf-idr-bgp-extended-messages-17.txt	2017-02-10 15:13:40.721158419 -0800
@@ -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: August 15, 2017                                         D. Ward
                                                            Cisco Systems
                                                        February 11, 2017
 
                     Extended Message support for BGP
-                draft-ietf-idr-bgp-extended-messages-16
+                draft-ietf-idr-bgp-extended-messages-17
 
 Abstract
 
    The BGP specification mandates a maximum BGP message size of 4096
    octets.  As BGP is extended to support newer AFI/SAFIs, there is a
    need to extend the maximum message size beyond 4096 octets.  This
    document updates the BGP specification RFC 4271 by providing an
    extension to BGP to extend its current message size from 4096 octets
    to 65535 octets.
 
@@ -110,21 +110,21 @@
 
 4.  Operation
 
    A BGP speaker that is willing to send and receive BGP Extended
    Messages from its peer should advertise the BGP Extended Message
    Capability to its 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 its peer.
 
    An implementation that supports the BGP Extended Messages MUST be
-   prepared to receive an OPEN message that is larger than 4096 bytes.
+   prepared to receive an UPDATE message that is larger than 4096 bytes.
 
    Applications generating messages which might be encapsulated within
    BGP messages MUST limit the size of their payload to take into
    account the maximum message size and all encapsulation overheads on
    the path the encapsulated data are expected to traverse.
 
 5.  Error Handling
 
    A BGP speaker that has the ability to use extended messages but has
    not advertised the BGP Extended Messages capability, presumably due