draft-ietf-idr-bgp-ipv6-rt-constrain-11.txt   draft-ietf-idr-bgp-ipv6-rt-constrain-12.txt 
Network Working Group K. Patel Network Working Group K. Patel
Internet-Draft Arrcus, Inc. Internet-Draft Arrcus, Inc.
Intended status: Standards Track R. Raszuk Intended status: Standards Track R. Raszuk
Expires: August 16, 2018 Bloomberg LP Expires: October 28, 2018 Bloomberg LP
M. Djernaes M. Djernaes
Juniper Networks Juniper Networks
J. Dong J. Dong
M. Chen M. Chen
Huawei Technologies Huawei Technologies
February 12, 2018 April 26, 2018
IPv6 Extensions for Route Target Distribution IPv6 Extensions for Route Target Distribution
draft-ietf-idr-bgp-ipv6-rt-constrain-11 draft-ietf-idr-bgp-ipv6-rt-constrain-12
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 https://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 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 August 16, 2018. This Internet-Draft will expire on October 28, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://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 publication of this document. Please review these documents
skipping to change at page 3, line 7 skipping to change at page 3, line 7
to distribute longer length Route Target prefixes. A new BGP to distribute longer length Route Target prefixes. A new BGP
capability known as BGP IPv6 Constrained Route Target capability is capability known as BGP IPv6 Constrained Route Target capability is
defined as part of extension that allows an exchange of longer length defined as part of extension that allows an exchange of longer length
Route Target prefixes. BGP speakers that do not exchange this Route Target prefixes. BGP speakers that do not exchange this
capability MUST use Route Target NLRIs of maximum length of 12 bytes. capability MUST use Route Target NLRIs of maximum length of 12 bytes.
In this way, the current extension would preserve the backward In this way, the current extension would preserve the backward
compatibility with [RFC4684]. compatibility with [RFC4684].
2. BGP IPv6 Constrained Route Target Capability 2. BGP IPv6 Constrained Route Target Capability
The "BGP IPV6 Constrained Route Target Capability" is a new BGP The "BGP IPv6 Constrained Route Target Capability" is a new BGP
capability [RFC5492]. The Capability code for this capability is capability [RFC5492]. The Capability code for this capability is
specified in the IANA Considerations section of this document. The specified in the IANA Considerations section of this document. The
Capability length field of this capability is zero. Capability length field of this capability is zero.
By advertising this capability to a peer, a BGP speaker conveys to By advertising this capability to a peer, a BGP speaker conveys to
the peer that the speaker support the longer length Route Target the peer that the speaker support the longer length Route Target
prefixes and the related procedures described in this document. prefixes and the related procedures described in this document.
3. IPv6 Constrained Route Target NLRI Advertisements 3. IPv6 Constrained Route Target NLRI Advertisements
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 IANA is requested to assign one new code point for "IPv6 Constrained
for BGP. The Capability code needs to be assigned by the IANA. Route Target Capability" from the "First Come First Served" range of
BGP "Capability Codes" registry.
+-------+------------------------------------------+----------------+
| Value | Description | Reference |
+-------+------------------------------------------+----------------+
| TBA | IPv6 Constrained Route Target Capability | [this document]|
+-------+------------------------------------------+----------------+
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
and Zhenqiang Li for discussions and review. and Zhenqiang Li for discussions and review.
 End of changes. 6 change blocks. 
7 lines changed or deleted 14 lines changed or added

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