Re: [mpls] Draft: Response to Updated draft Recommendation G.tpoam [Ref 043.02]

[Christopher LILJENSTOLPE <[e-mail]>]

Greetings Rui,

	I'm not sure how the LS should recognize anyone's "inputs" outside of the form of "there is an agreement and the IETF has a policy (as does the ITU) regarding referencing I-D's by other SDOs"  and this inbound liaison seems to contravene those.  The merits of bhh, or any other technical discussion, is not the topic of the LS.  My interpretation of the JWT agreement, IETF process, and ITU-T's own statements on reference to ID's would lead me to support this LS.

	On the non-germain topic of "not supporting service provider inputs" - it may not support all service provider inputs, but there are service providers that do support the current path of the WG.

	Chris

On 14Jan2011, at 05.24, Rui Costa wrote:

> Hello,	
> 
> This LS doesn't recognize service providers' inputs, where the inclusion of Y.1731 based OAM tools within the MPLS-TP OAM toolkit is grounded, so I don't agree with it.	
> 
> I think both approaches (this one as well as the one documented in a set of MPLS WG drafts) should proceed. This one meets a need that has been expressed in the IETF.   
> 
> Regards,	
> Rui	
> 
> 
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Stewart Bryant
> Sent: segunda-feira, 10 de Janeiro de 2011 10:57
> To: [e-mail]
> Subject: [mpls] Draft: Response to Updated draft Recommendation G.tpoam [Ref 043.02]
> 
> I propose to send the following Liaison Response to the ITU-T on Friday 
> 14th January and am posting it to the MPLS WG list for review.
> 
> =======
> 
> Response to Updated draft Recommendation G.tpoam [Ref 043.02]
> 
> From: IETF Liaison to ITU-T on MPLS [e-mail]
> To: [e-mail], [e-mail], [e-mail], [e-mail]
> CC: Greg Jones, [e-mail], [e-mail], [e-mail]
> [e-mail], [e-mail], [e-mail]
> [e-mail], [e-mail]
> [e-mail], [e-mail]
> [e-mail], [e-mail]
> 
> For Action
> 
> The MPLS Working Group notes that this document contains text describing 
> MPLS-TP OAM protocols not designed and standardized using the IETF 
> Standards process. Specifically it uses material from 
> draft-bhh-mpls-tp-oam-y1731-06.
> 
> We wish to draw your attention to the status section of 
> draft-bhh-mpls-tp-oam-y1731-06 which states:
> 
> "Internet-Drafts are draft documents valid for a maximum of six months 
> and may be updated, replaced, or obsoleted by other documents at any 
> time. It is inappropriate to use Internet-Drafts as reference material 
> or to cite them other than as "work in progress".
> 
> Please also note that since the draft filename starts with the prefix 
> string "draft-bhh" this clearly identifies it to the reader as a 
> document expressing the personal technical views of the authors and 
> hence hence as a document that that does not have any acknowledged level 
> of IETF consensus.
> 
> Since the text of draft Recommendation for G.tpoam is based on an 
> MPLS-TP OAM protocol not designed within the IETF Standards Process this 
> is a breach of the SG15 agreement with the IETF as published in Report 
> of the first meeting of Working Party 3/15 Transport network structures 
> (2009-2012) (Geneva, 1 - 12 December 2008) which can be found at 
> http://www.itu.int/md/T09-SG15-R-0004/en
> 
> Please confirm that the ITU-T intends to continue with the joint work on 
> MPLS-TP and that the ITU-T will align this recommendation with the IETF 
> MPLS-TP OAM design before advancing this document through the ITU-T 
> publication process.
> 
> The MPLS Working Group would also like to draw the attention of ITU-T 
> SG15 to the IETF copyright rules. Please see 
> http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.htm 
> for further details.
> 
> Since this draft Recommendation contains text in which the ITU-T SG15 
> has proposed making changes to IETF protocols without the approval of 
> the IETF, the MPLS Working Group have referred this liaison to the IAB 
> for their consideration.
> 
> 
> =========
> _______________________________________________
> mpls mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mpls
> 

---
李柯睿
Check my PGP key here:
https://www.asgaard.org/~cdl/cdl.asc