[saag] tm-rid -- Trustworthy Multipurpose RemoteID
Robert Moskowitz <rgm-sec@htt-consult.com> Thu, 25 July 2019 15:18 UTC
Return-Path: <rgm-sec@htt-consult.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D69E6120071 for <saag@ietfa.amsl.com>; Thu, 25 Jul 2019 08:18:20 -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, 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 Sm6eL8w7UFsx for <saag@ietfa.amsl.com>; Thu, 25 Jul 2019 08:18:18 -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 8DB5112006D for <saag@ietf.org>; Thu, 25 Jul 2019 08:18:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 56B1560945 for <saag@ietf.org>; Thu, 25 Jul 2019 11:18:17 -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 FYAYfSPZkPsu for <saag@ietf.org>; Thu, 25 Jul 2019 11:18:10 -0400 (EDT)
Received: from lx140e.htt-consult.com (dhcp-914c.meeting.ietf.org [31.133.145.76]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 51A156080C for <saag@ietf.org>; Thu, 25 Jul 2019 11:18:10 -0400 (EDT)
To: 'saag' <saag@ietf.org>
From: Robert Moskowitz <rgm-sec@htt-consult.com>
Message-ID: <1686af36-615d-4873-3942-61fd350a24fb@htt-consult.com>
Date: Thu, 25 Jul 2019 11:17:54 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.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/saag/5xcbFf_RbfxAUrFE7fWkDKsqPaI>
Subject: [saag] tm-rid -- Trustworthy Multipurpose RemoteID
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2019 15:18:21 -0000
This effort will be in INT, but has a lot of security components (read: Trustworthy) The slides from the side meeting are at: https://trac.ietf.org/trac/ietf/meeting/attachment/wiki/105side-slides/ Here is a brief about the initial work in tm-rid: ----------------------------------------------------------------------- Thanks to the FAA stating that they plan on the initial rule making on RemoteID for UAS in September, 2019, the initial work on tm-rid is extremely accelerated. My understanding is if we have initial draft documents we will then have some time for official RFCs. There will also need to be some level of interaction with ATSM that has been generating RemoteID standards. See: https://github.com/opendroneid/specs The IETF MAY desire to enter into an MOU with ATSM. ATSM may want it also. Note that ATSM claims to be the oldest SDO around. The work (drafts) I see are listed below. A charter for this effort SHOULD be within the 1st draft listed. I will be working with Stu and Adam on a charter that we will display somewhere given that we are pre-BOF here. We are looking for people interested in writing/reviewing. ====================== Initial Drafts ======================== Trustworthy Multipurpose Remote IDs in UAS draft-tm-rid-uas Abstract: This memo defines the use of Host Identity Tags (HIT) from the Host Identity Protocol (HIP) that can provide a self-asserting trustable identity for Unmanned Aircraft Systems (UAS). The justification for trust in the IDs, generation and registration of HITs, and use of HITs in UAS messages. Trustworthy Multipurpose Remote IDs in Discovery Services draft-tm-rid-uas-ds Abstract: This memo defines HIT based Discovery Services to obtain both static and dynamic information about UASs. These services will implement access policy rules to limit what different entities can learn and control of the UASs. Hierarchical HITs for HIP draft-tm-rid-hierarchical-hip Abstract: This document describes the structure of hierarchical HITs to facilitate large deployments in mobile networks. Registration Services for Hierarchical HITs draft-tm-rid-hierarchical-hip-registration Abstract: This document describes the registration of hierarchical HITs (HHIT). It provides for registrar entities and how they can be found. It does not describe the policies that registrars must meet as HHIT registrars. It may reference RFC7451. New crypto for HIP draft-moskowitz-hip-crypto-update Abstract: This document adds support for new cryptographic algorithms and methods to HIP. e.g. EDDSA, KMAC, cSHAKE, SHA-3, Kedje. Note that Kedje is a sort of placeholder as NIST is still working on the 'small' cypher that we want for this project. CBOR formats for HIP draft-tm-rid-hip-cbor Abstract: This document replaces the HIP TLV structures with CBOR CTW. HIP as OAUTH method draft-tm-rid-hip-oauth Abstract: This document adds support of HIP as an OAUTH method ============================================ Thank you
- [saag] tm-rid -- Trustworthy Multipurpose RemoteID Robert Moskowitz