[Tm-rid] We need to update the TMRID charter

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Wed, 05 February 2020 14:51 UTC

Return-Path: <evyncke@cisco.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 8337B1200C1 for <tm-rid@ietfa.amsl.com>; Wed, 5 Feb 2020 06:51:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.498
X-Spam-Level:
X-Spam-Status: No, score=-14.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=W4tTA1Lo; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=OHecZgYK
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 Bbq7qSsgbRbH for <tm-rid@ietfa.amsl.com>; Wed, 5 Feb 2020 06:50:57 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC5A21200B3 for <tm-rid@ietf.org>; Wed, 5 Feb 2020 06:50:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18047; q=dns/txt; s=iport; t=1580914257; x=1582123857; h=from:to:cc:subject:date:message-id:mime-version; bh=qt9iMaPnkIASC/MIUbkp8fjiN3ILzpAvuf8IcYTqPCk=; b=W4tTA1LovLKX+QqIsCOIgXcROB+rLEWLWKVodcrq5rVUGZeR65Gy0VaC S0CyLnqXWCmy/2xuFwyU5nvITcJd3j+MQ+E4Cd9EfaGvtCxJXIcYT+q0S FNKezgdkhgR22X6UbkQ8Hid6rlo1OErNnVzfGFPEWx5MpekMKwm++IwdW I=;
IronPort-PHdr: 9a23:k9m9rxzTfHdRcPDXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhSN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZuIF1z9J/3nRyc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C0DgBA1Tpe/5ldJa1gBYNmLyknBWxYIAQLKoQVg0YDinyWD4RiglIDVAkBAQEMAQEnBgIBAYN7RRmCIyQ4EwIDDQEBBAEBAQIBBQRthTcBC4VpAhQRHQEBNwERAUoCBDAnBA4gB4MEAYF9TQMuAQ6gUAKBOYhidYEygn8BAQWBLwERAkABgygYggwDBoE4il+BQxqBQT+BEScggh6DUAECAYE7GjuCYzKCLJAcO4ViJJgXdgqCOpE9hQYbgkgwk0uERo5igUuVLoQmAgQCBAUCDgEBBYFpIkSBFHAVOyoBgkFQGA1YjVEXgQQBAoJJgX+DFYU/dAIBgSaKZIJCAQE
X-IronPort-AV: E=Sophos;i="5.70,405,1574121600"; d="scan'208,217";a="709987405"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Feb 2020 14:50:56 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 015Eotcw005648 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 5 Feb 2020 14:50:55 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 5 Feb 2020 08:50:55 -0600
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 5 Feb 2020 08:50:54 -0600
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 5 Feb 2020 09:50:54 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IifCdikw2S9BvKjnMP35c3mtXoarWUw0Z1KB3PB11lCMhiZe2Be/y2tCOwbrmDSe5Os6TnfO2Hj6zf2whsvNdFwCBzMwQqYmp3JR8h1aopq7bt8tPo8EKLQVKgYBoLNiCFAxyxcrJqFPUpb/4yx76CBXHNTBBzV4TwaXFY6E4BTDva4q+Pi/YRR0w91GGS+WzaQT3eAJode2UHaJjB99pHyp2ARiho3UGdHf2Zm/U10txPClv2hZHSAPDvUqvZRMDiHQf64SBcP7lgSo616gYjz14fycy5vhHJx5rA+Ij/GqJNHAYaHdcRxAayeibKzVVDrjLIic5stYPqwjmXil6g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=qt9iMaPnkIASC/MIUbkp8fjiN3ILzpAvuf8IcYTqPCk=; b=BPEtw3uP8hi0NGMjmYVxidvWT57HbT2n9w9VdmP7i2K78XOWNbcYJv10bl9Xn87SDCP7iNgf/zhBCBk/PcAVWVq04us7btn0eZxK4PHIyFCVamNpw9tJYI+l++og/qx3a8x3/AU5rI82MkMSLpilGApu63evNYoRk4daY0f+7Ol1F/ftSzYgH44jSyI6EzwUOCTGi9+vKVHvvGCwGsfgXCM9D5gWaTqlMb63SpjAreSagUiU8Vdd2zvbS1wtXVCry+q5pWgfgS+oa3T8IzSmqiam1c8PVM3b42JzJMbpksiyOKFIynVOgPujNI52GystHh+0dp/3gwHs/aXTb3Qn5g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=qt9iMaPnkIASC/MIUbkp8fjiN3ILzpAvuf8IcYTqPCk=; b=OHecZgYK5VaqQW8sI4uqDaqrngfeD9Wh13ctjnElhJ5dsguv1yAsgY/p0ox+qv6yfVh9JxE9suDv6b8GaVvDHssnoxNzzfKnxqnC9DEUq8vqR5CZhBnpG91ne7cEB2phcr360iGheRiScv082DiI453XTD0ima5HZp93c3/QJLY=
Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB1593.namprd11.prod.outlook.com (10.172.35.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2707.21; Wed, 5 Feb 2020 14:50:53 +0000
Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca%3]) with mapi id 15.20.2707.020; Wed, 5 Feb 2020 14:50:53 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "tm-rid@ietf.org" <tm-rid@ietf.org>
CC: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, Daniel Migault <daniel.migault@ericsson.com>, Robert Moskowitz <rgm@labs.htt-consult.com>, "Wiethuechter, Adam" <adam.wiethuechter@axenterprize.com>, "Card, Stu" <stu.card@axenterprize.com>
Thread-Topic: We need to update the TMRID charter
Thread-Index: AQHV3DOpzBMvEKhYa0KAl7YS3GjQPg==
Date: Wed, 05 Feb 2020 14:50:53 +0000
Message-ID: <8C7B579D-E33D-4D76-BADB-726C15A214DC@cisco.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.21.0.200113
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:44f0:1250:65aa:af0:1eba:333b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 49555fa8-3ab3-4b06-2d51-08d7aa4acc89
x-ms-traffictypediagnostic: DM5PR11MB1593:
x-microsoft-antispam-prvs: <DM5PR11MB1593B4DA2A8A1DB3721CFBE1A9020@DM5PR11MB1593.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0304E36CA3
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(346002)(366004)(39860400002)(376002)(136003)(189003)(199004)(64756008)(91956017)(66446008)(54906003)(76116006)(66556008)(66946007)(66476007)(71200400001)(5660300002)(316002)(15650500001)(86362001)(478600001)(6506007)(6486002)(36756003)(6512007)(186003)(6916009)(966005)(4326008)(2616005)(66574012)(8936002)(33656002)(2906002)(81156014)(8676002)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1593; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: n0UX5QXYx07zUbfkQjuoOTLvsjFfoOPhwo8V5QM+2CO4QiUXbTYQtsZn4dotmhmpQRJiwpkW5OA6OliJgQ855F6XXvL1i0sMNafGBrrSXAR6qD3nuE+XPBQP+3CDBH8wYV4owSg+TrZekLTSAOozBvyYzottO+KtDGgsYcUTiPCP+LNhQUZCJRz32s6TPZWQu6W5q/BaChOypZcn5oHTRrSGxN7DG7A5Aye5cEG7eT9x4McQLIVN2SFV6K86b58dEMqev2pLsRQYMvK6Z9NqiT2Pxay+ki9iPzxAstQmcJk4eErFFB0iPMV9jrFN1wGDelVU5aFh5gPN6J25pd5gPezURQlL+hIhjioFBJbBAdq2MhKpnLTcOJdprX6dCfpIhkfsaaBXo6DZlS5Gd826nXv/sF2xCisK/9ISTQupycnt2Vnapl8cH3FvbklQWh7g4t0jtO9Ldj1qofu4WZ+OjB9h7D9iE6GB4qxJ9DllRui9Q9gjhlRs0DHkx186iF5zQfLlbe0RUON0BFDXDuMVRA==
x-ms-exchange-antispam-messagedata: LkZ1W3j1a9yO7WKGWWt57ZNpih0JpuEee8rJ6c9CoGhVXCiwtB7JrQyNAeDs6SEW3Ft2vlsxbyB6t5RM48j7hia+bp5JB5NjUaGeKAkFbib9X/DE7qUCYs5Rz0FbyT5Jm79PBmnp4t4QLQyi4zCu8/surUEEoeYkLCytB3JyOJXzzgmofdXKzwz7x3i/kzyAnSYLfBxh757G/aIb5jghQg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_8C7B579DE33D4D76BADB726C15A214DCciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 49555fa8-3ab3-4b06-2d51-08d7aa4acc89
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2020 14:50:53.0998 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: bhbZOWLmeufhN/AdmgspGwo8ig94Vqki59yYyp2d8Uj7SRvvarwMjAWiPVRXjaoP2y+YYCtAZ3fNWY779ypNTA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1593
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.16, xch-rcd-006.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/Adz6Y0XQD8p2ClvSQLJ7fjx0HZc>
Subject: [Tm-rid] We need to update the TMRID charter
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Trustworthy Multipurpose RemoteID <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: Wed, 05 Feb 2020 14:51:01 -0000

Let’s update the TMRID charter to fix the discussions done internally by the IESG and IAB. I have modified the text (see below), but there are still a couple of comments to be fixed. Suggestions are urgently welcome

  *   The “based on HIP” in “primarily leverage solutions based on HIP” seems pre-mature, the WG needs a document/work item to justify the choice of HIP (or possibly a liaison statement ?)
  *   Barry Leiba’s public comments should be acted upon (it is mostly editorial comments)
  *   I have already addressed the in-line expansion of acronyms (my suggestion to use foot notes was not well received by the IESG/IAB)

The above should really be fixed before Thursday 6th of February IESG telechat. **Suggestions are really welcome within 24 hours**

Magnus’ BLOCK is critical to be fixed. Unsure that the WG will manage to fix this part before tomorrow but we can give it a try. For example, on listing the work items for this WG ? This would limit the scope.
Updated charter below:

“CAAs (Civil Aviation Authorities) worldwide have initiated rule making for UAS (Unmanned Aircraft Systems) RID (Remote Identification). CAAs currently promulgate performance-based regulations that do not mandate specific techniques, but rather cite industry-consensus technical standards as acceptable means of compliance. One key standard is ASTM (formerly the American Society for Testing and Materials) WK65041 [1].  Network RID defines a set of information for UAS to make available globally indirectly via the Internet. Broadcast RID defines a set of messages for UA (Unmanned Aircraft) to send locally directly one-way over Bluetooth or Wi-Fi. WK65041 addresses how to neither populate/query registries, ensure trustworthiness of information nor make it instantly useful.
TMRID’s goal is to make RID immediately actionable, in both Internet and local-only connected scenarios, especially emergencies, in severely constrained UAS environments [2], balancing legitimate (e.g. public safety) authorities’ need to know trustworthy information with UAS operators’ privacy.

The  working group will primarily leverage solutions based on HIP as well as the domain name registration and focused on NPRM (Notice of Proposed Rule-Making) [3] published by US FAA (United States Federal Aviation Administration) as well as European CAA.

List of candidate drafts:
- draft-card-tmrid-uas
- draft-wiethuechter-tmrid-auth
- draft-moskowitz-hip-new-crypto
- draft-moskowitz-orchid-cshake
- draft-moskowitz-hip-hierarchical-hit
- draft-moskowitz-hip-hhit-registries


References:
[1] ASTM International F38 Committee Work Item WK65041 “Standard Specification for UAS Remote ID and Tracking” https://www.astm.org/DATABASE.CART/WORKITEMS/WK65041.htm
[2] UAS Identification and Tracking Aviation Rulemaking Committee Recommendations Final Report 2017 SEP 30 https://www.faa.gov/regulations_policies/rulemaking/committees/documents/media/UAS%20ID%20ARC%20Final%20Report%20with%20Appendices.pdf
[3] https://www.federalregister.gov/documents/2019/12/31/2019-28100/remote-identification-of-unmanned-aircraft-systems”