--- 1/draft-ietf-idr-bgp-ipv6-rt-constrain-07.txt 2015-11-25 01:15:09.405905162 -0800 +++ 2/draft-ietf-idr-bgp-ipv6-rt-constrain-08.txt 2015-11-25 01:15:09.421905548 -0800 @@ -1,24 +1,24 @@ Network Working Group K. Patel Internet-Draft Cisco Systems Intended status: Standards Track R. Raszuk -Expires: December 26, 2015 Mirantis Inc. +Expires: May 28, 2016 Bloomberg LP M. Djernaes Juniper Networks J. Dong M. Chen Huawei Technologies - June 24, 2015 + November 25, 2015 IPv6 Extensions for Route Target Distribution - draft-ietf-idr-bgp-ipv6-rt-constrain-07 + draft-ietf-idr-bgp-ipv6-rt-constrain-08 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. @@ -38,21 +38,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 http://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 December 26, 2015. + This Internet-Draft will expire on May 28, 2016. Copyright Notice Copyright (c) 2015 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 publication of this document. Please review these documents @@ -65,21 +65,21 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. BGP IPv6 Constrained Route Target Capability . . . . . . . . 3 3. IPv6 Constrained Route Target NLRI Advertisements . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 - 7.2. Informative References . . . . . . . . . . . . . . . . . 4 + 7.2. Informative References . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction The current constrained route distribution specification defined in [RFC4684] supports prefixes with a maximum length of 12 bytes. The prefix length needs to be extended to support the IPv6 specific Route Target extended community defined in [RFC5701] which is 20 bytes in length. This document defines an extension to the current constrained route distribution specification that allows BGP speakers @@ -150,60 +150,69 @@ 6. Acknowledgements 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, March 1997. + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, + . - [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway - Protocol 4 (BGP-4)", RFC 4271, January 2006. + [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, + . [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended - Communities Attribute", RFC 4360, February 2006. + Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, + February 2006, . [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, November 2006. + Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684, + November 2006, . [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement - with BGP-4", RFC 5492, February 2009. + with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February + 2009, . [RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community - Attribute", RFC 5701, November 2009. + Attribute", RFC 5701, DOI 10.17487/RFC5701, November 2009, + . 7.2. Informative References [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, - "Multiprotocol Extensions for BGP-4", RFC 4760, January - 2007. + "Multiprotocol Extensions for BGP-4", RFC 4760, + DOI 10.17487/RFC4760, January 2007, + . Authors' Addresses Keyur Patel Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 USA Email: keyupate@cisco.com Robert Raszuk - Mirantis Inc. - 615 National Ave. #100 - Mt View, CA 94043 + Bloomberg LP + 731 Lexington Ave + New York City, NY 10022 USA Email: robert@raszuk.net Martin Djernaes Juniper Networks 1194 N. Mathilda Avenue Sunnyvale, CA 94089 USA