Hi, Yes, Eric has retired - really retired😊 We always hope to see a good friend/colleague once again, possibly with a different hat. IAB's Liaison Coordinators (Wes, Tommy, me) have been in discussions with Russ (IEEE Liaison) on having an IEEE802.1 replacement. As we all know, it is an important role (too much for Russ alone to coordinate), even with the IETF/IEEE802 Coordination Group (and Russ and Dorothy's great leadership). We are planning to send out next week a request for volunteers for the 802.1 Liaison role - so please consider if interested.
I think it is great to provide more explicit guidance in 7042bis. Both when I was an AD and Chair, it was always a bit difficult to understand the process. Always deferred to Russ and Eric. I've cc'd Russ (just in case he is not on the int-area list (I'm sure he is)). I know Don has already been informing the IETF/IEEE802 Coordination Group on the ieee-ietf-coord list about this update. I'd recommend proposing text and coordinating with Russ and the coordination group on the proposal. For those not familiar with IETF/IEEE802 Coordination Group, Russ gave an overview at this week's IABopen meeting: https://datatracker.ietf.org/meeting/115/materials/slides-115-iabopen-liaison-relationship-ietf-and-ieee-802-russ-housley-00 Thanks Donald (and all) for this work on a bis - Deborah -----Original Message----- From: Liaison-coordination <liaison-coordination-boun...@iab.org> On Behalf Of Robert Moskowitz Sent: Thursday, November 10, 2022 8:35 AM To: Bob Hinden <bob.hin...@gmail.com>; Donald Eastlake <d3e...@gmail.com> Cc: IANA <i...@iana.org>; Internet Area <int-area@ietf.org>; int-...@ietf.org; liaison-coordinat...@iab.org; draft-ietf-intarea-rfc7042...@ietf.org; Eric Gray <eric.g...@ericsson.com> Subject: Re: [Liaison-coordination] [Int-area] Procedure for obtaining Ethertypes 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 <d3e...@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://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/ethertypes/__;!!BhdT!jPK28UMpfoBdS92whRlmdT_MUD5E1UX-Yopud6TqZtMMERGr3dUEZ_tEwK4MGIuCE2cXv3HzhNc3sARKLc24$ >> ) >> 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 >> d3e...@gmail.com >> >> _______________________________________________ >> Int-area mailing list >> Int-area@ietf.org >> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/int-area__;!!BhdT!jPK28UMpfoBdS92whRlmdT_MUD5E1UX-Yopud6TqZtMMERGr3dUEZ_tEwK4MGIuCE2cXv3HzhNc3sLbwvNRo$ >> > > _______________________________________________ > Int-area mailing list > Int-area@ietf.org > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/int-area__;!!BhdT!jPK28UMpfoBdS92whRlmdT_MUD5E1UX-Yopud6TqZtMMERGr3dUEZ_tEwK4MGIuCE2cXv3HzhNc3sLbwvNRo$ > -- Liaison-coordination mailing list liaison-coordinat...@iab.org https://urldefense.com/v3/__https://www.iab.org/mailman/listinfo/liaison-coordination__;!!BhdT!jPK28UMpfoBdS92whRlmdT_MUD5E1UX-Yopud6TqZtMMERGr3dUEZ_tEwK4MGIuCE2cXv3HzhNc3sCYVWDhb$ _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
