draft-ietf-mpls-tp-process-04.txt   draft-ietf-mpls-tp-process-05.txt 
Network Working Group A. Farrel (Ed.) Network Working Group A. Farrel (Ed.)
Internet-Draft M. Betts Internet-Draft Huawei Technologies
Intended status: BCP Huawei Intended status: BCP L. Andersson
Expires: May 24, 2010 L. Andersson Expires: July 24, 2010 Ericsson Inc.
Ericsson Inc.
D. Ward D. Ward
Cisco Systems Juniper Networks
M. Betts
November 24, 2009 January 24, 2010
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-04.txt draft-ietf-mpls-tp-process-05.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 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.
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."
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.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Abstract Abstract
The decision to develop a Multiprotocol Label Switching (MPLS) The decision to develop a Multiprotocol Label Switching (MPLS)
Transport Profile (MPLS-TP) in cooperation between the IETF and the Transport Profile (MPLS-TP) in cooperation between the IETF and the
ITU-T is document in RFC 5317 as the decision of the Joint Working ITU-T is document in RFC 5317 as the decision of the Joint Working
Team on MPLS-TP. Team on MPLS-TP.
This document provides additional detail of the processes for the This document provides additional detail of the processes for the
development of IETF RFCs on MPLS-TP. It provides an adaptation of the development of IETF RFCs on MPLS-TP. It provides an adaptation of the
skipping to change at page 3, line 7 skipping to change at page 3, line 7
review across the two organizations. review across the two organizations.
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 PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network. capabilities and functionalities of a packet transport network.
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 .......................... 5 1.1.1. IETF Terms and Abbreviations ........................... 5
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, Intent, and Procedures for Cooperation on MPLS-TP . 6
1.3. A Note on the MPLS-TP Interoperability Design Team ........ 8 1.3. A Note on the MPLS-TP Interoperability Design Team ......... 8
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 .......................... 9 2.1. IETF Consensus and Mailing Lists ........................... 9
2.2. Communications with the ITU-T ............................. 9 2.2. Communications with the ITU-T .............................. 9
2.3. Adapted IETF Working Group Process ....................... 10 2.3. Adapted IETF Working Group Process ........................ 10
2.3.1. Flow Chart ........................................... 10 2.3.1. Flow Chart ............................................ 10
2.3.2. The IETF MPLS-TP Process ............................. 12 2.3.2. The IETF MPLS-TP Process .............................. 12
2.4. Naming Conventions for MPLS-TP Documents ................. 16 2.4. Naming Conventions for MPLS-TP Documents .................. 16
2.5. Boilerplate Text For Inclusion in MPLS-TP Documents ...... 16 2.5. Boilerplate Text For Inclusion in MPLS-TP Documents ....... 16
2.5.1. Abstract ............................................. 17 2.5.1. Abstract .............................................. 17
2.5.2. Introduction ......................................... 17 2.5.2. Introduction .......................................... 17
2.5.3. Recognition of IETF Consensus for Informational RFCs . 17 2.5.3. Recognition of IETF Consensus for Informational RFCs .. 17
3. Expectations on ITU-T Participation in the Process ........... 17 3. Expectations on ITU-T Participation in the Process ............ 17
3.1. Working Group Document Review ............................ 18 3.1. Working Group Document Review ............................. 18
3.2. Working Group Last Call and Document Approval ............ 18 3.2. Working Group Last Call and Document Approval ............. 18
3.3. Non-Response to Liaisons ................................. 21 3.3. Non-Response to Liaisons .................................. 21
4. Guidelines For MPLS-TP work in the ITU-T ..................... 21 4. Guidelines For MPLS-TP work in the ITU-T ...................... 21
5. IANA Considerations .......................................... 22 5. IANA Considerations ........................................... 22
6. Security Considerations ...................................... 22 6. Security Considerations ....................................... 22
7. Acknowledgments .............................................. 22 7. Acknowledgments ............................................... 22
8. References ................................................... 22 8. References .................................................... 22
8.1. Normative References ..................................... 22 8.1. Normative References ...................................... 22
8.2. Informative References ................................... 22 8.2. Informative References .................................... 22
Authors' Addresses .............................................. 23 Authors' Addresses ............................................... 23
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).
This agreement is known as the Joint Working Team on MPLS-TP (JWT) This agreement is known as the Joint Working Team on MPLS-TP (JWT)
Agreement and is documented in [RFC5317]. The agreement states that Agreement and is documented in [RFC5317]. The agreement states that
MPLS-TP will be documented in IETF RFCs, and assumes that there will MPLS-TP will be documented in IETF RFCs, and assumes that there will
be close cooperation with the ITU-T in reviewing these RFCs. This be close cooperation with the ITU-T in reviewing these RFCs. This
cooperation will include review of the work at all stages of cooperation will include review of the work at all stages of
skipping to change at page 6, line 47 skipping to change at page 6, line 47
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 - Within the ITU-T, a contribution is a document that o Contribution - Within the ITU-T, a contribution is a document that
is submitted to the ITU-T to advance work on the development of a is submitted to the ITU-T to advance work on the development of a
Recommendation or to propose the development of a new Recommendation or to propose the development of a new
Recommendation. 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, Intent, and Procedures for 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)
to the development process for MPLS-TP. There is also a clear to the development process for MPLS-TP. There is also a clear
statement of expectation that the ITU-T's opinions will be heard statement of expectation that the ITU-T's opinions will be heard
within the IETF and must be properly considered during the within the IETF and must be properly considered during the
development of MPLS-TP documents. development of MPLS-TP documents.
It should be noted that other related technologies (espeically those
for core MPLS and pseudowire deployments) do not fall within this
cooperation agreement. The IETF will continue to develop Internet
technologies as before and welcomes particpation from all
individuals. Where such developments overlap with MPLS-TP such that
they are important to the work on MPLS-TP, they will form part of the
cooperation project.
The development of standards for MPLS-TP is, therefore, carried out The development of standards for MPLS-TP is, therefore, carried out
within the IETF according to IETF process and with strong input from within the IETF according to IETF process and with strong input from
the ITU-T. This input takes three forms (see also Section 2.2): the ITU-T. This input takes three forms (see also Section 2.2):
o Active participation. o Active participation.
All interested parties are encouraged to participate in the All interested parties are encouraged to participate in the
development of MPLS-TP standards within the IETF through the development of MPLS-TP standards within the IETF through the
normal IETF process. In short, this involves the generation and normal IETF process. In short, this involves the generation and
documentation of new ideas as Internet-Drafts, and the discussion documentation of new ideas as Internet-Drafts, and the discussion
skipping to change at page 22, line 27 skipping to change at page 22, line 27
across the industry is an essential component to ensuring the across the industry is an essential component to ensuring the
security and stability of MPLS networks. security and stability of MPLS networks.
7. Acknowledgments 7. Acknowledgments
Thanks to Eric Gray who helped with grammar and useful comments. Thanks to Eric Gray who helped with grammar and useful comments.
Thanks to Tom Petch who spent time trying to sort out what the Thanks to Tom Petch who spent time trying to sort out what the
document said, and who sent comments that helped clarify the document said, and who sent comments that helped clarify the
document. Thanks to the participants of ITU-T Study Group 15 who document. Thanks to the participants of ITU-T Study Group 15 who
provided review and comments on an early version of this text. provided review and comments on an early version of this text.
Thanks to Ben Niven-Jenkins for discussions.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 23, line 26 skipping to change at page 23, line 26
2008. 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 Juniper Networks
Email: dward@cisco.com Email: dward@juniper.net
Malcolm Betts Malcolm Betts
Huawei
Email: malcolm.betts@huawei.com Email: malcolm.betts@rogers.com
Adrian Farrel Adrian Farrel
Huawei Huawei Technologies
Email: adrian.farrel@huawei.com Email: adrian.farrel@huawei.com
 End of changes. 17 change blocks. 
50 lines changed or deleted 61 lines changed or added

This html diff was produced by rfcdiff 1.37c. The latest version is available from http://tools.ietf.org/tools/rfcdiff/