Re: [Tm-rid] Draft charter

Henk Birkholz <henk.birkholz@sit.fraunhofer.de> Thu, 10 October 2019 08:32 UTC

Return-Path: <henk.birkholz@sit.fraunhofer.de>
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 6B308120033 for <tm-rid@ietfa.amsl.com>; Thu, 10 Oct 2019 01:32:44 -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, RCVD_IN_DNSWL_HI=-5, 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 Wu7-B7m1LIlL for <tm-rid@ietfa.amsl.com>; Thu, 10 Oct 2019 01:32:41 -0700 (PDT)
Received: from mailext.sit.fraunhofer.de (mailext.sit.fraunhofer.de [141.12.72.89]) (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 45626120058 for <tm-rid@ietf.org>; Thu, 10 Oct 2019 01:32:39 -0700 (PDT)
Received: from mail.sit.fraunhofer.de (mail.sit.fraunhofer.de [141.12.84.171]) by mailext.sit.fraunhofer.de (8.15.2/8.15.2/Debian-10) with ESMTPS id x9A8WVGU012626 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA256 bits=128 verify=NOT); Thu, 10 Oct 2019 10:32:32 +0200
Received: from [134.102.159.0] (134.102.159.0) by mail.sit.fraunhofer.de (141.12.84.171) with Microsoft SMTP Server (TLS) id 14.3.468.0; Thu, 10 Oct 2019 10:32:26 +0200
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, Robert Moskowitz <rgm@labs.htt-consult.com>, "tm-rid@ietf.org" <tm-rid@ietf.org>
References: <0fc9d954-a9af-b590-afb2-64ad2594f552@labs.htt-consult.com> <d9b29364-c5ec-0391-6acf-10b15410855c@labs.htt-consult.com> <D9509822-DA8D-4622-BE7E-E1216DE75202@cisco.com>
From: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Message-ID: <6b77cccc-0e0a-e56f-aaf6-23f3e9e0bcb6@sit.fraunhofer.de>
Date: Thu, 10 Oct 2019 10:32:24 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <D9509822-DA8D-4622-BE7E-E1216DE75202@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [134.102.159.0]
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/Fji6YMiRgOnquCOth5PTt8k3K2s>
Subject: Re: [Tm-rid] Draft charter
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Trustworthy Multipurpose RemoteID <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: Thu, 10 Oct 2019 08:32:45 -0000

Congratulation TM-RID'lers,

this is great news!

Viele Grüße,

Henk

On 10.10.19 10:21, Eric Vyncke (evyncke) wrote:
> Bob and others,
> 
> During the BoF approval call with IESG & IAB, the TM-RID BoF has been 
> approved as a non-WG-forming BoF as the charter is not completely mature 
> (see below).
> 
> It was also preferred to have TM-RID as a stand-alone WG: based on 
> experience, a dedicated/focus group is lighter and more efficient. So, 
> HIP is unchanged but all work done around HIP for TM-RID will end up 
> (like now) into HIP WG.
> 
> The TM-RID charter will have to be discussed in the BoF meeting in 
> Singapore and must include a privacy statement/work item. The IAB/IESG 
> feedback was also that the current charter is too much on HIP and would 
> like to explore whether other technologies (including layer-2 ones) 
> could be applicable.
> 
> All the above does not prevent the current work on TM-RID related drafts 
> of course.
> 
> So, let’s talk in Singapore at the BoF
> 
> -éric
> 
> *From: *Tm-rid <tm-rid-bounces@ietf.org> on behalf of Robert Moskowitz 
> <rgm@labs.htt-consult.com>
> *Date: *Friday, 4 October 2019 at 00:48
> *To: *"tm-rid@ietf.org" <tm-rid@ietf.org>
> *Subject: *Re: [Tm-rid] Draft charter
> 
> 
> 
> 
> 
> Updated charter:
> 
> Governmental agencies worldwide, including the United States Federal 
> Aviation Administration (FAA), are embarking on rule making processes to 
> define Remote Identification (RID) requirements for Unmanned Aircraft 
> Systems (UAS). ASTM International (formerly the American Society for 
> Testing and Materials) F38 Committee Work Item WK65041, “Standard 
> Specification for UAS Remote ID and Tracking”, addresses such 
> anticipated requirements. Broadcast RID defines a set of messages for 
> UAS to send one-way over Bluetooth or IEEE 802.11. Network RID defines 
> how the same information (and potentially more) can be made available 
> via the Internet. The ASTM draft does not address how to ensure or at 
> least assess trustworthiness of information communicated via RID.
> 
> The Host Identity Protocol (HIP) Host Identity Tag (HIT) is ideally 
> suited to work within this RID effort. For each Unmanned Aircraft (UA), 
> a HIT can consolidate the 4-tuple of (UA ID, UA physical location, UA 
> onboard host ID, UA onboard host logical location [IP address list]) to 
> a 3-tuple (HIT, UA physical location, UA onboard host logical location) 
> and thereby provide significant benefits.
> 
> For HIP to be used effectively in this environment, it needs updates.
> 
> - Hierarchical HITs (HHIT) enabling scalable and trustable registration: 
> HHIT was part of the original design of HIP, but was dropped for lack of 
> a clear use case. RID messages containing HHITs will enable use of DNS 
> to access information about the UAS.
> 
> - expanded HIP Registration for HHITs: This registration process will 
> provide proof of authenticity and prevent duplicate HHITs from 
> occurring. Further, these Registries will provide the UAS DNS 
> information and other services (including support of RVS for Network RID 
> and related applications).
> 
> - new cryptographic algorithms: Extremely compact keys and signatures 
> (such as are enabled by EdDSA and Keccak functions) are needed to meet 
> the severely constrained UAS environment.
> 
> Additionally, tm-rid will offer specifications for HIP-augmented ASTM 
> RID messages. Initially this will consist of additional RID 
> Authentication Messages that use the HI in public key signing 
> operations: to prove UAS ownership of the HHIT; to authenticate other 
> claims made via RID, such as position and velocity, as having been made 
> by the owner of that HHIT; and to provide observers lacking current 
> Internet connectivity with locally verifiable UAS proof-of-registration 
> objects.
> 
> Further work will emerge as experience is gained in using HIP for UAS 
> RID. For example, some UAS Traffic Management (UTM) systems envision 
> using OAuth for Ground Control Systems (GCS) and authorized safety 
> personnel. HIP as an OAuth method may help in merging HIP into these 
> systems.
> 
> The goal is to complete these updates to HIP by the end of 2020.
> 
>