< draft-fulignoli-mpls-tp-bfd-cv-proactive-and-rdi-00.txt		draft-fulignoli-mpls-tp-bfd-cv-proactive-and-rdi-01.txt >
	MPLS Working Group A. Fulignoli (Ed)
			MPLS Working Group A. Fulignoli (Ed.)
	Internet Draft Ericsson		Internet Draft Ericsson
	Intended status: Informational		Intended status: Informational
			S. Boutros (Ed.)
			Cisco Systems, Inc
	Expires: January 2010 July 2, 2009		M.Vigoureux (Ed.)
			Alcatel-Lucent
			Expires: January 2010 July 7, 2009
	MPLS-TP BFD for Proactive CC-CV and RDI		MPLS-TP BFD for Proactive CC-CV and RDI
	draft-fulignoli-mpls-tp-bfd-cv-proactive-and-rdi-00.txt		draft-fulignoli-mpls-tp-bfd-cv-proactive-and-rdi-01.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance		This Internet-Draft is submitted to IETF in full conformance
	with the provisions of BCP 78 and BCP 79.		with the provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet		Internet-Drafts are working documents of the Internet
	Engineering Task Force (IETF), its areas, and its working		Engineering Task Force (IETF), its areas, and its working
	groups. Note that other groups may also distribute working		groups. Note that other groups may also distribute working
	documents as Internet-Drafts.		documents as Internet-Drafts.
	skipping to change at page 2, line 27 ¶		skipping to change at page 2, line 29 ¶
	This document specifies the BFD extension and behaviour to meet		This document specifies the BFD extension and behaviour to meet
	the requirements for MPLS-TP proactive Continuity Check and		the requirements for MPLS-TP proactive Continuity Check and
	Connectivity Verification functionality and the RDI		Connectivity Verification functionality and the RDI
	functionality as defined in [3].		functionality as defined in [3].
	Table of Contents		Table of Contents
	1. Introduction...................................................3		1. Introduction...................................................3
	1.1. Terminology..................................................4		1.1. Terminology..................................................4
	2. Trail Termination Source Identifier (TTSI) TLV Object..........4		2. Trail Termination Source Identifier (TTSI) TLV Object..........4
	2.1. Unique ME Identifier.........................................5		2.1. Unique ME Identifier.........................................6
	2.1.1. LSP ME ID IPv4 Source/Destination Address Format...........6		2.1.1. LSP ME ID IPv4 Source/Destination Address Format...........7
	2.1.2. LSP ME ID IPv6 Source/Destination Address Format...........8		2.1.2. LSP ME ID IPv6 Source/Destination Address Format...........8
	2.1.3. Type FEC128PWv4 Format.....................................9		2.1.3. Type FEC128PWv4 Format.....................................9
	2.1.4. Type FEC128PWv6 Format.....................................9		2.1.4. Type FEC128PWv6 Format.....................................9
	2.1.5. ICC-based Format...........................................9		2.1.5. ICC-based Format...........................................9
	3. Two different ACH encapsulation of BFD tool...................10		3. Two different ACH encapsulation of BFD tool...................11
	3.1. Current BFD with only CC functionality......................11		3.1. Current BFD with only CC functionality......................11
	3.2. New tool based on current BFD...............................12		3.2. New tool based on current BFD...............................12
	4. Backward compatibility........................................13		4. Backward compatibility........................................13
	5. BFD behavior specification for MPLS-TP OAM proactive CC&CV....13		5. BFD behavior specification for MPLS-TP OAM proactive CC&CV....13
	5.1. BFD State Machine...........................................14		5.1. BFD State Machine...........................................14
	5.2. Defect conditions...........................................18		5.2. Defect conditions...........................................18
	5.2.1. Loss of Continuity defect(dLOC)...........................18		5.2.1. Loss of Continuity defect(dLOC)...........................18
	5.2.2. Mis-connectivity defect (dUNME)...........................18		5.2.2. Mis-connectivity defect (dUNME)...........................18
	5.2.3. Unexpected MEP ID defect (dUNM)...........................18		5.2.3. Unexpected MEP ID defect (dUNM)...........................18
	5.2.4. Unexpected Period Defect (dUNP)...........................18		5.2.4. Unexpected Period Defect (dUNP)...........................18
	skipping to change at page 19, line 29 ¶		skipping to change at page 19, line 29 ¶
	|dUNME |Unexpected ME Identifier |#UnexpMEId==0 (K*CV_Period) |		|dUNME |Unexpected ME Identifier |#UnexpMEId==0 (K*CV_Period) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|dUNM |Unexpected MEP Id |#UnexpMEPId==0 (K*CV_Period) |		|dUNM |Unexpected MEP Id |#UnexpMEPId==0 (K*CV_Period) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|dUNP |Unexpected Period |#UnexpPeriod==0 (K*CV_Period)|		|dUNP |Unexpected Period |#UnexpPeriod==0 (K*CV_Period)|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|dRDI | Rx RDI == 1 | Rx RDI ==0 |		|dRDI | Rx RDI == 1 | Rx RDI ==0 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Table 1: Table of Raising Clearing Defect Conditions		Table 1: Table of Raising Clearing Defect Conditions
	In Table 1, N and K are protocol constants to be defined;		In Table 1, N and K are protocol constants to be defined; the
	the CV_Period corresponds to the configured transmission period;		CV_Period corresponds to the configured transmission period;
	K value is stored in bfd.DetectMult variable while the CV_Period		K value is stored in bfd.DetectMult variable while the CV_Period
	is stored bfd.DesiredMinTxInterval variable and carried in the		is stored bfd.DesiredMinTxInterval variable and carried in the
	relative BFD packet fields.		relative BFD packet fields.
	5.3. Consequent action		5.3. Consequent action
	. If a MEP detects an unexpected ME Identifier, or an unexpected		. If a MEP detects an unexpected ME Identifier, or an unexpected
	MEP, it MUST block (BLK) all the traffic (including also the		MEP, it MUST block (BLK) all the traffic (including also the
	user data packets) that it receives from the misconnected		user data packets) that it receives from the misconnected
	skipping to change at page 29, line 34 ¶		skipping to change at page 29, line 34 ¶
	bfd-04.txt, Work in Progress, May 2009		bfd-04.txt, Work in Progress, May 2009
	[8] Katz, D. and D. Ward, "Bidirectional Forwarding		[8] Katz, D. and D. Ward, "Bidirectional Forwarding
	Detection", draft-ietf-bfd-base-09.txt (work in progress),		Detection", draft-ietf-bfd-base-09.txt (work in progress),
	February 2009.		February 2009.
	[9] Katz, D. and D. Ward, "BFD for Multipoint Networks",		[9] Katz, D. and D. Ward, "BFD for Multipoint Networks",
	ID draft-katz-ward-bfd-multipoint-02.txt, February 2009		ID draft-katz-ward-bfd-multipoint-02.txt, February 2009
	[10] S. Boutros, et. al., "Definition of ACH TLV Structure",		[10] S. Boutros, et. al., "Definition of ACH TLV Structure",
	draft- bryant-mpls-tp-ach-tlv-00.txt, Work in		draft-bryant-mpls-tp-ach-tlv-00.txt, Work in
	Progress, January 2009.		Progress, January 2009.
	[11] A. Fulignoli, et. al.,''MPLS-TP Proactive Continuity and		[11] A. Fulignoli, et. al.,''MPLS-TP Proactive Continuity and
	Connectivity Verification'', draft-fhbs-mpls-tp-cv-		Connectivity Verification'', draft-fhbs-mpls-tp-cv-
	proactive-00.txt (work in progress), February 2009		proactive-00.txt (work in progress), February 2009
	[12] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,		[12] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
	"BFD For MPLS LSPs", draft-ietf-bfd-mpls-07 (work		"BFD For MPLS LSPs", draft-ietf-bfd-mpls-07 (work
	in progress), June 2008.		in progress), June 2008.
	[13] Martini, L.and M.Morrow, ''Pseudo Wire (PW) OAM Message		[13] Martini, L.and M.Morrow, ''Pseudo Wire (PW) OAM Message
	Mapping'', draft-eitd-pwe3-oam-msg-map-10 (work in		Mapping'', draft-eitd-pwe3-oam-msg-map-10 (work in
	progress), April 2009		progress), April 2009
	14.2. Informative References		14.2. Informative References
	Authors' Addresses		Authors' Addresses
	skipping to change at page 30, line 10 ¶		skipping to change at page 30, line 10 ¶
	[13] Martini, L.and M.Morrow, ''Pseudo Wire (PW) OAM Message		[13] Martini, L.and M.Morrow, ''Pseudo Wire (PW) OAM Message
	Mapping'', draft-eitd-pwe3-oam-msg-map-10 (work in		Mapping'', draft-eitd-pwe3-oam-msg-map-10 (work in
	progress), April 2009		progress), April 2009
	14.2. Informative References		14.2. Informative References
	Authors' Addresses		Authors' Addresses
	Annamaria Fulignoli (Editor)		Annamaria Fulignoli (Editor)
	Ericsson		Ericsson
	Email: annamaria.fulignoli@ericsson.com		Email: annamaria.fulignoli@ericsson.com
			Sami Boutros
			Cisco Systems, Inc.
			Email: sboutros@cisco.com
			Martin Vigoureux
			Alcatel-Lucent
			Email: martin.vigoureux@alcatel-lucent.com
End of changes. 12 change blocks.
	12 lines changed or deleted		16 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/