< draft-jc-pwe3-static-config-check-00.txt		draft-jc-pwe3-static-config-check-01.txt >
	Network Working Group L. Jin		Network Working Group L. Jin
	Internet-Draft R. Chen		Internet-Draft R. Chen
	Intended status: Standards Track ZTE		Intended status: Standards Track ZTE
	Expires: January 7, 2013 S. Boutros		Expires: April 12, 2013 S. Boutros
	Cisco Systems		Cisco Systems
	S. Kini		S. Kini
	Ericsson		Ericsson
	July 6, 2012		October 9, 2012
	Static pseudowire configuration checking using Generic Associated		Static pseudowire configuration checking using Generic Associated
	Channel (G-ACh) Advertisement Protocol		Channel (G-ACh) Advertisement Protocol
	draft-jc-pwe3-static-config-check-00.txt		draft-jc-pwe3-static-config-check-01.txt
	Abstract		Abstract
	This draft defines a method to verify the configuration parameters of		This document defines a method to verify the configuration parameters
	static pseudowires (PW). Since a static PW can be independently		of static pseudowires (PW). Since a static PW can be independently
	provisioned at each end of the PW there is a potential for a		provisioned at each end of the PW there is a potential for a
	configuration parameter mismatch and this can result in the PW not		configuration parameter mismatch and this can result in the PW not
	being operational. The procedures in this draft intend to solve this		being operational. This document introduces a configuration checking
	problem and simplify the provisioning.		protocol to simplify the provisioning and ease trouble shooting.
	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.
	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 January 7, 2013.		This Internet-Draft will expire on April 12, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 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 17 ¶		skipping to change at page 2, line 17 ¶
	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 . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. GAP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 4		3. GAP Extensions . . . . . . . . . . . . . . . . . . . . . . . . 4
	3.1. Static PW Application Message . . . . . . . . . . . . . . 4		3.1. Static PW Application Message . . . . . . . . . . . . . . 4
	3.2. PE Procedure . . . . . . . . . . . . . . . . . . . . . . . 7		3.2. PE Procedure for SS-PW . . . . . . . . . . . . . . . . . . 7
	3.2.1. Sending PW application Element TLV . . . . . . . . . . 7		3.2.1. Sending PW application Element TLV . . . . . . . . . . 7
	3.2.2. Receiving PW application Element TLV . . . . . . . . . 7		3.2.2. Receiving PW application Element TLV . . . . . . . . . 7
	3.2.3. PW Configuration Verification Process . . . . . . . . 8		3.2.3. PW Configuration Verification Process . . . . . . . . 8
	3.2.4. Remote Label Advertisement . . . . . . . . . . . . . . 8		3.2.4. Remote Label Advertisement . . . . . . . . . . . . . . 8
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 8		3.3. PE Procedure for MS-PW . . . . . . . . . . . . . . . . . . 8
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8		4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
			5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9		6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9		7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	7.1. Normative references . . . . . . . . . . . . . . . . . . . 9		7.1. Normative references . . . . . . . . . . . . . . . . . . . 9
	7.2. Informative References . . . . . . . . . . . . . . . . . . 9		7.2. Informative References . . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	The manual configuration of static PW in MPLS and MPLS-TP network		The manual configuration of static PW in MPLS and MPLS-TP network
	requires configuring different PW parameters at the two terminating		requires configuring different PW parameters at the two terminating
	PEs (Provider Edge). The PW parameters include PW-id, PW-Type,		PEs (Provider Edge). The PW parameters include PW-id, PW-Type,
	Control word setting, interface and VCCV parameters settings.		Control word setting, interface and VCCV parameters settings.
	The PW provisioned parameters MUST be aligned, so as to make the PW		The PW provisioned parameters MUST be aligned, so as to make the PW
	skipping to change at page 3, line 47 ¶		skipping to change at page 3, line 47 ¶
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	This document uses some terms and acronyms as follows:		This document uses some terms and acronyms as follows:
	MPLS: Multi Protocol Label Switching.		MPLS: Multi Protocol Label Switching.
	OAM: MPLS Operations, Administration and Maintenance.		OAM: MPLS Operations, Administration and Maintenance.
	PE: Provide Edge Node.		PE: Provide Edge Node.
			T-PE: PW Terminating Provider Edge.
			S-PE: PW Switching Provider Edge.
	PW: PseudoWire.		PW: PseudoWire.
	TLV: Type, Length, and Value.		TLV: Type, Length, and Value.
	VPLS: Virtual Private LAN Services.		SS-PW: Single-segment PseudoWire
	MS-PW: Multi-segment PseudoWire		MS-PW: Multi-segment PseudoWire
	3. GAP Extensions		3. GAP Extensions
	3.1. Static PW Application Message		3.1. Static PW Application Message
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 7, line 5 ¶		skipping to change at page 7, line 5 ¶
	The type of static PW suppress TLV is to be assigned by IANA.		The type of static PW suppress TLV is to be assigned by IANA.
	The static PW suppress TLV could be sent by a receiving PE to request		The static PW suppress TLV could be sent by a receiving PE to request
	a transmitting PE to stop sending GAP messages for the static PW FEC		a transmitting PE to stop sending GAP messages for the static PW FEC
	Element TLVs in the static PW suppress TLV.		Element TLVs in the static PW suppress TLV.
	The static PW application MUST follow all procedures defined in		The static PW application MUST follow all procedures defined in
	[I-D.ietf-mpls-gach-adv].		[I-D.ietf-mpls-gach-adv].
	3.2. PE Procedure		3.2. PE Procedure for SS-PW
	The mechanism defined in this draft provides a verification tool for		The mechanism defined in this draft provides a verification tool for
	the P2P PW configuration information between two PEs. Upon the		the P2P PW configuration information between two PEs. Upon the
	provisioning or re-provisioning of a PW at an endpoint PE, GAP		provisioning or re-provisioning of a PW at an endpoint PE, GAP
	messages carrying the static PW application TLV will be sent over the		messages carrying the static PW application TLV will be sent over the
	PW's corresponding PSN tunnel which the endpoints PEs of the P2P PW		PW's corresponding PSN tunnel which the endpoints PEs of the P2P PW
	selects by local policy.		selects by local policy.
	3.2.1. Sending PW application Element TLV		3.2.1. Sending PW application Element TLV
	skipping to change at page 8, line 42 ¶		skipping to change at page 8, line 42 ¶
	otherwise checking failed.		otherwise checking failed.
	3.2.4. Remote Label Advertisement		3.2.4. Remote Label Advertisement
	The mechanism described in this draft MAY also be used to communicate		The mechanism described in this draft MAY also be used to communicate
	local static PW labels to allow for single side provisioning of		local static PW labels to allow for single side provisioning of
	labels. As such, only incoming label will be included in the GAP		labels. As such, only incoming label will be included in the GAP
	message and this label will be used by the remote PE as the output		message and this label will be used by the remote PE as the output
	label for the PW.		label for the PW.
			3.3. PE Procedure for MS-PW
			The mechanism described above for verifying the SS-PW configuration
			applies for MS-PW. As described in section 3.2, an S-PE MUST verify
			the incoming and outgoing static PW labels, however no other PW
			configuration parameters checking are needed at S-PE, since only the
			labels will be configured at S-PE.
			An S-PE MUST pass through static PW application TLVs carried in GAP
			messages, from one PW segment's corresponding PSN tunnel to the other
			PW segment's corresponding PSN tunnel.
	4. Security Considerations		4. Security Considerations
	The mechanisms defined in this draft do not introduce any new threats		The mechanisms defined in this draft do not introduce any new threats
	more than what's described in [I-D.ietf-mpls-gach-adv].		more than what's described in [I-D.ietf-mpls-gach-adv].
	5. IANA Considerations		5. IANA Considerations
	IANA is requested to allocate a new "Static PW" Application ID in the		IANA is requested to allocate a new "Static PW" Application ID in the
	"G-Ach Advertisement Protocol Applications" registry.		"G-Ach Advertisement Protocol Applications" registry.
End of changes. 13 change blocks.
	14 lines changed or deleted		31 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/