Return-Path: X-Original-To: tm-rid@mail2.ietf.org Delivered-To: tm-rid@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 07940314E594; Thu, 5 Jun 2025 06:55:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.com Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hn2siLlAEwy5; Thu, 5 Jun 2025 06:55:29 -0700 (PDT) Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10on2100.outbound.protection.outlook.com [40.107.94.100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E5C03314E58D; Thu, 5 Jun 2025 06:55:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=q+dKxb2E/7N/e84psR0xJ3aj7tY+2b0YicEXH/m3XFfUPdjZUGgYtY0piDrJWYeaMhWi7TLDiCGnX285FUQy0m1+W/Iuj9QzRlC5NEm2j0tMFJgXjKo5+c+6rI0lzTLKFuNbrGCqNlcX9/ncv11CZtcHhtWP0DpapA8w2ZdESWCjS9fsCdYEORskj9qT1KvWT2MRcPKvzOIgYp5EaqX/8BHAWhZuChZUtpNEm8xmBPi7asFznqaIOld8RZ/ceuVEaQnqNsuPEKyHgxlsb3JX8VAQPB29yl7T9VNpLNqGbF39iT/rQ9uS9DcnFb08cELefNih9V2c8Gs/xoLu2/IshA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=CHXqEKyXwG1nBCV3Ljie3DmX9pq1yc2BtNIW8dveSY0=; b=kszITq5vF2R/1sn/f3xcdujao+7yGGvK2cighqNXpLnFqpY+yHP/P4+qAN88vKE4miH6i36Bgpar99/QehDiq/HGBitLTKsSlaiyj5k6Lm8H5tdPGH5MhLqlLEDOJ4BLpC49rbB8Z98bEa1QLUZ9JDYb4zjnmnCt9eqLo6zjFDY8CjTNMSkEhu8Oxm0iazSND9D68k+msEO2V6z1SYYtkZFIf5HwFyquIjwxRlv6uoNL69jLJZ9JePXGH9je+nZAj1RyOctpyNor5pBhnsZS1J+3U5h0silV+1g+DM/cgTKzQZC/vw9qR6nTLL3QiSO04Ysb+nvuEU99TNvYqWijiA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=evequefou.be; dmarc=pass action=none header.from=evequefou.be; dkim=pass header.d=evequefou.be; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector2-evequefou-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CHXqEKyXwG1nBCV3Ljie3DmX9pq1yc2BtNIW8dveSY0=; b=P9Q9KdPbNdTZXnk3XVOqPAnntejvlDses6ODhUVVn1AMB8o+3Ghef/PutWkzqGwXN33Yn/zAqaL8RouYpf4Ts+E4mX1TWG6lV4OGz1TIrxXVP5VIs8rCN/t+C6SjY8e7tBDcZkvP93eeyflWmSfGTRLWKI4/DuOw5qguP837rIk= Received: from IA0PPF726CD7A1F.namprd22.prod.outlook.com (2603:10b6:20f:fc04::d2b) by MN0PR22MB3595.namprd22.prod.outlook.com (2603:10b6:208:372::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8813.22; Thu, 5 Jun 2025 13:55:22 +0000 Received: from IA0PPF726CD7A1F.namprd22.prod.outlook.com ([fe80::c552:f531:59c0:7988]) by IA0PPF726CD7A1F.namprd22.prod.outlook.com ([fe80::c552:f531:59c0:7988%6]) with mapi id 15.20.8792.034; Thu, 5 Jun 2025 13:55:22 +0000 From: Mike Bishop To: "Eric Vyncke (evyncke)" , The IESG Thread-Topic: [Drip] Mike Bishop's Discuss on draft-ietf-drip-registries-29: (with DISCUSS and COMMENT) Thread-Index: AQHb1J1BMDXIXXFo2USZwxAkrikCjbP0l3oAgAAANY8= Date: Thu, 5 Jun 2025 13:55:21 +0000 Message-ID: References: <174896497413.2743391.17348434491953595708@dt-datatracker-59b84fc74f-84jsl> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=evequefou.be; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: IA0PPF726CD7A1F:EE_|MN0PR22MB3595:EE_ x-ms-office365-filtering-correlation-id: f1e6dd62-cce5-47d9-808a-08dda4389d49 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0;ARA:13230040|366016|376014|4022899009|10070799003|1800799024|13003099007|7053199007|8096899003|38070700018; x-microsoft-antispam-message-info: =?Windows-1252?Q?yhQx0kAz6kC4wZvfaQQsfT6K7/jxJG9qpQEuA000fVp72Ju2EiozQdw2?= =?Windows-1252?Q?+4hr02+ZypInuY+unqMgDHM8gztwNtGUQsJsj9XDkUY/WGogy6+Z2Qsv?= =?Windows-1252?Q?Q61Zn6fZsxh3KoR5x4tTRfMtchEjhZsSQXy+QfJBbxqjBkS0jWLw2DWJ?= =?Windows-1252?Q?kr/TJl2QhQFbDyMGaF6xf/cPRG+h2+QIdFDNATsshuNKx4u8P8n/5Fhh?= =?Windows-1252?Q?X1e3J4UW0ajK99TivNYLyDepD777ms1HbobxmseYRPmzOHS2IfA8D5jp?= =?Windows-1252?Q?36G2PC9wdXBiQ5WRTNqE5PSTkTWQ9cQNzJxmabf0M2yAgiFLUC5+NPz6?= =?Windows-1252?Q?5fosFGdD7QstSYidK42IrceJuT8z14xO/KygQQ/8u/UQi9MHqFfg3idu?= =?Windows-1252?Q?bJlxnhgMc8XioDpwUS2DaWLR9r9HTSauocMQ10DvbkY4NOu9MvqATLie?= =?Windows-1252?Q?eIhBYIgXrC7TtwQU9Eyl6g/FqleDdv4dwyPyT0MsoQ8MvlHoOovo937D?= =?Windows-1252?Q?5zDXsNwebNQitn6A6c5YxTyeQqWwTDYDTQ3FatqA1HQ4exnKPwDNWDpV?= =?Windows-1252?Q?U1liOLVsKyv/xwPlGDwxRKcHd+Ldw3Rbedn5eMEooEGyRCXNbNE5Q0zi?= =?Windows-1252?Q?CsitVn0PLxR+xQogf93xKu2udY5ZmIMFqQsyXx0uIOwnk86QSF3JiHTe?= =?Windows-1252?Q?qgYE6d8zGEIcd76V37gvATmHCmm0+I7LwLIrThfgxwANvK1vGNznNUEl?= =?Windows-1252?Q?p/qtlEuzcu3NiaqbotMnzKm/LPlyFMj0Cp4fpT0tLrLPM8KDB6zoLs5g?= =?Windows-1252?Q?bp53YCuwwqkNhzehUf2y/kB0ZMetvcbh6QPuA/UidXfsbUxCInIoTC9r?= =?Windows-1252?Q?48MsMw+pDz80N6xjDobI3yYkSqSBPlIOUFgyLUO7VxujkBVMjhq0/eX2?= =?Windows-1252?Q?OY3kRNVfamZJ9gU9VL+Npr57feDJxb9/CV7rVTvOguX/13HZmbVXVEJM?= =?Windows-1252?Q?8AEXpeTgCbhjaWBWAIGxyqZ98mTANPJiqU+sXiJiMvWTpKDZ3DlcWj6n?= =?Windows-1252?Q?iZwRDyXKud/I6EevGtFwwasP4cO0jieLTl45LVYwsLzHXIAyH8k0mNuj?= =?Windows-1252?Q?UU8sqAdMNV+t1E0+PFfuJ5dToW3SmnOQUsThC9OHLqGdT8ADlJWvl698?= =?Windows-1252?Q?K6koIWnKX4NHf++gUc+tc7STZJTvMJrNmVBm7KxRL/sHusRUcDzP5qq2?= =?Windows-1252?Q?dyPvjSMSAqJ1Hq/fy3fpgDzKDR7mVFx8F4IDcRnHPTEVjjbpSayOnpoO?= =?Windows-1252?Q?PxjpEs1S2abgAwzLvMD7fzLqyQSd1q1OqWuMHtb62gdGyaSh+QKH6EDV?= =?Windows-1252?Q?v+py86JmxQMWl01Gz829WHtCx8ngNQcakE7BFW0H24Dj9uoY/YLDwBmy?= =?Windows-1252?Q?/tqdDy/+LktiRO+Vxd8O1o7f+eeXQA7As/6xIcBxditZUFukBRn/rrG2?= =?Windows-1252?Q?pxpOD5YkZmHvXVNguRGpwqtLU1mDBz+GUe+YtJAIuwINO1NJlpQ=3D?= x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:IA0PPF726CD7A1F.namprd22.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(366016)(376014)(4022899009)(10070799003)(1800799024)(13003099007)(7053199007)(8096899003)(38070700018);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?TN4rBewMhBJefe1fxI6LqoF+AQgjQYo36NpLUl0cFZ6l1XT0Tk9bm3BT?= =?Windows-1252?Q?iw581Dk1dgxOVsczAkJSbUBFI31YGyCZS/76Z9NJKBB+TpBDsj8I+t49?= =?Windows-1252?Q?WpKwO7ijV2r238I0A0VaPQmRR7gJsgcTBjMj8SQt/QLpj5IujDYFVSYK?= =?Windows-1252?Q?9sKmF+ibxXB4zdcrFdaFsxhKHnXlSa2UVcBVoKtXFehBlzLLphuS5ew2?= =?Windows-1252?Q?ZoP6v+DLPtkwVUCpsJ4N7Yw76wrzICtT++MYCsZ5NaicPpCYaPIAc83I?= =?Windows-1252?Q?WWslir9Oql6IeXVOkd2MgMX7dHpYcuaTtWHxKkTSZLeskwY0MXcpIwHw?= =?Windows-1252?Q?njGlhjVtmTy+YOnMuXdqEqnlI8Wu2Cel4oN5fJ785iikgYCMwZBMGL3E?= =?Windows-1252?Q?wNWSYWHENbKblWuHS7LHe1t1mPcrl4QVFyVQjR9Rl3eJ6kCk9vl+eTEp?= =?Windows-1252?Q?xPpEp5H/AuNxZFHR+2+VVZpeSP+nVcdDuBWrYyZztbJ2nyzagpRa6KUG?= =?Windows-1252?Q?UnPGQEv8+27/kJ78ciUewtnTdxkRkg7pqAXKjIs1USI0fd3zxPOQtmqa?= =?Windows-1252?Q?nWQXZLYIKB3cE42IqBdIKPSnFSX8A22u4lvRZgYpyLIp15PQaCVPiCFd?= =?Windows-1252?Q?iHHD5xk9lRJzh2PMwxrcCRhQMun94oIZ+z2YB0/Lf/Fna24pNYYohiVG?= =?Windows-1252?Q?7NYWzEHb8U+/pQqVZu2jz4d1UGsuzU723G+C0EOpqhMO/MrIQVXn/98h?= =?Windows-1252?Q?WB0hpQGRoworoHSnenmTdHIdQmD/Ykkij8WXcatTgzBaSyu7IC8IS41Z?= =?Windows-1252?Q?KAl5xhFcJfOfa03cTiqQUyqsfCTTrZ39FKjxDsvjdPLHhms6XModKu2B?= =?Windows-1252?Q?yzUYIdP/q4KiWMbv+4DXqcPNGleXW5eifghewtFJOY4RXfDchT4tIsCJ?= =?Windows-1252?Q?mAT2XxYTRkNTqYbuWoI68liSo2/ikiVE9VUdM/5HnaIuqKcQNwIyf1QX?= =?Windows-1252?Q?U/3BQj+l+O9u+bJy6QYWbGg8PdH+x8JlN3wuuiUAnZyFy3O5vafG/iUV?= =?Windows-1252?Q?RcBBDDLFL/9ojOJurcRjJ0vv/9f/26pkNjNayWXHcqgxswdS2gIsA9dr?= =?Windows-1252?Q?OeURJT0pVjEou76CwpHn/J7F+9h/P4HxGHKFhXlh6u12cSbqom91Kx7V?= =?Windows-1252?Q?0JMdyIl/Kibt11atmnSFoNCVuTaV8J3wuAj0ynyFKtKZwPCssEu+B8jr?= =?Windows-1252?Q?JJAH9owlFhHsAbIpnLJazEfdRBzoFSMuNLSDyF/5iU8ifzWxLJ+amkF1?= =?Windows-1252?Q?MgONOxVmztQdbA2lLT9Bpe7xbaotx+lvSjzM5+UKcE1O8HByCIoVJfUV?= =?Windows-1252?Q?xhnqAECtQMdLHHbpnvX9FS3b6w/EYrO7FhZUDoR7p3ppxn9G6USRfdCX?= =?Windows-1252?Q?NVT9Jvknesc0PYBQfRnEpqgVsEh1DBuMm0yXdEVc4itNn09f8vFe+Wtr?= =?Windows-1252?Q?OYHTpRn2tAnzx+L3GtEUz5BjPq+Hs8C5ZwKHJziRq3nh3VU0z5JHzQ3e?= =?Windows-1252?Q?OM0ii5/u4f1EdeGg4mHsklBHnO3NYWKBaeADJSJS0KdpFO/FyZ0KFKaW?= =?Windows-1252?Q?zpbsA0QSSC9Uv1cHtptY4jpqBxkM1mv5+krj8nhZMrFR15EU6EzYCef+?= =?Windows-1252?Q?dIgd7R5Kg+65nCS7UCbAdr0KOAchILe06ZkkDmWHovf8UFS9Inv5ljpq?= =?Windows-1252?Q?3SarzbAAOBV9x6JZV+EEySjuEFUFGslpc7k9EIwY?= Content-Type: multipart/alternative; boundary="_000_IA0PPF726CD7A1F90F5D2C8B77C67D73124DA6FAIA0PPF726CD7A1F_" MIME-Version: 1.0 X-OriginatorOrg: evequefou.be X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: IA0PPF726CD7A1F.namprd22.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: f1e6dd62-cce5-47d9-808a-08dda4389d49 X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jun 2025 13:55:21.9931 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: lFXn1q7IzmgFMw6EoQtGERyvArZO2O8Hv+Sd5vwbO2DmiRgP4hSyco0y5BFT4QekuUs6ypECkUppfYCD3byD2w== X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN0PR22MB3595 Message-ID-Hash: E4EHVHWZ6VIULL6LKNOY27HDSLD3DZ7P X-Message-ID-Hash: E4EHVHWZ6VIULL6LKNOY27HDSLD3DZ7P X-MailFrom: mbishop@evequefou.be X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "draft-ietf-drip-registries@ietf.org" , "drip-chairs@ietf.org" , "tm-rid@ietf.org" , "daniel.migault@ericsson.com" X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5BDrip=5D_Re=3A_Mike_Bishop=27s_Discuss_on_draft-ietf-drip-regist?= =?utf-8?q?ries-29=3A_=28with_DISCUSS_and_COMMENT=29?= List-Id: Drone Remote Identification Protocol Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --_000_IA0PPF726CD7A1F90F5D2C8B77C67D73124DA6FAIA0PPF726CD7A1F_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Mostly. I was expecting https://github.com/ietf-wg-drip/draft-ietf-drip-reg= istries/blob/a8da51bfcafcdf91878f8862c52830aa736782c9/iso3166-raa.csv, but = -30 uses https://github.com/ietf-wg-drip/draft-ietf-drip-registries/commit/= a8da51bfcafcdf91878f8862c52830aa736782c9 instead. Probably close enough; I'= ll clear my DISCUSS after I see a thumbs-up from IANA. Thank you! ________________________________ From: Eric Vyncke (evyncke) Sent: Thursday, June 5, 2025 9:47 AM To: Mike Bishop ; The IESG Cc: draft-ietf-drip-registries@ietf.org ; drip-chairs@ietf.org ; tm-rid@ietf.org ; daniel.migault@ericsson.com Subject: Re: [Drip] Mike Bishop's Discuss on draft-ietf-drip-registries-29:= (with DISCUSS and COMMENT) Hello Mike, Does -30 address your issue about =93the mapping between ISO 3166-1 Numeric= Nation Codes and RAAs is specified as a CSV file..=94 as there is a specif= ic commit version in section 6.2.1 ? You may have seen IANA replies on a separate thread on this topic. Regards -=E9ric From: Mike Bishop via Datatracker Date: Tuesday, 3 June 2025 at 17:36 To: The IESG Cc: draft-ietf-drip-registries@ietf.org , drip-chairs@ietf.org , tm-rid@ietf.org , daniel.migault@ericsson.com Subject: [Drip] Mike Bishop's Discuss on draft-ietf-drip-registries-29: (wi= th DISCUSS and COMMENT) Mike Bishop has entered the following ballot position for draft-ietf-drip-registries-29: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-= ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-drip-registries/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- The mapping between ISO 3166-1 Numeric Nation Codes and RAAs is specified a= s a CSV file on the main branch of a GitHub repo. This seems problematic in two ways: - First, it is not an archival resource; future commits to the GitHub repo could modify it without notice. At the very least, this should link to the version of the file in a specific commit so that it cannot change without modifying the link in the document. - Second, the link does not appear in the document's references and probabl= y should. I'm sympathetic to the desire not to add a 4k row table in an appendix. Hav= e you collaborated with IANA on the best way for them to receive the initial values of this registry? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I second Gunter's observation that this document does not cater to new read= ers. The term DRIP is not introduced in the document, and RFC9153/RFC9434 is not clearly associated to this acronym to help anyone figure it out. There are several unfamiliar abbreviations just in Figure 1, which should be setting = the framework for understanding the rest of the document. (GCS, AAA, etc.) Whil= e I appreciate the pointer to RFCs 9153, 9374, and 9434 for terminology, a list= of the terms being imported from them would be useful to help readers look up terminology as needed. A brief explanation of what DRIP is and what role th= is document's work plays in that would go a long way. Related, I don't see a definition or reference for the term "nibble revers(ed|ing)" beyond "convention". You already have the STD88 reference, which uses similar language; I'd just point to it where appropriate. (From STD88, "The sequence of nibbles is encoded in reverse order, i.e. the low-o= rder nibble is encoded first, followed by the next low-order nibble and so on. E= ach nibble is represented by a hexadecimal digit.") The "Canonical Registration Certificate" is mentioned as a field in the HHI= T RRType without further context about what this is or how it is used. Please provide references inline as appropriate. In Section 5.2, I was not able to parse the phrase "public information typically sent of the UAS Broadcast RID that is static". Is there a missing= or substituted word here? If not, is there a different word order that would b= e easier to understand? In Section 6.1, the DE's authority is confusing to me in two ways. First, i= f the DE is "expected to process these delegation requests on a first-come, first-served basis," what need is there for the DE? Just permit IANA to allocate this space directly. Second, what does it mean that "[t]he DE will have the discretion to perform minimal technical checks" if the DE "[can]no= t enforce these"? Again, performing unenforceable checks could be done by any member of the public and doesn't require a DE. I note that the raft of DNS BCPs and RFCs to which security guidance is delegated are all informational. This may be correct, as this is guidance rather than a compatibility requirement, but please double-check that you d= on't intend any of these to be normative. =3D=3D=3DNITS FOLLOW=3D=3D=3D Abstract, "DRIP specific" =3D> "DRIP-specific" Section 4, "UAS specific" =3D> "UAS-specific" Section 5.1, "HHIT specific" =3D> "HHIT-specific" Section 6.1, "ie" =3D> "i.e." Section 7.1, "following RFC" =3D> "following RFCs" (or just drop it entirel= y, e.g. "[RFC7720], ...., and [RFC3007] provide suitable guidance.") -- Tm-rid mailing list -- tm-rid@ietf.org To unsubscribe send an email to tm-rid-leave@ietf.org --_000_IA0PPF726CD7A1F90F5D2C8B77C67D73124DA6FAIA0PPF726CD7A1F_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Mostly. I was expecting https://github.com/ietf-wg-drip/draf= t-ietf-drip-registries/blob/a8da51bfcafcdf91878f8862c52830aa736782c9/iso316= 6-raa.csv, but -30 uses h= ttps://github.com/ietf-wg-drip/draft-ietf-drip-registries/commit/a8da51bfca= fcdf91878f8862c52830aa736782c9 instead. Probably close enough; I'll clear my DISCUSS after I see a thumbs-up from = IANA.

Thank you!

From: Eric Vyncke (evyncke) <evyncke@cisco.com>
Sent: Thursday, June 5, 2025 9:47 AM
To: Mike Bishop <mbishop@evequefou.be>; The IESG <iesg= @ietf.org>
Cc: draft-ietf-drip-registries@ietf.org <draft-ietf-drip-reg= istries@ietf.org>; drip-chairs@ietf.org <drip-chairs@ietf.org>; tm= -rid@ietf.org <tm-rid@ietf.org>; daniel.migault@ericsson.com <dani= el.migault@ericsson.com>
Subject: Re: [Drip] Mike Bishop's Discuss on draft-ietf-drip-re= gistries-29: (with DISCUSS and COMMENT)
 

= Hello Mike,

=  

= Does -30 address your issue about =93the m= apping between ISO 3166-1 Numeric Nation Codes and RAAs is specified as a C= SV file..=94 as there is a specific commit version in section 6.2.1 ?

=  

= You may have seen IANA replies on a separa= te thread on this topic.

=  

= Regards

=  

= -=E9ric

=  

=  

From: Mike Bishop via Datatracker <= noreply@ietf.org>
Date: Tuesday, 3 June 2025 at 17:36
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-drip-registries@ietf.org <draft-ietf-drip-registri= es@ietf.org>, drip-chairs@ietf.org <drip-chairs@ietf.org>, tm-rid@= ietf.org <tm-rid@ietf.org>, daniel.migault@ericsson.com <daniel.mi= gault@ericsson.com>
Subject: [Drip] Mike Bishop's Discuss on draft-ietf-drip-registries-= 29: (with DISCUSS and COMMENT)

Mike Bishop has entered the following ball= ot position for
draft-ietf-drip-registries-29: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handlin= g-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatr= acker.ietf.org/doc/draft-ietf-drip-registries/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

The mapping between ISO 3166-1 Numeric Nation Codes and RAAs is specified a= s a
CSV file on the main branch of a GitHub repo. This seems problematic in two=
ways:

- First, it is not an archival resource; future commits to the GitHub repo<= br> could modify it without notice. At the very least, this should link to the<= br> version of the file in a specific commit so that it cannot change without modifying the link in the document.

- Second, the link does not appear in the document's references and probabl= y
should.

I'm sympathetic to the desire not to add a 4k row table in an appendix. Hav= e
you collaborated with IANA on the best way for them to receive the initial<= br> values of this registry?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I second Gunter's observation that this document does not cater to new read= ers.
The term DRIP is not introduced in the document, and RFC9153/RFC9434 is not=
clearly associated to this acronym to help anyone figure it out. There are<= br> several unfamiliar abbreviations just in Figure 1, which should be setting = the
framework for understanding the rest of the document. (GCS, AAA, etc.) Whil= e I
appreciate the pointer to RFCs 9153, 9374, and 9434 for terminology, a list= of
the terms being imported from them would be useful to help readers look up<= br> terminology as needed. A brief explanation of what DRIP is and what role th= is
document's work plays in that would go a long way.

Related, I don't see a definition or reference for the term "nibble revers(ed|ing)" beyond "convention". You already have the ST= D88 reference,
which uses similar language; I'd just point to it where appropriate. (From<= br> STD88, "The sequence of nibbles is encoded in reverse order, i.e. the = low-order
nibble is encoded first, followed by the next low-order nibble and so on. E= ach
nibble is represented by a hexadecimal digit.")

The "Canonical Registration Certificate" is mentioned as a field = in the HHIT
RRType without further context about what this is or how it is used. Please=
provide references inline as appropriate.

In Section 5.2, I was not able to parse the phrase "public information=
typically sent of the UAS Broadcast RID that is static". Is there a mi= ssing or
substituted word here? If not, is there a different word order that would b= e
easier to understand?

In Section 6.1, the DE's authority is confusing to me in two ways. First, i= f
the DE is "expected to process these delegation requests on a first-co= me,
first-served basis," what need is there for the DE? Just permit IANA t= o
allocate this space directly. Second, what does it mean that "[t]he DE= will
have the discretion to perform minimal technical checks" if the DE &qu= ot;[can]not
enforce these"? Again, performing unenforceable checks could be done b= y any
member of the public and doesn't require a DE.

I note that the raft of DNS BCPs and RFCs to which security guidance is
delegated are all informational. This may be correct, as this is guidance rather than a compatibility requirement, but please double-check that you d= on't
intend any of these to be normative.

=3D=3D=3DNITS FOLLOW=3D=3D=3D

Abstract, "DRIP specific" =3D> "DRIP-specific"

Section 4, "UAS specific" =3D> "UAS-specific"

Section 5.1, "HHIT specific" =3D> "HHIT-specific"
Section 6.1, "ie" =3D> "i.e."

Section 7.1, "following RFC" =3D> "following RFCs" (= or just drop it entirely,
e.g. "[RFC7720], ...., and [RFC3007] provide suitable guidance.")=



--
Tm-rid mailing list -- tm-rid@ietf.org
To unsubscribe send an email to tm-rid-leave@ietf.org

--_000_IA0PPF726CD7A1F90F5D2C8B77C67D73124DA6FAIA0PPF726CD7A1F_--