draft-ietf-idr-bgp-ipv6-rt-constrain-06.txt   draft-ietf-idr-bgp-ipv6-rt-constrain-07.txt 
Network Working Group K. Patel Network Working Group K. Patel
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track R. Raszuk Intended status: Standards Track R. Raszuk
Expires: June 25, 2015 Mirantis Inc. Expires: December 26, 2015 Mirantis Inc.
M. Djernaes M. Djernaes
Juniper Networks Juniper Networks
J. Dong J. Dong
M. Chen M. Chen
Huawei Technologies Huawei Technologies
December 22, 2014 June 24, 2015
IPv6 Extensions for Route Target Distribution IPv6 Extensions for Route Target Distribution
draft-ietf-idr-bgp-ipv6-rt-constrain-06 draft-ietf-idr-bgp-ipv6-rt-constrain-07
Abstract Abstract
The current route target distribution specification as described in The current route target distribution specification as described in
[RFC 4684] defines Route Target NLRIs of maximum length of 12 bytes. [RFC 4684] defines Route Target NLRIs of maximum length of 12 bytes.
The IPv6 specific Route Target extended community is defined in [RFC The IPv6 specific Route Target extended community is defined in [RFC
5701] as length of 20 bytes. Since the current specification only 5701] as length of 20 bytes. Since the current specification only
supports prefixes of maximum length of 12 bytes, the lack of an IPv6 supports prefixes of maximum length of 12 bytes, the lack of an IPv6
specific Route Target reachability information may be a problem when specific Route Target reachability information may be a problem when
an operator wants to use this application in a pure IPv6 environment. an operator wants to use this application in a pure IPv6 environment.
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 25, 2015. This Internet-Draft will expire on December 26, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 7 skipping to change at page 4, line 7
can be aggregated. Route Target Type and the Global Administrator can be aggregated. Route Target Type and the Global Administrator
Route Target fields MUST not be aggregated. Route Target fields MUST not be aggregated.
The default route target can be used to indicate to a peer the The default route target can be used to indicate to a peer the
willingness to receive all VPN route advertisements such as, for willingness to receive all VPN route advertisements such as, for
instance, the case of a route reflector speaking to one of its PE instance, the case of a route reflector speaking to one of its PE
router clients. router clients.
4. IANA Considerations 4. IANA Considerations
This document defined the IPV6 Constrained Route Target Capability This document defined the IPv6 Constrained Route Target Capability
for BGP. The Capability code needs to be assigned by the IANA. for BGP. The Capability code needs to be assigned by the IANA.
5. Security Considerations 5. Security Considerations
This extension to [RFC4684] does not change the underlying security This extension to [RFC4684] does not change the underlying security
issues inherent in the existing BGP and [RFC4684]. issues inherent in the existing BGP and [RFC4684].
6. Acknowledgements 6. Acknowledgements
The authors would like to thank Pedro Marques, John Scudder, Alton Lo The authors would like to thank Pedro Marques, John Scudder, Alton Lo
 End of changes. 6 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/