Re: [Drip] ADSB

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 12 July 2023 13:54 UTC

Return-Path: <alexandre.petrescu@gmail.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 55CC8C151522 for <tm-rid@ietfa.amsl.com>; Wed, 12 Jul 2023 06:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.332
X-Spam-Level:
X-Spam-Status: No, score=-4.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] 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 riWU017V77Eo for <tm-rid@ietfa.amsl.com>; Wed, 12 Jul 2023 06:54:30 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 3732EC14CF17 for <tm-rid@ietf.org>; Wed, 12 Jul 2023 06:54:30 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 36CDsRNC054595; Wed, 12 Jul 2023 15:54:27 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 47E2C203B30; Wed, 12 Jul 2023 15:54:27 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 37111203BA9; Wed, 12 Jul 2023 15:54:27 +0200 (CEST)
Received: from [10.14.3.171] ([10.14.3.171]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 36CDsRNa017015; Wed, 12 Jul 2023 15:54:27 +0200
Message-ID: <66d538c6-1ae0-8f87-2cea-9f08377e1e8a@gmail.com>
Date: Wed, 12 Jul 2023 15:54:27 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0
Content-Language: fr
To: 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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <C5708075-DE36-4803-BA30-E4219E0BF1CA@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/-BnVN9w5MK9fY9aKfEY1UU8d6-A>
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 13:54:32 -0000


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.

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
>