Re: [Drip] ADSB

Stephan Wenger <stewe@stewe.org> Tue, 04 August 2020 15:16 UTC

Return-Path: <stewe@stewe.org>
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 D37623A07C8 for <tm-rid@ietfa.amsl.com>; Tue, 4 Aug 2020 08:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steweorg.onmicrosoft.com
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 vZ-JlbMBpOIK for <tm-rid@ietfa.amsl.com>; Tue, 4 Aug 2020 08:16:39 -0700 (PDT)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2112.outbound.protection.outlook.com [40.107.244.112]) (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 EBB0E3A07C5 for <tm-rid@ietf.org>; Tue, 4 Aug 2020 08:16:38 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XJXq//4rHJM1PaWEkfx61N2ei22/56gJVBH+lqixOF4p6XSmNM+1M4CYmlfLHjNKEWY535AMGa4LU1QbF6/8hYmuPPza84zkXEQ1+51oN6APFPjValnXkz7PEUWwe7Wi9nlDTAmSg8pLbLsw+bH5++Fdn2DV6yKvjEIDF4yIkapE7QOZ8YSe+Hd9p9YIQOE2PtWR74rx8szcaYVrAfAjFYQWIEElf+xtmCaQdW2loTtoGd0gHXTVXBXElYVOcA7A2OwmjOtkAYsKsivau0gUeg+feB65tkIDOwbWGQdRbcb49a6/X49IadigmiLRg0kS82CEmslce56JPaBod3rcEw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=q/yTRA1aEfZbULztkz4dCW1hSqALKE+oN0f7ypMAiJE=; b=aFHs+SHNrDkkoMlE5G3H83FOGEaE3Dy4ZuTk8WGAw2XvjrUsQJE2gWaHq30XluaybwWsKwSFlLCsAfL6L+n1+fLzPt5IgKYXwGOPgzat4b2XccXfAiTj2VzaWhVGOZjFzacw5oxW6c7wtKRMH/RmfEzza0UqZTblt+gf+8WAcsdieHdJbB1wPjbpB5mNwhsXWZaeorSYPeXk1IUKx5KTFdBomIpxS8/EH+P/c2MiTeiBt2QkfZs26sGOjNMgxjqsRgcSOVFoXdBr1TbxZQogBCkPQ2HCkOCuwdcgG/IFIVKoVgq1kC8o84BcNsO6dQ0G6N+krzfSvyPtB1V+H+toZg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=stewe.org; dmarc=pass action=none header.from=stewe.org; dkim=pass header.d=stewe.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=steweorg.onmicrosoft.com; s=selector2-steweorg-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=q/yTRA1aEfZbULztkz4dCW1hSqALKE+oN0f7ypMAiJE=; b=ahQwS/JJGwOD0a4CE+pPqdnIYBlcLmqkcKOnZ4aXgP63ICJ+SRWcglZJ16RuMhtAVpZp2wv07DNNeXFmvVXgJanZ8ebbP2w+ALu+fP0nZvCAF1BHqNWBgWLBo5pWcSC18jFWiDA0f2WDVqOdPiTnljySmlbaSeisASwSNHTD+z0=
Received: from DM6PR17MB3036.namprd17.prod.outlook.com (2603:10b6:5:12e::14) by DM6PR17MB2825.namprd17.prod.outlook.com (2603:10b6:5:12a::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.15; Tue, 4 Aug 2020 15:16:36 +0000
Received: from DM6PR17MB3036.namprd17.prod.outlook.com ([fe80::88a:598:450b:a4c4]) by DM6PR17MB3036.namprd17.prod.outlook.com ([fe80::88a:598:450b:a4c4%5]) with mapi id 15.20.3239.022; Tue, 4 Aug 2020 15:16:36 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "tm-rid@ietf.org" <tm-rid@ietf.org>
Thread-Topic: [Drip] ADSB
Thread-Index: AQHWamaTKX8D7WRcqU6X/URQrOkY7KknmlWA
Date: Tue, 04 Aug 2020 15:16:36 +0000
Message-ID: <CCFDD2A2-C8A6-4FAA-A058-33A58B2B7E65@stewe.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>
In-Reply-To: <f4dd60a2-da57-35d5-6467-9a4b09b3d73c@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.39.20071300
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=stewe.org;
x-originating-ip: [2601:640:8300:f930:51f8:3264:b727:8d95]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d3857e18-e91f-4cf0-2d23-08d838896109
x-ms-traffictypediagnostic: DM6PR17MB2825:
x-microsoft-antispam-prvs: <DM6PR17MB2825FAD10505D9CBC1076261AE4A0@DM6PR17MB2825.namprd17.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: IPC2l1acLp8jxisxwWQ7NKOBNO2+5jgrjLdzA0SaPAfxN5BauAEj3GIgUHbfxYlbTIacP86JVMYTazpmcpoX2mN/g4d44/KWClQVfPYl91xvFa6GW3wcwhqiRpahyVm5zTlYMsLCENFWbhvdr0EMBFq7jTYYyhMASrj9as5MwngNSH/Onta4kon1S4HkuGeJpFIHgHJ4DAPG1QtqlpKl+8Kfsscc6n+emZpILu3+ojfFL7TKRKW7Hz6QYW1ONOtbxFAoRSagxG0x6OW1r7kFPf7KFJaJj1WU/UXQo5hZXxfbhKkF+zWZs/jorzRZnu2vY4EaOXto664twzzQxNZGI+z5w7ArB788M8CT8qazES2+0n9TQxuA1wWLLuj7rU0sc0QfG5REhN6PJHzVfo5MaA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR17MB3036.namprd17.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(366004)(136003)(396003)(39830400003)(376002)(346002)(966005)(316002)(2616005)(110136005)(6512007)(5660300002)(15974865002)(2906002)(508600001)(66446008)(6486002)(66574015)(86362001)(6506007)(53546011)(36756003)(33656002)(8936002)(66946007)(186003)(66476007)(66556008)(76116006)(91956017)(71200400001)(64756008)(83380400001)(8676002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: MTWMwfokPDZ79Gj/CQMD4gxxnMH8PDzC9MZeXGXKMbZq3dMve81KV2+UWmVRdw2tMacmgYjF/zsl5QkANYV9y2ahymdvr8KOZpcK7SOCHy7rZz2aznqkl4rR0MTk8zGRYdKAHhCaRd1boyIUL5j6duvJBR07o8ZxRkJj4OlB/SCA4x73Ve3loKxe/xHmIkyo7I4fpmz5R5rlLHpCmE8goK/So4FzB1AosNodnFFFlW1UAW5LER/rnxWz6711cDy4N4ZZCzVT/baQDBBPFO+hvoQKKF4n74iOolpkSgDen4X1navIk8uumsihcVIoU9JWOJBoByz0yjAR1p6UlCQEsRho17UvQ4i7t8w+sZZ0InFH5ADSU0xH4x2ce+/LyjaaThMJMK+cy2OY25e7qljcpiTuGYX+a9RfkW6/qai8ZV5Uaei0dAFvk7x4JqqWCFH8nAmw8mOZju2bOaUawlzVSkehMXiOaqzVMUxTq4+h6ir37qombK9kZp8YOZ5syS0uUo2rs4d7Rs4AJpKtEWCN6gUwVs+7eHGXUDeEsgOuA6GwrES680NIeakqCv1PEt7jFiipV+GlqsEQYvPKwdOTOaf836COgEORGPzgNpBKwq+trodeBQ+Ltz3H5capDyz4p0GvO9qPlC4oU61L8yeMeY7dC86aayOJD9yf9wIkrhTPEFFAlkuVHQuTctBjVEwuqR3n0r2HqMYj9yjEKybycw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <A683D0E0529CCF429E977520AB2032CD@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR17MB3036.namprd17.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d3857e18-e91f-4cf0-2d23-08d838896109
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Aug 2020 15:16:36.1242 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: YZwr5nu/S3jrJLs90YOn/idGo5zVZbLOPxFdgQlvJj61u+0CEJIs0DQodhzjsfsh
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR17MB2825
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/cQDmoNEl8cv2FR1Neue_duzqEh4>
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:16:41 -0000

Alexandre,

ADS-B is a 20+ year old technology and offers properties (bandwidth, security, cost) of a 20 year old technology.  That it just recently sees widespread adoption is a result of incredibly slow (even by IETF standards) deployment process, and that in turn is the result of the very conservative and safety conscious aviation community and regulators, as well as the high cost related to anything manmade that flies.  By speculating to use ADS-B as an underlying technology for IP, I fear you demonstrate a certain lack of background.  The Wikipedia article on ADS-B (https://en.wikipedia.org/wiki/Automatic_dependent_surveillance_–_broadcast) is mostly correct, and I recommend in particular the sections on "Theory of operation" and "System Design Considerations".

A few (of many) reasons why ADS-B is unsuitable for light drones (anything significantly smaller than a man-carrying aircraft):
-24 bit ICAO transponder code, limiting the number of (active or inactive) ADS-B equipment.  Each modern aircraft over a certain size (except the smallest two-seaters, powered parachutes, and aircraft without electrical systems such as antiques) has a unique code assigned for its lifetime.
-line-of-sight wireless connection for the "uplink" with only a few hundred ground stations for the whole US (or 70 for the whole Australia).  That means ADS-B coverage is almost everywhere only available at altitudes in which small drones are neither legal nor, in most cases, physically capable to fly (a few thousand feet in the US except near major airports where you don't want drones, 30000 ft in Australia).  Aircraft send over the uplink information such as aircraft ICAO code, aircraft type, speed, direction of flight, altitude, etc.).  Information is sent in the clear, by design.  You can buy a box receiving this info, hook it up to an Raspberry PI or something, and look at the traffic near your house and send it on to your friends--in fact, this type of crowdsourced ATC info is what makes flightradar24 and similar sites work.
-the downlink (system to aircraft) is bandwidth-limited to a few hundred kbit/s for all aircraft combined in the coverage of the satellite transponder.  (This is somewhat over-simplified, as the uplink is intentionally sent in the clear, and many ADS-B receivers monitor the uplink of other aircraft for redundancy and more up-to-date information about traffic; see abive.)  AFAIK, the whole continental US is covered by less than 20 transponders. N The downlink carries not only traffic information but also cruise and airport weather, certain airspace restrictions, and so forth.  All this is broadcasted and the ADS-B receivers in the aircraft need to filter out the information relevant for its position, course, and intentions.  Already, the bandwidth available is almost fully utilized to the point that the broadcast occasionally needs to omit certain less-critical information to make space for more critical one.  The system scales only by adding satellite transponders, which is expensive and not a fine granularity.

As for Mars, ADS-B is unsuitable until someone builds a ground-station network and has suitable satellites in orbit.  A bit closer to earth, for over-water and trans-pole operations there is ADS-C, which is completely satellite based and, AFAIK, even more bandwidth limited than ADS-B.  Yet another example for a network unsuitable to carry IP traffic, but I digress.

In short, forget ADS-B for the DRIP work..

Stephan


On 8/4/20, 6:53 AM, "Tm-rid on behalf of Alexandre Petrescu" <tm-rid-bounces@ietf.org on behalf of alexandre.petrescu@gmail.com> 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
    > 
    > 

    -- 
    Tm-rid mailing list
    Tm-rid@ietf.org
    https://www.ietf.org/mailman/listinfo/tm-rid