Re: [ieee-ietf-coord] Coordination Gathering Needed in Prague?

ROBERT GROW <bobgrow@cox.net> Tue, 19 March 2019 00:13 UTC

Return-Path: <bobgrow@cox.net>
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 7BF6A126C87 for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 18 Mar 2019 17:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level:
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 4oWUmBl9OI6v for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 18 Mar 2019 17:13:14 -0700 (PDT)
Received: from fed1rmfepo103.cox.net (fed1rmfepo103.cox.net [68.230.241.145]) by ietfa.amsl.com (Postfix) with ESMTP id 41EBF1240D3 for <ieee-ietf-coord@ietf.org>; Mon, 18 Mar 2019 17:13:14 -0700 (PDT)
Received: from fed1rmimpo306.cox.net ([68.230.241.174]) by fed1rmfepo103.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20190319001313.IOPB4136.fed1rmfepo103.cox.net@fed1rmimpo306.cox.net> for <ieee-ietf-coord@ietf.org>; Mon, 18 Mar 2019 20:13:13 -0400
From: ROBERT GROW <bobgrow@cox.net>
X-CT-Class: Clean
X-CT-Score: 0.00
X-CT-RefID: str=0001.0A090202.5C903419.0012, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CT-Spam: 0
X-Authority-Analysis: v=2.3 cv=NuZljPVJ c=1 sm=1 tr=0 a=bOrxLfn96c7CisXCwCr9cw==:117 a=bOrxLfn96c7CisXCwCr9cw==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=o83nqyVRAAAA:8 a=pGLkceISAAAA:8 a=soKBErP5AAAA:8 a=I0CVDw5ZAAAA:8 a=48vgC7mUAAAA:8 a=8xm7-ZKtu0ulT4U37jgA:9 a=QNEV8edWHjSORJgr:21 a=6OLqPcb8tPO9rn86:21 a=QEXdDO2ut3YA:10 a=Od2VD5mNr3sA:10 a=i_peRNKcDZU-vJ4_dvIA:9 a=MwSiAnBJzmhAYrPo:21 a=wRECD4P7N-3-W10C:21 a=pwrRjrwz0qoc9u8u:21 a=_W_S_7VecoQA:10 a=HCcp_izDSj6DkKgPSDQm:22 a=YdXdGVBxRxTCRzIkH2Jn:22 a=w1C3t2QeGrPiZgrLijVG:22
X-CM-Score: 0.00
Authentication-Results: cox.net; auth=pass (PLAIN) smtp.auth=bobgrow@cox.net
Message-Id: <AA5AB9F0-4E7B-47B0-958C-9D9AFF9CE3AA@cox.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CE6FDF62-50DF-4DD7-AC39-958F9B21ADE8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 18 Mar 2019 17:13:11 -0700
In-Reply-To: <CAF4+nEGuSZBHjCx=xCTFQMNaB-J53NMCmimFWM-vhmEpx4UHLQ@mail.gmail.com>
Cc: ieee-ietf-coord@ietf.org
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
References: <8F6BA90D-0324-4094-ABAC-871BA0309496@vigilsec.com> <84400696-f0b4-0c6e-18b9-fefd60e72974@gmail.com> <B385BFE2-A09D-44D1-85FD-30254B97C7B6@akayla.com> <CAF4+nEGuSZBHjCx=xCTFQMNaB-J53NMCmimFWM-vhmEpx4UHLQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/1-JpHS-vCwtsOqQ1_deAIdp3ryo>
Subject: Re: [ieee-ietf-coord] Coordination Gathering Needed in Prague?
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: Tue, 19 Mar 2019 00:13:17 -0000

Alex:

As Donald mentioned, Ethertypes (also capitalized EtherTypes) are administered by the IEEE Registration Authority (https://standards.ieee.org/products-services/regauth/ethertype/index.html <https://standards.ieee.org/products-services/regauth/ethertype/index.html>).  The referenced web page also includes a link to the Ethertype public listing.  An applicant cannot request a specific Ethertype number.  There is no experimental Ethertype expressly assigned for vehicular protocols.

IEEE Std 802 defines Experimental Ethertypes, and those can be used for protocol development, but an assignment is required for general use once the protocol is ready for deployment.  The Experimental Ethertype also includes specification of the sub typing that is now preferred in protocols.  (If sub typing is not used as explained in IEEE Std 802, an equivalent mechanism with explanation will be required to receive an assignment, as will an explanation of why subtypes of an existing assignment can’t be used for the protocol.)

—Bob Grow, Chair, IEEE Registration Authority Committee


> On Mar 15, 2019, at 8:59 AM, Donald Eastlake <d3e3e3@gmail.com>; wrote:
> 
> Of course the IEEE Registration Authority is the authoritative source
> for Ethertype assignment information. See
> https://standards.ieee.org/products-services/regauth/index.html It is
> somewhat of a historic accident that there is an informational listing
> of historic and IETF relevant Ethertypes on the IANA web
> pages...Thanks,Donald=============================== Donald E.
> Eastlake 3rd   +1-508-333-2270 (cell) 1424 Pro Shop Court, Davenport,
> FL 33896 USA d3e3e3@gmail.com
> On Fri, Mar 15, 2019 at 11:29 AM Peter Yee <peter@akayla.com>; wrote:
>> 
>> Ethertype 0x8948 is already assigned (although not listed on the IANA's page for Ethertypes, which is not the definitive listing of Ethertypes).  If you have a need for an Ethertype, you should reference RFC 7042 (Section 3) and the IANA's IEEE 802 Numbers page (https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml)  for more information.  Donald Eastlake (primary) and Juan Carlos Zuniga (secondary) are the IANA-designated experts for Ethertypes.
>> 
>>                -Peter
>> 
>> On 3/15/19, 3:14 AM, "ieee-ietf-coord on behalf of Alexandre Petrescu" <ieee-ietf-coord-bounces@ietf.org on behalf of alexandre.petrescu@gmail.com>; wrote:
>> 
>> One of my collaborators (RSU manufacturer) asked me in private which
>> EtherType to use  other than the allocated 0x8947 for GeoNetworking, on
>> which to send CAM messages from car to Road-Side Units that use empty
>> GeoNetworking and BTP headers.
>> 
>> These are not IP messages, but are transmitted on IEEE 802.11 OCB.  They
>> do contain ETSI GeoNetworking headers but these headers are empty
>> because we dont trust their necessity.
>> 
>> We agreed to put such CAMs with empty GeoNetowrking headers present both
>> on cars and on Road-Side Units, we agreed to put at a particular 5.9GHz
>> channel, but we explore which EtherType to use.
>> 
>> Is there some 'trial' EtherType for vehicles, which would not disturb
>> others, be future proof, be available immediately (in the following
>> months).
>> 
>> I thought to suggest 0x8948 (the next after 0x8947) but I dont know.
>> 
>> Alex
>> 
>> Le 20/02/2019 à 20:53, Russ Housley a écrit :
>>> During the coordination call today, no one had a topic that needed a gathering in Prague.  Since some of you could not make the call, we wanted to ask the list before deciding that there was not a reason to get together.  If you know of a topic, please speak now.
>>> 
>>> Russ
>>> 
>>> _______________________________________________
>>> ieee-ietf-coord mailing list
>>> ieee-ietf-coord@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord
> 
> _______________________________________________
> ieee-ietf-coord mailing list
> ieee-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord