Re: [Int-area] Procedure for obtaining Ethertypes
Robert Moskowitz <rgm-ietf@htt-consult.com> Thu, 10 November 2022 13:36 UTC
Return-Path: <rgm-ietf@htt-consult.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 C3CB0C1522DF; Thu, 10 Nov 2022 05:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level:
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, 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=unavailable autolearn_force=no
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 JfjOQ_CasTxz; Thu, 10 Nov 2022 05:36:27 -0800 (PST)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2563C152575; Thu, 10 Nov 2022 05:36:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 3F32E624D4; Thu, 10 Nov 2022 08:35:50 -0500 (EST)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id CyTkuRhmPFjF; Thu, 10 Nov 2022 08:35:42 -0500 (EST)
Received: from [31.133.132.136] (dhcp-8488.meeting.ietf.org [31.133.132.136]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id DE49260944; Thu, 10 Nov 2022 08:35:35 -0500 (EST)
Message-ID: <5cb52325-98ec-fb41-d504-e96ff62770f4@htt-consult.com>
Date: Thu, 10 Nov 2022 08:35:27 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1
To: Bob Hinden <bob.hinden@gmail.com>, Donald Eastlake <d3e3e3@gmail.com>
Cc: IANA <iana@iana.org>, Internet Area <int-area@ietf.org>, int-ads@ietf.org, liaison-coordination@iab.org, draft-ietf-intarea-rfc7042bis@ietf.org, Eric Gray <eric.gray@ericsson.com>
References: <CAF4+nEE5mO7d2Y31wprmOF_6c6E_r+PRS23ds=djK2GQ2SJb0g@mail.gmail.com> <C827C40F-0C03-421E-8BBF-2B9D02F0EC9B@gmail.com>
Content-Language: en-US
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
In-Reply-To: <C827C40F-0C03-421E-8BBF-2B9D02F0EC9B@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/LC1c8_3e2mrmRO8plu_Xhp9EUd4>
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 13:36:27 -0000
Since, in a sense, this is targetted at me to be the lab rat for this, I will read all this over carefully to see what mess I am getting myself into, :) Bob On 11/10/22 07:45, Bob Hinden wrote: > 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 > > _______________________________________________ > Int-area mailing list > Int-area@ietf.org > https://www.ietf.org/mailman/listinfo/int-area
- [Int-area] Procedure for obtaining Ethertypes Donald Eastlake
- Re: [Int-area] Procedure for obtaining Ethertypes Bob Hinden
- Re: [Int-area] Procedure for obtaining Ethertypes Wassim Haddad
- Re: [Int-area] Procedure for obtaining Ethertypes Robert Moskowitz
- Re: [Int-area] [Liaison-coordination] Procedure f… BRUNGARD, DEBORAH A