Re: [mpls-tp] New I-D desccribing how the IETF will review MPLS-TP Recommendations

Adrian,
My understanding of the outcome of the  JWT work has been that:
1. MPLS-TP will be developed by the IETF in accordance with ITU-T requirements
2. These requirements as well as specific MPLS-TP solutions will be eventually documented as RFCs
3. IETF will liaison I-Ds dealing with MPLS-TP to ITU-T and process their input at all the phases of its process
4. As a consequence, ITU-T will not develop any Recommendations pertaining to MPLS-TP.

Looks like this is not what is going to happen, in particular, ITU-T will develop Recommendations dealing with MPLS-TP.
Could you please explain how did this happen?

My personal experience of processing the same set of original concepts in multiple SDOs proves that this results in
a very messy situation with lots of minor discrepancies between the approved documents and confusion.
(I refer to the process of standardization of TDM PWs which resulted in 4 slightly different documents, approved accordingly
by IETF (RFC 4553, 5086 and 5087), ITU-T (Y.1413 and Y.1453), MEF (MEF-8) and BBF (MFA 4.1and MFA 8.0.0.
Tracing the differences between those (mainly the IETF and ITU-T versions can be traced on the PWE3 mailing list even now.)

Do we really need to do all that again, only on a much larger scale? (And yes, I know that it is good for job security:-)

Regards,
     Sasha

> -----Original Message-----
> From: mpls-tp-bounces@ietf.org 
> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Adrian Farrel
> Sent: Friday, January 15, 2010 4:28 PM
> To: mpls-tp@ietf.org
> Subject: [mpls-tp] New I-D desccribing how the IETF will 
> review MPLS-TP Recommendations
> 
> Hi,
> 
> Stewart and I have written an I-D describing our expectations 
> of how the 
> IETF expects to review and contribute to ITU-T 
> Recommendations on MPLS-TP.
> 
> Although this might be expected to have come from the ITU-T, 
> they say that 
> they are unable to do more than document existing process 
> (which is already 
> documented in process Recommendations) because anything else 
> would be "a 
> change in process" and would require consent at a very high 
> level. So we are 
> left with the somewhat suboptimal situation where we document our 
> "expectations".
> 
> Please note that there are a number of Recommendations and RFCs that 
> describe the "cooperative process" for work shared by the 
> ITU-T and IETF. 
> This draft covers a different situation where the ITU-T is producing 
> documents to describe aspects of MPLS-TP, but the design 
> authority for 
> MPLS-TP remains within the IETF. In this situation, the ITU-T 
> is responsible 
> for generating the text in the Recommendations, and the IETF needs to 
> provide a review and agree that the text is OK for publication.
> 
> We would welcome your comments on ways to clarify and improve 
> the text, and 
> your questions about areas that are unclear.
> 
> We have provided the text to the ITU-T's management across 
> MPLS-TP and have 
> had some useful comments back from Malcolm Betts (co-chair of 
> the ITU-T's Ad 
> Hoc Team for MPLS-TP). We also used a liaison from Study 
> Group 15 as the 
> basis for some of the description of process.
> 
> Thanks,
> Adrian
> ----- Original Message ----- 
> From: <Internet-Drafts@ietf.org>
> To: <i-d-announce@ietf.org>
> Sent: Friday, January 15, 2010 2:00 PM
> Subject: I-D Action:draft-farrel-mpls-tp-recommendation-review-00.txt
> 
> 
> >A New Internet-Draft is available from the on-line Internet-Drafts 
> >directories.
> >
> > Title           : IETF Expectations of Participation in 
> Development and 
> > Review of ITU-T Recommendations on MPLS-TP
> > Author(s)       : A. Farrel, S. Bryant
> > Filename        : draft-farrel-mpls-tp-recommendation-review-00.txt
> > Pages           : 12
> > Date            : 2010-01-15
> >
> > The decision to develop a Multiprotocol Label Switching (MPLS)
> > Transport Profile (MPLS-TP) in cooperation between the IETF and the
> > ITU-T is documented in RFC 5317 as the report of the Joint Working
> > Team on MPLS-TP. As part of this development process, the
> > International Telecommunications Union - Telecommunications
> > Standardisation Sector (ITU-T) will develop a number of
> > Recommendations that document the integration of MPLS-TP into the
> > transport network. Those Recomendations will not define any aspects
> > of MPLS-TP protocols or procedure because that work is reserved for
> > the IETF as the design authority for MPLS-TP.
> >
> > This document sets out the IETF's expectations of how the IETF,
> > through individual participation and through consensus decisions,
> > will contribute to in the development, review, and approval of those
> > Recommendations.
> >
> > This document does not modify any existing ITU-T or IETF procedures,
> > but shows how those procedures can be used to facilitate cooperation
> > for the MPLS-TP project.
> >
> > A URL for this Internet-Draft is:
> > 
> http://www.ietf.org/internet-drafts/draft-farrel-mpls-tp-recom
mendation-review-00.txt

_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp