Re: [Drip] my (Stu) review of -drip-arch-16
shuai zhao <shuai.zhao@ieee.org> Wed, 10 November 2021 21:39 UTC
Return-Path: <shuai.zhao@ieee.org>
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 535AC3A13F5 for <tm-rid@ietfa.amsl.com>; Wed, 10 Nov 2021 13:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=ieee.org
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 izrFeTLMKlva for <tm-rid@ietfa.amsl.com>; Wed, 10 Nov 2021 13:39:42 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 9E8D63A13F3 for <tm-rid@ietf.org>; Wed, 10 Nov 2021 13:39:42 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id h24so2624598pjq.2 for <tm-rid@ietf.org>; Wed, 10 Nov 2021 13:39:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=UpC8CI0ngBrweI/lwww4pmhmtddXHshfXz8e/oc4Exk=; b=dvMtXI1XlDG95Yz0T0tjKhXPjx7MnQA9cEi4hjBfMPkETN8ClNcRuOIc3ZHhJAUaW5 XcRJ3T3VX9PK7QTyF8suJfrLrN+mWFEg2aAeWByFU/2DmeFPEKaif2kE+DPmlfAZLaW5 HBHAeR62zltpkPTmwNYdM4XaVMsPRQuBlVZ8o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=UpC8CI0ngBrweI/lwww4pmhmtddXHshfXz8e/oc4Exk=; b=dvGMMHi3pSozQqmCKZifCZnYsDdUCSoi0FT0mcvH1kQE69tdumr+aczib9nYVfcIVZ xSZbhrLzRnUBSts59XpHBW8X4ANG5g0cltgXiKa1u8qM8S6Cok1jWzdixwTC31A8fMxJ ba0K1wRJtpCxH7aiJze4THQEDTCbQhwLQNe24LRQm0/lfC6FqP+AjuaLS/IGrYcNraqf P7iGkIz7+A7uvKXxXtMf17n4TEiT0iOw1hjm+A1Ksr0fkMarGKXgToUZzjnFSKNGjm2U GDlBxv7RH6BHPEL0ZMKm+7Njqj3Momk1vntIlDFc69QaK84tRAzM7DLO/etlooBv0ADo WvPw==
X-Gm-Message-State: AOAM532380YXQYnxJbioQWms6DYMrlgjDPzd2Ds/49iLVfSk5vSchFF8 0hYd82Jw/JUa4hV60CvlwCoj2/j80Jg/CQ==
X-Google-Smtp-Source: ABdhPJxIj04XEw3xzEsb1vDNIC2lSQX19z1kldy/gdLhHZfeYNcnW9+Ot5Pn1oCDvSbXn7Z5edP/+A==
X-Received: by 2002:a17:903:18d:b0:142:8ab:d11f with SMTP id z13-20020a170903018d00b0014208abd11fmr2532229plg.47.1636580380572; Wed, 10 Nov 2021 13:39:40 -0800 (PST)
Received: from smtpclient.apple ([2601:644:8c7f:f830:5570:9d0e:2b47:f378]) by smtp.gmail.com with ESMTPSA id p20sm566868pfw.96.2021.11.10.13.39.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Nov 2021 13:39:40 -0800 (PST)
From: shuai zhao <shuai.zhao@ieee.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0071B731-F603-45A3-BEDD-347B09959E80"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Wed, 10 Nov 2021 13:39:29 -0800
References: <b3a90e2b-e165-4902-4845-39f7dd72a441@axenterprize.com>
To: "Stuart W. Card" <stu.card@axenterprize.com>, tm-rid@ietf.org
In-Reply-To: <b3a90e2b-e165-4902-4845-39f7dd72a441@axenterprize.com>
Message-Id: <1A3C631F-4101-4171-A89C-7672FC97F6E3@ieee.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/1f3s3ny3U2jih2ICaiR2D0ghMt4>
Subject: Re: [Drip] my (Stu) review of -drip-arch-16
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Drone Remote Identification Protocol <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: Wed, 10 Nov 2021 21:39:47 -0000
Hi Stu and All, Revision -17 reflects the following updates > On Nov 8, 2021, at 10:42 PM, Stuart W. Card <stu.card@axenterprize.com> wrote: > > Section 1.1 EASA Paragraph is garbled: [Delegated] and [Implementing] don't make sense without the word "Regulations" after them; "unmanned aircraft systems" was previously spelled out so use "UAS". Shuai/ now implemented in revision -17 as follows: The EASA published a [Delegated] regulation in 2019 imposing requirements on UAS manufacturers and third-country operators, including but not limited to RID requirements. The EASA also published in 2019 an [Implementing] regulation laying down detailed rules and procedures for UAS operations and operating personnel. > > Section 1.2.1 spell out UA on 1st use (currently it is only expanded in parentheses on a later use). Shuai/ updated to "Broadcast RID provides information only about unmanned aircraft (UA)" > > Section 1.2.1 in last sentence, move 1st parenthetical notation "(see Section 7)" to replace 2nd parenthetical notation (list of examples, as better ones are given in Section 7). Shuai/ Bob proposed the following text: Broadcast RID provides information only about unmanned aircraft (UA) within direct RF LOS, typically similar to visual Light-Of-Sight (LOS), with a range up to approximately 1 km. This information may be 'harvested' from received broadcasts and made available via the Internet, enabling surveillance of areas too large for local direct visual observation or direct RF link based ID (see Section 7). Please let me know if that works for you. > > Section 1.2.2: definition of UAS does not belong here, but if one must be placed in this document, singular and plural forms need to agree; 2nd bullet claims UAS -> USS via a “secure internet connection” but F3411 specifies such a connection only between Net-RID SP & Net-RID DP; capitalize Internet. > Shuai/ 1.2.2. Network RID [F3411], using the same data dictionary that is the basis of Broadcast RID messages, defines a Network Remote Identification (Net- RID) data flow as follows. * The information to be reported via RID is generated by the UAS (typically some by the UA and some by the GCS, e.g. their respective GNSS derived locations). * The information is sent by the UAS (UA or GCS) via unspecified means to the cognizant Network Remote Identification Service Provider (Net-RID SP), typically the USS under which the UAS is operating if participating in UTM. * The Net-RID SP publishes via the Discovery and Synchronization Service (DSS) over the Internet that it has operations in various 4-D airspace volumes, describing the volumes but not the operations. * An Observer's device, expected typically but not specified to be web based, queries a Network Remote Identification Display Provider (Net-RID DP), typically also a USS, about any operations in a specific 4-D airspace volume. > Section 1.3 Figure 3 is confusing: the Observer _sees_ (or hears, or otherwise senses) UAS but does not _connect_ to them; the Observer can connect via the Internet to another USS (and thence via the DSS) for queries regarding the UAS. Shuai/ add "Editor-note-1: (Stu) re-draw this figure and propose text. Then double check the langauge in Editor-note-8" > > Section 1.4: most of the 1st paragraph belongs earlier in Section 1, before Sections 1.2 & 1.3; in our debates over figures this past summer, I think we agreed to replace this Figure 4 with the larger picture, which was deemed too detailed for Requirements but suitable for Architecture; "DNS:" -> "DNS"; need a line about authentication formats/protocols (after DNS etc., before "Harvesting"); need a line about Observer to Pilot (O2P) comms (after "Harvesting", before "Privacy"). Shuai/ updated as follows: 1) 1. Introduction This document describes an architecture for protocols and services to support Unmanned Aircraft System Remote Identification and tracking (UAS RID), plus RID-related communications. The architecture takes into account both current (including proposed) regulations and non- IETF technical standards. The architecture adheres to the requirements listed in the DRIP Requirements document [I-D.ietf-drip-reqs]. The requirements document provides an extended introduction to the problem space and use cases. 1.4. Overview of DRIP Architecture Figure 4 illustrate a brief summary of the general UAS RID usage scenarios in DRIP. 2). - Mechanisms to leverage Domain Name System (DNS [RFC1034]), Extensible Provisioning Protocol (EPP [RFC5731]) and Registration Data Access Protocol (RDAP) ([RFC7482]) for publishing public and private information (see Section 5.1 and Section 5.2). - Specific authentication methods and message payload formats to enable verification that Broadcast RID messages were sent by the claimed sender (Section 6) and that sender is in the claimed registry (Section 5 and Section 6). - Harvesting broadcast RID messages for UTM inclusion (Section 7). - Methods for instantly establishing secure communications between an Observer and the pilot of an observed UAS (Section 8). - Privacy in RID messages (PII protection) (Section 11). 3) the rest is implemented as suggested. > > Section 2 let’s define only acronyms, terms, etc. not defined in the Requirements document. Shuai/ Updated 2.2. Abbreviations EdDSA: Edwards-Curve Digital Signature Algorithm HHIT: Hierarchical HIT HIP: Host Identity Protocol HIT: Host Identity Tag 2.3. Additional Definitions > > Section 4.3 oops, sorry, my typo, “second pre-image attach” -> “second pre-image attack” Shuai/ Updated. > > Section 5 needs to cite the corresponding numbered requirement[s] that it supports. Shuai/ Added Editor-note-4: Section 5 needs to cite the corresponding numbered requirement that it supports.” > > Section 6 doesn’t use the word “authentication” in the section title, is there a reason to avoid it? Shuai/ Added Editor-note-5: Section 6 doesn't use the word "authentication" in the section title, is there a reason to avoid it?" > > Section 7 needs to cite the corresponding numbered requirement[s] that it supports. Shuai/ added Editor-note-6: Section 7 needs to cite the corresponding numbered requirement that it supports. " > > Section 7.2 order of sentences should be reversed, to first introduce the purpose of the CS-RID SDSP, then specify its interface. Shuai/ updated. A CS-RID SDSP aggregates and processes (e.g., estimates UA location using including using multilateration when possible) information collected by CS-RID Finders. A CS-RID SDSP should appear (i.e. present the same interface) to a Net-RID SP as a Net-RID DP. Editor-note-8: double check above paragraph after Editor-note-1 is resolved. > > Section A needs some tweaking to be standard English grammar, punctuation and style. Shuai/ Updated > > Section A.2 "fly rules" is non-standard terminology. Shuai/ Updated The LAANC program can automate the UAS operational intent (flight plan) submission and application for airspace authorization in real-time by checking against multiple aeronautical databases such as airspace classification and operating rules associated with it, FAA UAS facility map, special use airspace, Notice to Airmen (NOTAM), and Temporary Flight Restriction (TFR). > > Suggested replacement text blurbs to follow soon. > > -- > ----------------------------------------- > Stuart W. Card, PhD, Principal Engineer > AX Enterprize, LLC www.axenterprize.com > 4947 Commercial Drive, Yorkville NY 13495
- Re: [Drip] my (Stu) review of -drip-arch-16 shuai zhao