Internet DRAFT - draft-xu-l3vpn-prefix-orf
draft-xu-l3vpn-prefix-orf
Network Working Group X. Xu
Internet-Draft Huawei
Intended status: Standards Track January 23, 2014
Expires: July 27, 2014
VPN Address Prefix Based Outbound Route Filter for BGP-4
draft-xu-l3vpn-prefix-orf-00
Abstract
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 IP VPN environments.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 27, 2014.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Xu Expires July 27, 2014 [Page 1]
Internet-Draft January 2014
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. VPN Address Prefix ORF Encoding . . . . . . . . . . . . . . . 3
4. VPN Address Prefix ORF Matching . . . . . . . . . . . . . . . 3
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
7. Security Considerations . . . . . . . . . . . . . . . . . . . 3
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
8.1. Normative References . . . . . . . . . . . . . . . . . . 3
8.2. Informative References . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
The Outbound Route Filtering (ORF) Capability defined in [RFC5291]
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 [RFC5292]
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 [RFC5292] 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 [I-D.xu-l3vpn-virtual-subnet] and may also be applicable in
other BGP/MPLS IP VPN [RFC4364] environments.
1.1. Requirements Language
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 [RFC2119].
Xu Expires July 27, 2014 [Page 2]
Internet-Draft January 2014
2. Terminology
This memo makes use of the terms defined in [RFC5292] and [RFC4364].
3. VPN Address Prefix ORF Encoding
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.
4. VPN Address Prefix ORF Matching
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 [RFC5292] are almost preserved except that the RD SHOULD
be ingored.
5. Acknowledgements
The authors would like to thank Mach Chen and Shunwan Zhuang for
their comments on this document.
6. IANA Considerations
The type code of the VPN Address Prefix ORF needs to be assigned by
the IANA.
7. Security Considerations
This document does not introduce any new security considerations.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5291] Chen, E. and Y. Rekhter, "Outbound Route Filtering
Capability for BGP-4", RFC 5291, August 2008.
Xu Expires July 27, 2014 [Page 3]
Internet-Draft January 2014
[RFC5292] Chen, E. and S. Sangli, "Address-Prefix-Based Outbound
Route Filter for BGP-4", RFC 5292, August 2008.
8.2. Informative References
[I-D.xu-l3vpn-virtual-subnet]
Building, K., Hares, S., Yongbing, F., Jacquenet, C.,
Boyes, T., and B. Fee, "Virtual Subnet: A L3VPN-based
Subnet Extension Solution", draft-xu-l3vpn-virtual-
subnet-02 (work in progress), November 2013.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, February 2006.
Author's Address
Xiaohu Xu
Huawei
Email: xuxiaohu@huawei.com
Xu Expires July 27, 2014 [Page 4]
