IETF Logo Mail Archive

Re: [Drip] AD review of draft-ietf-drip-rid

mohamed.boucadair@orange.com Mon, 11 April 2022 11:38 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 6E09B3A1884; Mon, 11 Apr 2022 04:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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 w8FOh58AWBQR; Mon, 11 Apr 2022 04:38:39 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 EC1273A188B; Mon, 11 Apr 2022 04:38:38 -0700 (PDT)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) (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 opfednr21.francetelecom.fr (ESMTP service) with ESMTPS id 4KcRgw6J5Zz5w74; Mon, 11 Apr 2022 13:38:36 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1649677116; bh=piKV7GLTszsqUnMctSCvbVmu26SYGdyYcBeFI9iGyXc=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=QNsdwUwOe8VleWcy5DbiugG6NNa/bleSq9we0CjvjCNdYP9blC5Zn3v8Q+9rsNUfi j29HSYCCaIdObqvn7//rtFFmc3EZIcHuoCdfip5klenphxwwD7P0GtZqOR+nv6H29Z T6kPZf8jI59wSQjKFOf7h//atjA7FjYxVSN1vT9+Y8YUmVvou3E/P7AfNe+2Ofaput EHQo0C2QhHFD/wPYFjW8PRdz8m0/QPOmNSqB4KwF/ceLbFqr/IW0Lw+NBPSJRS23qu zOoWg/jYeg15zWPT82N9iIL2NrhEebrJ21mfJ7/sw0HMhQ72p1vUMAqVTLDuU3geEU qiI9jJL4IHsNw==
From: <mohamed.boucadair@orange.com>
To: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, "tm-rid@ietf.org" <tm-rid@ietf.org>
CC: "draft-ietf-drip-rid@ietf.org" <draft-ietf-drip-rid@ietf.org>
Thread-Topic: [Drip] AD review of draft-ietf-drip-rid
Thread-Index: AQHYTZL4CINt5+ahlUCPu2KpVHxNFazqjJ8g
Content-Class:
Date: Mon, 11 Apr 2022 11:38:36 +0000
Message-ID: <19882_1649677116_6254133C_19882_161_2_31c0c1eb89eb4e3f9a76147ee5d97df1@orange.com>
References: <A8A9DD48-F67A-46FD-8A35-7C4EA1C94F88@cisco.com>
In-Reply-To: <A8A9DD48-F67A-46FD-8A35-7C4EA1C94F88@cisco.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-11T11:21:48Z; 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=1b8d1bb4-ee07-47e2-a761-3521f2917cdb; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.27.51]
Content-Type: multipart/alternative; boundary="_000_31c0c1eb89eb4e3f9a76147ee5d97df1orangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/A_nRpdtFp9aMu4bBKMxP385_KC4>
Subject: Re: [Drip] AD review of draft-ietf-drip-rid
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: Mon, 11 Apr 2022 11:38:44 -0000

Hi Éric,

Thank you for the careful AD review.

Please see below for one specific point.

Cheers,
Med

De : Tm-rid <tm-rid-bounces@ietf.org> De la part de Eric Vyncke (evyncke)
Envoyé : lundi 11 avril 2022 12:58
À : tm-rid@ietf.org
Cc : draft-ietf-drip-rid@ietf.org
Objet : [Drip] AD review of draft-ietf-drip-rid


Hi,



Thanks to the authors, shepherd, and the DRIP WG for producing this 3rd I-D. And, I appreciate that the comments from iotdir, secdir, cfrg, .. were taken into accounts :-)



As usual, here is my AD review before going to the IETF Last Call and continuing the publication process. Except noted by a "***", all the comments can be ignored but I would appreciate a reply telling "we have read your comment but prefer to ignore" (or a variation of this text).



I hope this helps improving the document and ease the publication process.



Regards



-éric



---- review below



[snip] …



# Sec 11.2

*** F3411 & drip-registries & CTA2063A & RFC 8032 should probably be normative.



[Med] You are probably right for RFC8032. The good news is that it is already listed in https://datatracker.ietf.org/doc/downref/.



F3411 is cited once to call out the various types. Reading that document is not required to understand or implement HHITs/DETs.



Idem for drip-registries. What is important from an interoperability standpoint is to unambiguously identify a DET. This is done by means of the prefix part. How the RAA/HDA parts are assigned does not actually matter.



I’m neutral on CTA2063A.



_________________________________________________________________________________________________________________________

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