Re: [lamps] Proposed Re-Chartering Text for CMP updates and lightweight profile (RE: Follow-up on lightweight CMP profile)
"Panos Kampanakis (pkampana)" <pkampana@cisco.com> Wed, 08 May 2019 14:00 UTC
Return-Path: <pkampana@cisco.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 B5C6612011C for <spasm@ietfa.amsl.com>; Wed, 8 May 2019 07:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, SPF_PASS=-0.001, URIBL_BLOCKED=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=eneNO0rV; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=E33TvTrY
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 qA376VpzYxRq for <spasm@ietfa.amsl.com>; Wed, 8 May 2019 07:00:21 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 820F8120089 for <spasm@ietf.org>; Wed, 8 May 2019 07:00:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15840; q=dns/txt; s=iport; t=1557324021; x=1558533621; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Bu0c0mWE/EpBZkRe4SWHifmj3H43aY/rPAC8mLXi77I=; b=eneNO0rVP9a9pdev18JNWcYYCgxno9DqV7ljh/5Y/2IandQzcj6zW7cd UNjvNmjYSu0Bwo7cyL8qd3YZ1WG3Hu2fJRKaRovV03WQO3jUdEUREQqNc eRmrbT9q7JKhXlOQ0fNyC7QJPF0SqPsJNFHRKMQIC5wasxmNPJz05Brn2 U=;
IronPort-PHdr: 9a23:poRNABY3raHzZWIXvcifQIr/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavybCU/BM1EXXdu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AJAABG4NJc/5tdJa1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwIBAQEBAQsBgQ4vJCwDaVUgBAsoh1cDjn2CV5JXhE2BLhSBEANUCQcBARgBCQsCgQRdgl4CgggjNgcOAQMBAQQBAQIBBG0cDIVKAQEBBAEBEBsTAQEsBAcBDwIBCBEEAQEkBAcnCxQJCAEBBAENBQgagnsEAoEdTQMdAQ6iBgKBNYhfgiCCeQEBBYR8AxWCDgMGgTIBigqBQxeBQD+BEUaCHi4+gmEBAQIYgQsJARIBISsJgwaCBCKLHBEkhlaICY0WCQKCCYYdjE2CEJNHiGqDOoEhk1UCBAIEBQIOAQEFgVUBMQ1YcXAVO4JsE4FYJDeDOIUUhT9yAQEBAYEljSOBVG8BAQ
X-IronPort-AV: E=Sophos;i="5.60,446,1549929600"; d="scan'208,217";a="268815643"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 May 2019 14:00:20 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x48E0KnR026314 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 May 2019 14:00:20 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 8 May 2019 09:00:19 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 8 May 2019 09:00:17 -0500
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 8 May 2019 09:00:17 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rve7vHAfJ2S1/wgRCFAX5zlLiieKAh0yCm0/uZZjpmA=; b=E33TvTrYKMnS2kok0iNSS3DDNmudNYNRN5qDNVbK6VBOradHQjK7IHiOw9Wk1tEFXIZBXhkTYu2TVz0k0ElIRrXU6iOOR2kjwsbwUzLJ4lGNg4ixb7ltgY79bgAdG9SZUvO2eEalcC6xfQxDgTNDDn1HCz49nbubgOZYVXUq/Ms=
Received: from MWHPR11MB1838.namprd11.prod.outlook.com (10.175.53.141) by MWHPR11MB1344.namprd11.prod.outlook.com (10.169.232.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.12; Wed, 8 May 2019 14:00:15 +0000
Received: from MWHPR11MB1838.namprd11.prod.outlook.com ([fe80::4964:5495:9121:8f12]) by MWHPR11MB1838.namprd11.prod.outlook.com ([fe80::4964:5495:9121:8f12%7]) with mapi id 15.20.1878.019; Wed, 8 May 2019 14:00:15 +0000
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "spasm@ietf.org" <spasm@ietf.org>, Russ Housley <housley@vigilsec.com>, "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
CC: Jim Schaad <ietf@augustcellars.com>, "steffen.fries@siemens.com" <steffen.fries@siemens.com>
Thread-Topic: Proposed Re-Chartering Text for CMP updates and lightweight profile (RE: Follow-up on lightweight CMP profile)
Thread-Index: AdUFfDdARgDJEG61S0aIn5X7GJC6HQAKDYZw
Date: Wed, 08 May 2019 14:00:15 +0000
Message-ID: <MWHPR11MB1838E6295E39B04C0591DC28C9320@MWHPR11MB1838.namprd11.prod.outlook.com>
References: <AM0PR10MB24028210BCE560C64195A74EFE320@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <AM0PR10MB24028210BCE560C64195A74EFE320@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pkampana@cisco.com;
x-originating-ip: [2001:420:c0c4:1006::f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3fe00d9d-7a30-447f-e053-08d6d3bd7f17
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:MWHPR11MB1344;
x-ms-traffictypediagnostic: MWHPR11MB1344:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <MWHPR11MB1344FDD82C94B26D4FB3AEFDC9320@MWHPR11MB1344.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0031A0FFAF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(366004)(396003)(376002)(346002)(136003)(199004)(53754006)(189003)(33656002)(46003)(76176011)(74316002)(68736007)(53936002)(102836004)(6506007)(55016002)(71190400001)(790700001)(186003)(316002)(71200400001)(6116002)(236005)(15650500001)(6436002)(2420400007)(14444005)(256004)(446003)(606006)(229853002)(73956011)(9686003)(476003)(486006)(6306002)(54896002)(7736002)(11346002)(53546011)(2906002)(25786009)(8676002)(8936002)(5660300002)(966005)(478600001)(9326002)(99286004)(14454004)(66446008)(110136005)(6246003)(81166006)(76116006)(4326008)(52536014)(81156014)(66556008)(66476007)(2501003)(7110500001)(54906003)(7696005)(64756008)(86362001)(66946007); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1344; H:MWHPR11MB1838.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: zjjmc8+gC3kWwmsEuzpzTvLn2sxD+ZseB85Sa6fvihGHpWdxWDLZAX2RGrprJXeO+C/Wj072OW/1ogFOryF/xhMX83ugIJVMHZgBZ7C61tcjMsu3N2qcdhEtAOLmxhXeQZPKe5kqsOOgJR3O8WuWhYtSwl23mpZ4Tqo6sD9jE2eAxmSFGDOV5lpue89P4Q6zZJfIu1EGbOVLZ9McMZjmeVv1aaAuNk1UtEP77YXg9x8FNEHFFKmGyE04+9gGEa32MxAC9BCtfxy81lw+wMgAd+21QEwNNbWJkCKE5UXTjh0qV0WGpW0Wp102dSbrgyokunzvtzrovFUX1nzd4WtLMLT0m1et4yqhW4q9j0WJ2txDJimeBqJk6szeyUwKK5vj8Rl/JpOYzT9uBRV0XdkKDf1lAqt6456k6jxLMnAgMP0=
Content-Type: multipart/alternative; boundary="_000_MWHPR11MB1838E6295E39B04C0591DC28C9320MWHPR11MB1838namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3fe00d9d-7a30-447f-e053-08d6d3bd7f17
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2019 14:00:15.2103 (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-Transport-CrossTenantHeadersStamped: MWHPR11MB1344
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/nHRqnpwBec1Tqy9KKgPnnwbzfDo>
Subject: Re: [lamps] Proposed Re-Chartering Text for CMP updates and lightweight profile (RE: Follow-up on lightweight CMP profile)
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: Wed, 08 May 2019 14:00:25 -0000
Hi Hendrik, Long time since we talked. With such a profile, I have a concern that what happened with SCEP, CMC, CMPv2, EST is likely to happen in constrained environments. Using two or more protocols (EST-coaps, a CMP profile over different transports, and others) that do similar things would lead to fragmentation and confuse vendors that want to pick one. I am not sure I have heard a broad need for a CMP profile in ACE. If this is a single vendor need, does IETF even need to standardize this CMP profile? Panos From: Spasm <spasm-bounces@ietf.org> On Behalf Of Brockhaus, Hendrik Sent: Wednesday, May 08, 2019 5:10 AM To: spasm@ietf.org; Russ Housley <housley@vigilsec.com> Cc: Jim Schaad <ietf@augustcellars.com>; steffen.fries@siemens.com Subject: [lamps] Proposed Re-Chartering Text for CMP updates and lightweight profile (RE: Follow-up on lightweight CMP profile) Hi Russ, all, as discussed at IETF104 and on this list we would like to spend further work on updating and profiling CMP focusing on industrial use cases. To get input, feedback and support from LAMPS we propose the following charter text. As certificate management gets increasingly important in industrial 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 industrial environments it needs to be enhanced to more efficiently support of industrial 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. Hendrik Von: Russ Housley <housley@vigilsec.com<mailto:housley@vigilsec.com>> Gesendet: Mittwoch, 8. Mai 2019 02:18 An: Brockhaus, Hendrik (CT RDA ITS SEA-DE) <hendrik.brockhaus@siemens.com<mailto:hendrik.brockhaus@siemens.com>> Cc: spasm@ietf.org<mailto:spasm@ietf.org>; Jim Schaad <ietf@augustcellars.com<mailto:ietf@augustcellars.com>>; Fries, Steffen (CT RDA ITS) <steffen.fries@siemens.com<mailto:steffen.fries@siemens.com>> Betreff: Re: [lamps] Follow-up on lightweight CMP profile Hendrik: The current re-charter is about two weeks away. You would need to propose text for the charter on this list, and see if there are people that will review and implement. Russ On May 3, 2019, at 4:52 AM, Brockhaus, Hendrik <hendrik.brockhaus@siemens.com<mailto:hendrik.brockhaus@siemens.com>> wrote: Hi all Referring to the Email thread 'Seeking guidance on proceeding with question from IETF-104 presentation on lightweight CMP profile' and to the outcome of the WG meeting, we want to summarize the current state of the discussion. The discussion we had with Jim motivate a split of the current draft into a CMP Updates and a CMP Profile document. The update of CMP is needed because we identified at least two point where a change to CMP is needed: - Change the type of encryptedCert from EncryptedValue to EncryptedKey for ECC and post-quantum algorithm support - Extend the RootCAUpdate announcement message to e request/response message to enable requesting the update from the client side The remaining points from the initial email were seen as profiling topic and would therefore be handled in the CMP Profile document.. @Russ, how do you see the status of the current re-chartering process? Would you support to add both, or at least the CMP Updates, activities under the revised charter? - Hendrik _______________________________________________ Spasm mailing list Spasm@ietf.org<mailto:Spasm@ietf.org> https://www.ietf.org/mailman/listinfo/spasm<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fspasm&data=02%7C01%7Chendrik.brockhaus%40siemens.com%7Cb2dc4e66b2644d53d64308d6d34aa72c%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C636928715140199163&sdata=vbsWP%2FRwxnN6qgWKB2Qbq7aC5CFobDEJCTqJOBkSIJk%3D&reserved=0>
- [lamps] Proposed Re-Chartering Text for CMP updat… Brockhaus, Hendrik
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Panos Kampanakis (pkampana)
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Peylo, Martin (Nokia - FI/Espoo)
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Brockhaus, Hendrik
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Dr. Pala
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Brockhaus, Hendrik
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Panos Kampanakis (pkampana)
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Panos Kampanakis (pkampana)
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Brockhaus, Hendrik
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Brockhaus, Hendrik
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Panos Kampanakis (pkampana)
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Brockhaus, Hendrik
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Brockhaus, Hendrik
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Fries, Steffen
- Re: [lamps] Proposed Re-Chartering Text for CMP u… Brockhaus, Hendrik
- [lamps] Support for working on the lightweight CM… Russ Housley
- Re: [lamps] Support for working on the lightweigh… Tomas Gustavsson
- Re: [lamps] Support for working on the lightweigh… Peylo, Martin (Nokia - FI/Espoo)
- Re: [lamps] Support for working on the lightweigh… Brockhaus, Hendrik
- Re: [lamps] Support for working on the lightweigh… Panos Kampanakis (pkampana)
- Re: [lamps] Support for working on the lightweigh… Michael Richardson
- Re: [lamps] Support for working on the lightweigh… Fries, Steffen
- Re: [lamps] Support for working on the lightweigh… Tomas Gustavsson
- Re: [lamps] Support for working on the lightweigh… Peylo, Martin (Nokia - FI/Espoo)
- Re: [lamps] Support for working on the lightweigh… Michael Richardson
- Re: [lamps] Support for working on the lightweigh… Michael Richardson
- Re: [lamps] Support for working on the lightweigh… Tomas Gustavsson
- [lamps] Interest to standardize PKI REST APIs? Tomas Gustavsson
- Re: [lamps] Support for working on the lightweigh… Brockhaus, Hendrik
- Re: [lamps] Interest to standardize PKI REST APIs? Brockhaus, Hendrik
- Re: [lamps] Interest to standardize PKI REST APIs? Michael Richardson
- Re: [lamps] Interest to standardize PKI REST APIs? Tomas Gustavsson
- Re: [lamps] Interest to standardize PKI REST APIs? Salz, Rich
- Re: [lamps] Interest to standardize PKI REST APIs? Tomas Gustavsson
- Re: [lamps] Interest to standardize PKI REST APIs? Salz, Rich
- Re: [lamps] Interest to standardize PKI REST APIs? Tomas Gustavsson
- Re: [lamps] Interest to standardize PKI REST APIs? Salz, Rich
- Re: [lamps] Interest to standardize PKI REST APIs? Tomas Gustavsson
- Re: [lamps] Interest to standardize PKI REST APIs? Brockhaus, Hendrik
- Re: [lamps] Interest to standardize PKI REST APIs? Tomas Gustavsson
- Re: [lamps] Interest to standardize PKI REST APIs? Brockhaus, Hendrik
- Re: [lamps] Interest to standardize PKI REST APIs? Salz, Rich
- Re: [lamps] Interest to standardize PKI REST APIs? Dr. Pala
- Re: [lamps] Interest to standardize PKI REST APIs? Tomas Gustavsson