%% You should probably cite draft-ietf-idr-bgp-ipv6-rt-constrain-12 instead of this revision. @techreport{ietf-idr-bgp-ipv6-rt-constrain-02, number = {draft-ietf-idr-bgp-ipv6-rt-constrain-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ipv6-rt-constrain/02/}, author = {Keyur Patel and Robert Raszuk and Martin Djernaes and Jie Dong and Mach Chen}, title = {{IPv6 Extensions for Route Target Distribution}}, pagetotal = 7, year = 2012, month = jun, day = 12, 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.}, }