[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Google
  Web www.spinics.net

Re: 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



Yes/Support.

I also support the following comment from Mr.Tom Petch.

"There is no reason not to approve the allocation of a code point
and furthermore, I believe we should do it now, to facilitate the migration of the existing boxes to an approved solution."

It is very difficult for me to find the reason that a Generic Associated Channel Type for ITU-T MPLS-TP OAM cannot be allocated, considering the following points.

-Request from ITU-T(LS370 - Current status of Recommendation ITU-T G.8113.1/Y.1372.1, Operations, Administration and Maintenance mechanism for MPLS-TP in Packet Transport Network (PTN)) which I think reflects a strong demand for G.8113.1 in transport networks which sustain Internet all over the world.
-Necessity to continue cooperation and collaboration with ITU-T
-Expected difficulties to progress G.8113.1 OAM protocol based on Rough Consensus in IETF

IMHO, this is the case that the IETF leverages standards that are defined and maintained by other organizations; we continue to work with those organizations on their standards and do not attempt to take them over.

Best regards,

Yoshinori

> -----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



--
Yoshinori Koike
koike.yoshinori@xxxxxxxxxxxxx



[IETF Annoucements]     [IETF Obscurity Interest]     [IETF]     [IP Storage]     [Yosemite News]     [Linux]     [Pilates]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]

Add to Google