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

Robert Moskowitz <rgm@labs.htt-consult.com> Wed, 08 July 2020 15:39 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 A7F533A0E3A for <tm-rid@ietfa.amsl.com>; Wed, 8 Jul 2020 08:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ZyiZSPIiPcqh for <tm-rid@ietfa.amsl.com>; Wed, 8 Jul 2020 08:39:35 -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 79CF63A0E34 for <tm-rid@ietf.org>; Wed, 8 Jul 2020 08:39:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id D2566621B8; Wed, 8 Jul 2020 11:39:33 -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 Fw0KgUqpOzKl; Wed, 8 Jul 2020 11:39:27 -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 2283E62134; Wed, 8 Jul 2020 11:39:24 -0400 (EDT)
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: 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> <7ddd9a2f-23ba-dd82-8cfb-1d2974969e67@gmail.com>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
Message-ID: <d8cf3a43-910a-db2f-4408-184b52446c97@labs.htt-consult.com>
Date: Wed, 08 Jul 2020 11:39:19 -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: <7ddd9a2f-23ba-dd82-8cfb-1d2974969e67@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/zU0dhh_r_5zS3HdvNKhG6rVkmSA>
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: Wed, 08 Jul 2020 15:39:38 -0000


On 7/8/20 10:54 AM, Alexandre Petrescu wrote:
>
>
> Le 08/07/2020 à 15:02, Robert Moskowitz a écrit :
>>
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> 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?
>
> Can we expect an UAM vehicle to use 802.11-OCB mode (earlier known as 
> 802.11p) at 5.9GHz?
>
> Or is it some other IP-able link layer technology?
>
> Or is it a non-IP link? 

I really doubt it.  I know a bit about 802.11-OCB.  I was active in 802 
when 802.11p was done and did some time on 1609 as well...

I suspect there will be a turf war if the CAAs try to get into the DoTs 
spectrum.  :)

Plus the ICAO is concerned about security and garden-walling airspace 
from most ground space.

So you either have LTE/5G, perhaps a private addressing/slice.  Or 
something down-frequency like 500 - 900 MHz like IEEE 802.16 (note the 
work being done on the PHYs there in TG 802.15.16t).  So I see more of a 
money fight between the 3GPP cellular companies and the private spectrum 
companies.

The private spectrum companies have a very strong case for managing who 
uses their spectrum and maintaining the 'mission critical' 
communication.  Do check out:

http://www.ieee802.org/15/pub/TG16t.html

Some of these frequencies have very good characteristics for this 
application.

For UAM, it SHOULD be an IP link, but if they go Sat, all bets are off, 
depending on the Sat company.

Bob