<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-vpn-prefix-orf" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-vpn-prefix-orf-42">
   <front>
      <title>VPN Prefix Outbound Route Filter (VPN Prefix ORF) for BGP-4</title>
      <author initials="W." surname="Wang" fullname="Wei Wang">
         <organization>China Telecom</organization>
      </author>
      <author initials="A." surname="Wang" fullname="Aijun Wang">
         <organization>China Telecom</organization>
      </author>
      <author initials="H." surname="Wang" fullname="Haibo Wang">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="G. S." surname="Mishra" fullname="Gyan Mishra">
         <organization>Verizon Inc.</organization>
      </author>
      <author initials="J." surname="Dong" fullname="Jie Dong">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="May" day="19" year="2026" />
      <abstract>
	 <t>   This document defines an experimental specification for a new type of
   Outbound Route Filter (ORF), known as the Virtual Private Network
   (VPN) Prefix ORF.  The VPN Prefix ORF mechanism is applicable when
   VPN routes from different Virtual Routing and Forwarding (VRF)
   instances are exchanged through a single shared Border Gateway
   Protocol (BGP) session.  The purpose of the VPN Prefix ORF mechanism
   is to control the overload of VPN routes based on Route Distinguisher
   (RD), Route Target (RT) and other necessary routing information.
   This mechanism is applicable to intra-domain scenarios.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-vpn-prefix-orf-42" />
   
</reference>
