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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



All,

I agree with Stewart, while shortage of code points might be a reason
to think twice before allocating one, "abundance" in itself is never
a reason to allocate code points.

I'm way less inclined to approve of this draft in the condition it
is now. Actually I believe that we should think very careful before
approving it at all.

/Loa

On 2012-02-27 14:01, Stewart Bryant wrote:

Daniel

Shortage of ACh types was never an issue.

The issue issue is the concerns articulated in
draft-sprecher-mpls-tp-oam-considerations

Stewart


On 23/02/2012 10:35, Daniel Cohn wrote:
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




--


Loa Andersson                         email: loa.andersson@xxxxxxxxxxxx
Sr Strategy and Standards Manager            loa@xxxxx
Ericsson Inc                          phone: +46 10 717 52 13
                                             +46 767 72 92 13
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]