Re: [Tm-rid] Review of draft-drip-arch-02 w.r.t. RFC6973, RFC8280 and other

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 09 July 2020 16:04 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: tm-rid@ietfa.amsl.com
Delivered-To: tm-rid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360F13A0D19 for <tm-rid@ietfa.amsl.com>; Thu, 9 Jul 2020 09:04:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.671
X-Spam-Level:
X-Spam-Status: No, score=0.671 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, 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] 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 17Xf3eh0_TEb for <tm-rid@ietfa.amsl.com>; Thu, 9 Jul 2020 09:04:53 -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 BD6D53A0CFA for <tm-rid@ietf.org>; Thu, 9 Jul 2020 09:04:52 -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 069G4mOT007589; Thu, 9 Jul 2020 18:04:48 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0407B207776; Thu, 9 Jul 2020 18:04:48 +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 E797F2012E2; Thu, 9 Jul 2020 18:04:47 +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 069G4lVH002410; Thu, 9 Jul 2020 18:04:47 +0200
To: "Da Silva, Saulo" <Sdasilva@icao.int>, Robert Moskowitz <rgm@labs.htt-consult.com>
Cc: "tm-rid@ietf.org" <tm-rid@ietf.org>
References: <1bebf5b1-1fa5-6902-5bb7-9ec3582e6d9a@andersdotter.cc> <2990FBF0-FCB0-49CE-8F4B-BF5111CE5D57@tzi.org> <01a21161-aa8d-6d4b-b384-3129fe6d799b@gmail.com> <973223fd-0119-376d-12cd-21559a14ce87@labs.htt-consult.com> <b88975b0-ecfd-3091-4314-304c36d51e8f@gmail.com> <3c632ce9-115d-11f5-ee33-bfabd4973522@labs.htt-consult.com> <f5dc0567-c9a1-a26f-b240-aead0d85c11f@gmail.com> <c9cc2ff4-c24f-f575-150b-8b978a4c2ac5@labs.htt-consult.com> <52a7a755d3744e948c358671e617e1e9@icao.int>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <7cbbe677-1060-1481-9446-210f15a4d0d3@gmail.com>
Date: Thu, 09 Jul 2020 18:04:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <52a7a755d3744e948c358671e617e1e9@icao.int>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/LwsXbWApnUhfMUGJ1BjF6E07-Xc>
Subject: Re: [Tm-rid] Review of draft-drip-arch-02 w.r.t. RFC6973, RFC8280 and other
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Trustworthy Multipurpose RemoteID <tm-rid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tm-rid/>
List-Post: <mailto:tm-rid@ietf.org>
List-Help: <mailto:tm-rid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2020 16:05:03 -0000


Le 09/07/2020 à 16:51, Da Silva, Saulo a écrit :
> You mentioned my name, so, some comments below your notes. Saulo
> 
> -----Original Message----- From: Tm-rid <tm-rid-bounces@ietf.org> On
> Behalf Of Robert Moskowitz Sent: 8-Jul-20 9:02 AM To: Alexandre
> Petrescu <alexandre.petrescu@gmail.com> Cc: tm-rid@ietf.org Subject:
> Re: [Tm-rid] Review of draft-drip-arch-02 w.r.t. RFC6973, RFC8280 and
> other
> 
> 
> 
> On 7/8/20 8:49 AM, Alexandre Petrescu wrote:
>> 
>> 
>> Le 07/07/2020 à 19:26, Robert Moskowitz a écrit :
>>> ANSI/CTA 2063-A
>> 
>> Thank you.
>> 
>> I downloaded it.
>> 
>> But it says "Unmanned", whereas a flying taxi would be manned even
>> if that person would not control the flight.
>> 
>> Maybe they'll change the title of the document, or maybe the UAM 
>> inclined will invent a new ID for 'manned but not in control' or 
>> something like that.
> 
> Saulo: We call them autonomous.
> 
> For now, ICAO sees UAM as Unmanned and will use the 2063 numbering
> scheme.

Noted, thank you.

I will check the 2063 numbering scheme from the freely available 
document ANSI/CTA 2063-A (free, hm, but very unfriendly to privacy 
because it requests my postal address at work).

>  They are unmanned in the sense of no pilot on board.

YEs, but note how difficult is it to understand.

UAM - U means Urban
UAV - U means Unmanned

Unmanned - there is no Pilot onboard but there could be a journalist 
with no pilot skill, like in the ehang demo of a year ago or so.

Alex

   If
> there IS a pilot on board, then they are manned aircraft and fall
> under those regulations and numbering. (actually I believe testing to
> date have been onboard pilot air taxis.)
> 
> ICAO (Saulo needs to join in) has augmented the paper certification
> process for manned aircraft with a digital process.  Manned flying
> taxis will be in this category unless a new one is created.
> 
> Saulo: I don’t know wat you call "augmented paper certification" but
> whatever a vehicle is called "aircraft" it requests airworthiness
> certification, be it manned or unmanned and on the unmanned we may
> also have the autonomous category (no pilot onboard or on the ground)
> ones.
> 
> Then you get should a UAM, even manned participate in the Broadcast
> Remote ID messaging for safety purposes?  I would think so, but this
> is still really an unclear area.
> 
> Saulo: As of today's developments , without having the regulations to
> cover it, the answer is yes.
> 
> definitely they will not participate in the automotive V2X ecosystem,
> despite conversations over on the ITS list.  Oh, they may listen in,
> but what messaging impacts them?
> 
> Saulo: Agree.
> 
> Bob
> 
> -- Tm-rid mailing list Tm-rid@ietf.org 
> https://secure-web.cisco.com/1fVCI0d3ZjaRLYOqMoz20_QhDktYXzfHlKy6CLfTnv4KFnaZHu9HTvyETH-VA66yy-K1D3aWSetch81R8oetV7bN_1Gd9cxec72BWZpzMStE8jhFkE7FyW8BbZ7A8FQhrnu1jfxZLbtqsp2QjM5iSAjepvmNvstZz4eg4JOpwV-9XmxZpjKbithNlUzs4-WR2CfjyYnz9fINzZExnw-gcxVjcnwQX9F6hFGG_kUV1Yzuadz3QbQWgtNmAbawrxaPlIrF725lXvPPHkaRRcjlLkdK_8l0QE82tGwPOF_sGF54vD20ee1VofYgXwiE5472dpqKMlOgqccgTn7qjXO2XLA/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Ftm-rid
>