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

mohamed.boucadair@orange.com Tue, 08 March 2022 08: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 DDECA3A0C0C; Tue, 8 Mar 2022 00:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_MSPIKE_H4=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 SpLjbKXjq0zi; Tue, 8 Mar 2022 00:37:58 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (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 B7D413A1029; Tue, 8 Mar 2022 00:37:30 -0800 (PST)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) (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 opfednr25.francetelecom.fr (ESMTP service) with ESMTPS id 4KCTGd1Vd0zCrLk; Tue, 8 Mar 2022 09:37:29 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1646728649; bh=Ka0Lc2NQbtyO72a22iZZeMlwGpQIw2pdkuZ3SDh1Fsc=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=F7CxTOdBWZeCvHhG5sh46wEY2cvcdM8Kudgd3D8GRJeO7oZLjVbHuL2Y6rUgYyeTZ /2N0QWDOm6t6B4+Dao+azYTz74cloEKzS1Isspe5M1M/6WFXv/iNqgvNlUHZ3DGZT+ QU0wftn2xYoSHbr8vgbTTl28gZmwc2bUtG1IrM0j+3+YeltR/WeWZWZfbNApvzUc4m UG1hGB3/futSG/np3tVn3xVDIQu1jxW21+VwL0mZin/d3FlytUK3tOdhCm+UAzhcjt nTkFCW8Qx0v1zHsbpa9V1D+4KKO10tt5OUGQ9H6nCcUR3aD3mZHPhIjvIYIcHyZgrd TJ6BUjFD/cMHw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr04.francetelecom.fr (ESMTP service) with ESMTPS id 4KCTGd0nYwz1xpJ; Tue, 8 Mar 2022 09:37:29 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: "draft-ietf-drip-auth@ietf.org" <draft-ietf-drip-auth@ietf.org>
CC: "tm-rid@ietf.org" <tm-rid@ietf.org>
Thread-Topic: I-D Action: draft-ietf-drip-auth-05.txt
Thread-Index: AQHYMlmRAPWTlxf86E28pMDf/86WTqy1J3lQ
Content-Class:
Date: Tue, 8 Mar 2022 08:37:28 +0000
Message-ID: <27503_1646728649_622715C9_27503_189_1_787AE7BB302AE849A7480A190F8B9330354ACB38@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164668119132.9148.15526134845784853570@ietfa.amsl.com>
In-Reply-To: <164668119132.9148.15526134845784853570@ietfa.amsl.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-03-08T08:25:59Z; 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=ed3ea60f-b620-49e2-a5b2-de73754a3948; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/0TqFkQ49CjNDa_-N_1KsFcDyFpk>
Subject: Re: [Drip] I-D Action: draft-ietf-drip-auth-05.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: Tue, 08 Mar 2022 08:38:03 -0000

Hi Adam, all,

FYI, I requested a security review for this version to make sure that potential security issues are tagged early in the process. I indicated March 22 as a tentative date, but this will depend on the reviewers availability. 

One quick question about ICAO-related matters:

The draft says:
==
   The SAM Type field is maintained by the International Civil Aviation
   Organization (ICAO) and for DRIP four are allocated:
==

but also: 

==
8.  ICAO Considerations

   DRIP requests the following SAM Type's to be allocated:
==

Which seems to be conflicting. 

Can you please report about the currents status of these assignments? If the assignments are already made, then removing Section 8 would make sense.  

Thanks. 

Cheers,
Med

> -----Message d'origine-----
> De : I-D-Announce <i-d-announce-bounces@ietf.org> De la part de
> internet-drafts@ietf.org
> Envoyé : lundi 7 mars 2022 20:27
> À : i-d-announce@ietf.org
> Cc : tm-rid@ietf.org
> Objet : I-D Action: draft-ietf-drip-auth-05.txt
> 
> 
> 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 Authentication Formats & Protocols for
> Broadcast Remote ID
>         Authors         : Adam Wiethuechter
>                           Stuart Card
>                           Robert Moskowitz
> 	Filename        : draft-ietf-drip-auth-05.txt
> 	Pages           : 48
> 	Date            : 2022-03-07
> 
> Abstract:
>    This document describes how to include trust into the ASTM Remote ID
>    specification defined in ASTM F3411 under Broadcast Remote ID (RID).
>    It defines a few message schemes (sent within the Authentication
>    Message) that can be used to authenticate past messages sent by a
>    unmanned aircraft (UA) and provide proof of UA trustworthiness even
>    in the absence of Internet connectivity at the receiving node.
> 
> 
> The IETF datatracker status page for this 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-05.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-drip-auth-05
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-
> drafts
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt

_________________________________________________________________________________________________________________________

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.