Re: [ipwave] ITU-R liaison statement 1686
Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 21 October 2020 19:55 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 2BD663A131D for <its@ietfa.amsl.com>; Wed, 21 Oct 2020 12:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.425
X-Spam-Level: *
X-Spam-Status: No, score=1.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NICE_REPLY_A=-0.247, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001, URI_DOTEDU=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 LATIedMk6HtG for <its@ietfa.amsl.com>; Wed, 21 Oct 2020 12:55:26 -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 2F4DA3A1318 for <its@ietf.org>; Wed, 21 Oct 2020 12:55:25 -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 09LJtNa5013997; Wed, 21 Oct 2020 21:55:23 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 28E282071D1; Wed, 21 Oct 2020 21:55:23 +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 1B2A7202C0E; Wed, 21 Oct 2020 21:55:23 +0200 (CEST)
Received: from [10.11.240.65] ([10.11.240.65]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 09LJtMSN005070; Wed, 21 Oct 2020 21:55:22 +0200
To: Russ Housley <housley@vigilsec.com>
Cc: its@ietf.org
References: <4725B596-F5FA-49F9-A312-BC40CD053F23@kuehlewind.net> <9af15ae85892d25b98fc6dda98a8851c@vigilsec.com> <CAPK2DexczsruB-PwP0VXk6eS89F1ZQitOEJEASB1hAraQJR8cw@mail.gmail.com> <eb8f818c-a246-099f-8de3-567bcbbc023e@gmail.com> <1c00cc5f-3b7e-ae37-6f2f-1c28f0c2d3a4@gmail.com> <0fcd17f5b58ea9249bfb97acd9894ffe@vigilsec.com> <bf630134-5830-d175-efbc-3dc330e7bc50@gmail.com> <ACC30712-CBA5-43B4-BF87-2B762894D1B5@vigilsec.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <6ab7d79a-25af-f8ae-280b-c66d88f87a38@gmail.com>
Date: Wed, 21 Oct 2020 21:55:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2
MIME-Version: 1.0
In-Reply-To: <ACC30712-CBA5-43B4-BF87-2B762894D1B5@vigilsec.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/its/nTzozbhgmvPqBFjbFtTDFNZFitk>
Subject: Re: [ipwave] ITU-R liaison statement 1686
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, 21 Oct 2020 19:55:28 -0000
Hi, Russ, Indeed the scope I wrote might be well beyond the scope of the WG. I just listed topics concerning me now. But I will not be responding to ITU-R liaison, also because it seems to request material rather from organizations. Alex Le 21/10/2020 à 19:56, Russ Housley a écrit : > Alex: > > This seems to be well beyond the scope of the IPWAVE WG. Perhaps > you should respond as an individual. > > Russ > > >> On Oct 20, 2020, at 8:22 AM, Alexandre Petrescu >> <alexandre.petrescu@gmail.com> wrote: >> >> >> >> Le 17/10/2020 à 17:17, housley@vigilsec.com a écrit : >>> Since it is from ITU-R, it is about spectrum. >> >> Well, the liaison statement asks this: "Working Party 5A kindly >> requests the interested external organizations to provide material >> on the description, architecture, applications, technologies, and >> operational scenarios of CAVs and the radiocommunication >> requirements for CAVs." >> >> This is a very broad request. I think it is much more than just >> spectrum requirements for CAVs. I think only their request of >> 'radiocommunication requirements for CAVs' might indeed relate to >> spectrum requirements. >> >> With respect to 'radiocommunication requirements for CAVs' we >> could list the following: - the use of the 5.9GHz band specific to >> DSRC as used in automated vehicles. Use IP on the control channel >> of this band. - the use of 3.5GHz band specific to 5G as used in >> demonstrations of tele-operation of automated shuttle, such as the >> October Stockholm demonstration made by Ericsson. >> >> With respect to 'description, architecture, applications, >> technologies and operation scenarios' we could provide a pointer >> to the Internet Draft titled 'IPv6 Wireless Access in Vehicular >> Environments (IPWAVE): Problem Statement and Use Cases'. >> >> With respect to just the 'operational scenarios' we can provide a >> few additional pointers to CAV-specific use-cases of communication >> technologies: - the 6G use-cases relating to vehicular networking >> (some such use cases are listed in the 6gip email list of IETF), - >> the ITU-T FG-NET2030 use-cases that relate to automated driving, - >> the recent ToD (Tele Operated Driving) use-case described by 5GAA. >> >> An additional possibility might be to provide a list of projects >> involving the use of communication systems in CAVs (Connected >> Automated Vehicles). >> >> Alex >> >> >>> Russ On 2020-10-17 04:37, Alexandre Petrescu wrote: >>>> (For information, the ISO TC204 'ITS' too is looking at >>>> creating, or enhancing, an 'ADCG' - Automated Driving Control >>>> Group. It is a group trying to oversee how to bring the >>>> different characteristics of work related to AD into the >>>> various WGs of that TC. They have started a document titled >>>> 'Terms of Reference' on which they might need feedback. This >>>> is not a liaison statement from ISO TC204, just a FYI.) Alex >>>> Le 17/10/2020 à 10:31, Alexandre Petrescu a écrit : >>>>> I think too it is a good idea to point to our I-D. But, >>>>> since the ITU-R liaison is about CAV (Connected and >>>>> Automated Vehicles), I think there would be advantageous to >>>>> point to particular places in the draft that make for >>>>> Connected and for Automated. For the Connected part it is >>>>> straightforward, because many communication protocols are >>>>> referred to in the I-D. For the Automated part, maybe the V2V >>>>> use-cases described in the I-D. Maybe other parts of the I-D >>>>> as well. Alex Le 17/10/2020 à 09:47, Mr. Jaehoon Paul Jeong a >>>>> écrit : >>>>>> Hi Russ, We can point out our IPWAVE Problem Statement and >>>>>> Use Cases Draft can be a good foundation for their work: >>>>>> https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-19 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >> >>>>>> >>>>>> <https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-19> >>>> Thanks. >>>>>> Best Regards, Paul On Sat, Oct 17, 2020 at 4:05 AM >>>>>> <housley@vigilsec.com <mailto:housley@vigilsec.com>> wrote: >>>>>> The ITU-R sent a liaison: >>>>>> https://datatracker.ietf.org/liaison/1686/ >>>>>> <https://datatracker.ietf.org/liaison/1686/> Does anyone >>>>>> think that the IPWAVE WG should reply? Russ >>>>>> _______________________________________________ its >>>>>> mailing list its@ietf.org <mailto:its@ietf.org> >>>>>> https://www.ietf.org/mailman/listinfo/its >>>>>> <https://www.ietf.org/mailman/listinfo/its> -- >>>>>> =========================== Mr. Jaehoon (Paul) Jeong, Ph.D. >>>>>> Associate Professor Department of Computer Science and >>>>>> Engineering Sungkyunkwan University Office: +82-31-299-4957 >>>>>> Email: jaehoon.paul@gmail.com >>>>>> <mailto:jaehoon.paul@gmail.com>, pauljeong@skku.edu >>>>>> <mailto:pauljeong@skku.edu> Personal Homepage: >>>>>> http://iotlab.skku.edu/people-jaehoon-jeong.php >>>>>> <http://cpslab.skku.edu/people-jaehoon-jeong.php> >>>>>> _______________________________________________ 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 >
- [ipwave] ITU-R liaison statement 1686 housley
- Re: [ipwave] ITU-R liaison statement 1686 Mr. Jaehoon Paul Jeong
- Re: [ipwave] ITU-R liaison statement 1686 Alexandre Petrescu
- Re: [ipwave] ITU-R liaison statement 1686 Alexandre Petrescu
- Re: [ipwave] ITU-R liaison statement 1686 housley
- Re: [ipwave] ITU-R liaison statement 1686 Alexandre Petrescu
- Re: [ipwave] ITU-R liaison statement 1686 Russ Housley
- Re: [ipwave] ITU-R liaison statement 1686 Alexandre Petrescu
- Re: [ipwave] ITU-R liaison statement 1686 Alexandre Petrescu
- Re: [ipwave] ITU-R liaison statement 1686 Mr. Jaehoon Paul Jeong
- Re: [ipwave] ITU-R liaison statement 1686 Russ Housley
- Re: [ipwave] ITU-R liaison statement 1686 Abdussalam Baryun