< draft-hao-trill-dup-avoidance-active-active-00.txt		draft-hao-trill-dup-avoidance-active-active-01.txt >
	TRILL Weiguo Hao		TRILL Weiguo Hao
	Yizhou Li		Yizhou Li
	Zhibo Hu		Zhibo Hu
	Internet Draft Huawei		Internet Draft Huawei
	Intended status: Standards Track December 3, 2013		Intended status: Standards Track February 14, 2014
	Expires: June 2014		Expires: August 2014
	Frame Duplication Avoidance For TRILL Active-Active Access		Frame Duplication Avoidance For TRILL Active-Active Access
	draft-hao-trill-dup-avoidance-active-active-00.txt		draft-hao-trill-dup-avoidance-active-active-01.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79. This document may not be modified,		provisions of BCP 78 and BCP 79. This document may not be modified,
	and derivative works of it may not be created, and it may not be		and derivative works of it may not be created, and it may not be
	published except as an Internet-Draft.		published except as an Internet-Draft.
	skipping to change at page 2, line 13 ¶		skipping to change at page 2, line 13 ¶
	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/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 June 3, 2009.		This Internet-Draft will expire on August 14, 2009.
	Copyright Notice		Copyright 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 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
	skipping to change at page 5, line 22 ¶		skipping to change at page 5, line 22 ¶
	[RFC2119].		[RFC2119].
	This document uses the same terminology as found in the active-		This document uses the same terminology as found in the active-
	active problem statement draft [TRILL-Active-PS]. Some of the terms		active problem statement draft [TRILL-Active-PS]. Some of the terms
	defined in the that document have been repeated in this section for		defined in the that document have been repeated in this section for
	the convenience of the reader, along with additional terminology		the convenience of the reader, along with additional terminology
	that is used by this document.		that is used by this document.
	CE - customer equipment. Could be a bridge or end station.		CE - customer equipment. Could be a bridge or end station.
	FGL - Fine Grained Label.		FGL -Fine Grained Label.
	Edge group - a group of edge RBs to which one CE is multiply		Edge group - a group of edge RBs to which one CE is multiply
	Attached, a edge group corresponds to a MC-LAG. One RB can be in		Attached, a edge group corresponds to a MC-LAG. One RB can be in
	more than one edge group.		more than one edge group.
	3. DF election mechanism overview		3. DF election mechanism overview
	Each CE is multi-homed to multiple edge RBs in active-active mode		Each CE is multi-homed to multiple edge RBs in active-active mode
	through an MC-LAG. These edge RBs form one edge group. An edge group		through an MC-LAG. These edge RBs form one edge group. An edge group
	corresponds to an MC-LAG. A RB may join multiple edge groups to		corresponds to an MC-LAG. A RB may join multiple edge groups to
	skipping to change at page 5, line 50 ¶		skipping to change at page 6, line 5 ¶
	1. RB1 acquires the unique LAGID for that MC-LAG through manual or		1. RB1 acquires the unique LAGID for that MC-LAG through manual or
	automatic provisioning.		automatic provisioning.
	2. RB1 then starts a timer (default value = 10 seconds) to allow the		2. RB1 then starts a timer (default value = 10 seconds) to allow the
	reception of LAGID TLV LSP from other RB nodes of same edge group.		reception of LAGID TLV LSP from other RB nodes of same edge group.
	This timer value MUST be same across all RBs of same edge group.		This timer value MUST be same across all RBs of same edge group.
	3. RB1 announces self LAGID in TRILL LSP to TRILL campus before		3. RB1 announces self LAGID in TRILL LSP to TRILL campus before
	local timer expires.		local timer expires.
	4. DF election process starts when the timer expires.		4. All RBs that have same LAGID provisioned as in RB1's announcement
	5. All RBs that have same LAGID provisioned as in RB1's announcement
	discover each other and form an edge group.		discover each other and form an edge group.
			5. DF election process starts when the timer expires.
	6. Each RB in an edge group elects a DF using same algorithm which		6. Each RB in an edge group elects a DF using same algorithm which
	guarantees the same RB elected as DF per MC-LAG per VLAN. The RB		guarantees the same RB elected as DF per MC-LAG per VLAN. The RB
	that is elected as a DF for a given VLAN will unblocks multi-		that is elected as a DF for a given VLAN will unblocks multi-
	destination traffic in the egress direction towards the CE. All non-		destination traffic in the egress direction towards the CE. All non-
	DF PEs continue to drop multi-destination traffic in the egress		DF PEs continue to drop multi-destination traffic in the egress
	direction towards the CE.		direction towards the CE.
	All edge RBs, including DF and non-DF, can ingress the traffic to		All edge RBs, including DF and non-DF, can ingress the traffic to
	TRILL campus as usual. On the other hand, only the elected DF		TRILL campus as usual. On the other hand, only the elected DF
	RBridge can egress the multi-destination frame from TRILL campus to		RBridge can egress the multi-destination frame from TRILL campus to
	skipping to change at page 6, line 44 ¶		skipping to change at page 6, line 46 ¶
	should be considered per FGL. If there are some specific multicast		should be considered per FGL. If there are some specific multicast
	groups receivers connecting to TRILL campus, DF election should be		groups receivers connecting to TRILL campus, DF election should be
	considered per multicast group.		considered per multicast group.
	If VLANs and multicast group addresses are statically configured on		If VLANs and multicast group addresses are statically configured on
	edge RBridge access port, the operators will ensure configuration		edge RBridge access port, the operators will ensure configuration
	consistency in an edge group. The algorithm always give consistent		consistency in an edge group. The algorithm always give consistent
	calculation result during DF election.		calculation result during DF election.
	If VLANs is dynamically enabled through VLAN registration protocol		If VLANs is dynamically enabled through VLAN registration protocol
	(VRP) (GVRP or MVRP), VLANs enabled on for each MC-LAG should be		(VRP) (GVRP or MVRP), VLANs enabled for each MC-LAG should be either
	either provisioned on all the corresponding ports on RBs of the same		provisioned on all the corresponding ports on RBs of the same edge
	edge group or synchronized among those RBs. Similarly, the		group or synchronized among those RBs. Similarly, the multicast
	multicast groups dynamically joined through IGMP or MLD protocol by		groups dynamically joined through IGMP or MLD protocol by a RBridge
	a RBridge port should follow the same logic. The detailed		port should follow the same logic. The detailed synchronization
	synchronization mechanism is beyond the scope of this draft.		mechanism is beyond the scope of this draft.
	In a steady state, all VLANs and multicast group addresses are		In a steady state, all VLANs and multicast group addresses are
	consistent among all edge RBs in an edge group. Therefore the DF		consistent among all edge RBs in an edge group. Therefore the DF
	election algorithm gives the consistency calculation result for each		election algorithm gives the consistency calculation result for each
	MC-LAG and each VLAN(or FGL/multicast group).		MC-LAG and each VLAN(or FGL/multicast group).
	5. Link and node failure process		5. Link and node failure process
	When an edge RB, say RB1, has all downlink ports in a particular MC-		When an edge RB, say RB1, has all downlink ports in a particular MC-
	LAG failed,RB1 should announce a new LSP with the rest alive LAGIDs.		LAG failed, RB1 should announce a new LSP with the remaining alive
	When other RBs in the same edge group as RB1 receive the LSP, these		LAGIDs. When other RBs in the same edge group as RB1 receive the LSP,
	RBs think RB1 has left the edge group and will trigger the DF re-		these RBs think RB1 has left the edge group and will trigger the DF
	election process.		re-election process.
	If RB1 suffers a node failure, after other RBs in the same edge		If RB1 suffers a node failure, after other RBs in the same edge
	group know this information , they will trigger the DF re-election		group know this information because RB1 becomes unreachable in the
	process.		core IS-IS link state data base (all links to RB1 will appear to be
			down), other RBs will re-run the DF election process.
	6. TRILL protocol extension		6. TRILL protocol extension
	The LAGID TLV is introduced to support global LAGID announcement. It		The LAGID TLV is introduced to support global LAGID announcement. It
	is carried in an LSP PDU. Edge RBs rely on the LAGID TLV to		is carried in an LSP PDU. Edge RBs rely on the LAGID TLV to
	automatically form edge group corresponding to each MC-LAG. DF		automatically form edge group corresponding to each MC-LAG. DF
	election of the edge group is followed by such auto-discovery.		election of the edge group is followed by such auto-discovery.
	6.1. The LAGID TLV		6.1. The LAGID TLV
	skipping to change at page 8, line 32 ¶		skipping to change at page 8, line 32 ¶
	Specification", RFC 6325, July 2011.		Specification", RFC 6325, July 2011.
	[3] [RFC6326bis] Eastlake, D., Banerjee, A., Dutt, D., Perlman,		[3] [RFC6326bis] Eastlake, D., Banerjee, A., Dutt, D., Perlman,
	R., and A. Ghanwani, "TRILL Use of IS-IS", draft-eastlake-		R., and A. Ghanwani, "TRILL Use of IS-IS", draft-eastlake-
	isis-rfc6326bis, work in progress.		isis-rfc6326bis, work in progress.
	9.2. Informative References		9.2. Informative References
	[4] [TRILL-Active-PS] Li,Y., et.al., "Problems of Active-Active		[4] [TRILL-Active-PS] Li,Y., et.al., "Problems of Active-Active
	connection at the TRILL Edge", draft-yizhou-trill-active-		connection at the TRILL Edge", draft-yizhou-trill-active-
	active-connection-prob-00, Work in progress, July		active-connection-prob-02, Work in progress, July
	2013.		2014.
	10. Acknowledgments		10. Acknowledgments
	The authors wish to acknowledge the important contributions of		The authors wish to acknowledge the important contributions of
	Junlin Zhang.		Donald Eastlake, Junlin Zhang.
	Authors' Addresses		Authors' Addresses
	Weiguo Hao		Weiguo Hao
	Huawei Technologies		Huawei Technologies
	101 Software Avenue,		101 Software Avenue,
	Nanjing 210012		Nanjing 210012
	China		China
	Phone: +86-25-56623144		Phone: +86-25-56623144
End of changes. 13 change blocks.
	25 lines changed or deleted		26 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/