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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 17 July 2019 14:56 UTC

Return-Path: <alexandru.petrescu@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 193BD1206C0 for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 17 Jul 2019 07:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham 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 mTEAmHhNHrgP for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 17 Jul 2019 07:56:31 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 CDB281204ED for <ieee-ietf-coord@ietf.org>; Wed, 17 Jul 2019 07:56:30 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x6HEuQec038237; Wed, 17 Jul 2019 16:56:26 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CC63D204DE7; Wed, 17 Jul 2019 16:56:26 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BC97F204DBA; Wed, 17 Jul 2019 16:56:26 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x6HEuQQV013887; Wed, 17 Jul 2019 16:56:26 +0200
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: ieee-ietf-coord@ietf.org, Peter Yee <peter@akayla.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> <80d403d5-0e2b-3bd7-4a13-129f03013d84@gmail.com> <CAF4+nEGKSP1QdgHKxOryTKTebtJT7y4zS6jvo4zMe7NUdR4dTw@mail.gmail.com>
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <18558887-4c57-7479-36a4-0a64022fe173@gmail.com>
Date: Wed, 17 Jul 2019 16:56:26 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CAF4+nEGKSP1QdgHKxOryTKTebtJT7y4zS6jvo4zMe7NUdR4dTw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/DiRZwGSd6AM2oq0WU89tx5fb9tU>
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: Wed, 17 Jul 2019 14:56:39 -0000

Donald,

For information today we sent the first CAM over 802.11-OCB with empty 
GeoNetworking/BTP headers, with EtherType 0x88B5.  This is in agreement 
with RSU manufacturer (the one who receives that CAM).

The problem we are trying to solve with this solution is the following: 
when the car sends a CAM with empty GeoNet/BTP headers near the RSU it 
breaks the RSU.  We think that breaks because the V2X stack on the RSU 
expects filled GeoNetworking/BTP headers when the EtherType is 0x8947 
(called 'GeoNetworking').

So we will try this new solution in the street and see whether it works 
better.

Alex

Le 04/04/2019 à 17:05, Donald Eastlake a écrit :
> Hi Alex,
> 
> I would say you should not use 0xFFFF. IEEE standards are clear that 
> 0xFFFF is not a valid Ethertype.
> 
> I suggest you use 0x88B5 or 0x88B6, the Ethertypes reserved for local 
> experimentation.
> 
> By the way, IEEE traditionally waives the fee when Ethertypes are 
> assigned for standards use but, as far as I know, there is no facility 
> for "temporary" Ethertype assignments.
> 
> Thanks,
> Donald
> ===============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   1424 Pro Shop Court, Davenport, FL 33896 USA
> d3e3e3@gmail.com <mailto:d3e3e3@gmail.com>
> 
> 
> On Thu, Apr 4, 2019 at 4:55 AM Alexandru Petrescu 
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
> 
>     I propose I use 0xFFFF for now for CAMs over empty BTP and
>     GeoNetworking.
> 
>     I suppose 0xffff is not used, as it is the last one.
> 
>     I can not plan for budget for it at this time, but I need to use it in
>     the street.  I can provide the location if needed.
> 
>     I want to thank you for the clarification.
> 
>     The blocking point to further exploring is the apparent necessity of
>     Registration Fee of cca 3k usd.  It is not the amount, but it is the
>     potential risk of temporary  use.  It's hard to pay money just for a
>     few
>     months of use.  I dont know whether it will be succesful any further to
>     warrant spending, for now.
> 
>     Alex
> 
>     Le 15/03/2019 à 16:59, Donald Eastlake a écrit :
>      > 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 <mailto:d3e3e3@gmail.com>
>      > On Fri, Mar 15, 2019 at 11:29 AM Peter Yee <peter@akayla.com
>     <mailto: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
>     <mailto:ieee-ietf-coord-bounces@ietf.org> on behalf of
>     alexandre.petrescu@gmail.com <mailto: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 <mailto:ieee-ietf-coord@ietf.org>
>      >>> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord
>      >
>