IETF Logo Mail Archive

Re: [Drip] I-D Action: draft-ietf-drip-rid-18.txt

mohamed.boucadair@orange.com Fri, 01 April 2022 13:36 UTC

Return-Path: <mohamed.boucadair@orange.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 4BF193A127F for <tm-rid@ietfa.amsl.com>; Fri, 1 Apr 2022 06:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 IRKNRuLXLQFF for <tm-rid@ietfa.amsl.com>; Fri, 1 Apr 2022 06:36:44 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (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 C5A8F3A1269 for <tm-rid@ietf.org>; Fri, 1 Apr 2022 06:36:43 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar21.francetelecom.fr (ESMTP service) with ESMTPS id 4KVLmp0111z7tMp; Fri, 1 Apr 2022 15:36:42 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1648820202; bh=y7zcYGIAtH+HCQOtQuUlNq7/eKA0AdWQ6OwpWFILbyE=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=OFWYF9CVCrOUT1iozlNw9NWdah92C1B30LWSm/9KRU5eRT/nhHPsVTbUwx7hkl2jm f08AN7oftCUA1Dai/3YcLwqd4xc+j+G8JveBDI0Mc5VC4tStu4p4WlqFVw4EAfqFOh nODG69uTrWt2nFAuZ/SU4i/YzCUp2SxTiEmXgmKcuQP7UYbqoAgQ08qVNrDAU0kyzW /CovrkImzYaIT0DJQ83XbYIS0HqwFuHR+hWaealR5W8Q9KXmYwR6gAMi1o+W0IcL0W bRqRYLm87rt2SrIVwYurJ8+aVKd6itxApli40qJk8mTJMtcQMuJ3SE77MFuQno+Aun SW34V7tfOqtdg==
From: <mohamed.boucadair@orange.com>
To: Robert Moskowitz <rgm@labs.htt-consult.com>
CC: "tm-rid@ietf.org" <tm-rid@ietf.org>
Thread-Topic: [Drip] I-D Action: draft-ietf-drip-rid-18.txt
Thread-Index: AQHYRcu3u0teCY/h2EykxcOd7xZNRazbDTmw
Content-Class:
Date: Fri, 1 Apr 2022 13:36:41 +0000
Message-ID: <26350_1648820201_6246FFE9_26350_274_1_e420ea00cf48471b83a8ebaac9f3a0fe@orange.com>
References: <164874151970.19999.10082987967478424394@ietfa.amsl.com> <d62d974b-82eb-3cba-8a9d-e1d44ae1c952@labs.htt-consult.com> <31953_1648798887_6246ACA7_31953_361_4_1ab40a0c1e03458f9636a582de440d56@orange.com> <31480_1648818466_6246F922_31480_173_1_1af11ed4ff834cddba6d86da2a176d74@orange.com> <542cad9f-8a32-c6de-d073-6c50fa9d3de0@labs.htt-consult.com>
In-Reply-To: <542cad9f-8a32-c6de-d073-6c50fa9d3de0@labs.htt-consult.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-04-01T13:29:27Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=39511ebd-b61f-455f-a543-2a20a9a9f916; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.52]
Content-Type: multipart/alternative; boundary="_000_e420ea00cf48471b83a8ebaac9f3a0feorangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/Wn4jylE9r47ZsqHq88wrsIsXeoM>
Subject: Re: [Drip] I-D Action: draft-ietf-drip-rid-18.txt
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: Fri, 01 Apr 2022 13:36:50 -0000

Re-,

Thanks, Rob.

Removing individual references would be helpful. Also, when we cite the auth I-D, we need to make sure we are not doing so normatively. I made many suggestions so that we can refer to 2.2 of 9153 when appropriate.

Updated RFCs should be mentioned in the abstract, but not as citations: “… the Abstract must not contain citations.” (RFC7322). See the file with a proposal to be explicit about what is being updated for each of these two RFCs.

Cheers,
Med

PS: “Surlignage”: This is so that you can double check the highlighted text. Apologies for the inconvenience.


De : Tm-rid <tm-rid-bounces@ietf.org> De la part de Robert Moskowitz
Envoyé : vendredi 1 avril 2022 15:23
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
Cc : tm-rid@ietf.org
Objet : Re: [Drip] I-D Action: draft-ietf-drip-rid-18.txt

Just some quick comments.  I will be working on this next week (some grandkids, and parents arrived for the weekend early this morning :) ).
On 4/1/22 09:07, mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> wrote:
Rob,

Please find below my comments to -18:


  1.  pdf: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-drip-rid-18-rev%20Med.pdf
  2.  doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-drip-rid-18-rev%20Med.doc

I had to log into github to access....

Some earlier commenter said I had to put the RFCs updated into the abstract!  ARGH!

And after I pushed out -18, I thought about removing both the crowd-source and secure-nrid draft references.  Those dependencies would delay this document.  I want to avoid what happened in PKIX!

There are some comments in French like:  Surlignage and "a mis en forme : Français (France)"

Can you please help me with them?

Lots of good comments, thanks.  I will target a -19 for the end of next week.  Passover is coming and I will be away, but still connected and writing Apr 14 - 26.



Thank you.

Cheers,
Med

De : Tm-rid <tm-rid-bounces@ietf.org><mailto:tm-rid-bounces@ietf.org> De la part de mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
Envoyé : vendredi 1 avril 2022 09:41
À : Robert Moskowitz <rgm@labs.htt-consult.com><mailto:rgm@labs.htt-consult.com>; tm-rid@ietf.org<mailto:tm-rid@ietf.org>
Objet : Re: [Drip] I-D Action: draft-ietf-drip-rid-18.txt

Hi Bob, all,

Thank you for implementing the list of agreed changes (https://mailarchive.ietf.org/arch/msg/tm-rid/K1tOOlHcdsz1RdMZXsahP2qrBvA/).

I invite everyone to carefully look into this version and share any remaining concern by ** April, 07 **.

Absent any follow-up, we will request publication for this document next Friday 08/04.

If we hear back from IANA before then, Rob will take care of the comments. If not, IANA-related comments will be addressed in due time (IETF LC).

As I already reviewed the document several times, I may have only nits/minor fixes that I will directly share with Rob.

Cheers,
Med

De : Tm-rid <tm-rid-bounces@ietf.org<mailto:tm-rid-bounces@ietf.org>> De la part de Robert Moskowitz
Envoyé : jeudi 31 mars 2022 17:50
À : tm-rid@ietf.org<mailto:tm-rid@ietf.org>
Objet : Re: [Drip] I-D Action: draft-ietf-drip-rid-18.txt

Fixed outstanding items of supporting 8-bit HHIT Suite ID.  Please check out that I now have this all done.  Particularly sections 4.2 and 5.

Moved HID registration to drip-registries (and changed reference to ietf-drip-registries!).  That is no longer asking ICAO, here, to manage RAA space.

Some other cleanup, please look at diff.

Still to do:  waiting for IANA review.  So I anticipate a -19
On 3/31/22 11:45, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> wrote:



A New Internet-Draft is available from the on-line Internet-Drafts directories.

This draft is a work item of the Drone Remote ID Protocol WG of the IETF.



        Title           : DRIP Entity Tag (DET) for Unmanned Aircraft System Remote Identification (UAS RID)

        Authors         : Robert Moskowitz

                          Stuart W. Card

                          Adam Wiethuechter

                          Andrei Gurtov

 Filename        : draft-ietf-drip-rid-18.txt

 Pages           : 33

 Date            : 2022-03-31



Abstract:

   This document describes the use of Hierarchical Host Identity Tags

   (HHITs), updating both [RFC7401] and [RFC7343], as self-asserting

   IPv6 addresses and thereby a trustable identifier for use as the

   Unmanned Aircraft System Remote Identification and tracking (UAS

   RID).  Within the context of RID, HHITs will be called DRIP Entity

   Tags (DET).  HHITs self-attest to the included explicit hierarchy

   that provides Registrar discovery for 3rd-party identifier

   attestation.





The IETF datatracker status page for this draft is:

https://datatracker.ietf.org/doc/draft-ietf-drip-rid/



There is also an HTML version available at:

https://www.ietf.org/archive/id/draft-ietf-drip-rid-18.html



A diff from the previous version is available at:

https://www.ietf.org/rfcdiff?url2=draft-ietf-drip-rid-18





Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts





--
Robert Moskowitz
Owner
HTT Consulting
C:      248-219-2059
F:      248-968-2824
E:      rgm@labs.htt-consult.com<mailto: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.

_________________________________________________________________________________________________________________________



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.




_________________________________________________________________________________________________________________________

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.

v2.8.7 | Report a Bug | By Email