draft-ietf-mpls-tp-process-03.txt   draft-ietf-mpls-tp-process-04.txt 
Network Working Group L. Andersson Network Working Group A. Farrel (Ed.)
Internet-Draft Ericsson Inc Internet-Draft M. Betts
Intended status: BCP D. Ward Intended status: BCP Huawei
Expires: April 16, 2010 Cisco Systems Expires: May 24, 2010 L. Andersson
M. Betts Ericsson Inc.
A. Farrel D. Ward
Huawei Cisco Systems
October 16, 2009
November 24, 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-03.txt draft-ietf-mpls-tp-process-04.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 5 skipping to change at page 2, line 27
This document does not specify any ITU-T process; ITU-T activities This document does not specify any ITU-T process; ITU-T activities
will be done according to ITU-T process/rules. will be done according to ITU-T process/rules.
This document does not specify or modify the normal IETF working This document does not specify or modify the normal IETF working
group process. It is limited to the specific adaptations of that group process. It is limited to the specific adaptations of that
process to facilitate the cooperation agreement between the IETF and process to facilitate the cooperation agreement between the IETF and
the ITU-T on MPLS-TP, and to ensure a good and consistent document the ITU-T on MPLS-TP, and to ensure a good and consistent document
review across the two organizations. review across the two organizations.
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
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 .......................... 4 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 and Intent of 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 .......................... 8 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 ........................ 9 2.3. Adapted IETF Working Group Process ....................... 10
2.3.1. Flow Chart ............................................ 9 2.3.1. Flow Chart ........................................... 10
2.3.2. The IETF MPLS-TP Process ............................. 11 2.3.2. The IETF MPLS-TP Process ............................. 12
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 ........... 15 2.5. Boilerplate Text For Inclusion in MPLS-TP Documents ...... 16
3.1. Working Group Document Review ............................ 16 2.5.1. Abstract ............................................. 17
3.2. Working Group Last Call and Document Approval ............ 16 2.5.2. Introduction ......................................... 17
3.3. Non-Response to Liaisons ................................. 19 2.5.3. Recognition of IETF Consensus for Informational RFCs . 17
4. Guidelines For MPLS-TP work in the ITU-T ..................... 19 3. Expectations on ITU-T Participation in the Process ........... 17
5. IANA Considerations .......................................... 20 3.1. Working Group Document Review ............................ 18
6. Security Considerations ...................................... 20 3.2. Working Group Last Call and Document Approval ............ 18
7. Acknowledgments .............................................. 20 3.3. Non-Response to Liaisons ................................. 21
8. References ................................................... 20 4. Guidelines For MPLS-TP work in the ITU-T ..................... 21
8.1. Normative References ..................................... 20 5. IANA Considerations .......................................... 22
8.2. Informative References ................................... 20 6. Security Considerations ...................................... 22
Authors' Addresses .............................................. 21 7. Acknowledgments .............................................. 22
8. References ................................................... 22
8.1. Normative References ..................................... 22
8.2. Informative References ................................... 22
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 4, line 43 skipping to change at page 4, line 43
process to facilitate the cooperation agreement between the IETF and process to facilitate the cooperation agreement between the IETF and
the ITU-T on MPLS-TP, and to ensure a good and consistent document the ITU-T on MPLS-TP, and to ensure a good and consistent document
review across the two organizations. review across the two organizations.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Although this document is not a protocol specification, this language Although this document is not a protocol specification, this language
is used for clarity and decisiveness. is used for clarity and decisiveness.
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.
1.1. Terminology 1.1. Terminology
This section includes a number of terms and abbreviations that are This section includes a number of terms and abbreviations that are
used in this document. The section is split into two subsection: used in this document. The section is split into two subsection:
IETF terms and ITU-T terms. IETF terms and ITU-T terms.
1.1.1. IETF Terms and Abbreviations 1.1.1. IETF Terms and Abbreviations
o JWT - Joint Working Team, a team with participants with experience o JWT - Joint Working Team, a team with participants with experience
from standards development in the IETF and the ITU-T. from standards development in the IETF and the ITU-T.
Note: The JWT is not part of either the IETF or ITU-T, but a group Note: The JWT is not part of either the IETF or ITU-T, but a group
that has been set up to facilitate cooperation on MPLS-TP between that has been set up to facilitate cooperation on MPLS-TP between
the two organizations. the two organizations.
skipping to change at page 15, line 48 skipping to change at page 16, line 48
draft-ietf-wgname-mpls-tp-topic-??.txt draft-ietf-wgname-mpls-tp-topic-??.txt
"wgname" is the acronym for any working group chartered to do "wgname" is the acronym for any working group chartered to do
MPLS-TP work, e.g. pwe3 or ccamp. MPLS-TP work, e.g. pwe3 or ccamp.
"topic" indicates the content of the draft, e.g. "oam-framework". "topic" indicates the content of the draft, e.g. "oam-framework".
"??" indicates a two digit version number, starting with "00". "??" indicates a two digit version number, starting with "00".
2.5. Boilerplate Text For Inclusion in MPLS-TP Documents
In order to clarify the status of MPLS-TP documents within the IETF,
the following boilerplate text is included in Internet-Drafts.
2.5.1. Abstract
In the Abstract of each MPLS-TP Internet-Draft, as the final
paragraph, the following text is included:
This document is a product of a joint Internet Engineering Task
Force (IETF) / International Telecommunication Union
Telecommunication Standardization Sector (ITU-T) effort to include
an MPLS Transport Profile within the IETF MPLS and PWE3
architectures to support the capabilities and functionalities of a
packet transport network.
2.5.2. Introduction
Somewhere within the Introduction section of each MPLS-TP Internet-
Draft, the following text is included:
This document is a product of a joint Internet Engineering Task
Force (IETF) / International Telecommunication Union
Telecommunication Standardization Sector (ITU-T) effort to include
an MPLS Transport Profile within the IETF MPLS and PWE3
architectures to support the capabilities and functionalities of a
packet transport network.
2.5.3. Recognition of IETF Consensus for Informational RFCs
In order to allow the ITU-T to make normative references to
Informational RFCs, the documents need to progress through IETF last
call and have the weight of IETF consensus. This will be recorded in
the published RFC using text added by the RFC Editor.
To make sure that the RFC Editor is reminded to do this, the
following two paragraphs are included before the Introduction section
of an Informational MPLS-TP Internet-Draft.
This Informational Internet-Draft is aimed at achieving IETF
Consensus before publication as an RFC and will be subject to an
IETF Last Call.
[RFC Editor, please remove this note before publication as an RFC
and insert the correct Streams Boilerplate to indicate that the
published RFC has IETF Consensus.]
3. Expectations on ITU-T Participation in the Process 3. Expectations on ITU-T Participation in the Process
The IETF looks for input from the ITU-T at two key points in the The IETF looks for input from the ITU-T at two key points in the
process described in Section 2. process described in Section 2.
o Steps 5 and 6 : Review of Working Group Documents o Steps 5 and 6 : Review of Working Group Documents
o Steps 9 and 10 : Working Group Last Call and Document Approval o Steps 9 and 10 : Working Group Last Call and Document Approval
This section briefly describes what the IETF expects to happen on the This section briefly describes what the IETF expects to happen on the
 End of changes. 9 change blocks. 
27 lines changed or deleted 93 lines changed or added

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