< draft-xu-bess-l3vpn-prefix-orf-01.txt		draft-xu-bess-l3vpn-prefix-orf-02.txt >
	Network Working Group X. Xu		Network Working Group X. Xu
	Internet-Draft Huawei		Internet-Draft Huawei
	Intended status: Standards Track C. Jacquenet		Intended status: Standards Track C. Jacquenet
	Expires: September 21 2015 Orange		Expires: October 29, 2015 Orange
	March 22, 2015		L. Fang
			Microsoft
			April 27, 2015
	L3VPN Address Prefix Based Outbound Route Filter for BGP-4		L3VPN Address Prefix Based Outbound Route Filter for BGP-4
	draft-xu-bess-l3vpn-prefix-orf-01		draft-xu-bess-l3vpn-prefix-orf-02
	Abstract		Abstract
	This document defines a new Outbound Router Filter (ORF) type for		This document defines a new Outbound Router Filter (ORF) type for
	BGP, refered to as "L3VPN Address Prefix Outbound Route Filter", that		BGP, refered to as "L3VPN Address Prefix Outbound Route Filter", that
	can be used to perform L3VPN address-prefix-based route filtering.		can be used to perform L3VPN address-prefix-based route filtering.
	This ORF-type supports prefix-length- or range-based matching, wild-		This ORF-type supports prefix-length- or range-based matching, wild-
	card-based address prefix matching, as well as the exact address		card-based address prefix matching, as well as the exact address
	prefix matching for L3VPN address families. The L3VPN Address Prefix		prefix matching for L3VPN address families. The L3VPN Address Prefix
	ORF is applicable in the Virtual Subnet context.		ORF is applicable in the Virtual Subnet context.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 39 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on September 21, 2015.		This Internet-Draft will expire on October 29, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. L3VPN Address Prefix ORF Encoding . . . . . . . . . . . . . . 3		3. L3VPN Address Prefix ORF Encoding . . . . . . . . . . . . . . 3
	4. L3VPN Address Prefix ORF Matching . . . . . . . . . . . . . . 4		4. L3VPN Address Prefix ORF Matching . . . . . . . . . . . . . . 3
	5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4		5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 4		7. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
	8.1. Normative References . . . . . . . . . . . . . . . . . . 4		8.1. Normative References . . . . . . . . . . . . . . . . . . 4
	8.2. Informative References . . . . . . . . . . . . . . . . . 5		8.2. Informative References . . . . . . . . . . . . . . . . . 4
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
	1. Introduction		1. Introduction
	The Outbound Route Filtering (ORF) Capability defined in [RFC5291]		The Outbound Route Filtering (ORF) Capability defined in [RFC5291]
	provides a mechanism for a BGP speaker to send to its BGP peer a set		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		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]		updates to the speaker. The Address Prefix ORF defined in [RFC5292]
	is used to perform address-prefix-based route filtering. However,		is used to perform address-prefix-based route filtering. However,
	the Address Prefix ORF is not much suitable for L3VPN [RFC4364] route		the Address Prefix ORF is not much suitable for L3VPN [RFC4364] route
	filtering since there is no Route-Target (RT) field contained in the		filtering since there is no Route-Target (RT) field contained in the
	skipping to change at page 4, line 8 ¶		skipping to change at page 3, line 33 ¶
	A L3VPN Address Prefix ORF entry is encoded as follows: the "Action",		A L3VPN Address Prefix ORF entry is encoded as follows: the "Action",
	"Match" and "Reserved" fields of the entry are encoded in the common		"Match" and "Reserved" fields of the entry are encoded in the common
	part [RFC5291], while the remaining fields of the entry are encoded		part [RFC5291], while the remaining fields of the entry are encoded
	in the "type specific part" [RFC5291], as shown in Figure 1. When		in the "type specific part" [RFC5291], as shown in Figure 1. When
	the Action component of an ORF entry specifies REMOVE-ALL, the entry		the Action component of an ORF entry specifies REMOVE-ALL, the entry
	consists of only the common part.		consists of only the common part.
	+--------------------------------+		+--------------------------------+
	| Sequence (4 octets) |		| Sequence (4 octets) |
	+--------------------------------+		+--------------------------------+
	| Route Target (8 octets) |		| Route Target(8 or 16 octets) |
	+--------------------------------+		+--------------------------------+
	| Minlen (1 octet) |		| Minlen (1 octet) |
	+--------------------------------+		+--------------------------------+
	| Maxlen (1 octet) |		| Maxlen (1 octet) |
	+--------------------------------+		+--------------------------------+
	| Length (1 octet) |		| Length (1 octet) |
	+--------------------------------+		+--------------------------------+
	| Prefix (variable length) |		| Prefix (variable length) |
	+--------------------------------+		+--------------------------------+
	skipping to change at line 189 ¶		skipping to change at page 5, line 4 ¶
	[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private		[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
	Networks (VPNs)", RFC 4364, February 2006.		Networks (VPNs)", RFC 4364, February 2006.
	Authors' Addresses		Authors' Addresses
	Xiaohu Xu		Xiaohu Xu
	Huawei		Huawei
	Email: xuxiaohu@huawei.com		Email: xuxiaohu@huawei.com
	Christian Jacquenet		Christian Jacquenet
	Orange		Orange
	Email: christian.jacquenet@orange.com		Email: christian.jacquenet@orange.com
			Luyuan Fang
			Microsoft
			Email: lufang@microsoft.com
End of changes. 9 change blocks.
	10 lines changed or deleted		11 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/