Re: [Tm-rid] Making progress to the TMRID charter

"Card, Stu" <stu.card@axenterprize.com> Thu, 06 February 2020 16:07 UTC

Return-Path: <stu.card@axenterprize.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 E915A12098C for <tm-rid@ietfa.amsl.com>; Thu, 6 Feb 2020 08:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=axenterprize.com
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 NAZV3RnwkOig for <tm-rid@ietfa.amsl.com>; Thu, 6 Feb 2020 08:07:37 -0800 (PST)
Received: from mail-yw1-xc2f.google.com (mail-yw1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C5D7120943 for <tm-rid@ietf.org>; Thu, 6 Feb 2020 08:07:37 -0800 (PST)
Received: by mail-yw1-xc2f.google.com with SMTP id n184so5313681ywc.3 for <tm-rid@ietf.org>; Thu, 06 Feb 2020 08:07:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=axenterprize.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ODrVcys38uO59bCkUgvmpmgzBHoNyVa+UKQH3CGs43k=; b=KfbL+31PDVeoqg4UsTOYfKmI/tqHD+jcTsNummIT8pHn0bsKUW4ZIE0kNG15cnhHms zi5tOzBf5vl41KctgYIkHYSDb93pdUUsbcHphyTt34vrLn9qZO4Nwt08VycwsN9HrBUy pjSy/4dSFCfUv8t4t/wIIOxRmfgnOqaxp9Hdg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ODrVcys38uO59bCkUgvmpmgzBHoNyVa+UKQH3CGs43k=; b=OgBsmlyibmJbzdRZkes2/PZkrlk7me2Bmi1vTkY33yVd8c6DXptLQyUxkfVgpR/TQ8 paWXTiz6yS4lNQOqyHQSvRE9YW/1OnAZXiZ8MJgFPlmA9t9sU627HCk88P+kaSEdo89A uG9mJgNOrlKAMxCE3VNMaSlpTPoUqBnsWJKgD4Mc32kgzbZjLIJ6Fe18X78bf4i9QcZM AGLGlN/HAlaFlrggTxxchfRCtN8iy48bs+bqUyI5RkE4ykFgwL/HPUGQ44uybuqC8DBF gKn8BILztj2ckD4U1WYmOMn6SxlyBAgNG+wF8hWTm4sJGs+VEaJ/7C0TKbRtBErRjuox Ih8w==
X-Gm-Message-State: APjAAAUKMRRJinHAmS6SfDoPH5MWBe2IFWv/0A2JfNHpNSV1qGlJ9C2P aopaKwB14SDO7Gd9K1hx3nmCOjobt/qWp60ryDHknQ==
X-Google-Smtp-Source: APXvYqzdyZgoKAnAZZNqQev1XpL1n9Qc8r7xUBQPG3tIpPR/GMvIbSFQflnTlqstttcjYaaZueiLLuDujn1EDJ6fZgw=
X-Received: by 2002:a0d:e210:: with SMTP id l16mr3659593ywe.501.1581005254689; Thu, 06 Feb 2020 08:07:34 -0800 (PST)
MIME-Version: 1.0
References: <B84AF561-BD9E-4C62-81AD-F8C7643B6002@cisco.com>
In-Reply-To: <B84AF561-BD9E-4C62-81AD-F8C7643B6002@cisco.com>
From: "Card, Stu" <stu.card@axenterprize.com>
Date: Thu, 06 Feb 2020 11:07:18 -0500
Message-ID: <CAKM0pYM_MYqvxOj8GLsZOuNcszGvYtmyfFw75EUCDWqkgr2vRA@mail.gmail.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: tm-rid@ietf.org, Magnus Westerlund <magnus.westerlund@ericsson.com>, Benjamin Kaduk <kaduk@mit.edu>
Content-Type: multipart/alternative; boundary="000000000000982119059dea78d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/z2rLx6hn683R4yrvvukYJS_seY0>
Subject: Re: [Tm-rid] Making progress to the TMRID 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, 06 Feb 2020 16:07:46 -0000

Clarification: "This specification defines the baseline design,
construction, and verification requirements for an UAS" needs "RID system"
appended, as the cited ASTM standard is exclusively about RID, not any
other aspect of UAS.

On Thu, Feb 6, 2020, 10:54 Eric Vyncke (evyncke) <evyncke@cisco.com> wrote:

> There was some discussions among the IESG, IAB and TM-RID BoF chairs about
> the charter during today IESG telechat. The latest version is below but we
> need to wait until Monday when Magnus will have time to review it and
> probably clear his BLOCK (Ben has promised to have a look at the revised
> draft before our interim meeting).
>
>
>
> Let’s discuss it later today.
>
>
>
> -éric
>
>
>
> ----
>
> Civil Aviation Authorities (CAAs) worldwide have initiated rule making for
> Unmanned Aircraft Systems (UAS) Remote Identification (RID). CAAs currently
> promulgate performance-based regulations that do not mandate specific
> techniques, but rather cite industry-consensus technical standards as
> acceptable means of compliance. One key standard is ASTM (formerly the
> American Society for Testing and Materials) WK65041 [1]. This specification
> defines the baseline design, construction, and verification requirements
> for an UAS. Network RID defines a set of information for UAS to make
> available globally via the Internet. Broadcast RID defines a set of
> messages for UAS to send locally one-way over Bluetooth or Wi-Fi. But
> WK65041 does not address how to populate/query registries, how to ensure
> trustworthiness of information, nor how to make the information useful.
>
>
>
> TMRID’s goal is to specify how RID can be made available in both Internet
> and local-only connected scenarios, especially in emergency situations.
> Some UAS operate in environments where the network or the devices or both
> are severely constrained [2] in terms of processing, bandwidth (e.g.,
> Bluetooth 4 packet is 21 byte long), or battery life, and TMRID aims to
> function in these environments. The specifications produced by the WG will
> need to balance public safety authorities’ need to know trustworthy
> information with UAS operators’ privacy.
>
>
>
> The working group will primarily leverage Internet standards (including
> HIP, EPP, RDAP and DNS) and infrastructure as well as domain name
> registration business models. The WG will track the requirements being
> developed by regulatory authorities including the US Federal Aviation
> Administration (US FAA) and the European Union Civil Aviation Authority
> CAA) and will aim to align with those requirements (e.g., [3]).
>
>
>
> The working group will work on the following items:
>
> * Requirements: The WG is expected to provide an information document that
> lists the requirements the UAS Remote Identification (UAS RID) - that is
> the system for identifying UA during flight by other parties must meet.
> Requirements will also include those associated to the UAS Identifier that
> need to both meet some constraints as well as some specific properties.
>
> * Architecture: The WG will propose a standard document that describes the
> architecture that address the requirements and that will re-use protocols
> or architectures already standardized at the IETF.
>
> * Protocol design: While the primary purpose of TM-RID WG is to leverage
> on existing protocols, the specificities of the UAS environment is likely
> to require existing protocols to be extended or new protocols to be
> designed. The WG will be focused on standardizing this protocols or
> extensions.
>
>
>
> List of candidate drafts:
>
> - draft-card-tmrid-uas-reqs
>
> - draft-card-tmrid-uas-arch
>
> - draft-wiethuechter-tmrid-auth
>
> - draft-moskowitz-hip-new-crypto
>
> - draft-moskowitz-orchid-cshake
>
> - draft-moskowitz-hip-hierarchical-hit
>
> - draft-moskowitz-hip-hhit-registries
>
>
>
> References:
>
> [1] ASTM International F38 Committee Work Item WK65041 “Standard
> Specification for UAS Remote ID and Tracking”
> https://www.astm.org/DATABASE.CART/WORKITEMS/WK65041.htm
>
> [2] UAS Identification and Tracking Aviation Rulemaking Committee
> Recommendations Final Report 2017 SEP 30
> https://www.faa.gov/regulations_policies/rulemaking/committees/documents/media/UAS%20ID%20ARC%20Final%20Report%20with%20Appendices.pdf
>
> [3]
> https://www.federalregister.gov/documents/2019/12/31/2019-28100/remote-identification-of-unmanned-aircraft-systems
>
> ----
> --
> Tm-rid mailing list
> Tm-rid@ietf.org
> https://www.ietf.org/mailman/listinfo/tm-rid
>