<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.keyur-bgp-af-specific-rt-constrain" target="https://datatracker.ietf.org/doc/html/draft-keyur-bgp-af-specific-rt-constrain-01">
   <front>
      <title>IPv6 AF Extensions for Route Target Distribution</title>
      <author initials="K." surname="Patel" fullname="Keyur Patel">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="R." surname="Raszuk" fullname="Robert Raszuk">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="M." surname="Djernaes" fullname="Martin Djernaes">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="J." surname="Dong" fullname="Jie Dong">
         <organization>Huawei Technologies Co., Ltd.</organization>
      </author>
      <author initials="M." surname="Chen" fullname="Mach Chen">
         <organization>Huawei Technologies Co., Ltd.</organization>
      </author>
      <date month="March" day="9" year="2011" />
      <abstract>
	 <t>The current route target distribution specification described in
RFC4684 defines Route Target NLRIs of maxiumum 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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-keyur-bgp-af-specific-rt-constrain-01" />
   
</reference>
