Re: [Tm-rid] Alissa Cooper's No Objection on charter-ietf-drip-00-01: (with COMMENT)

Robert Moskowitz <rgm@htt-consult.com> Mon, 24 February 2020 13:39 UTC

Return-Path: <rgm@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 E248C3A0B64; Mon, 24 Feb 2020 05:39:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 Ga4uZMYRKh-H; Mon, 24 Feb 2020 05:39:17 -0800 (PST)
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 21E9D3A0B59; Mon, 24 Feb 2020 05:39:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id C6C2E62123; Mon, 24 Feb 2020 08:39:13 -0500 (EST)
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 VkfvV-yQnD2j; Mon, 24 Feb 2020 08:39:01 -0500 (EST)
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 3AED56211E; Mon, 24 Feb 2020 08:39:01 -0500 (EST)
To: "Card, Stu" <stu.card@axenterprize.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: "drip-chairs@ietf.org" <drip-chairs@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>, "tm-rid@ietf.org" <tm-rid@ietf.org>, Adam Wiethuechter <Adam.Wiethuechter@axenterprize.com>, "Da Silva, Saulo" <Sdasilva@icao.int>
References: <158217542781.17775.11240749461767725731.idtracker@ietfa.amsl.com> <471CDB97-3D49-470D-8201-194508365E8C@cisco.com> <FE3106DE-5D28-4DC3-8D1D-D61CD3787DFD@cisco.com> <CA+r8TqXjhftzCcP-hxdffnaG54LVWz776hPDdx9gXnGhXC48tg@mail.gmail.com> <84219182-424F-4FF3-9BD5-64517765B9EF@cisco.com> <CA+r8TqUXFYZPvy56OnUaGv+fHZ+j1PCd+DPX8KiZ4v8o=orAVQ@mail.gmail.com> <CAKM0pYOpF7+_WFENkgfA-FAuwEkEjZc_ELfsRhSbShbTAtyrMQ@mail.gmail.com>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <f1f177ba-d1eb-dd88-1e90-e04253a8cf99@htt-consult.com>
Date: Mon, 24 Feb 2020 08:38:58 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <CAKM0pYOpF7+_WFENkgfA-FAuwEkEjZc_ELfsRhSbShbTAtyrMQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------9814746A13990867C901610E"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/JjBBooNXZPP40jTs4Utcu_gUmNU>
Subject: Re: [Tm-rid] Alissa Cooper's No Objection on charter-ietf-drip-00-01: (with COMMENT)
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: Mon, 24 Feb 2020 13:39:20 -0000

Stu,

Mailing list changes are done by the IETF admin and we will be notified 
of the change.  It will occur, most likely, when Eric finishes all your 
prior points.  :)

On 2/24/20 8:32 AM, Card, Stu wrote:
> Did Saulo DaSilva's suggestion about adding ICAO along with FAA and 
> EASA make the cut?
> Did Adam's proposed sentence clarifying UAS RID identifier properties 
> satisfy everyone?
> Does our charter now address all of the points that the commenters and 
> IESG wanted?
> IOW, is our charter now fully accepted, so that our WG is not merely 
> _conditionally_ approved?
> If so, should we move our mailing list from tm-rid@ietf.org 
> <mailto:tm-rid@ietf.org> to drip@ietf.org <mailto:drip@ietf.org>?
>
>
> On Fri, Feb 21, 2020 at 5:20 PM Wiethuechter, Adam 
> <adam.wiethuechter@axenterprize.com 
> <mailto:adam.wiethuechter@axenterprize.com>> wrote:
>
>     OLD: "These requirements will also include those associated to the
>     UAS Identifier that need to both meet some constraints as well as
>     some specific properties."
>
>     NEW: "These requirements also include showing that new or adapted
>     identifiers from existing protocols conform and meet the
>     specifications to be certified as a UAS ID."
>
>     How is this everyone?
>
>     On Fri, Feb 21, 2020 at 5:13 PM Eric Vyncke (evyncke)
>     <evyncke@cisco.com <mailto:evyncke@cisco.com>> wrote:
>
>         Adam
>
>         Would you mind proposing a sentence to replace the existing one ?
>
>         *From: *"Wiethuechter, Adam"
>         <adam.wiethuechter@axenterprize.com
>         <mailto:adam.wiethuechter@axenterprize.com>>
>         *Date: *Friday, 21 February 2020 at 23:10
>         *To: *Eric Vyncke <evyncke@cisco.com <mailto:evyncke@cisco.com>>
>         *Cc: *"tm-rid@ietf.org <mailto:tm-rid@ietf.org>"
>         <tm-rid@ietf.org <mailto:tm-rid@ietf.org>>,
>         "drip-chairs@ietf.org <mailto:drip-chairs@ietf.org>"
>         <drip-chairs@ietf.org <mailto:drip-chairs@ietf.org>>, Michael
>         Richardson <mcr+ietf@sandelman.ca
>         <mailto:mcr%2Bietf@sandelman.ca>>, Robert Moskowitz
>         <rgm@htt-consult.com <mailto:rgm@htt-consult.com>>
>         *Subject: *Re: [Tm-rid] Alissa Cooper's No Objection on
>         charter-ietf-drip-00-01: (with COMMENT)
>
>         This (the second point) is mentioning that the UAS Identifier
>         has its own set of constraints and properties that it must
>         hold - defined and regulated by parties outside the IETF. For
>         example UAS IDs are constrained to 20 bytes.
>
>         So the requirements documents produced by the WG will also
>         specify other identifiers, created new or adapted from an
>         existing protocol (this is exactly with the HHITs are from
>         HIP), that conform and meet the specifications to be certified
>         as a UAS ID.
>
>         Probably not the exact words to use, but I think it clears up
>         the confusion?
>
>         On Fri, Feb 21, 2020 at 4:48 PM Eric Vyncke (evyncke)
>         <evyncke@cisco.com <mailto:evyncke@cisco.com>> wrote:
>
>             Any taker to answer Alissa's second point ? about what is
>             the subject (see below) ?
>
>             I would have loved to finalize the charter this week and
>             this is the only open point left before approval
>
>             -éric
>
>             On 20/02/2020, 10:28, "Tm-rid on behalf of Eric Vyncke
>             (evyncke)" <tm-rid-bounces@ietf.org
>             <mailto:tm-rid-bounces@ietf.org> on behalf of
>             evyncke@cisco.com <mailto:evyncke@cisco.com>> wrote:
>
>                 Alissa and Ben,
>
>                 Thank you for your comments and let's work to fix all
>             ambiguities...
>
>                 TM-RID list members can you please comment on Alissa &
>             Ben's reviews ?
>                 - Alissa: we need to expand UAS as "Unmanned Aircraft
>             System" at first use even if only to avoid being ambiguous
>                 - Alissa: what is the subject of the "need to": is it
>             "these requirements" or "those associated to the UAS
>             identifier" or "UAS identifier", let's be clear on this
>                 - Ben: indeed milestone are quite optimistic...
>             adoption should be target and request for publication 6
>             month later ?
>                 - Ben: should RID be trustworthy (my guess is yes of
>             course as this is the main purpose of this group)
>
>                 The DRIP charter will be reviewed today at 15H00 UTC,
>             so, a prompt reply from the proponents of the list will be
>             appreciated
>
>                 -éric
>
>                 On 20/02/2020, 06:10, "Tm-rid on behalf of Alissa
>             Cooper via Datatracker" <tm-rid-bounces@ietf.org
>             <mailto:tm-rid-bounces@ietf.org> on behalf of
>             noreply@ietf.org <mailto:noreply@ietf.org>> wrote:
>
>                     Alissa Cooper has entered the following ballot
>             position for
>                     charter-ietf-drip-00-01: No Objection
>
>                     When responding, please keep the subject line
>             intact and reply to all
>                     email addresses included in the To and CC lines..
>             (Feel free to cut this
>                     introductory paragraph, however.)
>
>
>
>                     The document, along with other ballot positions,
>             can be found here:
>             https://datatracker.ietf.org/doc/charter-ietf-drip/
>
>
>
>             ----------------------------------------------------------------------
>                     COMMENT:
>             ----------------------------------------------------------------------
>
>                     Two questions about this:
>
>                     "* Requirements: the WG is expected to provide an
>             informational document that
>                     lists the technical requirements for applying IETF
>             protocols to the UAS Remote
>                     Identification (UAS RID) - that is the system for
>             identifying UA during flight
>                     by other parties. These requirements will also
>             include those associated to the
>                     UAS Identifier that need to both meet some
>             constraints as well as some specific
>                     properties."
>
>                     Is UA distinct from UAS?
>
>                     The last sentence doesn't parse properly for me.
>             What is the subject of "need
>                     to"? Is this saying "requirements ... need to ...
>             meet some constraints ...
>                     [and meet] some specific properties"? What does
>             that mean?
>
>
>                     --
>                     Tm-rid mailing list
>             Tm-rid@ietf.org <mailto:Tm-rid@ietf.org>
>             https://www.ietf.org/mailman/listinfo/tm-rid
>
>
>                 --
>                 Tm-rid mailing list
>             Tm-rid@ietf.org <mailto:Tm-rid@ietf.org>
>             https://www.ietf.org/mailman/listinfo/tm-rid
>
>
>             -- 
>             Tm-rid mailing list
>             Tm-rid@ietf.org <mailto:Tm-rid@ietf.org>
>             https://www.ietf.org/mailman/listinfo/tm-rid
>
>
>
>         -- 
>
>         73's,
>
>         Adam T. Wiethuechter
>
>         AX Enterprize, LLC
>
>
>
>     -- 
>     73's,
>     Adam T. Wiethuechter
>     AX Enterprize, LLC
>
>     -- 
>     Tm-rid mailing list
>     Tm-rid@ietf.org <mailto:Tm-rid@ietf.org>
>     https://www.ietf.org/mailman/listinfo/tm-rid
>