[ieee-ietf-coord] IEEE Ethertype Registration Update

Alvaro Retana <aretana.ietf@gmail.com> Thu, 12 March 2020 20:57 UTC

Return-Path: <aretana.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 50D6F3A094C for <ieee-ietf-coord@ietfa.amsl.com>; Thu, 12 Mar 2020 13:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 lofHEv2UY9Zm for <ieee-ietf-coord@ietfa.amsl.com>; Thu, 12 Mar 2020 13:57:33 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 757833A098B for <ieee-ietf-coord@ietf.org>; Thu, 12 Mar 2020 13:57:33 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id n18so9232279edw.9 for <ieee-ietf-coord@ietf.org>; Thu, 12 Mar 2020 13:57:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:date:message-id:subject:to; bh=Y0CMSa5x6JFgYY/fKHqS6bcohFk+U0VJQqJo3CF+ufg=; b=QW9Sd9Wmr7r0mR+LCXpk4OJL4TwOZZCIZs9YR8ynAODduh/o9wR9phmWTNbo5P8q0L SLFOs9+5ShfaunUuOW+f/bdnUnB9j5OCuhXaAo1RvV2A/g30piSEBjyvd6P1RhUGOyYU SbzfawPGIxvuj6q5umzt6A0Lwc1Fs/TqgGd+plXGzeDrkqFYj1urRyQyhhf3DFBIxp6o XHHBuqunaiWbOTwLJ+NFfJSodmVoBMvzcPsNWS3TcCjhsPujHz+AYeftYDSaAcAqBxCc Rgo0m3tOO/N9hyL2g/yZ0o7AXVSMFiTVc01NBJsYuhtzWHnAH2LW8W8yLbpROfuVrD70 RSzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=Y0CMSa5x6JFgYY/fKHqS6bcohFk+U0VJQqJo3CF+ufg=; b=R5jqaEMT0OtpB+yt9zIdAg9oB5sKhTNmykqN4UftTDjY8X0gPrrvbzpHYZMAxRbnZW m3jQRlyaW4W+zreJH3qPqU3EZAiCsjEgh+Zr4uBdaWADwy1oxyng52gy1yTMmFQNmI/f jrS6vq+J+xPB+tZDpxodNwPTCFC3GKcg8MIUXljziElO+ZmpTB7V1hz83XPeEYGqBhHj bNM6HXz68ysXhoc6h2CVTHmw0eqIm6XHijvdNOzs2Wdu966agikLsLkoSotoROuXuvJP cU0vuyzzWdiShlmt6isd/iCujT4UHz9MO2pg1XRyeTkWwlHay1b7+lbETBmp/DKJYxKz QAAQ==
X-Gm-Message-State: ANhLgQ0CJz71I6E0Yh8AiabCkfAJoarvJNhEhmrHXstTBEGEGqL9JloI b9xE6Qw3s20oRlRV4gI4vJ3aGg5MYKm7BRuIkQ6viVXv
X-Google-Smtp-Source: ADFU+vsscuPgDkg680GGaNGEjy0J6hr4ikyCoyZ2afQNmUmHfxHeG8L310lOA+bocaUbGZIQ5BdtlCvr6H7ODKtZ1p0=
X-Received: by 2002:a17:906:7083:: with SMTP id b3mr8785922ejk.238.1584046650751; Thu, 12 Mar 2020 13:57:30 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 12 Mar 2020 20:57:28 +0000
From: Alvaro Retana <aretana.ietf@gmail.com>
MIME-Version: 1.0
Date: Thu, 12 Mar 2020 20:57:28 +0000
Message-ID: <CAMMESszk2TxwAPsQJsRJUt5F1-0t0SX1isTJ2o-04a8PU17s+w@mail.gmail.com>
To: ieee-ietf-coord@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ecfe9d05a0ae9976"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/RTKWilJXWqR9mzY4hbFqJw_WiNw>
Subject: [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: Thu, 12 Mar 2020 20:57:42 -0000

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