Hello,
I still expect the author of draft-betts to answer my question...
"Maybe you could clarify how the text in your draft can be improved to
protect the use of the code point from future extensions beyond the purpose of
the code point allocation?"
I am a bit disappointed to see that the author simply does not respond to the
questions and proposed modifications he got on the list.
If we want to productively move forward, it would be good to have the author
responding to the questions and proposals.
Best regards,
Nurit
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of ext
Huub van Helvoort
Sent: Wednesday, March 21, 2012 1:19 AM
To: [email protected]
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet
basedOAM) to Informational RFC
Hello,
I continue my support for the codepoint allocation
I agree with Russ's statement in
https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=62185&tid=1331648664
"Some people are using the lack of a code point as the reason that
the cannot support the ITU-T document. My approach tells the ITU-T
that a code point is available to them IFF they are able to reach
consensus. The removes IETF from the discussion. This creates a
situation where G.8113.1 succeeded or fails based on the ITU-T
members actions, with no finger pointing at the IETF. This is
completely a Layer 9 consideration, and it has noting to do with
the technical content of the document. "
The codepoint allocation should allow the ITU-T to make refinements
to G.8113.1 such that it can satisfy the functional requirements defined
in RFC 5860.
Regards, Huub.
===================================================================
On 22-02-12 16:12, The IESG wrote:
>
> 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-Announce mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ietf-announce
--
*****************************************************************
我爱外点一七三一
