RE: Draft IESG Statement Regarding Ethertype Requests

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 30 July 2012 21:20 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4327211E80DF for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 14:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.926
X-Spam-Level:
X-Spam-Status: No, score=-102.926 tagged_above=-999 required=5 tests=[AWL=-0.327, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h0MY1Skv8-Eq for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 14:20:41 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 9147411E80DB for <ietf@ietf.org>; Mon, 30 Jul 2012 14:20:41 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOD5FlCHCzI1/2dsb2JhbABFuVmBB4IgAQEBAQMSHgpLBAIBCA0EAQMBAQsGDAsBBgFFAwYIAQEEEwgah2sLnWSdHotQhilgA5ZdhGmKEIJh
X-IronPort-AV: E=Sophos;i="4.77,682,1336363200"; d="scan'208";a="20358569"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 30 Jul 2012 17:15:17 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 30 Jul 2012 17:00:58 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Draft IESG Statement Regarding Ethertype Requests
Date: Mon, 30 Jul 2012 23:20:38 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407E24097@307622ANEX5.global.avaya.com>
In-Reply-To: <CDF73C59-A8E8-43B4-B67D-34CFAF541DB6@ietf.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Draft IESG Statement Regarding Ethertype Requests
Thread-Index: Ac1ucglK7XvYelX1TvqXeISuKMPP3AAJdJQA
References: <CDF73C59-A8E8-43B4-B67D-34CFAF541DB6@ietf.org>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 21:20:42 -0000

(I hope not to open some Pandora box or a long thread - my goal is to
make sure there is clarity in the language of the statement)

What 'IETF protocol specification' means here? 

Pretty clear it covers protocols defined in IETF standards-track
documents. 

Does it also cover protocols defined (described) in Informational RFCs
which are part of the IETF stream? 

Dan


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of IETF Chair
> Sent: Monday, July 30, 2012 7:40 PM
> To: IETF Announce
> Cc: IETF
> Subject: Draft IESG Statement Regarding Ethertype Requests
> 
> Last week the IAB and the IESG met with the leadership of IEEE 802.
One
> of the things that was discussed was the IEEE policies for allocating
> EtherTypes, and the IESG is considering the attached IESG Statement to
> implement an IETF policy that aligns with the IEEE policy.
> 
> If you have an comments on this proposed policy, please raise them on
> ietf@ietf.org.
> 
> Russ
> 
> = = = = = =
> 
> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some IETF
> protocol specification make use of Ethertypes.  Since Ethertypes are a
> fairly scarce resource, the IEEE RAC will not assign an Ethertype to a
> new IETF protocol specification that needs a new Ethertype until the
> IESG has approved the specification for publication as an RFC.
> 
> To let the IEEE RAC know that the IESG has approved an IETF protocol
> specification for publication, all future requests for assignment of
> Ethertypes for IETF protocol specifications will be made by the IESG.
> 
> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for
use
> during development and experimentation.
> 
> 
> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>     IEEE standard for Local and Metropolitan Area Networks:
>     Overview and Architecture -- Amendment 1: Ethertypes for
>     Prototype and Vendor-Specific Protocol Development.