[lamps] Re: [EXTERNAL] Call for adoption of draft-brockhaus-lamps-automation-keyusages/
"Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com> Wed, 20 November 2024 10:12 UTC
Return-Path: <hendrik.brockhaus@siemens.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8318BC1CAE79 for <spasm@ietfa.amsl.com>; Wed, 20 Nov 2024 02:12:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_FONT_LOW_CONTRAST=0.001, 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=siemens.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PXMUqAKKjBM1 for <spasm@ietfa.amsl.com>; Wed, 20 Nov 2024 02:12:41 -0800 (PST)
Received: from EUR03-DBA-obe.outbound.protection.outlook.com (mail-dbaeur03on2050.outbound.protection.outlook.com [40.107.104.50]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 3F385C180B69 for <spasm@ietf.org>; Wed, 20 Nov 2024 02:12:41 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=tbJCYTOFk+zoxNdi5aTJL9xMlkfkXebyf1+dbFc3IUpvrlDj1Y/cIlSZeWzaC1QcTgyfkeD40Czxfb6D26XwISArcoW9YasnQT2iBY+HY+ya17PrP7/kWM0BRV/E72lhtFpSU2ktb5Gx6oixdyqiyCxlvzJm9o6FWv1QeYaCF16Wicunmrq3CkwQjnIby75e011uQfhF8ZVFCIQFPXOMRyWlfhUoW68qAH2Gqbo5GmuNR55yOu7GXS5mbUR91aYcZ1OGAj4KDxXofnYnDDvBYXIBg8EC/N79qIh7GsL+ebuz/1Ed1hv9H/37OIn/+S8IKCduHzo/53iXN3NNZzlxvw==
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=DLPcZy839Ikq+5nkkrt1YfzYp3+BNztWYTfEEOJcbyQ=; b=lF/VwBgQwakwbyu6rJ+pc1hLH1F+2nKiwKjGGosZTA4r2LNjkPdvGBp1ZN+dKVf11mqTEJgzgamzQj7nT5JwcGjWmgNkFqMq65Gr46D+Pp2yoAh6wobiBwoIusGzarMW2nvVDikOhhxoqgU2G/J96+F1M6iPMveIcNUPqBtLsd2Q2LKdhWU8hbPyS1OIuu9Llke2B18m2Xj6H5b/a5B71eXZadfxaaMIY+Uj5P223R2GzOApHOOEHPVV7nxXu11WEb0ejxee0P1ARh9zIJOzMBtwEQOxfi0CrZIaUEmAVaa+DPqtwmKhaMbyOZ/n2ui1vybw/Sqo4tHZH79F/rW8dA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DLPcZy839Ikq+5nkkrt1YfzYp3+BNztWYTfEEOJcbyQ=; b=RqEOt7fpTic3772jkIkIFRL3zIjePzjzpHG71wJlBnRfVlKntollH8xeTrtjfqPvcfLsow/RGn76MrmuSbHZF6Oq/VIpDpjOQrYg6dE2MFP0xzZb6JC2oYqyk3qmMDV9OqRv3XUyxyeCTRjTrrE5C2AxtYlU5OfPG81W7QjqappV67wYpTF8h4Jqf/mtWrVM6qDFMNtzGLZkNVpNeEy6hiBOhVecY/AAwod8JmfmAAAerQ2gsKfSv75SvpNaMTtUPfsxvLrFwQSeWGL4BKnroks0PxzfCgbWz9Swei6wYrHafPf0GYEQS9MEMn2XMX1fJHgW3xJUC3F9ycQ6w8zpaQ==
Received: from DB9PR10MB5715.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:10:2ee::5) by DB9PR10MB6692.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:10:3d0::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8182.12; Wed, 20 Nov 2024 10:12:37 +0000
Received: from DB9PR10MB5715.EURPRD10.PROD.OUTLOOK.COM ([fe80::8b02:6852:93f4:50a]) by DB9PR10MB5715.EURPRD10.PROD.OUTLOOK.COM ([fe80::8b02:6852:93f4:50a%4]) with mapi id 15.20.8182.004; Wed, 20 Nov 2024 10:12:37 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: Michael StJohns <msj@nthpermutation.com>, Russ Housley <housley@vigilsec.com>
Thread-Topic: [lamps] Re: [EXTERNAL] Call for adoption of draft-brockhaus-lamps-automation-keyusages/
Thread-Index: AQHbOrvh+bfOWMvRNUqmZIKNyU8iz7K/7fUA
Date: Wed, 20 Nov 2024 10:12:37 +0000
Message-ID: <DB9PR10MB5715DEAA9C12F3F7864F36B7FE212@DB9PR10MB5715.EURPRD10.PROD.OUTLOOK.COM>
References: <1AB2EA5B-1B9B-44FF-9825-6EE779DC25B7@vigilsec.com> <CH0PR11MB57395B5F463B1890E094956E9F272@CH0PR11MB5739.namprd11.prod.outlook.com> <DB9PR10MB571565A8FB5CE565F5F01B0FFE202@DB9PR10MB5715.EURPRD10.PROD.OUTLOOK.COM> <CF77109C-5B3D-4C9F-A7A7-EDA84E0425F9@vigilsec.com> <f0f60fed-2642-4fee-b868-5522fb753782@nthpermutation.com>
In-Reply-To: <f0f60fed-2642-4fee-b868-5522fb753782@nthpermutation.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_9d258917-277f-42cd-a3cd-14c4e9ee58bc_ActionId=5acea563-c1b6-400b-9a02-68afabc7733e;MSIP_Label_9d258917-277f-42cd-a3cd-14c4e9ee58bc_ContentBits=0;MSIP_Label_9d258917-277f-42cd-a3cd-14c4e9ee58bc_Enabled=true;MSIP_Label_9d258917-277f-42cd-a3cd-14c4e9ee58bc_Method=Standard;MSIP_Label_9d258917-277f-42cd-a3cd-14c4e9ee58bc_Name=restricted;MSIP_Label_9d258917-277f-42cd-a3cd-14c4e9ee58bc_SetDate=2024-11-20T09:51:04Z;MSIP_Label_9d258917-277f-42cd-a3cd-14c4e9ee58bc_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a;
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=siemens.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DB9PR10MB5715:EE_|DB9PR10MB6692:EE_
x-ms-office365-filtering-correlation-id: 766270eb-310c-430b-d03d-08dd094bdc39
x-ms-exchange-atpmessageproperties: SA
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|366016|1800799024|4022899009|376014|38070700018|7053199007|8096899003;
x-microsoft-antispam-message-info: yx4gsQ/Emln7o84vQ4/OLBcWQHqyNT5swwfyp/rGP0ZYnRHRQuUg4IM30xZr2xmzZDKcxIxf1tEVURWJj7GBLOZlXF2xMa6zbQf6518Rs1KHGoNjZ7ia+uCOgw9UmAqs8+erRw8z2sWjtP15y6/Nbl7r+mIRygCydweBqBH+3/9kUSsW8xlEZsL8z+dwCWYExDUOfbZ2sf/L1a/FczHDiGksT9teUi9visqvtIi/MqG3Sp1EqdxLLn3qRdZesi8WIWduHfdLyep0BEhlxTLJcZV2svlTKQkWR0MfAHT+fyHcCy0vx2mzlipe0k3AcJDWxKzgocmHAv9TDS+6kThjynaY7PfPkFVPgqK3Jx0QwDcLVYB2g5I3dVW3I+/KfdRJr+5ZsBO9D0EMfT71g2LMP1QCjovImw2dsEeBLopdx9JHWOhFZWH3efaDPoiDZ8aQbOcyQt7WWPDQCBgLaXvJ4oGaJ7rlM1jvUPNFZKeN513aY44ksDiAnQQkHJxkziU/FEdx5d4wcqfpPM07LR/aIzKYa3ELG5MoS7ql3VDCJ+vyMINGLF0ECHdKV0/nRD0GmKUtcrbtfcROeuGRlTDtL3GNBLWcWycFxBwkJ2jNAJ70xEFUjguWDbYc2mSTR4J2RE6SI9HujH61jv5WQC1s2rIV2ysST3yf9Gx4fuTjmlAbgkaU0JuN3muoZbXkriF4mGE3yrcUT4FpWT6ykZfUGe3kuM36NCWfLhB3Lwp3o4hZKJe2gnxyTjzyGCEyhP8w8Ab0IgQlJ4J4yo/AUyMt3NEMHiG/+3aNFCdjHIW2wkxYxKy+TL0c/lRpo+QlXiKvJLXRBNnkvyHsUohGuA1Vydx+wHEbEINPhasFACMuW2DJQ1SPq/S7VG0moT6HDmDfFgmTknlOR/93OJXXSJ+urSCG6wJbrJOLqDcHllvAhBpOsLo1yWl91HHygcpqBTKgr/nl580fjq3cbA2HdFZvKvV7XxfPHwSIQkzyuAD2cAJV0EjXBviw7s8OfZALG19BIujLT8cvgFK++UlrRsZ26G4gssC8c05qQOxl6kSvo2tBHbQ3vnKZLu0+ghTCaLdJzv9B8roHPhtM8z0AygykPXhjOd0m5e91U4/Y3ExvOdDGQ6q7HTG3MABObULnWfuGTXLIoB/XSny7W/rdzOcGTUqMJgqDMPikVx5Ky+igigA5Pp0fH32imppKNNs3AN0RQowdNlSgEc36QJk6uPGB4AIfJznndBwxcSguhbcHnAgbj+Ku7zGJ7AYyEyfBNd2juu5jdRAWCnIhels612AOJjEbsIAwyFEve+9nzRMlbTEf7/4D5uHnLmY/QkCS4Mjx
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DB9PR10MB5715.EURPRD10.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(366016)(1800799024)(4022899009)(376014)(38070700018)(7053199007)(8096899003);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: mBSMbSgLxPiNavpTeLwSux+N9VmoW3dSk9wVn4vin7nsTbkl5y8JSxm0ZjGNXqHaDUT16UUGtJwTPqqfzeADQajX5ak1KNT6WVjxxg5YMlTcobxjuMGVixcaoJA7njxQhMLn/t/gFTr+wcQNJ8TLJzmRq7LHE2h3lBTnipWEdPaYUg9F7swNaBg/W3X/l49LLrkfcUOciJld7Sc7H9MCBGb6JXQqXKLGKKMP1wL+twa+QPPl9du6SK+SHZjNjOlvZ8aKRMt3mjN3BaFwiBEtwBwKXSCFbX6DFpx/icS0O+nvfa+Ru4bU4iToB0LAgnNJrH2Hrzv8JwGcmt4uAhfjSvTdKjZ8XlcyNQUaaxOEYUNZvhrK82qqq++EauFylGuUtQO8HCXc1pMpr1nMlk8hNvB4S+OwA3U/ul139y/JSOnzy6aTy4cKpnO4CuAUSfUcU14XqtV1ygAre0tl4jLm/gFepizfND5oSwiLLHjG8oMq7ld0lnYEtuPiN689kIrSR7f2teT0tZ8Mlp280c23ySaolfZKMEcUKYr+jFaplrIBwAaS+LcQfk3SasB8B/FHE6jOak77xG5Pg/s30eB7DKGWaRZ8qAQwNClT2p48Ix315Z6xiKULSR1iAbfD6MFr0ffLZHthpzA9lxFsTa5qZUdp5k6+HNlBc+d7+jngbGgapIlN7PVNt+ErPpknomLDQyJA1EIFVW7hN+moDgHy50RQH92ZWMVKORlN1BuNZ387j9I7WO5b73EVnuzeeUfO/qo8Cn8Onkr1zl/P1PpbwhJzk8V+Fdzq2JFSOy3JikiYMB04kXhD5slq20mqVc3qiOJWkS0683z48JcsguQlM4OEoXG+mn0u1BGT+31Dn2QPRUR0PN6yCpSI5oTwqalfLL3aXXFm64awqH28oN5ilxIDjwLctBYYMSHaXWldTRqX371lpveleBdTfv25lAGSR4Onxf4WodranLww3Vwl0WK29Erz8klUrMxbGa/R9Ies8ZggtUCvoXHvSjzjuGbmx5rlIuaGhatpybCM0KrgVC0Q9wurYNSBorctj0z2jkMy4XGVIImnCtpeN00qzzMhfBc8UDPoWpi65e/r7J7obKD5hZA8tKdxiO471kkPaFa8WnKxb1m5xy0oXsklrTGNQULIAO4h/V1cjQn3rEe7j3OLT9ZCGrBKXkdpsmWPi43+xg8vn7ICTGmtXtRW1xkeMZX47OUpIKgxjyBhhZWchnK3rG/WkO4Ok6AtUWumGYarJquT7CVIJCMO0bg+gXBcfuVBqnnnEnBxF2rhPvwU+1C0U5WDmgMPRMjiTy61TLhH4RZ3Y412OLFzn4DMtobzRWoV+HZcofiYpmmTb4MOwuh4nrlNW/j40ufOI8u3lAUism/eXs/HG86dgi4BM0KPrhbt8jgGW3Xv123rlugmf999246RhuoXzjQtK7C82IZNFljqi8H7D1OCiS2wtpQndpaY7PtmElULK2jlmZsOFzxKKxUKptqV1b0BdBOusXYNHXUYosUUchKrAYfd47ClUW6qSKToeemUDaqn/VbbYJzRKsNK4RscJAFuASzwbtiFDdXi208Av4K2lDO+oCDnXEQjZNTpchUlAJuelqss7g==
Content-Type: multipart/alternative; boundary="_000_DB9PR10MB5715DEAA9C12F3F7864F36B7FE212DB9PR10MB5715EURP_"
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DB9PR10MB5715.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 766270eb-310c-430b-d03d-08dd094bdc39
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Nov 2024 10:12:37.7958 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: MFdC0pFKUD6j1dwpcK4kzbGvATnCB4QEmWdiFY70gDRahQQENO8/QD+2llIZ/3V5nY3LPeG5irUHIpQbDVSSbIle9XNYMI5VHmUKlA4MTxo=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB9PR10MB6692
Message-ID-Hash: 4JVILEN4KKATFIZQFQPUO7ZWLLMLZ6UN
X-Message-ID-Hash: 4JVILEN4KKATFIZQFQPUO7ZWLLMLZ6UN
X-MailFrom: hendrik.brockhaus@siemens.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spasm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "spasm@ietf.org" <spasm@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [lamps] Re: [EXTERNAL] Call for adoption of draft-brockhaus-lamps-automation-keyusages/
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Gx6DptAlXwin65L5HwpMIPANaks>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Owner: <mailto:spasm-owner@ietf.org>
List-Post: <mailto:spasm@ietf.org>
List-Subscribe: <mailto:spasm-join@ietf.org>
List-Unsubscribe: <mailto:spasm-leave@ietf.org>
Mike Thank you for your support :-) Russ Like Mike wrote, the id-kp-codeSigning is used for signing DLLs or other executable code. The id-kp-updateSigning is supposed to sign a complete SW and FW package for a dedicated device including many files, potentially including files signed using id-kp-codeSigning. It is a different abstraction layer. And yes, for usage of theses OIDs in the EU-Rail environment, this will be specified in ERJU standards. Hendrik Von: Michael StJohns <msj@nthpermutation.com> Gesendet: Dienstag, 19. November 2024 20:47 An: spasm@ietf.org Betreff: [lamps] Re: [EXTERNAL] Call for adoption of draft-brockhaus-lamps-automation-keyusages/ Hi Russ - Maybe? id-kp-codeSigning says "Signing of downloadable executable code". id-kp-updateSigning says - "verifying signatures of secure software or firmware update packages" The former could be the code, the latter could be the package containing the signed code along with the directions to update a device with the code? The former might be used by the device manufacturer, with the latter used by the device operator/owner. In any event, the relying party is going to have to decide what these mean to them in a concrete manner. I'd expect that EU-Rail will probably write something describing the behavior for "certified" devices in its space. I think what's here is sufficiently clear (especially considering most OIDs don't have much more than this) to just go forward. E.g. there's no global document that says "you must reject a signature over executable code unless it's signed by a key in a cert with id-kp-codeSigning", but there are documents like that for say signing javacode or a particular router vendors code load. To answer Mike's question - no, these don't affect XML or YAML unless we write a document that says they do and this one doesn't say that. Mike ps - I can see the possible need for three different signature KPs - one to sign the code, one to sign the update package and perhaps one to permit the file to be uploaded to the device and have the update package processed. On 11/19/2024 12:00 PM, Russ Housley wrote: Hendrik: I have a hard time seeing why id-kp-updateSigning is needed. It seems to me that id-kp-codeSigning already meets this need. Russ On Nov 19, 2024, at 11:54 AM, Brockhaus, Hendrik <hendrik.brockhaus@siemens.com><mailto:hendrik.brockhaus@siemens.com> wrote: Mike, Rich Thank you for your feedback. Please see some general explanation upfront and further responses inline below. The keyPurpose OIDs are not only relevant in the EU-Rail environment, but also in other industries that are working on the application of the IEC 62443 framework for security in industrial control systems. The EU-Rail project is the one that has made the most progress in standardizing a security pillar in which details like keyPurpose OIDs must be defined across vendors. However, since the use cases are becoming relevant in other industries, it would not be helpful in my opinion to register OIDs for the same purpose per industry. This also applies to the safetyCommunication keyPurpose OID. Safety communication is often not secure. In addition to RaSTA from the railway environment, there is also PROFISafe from industrial automation, both of which are safe but not secure. Standard protocols such as TLS or IPSEC are used to secure them. Here it is important to identify whether the remote station is an authorized endpoint for safety communication. See also my planned presentation https://datatracker.ietf.org/meeting/121/materials/slides-121-lamps-new-ekus-for-automation-00 Hendrik Von: Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org<mailto:Mike.Ounsworth=40entrust.com@dmarc.ietf.org>> Gesendet: Montag, 18. November 2024 21:51 An: Russ Housley <housley@vigilsec.com<mailto:housley@vigilsec.com>>; LAMPS <spasm@ietf.org<mailto:spasm@ietf.org>> Betreff: [lamps] Re: [EXTERNAL] Call for adoption of draft-brockhaus-lamps-automation-keyusages/ I have basically the same feedback that I submitted on Oct 16 [1]. Basically I feel like these EKUs are too broad. It’s defining 4 new EKUs: * id-kp-configSigning * id-kp-trustanchorSigning * id-kp-updateSigning * id-kp-safetyCommunication The first three feel too broad with weird overlap and implications for things already in 5280 – does the first one mean that I can no longer use a regular no-EKU cert to sign XML or YAML content? [HB] All key Purpose OIDs are optional to use. No PKI should have to use these OIDs if their subscribers do not have use cases where they benefit from the use of these OIDs. In other RFCs, there are also keyPurpose OIDs defined, which have been defined quite broadly. For example, RFC 9509 defines an OID for OAuth 2.0 Access Tokens, but the document doesn't require that keyPurpose always be set in an OAuth 2.0 Access Token. Section 3 of RFC 9509 states “Network Functions that verify the signature of […] SHOULD require that corresponding KeyPurposeIds be specified by the EKU extension. If the certificate requester knows the certificate users are mandated to use these KeyPurposeIds, it MUST enforce their inclusion.”. As in RFC 9509, the OIDs in our document are defined in an IETF document stating the purpose, the policy for using the OID is then defined in the specific standards of the vertical, e.g. 3GPP or EJRU. RFC 9336 makes this even more explicit. Section 3 of RFC 9336 states "Document-Signing applications MAY require that the EKU extension be present and that the id-kp-documentSigning be indicated in order for the certificate to be acceptable to that Document-Signing application.". If it helps, we can make the following change to make it clear that using the OIDs is optional. OLD Systems or applications that verify the signature of a general-purpose or trust anchor configuration file, the signature of a software or firmware update package, or the authentication of a communication peer for safety-critical communication SHOULD require that corresponding KeyPurposeIds be specified by the EKU extension. NEW Systems or applications that verify the signature of a general-purpose or trust anchor configuration file, the signature of a software or firmware update package, or the authentication of a communication peer for safety-critical communication MAY require that corresponding KeyPurposeIds be specified by the EKU extension. Do we need to start putting the second one on self-signed root certs? [HB] No, the OID is defined for “verifying signatures of trust anchor configuration files” not for self-signed root certificates. How does the third one interact with id-kp-codeSigning that is already defined in RFC 5280? [HB] In my opinion, the scope of OID id-kp-codeSigning is too broad to differentiate the different types of software or firmware to be installed on a device. Therefore, we require that an OID for “verifying signatures of secure software or firmware update packages” is worth to be defined. And again, if a PKI does not see the need for this differentiation, it can easily continue using id-kp-codeSigning. For the last one, what does “safetyCommunication” mean? [HB] As explained above, safety communication refers to, e.g., RaSTA or PROFIsafe. How is a CA supposed to know if a TLS cert they are issuing will be used for “safety-critical communication based on TLS or other protocols” and therefore require this EKU? [HB] That's an interesting question. How can a CA know that a certificate it issues should be used for code signing, OAuth 2.0 Access Token signing, document signing, or TLS client authentication? In many environments, e.g., also in 3GPP and EJRU, the PKI is used specifically for this environment. Thus, within the enrollment and operational procedures, it is defined which entity or which RA is allowed to request a certificates for which purpose. The introduction leads me to believe that this intended purpose of this document is for “EURJU documents for safety-critical communication” – so it’s sorta a “if you need these, then you’ll know, and everyone else can ignore them”. [HB] As stated above, the OIDs shall be optional to use. The document just defines the purpose indicated if they are used. To that end, should these new EKUs be scoped to the EURJU (Europe Rail Joint Undertaking)? IE register them as “id-kp-eurju-configSigning” ? That would make it clear that they are intended specifically for EURJU applications, and not generally applicable for Internet. [HB] As stated above, the generic use cases are also applicable for other verticals. I think it is more following the spirit of the EKU to define an OID for a purpose and not for a purpose scoped to a vertical. This could end up in too many vertical-specific OIDs for the same purpose. I would like to sort out this scoping question before I vote in favour of adoption. [1]: https://mailarchive.ietf.org/arch/msg/spasm/Vl1LINXWE9PO3PGoe2aPbX1l2KU/ --- Mike Ounsworth From: Russ Housley <housley@vigilsec.com<mailto:housley@vigilsec.com>> Sent: Monday, November 18, 2024 11:59 AM To: LAMPS <spasm@ietf.org<mailto:spasm@ietf.org>> Subject: [EXTERNAL] [lamps] Call for adoption of draft-brockhaus-lamps-automation-keyusages/ The authors have asked the LAMPS WG to adopt this I-D. It assigns four new extended key usage values. The Internet-Draft is here: https: //urldefense. com/v3/__https: //datatracker. ietf. org/doc/draft-brockhaus-lamps-automation-keyusages/__;!!FJ-Y8qCqXTj2!dyEqI2HZVMIUs-GK_AUwv-Fy5mpac7kwVgarbJoO-WI5I4F8qcmL-wkUUoANDeocPy-d8XaV0oqw1CbeDtW4nKQSiQQy$ The authors have asked the LAMPS WG to adopt this I-D. It assigns four new extended key usage values. The Internet-Draft is here: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-brockhaus-lamps-automation-keyusages/__;!!FJ-Y8qCqXTj2!dyEqI2HZVMIUs-GK_AUwv-Fy5mpac7kwVgarbJoO-WI5I4F8qcmL-wkUUoANDeocPy-d8XaV0oqw1CbeDtW4nKQSiQQy$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-brockhaus-lamps-automation-keyusages/__;!!FJ-Y8qCqXTj2!dyEqI2HZVMIUs-GK_AUwv-Fy5mpac7kwVgarbJoO-WI5I4F8qcmL-wkUUoANDeocPy-d8XaV0oqw1CbeDtW4nKQSiQQy$> Please voice your support or concerns for the LAMPS WG adoption of this document by 2 December 2024. For the LAMPS WG Chair, Russ _______________________________________________ Spasm mailing list -- spasm@ietf.org<mailto:spasm@ietf.org> To unsubscribe send an email to spasm-leave@ietf.org<mailto:spasm-leave@ietf.org> _______________________________________________ Spasm mailing list -- spasm@ietf.org<mailto:spasm@ietf.org> To unsubscribe send an email to spasm-leave@ietf.org<mailto:spasm-leave@ietf.org>
- [lamps] Call for adoption of draft-brockhaus-lamp… Russ Housley
- [lamps] Re: Call for adoption of draft-brockhaus-… StJohns, Michael
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Mike Ounsworth
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Salz, Rich
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael Richardson
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Russ Housley
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael StJohns
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael StJohns
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Mike Ounsworth
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Mike Ounsworth
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Salz, Rich
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Salz, Rich
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Russ Housley
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Mike Ounsworth
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Salz, Rich
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael Richardson
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael Richardson
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael Richardson
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael Richardson
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Salz, Rich
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael Richardson
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Brockhaus, Hendrik
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael Richardson
- [lamps] Re: [EXTERNAL] Call for adoption of draft… StJohns, Michael
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Alan DeKok
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael Richardson
- [lamps] Re: [EXTERNAL] Call for adoption of draft… Michael StJohns
- [lamps] Re: [EXTERNAL] Call for adoption of draft… David von Oheimb
- [lamps] Re: Call for adoption of draft-brockhaus-… Brockhaus, Hendrik
- [lamps] Re: Call for adoption of draft-brockhaus-… Michael Richardson
- [lamps] Re: Call for adoption of draft-brockhaus-… Brockhaus, Hendrik
- [lamps] Re: Call for adoption of draft-brockhaus-… Russ Housley
- [lamps] Re: Call for adoption of draft-brockhaus-… Michael Richardson
- [lamps] Re: Call for adoption of draft-brockhaus-… Brockhaus, Hendrik
- [lamps] Re: Call for adoption of draft-brockhaus-… Russ Housley
- [lamps] Re: Call for adoption of draft-brockhaus-… Brockhaus, Hendrik