[Tm-rid] Draft charter
Robert Moskowitz <rgm@labs.htt-consult.com> Fri, 27 September 2019 14:53 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 28F09120819 for <tm-rid@ietfa.amsl.com>; Fri, 27 Sep 2019 07:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 B8bOTW7x62fw for <tm-rid@ietfa.amsl.com>; Fri, 27 Sep 2019 07:53:51 -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 B4904120817 for <tm-rid@ietf.org>; Fri, 27 Sep 2019 07:53:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 84145615FA for <tm-rid@ietf.org>; Fri, 27 Sep 2019 10:53:50 -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 h+e35eMMyzCv for <tm-rid@ietf.org>; Fri, 27 Sep 2019 10:53:44 -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 231AB60029 for <tm-rid@ietf.org>; Fri, 27 Sep 2019 10:53:44 -0400 (EDT)
To: "tm-rid@ietf.org" <tm-rid@ietf.org>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
Message-ID: <0fc9d954-a9af-b590-afb2-64ad2594f552@labs.htt-consult.com>
Date: Fri, 27 Sep 2019 10:53:38 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/fGJZpsNlRc1-EbAtKCbYbAxiw1Q>
Subject: [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: Fri, 27 Sep 2019 14:53:54 -0000
Here is my first attempt at a charter for tm-rid. It will be up to our AD and HIP chairs if tm-rid is a standalone effort, or if this charter will be melded into a revised charter for additional HIP work. Here goes: The Federal Aviation Administration (FAA) Unmanned Aircraft Systems (UAS) Identification (ID) and Tracking Aviation Rulemaking Committee (ARC) (UAS-ID ARC) made recommendations to the FAA regarding technologies available for remote identification and tracking of UAS. The ARC recommended two modalities for remote identification, “broadcast” and “network”. “Broadcast” would require UAS to transmit information without bi-directional communication with a receiver. “Network” would require UAS to communicate information to a network such as UTM (Unmanned Aircraft Traffic Management). The ASTM (American Society for Testing and Materials) F38 Committee on UAS has been working on an industry consensus standard for Remote ID (RID) and Tracking, WK65041. They have defined a set of messages for UAS to send over Bluetooth Beacon Advertisements or IEEE 802.11 Neighborhood Area Network (NAN) to meet the FAA requirements. The Host Identity Tag (HIT) of HIP is ideally suited to work within this Boradcast RemoteID effort. HITs 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). For HIP to be used effectively in this environment, it needs updates for: Hierarchical HITs (HHIT) to provide a direct registry of HITs. HHIT was part of the original design of HIP, but was dropped for lack of a clear use case. With HHITs, RemoteID messages containing HHITs will provide the information to use DNS to access information about the UAS. Expanded HIP Registration to support registration of a UAS HHIT in a Registry. 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, potentially, RVS for future FAA NetworkID effort). New cryptographic algorithms (e.g. EdDSA and Keccak functions) to meet the UAS constrained environment. Additionally, the ASTM RemoteID messages will be augmented for use with HIP. Initially this will consist of additional RemoteID Authentication Messages that will use the HI in a public key signing operation to prove UAS ownership of the HHIT and provide ground-listeners proof of registration objects for safe UAS operation when ground-listeners do not have Internet access. Further work will emerge as experience is gained in using HIP for UAS RemoteID. For example, some UTM systems envision using OATH for GCS (Ground Control Systems) and authorized safety personnel. HIP as an OATH 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)