IPv6 Extensions for Route Target Distribution
draft-ietf-idr-bgp-ipv6-rt-constrain-05
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Keyur Patel , Robert Raszuk , Martin Djernaes , Jie Dong , Mach Chen | ||
Last updated | 2014-12-12 (Latest revision 2014-06-10) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Keyur Patel
Robert Raszuk
Martin Djernaes
Jie Dong
Mach Chen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)