Re: [Drip] ADSB

Robert Moskowitz <rgm@labs.htt-consult.com> Tue, 04 August 2020 15:53 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 9F1333A0A3B for <tm-rid@ietfa.amsl.com>; Tue, 4 Aug 2020 08:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.847
X-Spam-Level:
X-Spam-Status: No, score=-2.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.949, 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 fqY7_iMaLTFx for <tm-rid@ietfa.amsl.com>; Tue, 4 Aug 2020 08:53:31 -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 ADBDB3A0A12 for <tm-rid@ietf.org>; Tue, 4 Aug 2020 08:53:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 5B9BA62434; Tue, 4 Aug 2020 11:53:30 -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 6HDxluGQb5p2; Tue, 4 Aug 2020 11:53:20 -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 B978362415; Tue, 4 Aug 2020 11:53:19 -0400 (EDT)
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 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> <d8cf3a43-910a-db2f-4408-184b52446c97@labs.htt-consult.com> <a288966d-d22a-d0fa-c544-ae2db7d1533e@gmail.com> <e60a44a7-a659-1937-19fb-d468c4329bb2@axenterprize.com> <A80AB482-557C-44C7-A99A-B494852D59AB@tencent.com> <f4dd60a2-da57-35d5-6467-9a4b09b3d73c@gmail.com> <c09092f9-2c59-65be-6af8-47d1135c6cfe@axenterprize.com> <61511ef6-5b9b-5b62-f922-d32b994a35b9@gmail.com>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
Message-ID: <34a78f0e-46ed-584e-492e-f729d2f01ef4@labs.htt-consult.com>
Date: Tue, 04 Aug 2020 11:53:19 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <61511ef6-5b9b-5b62-f922-d32b994a35b9@gmail.com>
Content-Type: multipart/alternative; boundary="------------AC7C4273E38D797F448F4D75"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/t6O4Ib3HEWni6-Im9JNEUsloXgY>
Subject: Re: [Drip] ADSB
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Drone Remote Identification Protocol <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: Tue, 04 Aug 2020 15:53:35 -0000


On 8/4/20 11:27 AM, Alexandre Petrescu wrote:
> Thanks for the clarification.
>
> Le 04/08/2020 à 17:17, Stuart W. Card a écrit :
>> I just want to respond to one line that I think comes from confusion:
>>
>>> But if we have reluctance about the use of ADS-B, and thus of IP,
>>> and we recommend Bluetooth-without-IP to identify drones
>>
>> We aren't recommending Bluetooth-without-IP, we are _supporting_ it,
>
> But, the security manifest that I have seen on slides during the 
> presentation of the DRIP WG meeting - is something below IP, right?
>

Oh, and for Network Remote ID and C2 see my draft:

draft-moskowitz-drip-secure-nrid-c2

> Alex
>
>  as
>> it is specified in ASTM F3411, which most of the regulators are dubbing
>> as an approved technical means of regulatory compliance.
>>
>> AFAIK, no one runs IP over ADS-B, which was designed as a narrowband
>> application specific communications stovepipe, not a data link
>> supporting higher layer network protocols, so not great for IP.
>>
>> More importantly, we have no "reluctance about the use of... IP", which
>> is an entirely separate issue from ADS-B.
>>
>> On 8/4/2020 9:52 AM, Alexandre Petrescu wrote:
>>> architectural layers discussion...
>>>
>>> Le 30/07/2020 à 11:49, shuaiizhao(Shuai Zhao) a écrit :
>>>> Just to echo Stu on the ADSB, AFAIK, ADSB will  not be feasible for
>>>> most of the drones mostly due to SwaP, commercial drones might be
>>>> exception.
>>>
>>> It might be that ADS-B might be forbidden in drones on Earth, but how
>>> about the drones on Mars? ('NASA Mars helicopters', or ESA too).  On
>>> Mars there would be much less such drones, so less risk of 
>>> interference.
>>>
>>> With such a system (ADS-B under IP) one could re-use DTN (Delay 
>>> Tolerant
>>> Networking) between planets, and so identify drones even on Mars.
>>>
>>> But if we have reluctance about the use of ADS-B, and thus of IP, 
>>> and we
>>> recommend Bluetooth-without-IP to identify drones, then we might become
>>> too dependent on it?
>>>
>>> (do not get me wrong, I do like Bluetooth, but I like many other things
>>> together with Bluetooth).
>>>
>>> Alex
>>>
>>>>
>>>> Best,
>>>>
>>>> Shuai Zhao
>>>>
>>>> *From: *Tm-rid <tm-rid-bounces@ietf.org> on behalf of "Stuart W.
>>>> Card" <stu.card@axenterprize.com> *Date: *Wednesday, July 29, 2020 at
>>>> 19:46 *To: *"tm-rid@ietf.org" <tm-rid@ietf.org> *Subject: *[Drip]
>>>> ADSB (was: Review of draft-drip-arch-02 w.r.t. RFC6973, RFC8280 and
>>>> other)(Internet mail)
>>>>
>>>> Sorry for the slow reply.
>>>>
>>>> ADS-B is gradually being mandated for essentially all manned
>>>> aircraft.
>>>>
>>>> ADSB-In and ADSB-Out are mandated for airliners: -In gives their
>>>> pilots
>>>>
>>>> some Situational Awareness (SA) of other aircraft; -Out gives other
>>>>
>>>> pilots SA of the airliners.
>>>>
>>>> "ADSB-Out" is mandated even for small general aviation aircraft: it
>>>> does
>>>>
>>>> not directly benefit the pilots of those aircraft; but by providing
>>>> SA
>>>>
>>>> to others, it indirectly benefits all.
>>>>
>>>> ADSB is _not_ going to be deployed on large numbers of small UAS as
>>>> it
>>>>
>>>> would overwhelm the limited bandwidth available at those lower radio
>>>>
>>>> frequencies (which propagate long ranges). In fact, it is expected to
>>>> be
>>>>
>>>> explicitly prohibited in the US per the FAA NPRM; I suspect most of
>>>> the
>>>>
>>>> rest of the world will do likewise.
>>>>
>>>> ADSB is also altogether insecure.
>>>>
>>>> On 7/9/2020 3:02 AM, Alexandre Petrescu wrote:
>>>>
>>>> ...
>>>>
>>>> They call it "ADS-B Receivers" (Automatic Dependent Surveillance -
>>>>
>>>> Broadcast).
>>>>
>>>> I wouuld like to ask if there is a packet dump available showing
>>>> such
>>>>
>>>> presence data form planes?  Maybe wireshark already supports it,
>>>> maybe
>>>>
>>>> it even dissects it...
>>>>
>>>> -- 
>>>>
>>>> -----------------------------------------
>>>>
>>>> Stuart W. Card, PhD, Principal Engineer
>>>>
>>>> AX Enterprize, LLC  www.axenterprize.com
>>>>
>>>> 4947 Commercial Drive, Yorkville NY 13495
>>>>
>>>>
>>>
>>
>>
>>
>

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