Re: [ipwave] Feedback from ITU-R CITS about IP and cellular for vehicular networks

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 15 October 2021 12:43 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 0545B3A074B for <its@ietfa.amsl.com>; Fri, 15 Oct 2021 05:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.667
X-Spam-Level:
X-Spam-Status: No, score=0.667 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=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 86Ak5NS-Apj0 for <its@ietfa.amsl.com>; Fri, 15 Oct 2021 05:43:06 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 2DB793A06E7 for <its@ietf.org>; Fri, 15 Oct 2021 05:43:05 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 19FCgxUd000431; Fri, 15 Oct 2021 14:42:59 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D00C920476A; Fri, 15 Oct 2021 14:42:59 +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 C1644200C1E; Fri, 15 Oct 2021 14:42:59 +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 19FCgx2p014891; Fri, 15 Oct 2021 14:42:59 +0200
To: dickroy@alum.mit.edu, its@ietf.org
References: <8d49b3c9-f0cc-6896-b906-b7c4b92367af@gmail.com> <1650abc2-8008-4b23-c0c6-a3c32e497edd@gmail.com> <58EA7A21BDF94709893836420F54177A@SRA6> <ebf84b99-faef-93ef-5d8b-b2825fa3ffe5@gmail.com> <8D942722D930465FAB7B3E59AEFB8E03@SRA6>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <f5c84db9-77d4-2b70-08e0-b0c8a93fbfed@gmail.com>
Date: Fri, 15 Oct 2021 14:42:58 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <8D942722D930465FAB7B3E59AEFB8E03@SRA6>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/fuSlD1IrpDhkcjMAgkCz15W0RVA>
Subject: Re: [ipwave] Feedback from ITU-R CITS about IP and cellular for vehicular networks
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: Fri, 15 Oct 2021 12:43:11 -0000


Le 05/10/2021 à 17:24, Dick Roy a écrit :
> -----Original Message----- From: its [mailto:its-bounces@ietf.org]
> On Behalf Of Alexandre Petrescu Sent: Tuesday, October 5, 2021 5:29
> AM To: dickroy@alum.mit.edu; its@ietf.org Subject: Re: [ipwave]
> Feedback from ITU-R CITS about IP and cellular for vehicular
> networks
> 
> [...]
> 
>> There might be other problems with IP on C-V2X on a car-to-car
> 
>> without base station scenario.
> 
>> 
> 
>> */[RR] Like there being NO layer-2 addressing in C-V2X …  ONLy
> 
>> broadcasts! Just imagine how efficient that will be! /*
> 
> It sounds as if one has read a specification of C-V2X and has seen 
> the
> 
> C-V2X headers and in these headers there are no addresses.
> 
> */[RR] yup! C-V2X can ONLy be used for broadcasts in the US! When
> one is being manipulated for corporate aggrandizement, it is wise to
> do one’s homework. Yes it involves effort, effort which many are 
> unfortunately not willing to expend so I guess they’ll just have to 
> live with the consequences, consequences which I am positive they
> are going to deeply regret having to suffer through. They can not
> say that they haven’t been warned however, so it’s really their own 
> fault. /*
> 
> Can I see that?
> 
> */[RR] Sure can.  Just read the 3GPP LTE Rel14 (cf. mode 3 and mode
> 4 PC5 sidelink) specs and J3161 (which is not available to you yet
> of course) and you will see there are NO layer-2 addresses.  There is
> a 24-bit control field in the MAC header which is useless without an
>  eNodeB so there have been attempts to use it for other purposes.
> The Chinese use it to encode a hash of the ITS-AID (brilliant!) and
> the US just populates it with random numbers (which have to tumble
> with all the other immutable fields for pseudonymity!). It gets even 
> better … ^(((((/*
> 
> *//*

Richard,

You are helping in a sense, but still it is confusing.

Let me be straight.

If you think that C-V2X is an invisible document to me (J3161) then of
course I can not even dream to work on it.  Note that it might be that I
might ask a kind soul to show it to me for standardisation purposes; if
the request is strong enough it might even become public officially.
But that is speculation.

Still, if C-V2X J3161 is invisible then one can try to tell back to ITU
that their strong invitation to develop a document for IPv6 for C-V2X
can not succeed because of that J3161 unavailability.  And we end there.

If on another hand you think that 3GPP LTE Rel14 cf. mode 3 and mode 4
can be equivalent to 'C-V2X' then we can work on that, because the specs
are available openly.  Here we might struggle with other issues
that I will raise when necessary, but it might be workable.

So, the basic question is this: what is 'C-V2X'?  Is 'C-V2X' a set of
3GPP documents or a set of SAE documents?

Alex

> 
> */RR /*
> 
> Alex
> 
>> 
> 
>> Alex
> 
>> 
> 
>> Le 04/10/2021 à 11:52, Alexandre Petrescu a écrit :
> 
>> 
> 
>>> Hi, IPWAVErs,
> 
>> 
> 
>>> 
> 
>> 
> 
>>> I gave a brief presentation of the IPWAVE WG, RFC8691 and
> 
>>> Vehicular
> 
>> 
> 
>>> Networks I-D to the ITU CITS 'Collaboration on ITS Standards', 
>>> in
> 
>> 
> 
>>> September, 2021.
> 
>> 
> 
>>> 
> 
>> 
> 
>>> This is the feedback I received:
> 
>> 
> 
>>> 
> 
>> 
> 
>>> Bring the cellular kind of work, like  IP-over-cellular, in
> 
>> 
> 
>>> IPWAVE WG.  This request is so  because:
> 
>> 
> 
>>> - because China efforts on cellular and because
> 
>> 
> 
>>> USA FCC  regulation changes at 5.9GHz to include
> 
>> 
> 
>>> C-V2X  ('C'==cellular).
> 
>> 
> 
>>> - because at ETSI it  is thought that it is easy
> 
>> 
> 
>>> to do IP  over any access layer, be it 802.11-OCB
> 
>> 
> 
>>> or a  cellular kind of link layer.
> 
>> 
> 
>>> 
> 
>> 
> 
>>> What do you think?
> 
>> 
> 
>>> 
> 
>> 
> 
>>> Alex
> 
>> 
> 
>>> 
> 
>> 
> 
>>> _______________________________________________
> 
>> 
> 
>>> its mailing list
> 
>> 
> 
>>> its@ietf.org
> 
>> 
> 
>>> https://www.ietf.org/mailman/listinfo/its
> 
>> 
> 
>> _______________________________________________
> 
>> 
> 
>> its mailing list
> 
>> 
> 
>> its@ietf.org
> 
>> 
> 
>> https://www.ietf.org/mailman/listinfo/its
> 
>> 
> 
> _______________________________________________
> 
> its mailing list
> 
> its@ietf.org
> 
> https://www.ietf.org/mailman/listinfo/its
>