Re: [Drip] ADSB

Robert Moskowitz <rgm@labs.htt-consult.com> Wed, 12 July 2023 14:55 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 B52AEC151717 for <tm-rid@ietfa.amsl.com>; Wed, 12 Jul 2023 07:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MGMwe6DpuRc7 for <tm-rid@ietfa.amsl.com>; Wed, 12 Jul 2023 07:55:33 -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 A19F1C137384 for <tm-rid@ietf.org>; Wed, 12 Jul 2023 07:54:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 5EFAA62794; Fri, 1 Jan 2010 18:05:54 -0500 (EST)
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 h2VzvEYWs70h; Fri, 1 Jan 2010 18:05:45 -0500 (EST)
Received: from [192.168.160.29] (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id A658662620; Fri, 1 Jan 2010 18:05:42 -0500 (EST)
Content-Type: multipart/alternative; boundary="------------ov05JRW7zijNT0IHN6a0RNJP"
Message-ID: <694775d8-e7b4-867c-4fca-56f85fd23e59@labs.htt-consult.com>
Date: Wed, 12 Jul 2023 10:54:41 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0
Content-Language: en-US
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, Carsten Bormann <cabo@tzi.org>
Cc: Stu Card <stu.card@axenterprize.com>, "tm-rid@ietf.org" <tm-rid@ietf.org>
References: <6dfe8ea4-e803-5a70-c8eb-08eb3c1d4c4c@gmail.com> <2dd5fa11-d586-43e4-bd09-828c6aa77a0f@cea.fr> <MN2PR13MB4207C77AF8314327F9757A8FF831A@MN2PR13MB4207.namprd13.prod.outlook.com> <3decc87c-5b25-6349-b98f-618775dc5a57@gmail.com> <C5708075-DE36-4803-BA30-E4219E0BF1CA@tzi.org> <66d538c6-1ae0-8f87-2cea-9f08377e1e8a@gmail.com>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
In-Reply-To: <66d538c6-1ae0-8f87-2cea-9f08377e1e8a@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/1LQ2b-47peQPdrJZm6FrUNKqV6w>
Subject: Re: [Drip] ADSB
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 12 Jul 2023 14:55:33 -0000


On 7/12/23 09:54, Alexandre Petrescu wrote:
>
>
> Le 12/07/2023 à 12:45, Carsten Bormann a écrit :
>> On 2023-07-12, at 11:52, Alexandre Petrescu 
>> <alexandre.petrescu@gmail.com> wrote:
>>>
>>> why not 400m
>>
>> This is not a domain where we get to invent boundaries.
>
> I agree.
>
> But each domain to its own competencies.
>
> If the air flight domain invents incompatible imperial-metric 
> boundaries among continents that does not mean that the communication 
> protocol operation should do the same.

And it is the characteristics of ADS-B capacity that has ruled it out 
for use by UAS.  End of discussion.


>
> If they want to limit the kinds of flying devices that are allowed to 
> carry a certain type of radio equipment then they should express the 
> limitation based on radio equipment characteristics.
>
> It's the same with weight: if they want to limit the devices who can 
> carry an ADS-B device to the heavier ones ('birds') then it is the 
> same problem: ounces and grams, are not converted easily.
>
> For example, if I want to put a starlink user equipment on a drone I 
> hope I will not get limited by some altitude limit; I am ready to look 
> at the radio communication limits but not the altitude limit.  The 
> altitude limit is for those who build mechanical matters to respect 
> mechanical limits like altitudes.
>
> Maybe they want to say that a drone UAS which carries ADS-B must not 
> interfere with others.  That's a radio communication requirement, easy 
> to understand.
>
> Alex
>
>>
>> (Also, generally speaking, of course we should have a strong bias to 
>> using SI units, but in a domain where regulation is widely based on 
>> furlongs per fortnight, we’ll have to adapt.)
>>
>> Grüße, Carsten
>>
>

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