Re: [lamps] Proposed Re-Chartering Text for CMP updates and lightweight profile (RE: Follow-up on lightweight CMP profile)

Tomas Gustavsson <tomas.gustavsson@primekey.com> Wed, 08 May 2019 11:05 UTC

Return-Path: <tomas.gustavsson@primekey.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 7F7E7120094 for <spasm@ietfa.amsl.com>; Wed, 8 May 2019 04:05:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=primekey.com header.b=asvsyzyw; dkim=pass (1024-bit key) header.d=primekey.com header.b=asvsyzyw
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 ZtdwSZwQGxaZ for <spasm@ietfa.amsl.com>; Wed, 8 May 2019 04:05:16 -0700 (PDT)
Received: from mail.primekey.com (mail.primekey.com [84.55.121.163]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00B1612003E for <spasm@ietf.org>; Wed, 8 May 2019 04:05:15 -0700 (PDT)
Received: from mail.primekey.com (localhost [127.0.0.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.primekey.com (Postfix) with ESMTPS id 182946AA0090 for <spasm@ietf.org>; Wed, 8 May 2019 13:05:10 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=primekey.com; s=mail; t=1557313510; bh=TERkS9tkH1nY0LjDzDDcjg4ERgFvnow+grCXdTdMQ9o=; h=Subject:To:References:From:Date:In-Reply-To:From; b=asvsyzywyvL0EuQrCLEZQtMwrqPAwhXTgatIuVnFbhhc2a9SOYg1zJKtFphVRcae0 ZFjqO+AQ9oBZzl84MOg23iARSaK9SLEoU9O/m8oDHEskJ7osouau33/adwdRMhBG+/ C4LZrmacT0nJKqn4azMDmZemcjCSNOyXPYoNtu+0=
Received: from [192.168.43.22] (unknown [94.234.44.239]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.primekey.com (Postfix) with ESMTPSA id 916B36AA008C for <spasm@ietf.org>; Wed, 8 May 2019 13:05:09 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=primekey.com; s=mail; t=1557313510; bh=TERkS9tkH1nY0LjDzDDcjg4ERgFvnow+grCXdTdMQ9o=; h=Subject:To:References:From:Date:In-Reply-To:From; b=asvsyzywyvL0EuQrCLEZQtMwrqPAwhXTgatIuVnFbhhc2a9SOYg1zJKtFphVRcae0 ZFjqO+AQ9oBZzl84MOg23iARSaK9SLEoU9O/m8oDHEskJ7osouau33/adwdRMhBG+/ C4LZrmacT0nJKqn4azMDmZemcjCSNOyXPYoNtu+0=
To: spasm@ietf.org
References: <153919524373.5861.7228296681722124369.idtracker@ietfa.amsl.com> <F16925E1-F8F1-4069-BF5A-91CBCF98C7C9@isara.com>
From: Tomas Gustavsson <tomas.gustavsson@primekey.com>
Openpgp: preference=signencrypt
Autocrypt: addr=tomas.gustavsson@primekey.com; prefer-encrypt=mutual; keydata= mQENBEyuwwYBCAD31Jsxn1lf7rnFc7y3Ol+TE7pU7ohO78kMdoVrZdAMnU9W0P33GedbU+kF 8/RFq7HlXV8a91RkgtdcMAK8tSdtBKDGZCOJZm5qOZ/EHikY8k/7s1wgSQSF4hYSG/IABCCA W139joDFl4L3buWyk2lsYX1HDBpuXGDL5HFyu165T0ZVlt23T04xmAwpIHUViKUWw1QYnlRz s66Desn2WeP+X8/QlqF1zOTUXbgrThB1X/Oh2+wzP08HVoTQCzlrEMeb9x2k+oa8PtVdnflh nZKBtyyBkZxRoHG3tNKcaf7JLoadSXcSKSKvfApcsxpP2JpkQgIhLi3JWik/Z+RR2WD1ABEB AAG0MFRvbWFzIEd1c3RhdnNzb24gPHRvbWFzLmd1c3RhdnNzb25AcHJpbWVrZXkuY29tPokB NwQTAQgAIQUCWX8yTAIbIwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBibcSbAEP+QGAU CAC82dn8XCQ8Ei7gxQAdRSc2imaP/388i/ObDMYhNhg5j4gXs3tkfxuCvhwkzskUFgOtmaEy uz/gIiVjQIsjQrHh5tl9M0q2tqbDHJpWfE6/SkXPUmTqQ0VGyq1MmZ3/zg2jSoll74qBSfdH V7sWugRXeCBxfaPeYo8DdPCGi27yrdL8zb3xkJ3BxPcDGNdkLm+Yza+qAOrssCD7MSLN+6Sd ML5Xcmw6pgRPlQ0aCsM7scrwgBNb7KrwxaqBxqwcuqF0NMgNjeiEHi2Oj3HOZdYU4Blk2GFq 9zHuCzTWumgNOlfksZ9K3ZMJBn6KLPot5bVXIKdnHwWRzoKMDxkSZjM5uQENBEyuwwYBCADZ 98eCFQ64zKo1OKkUgEJHO1JdsiqRO1znu6KyaTcd2vXfOCGkFFVBL+vjzzyyYV7Sg1/AaG4r l9TKJCwvx8mUmTJkKQspTfOj6AY33bmfMB/8LBYj2BjtxXyMucPjNTJqbL2r1HeGPV2nwyof MAyo2qcYuiLs20Ob7U8vooOV3GDDKEkXtJYZzTEU6qabGsepGIvMu770OZwvm4akQiCGe5sQ 4+/UH1pMZQNi+/fGbONFx+TUVMM8EkXD6dQ5WoL+xPabPjqiUmR7EBvg0uocr70Ag93tWk1d 4RgFcicjwMFcPg4TZ8Y/3Y7Nmbyo14+4SMNfNPFLgQMawL+cLLkdABEBAAGJAR8EGAECAAkC GwwFAlYXhXUACgkQYm3EmwBD/kA2igf/QNpPe7sLt3KdRD3x4cStxGjLCWyj7x1YLVnV4Nnu TvaNhC+KHx3uG39y1x3PJQwslpeSQ6JipOUmxeQjjGJGQZLV41L1PCJVhCL98Dinr6dJkYB7 cAVhfmW8PI51jiANExLZu8U5gnthj5CGv4428ODQgSoRI0demG3HmVCNrKdap+orhT8zRkq8 DuHTO01U7PKsfvQ2k8AqSAC/JjMOs1mpFe032IApXxlZkE+33Q3dE5BiJmICYg8hsRXvpKTm ZMCdNZJUQLq+XNpg6RtAPQIPMmCepXrE9M/KuH+jFS2G5+Hx5VBSM644E1G2i+HOPCVdHjof iaNi3V/ItEG3jw==
Message-ID: <9630953f-b7d3-3cc2-8fc6-e01738905bd3@primekey.com>
Date: Wed, 8 May 2019 13:05:11 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <F16925E1-F8F1-4069-BF5A-91CBCF98C7C9@isara.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/xBNWF8Ra3zH9gZeVciGteNhYs5Q>
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 11:05:19 -0000

Hi,

I support this initiative/re-charter.

Regards,
Tomas Gustavsson
PrimeKey Solutions AB

---
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>om>;
Gesendet: Mittwoch, 8. Mai 2019 02:18
An: Brockhaus, Hendrik (CT RDA ITS SEA-DE) <hendrik.brockhaus@siemens.com>om>;
Cc: spasm@ietf.org; Jim Schaad <ietf@augustcellars.com>om>;; Fries, Steffen
(CT RDA ITS) <steffen.fries@siemens.com>om>;
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>