IETF Logo Mail Archive

Re: [ieee-ietf-coord] IEEE Ethertype Registration Update

Juan Carlos Zuniga <j.c.zuniga@ieee.org> Fri, 13 March 2020 17:45 UTC

Return-Path: <j.c.zuniga@ieee.org>
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 E2C333A0402 for <ieee-ietf-coord@ietfa.amsl.com>; Fri, 13 Mar 2020 10:45:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org
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 hfud0AtA1FPI for <ieee-ietf-coord@ietfa.amsl.com>; Fri, 13 Mar 2020 10:45:11 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 006A23A03FF for <ieee-ietf-coord@ietf.org>; Fri, 13 Mar 2020 10:45:10 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id a132so10918395wme.1 for <ieee-ietf-coord@ietf.org>; Fri, 13 Mar 2020 10:45:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eUZLJPvpC1qdJrWZd/Pg71yMJpA1RaMgznA2an5eRos=; b=ETTr6sTPm5RdI20nE5Op/U5hGXgbs0hqPRh1UJPEEcFcMyBwBZbUlvyLwE8COA04Ae dXy1+3mKhW2e4gUbZ4DrZIJg2dYyn21TGed/vISsbSf13RlVPG7NDQAimuvbXdiN5e4M QBIrQLUTc01x/GI/x/ZSf/bZv0GLYI1haIfZY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eUZLJPvpC1qdJrWZd/Pg71yMJpA1RaMgznA2an5eRos=; b=RnzfBx3UTnDaQL3Z0zAzg4FFirBs0+tD9Qw+oUcvg9LFpR4SJi4zmMeYF05dK6Pyfm QGUyO5lKZLpF4xrxkfxiUVvRBULqaQARQfj7D+N3bDCwGVjvHTNTqgJTlISSNQlQy2GA S1tLwqQAfqD8GRJ1ME0t4p2qAzIk2cXBYtKVzVuRt8nzwZMR5Qz9EicFoZg6K8F6ejfl mVsstFTkF2lW0k9jBucp6u+OIaY6fNcsTIIAqCzv4f7GhG56RfPCNNtk/zfC+4ui7oDE 6a8Vvtv58O85f6t+v8E6/C1UztTmMIf0v8rOw5XGOPUpkLSDVxUbjxjaLhKdqK3vnggZ C0GA==
X-Gm-Message-State: ANhLgQ2pytK0A6FPuSBSeuExwX00u9lojgXA2tOe3qqPY3sJ9/M/CP7P HSVjj+GiAD5mhu2tK8rckEQR583YOCYi+n6ctx+H+w==
X-Google-Smtp-Source: ADFU+vuijQAiFPRp3WJUs+JFJmqYudl5hope15YoMSuOnjnkbqPIpsOr+EklyQ7JtSUI+kk8/0pNd2XeW/T8H2IluEs=
X-Received: by 2002:a1c:2d4f:: with SMTP id t76mr11735299wmt.60.1584121509154; Fri, 13 Mar 2020 10:45:09 -0700 (PDT)
MIME-Version: 1.0
References: <CAMMESszk2TxwAPsQJsRJUt5F1-0t0SX1isTJ2o-04a8PU17s+w@mail.gmail.com> <DM5PR15MB1772D833AD46792494E72CF98BFA0@DM5PR15MB1772.namprd15.prod.outlook.com>
In-Reply-To: <DM5PR15MB1772D833AD46792494E72CF98BFA0@DM5PR15MB1772.namprd15.prod.outlook.com>
From: Juan Carlos Zuniga <j.c.zuniga@ieee.org>
Date: Fri, 13 Mar 2020 13:44:58 -0400
Message-ID: <CAHLBt83U8W9J+fGKo0z9QQZB9QiuA9jYvMTTT52YJRFA013oVQ@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Cc: "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>, Scott Mansfield <scott.mansfield=40ericsson.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d5bf8d05a0c0079d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/jpibUeElrATk59x-t9MYkHeJuFM>
Subject: Re: [ieee-ietf-coord] IEEE Ethertype Registration Update
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Mar 2020 17:45:14 -0000

Hi Alvaro,

I would suggest the option that Scott mentions of a direct email to the
ieee-registration-authority@ieee.org

For more info, you can read this
http://standards.ieee.org/develop/regauth/tut/ethertype.pdf

Best,

Juan Carlos

On Fri, Mar 13, 2020 at 8:28 AM Scott Mansfield <scott.mansfield=
40ericsson.com@dmarc.ietf.org> wrote:

> My understanding is that you login here:
> https://regauth.standards.ieee.org/standards-ra-web/app and submit an
> order.  Another option is to send an email to
> ieee-registration-authority@ieee.org with the same info from your email
> below and see what they say.
>
>
>
> -scott.
>
>
>
> *From:* ieee-ietf-coord <ieee-ietf-coord-bounces@ietf.org> *On Behalf Of *Alvaro
> Retana
> *Sent:* Thursday, March 12, 2020 4:57 PM
> *To:* ieee-ietf-coord@ietf.org
> *Subject:* [ieee-ietf-coord] IEEE Ethertype Registration Update
>
>
>
> Hi!
>
>
>
> To our IEEE friends, is there a process to update the registration
> information for Ethertypes?
>
>
>
>
>
> The IEEE RA assigned an Ethertype (0xAB37) to be used for
> draft-ietf-bier-mpls-encapsulation (this was done in 2018).  The request
> (according to the policies) was made after the IESG approved the document
> for publication, but before an RFC number was assigned (rfc8296, in this
> case).  The result is that the IEEE RA lists the assignment referring to
> draft-ietf-bier-mpls-encapsulation and not rfc8296 [1].
>
>
>
> Is there an easy way to update this information?  I can send e-mail to the
> IEEE RA, but was wondering if there is another way.  Also, the contact
> information for this particular entry is listed as "IETF Routing Area” —
> even though I haven’t asked, I would assume the IESG would want itself as
> the contact for IETF-related listings.  There are several entries with
> similar issues.
>
>
>
> Obviously this is not an urgent matter, just a little “spring cleanup”
> being done in the WG.
>
>
>
> Thanks!
>
>
>
> Alvaro.
>
>
>
>
>
> [1]
> https://regauth.standards.ieee.org/standards-ra-web/pub/view..html#registries
> <https://regauth.standards.ieee.org/standards-ra-web/pub/view.html#registries>
>
>
>
>
>
> _______________________________________________
> 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