Re: [ipwave] LTE-V2X term in Problem Statement document

Jérôme Härri <jerome.haerri@eurecom.fr> Wed, 17 April 2019 12:46 UTC

Return-Path: <jerome.haerri@eurecom.fr>
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 EF6F81200DF for <its@ietfa.amsl.com>; Wed, 17 Apr 2019 05:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.91
X-Spam-Level:
X-Spam-Status: No, score=-0.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 PohYplS5DDxu for <its@ietfa.amsl.com>; Wed, 17 Apr 2019 05:46:11 -0700 (PDT)
Received: from smtp.eurecom.fr (smtp.eurecom.fr [193.55.113.210]) by ietfa.amsl.com (Postfix) with ESMTP id 0F8941200B2 for <its@ietf.org>; Wed, 17 Apr 2019 05:46:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.60,362,1549926000"; d="scan'208,217";a="9936518"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago1i.eurecom.fr with ESMTP; 17 Apr 2019 14:46:09 +0200
Received: from xerus29 (unknown [192.168.200.6]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by monza.eurecom.fr (Postfix) with ESMTPSA id 9FA2337B9; Wed, 17 Apr 2019 14:46:09 +0200 (CEST)
From: Jérôme Härri <jerome.haerri@eurecom.fr>
To: 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>, its@ietf.org
References: <abfbf312-be3c-c957-d58e-67b141697a14@gmail.com>
In-Reply-To: <abfbf312-be3c-c957-d58e-67b141697a14@gmail.com>
Date: Wed, 17 Apr 2019 14:46:09 +0200
Organization: EURECOM
Message-ID: <005c01d4f51b$8815f710$9841e530$@eurecom.fr>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005D_01D4F52C.4BA13810"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ77LBrwb839vTeo9AqYtlEbSGD0aTyUYxA
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/8iKmv1LXvNdtI57diZOn2WJf8XU>
Subject: Re: [ipwave] LTE-V2X term in Problem Statement document
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 17 Apr 2019 12:46:14 -0000

Hi Alex, All,

 

Good point…we indeed really need to avoid multiple acronyms.

 

One aspect worth mentioning is that there is no ‘official’ naming for what we try to indicate in 3GPP. LTE_V2X is just a WI name, which is an internal denomination (a bit when you are in a IEEE PAR and you have a working title, NGV instead of now 11BD). Of course, that is as far the only ‘one-term’ does it all to indicate this. But I would also suggest not to simply use this term, as it implies many unclear aspects:

1)      There are other work items on V2X, which actually do not use the ‘_’, e.g. eV2X, eV2XARC, V2XIMP etc..

2)      This WI no longer exist per say (as created in 2016)..and never produced a specific standard (by itself…, which would have taken the name)….it has been split in various other WIs, like LTE_V2X-Core, LTE_V2X-Perf, etc…

3)      V2X Slidelink

4)      V2X Uu (V2X Uu is not per say part of the WI LTE_V2X), but I suspect that IETF will include this as well.

5)      V2X Direct Communication (different from V2X Discovery)

6)      3GPP generally defines”V2X Services”…

7)      If we refer to horizontal communication, Sidelink is most likely used…but transparently includes D2D and V2X as these are configuration of the former. 

8)      5GAA uses C-V2X (taken from a US proposal, as the US do not use the term LTE, and prefer Cellular ‘whatever’

9)      ETSI/C2C uses LTE-V2X (here, as there was nothing to actually refer to…)

10)   Even found names such as LTE-V, or LTE short range (LTE Sidelink), LTE long range (LTE Uu)

 

So, my point is: I do not think there is one ‘term’…so, there should be a  decision at IETF to commonly use one, whatever it is, but having a section describing that it refers to (and linking to all other namings). 

Considering that 3GPP does not really has one (or only one), let’s review what is there:

·         SAE uses  (Cellular V2X, would suggest to avoid this, as this is generally not accepted in EU norms…as LTE V2X mode 4 is far from being ‘cellular’),  

·         ISO CALM uses LTE-V2X (ISO/FDIS 17515-3 Intelligent transport systems -- Evolved-universal terrestrial radio access network -- Part 3: LTE-V2X, https://www.iso.org/obp/ui/#iso:std:iso:17515:-3:dis:ed-1:v1:en) 

·         ETSI uses LTE-V2X (future EN (European Norm) 304 613, or the publicly available TS 103 613)…as the term has been used for much more time that IETF…, 

·         IEEE 1609.3 – I could not find a reference…but they might in the update cycle..

 

So, to be coherent between standards (ETSI, IEEE, SAE and ISO, considering we cannot refer to a standard in 3GPP having a single simple acronym, as far as I know) and common literature. I would suggest to use LTE-V2X as general term, but if LTE_V2X is selected, that is OK as well…we should just explain why and cycle other terms to avoid confusion…

 

My two cents,


BR,

 

Jérôme

 

 

 

From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre Petrescu
Sent: Wednesday 17 April 2019 13:18
To: its@ietf.org
Subject: [ipwave] LTE-V2X term in Problem Statement document

 

Hi IPWAVErs,

The IPWAVE Problem Statement document uses the term 'LTE-V2X' at one point. ("e.g., IEEE 802.11-OCB and LTE-V2X")

I would like to suggest to make a careful definition of the term 'LTE-V2X'.

One would expect the term 'LTE-V2X' to be defined precisely at 3GPP or similar.  But that is not the case.  The 3GPP document that is closest to this term is RP-161298, publicly available, defines the term 'LTE_V2X' (remark underscore '_', instead of dash '-').

I suggest the addition of the following term in the Problem Statement draft:

LTE-V2X: the transmission of ETSI CAM and DENM messages over IP over a cellular link such as 3G, 4G and successors.

Alex