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

Dan Romascanu <dromasca@gmail.com> Sat, 24 September 2016 04:29 UTC

Return-Path: <dromasca@gmail.com>
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 B4BA512B8A1; Fri, 23 Sep 2016 21:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Fx7w_a898j2n; Fri, 23 Sep 2016 21:29:50 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D44F412B89D; Fri, 23 Sep 2016 21:29:49 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id n185so123651259qke.1; Fri, 23 Sep 2016 21:29:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wqgOxxkjx/ZcMuokSFRTQpPIf16ImAf9pWSWKlweJ2A=; b=ggkG8n1QD8p+i6T4NjxHxGwxzI4nRohTfe4m3oW0+Q8ycdcWhVpU7EHVwt2iOx1V5o HX9q5vWNmc2MJBG3/enLjnUlZ1ybNXrxfy7UHPN3hxrDXUaS/EFk7fR5U4GfM6pVrLFr evgLa94Ig6AE59Ad1Bs3Ijk99m0fgJMBX3/Qr1UPgbjkvwU9MI5fPDvZzuDSlXWTAejB j74l8fsZA6qSxYWMEGoom3L95qR2RLNn67AsE+iebhcsPdZiq+TWbqgMGG0Yg1rw5r1N kOF8qSF6vlWk6V+VenTY0/rRbh4khQBjpAl3tyTA6uPR1UPVNllL1nYvLENXva0p+OGS Of+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wqgOxxkjx/ZcMuokSFRTQpPIf16ImAf9pWSWKlweJ2A=; b=ID1pb/6r04XRUkQHodEt63QxJanvDLbUCDjxbdhxl1+r3vpVl89jtoYIfqEWS3mHKA eNZcjqrQfz6dllIZJzGv/ahXzApg80RJT/PAQJ3eZRo2lvrE7GFATr5zpa22eWBoYZMH PhAhzzf0kRoNwbxMJQnn6B/aqMPgiq42IWZhEo5aBcXrNMfqPUMVkaQSR7Vkm4sbSj+m OxK4gkEr1rwD8PsTGgyhUsXkLUr7wrR4pmCkoVrMtinCb6Vv/153vLl7fRXYTm1sDwdp lRB6DHry1NQ07yb+vvy1oSn1/aSI98lGUprp3FqYyK75ssfnCgZJLmqgFMWKKShgcSIM 7tyg==
X-Gm-Message-State: AA6/9RkamJoIjDhXgGoaWP4XI4x88j989H/n8WKT6jd9/Vew2WhiYT9hi3txEamxMXmbOIB6VKkDZ4Nb8Tl8aw==
X-Received: by 10.55.163.196 with SMTP id m187mr11226851qke.40.1474691389027; Fri, 23 Sep 2016 21:29:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.38.180 with HTTP; Fri, 23 Sep 2016 21:29:48 -0700 (PDT)
In-Reply-To: <84ADCFD6-FDBC-4927-A88C-9BB699D081AB@cox.net>
References: <CAG4d1rcF9PfaAJnJ2Rp85sMwgk1TiHXSXmFLthLwfqj-wR889g@mail.gmail.com> <CAF4+nEGM+opEw8NT2KQZRtF8tOPe_g8-NdUpiPaOQYDo0zm7dg@mail.gmail.com> <84ADCFD6-FDBC-4927-A88C-9BB699D081AB@cox.net>
From: Dan Romascanu <dromasca@gmail.com>
Date: Fri, 23 Sep 2016 21:29:48 -0700
Message-ID: <CAFgnS4VEc_dgr4aV=x6zYayS4Z5ZdSKFGZh+ss5-D_=GMYb2SQ@mail.gmail.com>
To: ROBERT GROW <bobgrow@cox.net>
Content-Type: multipart/alternative; boundary="94eb2c05ecb66597cc053d3958d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/_M0UfTncx5r2Yx20-jlMuu0_lAQ>
Cc: "draft-ietf-forces-interfelfb@ietf.org" <draft-ietf-forces-interfelfb@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, Alia Atlas <akatlas@gmail.com>, Ralph Droms <rdroms.ietf@gmail.com>, Donald Eastlake <d3e3e3@gmail.com>, "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
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: Sat, 24 Sep 2016 04:29:52 -0000

Hi Bob,

Is there any way to accelerate this process and have responses or possible
further clarification questions in a shorter time than the maximal 90 days?

Thanks and Regards,

Dan


On Fri, Sep 23, 2016 at 3:05 PM, ROBERT GROW <bobgrow@cox.net> wrote:

> 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
>> <https://datatracker.ietf.org/doc/draft-ietf-forces-interfelfb/>, 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
>
>
>
> _______________________________________________
> ieee-ietf-coord mailing list
> ieee-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord
>
>