Maarten, please be aware of what u asking for - you won't have a "an ACH codepoint to G.8113.1".
First, what is requested is an "Associated Channel Type" and it will be assigned to the RFC resulting from draft-betts-. I will not do my tutorial on Associated Channel acronyms, but it could do it if needed, but some other venue. Assigning the Associated Channel Type is what I see that a solid majority want to happen! This is not an attempt to end-run the consensus call by the AD, just my personal read of the situation. The first remaining caveat is the draft-betts is too poorly written and need to be improve, suggestions has been sent to this mailing list, I take it that people who send mails to this list saying that they support Russ' proposal also implicitly support these improvements. The second caveat is that an ITU-T Recommendation is not stable according to the criteria we normally apply to RFCs. We are solving this by generating a RFC from draft-betts-. I believe that the way out here is to "update" "RFC draft-betts-" every time ITU-T rev G.8113.1. That way we will have our stable reference pointing to the right version of G.8113.1. I'd like to hear from the process people on this, but not as part of this last call. /Loa On 2012-03-19 11:55, Maarten vissers wrote:
+1 -------- Original Message -------- From: Rui Costa<[email protected]> Sent: zaterdag 17 maart 2012 12:00:56 +0000 To: [email protected]<[email protected]> 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 Hello, I support the allocation of an ACH codepoint to G.8113.1, not precluding the ITU-T to progress refinements. Ergo, i support this draft and proposal http://www.ietf.org/mail-archive/web/ietf/current/msg72191.html IMHO, the status quo analysis expressed in both http://www.ietf.org/mail-archive/web/ietf/current/msg72188.html and http://www.ietf.org/mail-archive/web/ietf/current/msg72273.html is accurate. Regards, Rui ========================================================= -------- Original Message -------- From: The IESG<[email protected]> Sent: Wed, 22 Feb 2012 07:12:52 -0800 To: IETF-Announce<[email protected]> 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 [email protected] mailing lists by 2012-03-21. Exceptionally, comments may be sent to [email protected] 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 mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf
-- Loa Andersson email: [email protected] Sr Strategy and Standards Manager [email protected] Ericsson Inc phone: +46 10 717 52 13 +46 767 72 92 13
