Re: [Int-area] Procedure for obtaining Ethertypes

Bob Hinden <bob.hinden@gmail.com> Thu, 10 November 2022 12:45 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEC92C14F726; Thu, 10 Nov 2022 04:45:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 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, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJv--1KNt6ku; Thu, 10 Nov 2022 04:45:33 -0800 (PST)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7E8CC14F73D; Thu, 10 Nov 2022 04:45:33 -0800 (PST)
Received: by mail-qt1-x82e.google.com with SMTP id hh9so793196qtb.13; Thu, 10 Nov 2022 04:45:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=C3AOpqWFarRSTzRNIQvZ0T93+YQ+E37wxSJbdBeFtGc=; b=YQf4kQL1o5XlXsmBhelc8xoV5qkQUt6+G9xeuew4wD2kaHilJIHoxlWi/11SpzNY6N 2aovaZ3eyps4AGZcIYfCheBCFE2/7P4xglV+WFFbNcW/KaseWOQktiRLhbCufEvmGtcd Qw+7Ot6fbt9jwsJzznFSn70hVx8piww3TQ8DqlU5EnndIxkcK9FIXT+nMjq9jwRcALfl 5fGgYcsnNAcY+1xp2CgFnSWHUoSd6g/GcGywFBpsX3W1npJiRMrN92rZAQywxrzmBKYD Aa5zKpPBABKRBGhxWUFJ16j0KnCDm9zVm+MyNvDO9ACFTqY4CElwxA6rpZc8gsg9gH2z 87Jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=C3AOpqWFarRSTzRNIQvZ0T93+YQ+E37wxSJbdBeFtGc=; b=Er16AlFNXbcvpz3krUcp9Sl/ud694Nk8+Bx5tmAapSzCVhgDe/nr/p2/18J5dErM23 WhK2uFFGWW4l5CAG5IzXSf6AuCUCS2m6kUan3HbiakUHZWttrFUzHTdmH2mQnfOsA02Z 7Ew5WoNW1OEqn5t4NT843Mi7DcyHzwYn/x8ouQ4tIbnn8XH/O5UlgIVSkHBQ9DxjvmBF oO5DpuovyPt8UdNNJS6KuEhnWmfIAi4hbEir+0TL2AbGAr6J0lqdRIHBbR31NZ3QZn2J Tshty/WMsVCYbchK8YqIkIFhD+AYK/yy8Hsof2Qymm9LNoiC9QWpmTlC5reN5Z1jYWkm 9AVg==
X-Gm-Message-State: ANoB5pms2pWOOu5fbAoML2P9N0D391l7moZJdzp+WW4biz03E9yaRsbi ijLNSfWBCD9YTZy01RlDfEA=
X-Google-Smtp-Source: AA0mqf6hFSXwn3gLgBJcUXZVKg9RoNH5oaHwoqH7f1hEfSwRGLBTF9/rv+8+gscGkeGJXKwVpZn1DQ==
X-Received: by 2002:ac8:7393:0:b0:3a5:91b2:a2a6 with SMTP id t19-20020ac87393000000b003a591b2a2a6mr15032592qtp.143.1668084332764; Thu, 10 Nov 2022 04:45:32 -0800 (PST)
Received: from smtpclient.apple ([2001:67c:370:128:584a:1084:d04f:8c08]) by smtp.gmail.com with ESMTPSA id bl42-20020a05620a1aaa00b006fa8299b4d5sm12759224qkb.100.2022.11.10.04.45.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Nov 2022 04:45:31 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_F9B8672D-98B6-4597-88D1-73382A02EE07"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CAF4+nEE5mO7d2Y31wprmOF_6c6E_r+PRS23ds=djK2GQ2SJb0g@mail.gmail.com>
Date: Thu, 10 Nov 2022 12:45:28 +0000
Cc: Bob Hinden <bob.hinden@gmail.com>, Internet Area <int-area@ietf.org>, int-ads@ietf.org, Eric Gray <eric.gray@ericsson.com>, liaison-coordination@iab.org, IANA <iana@iana.org>, draft-ietf-intarea-rfc7042bis@ietf.org
Message-Id: <C827C40F-0C03-421E-8BBF-2B9D02F0EC9B@gmail.com>
References: <CAF4+nEE5mO7d2Y31wprmOF_6c6E_r+PRS23ds=djK2GQ2SJb0g@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/Ta6P_wvfGmPXZy_Xtun9EbjCQD0>
Subject: Re: [Int-area] Procedure for obtaining Ethertypes
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2022 12:45:36 -0000

Don,

Adding a procedure describing how to obtain an Ethertype for IETF work seems reasonable to me as well.

Bob


> On Nov 10, 2022, at 12:24 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> 
> During the INTAREA WG meeting yesterday, there was a desire expressed
> to include in the rfc7042bis draft an explicit process, from the IETF
> side, for applying to the IEEE Registration Authority for an Ethertype
> assignment. This seems pretty reasonable. The rfc7042bis draft does
> include the IESG Statement requiring IESG approval before such
> applications but does not make it clear just who talks to who inside
> the IETF and who actually does the clerical work to apply to the IEEE
> Registration Authority for an Ethertype assignment after IESG
> approval.
> 
> Thinking about this, it seems to me that you want one point person who
> normally does the application process. This should be a position that
> has low turnover so that the person in that position is likely to have
> some experience doing this. The two possibilities that occur to me are
> (1) the IETF 802.1 Liaison (currently Eric Gray) or (2) the Expert for
> the IANA Informational Ethertype Registry (currently me). (I have been
> through the Ethertype assignment process for an IETF protocol several
> times.)
> 
> The IESG Statement (see
> https://www.ietf.org/about/groups/iesg/statements/ethertypes/)
> requires IESG approval and, as I recall, the last time this happened,
> after the IESG had approved, the IESG was unclear on what to do next
> but their first inclination was to tell IANA to do the application to
> the IEEE Registration Authority. This seems natural as IANA is who you
> would think of when it comes to assignments. And IANA maintains
> contact with their registry experts. While this probably doesn't
> matter at a practical level, considering the liaison alternative, the
> IETF does not seems to currently have a liaison to IEEE 802.1 while
> the IEEE Registration Authority is not at the IEEE 802.1 or the IEEE
> 802 level but rather at the IEEE level .
> 
> Any comments welcome but, based on the above, I'm inclined to draft
> some text based on the point person doing the clerical work of
> actually applying to the IEEE Registration Authority being the IANA
> Ethertype Informational Registry expert (actual Registry name "IEEE
> 802 Numbers"). Of course, whoever it is, they could have someone else
> do it on their behalf in any particular instance but they would be
> responsible to see that it gets done.
> 
> Thanks,
> Donald
> ===============================
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 2386 Panoramic Circle, Apopka, FL 32703 USA
> d3e3e3@gmail.com
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area