Re: [ipwave] Update about advancement of requirements for LTE-V2X V2V Safety Communications, SAE J3161/1

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 26 April 2022 19:51 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6928C1D18E9 for <its@ietfa.amsl.com>; Tue, 26 Apr 2022 12:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.185
X-Spam-Level:
X-Spam-Status: No, score=-6.185 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-1.857, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 RwnQG6KgOpxi for <its@ietfa.amsl.com>; Tue, 26 Apr 2022 12:51:19 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 B5517C1D18E3 for <its@ietf.org>; Tue, 26 Apr 2022 12:51:18 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 23QJpDWY031054; Tue, 26 Apr 2022 21:51:13 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 39A4621136F; Tue, 26 Apr 2022 21:51:13 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 2C8E72111DA; Tue, 26 Apr 2022 21:51:13 +0200 (CEST)
Received: from [10.11.240.85] ([10.11.240.85]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 23QJpCtj014255; Tue, 26 Apr 2022 21:51:12 +0200
Message-ID: <a70bd415-8ee4-74c8-a5ad-73edf6cd2867@gmail.com>
Date: Tue, 26 Apr 2022 21:51:13 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
Content-Language: fr
To: dickroy@alum.mit.edu, 'IPWAVE WG' <its@ietf.org>
References: <d2387493-e398-77b6-25ee-4a192cb42763@gmail.com> <88B542212C694AC799730E42CF44F87A@SRA6> <4d035a5b-21a3-c248-91a8-fd4d5cfd4e08@gmail.com> <1F3BCFAEB5B34C82A62A2ADB630177CF@SRA6>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <1F3BCFAEB5B34C82A62A2ADB630177CF@SRA6>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/tQn9RPpGXo7_aXKFIv9gl-OV3Q4>
Subject: Re: [ipwave] Update about advancement of requirements for LTE-V2X V2V Safety Communications, SAE J3161/1
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2022 19:51:22 -0000


Le 26/04/2022 à 21:46, Dick Roy a écrit :
> -----Original Message-----
> From: Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com]
> Sent: Tuesday, April 26, 2022 12:24 PM
> To: dickroy@alum.mit.edu; 'IPWAVE WG'
> Subject: Re: [ipwave] Update about advancement of requirements for 
> LTE-V2X V2V Safety Communications, SAE J3161/1
> 
> Le 21/04/2022 à 19:54, Dick Roy a écrit :
> 
>> IP networking is supported/possible,
> 
> IP in common parlance by many here means IPv6.
> 
> */[RR] All versions of IP are "supported"

There is one thing to be supported for smartphone, and another thing to 
be supported for cars.

Currently, LTE does not support IP (IPv6 that is) for cars.

Alex

  in the sense that the layer 1
> and 2 standards (DSRC/G5 or LTE Rel 14 V2X) do not specify anything 
> about the layer 3 protocols that "shall" or "shall not" be used, and 
> both have means for indicating what layer 3 protocol is being used. 
> DSRC/G5 (IEEE 109.3 and friends) uses the standard ethertype identifier 
> and can support ANY layer 3 protocol w/ an associated ethertype. In the 
> case of LTE, it’s a kludge, but so is everything else about LTE V2X so 
> it's neither news nor surprising and only “IP and non-IP” are 
> supported.  [The IP-related info in the service 
> announcement/advertisement message is not relevant here.] /*
> 
> *//*
> 
> However, there is no IPv6 in cars.
> 
> */[RR] Not true.  Aftermarket devices in cars today in Europe and the US 
> have IPv6 stacks w.p.1. … just because there is no IPv6 in IVNs does not 
> mean there is no IPv6 in  cars./*
> 
> Because of that, I think there might be a problem in stating that IP is
> 
> supported/possible in LTE-V2X when there is actually no such thing as IP
> 
> on LTE in Vehicles (provided, again, that by IP we mean IPv6).
> 
> */[RR] There is no problem.  See above./*
> 
> *//*
> 
> */RR/*
> 
> Alex
> 
>    however it is important to note
> 
>> that there is NO layer 2 addressing so every LTE-V2X transmission  is a
> 
>> broadcast (at layer 2). Just one of the many kludges required when
> 
>> pounding a square peg in to a round hole! J
> 
>> 
> 
>> RR
> 
>> 
> 
>>  ------------------------------------------------------------------------
> 
>> 
> 
>> *From:*its [mailto:its-bounces@ietf.org] *On Behalf Of *Alexandre  Petrescu
> 
>> *Sent:* Thursday, April 21, 2022 7:56 AM
> 
>> *To:* IPWAVE WG
> 
>> *Subject:* [ipwave] Update about advancement of requirements for  LTE-V2X
> 
>> V2V Safety Communications, SAE J3161/1
> 
>> 
> 
>> Hi, IPWAVE,
> 
>> 
> 
>> In March 2022, the SAE has finished the document SAE J3161/1  titled
> 
>> "On-Board System Requirements for LTE-V2X V2V Safety  Communications".
> 
>> 
> 
>> The document contents is not cheap, but from the title it can be 
> 
>> presumed that it formulates requirements for the use of LTE-V2X in  a V2V
> 
>> manner between vehicles or to pedestrians. 
> 
>> https://www.sae.org/standards/content/j3161/1_202203 
> 
>> <https://www.sae.org/standards/content/j3161/1_202203>
> 
>> 
> 
>> This interesting advancement might lead to a need of an IP-based 
> 
>> inter-vehicle communications system.
> 
>> 
> 
>> Some slides about this advancement were presented at recent ITU  C-ITS
> 
>> online meeting and at ISO/TC 204 online meeting.
> 
>> 
> 
>> Alex
> 
>> 
>