draft-ietf-idr-flowspec-l2vpn-00.txt		draft-ietf-idr-flowspec-l2vpn-01.txt
	IDR W. Hao		IDR W. Hao
	Q. Liang		Q. Liang
	Internet Draft Huawei Technologies Ltd.		Internet Draft Huawei Technologies Ltd.
	Intended status: Standards Track Jim Uttaro		Intended status: Standards Track Jim Uttaro
	AT&T		AT&T
	S. Litkowski		S. Litkowski
	Orange Business Service		Orange Business Service
	S. Zhuang		S. Zhuang
	Huawei Technologies Ltd.		Huawei Technologies Ltd.
	Expires: September 2015 March 7, 2015		Expires: November 2015 May 9, 2015
	Dissemination of Flow Specification Rules for L2 VPN		Dissemination of Flow Specification Rules for L2 VPN
	draft-ietf-idr-flowspec-l2vpn-00.txt		draft-ietf-idr-flowspec-l2vpn-01.txt
	Abstract		Abstract
	This document defines BGP flow-spec extension for Ethernet traffic		This document defines BGP flow-spec extension for Ethernet traffic
	filtering in L2 VPN network. SAFI=134 in [RFC5575] is redefined for		filtering in L2 VPN network. SAFI=134 in [RFC5575] is redefined for
	dissemination traffic filtering information in an L2VPN environment.		dissemination traffic filtering information in an L2VPN environment.
	A new subset of component types and extended community also are		A new subset of component types and extended community also are
	defined.		defined.
	Status of this Memo		Status of this Memo
	skipping to change at page 1, line 40		skipping to change at page 1, line 40
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	Internet-Drafts are draft documents valid for a maximum of six		Internet-Drafts are draft documents valid for a maximum of six
	months and may be updated, replaced, or obsoleted by other documents		months and may be updated, replaced, or obsoleted by other documents
	at any time. It is inappropriate to use Internet-Drafts as		at any time. It is inappropriate to use Internet-Drafts as
	reference material or to cite them other than as "work in progress."		reference material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/1id-abstracts.html
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on September 7, 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
	skipping to change at page 2, line 21		skipping to change at page 2, line 21
	document must include Simplified BSD License text as described in		document must include Simplified BSD License text as described in
	Section 4.e of the Trust Legal Provisions and are provided without		Section 4.e of the Trust Legal Provisions and are provided without
	warranty as described in the Simplified BSD License.		warranty as described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction ................................................ 2		1. Introduction ................................................ 2
	2. Layer 2 Flow Specification encoding in BGP................... 3		2. Layer 2 Flow Specification encoding in BGP................... 3
	3. Ethernet Flow Specification encoding in BGP.................. 4		3. Ethernet Flow Specification encoding in BGP.................. 4
	4. Ethernet Flow Specification Traffic Actions.................. 6		4. Ethernet Flow Specification Traffic Actions.................. 6
	5. Security Considerations...................................... 7		5. Security Considerations...................................... 8
	6. IANA Considerations ......................................... 7		6. IANA Considerations ......................................... 8
	6.1. Normative References.................................... 8		6.1. Normative References................................... 10
	6.2. Informative References.................................. 9		6.2. Informative References................................. 10
	7. Acknowledgments ............................................. 9		7. Acknowledgments ............................................ 10
	1. Introduction		1. Introduction
	BGP Flow-spec is an extension to BGP that allows for the		BGP Flow-spec is an extension to BGP that allows for the
	dissemination of traffic flow specification rules. It leverages the		dissemination of traffic flow specification rules. It leverages the
	BGP Control Plane to simplify the distribution of ACLs, new filter		BGP Control Plane to simplify the distribution of ACLs, new filter
	rules can be injected to all BGP peers simultaneously without		rules can be injected to all BGP peers simultaneously without
	changing router configuration. The typical application of BGP Flow-		changing router configuration. The typical application of BGP Flow-
	spec is to automate the distribution of traffic filter lists to		spec is to automate the distribution of traffic filter lists to
	routers for DDOS mitigation.		routers for DDOS mitigation.
	skipping to change at page 3, line 30		skipping to change at page 3, line 30
	[4761], EVPN and LDP-based VPLS [4762] with BGP auto-discovery		[4761], EVPN and LDP-based VPLS [4762] with BGP auto-discovery
	[6074].		[6074].
	This draft proposes a new subset of component types and extended		This draft proposes a new subset of component types and extended
	community to support L2VPN flow-spec application. SAFI=134 in		community to support L2VPN flow-spec application. SAFI=134 in
	[RFC5575] is redefined for dissemination traffic filtering		[RFC5575] is redefined for dissemination traffic filtering
	information in an L2VPN environment.		information in an L2VPN environment.
	2. Layer 2 Flow Specification encoding in BGP		2. Layer 2 Flow Specification encoding in BGP
	The [RFC5575] defines SAFI 133 and SAFI 134 for "dissemination of		The [RFC5575] defines SAFI 133 and SAFI 134 for ''dissemination of
	IPv4 flow specification rules" and "dissemination of VPNv4 flow		IPv4 flow specification rules'' and ''dissemination of VPNv4 flow
	specification rules" respectively. [draft-ietf-idr-flow-spec-v6-06]		specification rules'' respectively. [draft-ietf-idr-flow-spec-v6-06]
	redefines the [RFC5575] SAFIs in order to make them applicable to		redefines the [RFC5575] SAFIs in order to make them applicable to
	both IPv4 and IPv6 applications. This document will further redefine		both IPv4 and IPv6 applications. This document will further redefine
	the SAFI 134 in order to make them applicable to L2VPN applications.		the SAFI 134 in order to make them applicable to L2VPN applications.
	The following changes are defined:		The following changes are defined:
	"SAFI 134 for dissemination of L3VPN flow specification rules" to		''SAFI 134 for dissemination of L3VPN flow specification rules'' to
	now be defined as "SAFI 134 for dissemination of VPN flow		now be defined as ''SAFI 134 for dissemination of VPN flow
	specification rules"		specification rules''
	For SAFI 134 the indication to which address family it is referring		For SAFI 134 the indication to which address family it is referring
	to will be recognized by AFI value (AFI=1 for VPNv4, AFI=2 VPNv6 and		to will be recognized by AFI value (AFI=1 for VPNv4, AFI=2 VPNv6 and
	AFI=25 for L2VPN). Such modification is fully backwards compatible		AFI=25 for L2VPN). Such modification is fully backwards compatible
	with existing implementation and production deployments.		with existing implementation and production deployments.
	3. Ethernet Flow Specification encoding in BGP		3. Ethernet Flow Specification encoding in BGP
	The NLRI format for this address family consists of a fixed-length		The NLRI format for this address family consists of a fixed-length
	Route Distinguisher field (8 bytes) followed by a flow specification,		Route Distinguisher field (8 bytes) followed by a flow specification,
	skipping to change at page 7, line 5		skipping to change at page 7, line 5
	+--------+--------------------+--------------------------+		+--------+--------------------+--------------------------+
	| 0x8006 | traffic-rate | 2-byte as#, 4-byte float |		| 0x8006 | traffic-rate | 2-byte as#, 4-byte float |
	| 0x8007 | traffic-action | bitmask |		| 0x8007 | traffic-action | bitmask |
	| 0x8008 | redirect | 6-byte Route Target |		| 0x8008 | redirect | 6-byte Route Target |
	| 0x8009 | traffic-marking | DSCP value |		| 0x8009 | traffic-marking | DSCP value |
	+--------+--------------------+--------------------------+		+--------+--------------------+--------------------------+
	Besides to support the above extended communities per RFC5575, this		Besides to support the above extended communities per RFC5575, this
	document also proposes the following BGP extended communities		document also proposes the following BGP extended communities
	specifications for Ethernet flow to extend [RFC5575]:		specifications for Ethernet flow to extend [RFC5575]:
	+--------+--------------------+--------------------------+		+--------+------------------------+--------------------------+
	| type | extended community | encoding |		| type | extended community | encoding |
	+--------+--------------------+--------------------------+		+--------+------------------------+--------------------------+
	| 0x800A | VLAN COS marking | COS value |		| 0x800A | VLAN-action | bitmask |
	+--------+--------------------+--------------------------+		| 0x800B | TPID-action | bitmask |
	The VLAN COS marking extended community instructs a system to modify		+--------+------------------------+--------------------------+
	the COS bits of a transiting Ethernet packet to the corresponding
	value. This extended community is encoded as a sequence of 5 zero
	bytes followed by the VLAN COS value encoded in the 3 least
	significant bits of 6th byte.
	In virtual local-area network (VLAN) stacking case, the VLAN COS is		VLAN-action: The VLAN-action extended community consists of 6 bytes
	outer VLAN COS.		which include the fields of action Flags, and two VLAN ID/COS value.
			The action Flags field includes PO, PU, SW, RI, RO, CI and CO Flag
			to indicate the action type. The two VLAN ID/COS value are carried
			in COS1/VLAN ID1 and COS2/VLAN ID2 field respectively.
			0 15
			+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
			|PO|PU|SW|RI|RO|CI|CO| Resv |
			+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
			| COS1 |R | VLAN ID1 |
			+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
			| COS2 |R | VLAN ID2 |
			+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
			PO: Pop action. It indicates the outmost VLAN should be removed.
			PU: Push action. It indicates a new VLAN should be added as outmost
			VLAN, the new VLAN is VLAN ID1.
			SW: Swap action. It indicates the outer VLAN and inner VLAN should
			be swapped.
			RI: Rewrite inner VLAN action. It indicates the inner VLAN should be
			replaced by a new VLAN, the new VLAN is VLAN ID1.
			RO: Rewrite outer VLAN action. It indicates the outer VLAN should be
			replaced by a new VLAN, the new VLAN is VLAN ID2.
			CI: Mapping inner COS action. It indicates the inner COS should be
			replaced by a new COS, the new COS is COS1.
			CO: Mapping outer COS action. It indicates the outer COS should be
			replaced by a new COS, the new COS is COS2.
			Resv: Reserved for future use.
			COS1: 3 bits. COS value.
			COS2: 3 bits. COS value.
			VLAN ID1: 12 bits. VLAN ID value.
			VLAN ID2: 12 bits. VLAN ID value.
			R: Reserved for future use.
			TPID-action: The TPID-action extended community consists of 6 bytes
			which include the fields of action Flags, TPID1 and TPID2.
			0 15
			+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
			|TI|TO| Resv |
			+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
			| TP ID1 |
			+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
			| TP ID2 |
			+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
			TI: Mapping inner TP ID action. It indicates the inner TP ID should
			be replaced by a new TP ID, the new TP ID is TP ID1.
			TO: Mapping outer TP ID action. It indicates the outer TP ID should
			be replaced by a new TP ID, the new TP ID is TP ID2.
			Resv: Reserved for future use.
			In some cases, some more complicated actions are needed, such as
			SwapPop, PushSwap, etc. These actions can be represented using two
			catenated VLAN-actions which are carried in two VLAN-action extended
			communities. For example, Swap and Pop action can be represented by
			catenation of Swap action 1 and Pop action 2.
	5. Security Considerations		5. Security Considerations
	No new security issues are introduced to the BGP protocol by this		No new security issues are introduced to the BGP protocol by this
	specification.		specification.
	6. IANA Considerations		6. IANA Considerations
	IANA is requested to rename currently defined SAFI 134 per [RFC5575]		IANA is requested to rename currently defined SAFI 134 per [RFC5575]
	to read:		to read:
	skipping to change at page 8, line 44		skipping to change at page 9, line 50
	| 24 |This draft | Inner VLAN COS |		| 24 |This draft | Inner VLAN COS |
	+--------+-------------------------------+--------------------------+		+--------+-------------------------------+--------------------------+
	IANA is requested to update the reference for the following		IANA is requested to update the reference for the following
	assignment in the "BGP Extended Communities Type - extended,		assignment in the "BGP Extended Communities Type - extended,
	transitive" registry:		transitive" registry:
	Type value Name Reference		Type value Name Reference
	---------- ---------------------------------------- ---------		---------- ---------------------------------------- ---------
	0x080A Flow spec VLAN COS marking [this document]		0x080A Flow spec VLAN action [this document]
			0x080B Flow spec TPID action [this document]
	6.1. Normative References		6.1. Normative References
	[1] [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[1] [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[2] [RFC5575] P. Marques, N. Sheth, R. Raszuk, B. Greene, J.Mauch,		[2] [RFC5575] P. Marques, N. Sheth, R. Raszuk, B. Greene, J.Mauch,
	D. McPherson, "Dissemination of Flow Specification Rules", RFC		D. McPherson, "Dissemination of Flow Specification Rules", RFC
	5575, August 2009.		5575, August 2009.
	skipping to change at page 9, line 32		skipping to change at page 10, line 39
	[1] [EVPN] Sajassi et al., "BGP MPLS Based Ethernet VPN", draft-		[1] [EVPN] Sajassi et al., "BGP MPLS Based Ethernet VPN", draft-
	ietf-l2vpn-evpn-07.txt, work in progress, May, 2014.		ietf-l2vpn-evpn-07.txt, work in progress, May, 2014.
	[2] [IEEE 802.1p] Javin, et.al. "IEEE 802.1p: LAN Layer 2 QoS/CoS		[2] [IEEE 802.1p] Javin, et.al. "IEEE 802.1p: LAN Layer 2 QoS/CoS
	Protocol for Traffic Prioritization", 2012-02-15		Protocol for Traffic Prioritization", 2012-02-15
	7. Acknowledgments		7. Acknowledgments
	The authors wish to acknowledge the important contributions of		The authors wish to acknowledge the important contributions of
	Xiaohu Xu, Lucy Yong.		Hannes Gredler, Xiaohu Xu and Lucy Yong.
	Authors' Addresses		Authors' Addresses
	Weiguo Hao		Weiguo Hao
	Huawei Technologies		Huawei Technologies
	101 Software Avenue,		101 Software Avenue,
	Nanjing 210012		Nanjing 210012
	China		China
	Email: haoweiguo@huawei.com		Email: haoweiguo@huawei.com
	Qiandeng Liang		Qiandeng Liang
	Huawei Technologies		Huawei Technologies
	101 Software Avenue,		101 Software Avenue,
	Nanjing 210012		Nanjing 210012
	China		China
	Email: liangqiandeng@huawei.com		Email: liangqiandeng@huawei.com
			Shunwan Zhuang
			Huawei Technologies
			Huawei Bld., No.156 Beiqing Rd.
			Beijing 100095
			China
			Email: zhuangshunwan@huawei.com
	James Uttaro		James Uttaro
	AT&T		AT&T
	EMail: uttaro@att.com		EMail: uttaro@att.com
	Stephane Litkowski		Stephane Litkowski
	Orange		Orange
	stephane.litkowski@orange.com		stephane.litkowski@orange.com
	Shunwan Zhuang
	Huawei Technologies
	Huawei Bld., No.156 Beiqing Rd.
	Beijing 100095
	China
	Email: zhuangshunwan@huawei.com
End of changes. 13 change blocks.
	31 lines changed or deleted		103 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/