< draft-allan-l2vpn-mldp-evpn-01.txt		draft-allan-l2vpn-mldp-evpn-02.txt >
	L2VPN Working Group Dave Allan, Jeff Tantsura		L2VPN Working Group Dave Allan, Jeff Tantsura
	Internet Draft Ericsson		Internet Draft Ericsson
	Intended status: Standards Track		Intended status: Standards Track
	Expires: January 2014		Expires: July 2014
	July 2013		January 2014
	mLDP extensions for integrating EVPN and multicast		mLDP extensions for integrating EVPN and multicast
	draft-allan-l2vpn-mldp-evpn-01		draft-allan-l2vpn-mldp-evpn-02
	Abstract		Abstract
	This document describes how mLDP FECs can be encoded to support both		This document describes how mLDP FECs can be encoded to support both
	service specific and shared multicast trees and describes the		service specific and shared multicast trees and describes the
	associated procedures for EVPN PEs. Thus, mLDP can implement		associated procedures for EVPN PEs. Thus, mLDP can implement
	multicast for EVPN.		multicast for EVPN.
	Status of this Memo		Status of this Memo
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	documents at any time. It is inappropriate to use Internet-		documents at any time. It is inappropriate to use Internet-
	Drafts as reference material or to cite them other than as "work		Drafts as reference material or to cite them other than as "work
	in progress".		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/ietf/1id-abstracts.txt.
	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 January 2014.		This Internet-Draft will expire on July 2014.
	Copyright and License Notice		Copyright and License Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2014 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		carefully, as they describe your rights and restrictions with
	respect to this document. Code Components extracted from this		respect to this document. Code Components extracted from this
	document must include Simplified BSD License text as described		document must include Simplified BSD License text as described
	in Section 4.e of the Trust Legal Provisions and are provided		in Section 4.e of the Trust Legal Provisions and are provided
	skipping to change at page 3, line 7 ¶		skipping to change at page 3, line 7 ¶
	David Allan, Jeff Tantsura		David Allan, Jeff Tantsura
	1.2. Requirements Language		1.2. Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC2119 [1].		document are to be interpreted as described in RFC2119 [1].
	2. Changes since last version		2. Changes since last version
	1) Clarifications to the use of FEC encoding for RTs and VLANs		1) Keep alive update.
	added to section 6.
	3. Conventions used in this document		3. Conventions used in this document
	3.1. Terminology		3.1. Terminology
	BCB: Backbone Core Bridge		BCB: Backbone Core Bridge
	BEB: Backbone Edge Bridge		BEB: Backbone Edge Bridge
	BU: Broadcast/Unknown		BU: Broadcast/Unknown
	B-MAC: Backbone MAC Address		B-MAC: Backbone MAC Address
	B-VID: Backbone VLAN ID		B-VID: Backbone VLAN ID
	skipping to change at page 7, line 12 ¶		skipping to change at page 7, line 12 ¶
	Where:		Where:
	- RT is the route target for the EVPN instance		- RT is the route target for the EVPN instance
	- Sorted list of DF addresses identifies the set of leaves that have		- Sorted list of DF addresses identifies the set of leaves that have
	registered interest in one or more Ethernet services (either C/S or I		registered interest in one or more Ethernet services (either C/S or I
	tagged).		tagged).
	7. Acknowledgements		7. Acknowledgements
	The authors would like to thank Panagiotis Saltsidis, Jakob Heitz and		The authors would like to thank Panagiotis Saltsidis, Jakob Heitz,
	Janos Farkas for their detailed review of this draft.		Don Fedyk and Janos Farkas for their detailed review of this draft.
	8. Security Considerations		8. Security Considerations
	For a future version of this document.		For a future version of this document.
	9. IANA Considerations		9. IANA Considerations
	For a future version of this document.		For a future version of this document.
	10. References		10. References
End of changes. 6 change blocks.
	9 lines changed or deleted		8 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/