--- 1/draft-ietf-idr-bgp-ipv6-rt-constrain-10.txt	2018-02-11 18:13:08.959108940 -0800
+++ 2/draft-ietf-idr-bgp-ipv6-rt-constrain-11.txt	2018-02-11 18:13:08.975109322 -0800
@@ -1,24 +1,24 @@
 
 Network Working Group                                           K. Patel
 Internet-Draft                                              Arrcus, Inc.
 Intended status: Standards Track                               R. Raszuk
-Expires: July 3, 2017                                       Bloomberg LP
+Expires: August 16, 2018                                    Bloomberg LP
                                                              M. Djernaes
                                                         Juniper Networks
                                                                  J. Dong
                                                                  M. Chen
                                                      Huawei Technologies
-                                                       December 30, 2016
+                                                       February 12, 2018
 
              IPv6 Extensions for Route Target Distribution
-                draft-ietf-idr-bgp-ipv6-rt-constrain-10
+                draft-ietf-idr-bgp-ipv6-rt-constrain-11
 
 Abstract
 
    The current route target distribution specification as described in
    [RFC 4684] defines Route Target NLRIs of maximum length of 12 bytes.
    The IPv6 specific Route Target extended community is defined in [RFC
    5701] as length of 20 bytes.  Since the current specification only
    supports prefixes of maximum length of 12 bytes, the lack of an IPv6
    specific Route Target reachability information may be a problem when
    an operator wants to use this application in a pure IPv6 environment.
@@ -32,36 +32,36 @@
    document are to be interpreted as described in RFC 2119 [RFC2119].
 
 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 July 3, 2017.
+   This Internet-Draft will expire on August 16, 2018.
 
 Copyright Notice
 
-   Copyright (c) 2016 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.
 
 Table of Contents
 
    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
@@ -152,52 +152,52 @@
    The authors would like to thank Pedro Marques, John Scudder, Alton Lo
    and Zhenqiang Li for discussions and review.
 
 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>.
 
    [RFC4360]  Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
               Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,
-              February 2006, <http://www.rfc-editor.org/info/rfc4360>.
+              February 2006, <https://www.rfc-editor.org/info/rfc4360>.
 
    [RFC4684]  Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,
               R., Patel, K., and J. Guichard, "Constrained Route
               Distribution for Border Gateway Protocol/MultiProtocol
               Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual
               Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684,
-              November 2006, <http://www.rfc-editor.org/info/rfc4684>.
+              November 2006, <https://www.rfc-editor.org/info/rfc4684>.
 
    [RFC5492]  Scudder, J. and R. Chandra, "Capabilities Advertisement
               with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February
-              2009, <http://www.rfc-editor.org/info/rfc5492>.
+              2009, <https://www.rfc-editor.org/info/rfc5492>.
 
    [RFC5701]  Rekhter, Y., "IPv6 Address Specific BGP Extended Community
               Attribute", RFC 5701, DOI 10.17487/RFC5701, November 2009,
-              <http://www.rfc-editor.org/info/rfc5701>.
+              <https://www.rfc-editor.org/info/rfc5701>.
 
 7.2.  Informative References
 
    [RFC4760]  Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
               "Multiprotocol Extensions for BGP-4", RFC 4760,
               DOI 10.17487/RFC4760, January 2007,
-              <http://www.rfc-editor.org/info/rfc4760>.
+              <https://www.rfc-editor.org/info/rfc4760>.
 
 Authors' Addresses
 
    Keyur Patel
    Arrcus, Inc.
    USA
 
    Email: keyur@arrcus.com
 
    Robert Raszuk