Russ, The LS370 version of G.8113.1 has been sent to the ITU-T Nov 2012 meeting (a.k.a. WTSA) for further discussion. At this point, no one can tell if it will be approved. As the level of stability and maturity of G.8113.1 will not be changed between now and Nov, the opinions made by ITU-T members at the last meeting concerning its stability would not be changed. So the concerns expressed in this Last Call relating to the LS370 version will remain even if G.8113.1 is approved at the ITU-T Nov meeting. Thanks, KY -----Original Message----- From: Russ Housley [mailto:housley@xxxxxxxxxxxx] Sent: Thursday, March 01, 2012 11:06 AM To: Kyung-Yeop Hong (hongk) Cc: ietf@xxxxxxxx Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC KY: Would you support the assignment to an approved G.8113.1? That is, if the document contained a normative reference to the approved G.8113.1, then the document that makes the code point allocations would sit in the RFC Editor queue until the ITU-T reaches consensus and approves G.8113.1. Russ On Mar 1, 2012, at 10:14 AM, Kyung-Yeop Hong (hongk) wrote: > No/do not support. > > One of the issues with G.8113.1 in LS370 is its stability and maturity. > That was one of the reasons why it was not approved. > > The Ethernet based OAM protocol documented in the LS370 version is > intended to be deployed for MPLS networks. I think the IETF has a duty > to ensure that a solution is stable and works for MPLS networks before > the code point allocation. A number of concerns with the deployment of > this proposed protocol raised in > draft-spercher-mpls-tp-oam-considerations are critical to the Internet > and must be taken into consideration in this Last Call. > > KY > > >> -----Original Message----- >> From: ietf-announce-bounces@xxxxxxxx [mailto:ietf-announce- >> bounces@xxxxxxxx] On Behalf Of The IESG >> Sent: 22 February 2012 15:13 >> To: IETF-Announce >> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> > (Allocation of > an >> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to >> Informational RFC >> >> >> The IESG has received a request from an individual submitter to > consider >> the following document: >> - 'Allocation of an Associated Channel Code Point for Use by ITU-T >> Ethernet based OAM' >> <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RFC >> >> The IESG plans to make a decision in the next few weeks, and solicits >> final comments on this action. Please send substantive comments to the >> ietf@xxxxxxxx mailing lists by 2012-03-21. Exceptionally, comments may > be >> sent to iesg@xxxxxxxx instead. In either case, please retain the >> beginning of the Subject line to allow automated sorting. >> >> Abstract >> >> This document assigns an Associated Channel Type code point for >> carrying Ethernet based Operations, Administration, and Management >> messages in the MPLS Generic Associated Channel (G-ACh). >> >> The file can be obtained via >> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/ >> >> IESG discussion can be tracked via >> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/ >> >> >> No IPR declarations have been submitted directly on this I-D. >> _______________________________________________ >> IETF-Announce mailing list >> IETF-Announce@xxxxxxxx >> https://www.ietf.org/mailman/listinfo/ietf-announce > > _______________________________________________ > mpls mailing list > mpls@xxxxxxxx > https://www.ietf.org/mailman/listinfo/mpls > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf