--- 1/draft-ietf-idr-bgp-attribute-announcement-01.txt	2018-01-28 22:13:07.632905031 -0800
+++ 2/draft-ietf-idr-bgp-attribute-announcement-02.txt	2018-01-28 22:13:07.656905600 -0800
@@ -1,25 +1,25 @@
 
 Network Working Group                                           K. Patel
 Internet-Draft                                              Arrcus, Inc.
 Intended status: Standards Track                               J. Uttaro
-Expires: November 19, 2017                                           ATT
+Expires: August 1, 2018                                              ATT
                                                              B. Decraene
                                                                   Orange
                                                            W. Henderickx
                                                           Alcatel Lucent
                                                                  J. Haas
                                                         Juniper Networks
-                                                            May 18, 2017
+                                                        January 28, 2018
 
               Constrain Attribute announcement within BGP
-            draft-ietf-idr-bgp-attribute-announcement-01.txt
+            draft-ietf-idr-bgp-attribute-announcement-02.txt
 
 Abstract
 
    [RFC4271] defines four different categories of BGP Path attributes.
    The different Path attribute categories can be identified by the
    attribute flag values.  These flags help identify if an attribute is
    optional or well-known, Transitive or non-Transitive, Partial, or of
    an Extended length type.  BGP attribute announcement depends on
    whether an attribute is a well-known or optional, and whether an
    attribute is a transitive or non-transitive.  BGP implementations
@@ -37,37 +37,37 @@
    BGP member-AS in Confederation
 
 Status of This Memo
 
    This Internet-Draft is submitted in full conformance with the
    provisions of BCP 78 and BCP 79.
 
    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 http://datatracker.ietf.org/drafts/current/.
+   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 November 19, 2017.
+   This Internet-Draft will expire on August 1, 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
-   (http://trustee.ietf.org/license-info) in effect on the date of
+   (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
    described in the Simplified BSD License.
 
    This document may contain material from IETF Documents or IETF
    Contributions published or made publicly available before November
    10, 2008.  The person(s) controlling the copyright in some of this
@@ -321,46 +321,46 @@
    The authors would like to thank John Scudder, Jakob Heitz, Shyam
    Seturam, Juan Alcaide and Acee Lindem for the review and comments.
 
 7.  References
 
 7.1.  Normative References
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119,
               DOI 10.17487/RFC2119, March 1997,
-              <http://www.rfc-editor.org/info/rfc2119>.
+              <https://www.rfc-editor.org/info/rfc2119>.
 
    [RFC4271]  Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
               Border Gateway Protocol 4 (BGP-4)", RFC 4271,
               DOI 10.17487/RFC4271, January 2006,
-              <http://www.rfc-editor.org/info/rfc4271>.
+              <https://www.rfc-editor.org/info/rfc4271>.
 
    [RFC7606]  Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.
               Patel, "Revised Error Handling for BGP UPDATE Messages",
               RFC 7606, DOI 10.17487/RFC7606, August 2015,
-              <http://www.rfc-editor.org/info/rfc7606>.
+              <https://www.rfc-editor.org/info/rfc7606>.
 
 7.2.  Information References
 
    [RFC3392]  Chandra, R. and J. Scudder, "Capabilities Advertisement
               with BGP-4", RFC 3392, DOI 10.17487/RFC3392, November
-              2002, <http://www.rfc-editor.org/info/rfc3392>.
+              2002, <https://www.rfc-editor.org/info/rfc3392>.
 
    [RFC4486]  Chen, E. and V. Gillet, "Subcodes for BGP Cease
               Notification Message", RFC 4486, DOI 10.17487/RFC4486,
-              April 2006, <http://www.rfc-editor.org/info/rfc4486>.
+              April 2006, <https://www.rfc-editor.org/info/rfc4486>.
 
    [RFC4724]  Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y.
               Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724,
               DOI 10.17487/RFC4724, January 2007,
-              <http://www.rfc-editor.org/info/rfc4724>.
+              <https://www.rfc-editor.org/info/rfc4724>.
 
 Authors' Addresses
 
    Keyur Patel
    Arrcus, Inc.
 
    Email: keyur@arrcus.com
    James Uttaro
    ATT
    200 S. Laurel Ave