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

Robert Moskowitz <rgm@labs.htt-consult.com> Thu, 09 July 2020 16:34 UTC

Return-Path: <rgm@labs.htt-consult.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 1558E3A0C34 for <tm-rid@ietfa.amsl.com>; Thu, 9 Jul 2020 09:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 0Da7QoQzx8_d for <tm-rid@ietfa.amsl.com>; Thu, 9 Jul 2020 09:34:10 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 78D223A0C2A for <tm-rid@ietf.org>; Thu, 9 Jul 2020 09:34:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id DF41F62221; Thu, 9 Jul 2020 12:34:07 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id MU-1FOVb5hbh; Thu, 9 Jul 2020 12:33:58 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 57D66621B8; Thu, 9 Jul 2020 12:33:58 -0400 (EDT)
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "Da Silva, Saulo" <Sdasilva@icao.int>
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> <7cbbe677-1060-1481-9446-210f15a4d0d3@gmail.com>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
Message-ID: <952b8106-7160-8157-5de3-0d188d7e8f45@labs.htt-consult.com>
Date: Thu, 09 Jul 2020 12:33:52 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <7cbbe677-1060-1481-9446-210f15a4d0d3@gmail.com>
Content-Type: multipart/alternative; boundary="------------EF1849E83D7D56DB3F92B5A9"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/hdkHmQ0Ggb9RYoHdV1UEojzFyds>
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:34:14 -0000


On 7/9/20 12:04 PM, Alexandre Petrescu wrote:
>
>
> 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

TLDs, ya just got to love it...  :)

> 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.

SOMEONE has to be onboard, or it is not a 'taxi'.  :)

Unmanned means no LICENSED pilot in control.

>
> 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
>>
>

-- 
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:rgm@labs.htt-consult.com

There's no limit to what can be accomplished if it doesn't matter who 
gets the credit