IETF Logo Mail Archive

Re: [ieee-ietf-coord] requesting an EtherType

ROBERT GROW <bobgrow@cox.net> Fri, 23 September 2016 22:06 UTC

Return-Path: <bobgrow@cox.net>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC2F12BA4B for <ieee-ietf-coord@ietfa.amsl.com>; Fri, 23 Sep 2016 15:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.217
X-Spam-Level:
X-Spam-Status: No, score=-4.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6hAl9G_3tDn0 for <ieee-ietf-coord@ietfa.amsl.com>; Fri, 23 Sep 2016 15:06:02 -0700 (PDT)
Received: from fed1rmfepo101.cox.net (fed1rmfepo101.cox.net [68.230.241.143]) by ietfa.amsl.com (Postfix) with ESMTP id 5FCA612BA30 for <ieee-ietf-coord@ietf.org>; Fri, 23 Sep 2016 15:06:02 -0700 (PDT)
Received: from fed1rmimpo306.cox.net ([68.230.241.174]) by fed1rmfepo101.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20160923220601.BBIA2641.fed1rmfepo101.cox.net@fed1rmimpo306.cox.net> for <ieee-ietf-coord@ietf.org>; Fri, 23 Sep 2016 18:06:01 -0400
Received: from [192.168.1.16] ([68.101.171.193]) by fed1rmimpo306.cox.net with cox id nA601t00X4AilM801A61Mp; Fri, 23 Sep 2016 18:06:01 -0400
X-CT-Class: Clean
X-CT-Score: 0.00
X-CT-RefID: str=0001.0A090205.57E5A749.004F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CT-Spam: 0
X-Authority-Analysis: v=2.1 cv=S5x5uNYP c=1 sm=1 tr=0 a=zfK2h7QH0I6ncxJ5I0E4kQ==:117 a=zfK2h7QH0I6ncxJ5I0E4kQ==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=pGLkceISAAAA:8 a=48vgC7mUAAAA:8 a=LblHZJZWyH3ivculKeQA:9 a=CjuIK1q_8ugA:10 a=rH5NFpFiZ9QA:10 a=mau0lnv0J6cA:10 a=rWG3eU-jwRe_16CzjxgA:9 a=CAbqeEBI6JAl9FMt:21 a=_W_S_7VecoQA:10 a=6kGIvZw6iX1k4Y-7sg4_:22 a=w1C3t2QeGrPiZgrLijVG:22
X-CM-Score: 0.00
Authentication-Results: cox.net; auth=pass (PLAIN) smtp.auth=bobgrow@cox.net
Content-Type: multipart/alternative; boundary="Apple-Mail=_4A794E21-8DEC-4CAD-9172-C4CF36E5A291"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: ROBERT GROW <bobgrow@cox.net>
In-Reply-To: <n9e11t00G0xxhYs019e26x>
Date: Fri, 23 Sep 2016 15:05:25 -0700
Message-Id: <84ADCFD6-FDBC-4927-A88C-9BB699D081AB@cox.net>
References: <CAG4d1rcF9PfaAJnJ2Rp85sMwgk1TiHXSXmFLthLwfqj-wR889g@mail.gmail.com> <CAF4+nEGM+opEw8NT2KQZRtF8tOPe_g8-NdUpiPaOQYDo0zm7dg@mail.gmail.com> <n9e11t00G0xxhYs019e26x>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/DJcZjpZ4bqfNR1CWoo9Bwzb3Q6Q>
Cc: Donald Eastlake <d3e3e3@gmail.com>, "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>, "draft-ietf-forces-interfelfb@ietf.org" <draft-ietf-forces-interfelfb@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, Alia Atlas <akatlas@gmail.com>
Subject: Re: [ieee-ietf-coord] requesting an EtherType
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Sep 2016 22:06:04 -0000

It is important to answer the questions on the form clearly, especially about sub typing, including indication of why a new Ethertype is needed versus using an existing IETF assignment.  If the application has already been submitted, and not sufficiently answered, you might get a request for more information.  The application is processed within 90 days.

Bob Grow
Chair, IEEE-SA Registration Authority Committee.


On Sep 23, 2016, at 2:29 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:

> My recollection is that suresh has taken responsibility here and submitted the request.
> 
> - Ralph
> 
> On Sep 23, 2016, at 3:24 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> 
>> Last time I did this, you just go to the public Ethertype request site, fill out the form saying it is for standards use, indicate you are going to pay by wire transfer, and interact with the IEEE office that handles this and have the invoice amount set to zero.
>> 
>> Donald
>> from iPhone 
>> 
>> On Friday, September 23, 2016, Alia Atlas <akatlas@gmail.com> wrote:
>> Hi,
>> 
>> A document, draft-ietf-forces-interfelfb-06, was approved by the IESG for publication and is in the RFC Editor queue.
>> 
>> I had assumed that the EtherType request would be made as part of the processing, as per https://www.ietf.org/iesg/statement/ethertypes.html.  That appears to not be the case.
>> 
>> What is the correct procedure for officially requesting the EtherType so that this document can finally be published?
>> 
>> Thanks,
>> Alia
>> 
>> 
>> -- 
>> Sent from Gmail Mobile
>> _______________________________________________
>> ieee-ietf-coord mailing list
>> ieee-ietf-coord@ietf.org
>> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord
> _______________________________________________
> ieee-ietf-coord mailing list
> ieee-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord

v2.23.0 | Report a Bug | By Email