Feng Surely you agree with me that the primary consideration is that we should do what what we collectively believe is best for the Internet in the long term? There are many cases where the IETF has been presented with an existing implementation, but the collective view is that the pre-standards implementation is NOT RECOMMENDED for deployment going forward. Draft spercher-mpls-tp-oam-considerations raises a number of concerns with the deployment of the proposal that underlines draft-betts-itu-oam-ach-code-point, which surely need to be taken into consideration. - Stewart On 27/02/2012 03:58, HUANG Feng F wrote: > +1 > > The Internet Engineering Task Force (IETF) is a large open international community, it should support running code has been deployed in real network. > > Quote from David Clark: "We reject kings, presidents and voting. We believe in rough consensus and running code". > > B.R. > Feng > > > -----Original Message----- > From: ietf-bounces@xxxxxxxx [mailto:ietf-bounces@xxxxxxxx] On Behalf Of Daniel Cohn > Sent: 2012年2月23日 18:35 > To: ietf@xxxxxxxx > Subject: RE: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC > > Support - as there is no foreseen shortage in ACH types, I don't see a > reason why this code point should not be allocated to an ITU developed > protocol that is already deployed in the field. > > DC > >> -----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 > _______________________________________________ > pwe3 mailing list > pwe3@xxxxxxxx > https://www.ietf.org/mailman/listinfo/pwe3 > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf -- For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf