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

Dan Romascanu <dromasca@gmail.com> Sat, 24 September 2016 14:03 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 2E2EE12B8D8; Sat, 24 Sep 2016 07:03:45 -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 MX-oczo5Zboz; Sat, 24 Sep 2016 07:03:42 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 AEAC212B150; Sat, 24 Sep 2016 07:03:42 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id g67so69489991qkd.0; Sat, 24 Sep 2016 07:03:42 -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=pOh2nRsV1qCy987Q3RKrhlPJZl943ZU1VzKk+6Ln86c=; b=wHGau9LzYjaO+rJkZwhNZ6g5ekTtlqz91Z+jMRDsdhqRS/igaQhhYxoLxNllFVrsNZ WQabHzGaVvRamHnV1nXVy5NfSCNupg0QmqeOidxCRMlv6DOKHSgAjPry9WRLs7FEOqKT LbxDq9hj71bw5XU2EVMoCFN5bVyB8lMpvAoPWslfmPnOHwNbWoSzEICLgrR1/uZHOpJ5 kH01F9bJuvwq/jf4RZPpKF/R8G1v5eSWi1qbcPUwGxa8KBEH6iuvz1lFB2CghMjX2y1Z 0RjrOSoH4QObmih8/nL/YeqIXpUfiPKl1TSnPwuEu/LPG/b8+dpSGwH7CmkyzP0iDBqk n7Zg==
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=pOh2nRsV1qCy987Q3RKrhlPJZl943ZU1VzKk+6Ln86c=; b=GAb8X9OjT6myqv70V9mDw98v3AIeGcvPZG2KHqCe8hHpO7ySHOH/v1gajuGB00U2E7 nfL1QG0L0/y5i7nIeTtn+9QX/t6GaOWgJtRZgaDQ3m6SrBNAF8vKT8hbJUgfZGIpLQX/ dI7qjTGTehy/jNhIYD0fhEVDn5f09TQMA3R2Mgw4/x+/LLpMQPRHRTKSDRTgHZQj5PM1 kwC+EOwxxSTN4HMLv7XoUeNnjtzaIh8MLLDvgq+OY51C1BvGav9oMC9W08TV/xr01fdg EAcVU4HkqQVKQuVDsiAsKPRyAF2oDg4FC6rOiDd7nYyAoL+F+8J1HI9LkXrhc30UBkBG hEZQ==
X-Gm-Message-State: AA6/9RlRM/l3WWe/kQZZFL2xV8rpKguyqm38ogy/wJ9bkugeLlBZClpy3ZxLN8X7dnmuud7fgfaTjbO2XB3iAQ==
X-Received: by 10.55.166.81 with SMTP id p78mr13008591qke.18.1474725821845; Sat, 24 Sep 2016 07:03:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.38.180 with HTTP; Sat, 24 Sep 2016 07:03:41 -0700 (PDT)
In-Reply-To: <CAF4+nEGusH7kC8wnShLRVDea8=eUDYwynS9bCuaH4cpu1WMhMA@mail.gmail.com>
References: <CAG4d1rcF9PfaAJnJ2Rp85sMwgk1TiHXSXmFLthLwfqj-wR889g@mail.gmail.com> <CAF4+nEGM+opEw8NT2KQZRtF8tOPe_g8-NdUpiPaOQYDo0zm7dg@mail.gmail.com> <84ADCFD6-FDBC-4927-A88C-9BB699D081AB@cox.net> <CAFgnS4VEc_dgr4aV=x6zYayS4Z5ZdSKFGZh+ss5-D_=GMYb2SQ@mail.gmail.com> <CAF4+nEGusH7kC8wnShLRVDea8=eUDYwynS9bCuaH4cpu1WMhMA@mail.gmail.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Sat, 24 Sep 2016 07:03:41 -0700
Message-ID: <CAFgnS4VzxuEnL_h64ev8m+V7kTm7zRJHUktPxwECqmJSiGhLxA@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary="94eb2c06e24cc094ee053d415cdd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/s4aATZp42IshKH7u8SctCBH3kcM>
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>, ROBERT GROW <bobgrow@cox.net>, "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 14:03:45 -0000

Can we maybe try to cut a little bit from the clerical process and make the
earlier review of such requests part of our coordination, at least in what
concerns the technical aspects? The Internet-Drafts were written with the
purpose of providing the required technical documentation. They went
through the IETF consensus process, with its principal milestones (LCs)
also announced on this (ieee-ietf) list. I would suspect that if any
important information was missing or the request was not targeting the
right level, this would have been already flagged up. If something was
somehow missed, we  should know earlier than the three month typical
response time.

Thanks and Regards,

Dan


On Sat, Sep 24, 2016 at 6:07 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> I have limited network access right now.
>
> As I recall, you have to provide technical documentation (can reference an
> Internet draft) which should mention sub typing, etc. (There have been
> cases of tags where subtyping is not required but it's more difficult to
> get through the system.) Generally there has been a contractor that
> examines the application.
>
> If you want to know if your application is in process, I recommend picking
> up the phone during business hours in the eastern US time zone and calling
> the office that handles this. You will get a clerical person but at least
> they can confirm that the application was received.
>
> I believe Pat Thaler has volunteered to informally assist but she may be
> very busy today and might not get to email for a day or two.
>
> Donald
> from iPhone
>
>
> On Saturday, September 24, 2016, Dan Romascanu <dromasca@gmail.com> wrote:
>
>> 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
>>>
>>>
>>
>
> --
> Sent from Gmail Mobile
>