--- 1/draft-ietf-idr-bgp-ipv6-rt-constrain-03.txt 2013-08-08 00:14:21.858169733 -0700 +++ 2/draft-ietf-idr-bgp-ipv6-rt-constrain-04.txt 2013-08-08 00:14:21.874170153 -0700 @@ -1,86 +1,86 @@ Network Working Group K. Patel Internet-Draft Cisco Systems Intended status: Standards Track R. Raszuk -Expires: June 21, 2013 NTT MCL Inc. +Expires: February 09, 2014 NTT MCL Inc. M. Djernaes Juniper Networks J. Dong M. Chen Huawei Technologies - December 18, 2012 + August 08, 2013 IPv6 Extensions for Route Target Distribution - draft-ietf-idr-bgp-ipv6-rt-constrain-03 + draft-ietf-idr-bgp-ipv6-rt-constrain-04 Abstract The current route target distribution specification described in RFC4684 defines Route Target NLRIs of maximum length of 12 bytes. The IPv6 specific Route Target extended community is defined in [RFC5701] 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. This document defines an extension that allows BGP to exchange longer length IPv6 Route Target prefixes. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. -Status of this Memo +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/. 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 June 21, 2013. + This Internet-Draft will expire on February 09, 2014. Copyright Notice - Copyright (c) 2012 IETF Trust and the persons identified as the + Copyright (c) 2013 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 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 2. BGP IPv6 Constrained Route Target Capability . . . . . . . . . 4 - 3. IPv6 Constrained Route Target NLRI Advertisements . . . . . . . 4 - 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 - 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 - 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 - 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 + 2. BGP IPv6 Constrained Route Target Capability . . . . . . . . 2 + 3. IPv6 Constrained Route Target NLRI Advertisements . . . . . . 3 + 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 + 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 + 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 + 7.2. Informative References . . . . . . . . . . . . . . . . . 4 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 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 to distribute longer length Route Target prefixes. A new BGP @@ -112,23 +111,24 @@ This prefix is structured as follows: +-------------------------------+ | origin as (4 octets) | +-------------------------------+ | route target (8 or 20 octets)| ~ ~ | | +-------------------------------+ + Except for the default route target, which is encoded as a zero- - length prefix, the minimum prefix length is 32 bits. As the - origin-AS field cannot be interpreted as a prefix. + length prefix, the minimum prefix length is 32 bits. As the origin- + AS field cannot be interpreted as a prefix. Route targets can then be expressed as prefixes, where, for instance, a prefix would encompass all route target extended communities assigned by a given Global Administrator [RFC4360] and [RFC5701]. Alternatively, route target prefixes could be aggregated however if done so, then only the Local Administrator field of the Route Target can be aggregated. Route Target Type and the Global Administrator Route Target fields MUST not be aggregated. The default route target can be used to indicate to a peer the @@ -172,25 +171,24 @@ [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement with BGP-4", RFC 5492, February 2009. [RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community Attribute", RFC 5701, 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, January + 2007. Authors' Addresses - Keyur Patel Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 USA Email: keyupate@cisco.com Robert Raszuk NTT MCL Inc.