]> VPN Address Prefix Based Outbound Route Filter for BGP-4 Huawei
xuxiaohu@huawei.com
This document defines a new Outbound Router Filter (ORF) type for BGP, refered to as "VPN Address Prefix Outbound Route Filter", that can be used to perform VPN address-prefix-based route filtering. This ORF-type supports prefix-length- or range-based matching, wild-card-based address prefix matching, as well as the exact address prefix matching for VPN address families. The VPN Address Prefix ORF is applicable in the context of Virtual Subnet and may also be applicable in other BGP/MPLS VPN environments.
The Outbound Route Filtering (ORF) Capability defined in provides a mechanism for a BGP speaker to send to its BGP peer a set of ORFs that can be used by its peer to filter its outbound routing updates to the speaker. The Address Prefix ORF defined in is used to perform address-prefix-based route filtering. However, the Address Prefix ORF is not much suitable for VPN route filting since there is no Route-Target (RT) field contained in the Address Prefix ORF entry. This document builds on and defines a new ORF-type for BGP, refered to as "VPN Address Prefix Outbound Route Filter (VPN Address Prefix ORF)", that can be used to perform VPN address-prefix-based route filtering. The VPN Address Prefix ORF supports prefix-length- or range-based matching, wild-card-based address prefix matching, as well as the exact address prefix matching for VPN address families. The VPN Address Prefix ORF is applicable in the context of Virtual Subnet and may also be applicable in other BGP/MPLS VPN environments.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
This memo makes use of the terms defined in and .
A VPN Address Prefix ORF entry includes a Route Target field in addition to those fields which have been contained in the Address Prefix ORF. That's to say, the VPN Address Prefix ORF entry consists of the fields <Sequence, Match, Route-Target, Length, Prefix, Minlen, Maxlen>. Note that the Prefix field here doesn't include the Route Distinguisher (RD) part of a VPN address prefix. For example, in the case of VPNv4 address prefix, only the IPv4 address prefix part is contained in that Prefix field.
When performing route matching search on those VPN routes which are assocaited with the Route Target as specified in the received VPN Adress Prefix ORF, the Address-Prefix-ORF-specific matching rules defined in are almost preserved except that the RD SHOULD be ingored.
The authors would like to thank Mach Chen and Shunwan Zhuang for their comments on this document.
The type code of the VPN Address Prefix ORF needs to be assigned by the IANA.
This document does not introduce any new security considerations.
&RFC2119;