Re: [Drip] I-D Action: draft-ietf-drip-auth-40.txt

Robert Moskowitz <rgm@labs.htt-consult.com> Fri, 17 November 2023 14:59 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 C2448C151068 for <tm-rid@ietfa.amsl.com>; Fri, 17 Nov 2023 06:59:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.205
X-Spam-Level:
X-Spam-Status: No, score=-4.205 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iiWMjem9Uh-5 for <tm-rid@ietfa.amsl.com>; Fri, 17 Nov 2023 06:59:24 -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 BC397C14CE39 for <tm-rid@ietf.org>; Fri, 17 Nov 2023 06:59:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 93BF362769; Fri, 17 Nov 2023 09:58:43 -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 O9YY+V-X++dU; Fri, 17 Nov 2023 09:58:30 -0500 (EST)
Received: from [192.168.160.29] (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id D21FD62569; Fri, 17 Nov 2023 09:58:27 -0500 (EST)
Content-Type: multipart/alternative; boundary="------------upoxVYjhIIpplpI6rQeiroUH"
Message-ID: <97d3e82f-3a49-46d7-96d0-a7b2bf94b658@labs.htt-consult.com>
Date: Fri, 17 Nov 2023 09:59:04 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: Adam Wiethuechter <adam.wiethuechter@axenterprize.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "tm-rid@ietf.org" <tm-rid@ietf.org>
References: <169999366067.5911.11221182236709295111@ietfa.amsl.com> <SN6PR13MB2446D41CC5FF75B1D39F67D288B2A@SN6PR13MB2446.namprd13.prod.outlook.com> <7fc62959-3b46-45e0-995b-19395a24bab1@labs.htt-consult.com> <DU2PR02MB10160878575F6CA708211DD2088B1A@DU2PR02MB10160.eurprd02.prod.outlook.com> <SN6PR13MB2446C890D49AD53D33ECFF8288B0A@SN6PR13MB2446.namprd13.prod.outlook.com>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
In-Reply-To: <SN6PR13MB2446C890D49AD53D33ECFF8288B0A@SN6PR13MB2446.namprd13.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/8gP9nWxswrLdCU3uGrLTEyDtZ0M>
Subject: Re: [Drip] I-D Action: draft-ietf-drip-auth-40.txt
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 17 Nov 2023 14:59:28 -0000

Yes, that is the section.

At best see if there is some text from the req or arch RFCs. Otherwise 
just drop this pointer.

Charters change.  Look over at MLS as they debate what to change. There 
is no tracking of charters, maybe there should, but there isn't.  ERGO 
don't site them.

On 11/16/23 15:11, Adam Wiethuechter wrote:
> Bob is referring to this specific line:
>
> "DRIP’s goal is to specify how RID can be made trustworthy and 
> available in both Internet and local-only connected scenarios, 
> especially in emergency situations."
>
> Which is directly lifted from the current charter without citation.
>
> I agree with Med that there is no need for a pointer to the charter 
> (especially if it changes).
>
> --------
> 73,
> Adam T. Wiethuechter
> Software Engineer; AX Enterprize, LLC
> ------------------------------------------------------------------------
> *From:* mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>
> *Sent:* Wednesday, November 15, 2023 3:47 AM
> *To:* Robert Moskowitz <rgm@labs.htt-consult.com>; Adam Wiethuechter 
> <adam.wiethuechter@axenterprize.com>; tm-rid@ietf.org <tm-rid@ietf.org>
> *Subject:* RE: [Drip] I-D Action: draft-ietf-drip-auth-40.txt
>
> Hi Bob,
>
> Can you please indicate which part of the text are you referring to? 
> Thanks.
>
> If you are referring to the last sentence of the first para in that 
> section, I don’ think we need a pointer to the charter.
>
> Cheers,
>
> Med
>
> *De :* Tm-rid <tm-rid-bounces@ietf.org> *De la part de* Robert Moskowitz
> *Envoyé :* mardi 14 novembre 2023 22:01
> *À :* Adam Wiethuechter <adam.wiethuechter@axenterprize.com>; 
> tm-rid@ietf.org
> *Objet :* Re: [Drip] I-D Action: draft-ietf-drip-auth-40.txt
>
> Just one comment on going through the diffs.
>
> The Introduction refers to the wg charter.  Last week we were 
> discussing rechartering...
>
> How is it handled in various workgroups, pointing to text in the 
> charter which may change at later readings?  There is no history of wg 
> charter evolution as there are for expired drafts.   Is it good to 
> reference charter content?
>
> Chairs, AD?  what is the recommended style here.
>
>
> On 11/14/23 15:30, Adam Wiethuechter wrote:
>
>     All,
>
>     This -40 should be closing all issues in the GitHub and be ready
>     for submission to IESG.
>
>     I believe it would be wise that we quickly check to ensure the use
>     of the words "verification" and "validation" throughout the
>     document. This is after a personal comment from Stu from his
>     experience witnessing confusion last week in ICAO/ASTM of these terms.
>
>     --------
>
>     73,
>
>     Adam T. Wiethuechter
>
>     Software Engineer; AX Enterprize, LLC
>
>     ------------------------------------------------------------------------
>
>     *From:*Tm-rid <tm-rid-bounces@ietf.org>
>     <mailto:tm-rid-bounces@ietf.org> on behalf of
>     internet-drafts@ietf.org <internet-drafts@ietf.org>
>     <mailto:internet-drafts@ietf.org>
>     *Sent:* Tuesday, November 14, 2023 3:27 PM
>     *To:* i-d-announce@ietf.org <i-d-announce@ietf.org>
>     <mailto:i-d-announce@ietf.org>
>     *Cc:* tm-rid@ietf.org <tm-rid@ietf.org> <mailto:tm-rid@ietf.org>
>     *Subject:* [Drip] I-D Action: draft-ietf-drip-auth-40.txt
>
>     Internet-Draft draft-ietf-drip-auth-40.txt is now available. It is
>     a work item
>     of the Drone Remote ID Protocol (DRIP) WG of the IETF.
>
>        Title:   DRIP Entity Tag Authentication Formats & Protocols for
>     Broadcast Remote ID
>        Authors: Adam Wiethuechter
>                 Stuart Card
>                 Robert Moskowitz
>        Name:    draft-ietf-drip-auth-40.txt
>        Pages:   44
>        Dates:   2023-11-14
>
>     Abstract:
>
>        The Drone Remote Identification Protocol (DRIP), plus trust
>     policies
>        and periodic access to registries, augments Unmanned Aircraft
>     System
>        (UAS) Remote Identification (RID), enabling local real time
>        assessment of trustworthiness of received RID messages and observed
>        UAS, even by Observers then lacking Internet access.  This document
>        defines DRIP message types and formats to be sent in Broadcast RID
>        Authentication Messages to verify that attached and recent detached
>        messages were signed by the registered owner of the DRIP Entity Tag
>        (DET) claimed.
>
>     The IETF datatracker status page for this Internet-Draft is:
>     https://datatracker.ietf.org/doc/draft-ietf-drip-auth/
>
>     There is also an HTML version available at:
>     https://www.ietf.org/archive/id/draft-ietf-drip-auth-40.html
>
>     A diff from the previous version is available at:
>     https://author-tools.ietf.org/iddiff?url2=draft-ietf-drip-auth-40
>
>     Internet-Drafts are also available by rsync at:
>     rsync.ietf.org::internet-drafts
>
>
>     -- 
>     Tm-rid mailing list
>     Tm-rid@ietf.org
>     https://www.ietf.org/mailman/listinfo/tm-rid
>
>
>
> -- 
> Robert Moskowitz
> Owner
> HTT Consulting
> C: 248-219-2059
> F: 248-968-2824
> E: rgm@labs.htt-consult.com
>
> There's no limit to what can be accomplished if it doesn't matter who 
> gets the credit
>
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>

-- 
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:rgm@labs.htt-consult.com

There's no limit to what can be accomplished if it doesn't matter who 
gets the credit