Re: [Drip] Comment on -arch-22
Jens Finkhaeuser <jens@interpeer.io> Wed, 30 March 2022 10:49 UTC
Return-Path: <jens@interpeer.io>
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 9EE1B3A084B
for <tm-rid@ietfa.amsl.com>; Wed, 30 Mar 2022 03:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001,
RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=interpeer.io
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 p2BkpI_I-Xed for <tm-rid@ietfa.amsl.com>;
Wed, 30 Mar 2022 03:49:24 -0700 (PDT)
Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136])
(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 9C1B33A0831
for <tm-rid@ietf.org>; Wed, 30 Mar 2022 03:49:23 -0700 (PDT)
Date: Wed, 30 Mar 2022 10:49:13 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interpeer.io;
s=protonmail; t=1648637360;
bh=zEuEeSG2fDSFtedAwKDRc4jFiaCCb21PWvgDnmiujis=;
h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To:
References:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID;
b=MTIgRiaf8rw+FIF2Vibw4jk/C6oM6rHDutePs5qZEBViN9kvygq4L5719jE7av11W
9wQOVGSkWkW3cgmFoQgonovtllsUMC9MsaDtOh6qYGRGAgEJfKKMH9JklmEo9Uzzfz
N91zTFOwpJMavxXMxV8dGGa8hKu/hk/M1/qYREHo=
To: Andrei Gurtov <andrei.gurtov@liu.se>
From: Jens Finkhaeuser <jens@interpeer.io>
Cc: "tm-rid@ietf.org" <tm-rid@ietf.org>
Reply-To: Jens Finkhaeuser <jens@interpeer.io>
Message-ID: <PEjAyWfi_N8XBVJ18pYnGI1SOl7I0DaEE1ce4qFp-YHWi4UGbXkUVFl5AJYIwUnau_2Z0u5xkrZclIr4HSxjfGegm7lHfvPtYqFVpdYsRIw=@interpeer.io>
In-Reply-To: <b640c6f4-29c8-b4c5-36bb-e3aa2986f778@liu.se>
References: <t941p8wbPadYaW5iXMZZ92fRZxA9AShZYY2-vpoY4Nh9uhgeZozaJJI1GnLhzKJlirvUFL4vy8ARuip2QVfc0Br6upFgliBWVCM2YXJsWhw=@protonmail.com>
<b640c6f4-29c8-b4c5-36bb-e3aa2986f778@liu.se>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
micalg=pgp-sha512;
boundary="------a6a04eb341160961e3af86d44bf0f5c46ebde2d8c2d6f92eb348e37652dc4dd5";
charset=utf-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/w6MI6wy06In1YM6xEJIyV2y7EF4>
Subject: Re: [Drip] Comment on -arch-22
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: Wed, 30 Mar 2022 10:49:30 -0000
Hi, I was under the impression that Corus is completed. I do not know the -xuam postfix. Is it a follow-on or subproject? Since Corus is more related to U-SPACE and therefore (internet-) connected services, and our projects are more related to the vehicles themselves, I suspect there is some use in better coordination. We do of course consume results from such projects, but I get the impression that on occasion they're less connected than might be useful. That's generally the case between any of these projects, also we are sometimes busy transferring insights from one to the other and back. It's interesting as well that the drone identification issue overlaps in the communication space with the more general discussion occurring in int-area on locators vs identifiers. The latter here is a network identifier, which from a communications perspective shouldn't be all that different from the drone identifier - either one derived from the other, or the same. That is, it is desirable from a ground control station to "speak with the drone" rather than "speak with the first network interface on the drone" or "speak with the IP address that the first network interface of the drone currently has assigned". I'm trying to provide this perspective to that conversation at the moment. That's also the lens through which I'm exploring DRIP. Fun times ahead! Jens ------- Original Message ------- On Tuesday, March 29th, 2022 at 18:06, Andrei Gurtov <andrei.gurtov@liu.se> wrote: > Hello Jens, > > Thanks for interest in DRIP and greetings from nearby Sweden. > > Maybe you've heard about EU projects AiRMOUR and Corus-Xuam where we try to demo DRIP as a part of their tests. > > https://airmour.eu/ > > https://corus-xuam.eu/ > > Btw, there is an interesting show from a Swiss company Involi about an add-on box for Remote ID, should we get them involved in DRIP? > > https://dronelife.com/2022/03/27/remote-id-drone-tracker-leman-remoteid-from-involi-video/ > > BR Andrei > -- > Andrei Gurtov, PhD, ACM Distinguished Scientist > Professor, LiU, Sweden > Chair, IEEE Sweden > https://www.ida.liu.se/~andgu38/ > > On 24-Mar-22 10:45, Jens Finkhaeuser wrote: > > > Hi all, > > > > since I am active through my employer in European drone research (ADACORSA and COMP4DRONES projects to name just two), and our speciality here is communications which relates to identification, I read the draft with some interest. I fear a full analysis and review would require more effort than I have managed to put into it. > > > > However, as a comment, it appears that the draft is very strongly related to ASTM F3411, and maybe more so than immediately apparent. I wonder how intentional that is? > > > > I ask for two reasons: > > > > 1. The EASA regulation referenced is not the most relevant, and potentially a bit out of date; consequently, it is unclear how well this proposal will work as-is in European airspace. > > > > 2. The assumptions made on communications technologies seem to exclude some drone categories and use cases (which admittedly are also a source of disagreement between some of our research partners). > > > > I'd be happy to bring more perspectives to this, but I am not sure this is appropriate to the draft's intent. > > > > Jens
- [Drip] Comment on -arch-22 Jens Finkhaeuser
- Re: [Drip] Comment on -arch-22 mohamed.boucadair
- Re: [Drip] Comment on -arch-22 Card, Stu
- Re: [Drip] Comment on -arch-22 Jens Finkhaeuser
- Re: [Drip] Comment on -arch-22 Robert Moskowitz
- Re: [Drip] Comment on -arch-22 Robert Moskowitz
- Re: [Drip] Comment on -arch-22 Card, Stu
- Re: [Drip] Comment on -arch-22 Robert Moskowitz
- Re: [Drip] Comment on -arch-22 Jens Finkhaeuser
- Re: [Drip] Comment on -arch-22 Robert Moskowitz
- Re: [Drip] Comment on -arch-22 Robert Moskowitz
- Re: [Drip] Comment on -arch-22 Jens Finkhaeuser
- Re: [Drip] Comment on -arch-22 mohamed.boucadair
- Re: [Drip] Comment on -arch-22 Andrei Gurtov
- Re: [Drip] Comment on -arch-22 Jens Finkhaeuser
- Re: [Drip] Comment on -arch-22 Card, Stu