From nobody Tue Nov 3 00:37:42 2020 Return-Path: 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 5D2DF3A0985 for ; Tue, 3 Nov 2020 00:37:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 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, 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 L5okX0j8QulY for ; Tue, 3 Nov 2020 00:37:40 -0800 (PST) Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBCA33A0957 for ; Tue, 3 Nov 2020 00:37:39 -0800 (PST) Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by opfedar27.francetelecom.fr (ESMTP service) with ESMTPS id 4CQNSy2qFVz2xRK; Tue, 3 Nov 2020 09:37:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1604392658; bh=qaow6lRcWmNiA2xT421x164WNfC5aH72nEf9lvqV+M4=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=Lm1cBRHd2X1GC7kFk6YQPoRaPm19z4PpxjRDmIn/sS3kCnnYr2Bi7YFx/LFszyQ5/ JeHjdzpC3sRBuPZxSM3C3skXdIrrZses8utPdwFK9zTlPZQqjA+3p1oeMYHBKOSD9d 0oMbZ64VDV+dsMv6lD6QRq4ti8PNgQkGu9CBzigdNVr/4YRluIsSPwUgeFCriyheVx AqoPjZ2izQjvdeRd7vfaQ4oR4VfhHO/bav/leZp//hzlQ8pdCX3oJ8hUSrtZxnLRxX rbzZaQtC0bs/ga+V2oiJPdiivycvR0qPrLW/ojPZKQigrQ1sk6HCchddTNz9w6yYld geCUTlwKnwDDw== Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by opfedar00.francetelecom.fr (ESMTP service) with ESMTPS id 4CQNSy1tHQzCqjy; Tue, 3 Nov 2020 09:37:38 +0100 (CET) From: To: Robert Moskowitz , "tm-rid@ietf.org" Thread-Topic: [Drip] I-D Action: draft-ietf-drip-reqs-06.txt Thread-Index: AQHWsVUOOxvZmhbZi0OP/9V9nXU746m2FVeA Date: Tue, 3 Nov 2020 08:37:37 +0000 Message-ID: <8237_1604392658_5FA116D2_8237_210_1_787AE7BB302AE849A7480A190F8B93303156ED20@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> References: <160428566212.6611.17102125374039107308@ietfa.amsl.com> <8a6735ac-5fd9-b331-23b8-41c1014ca29d@labs.htt-consult.com> In-Reply-To: <8a6735ac-5fd9-b331-23b8-41c1014ca29d@labs.htt-consult.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: 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: Subject: Re: [Drip] I-D Action: draft-ietf-drip-reqs-06.txt X-BeenThere: tm-rid@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Drone Remote Identification Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2020 08:37:41 -0000 Hi Bob, all (as individual) I like this version as well. Thank you, Stu. The descriptive text is OK to be included as it allows the readers to conte= xtualize the requirements.=20=20 Cheers, Med > -----Message d'origine----- > De=A0: Tm-rid [mailto:tm-rid-bounces@ietf.org] De la part de Robert > Moskowitz > Envoy=E9=A0: lundi 2 novembre 2020 21:15 > =C0=A0: tm-rid@ietf.org > Objet=A0: Re: [Drip] I-D Action: draft-ietf-drip-reqs-06.txt >=20 > I have reviewed this draft and feel it is ready for wg approval and > forwarding to the AD. >=20 > If I have anything to say, much of the descriptive text belongs in > the architecture draft, but since reqs was done first, the text > needs to stay there, but may be duplicated in the architecture > draft. >=20 > On 11/1/20 9:54 PM, 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 : Drone Remote Identification Protocol > (DRIP) Requirements > > Authors : Stuart W. Card > > Adam Wiethuechter > > Robert Moskowitz > > Andrei Gurtov > > Filename : draft-ietf-drip-reqs-06.txt > > Pages : 36 > > Date : 2020-11-01 > > > > Abstract: > > This document defines terminology and requirements for Drone > Remote > > Identification Protocol (DRIP) Working Group protocols to > support > > Unmanned Aircraft System Remote Identification and tracking > (UAS RID) > > for security, safety and other purposes. Complementing > external > > technical standards as regulator-accepted means of compliance > with > > UAS RID regulations, DRIP will: > > > > facilitate use of existing Internet resources to support > UAS RID > > and to enable enhanced related services; > > > > enable online and offline verification that UAS RID > information is > > trustworthy. > > > > > > The IETF datatracker status page for this draft is: > > https://datatracker.ietf.org/doc/draft-ietf-drip-reqs/ > > > > There is also an HTML version available at: > > https://www.ietf.org/archive/id/draft-ietf-drip-reqs-06.html > > > > A diff from the previous version is available at: > > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-drip-reqs-06 > > > > > > Please note that it may take a couple of minutes from the time of > > submission until the htmlized version and diff are available at > tools.ietf.org. > > > > Internet-Drafts are also available by anonymous FTP at: > > ftp://ftp.ietf.org/internet-drafts/ > > > > >=20 > -- > Tm-rid mailing list > Tm-rid@ietf.org > https://www.ietf.org/mailman/listinfo/tm-rid ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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.