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

<Dirk.von-Hugo@telekom.de> Wed, 17 April 2019 12:33 UTC

Return-Path: <Dirk.von-Hugo@telekom.de>
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 6F6C0120359 for <its@ietfa.amsl.com>; Wed, 17 Apr 2019 05:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.289
X-Spam-Level:
X-Spam-Status: No, score=-4.289 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 pKTguWgzAzmJ for <its@ietfa.amsl.com>; Wed, 17 Apr 2019 05:33:00 -0700 (PDT)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (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 3136F120357 for <its@ietf.org>; Wed, 17 Apr 2019 05:32:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1555504380; x=1587040380; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=xUOZd87xCCorNAcnZ3SSqEjEH/CBm+vvBYJVD6GucmU=; b=ndwaDT9YEc5Z4mYhihoa1OZKr78KHkMrEEpEs3SaTmZqZbUH/R7pCfBr L+1QV8uftNelDnK66BVZpwU3KA/Zyt7dqCBORX79oDUpx90Yo2ZfNWc9o s8p0rOfP/xTHZmKSWP8j2A7kKrKLdrizSRY0RkDQ7QHmTse3uP+X45TYC EPOvoxqzJC0424S2K1eIkbnzUwoxELeq3j4Urlpy6c3Ipl+b0ubb7btTu Fh5XO1DmTW1/ar0pqGJvER4UTjTc+HtdTHjkwpxqjJPH7EIl/0bqPJC7c ck0A+3/69mLdqfKp/CpQHV8zb6hQzir26g9L12xE39xNSxciiAXdPkZNI g==;
Received: from qdec94.de.t-internal.com ([10.171.255.41]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Apr 2019 14:32:57 +0200
X-IronPort-AV: E=Sophos;i="5.60,361,1549926000"; d="scan'208,217";a="406905099"
X-MGA-submission: MDFsf4U6VGh0GN7ATcWugqFHklEvsh2o2lVz+9dW8B4Cz0088t3Ma7+2pUbMBEkrsiYaZtIvZGP1qJl+n4MhNMGHgA/1/uq3BxTc3IjdCht/QZaoD1BCyfskVjNgz4Oql0frpZljiGSa3TyzMjwZ4mCtbmP0syJ8p9DpHgI6j2MQ4A==
Received: from he101947.emea1.cds.t-internal.com ([10.169.118.83]) by QDEC97.de.t-internal.com with ESMTP/TLS/AES256-SHA; 17 Apr 2019 14:32:29 +0200
Received: from HE105664.EMEA1.cds.t-internal.com (10.169.118.61) by HE101947.emea1.cds.t-internal.com (10.169.118.83) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 17 Apr 2019 14:32:29 +0200
Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105664.EMEA1.cds.t-internal.com (10.169.118.61) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 17 Apr 2019 14:32:29 +0200
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.17) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 17 Apr 2019 14:32:25 +0200
Received: from LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE (10.158.167.18) by LEXPR01MB0670.DEUPRD01.PROD.OUTLOOK.DE (10.158.167.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.19; Wed, 17 Apr 2019 12:32:28 +0000
Received: from LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE ([fe80::2c14:6934:c317:5689]) by LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE ([fe80::2c14:6934:c317:5689%7]) with mapi id 15.20.1792.021; Wed, 17 Apr 2019 12:32:28 +0000
From: Dirk.von-Hugo@telekom.de
To: alexandre.petrescu@gmail.com, its@ietf.org
Thread-Topic: [ipwave] LTE-V2X term in Problem Statement document
Thread-Index: AQHU9Q9XNNITxzOxgUewnZpGGFTaOqZAP3dA
Date: Wed, 17 Apr 2019 12:32:28 +0000
Message-ID: <LEXPR01MB06697DF790A19AEBC7E7E4D2D1250@LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE>
References: <abfbf312-be3c-c957-d58e-67b141697a14@gmail.com>
In-Reply-To: <abfbf312-be3c-c957-d58e-67b141697a14@gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Dirk.von-Hugo@telekom.de;
x-originating-ip: [212.201.104.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2feeeff3-e232-43cd-0966-08d6c330c0f9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600140)(711020)(4605104)(2017052603328)(7193020); SRVR:LEXPR01MB0670;
x-ms-traffictypediagnostic: LEXPR01MB0670:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <LEXPR01MB0670BF5087E5B7510C54C8E1D1250@LEXPR01MB0670.DEUPRD01.PROD.OUTLOOK.DE>
x-forefront-prvs: 0010D93EFE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39860400002)(376002)(136003)(346002)(366004)(189003)(199004)(97736004)(6246003)(236005)(86362001)(106356001)(9686003)(478600001)(66066001)(53936002)(55016002)(74482002)(8936002)(2501003)(105586002)(75402003)(6306002)(54896002)(606006)(72206003)(966005)(33656002)(14454004)(2906002)(790700001)(256004)(3846002)(316002)(71190400001)(71200400001)(68736007)(6116002)(7736002)(76176011)(102836004)(81156014)(446003)(5660300002)(186003)(476003)(52396003)(26005)(7696005)(110136005)(81166006)(53546011)(8676002)(229853002)(486006)(11346002); DIR:OUT; SFP:1101; SCL:1; SRVR:LEXPR01MB0670; H:LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: TDrdXYYRP28hH+R9RmdeIyCaO6q9PRqoriSv04ib4qgiLnbD0Dkt+RP3ung1NTlyLLYykasnwoP7HZa0tmUKTjRB3FAWs+mu4jnIIhlr1t6tbzK3Nhm98LNLito/jpm/Nf1A1NWp/TGSSj8L3dj2Zcmzap3npRy2lCHK8ceOqcyo4utVWFdVW7e3ZxCESET9DGrnaBnNPTa0Yb7rnXsJbP49N/pi4jjiGTtOdimyEtrAFNw7n1c9iABoAGzujEZPlsKNuZ0YpY8/fqOEif8WXpJ8BL3Y9rjvBaDWXt/HXItVzYQuTqFPiXmVr/meGibgQUoA5TIomKt+QeJTyJrSvk3ZViOsRAzVDdfM7d+r2qIgdGa51jKkhN28FJ6rYvozO2s2p5Yx7iFzIE37M7e6HUcs4k2pIcqsVXzu50/PmiE=
Content-Type: multipart/alternative; boundary="_000_LEXPR01MB06697DF790A19AEBC7E7E4D2D1250LEXPR01MB0669DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2feeeff3-e232-43cd-0966-08d6c330c0f9
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Apr 2019 12:32:28.1745 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEXPR01MB0670
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/pB33ldCSFqF_3Sj0CiHJ1QZkVxw>
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:33:03 -0000

Hi Alex,
I strongly agree with you that we need a precise definition on what we mean with cellular V2X (often denoted as C-V2X in general – so covering LTE and 5G/NR) – especially since – as you correctly pointed out - 3GPP has none such official definition as LTE-V2X or NR-V2X .

However when defining LTE-V2X we should be aware that there are two different modes of operation for V2X communication in 3GPP cellular systems (as also described in Annex A.5 of PS document https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-08).

E.g. according to 3GPP TR 21.914 giving a Release 14 (i.e. LTE) Description and Summary of Rel-14 Work Items, but similarly also for 5G/NR or Rel. 15 and higher (here in still draft TR 21.915) the modes of operation are described as

-          Direct V2X communication between UEs over a 3GPP sidelink (PC5 interface)

-          V2X communication over LTE-Uu interface (i.e. via base stations / eNBs)

In addition there are 2 different modes for PC5/sidelink:

-          in coverage of cellular system with LTE assistance

-          out of coverage: ad-hoc mode w/o assistance … very similar to OCB.

So I would recommend to specify more exactly what we have in mind.

LTE-V2X: the transmission of ETSI CAM and DENM messages over IP over a cellular link such as 3GPP 4G – both via base station and directly between vehicles

Or more general:

C-V2X: the transmission of ETSI CAM and DENM messages over IP over a cellular link such as 3G, 4G and successors – both in infrastructure mode (via base station / Uu interface) and ad-hoc mode (direct link / sidelink interface) if available [since sidelink is only specified for 4G/5G]

Or one may even reflect differentiation between those modes in the acronym (which I would not recommend here being not in scope for this document)

Just my 2 cents
Kind regards
Dirk

From: its <its-bounces@ietf.org> On Behalf Of Alexandre Petrescu
Sent: Mittwoch, 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