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

Ralph Droms <rdroms.ietf@gmail.com> Fri, 23 September 2016 21:38 UTC

Return-Path: <rdroms.ietf@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 6023E12B205; Fri, 23 Sep 2016 14:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 P0oJDwRfCD7v; Fri, 23 Sep 2016 14:38:00 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 6C4ED12B67A; Fri, 23 Sep 2016 14:29:29 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id t7so118138251qkh.2; Fri, 23 Sep 2016 14:29:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UyxJSQmiUFunSxWkGv1VnuXqQ+ATgH5blL2U1B2J2k8=; b=c3TFk2pgLvKzJ55h3WB4o6jbSiO5fykqCkpfuCJEUxL14p0qLkEH9E/pcHhcCovI6S Bd7kWmU5mPaeIDM8gAmiprkid0vg+t9lCecPnfbC+laxtRfcIiEr7AEZ+6+F5egdHoPu SL8W/PPaY2MKclwr80x+DOXIbx7oUzJakLB7PanV++8zPtBio+tWQDYs/BSVstYdvTyF +DD8gCPSByj1mTbiBSqo6vdq2AeBqj6XIhCUUF5tlyb+jvwwS7QOrT4ow11tZowI5Cs0 RDdKmUwxrWQ2VjQQnI2NXeWsewSq9xRLdeFgu7B7DsFBCmqTsNdOaB2clHCWTOlyNTom xEDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UyxJSQmiUFunSxWkGv1VnuXqQ+ATgH5blL2U1B2J2k8=; b=Pde9iI91c4xG+wdvVzwt/BjCk6sRJZSqBqbCqA2D1PrFNMz+TcQAJ5mU/y7Nk16z0f dx4LQJ19R7BsCjYX4yP4IQPeQkAnPvnYK8tSfJ1L047M+mlW1LVeZyhDjZlkGTud+03P UYM4kygpNmcxLE+qLgE2e868imRffrlMEVgExdkhVpxkuqK8Q5V1CsV00lBEHCNNGQ+6 cFuXFvZmkR90eg1R27tUZEEQjekB5+rPVt+HL2l6UIiqs/Y21xUjV0dWl2BUrHOkYE1l Z0pii/1sAmJ280TkeVDzgB4Ckl+VgyyFO9l0nDc1r/r6eUqdwCsQyVbGmIyAooUJwH3m 9Jcg==
X-Gm-Message-State: AA6/9RmdNpfKuGnA5ZexmVVp8f2yhxFnuWeK5x9OR8E+rGe7Kb/LorN68zeVL9ODJsEinA==
X-Received: by 10.55.138.67 with SMTP id m64mr11045856qkd.265.1474666168589; Fri, 23 Sep 2016 14:29:28 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:e2:336c:253f:606? ([2601:18f:801:600:e2:336c:253f:606]) by smtp.gmail.com with ESMTPSA id q68sm4908508qka.1.2016.09.23.14.29.28 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 23 Sep 2016 14:29:28 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-9965EF89-8D79-429C-99C1-D158B8D0551E"
Mime-Version: 1.0 (1.0)
From: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: iPad Mail (14A403)
In-Reply-To: <CAF4+nEGM+opEw8NT2KQZRtF8tOPe_g8-NdUpiPaOQYDo0zm7dg@mail.gmail.com>
Date: Fri, 23 Sep 2016 17:29:27 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <DF6D98C2-0B7D-4728-BC41-6ABF3EA1AAFE@gmail.com>
References: <CAG4d1rcF9PfaAJnJ2Rp85sMwgk1TiHXSXmFLthLwfqj-wR889g@mail.gmail.com> <CAF4+nEGM+opEw8NT2KQZRtF8tOPe_g8-NdUpiPaOQYDo0zm7dg@mail.gmail.com>
To: Alia Atlas <akatlas@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/l7Qx7Bjk8Iu7od4NqFWiYfrzC30>
Cc: Donald Eastlake <d3e3e3@gmail.com>, "draft-ietf-forces-interfelfb@ietf.org" <draft-ietf-forces-interfelfb@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.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: Fri, 23 Sep 2016 21:38:01 -0000

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