IETF Logo Mail Archive

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

"Da Silva, Saulo" <Sdasilva@icao.int> Thu, 09 July 2020 14:51 UTC

Return-Path: <Sdasilva@icao.int>
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 B23853A0C47 for <tm-rid@ietfa.amsl.com>; Thu, 9 Jul 2020 07:51:55 -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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 anaRpoVFQ0yi for <tm-rid@ietfa.amsl.com>; Thu, 9 Jul 2020 07:51:53 -0700 (PDT)
Received: from esa4.hc196-20.ca.iphmx.com (esa4.hc196-20.ca.iphmx.com [216.71.130.19]) (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 8AEC03A0C80 for <tm-rid@ietf.org>; Thu, 9 Jul 2020 07:51:48 -0700 (PDT)
IronPort-SDR: GJSIqkeiKXkBVGB5jZX5ik25WgxaNsXHYd6JAHFaoN8x32OAWCqUTG8v2/5kbLYb2RnAs4Q12D NY3WrR4/wfnQSRtspjGG7cDr0Gbs4Tk4S9elICs3cVhnQcMWzhM8+w8b5wff8A4FNYunli4J2k UFlxnAAfZx4s0qeheoU47sVNZqnim48fwsO8OuZMOF8PWgwRQthBc9Ii8wZhDizOGEP5xgN0WV L5e5mBJvCvLSSFX+77uHOs44lZUo4u1BgO3p5qRFC+8LfeJKqht84AvyYk1BrijjsJNpoEeDFP 7hQ=
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from smtp.icao.int ([192.206.28.75]) by esa4.hc196-20.ca.iphmx.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 09 Jul 2020 10:51:44 -0400
Received: from ExchMBX1.icaohq.icao.lan (10.1.4.158) by Exch2.icaohq.icao.lan (10.1.4.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Thu, 9 Jul 2020 10:51:43 -0400
Received: from ExchMBX1.icaohq.icao.lan (10.1.4.158) by ExchMBX1.icaohq.icao.lan (10.1.4.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Thu, 9 Jul 2020 10:51:43 -0400
Received: from ExchMBX1.icaohq.icao.lan ([fe80::190f:1f34:f603:5101]) by ExchMBX1.icaohq.icao.lan ([fe80::190f:1f34:f603:5101%2]) with mapi id 15.01.1979.003; Thu, 9 Jul 2020 10:51:43 -0400
From: "Da Silva, Saulo" <Sdasilva@icao.int>
To: Robert Moskowitz <rgm@labs.htt-consult.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
CC: "tm-rid@ietf.org" <tm-rid@ietf.org>
Thread-Topic: [Tm-rid] Review of draft-drip-arch-02 w.r.t. RFC6973, RFC8280 and other
Thread-Index: AQHWU8HCrx7JMrS0nkSuYv0W62OQS6j7KhUAgAFJboCAAArgAIAADZOAgAAXFwCAAUT7gIAAA4qAgAFrcaA=
Date: Thu, 09 Jul 2020 14:51:43 +0000
Message-ID: <52a7a755d3744e948c358671e617e1e9@icao.int>
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>
In-Reply-To: <c9cc2ff4-c24f-f575-150b-8b978a4c2ac5@labs.htt-consult.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.4.248]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/2hcn0KaqCGLCixsNOPAaCA5Vi-c>
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 14:51:56 -0000

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.  They are unmanned in the sense of no pilot on board.  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

v2.23.0 | Report a Bug | By Email