draft-ietf-mpls-tp-process-01.txt		draft-ietf-mpls-tp-process-02.txt
	<div class="moz-text-flowed" style="font-family: -moz-fixed">
	Network Working Group L. Andersson		Network Working Group L. Andersson
	Internet-Draft Ericsson Inc		Internet-Draft Ericsson Inc
	Intended status: BCP D. Ward		Intended status: BCP D. Ward
	Expires: March 9, 2010 Cisco Systems		Expires: March 19, 2010 Cisco Systems
	M. Betts		M. Betts
	A. Farrel		A. Farrel
	Huawei		Huawei
	September 9, 2009		September 19, 2009
	IETF Multi-Protocol Label Switching (MPLS)		IETF Multi-Protocol Label Switching (MPLS)
	Transport Profile (MPLS-TP) Document Process		Transport Profile (MPLS-TP) Document Process
	draft-ietf-mpls-tp-process-01.txt		draft-ietf-mpls-tp-process-02.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 3, line 14		skipping to change at page 3, line 14
	Table of Contents		Table of Contents
	1. Introduction .................................................. 4		1. Introduction .................................................. 4
	1.1. Terminology ............................................... 4		1.1. Terminology ............................................... 4
	1.1.1. IETF Terms and Abbreviations .......................... 4		1.1.1. IETF Terms and Abbreviations .......................... 4
	1.1.2. ITU-T Terms and Abbreviations ......................... 6		1.1.2. ITU-T Terms and Abbreviations ......................... 6
	1.2. Purpose and Intent of Cooperation on MPLS-TP .............. 6		1.2. Purpose and Intent of Cooperation on MPLS-TP .............. 6
	2. Adaptation of the IETF Working Group Process .................. 8		2. Adaptation of the IETF Working Group Process .................. 8
	2.1. IETF Consensus and Mailing Lists .......................... 8		2.1. IETF Consensus and Mailing Lists .......................... 8
	2.2. Communications with the ITU-T ............................. 8		2.2. Communications with the ITU-T ............................. 9
	2.3. Adapted IETF Working Group Process ........................ 9		2.3. Adapted IETF Working Group Process ........................ 9
	2.3.1. Flow Chart ............................................ 9		2.3.1. Flow Chart ............................................ 9
	2.3.2. The IETF MPLS-TP Process ............................. 11		2.3.2. The IETF MPLS-TP Process ............................. 11
	2.4. Naming Conventions for MPLS-TP Documents ................. 15		2.4. Naming Conventions for MPLS-TP Documents ................. 16
	3. Expectations on ITU-T Participation in the Process ........... 16		3. Expectations on ITU-T Participation in the Process ........... 16
	3.1. MEAD Team Document Review ................................ 17		3.1. MEAD Team Document Review ................................ 17
	3.2. Working Group Document Review ............................ 17		3.2. Working Group Document Review ............................ 17
	3.3. Working Group Last Call and Document Approval ............ 18		3.3. Working Group Last Call and Document Approval ............ 18
	3.4. Non-Response to Liaisons ................................. 19		3.4. Non-Response to Liaisons ................................. 19
	4. Guidelines For MPLS-TP work in the ITU-T ..................... 20		4. Guidelines For MPLS-TP work in the ITU-T ..................... 20
	5. IANA Considerations .......................................... 20		5. IANA Considerations .......................................... 21
	6. Security Considerations ...................................... 20		6. Security Considerations ...................................... 21
	7. Acknowledgments .............................................. 21		7. Acknowledgments .............................................. 21
	8. References ................................................... 21		8. References ................................................... 21
	8.1. Normative References ..................................... 21		8.1. Normative References ..................................... 21
	8.2. Informative References ................................... 21		8.2. Informative References ................................... 21
	Authors' Addresses .............................................. 22		Authors' Addresses .............................................. 22
	1. Introduction		1. Introduction
	The IETF and ITU-T have entered into an agreement to develop the		The IETF and ITU-T have entered into an agreement to develop the
	Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP).		Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP).
	skipping to change at page 6, line 18		skipping to change at page 6, line 18
	by the IETF Routing Area Directors.		by the IETF Routing Area Directors.
	o MPLS-TP responsible AD - An IETF Routing Area Director with		o MPLS-TP responsible AD - An IETF Routing Area Director with
	management responsibility for the MPLS-TP effort.		management responsibility for the MPLS-TP effort.
	o IETF liaison to the ITU-T on MPLS - An individual assigned		o IETF liaison to the ITU-T on MPLS - An individual assigned
	responsibility by the IAB for managing the liaison relationship		responsibility by the IAB for managing the liaison relationship
	to the ITU-T in regard of all issues concerning MPLS, including		to the ITU-T in regard of all issues concerning MPLS, including
	MPLS-TP.		MPLS-TP.
			o Contribution - Within the IETF, a contribution is any submission
			to the IETF intended by the Contributor for publication as all or
			part of an Internet-Draft or RFC, and any statement made within
			the context of an IETF activity. Such statements include oral
			statements in IETF sessions as well as written and electronic
			communications. For more information on the IETF definition of a
			contribution see [RFC5378].
	1.1.2. ITU-T Terms and Abbreviations		1.1.2. ITU-T Terms and Abbreviations
	o Ad Hoc Team on MPLS-TP (ahtmplstp) - A team established by Study		o Ad Hoc Team on MPLS-TP (ahtmplstp) - A team established by Study
	Group 15 of the ITU-T to coordinate the work on MPLS-TP within the		Group 15 of the ITU-T to coordinate the work on MPLS-TP within the
	ITU-T and to act as a focal point for communication with the IETF		ITU-T and to act as a focal point for communication with the IETF
	about MPLS-TP.		about MPLS-TP.
	o Ad Hoc Team on MPLS-TP mailing list - An ITU-T mail exploder		o Ad Hoc Team on MPLS-TP mailing list - An ITU-T mail exploder
	(ahmpls-tp@lists.itu.int) established specifically for the		(ahmpls-tp@lists.itu.int) established specifically for the
	discussion and coordination of the MPLS-TP effort within the		discussion and coordination of the MPLS-TP effort within the
	ITU-T.		ITU-T.
	o Contribution - A contribution is a document that is submitted to		o Contribution - Within the ITU-T, a contribution is a document that
	the ITU-T to advance work on the development of a Recommendation		is submitted to the ITU-T to advance work on the development of a
	or to propose the development of a new Recommendation.		Recommendation or to propose the development of a new
			Recommendation.
	o Recommendation - A Recommendation is an ITU-T standards document.		o Recommendation - A Recommendation is an ITU-T standards document.
	1.2. Purpose and Intent of Cooperation on MPLS-TP		1.2. Purpose and Intent of Cooperation on MPLS-TP
	The purpose and objectives of the development activity on MPLS-TP is		The purpose and objectives of the development activity on MPLS-TP is
	described in [RFC5317]. The JWT decision includes the recognition		described in [RFC5317]. The JWT decision includes the recognition
	that the design authority for MPLS (including MPLS-TP) is the IETF.		that the design authority for MPLS (including MPLS-TP) is the IETF.
	At the same time, the JWT decision recognises the role of the ITU-T		At the same time, the JWT decision recognises the role of the ITU-T
	in providing input (especially input to the requirements statements)		in providing input (especially input to the requirements statements)
	skipping to change at page 22, line 14		skipping to change at page 22, line 14
	[RFC4929] Andersson, L. and Farrel, A., "Change Process for		[RFC4929] Andersson, L. and Farrel, A., "Change Process for
	Multiprotocol Label Switching (MPLS) and Generalized MPLS		Multiprotocol Label Switching (MPLS) and Generalized MPLS
	(GMPLS) Protocols and Procedures", BCP 129, RFC4929, June		(GMPLS) Protocols and Procedures", BCP 129, RFC4929, June
	2007.		2007.
	[RFC5317] Bryant, S. and L. Andersson, "Joint Working Team (JWT)		[RFC5317] Bryant, S. and L. Andersson, "Joint Working Team (JWT)
	Report on MPLS Architectural Considerations for a		Report on MPLS Architectural Considerations for a
	Transport Profile", RFC 5317, February 2009.		Transport Profile", RFC 5317, February 2009.
			[RFC5378] Bradner, S., and Contreras, J., "Rights Contributors
			Provide to the IETF Trust", BCP 78, RFC 5378, November
			2008.
	Authors' Addresses		Authors' Addresses
	Loa Andersson		Loa Andersson
	Ericsson Inc		Ericsson Inc
	Email: loa.andersson@ericsson.com		Email: loa.andersson@ericsson.com
	David Ward		David Ward
	Cisco Systems		Cisco Systems
	skipping to change at line 956		skipping to change at line 968
	Malcolm Betts		Malcolm Betts
	Huawei		Huawei
	Email: malcolm.betts@huawei.com		Email: malcolm.betts@huawei.com
	Adrian Farrel		Adrian Farrel
	Huawei		Huawei
	Email: adrian.farrel@huawei.com		Email: adrian.farrel@huawei.com
	</div>
End of changes. 11 change blocks.
	11 lines changed or deleted		23 lines changed or added
This html diff was produced by rfcdiff 1.36. The latest version is available from http://tools.ietf.org/tools/rfcdiff/