IETF Logo Mail Archive

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

Donald Eastlake <d3e3e3@gmail.com> Fri, 23 September 2016 19:24 UTC

Return-Path: <d3e3e3@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 0189212B1FB; Fri, 23 Sep 2016 12:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, 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 FC_DdxYZ-Ah8; Fri, 23 Sep 2016 12:24:12 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 ECDD912B3D2; Fri, 23 Sep 2016 12:24:11 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id o3so23981589ita.1; Fri, 23 Sep 2016 12:24:11 -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=JxAZbEPX++aHpqJB2BpGH7er46MEtcPjKFQtPvqdzYw=; b=v9GlCkuLu7ANBmDrV5Kt/y560VWmtJHVzO4CHH8gbO4Z6Na5fnE4Z0xo7S2hZTHS8N YRtFlvDy1Izl6khBPMQvkPr2a7IQm6IgnAxLgtrq3XoPj/RGRCX6k44WLj8LPjmTeScX abGaw7PmI+1oO+9jo3OVkzORAaXgcCBNFIVyo+DdyEmq1+CZunRo2cfUd2BYOJXAbqmf IcABv5Ymn7dyjJUWxcgSOjTrF6tsSaIo3sbXw/B6y/LHqDEY93HaYiTnUoLiq5zo/oiH cc9MAbqNgM9D3q5ibXm2I9Gk1cPN6POPBDXubtgPLAM2gzWZHE2VMSYnrrVeYzHcgOTU W+8A==
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=JxAZbEPX++aHpqJB2BpGH7er46MEtcPjKFQtPvqdzYw=; b=RC9ckxmhgwl8Ki3hkP3ONzAztJhyKz0+IJsEE/z/cJJ/1OgrMacu6sDkSczlFSeL97 vke7BurqNxOJ2M6MCh6YY8/7FZte7ve8FkR/EW5W5BbaCNYXLjFNPoFQlI0fcYKMe+yz gB8P4/UCKToT5iuqj16167LGsV6yIHhNDLEoztIkrTYRBKZahEgYMnNhfGSGnoclfGl7 bKQQ9pt9Jz3pP7Fri2xikfbEMKte7EB4OdptEag746TIfidiW1J9vo6YIlqR54byOve5 J5nCsu7NuOOwmhSsDUUS4lBQcMUWKAXd43+oaAA9mcYv0yo5CE4dnfoR34ywI5UvP9oV uIMQ==
X-Gm-Message-State: AA6/9RmbO3auBb5PXYNuE7iNom72hmcEZjuL/7F2LwajKd+1xdU9x4KQghXmvFGrAXw2xiIlqYcumfdrZoRfZQ==
X-Received: by 10.36.193.130 with SMTP id e124mr5054788itg.53.1474658651364; Fri, 23 Sep 2016 12:24:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.154.144 with HTTP; Fri, 23 Sep 2016 12:24:10 -0700 (PDT)
In-Reply-To: <CAG4d1rcF9PfaAJnJ2Rp85sMwgk1TiHXSXmFLthLwfqj-wR889g@mail.gmail.com>
References: <CAG4d1rcF9PfaAJnJ2Rp85sMwgk1TiHXSXmFLthLwfqj-wR889g@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 23 Sep 2016 15:24:10 -0400
Message-ID: <CAF4+nEGM+opEw8NT2KQZRtF8tOPe_g8-NdUpiPaOQYDo0zm7dg@mail.gmail.com>
To: Alia Atlas <akatlas@gmail.com>
Content-Type: multipart/alternative; boundary="94eb2c07d1ea149750053d31b967"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/YRshCu06cRnF3fvNr9-sHezL6oE>
Cc: "draft-ietf-forces-interfelfb@ietf.org" <draft-ietf-forces-interfelfb@ietf.org>, "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: Fri, 23 Sep 2016 19:24:15 -0000

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

v2.23.0 | Report a Bug | By Email