draft-ietf-ccamp-mpls-tp-cp-framework-04.txt		draft-ietf-ccamp-mpls-tp-cp-framework-05.txt
	Internet Draft Loa Andersson, Ed. (Ericsson)		Internet Draft Loa Andersson, Ed. (Ericsson)
	Category: Informational Lou Berger, Ed. (LabN)		Category: Informational Lou Berger, Ed. (LabN)
	Expiration Date: May 19, 2011 Luyuan Fang, Ed. (Cisco)		Expiration Date: July 7, 2011 Luyuan Fang, Ed. (Cisco)
	Nabil Bitar, Ed. (Verizon)		Nabil Bitar, Ed. (Verizon)
	Eric Gray, Ed. (Ericsson)		Eric Gray, Ed. (Ericsson)
	November 19, 2010		January 7, 2011
	MPLS-TP Control Plane Framework		MPLS-TP Control Plane Framework
	draft-ietf-ccamp-mpls-tp-cp-framework-04.txt		draft-ietf-ccamp-mpls-tp-cp-framework-05.txt
	Abstract		Abstract
	The MPLS Transport Profile (MPLS-TP) supports static provisioning		The MPLS Transport Profile (MPLS-TP) supports static provisioning
	of transport paths via a Network Management System (NMS), and		of transport paths via a Network Management System (NMS), and
	dynamic provisioning of transport paths via a control plane. This		dynamic provisioning of transport paths via a control plane. This
	document provides the framework for MPLS-TP dynamic provisioning,		document provides the framework for MPLS-TP dynamic provisioning,
	and covers control plane addressing, routing, path computation,		and covers control plane addressing, routing, path computation,
	signaling, traffic engineering, and path recovery. MPLS-TP uses		signaling, traffic engineering, and path recovery. MPLS-TP uses
	GMPLS as the control plane for MPLS-TP LSPs. MPLS-TP also uses		GMPLS as the control plane for MPLS-TP LSPs. MPLS-TP also uses
	the control plane for Pseudowires (PWs). Management plane		the Pseudowire (PW) control plane for Pseudowires (PWs).
	functions are out of scope of this document.		Management plane functions are out of scope of this document.
	This document is a product of a joint Internet Engineering Task Force		This document is a product of a joint Internet Engineering Task Force
	(IETF) / International Telecommunication Union Telecommunication		(IETF) / International Telecommunication Union Telecommunication
	Standardization Sector (ITU-T) effort to include an MPLS Transport		Standardization Sector (ITU-T) effort to include an MPLS Transport
	Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge		Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
	(PWE3) architectures to support the capabilities and functionalities		(PWE3) architectures to support the capabilities and functionalities
	of a packet transport network as defined by the ITU-T.		of a packet transport network as defined by the ITU-T.
	This Informational Internet-Draft is aimed at achieving IETF		This Informational Internet-Draft is aimed at achieving IETF
	Consensus before publication as an RFC and will be subject to an IETF		Consensus before publication as an RFC and will be subject to an IETF
	skipping to change at page 2, line 13		skipping to change at page 2, line 13
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/1id-abstracts.html		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 May 19, 2011		This Internet-Draft will expire on July 7, 2011
	Copyright and License Notice		Copyright and License Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2011 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 respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	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
	skipping to change at page 2, line 51		skipping to change at page 2, line 51
	2.5 Identifier Requirements ................................ 24		2.5 Identifier Requirements ................................ 24
	3 Relationship of PWs and TE LSPs ........................ 25		3 Relationship of PWs and TE LSPs ........................ 25
	4 TE LSPs ................................................ 26		4 TE LSPs ................................................ 26
	4.1 GMPLS Functions and MPLS-TP LSPs ....................... 26		4.1 GMPLS Functions and MPLS-TP LSPs ....................... 26
	4.1.1 In-Band and Out-Of-Band Control ........................ 26		4.1.1 In-Band and Out-Of-Band Control ........................ 26
	4.1.2 Addressing ............................................. 28		4.1.2 Addressing ............................................. 28
	4.1.3 Routing ................................................ 28		4.1.3 Routing ................................................ 28
	4.1.4 TE LSPs and Constraint-Based Path Computation .......... 28		4.1.4 TE LSPs and Constraint-Based Path Computation .......... 28
	4.1.5 Signaling .............................................. 29		4.1.5 Signaling .............................................. 29
	4.1.6 Unnumbered Links ....................................... 29		4.1.6 Unnumbered Links ....................................... 29
	4.1.7 Link Bundling .......................................... 29		4.1.7 Link Bundling .......................................... 30
	4.1.8 Hierarchical LSPs ...................................... 30		4.1.8 Hierarchical LSPs ...................................... 30
	4.1.9 LSP Recovery ........................................... 30		4.1.9 LSP Recovery ........................................... 31
	4.1.10 Control Plane Reference Points (E-NNI, I-NNI, UNI) ..... 31		4.1.10 Control Plane Reference Points (E-NNI, I-NNI, UNI) ..... 31
	4.2 OAM, MEP (Hierarchy), MIP Configuration and Control .... 31		4.2 OAM, MEP (Hierarchy), MIP Configuration and Control .... 31
	4.2.1 Management Plane Support ............................... 32		4.2.1 Management Plane Support ............................... 32
	4.3 GMPLS and MPLS-TP Requirements Table ................... 33		4.3 GMPLS and MPLS-TP Requirements Table ................... 33
	4.4 Anticipated MPLS-TP Related Extensions and Definitions . 36		4.4 Anticipated MPLS-TP Related Extensions and Definitions . 36
	4.4.1 MPLS-TE to MPLS-TP LSP Control Plane Interworking ...... 36		4.4.1 MPLS-TE to MPLS-TP LSP Control Plane Interworking ...... 36
	4.4.2 Associated Bidirectional LSPs .......................... 36		4.4.2 Associated Bidirectional LSPs .......................... 36
	4.4.3 Asymmetric Bandwidth LSPs .............................. 37		4.4.3 Asymmetric Bandwidth LSPs .............................. 37
	4.4.4 Recovery for P2MP LSPs ................................. 37		4.4.4 Recovery for P2MP LSPs ................................. 37
	4.4.5 Test Traffic Control and other OAM functions ........... 37		4.4.5 Test Traffic Control and other OAM functions ........... 37
	4.4.6 DiffServ Object usage in GMPLS ......................... 37		4.4.6 DiffServ Object usage in GMPLS ......................... 38
	4.4.7 Support for MPLS-TP LSP Identifiers .................... 38		4.4.7 Support for MPLS-TP LSP Identifiers .................... 38
	4.4.8 Support for MPLS-TP Maintenance Identifiers ............ 38		4.4.8 Support for MPLS-TP Maintenance Identifiers ............ 38
	5 Pseudowires ............................................ 38		5 Pseudowires ............................................ 38
	5.1 LDP Functions and Pseudowires .......................... 38		5.1 LDP Functions and Pseudowires .......................... 38
	5.2 PW Control (LDP) and MPLS-TP Requirements Table ........ 39		5.2 PW Control (LDP) and MPLS-TP Requirements Table ........ 39
	5.3 Anticipated MPLS-TP Related Extensions ................. 41		5.3 Anticipated MPLS-TP Related Extensions ................. 41
	5.3.1 Extensions to Support Out-of-Band PW Control ........... 42		5.3.1 Extensions to Support Out-of-Band PW Control ........... 42
	5.3.2 Support for Explicit Control of PW-to-LSP Binding ...... 42		5.3.2 Support for Explicit Control of PW-to-LSP Binding ...... 42
	5.3.3 Support for Dynamic Transfer of PW Control/Ownership ... 43		5.3.3 Support for Dynamic Transfer of PW Control/Ownership ... 43
	5.3.4 Interoperable Support for PW/LSP Resource Allocation ... 43		5.3.4 Interoperable Support for PW/LSP Resource Allocation ... 43
	5.3.5 Support for PW Protection and PW OAM Configuration ..... 44		5.3.5 Support for PW Protection and PW OAM Configuration ..... 44
	5.3.6 Client Layer and Cross-Provider Interfaces to PW Control ...45		5.3.6 Client Layer and Cross-Provider Interfaces to PW Control.. 45
	5.4 ASON Architecture Considerations ....................... 45		5.4 ASON Architecture Considerations ....................... 45
	6 Security Considerations ................................ 45		6 Security Considerations ................................ 45
	7 IANA Considerations .................................... 46		7 IANA Considerations .................................... 46
	8 Acknowledgments ........................................ 46		8 Acknowledgments ........................................ 46
	9 References ............................................. 46		9 References ............................................. 46
	9.1 Normative References ................................... 46		9.1 Normative References ................................... 46
	9.2 Informative References ................................. 49		9.2 Informative References ................................. 49
	10 Authors' Addresses ..................................... 54		10 Authors' Addresses ..................................... 54
	1. Introduction		1. Introduction
	skipping to change at page 6, line 31		skipping to change at page 6, line 31
	via both PWs and LSPs. PW client interfaces, or adaptations, are		via both PWs and LSPs. PW client interfaces, or adaptations, are
	defined on an interface technology basis, e.g., Ethernet over PW		defined on an interface technology basis, e.g., Ethernet over PW
	[RFC4448]. In the context of MPLS-TP LSP, the client interface is		[RFC4448]. In the context of MPLS-TP LSP, the client interface is
	provided at the network layer and may be controlled via a GMPLS based		provided at the network layer and may be controlled via a GMPLS based
	UNI, see [RFC4208], or statically provisioned. As discussed in		UNI, see [RFC4208], or statically provisioned. As discussed in
	[RFC5921], MPLS-TP also presumes an LSP NNI reference point.		[RFC5921], MPLS-TP also presumes an LSP NNI reference point.
	The MPLS-TP end-to-end control plane reference model is shown in		The MPLS-TP end-to-end control plane reference model is shown in
	Figure 1. The Figure shows the control plane protocols used by MPLS-		Figure 1. The Figure shows the control plane protocols used by MPLS-
	TP, as well as the UNI and NNI reference points, in the case of a		TP, as well as the UNI and NNI reference points, in the case of a
	single segment PW. (The MS-PW case is not shown.)		single segment PW supported by an end-to-end LSP without any
			hierarchical LSPs. (The MS-PW case is not shown.) Each service
			provider node's participation in routing and signaling (both GMPLS
			RSVP-TE and PW LDP) is represented. Note that only the service end
			points participate in PW LDP signaling, while all service provider
			nodes participate in GMPLS TE LSP routing and signaling.
	|< ---- client signal (e.g., IP / MPLS / L2) -------- >|		|< ---- client signal (e.g., IP / MPLS / L2) -------- >|
	|< --------- SP1 ---------- >|< ------- SP2 ----- >|		|< --------- SP1 ---------- >|< ------- SP2 ----- >|
	|< ---------- MPLS-TP End-to-End PW --------- >|		|< ---------- MPLS-TP End-to-End PW --------- >|
	|< -------- MPLS-TP End-to-End LSP ------ >|		|< -------- MPLS-TP End-to-End LSP ------ >|
	+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+		+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
	|CE1|-|-|PE1|--|P1 |--|P2 |--|PE2|-|-|PEa|--|Pa |--|PEb|-|-|CE2|		|CE1|-|-|PE1|--|P1 |--|P2 |--|PE2|-|-|PEa|--|Pa |--|PEb|-|-|CE2|
	+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+		+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
	UNI NNI UNI		UNI NNI UNI
			GMPLS
			TE-RTG, |<-----|------|------|-------|------|----->|
			& RSVP-TE
	TE-RTG, |< ---------------- >|< --- >|< ---------- >|		PW LDP |< ---------------------------------------- >|
	& RSVP-TE
	LDP |< --------------------------------------- >|
	Figure 1. End-to-End MPLS-TP Control Plane Reference Model		Figure 1. End-to-End MPLS-TP Control Plane Reference Model
	Legend:		Legend:
	CE: Customer Edge		CE: Customer Edge
	Client signal: defined in MPLS-TP Requirements		Client signal: defined in MPLS-TP Requirements
	L2: Any layer 2 signal that may be carried		L2: Any layer 2 signal that may be carried
	over a PW, e.g. Ethernet.		over a PW, e.g. Ethernet.
	NNI: Network to Network Interface		NNI: Network to Network Interface
	PE: Provider Edge		PE: Provider Edge
	SP: Service Provider		SP: Service Provider
	TE-RTG: OSPF-TE or ISIS-TE		TE-RTG: GMPLS OSPF-TE or ISIS-TE
	UNI: User to Network Interface		UNI: User to Network Interface
			Note: The MS-PW case is not shown.
	Figure 2 adds three hierarchical LSP segments, labeled as "H-LSPs".		Figure 2 adds three hierarchical LSP segments, labeled as "H-LSPs".
	These segments are present to support scaling, OAM and Maintenance		These segments are present to support scaling, OAM and Maintenance
	End Points (MEPs), see [TP-OAM], within each provider domain and		End Points (MEPs), see [TP-OAM], within each provider domain and
	across the inter-provider NNI. The MEPs are used to collect		across the inter-provider NNI. (H-LSPs are used to implement Sub-
	performance information, support diagnostic and fault management		Path Maintenance Elements (SPMEs) as defined in [RFC5921].) The MEPs
	functions, and support OAM triggered survivability schemes as		are used to collect performance information, support diagnostic and
	discussed in [TP-SURVIVE]. Each H-LSP may be protected or restored		fault management functions, and support OAM triggered survivability
	using any of the schemes discussed in [TP-SURVIVE]. End-to-end		schemes as discussed in [TP-SURVIVE]. Each H-LSP may be protected or
	monitoring is supported via MEPs at the End-to-End LSP and PW end		restored using any of the schemes discussed in [TP-SURVIVE]. End-to-
			end monitoring is supported via MEPs at the End-to-End LSP and PW end
	points. Note that segment MEPs may be collocated with MIPs of the		points. Note that segment MEPs may be collocated with MIPs of the
	next higher-layer (e.g., end-to-end) LSPs. H-LSPs may also be used		next higher-layer (e.g., end-to-end) LSPs. (The MS-PW case is not
	to implement Sub-Path Maintenance Elements (SPMEs) as defined in		shown.)
	[RFC5921]. (The MS-PW case is not shown.)
	|< ------- client signal (e.g., IP / MPLS / L2) ----- >|		|< ------- client signal (e.g., IP / MPLS / L2) ----- >|
	|< -------- SP1 ----------- >|< ------- SP2 ----- >|		|< -------- SP1 ----------- >|< ------- SP2 ----- >|
	|< ----------- MPLS-TP End-to-End PW -------- >|		|< ----------- MPLS-TP End-to-End PW -------- >|
	|< ------- MPLS-TP End-to-End LSP ------- >|		|< ------- MPLS-TP End-to-End LSP ------- >|
	|< -- H-LSP1 ---- >|<-H-LSP2->|<- H-LSP3 ->|		|< -- H-LSP1 ---- >|<-H-LSP2->|<- H-LSP3 ->|
	+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+		+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
	|CE1|-|-|PE1|--|P1 |--|P2 |--|PE2|-|-|PEa|--|Pa |--|PEb|-|-|CE2|		|CE1|-|-|PE1|--|P1 |--|P2 |--|PE2|-|-|PEa|--|Pa |--|PEb|-|-|CE2|
	+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+		+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
	UNI NNI UNI		UNI NNI UNI
			..... .....
			End2end |MEP|--------------------------------------|MEP|
			PW OAM ''''' '''''
	..... ..... ..... .....		..... ..... ..... .....
	End2end |MEP|----------------|MIP|---|MIP|---------|MEP|		End2end |MEP|----------------|MIP|---|MIP|---------|MEP|
	PW OAM ''''' ''''' ''''' '''''		LSP OAM ''''' ''''' ''''' '''''
	..... ..... ..... ......... ......... ..... .....		..... ..... ..... ......... ......... ..... .....
	Segment |MEP|-|MIP|-|MIP|-|MEP|MEP|-|MEP|MEP|-|MIP|-|MEP|		Segment |MEP|-|MIP|-|MIP|-|MEP|MEP|-|MEP|MEP|-|MIP|-|MEP|
	OAM ''''' ''''' ''''' ''''''''' ''''''''' ''''' '''''		LSP OAM ''''' ''''' ''''' ''''''''' ''''''''' ''''' '''''
	Seg.TE-RTG|< -- >|< -- >|< -- >||< -- >||< -- >|< -- >|		H-LSP GMPLS
	&RSVP-TE (within an MPLS-TP network)		TE-RTG |<-----|------|----->||<---->||<-----|----->|
			&RSVP-TE (within an MPLS-TP network)
	E2E TE-RTG|< ---------------- >|< ---- >|< --------- >|		E2E GMPLS
	&RSVP-TE		TE-RTG |< ------------------|--------|------------>|
			&RSVP-TE
	LDP |< --------------------------------------- >|		PW LDP |< ---------------------------------------- >|
	Figure 2. MPLS-TP Control Plane Reference Model with OAM		Figure 2. MPLS-TP Control Plane Reference Model with OAM
	Legend:		Legend:
	CE: Customer Edge		CE: Customer Edge
	Client signal: defined in MPLS-TP Requirements		Client signal: defined in MPLS-TP Requirements
	E2E: End-to-end		E2E: End-to-end
	L2: Any layer 2 signal that may be carried		L2: Any layer 2 signal that may be carried
	over a PW, e.g. Ethernet.		over a PW, e.g. Ethernet.
	H-LSP: Hierarchical LSP		H-LSP: Hierarchical LSP
	MEP: Maintenance end point		MEP: Maintenance end point
	MIP: Maintenance intermediate point		MIP: Maintenance intermediate point
	NNI: Network to Network Interface		NNI: Network to Network Interface
	PE: Provider Edge		PE: Provider Edge
	SP: Service Provider		SP: Service Provider
	TE-RTG: OSPF-TE or ISIS-TE		TE-RTG: GMPLS OSPF-TE or ISIS-TE
			Note: The MS-PW case is not shown.
	While not shown in the Figures above, the MPLS-TP control plane must		While not shown in the Figures above, the MPLS-TP control plane must
	support the addressing separation and independence between the data,		support the addressing separation and independence between the data,
	control and management planes. Address separation between the planes		control and management planes. Address separation between the planes
	is already included in GMPLS. Such separation is also already		is already included in GMPLS. Such separation is also already
	included in LDP as LDP session end point addresses are never		included in LDP as LDP session end point addresses are never
	automatically associated with forwarding.		automatically associated with forwarding.
	2. Control Plane Requirements		2. Control Plane Requirements
	skipping to change at page 13, line 9		skipping to change at page 13, line 17
	Automatically Switched Optical Networks (ASON) in G.8080		Automatically Switched Optical Networks (ASON) in G.8080
	[ITU.G8080.2006] and G.8080 Amendment 1 [ITU.G8080.2008]. An		[ITU.G8080.2006] and G.8080 Amendment 1 [ITU.G8080.2008]. An
	interpretation of the ASON signaling and routing requirements		interpretation of the ASON signaling and routing requirements
	in the context of GMPLS can be found in [RFC4139] and [RFC4258]		in the context of GMPLS can be found in [RFC4139] and [RFC4258]
	[RFC5654, Section 2.4., Paragraph 2 and 3].		[RFC5654, Section 2.4., Paragraph 2 and 3].
	40. The MPLS-TP control plane must support control plane topology		40. The MPLS-TP control plane must support control plane topology
	and data plane topology independence [RFC5654, requirement 47].		and data plane topology independence [RFC5654, requirement 47].
	41. A failure of the MPLS-TP control plane must not interfere with		41. A failure of the MPLS-TP control plane must not interfere with
	the deliver of service or recovery of established transport		the delivery of service or recovery of established transport
	paths [RFC5654, requirement 47].		paths [RFC5654, requirement 47].
	42. The MPLS-TP control plane must be able to operate independent		42. The MPLS-TP control plane must be able to operate independent
	of any particular client or server layer control plane		of any particular client or server layer control plane
	[RFC5654, requirement 48].		[RFC5654, requirement 48].
	43. The MPLS-TP control plane should support, but not require, an		43. The MPLS-TP control plane should support, but not require, an
	integrated control plane encompassing MPLS-TP together with its		integrated control plane encompassing MPLS-TP together with its
	server and client layer networks when these layer networks		server and client layer networks when these layer networks
	belong to the same administrative domain [RFC5654, requirement		belong to the same administrative domain [RFC5654, requirement
	skipping to change at page 24, line 43		skipping to change at page 24, line 50
	137. The MPLS-TP control plane must support MPLS-TP point to point		137. The MPLS-TP control plane must support MPLS-TP point to point
	tunnel identifiers of the forms defined in [TP-IDENTIFIERS,		tunnel identifiers of the forms defined in [TP-IDENTIFIERS,
	Section 5.1].		Section 5.1].
	138. The MPLS-TP control plane must support MPLS-TP LSP identifiers		138. The MPLS-TP control plane must support MPLS-TP LSP identifiers
	of the forms defined in [TP-IDENTIFIERS, Section 5.2], and the		of the forms defined in [TP-IDENTIFIERS, Section 5.2], and the
	mappings to GMPLS as defined in [TP-IDENTIFIERS, Section 5.3].		mappings to GMPLS as defined in [TP-IDENTIFIERS, Section 5.3].
	139. The MPLS-TP control plane must support Pseudowire path		139. The MPLS-TP control plane must support Pseudowire path
	identifiers of the form defined in [TP-IDENTIFIERS, Section 6].		identifiers of the form defined in [TP-IDENTIFIERS, Section
			6.].
	140. The MPLS-TP control plane must support MEG_IDs for LSPs and PWs		140. The MPLS-TP control plane must support MEG_IDs for LSPs and PWs
	as defined in [TP-IDENTIFIERS, Section 7.1.1].		as defined in [TP-IDENTIFIERS, Section 7.1.1].
	141. The MPLS-TP control plane must support IP compatible MEG_IDs		141. The MPLS-TP control plane must support IP compatible MEG_IDs
	for LSPs and PWs as defined [TP-IDENTIFIERS, Section 7.1.2].		for LSPs and PWs as defined [TP-IDENTIFIERS, Section 7.1.2].
	142. The MPLS-TP control plane must support MEP_IDs for LSPs and PWs		142. The MPLS-TP control plane must support MEP_IDs for LSPs and PWs
	of the forms defined in [TP-IDENTIFIERS, Section 7.2.1].		of the forms defined in [TP-IDENTIFIERS, Section 7.2.1].
	skipping to change at line 2577		skipping to change at line 2590
	Martin Vigoureux		Martin Vigoureux
	Alcatel-Lucent		Alcatel-Lucent
	Email: martin.vigoureux@alcatel-lucent.fr		Email: martin.vigoureux@alcatel-lucent.fr
	Elisa Bellagamba		Elisa Bellagamba
	Ericsson		Ericsson
	Farogatan, 6		Farogatan, 6
	164 40, Kista, Stockholm, SWEDEN		164 40, Kista, Stockholm, SWEDEN
	Email: elisa.bellagamba@ericsson.com		Email: elisa.bellagamba@ericsson.com
	Generated on: Thu, Nov 18, 2010 10:42:13 AM		Generated on: Fri, Jan 07, 2011 2:44:55 PM
End of changes. 27 change blocks.
	37 lines changed or deleted		52 lines changed or added
This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/