IETF Logo Mail Archive

Re: [lamps] Request to add the CMP activities to the LAMPS charter

"Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com> Mon, 29 July 2019 11:59 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 8625512019B for <spasm@ietfa.amsl.com>; Mon, 29 Jul 2019 04:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.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 ZuU7bankDNCA for <spasm@ietfa.amsl.com>; Mon, 29 Jul 2019 04:59:09 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30070.outbound.protection.outlook.com [40.107.3.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89E0B120120 for <spasm@ietf.org>; Mon, 29 Jul 2019 04:59:08 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=V0H0VarSg1x1fVDy2DRNu0yUlOM0k2T/FrKOJEKbJbux3aL9Q30mdXg3MS19N/cRQJSv7LCxgg1MWGozAF2vcGpaZ0kEcpnruoNaoldIS/MyIeY5VuCo3C7FfWBh7f0OJ3+M3bGvs0rK0PyIsf46MFiuP6y0khNQxDuEnUKe8u2TobYbc0CdBQcbvYFibImb2blBMeSo7x7ZX3ZO3vsng9FAml8z9qprq0Pf8KqpHG33vPwmOkqcF6nJmL47veDUxY5tOAIuxz96AQyfJ8/wfC1mfPEX97zEId8OCwm20uYgclOzcCKdSMQJz8tc+/FS9rgtRAP0lEExsFlah9bWog==
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=OEuQYCjQ7mzdTQnhiT7DaqzMy8ScntvSmUuPYQoFDrM=; b=TqFkVA1NG/w+etPDCBkx4kUfnWmo7l6yLHVenCke5Rled0kWY5JLRE7HiCPonAXZF9Y4uhrNjbzGmQEzyIJhIAEdSqOI/o91HATWd8dHqnqqeYCHqsvASh3lAStmKvs1CVBmyvvtmt5tALS13JnVBYoVJegE/na0PClerN0YePPw1ahY1xfYiFdx5LZqXRgxRwqS22ydZ8dTGBKnG6UH6LM5AQAR2ad6Bivt5OgVoAU9iZKGbEX3/qGwTe8CboHcwYdMsOUAnKN8K/nEyGls1g772PsniHHIxY1/7qXw2mJpsnD8q0OZx+PKg7Pvz0A+fFA9H0hG1ZHutu3AksDnsw==
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.onmicrosoft.com; s=selector2-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OEuQYCjQ7mzdTQnhiT7DaqzMy8ScntvSmUuPYQoFDrM=; b=FZvpT+gp8wC51mFyQONZSEaO/2yAAyBmWrRvd68Yg2TTBi1UQLSKy+LF2GYCBeUNmcyGNGcQ/6xSwzUj5PicvL3D2DNZwT06/XTDcR+D3FE4fw87g0IYMwfclCKs9JvLo9/VzSAHiHzkCxF+NYbrfv5EA+IzaNnZpevmh8aMW9A=
Received: from DB7PR10MB2411.EURPRD10.PROD.OUTLOOK.COM (20.177.121.209) by DB7PR10MB2379.EURPRD10.PROD.OUTLOOK.COM (20.176.239.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.10; Mon, 29 Jul 2019 11:59:06 +0000
Received: from DB7PR10MB2411.EURPRD10.PROD.OUTLOOK.COM ([fe80::7113:bf0:9bf8:ee0c]) by DB7PR10MB2411.EURPRD10.PROD.OUTLOOK.COM ([fe80::7113:bf0:9bf8:ee0c%7]) with mapi id 15.20.2115.005; Mon, 29 Jul 2019 11:59:06 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: Russ Housley <housley@vigilsec.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] Request to add the CMP activities to the LAMPS charter
Thread-Index: AdVC/1yDqiHBKiMuSN6L6Z+PFQlNYgACmNaAACG9Q+AAEkxggACKicWw
Date: Mon, 29 Jul 2019 11:59:06 +0000
Message-ID: <DB7PR10MB2411D0F70F7188010D97CC70FEDD0@DB7PR10MB2411.EURPRD10.PROD.OUTLOOK.COM>
References: <AM0PR10MB24020F02CF348E7D2C028B1FFEC10@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM> <1FD547B6-F127-4DD7-AE56-989E037AB7A6@vigilsec.com> <AM0PR10MB24024BD359A24032891C7E17FEC00@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM> <4CC67DC2-C5DB-4D0D-82D6-30CB3F17B6CA@vigilsec.com>
In-Reply-To: <4CC67DC2-C5DB-4D0D-82D6-30CB3F17B6CA@vigilsec.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-document-confidentiality: NotClassified
authentication-results: spf=none (sender IP is ) smtp.mailfrom=hendrik.brockhaus@siemens.com;
x-originating-ip: [195.145.170.166]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5773438e-79fe-4244-d355-08d7141c285d
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:DB7PR10MB2379;
x-ms-traffictypediagnostic: DB7PR10MB2379:
x-microsoft-antispam-prvs: <DB7PR10MB2379B1EB8867DDD675EB405AFEDD0@DB7PR10MB2379.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 01136D2D90
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(396003)(346002)(39860400002)(136003)(376002)(199004)(189003)(53936002)(7696005)(8676002)(81156014)(81166006)(8936002)(76176011)(33656002)(99286004)(66946007)(54896002)(6306002)(55016002)(76116006)(9686003)(236005)(19627235002)(71200400001)(71190400001)(86362001)(110136005)(316002)(66446008)(66476007)(64756008)(5660300002)(25786009)(2501003)(66556008)(52536014)(68736007)(790700001)(66574012)(186003)(6506007)(74316002)(102836004)(3846002)(6116002)(53546011)(478600001)(26005)(256004)(14444005)(486006)(6436002)(14454004)(11346002)(446003)(476003)(2906002)(66066001)(7736002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB7PR10MB2379; H:DB7PR10MB2411.EURPRD10.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: siemens.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: gleO+/HK+yVEupPwf8/+tUDNgCSMvivWm7xJ0T2tPi6oH0kwBZABNmHqhWdpxpIDaDfHtlsXm5e7ITSHzJkMxlSaL7uCGdc04esNaQ30XltomxzpI9na0uGL2QXgpRu/+lFvAE+/s8qSDiurF7mIFi0TaY/XOYkHHxvXDNxahDyb51pn6Z2+J5otdS0fIlusnm4fkxgdoaUFK2AjGQ02twQVTFB1K/VGH3mUCUwjlm+3sSnS72SJr7Rf32zLE3mDGLfslEmYv1ilPtG6DQQ5iDeZjPzi7RDsKkDYyZqJsnJF3isxt6ksf1ZsMKl7h4HZ/V0E2KdK45ePz0kXhcWcPcXhlzHTDsyqNnVIqFSSACfwoLffkybIkrrc+QMtbNYzLrI+OsavEn9ycwXHO7mMq0JwJcUxjjPmPjM6EOsADPk=
Content-Type: multipart/alternative; boundary="_000_DB7PR10MB2411D0F70F7188010D97CC70FEDD0DB7PR10MB2411EURP_"
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5773438e-79fe-4244-d355-08d7141c285d
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jul 2019 11:59:06.3792 (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: hendrik.brockhaus@siemens.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR10MB2379
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Jc3FC4Eo88ZIFLQXUwN-LjonxS4>
Subject: Re: [lamps] Request to add the CMP activities to the LAMPS charter
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2019 11:59:13 -0000

Just for clarity I would like to add the updates to CMP to the charter text as it is currently not covered by the general charter introduction.

New text:
8. As certificate management gets increasingly important in many
environments, it needs to be tailored to the specific needs. CMP is an
existing protocol offers a vast range of certificate management options,
and CMP is already being used in different industrial environments. The
LAMPS WG will develop a "lightweight" profile of CMP to more efficiently
support of these use cases and better facilitate interoperable
implementation, while preserving cryptographic algorithm agility.
Necessary updates and clarifications to CMP will be specified in a
separate document.

Hendrik

Von: Spasm <spasm-bounces@ietf.org> Im Auftrag von Russ Housley
Gesendet: Freitag, 26. Juli 2019 19:45
An: spasm@ietf.org
Betreff: Re: [lamps] Request to add the CMP activities to the LAMPS charter

I am just trying to simplify the language and provide a little bit of flexibility.  Please review the proposed text and milestones.

Russ

= = = = = = =

8. As certificate management gets increasingly important in many
environments, it needs to be tailored to the specific needs. CMP is an
existing protocol offers a vast range of certificate management options,
and CMP is already being used in different industrial environments. The
LAMPS WG will develop a "lightweight" profile of CMP to more efficiently
support of these use cases and better facilitate interoperable
implementation, while preserving cryptographic algorithm agility.

March 2020 - WG adoption of Internet-Drafts for CMP

October 2020 - Forward CMP drafts to IESG for publication on the standards-track




On Jul 26, 2019, at 5:04 AM, Brockhaus, Hendrik <hendrik.brockhaus@siemens.com<mailto:hendrik.brockhaus@siemens.com>> wrote:

“As certificate management gets increasingly important in many environments, it needs to be tailored to the specific needs. CMP as existing protocol offers a vast range of options. As it is already being applied in different industrial environments it needs to be enhanced to more efficiently support of these use cases, crypto agility and specific communication relations on the one hand and profiled to the necessary functionality on the other hand to ease application and to better facilitate interoperable implementation.”

v2.46.0 | Report a Bug | By Email | System Status