Re: [Tm-rid] Draft charter
Robert Moskowitz <rgm@labs.htt-consult.com> Thu, 03 October 2019 22:48 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 CC9AB1200FB for <tm-rid@ietfa.amsl.com>; Thu, 3 Oct 2019 15:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 BxKlpmZRoiLP for <tm-rid@ietfa.amsl.com>; Thu, 3 Oct 2019 15:48:08 -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 3252D120059 for <tm-rid@ietf.org>; Thu, 3 Oct 2019 15:48:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id D1FF96211F for <tm-rid@ietf.org>; Thu, 3 Oct 2019 18:48:06 -0400 (EDT)
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 w0jA9SXvZtxq for <tm-rid@ietf.org>; Thu, 3 Oct 2019 18:47:59 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 3DCC662116 for <tm-rid@ietf.org>; Thu, 3 Oct 2019 18:47:57 -0400 (EDT)
From: Robert Moskowitz <rgm@labs.htt-consult.com>
To: "tm-rid@ietf.org" <tm-rid@ietf.org>
References: <0fc9d954-a9af-b590-afb2-64ad2594f552@labs.htt-consult.com>
Message-ID: <d9b29364-c5ec-0391-6acf-10b15410855c@labs.htt-consult.com>
Date: Thu, 03 Oct 2019 18:47:53 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0
MIME-Version: 1.0
In-Reply-To: <0fc9d954-a9af-b590-afb2-64ad2594f552@labs.htt-consult.com>
Content-Type: multipart/alternative; boundary="------------6A4FE3C3E19EF01AFDCFAF82"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/-t-nQxfhgm9JSKhSZD0uZe3rZ40>
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, 03 Oct 2019 22:48:13 -0000
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.
- [Tm-rid] Draft charter Robert Moskowitz
- Re: [Tm-rid] Draft charter Eric Vyncke (evyncke)
- Re: [Tm-rid] Draft charter Robert Moskowitz
- Re: [Tm-rid] Draft charter Eric Vyncke (evyncke)
- Re: [Tm-rid] Draft charter Henk Birkholz
- Re: [Tm-rid] Draft charter Robert Moskowitz
- Re: [Tm-rid] Draft charter Card, Stu
- Re: [Tm-rid] Draft charter Robert Moskowitz
- Re: [Tm-rid] Draft charter Eric Vyncke (evyncke)
- Re: [Tm-rid] Draft charter Robert Moskowitz
- Re: [Tm-rid] Draft charter Card, Stu
- Re: [Tm-rid] Draft charter Eric Vyncke (evyncke)