Re: [lamps] Follow-up on lightweight CMP profile

Russ Housley <housley@vigilsec.com> Wed, 08 May 2019 00:18 UTC

Return-Path: <housley@vigilsec.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 ABAF9120254 for <spasm@ietfa.amsl.com>; Tue, 7 May 2019 17:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 bPzl5bx-pJhM for <spasm@ietfa.amsl.com>; Tue, 7 May 2019 17:18:07 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABA4312028B for <spasm@ietf.org>; Tue, 7 May 2019 17:18:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 4E3E2300AEC for <spasm@ietf.org>; Tue, 7 May 2019 19:58:49 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id lbof-nZtQi6z for <spasm@ietf.org>; Tue, 7 May 2019 19:58:47 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id E792A300474; Tue, 7 May 2019 19:58:46 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <E83F28FC-0328-44EB-B401-86EB32EB4751@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F4D423D9-0077-4992-82EB-424E36C9B10F"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Tue, 07 May 2019 20:18:03 -0400
In-Reply-To: <AM0PR10MB24025419EFD95ED54F7D79B5FE350@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM>
Cc: "spasm@ietf.org" <spasm@ietf.org>, Jim Schaad <ietf@augustcellars.com>, "steffen.fries@siemens.com" <steffen.fries@siemens.com>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
References: <AM0PR10MB24025419EFD95ED54F7D79B5FE350@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/V29w-_byKXmJ3rSgQ6bWFokVo_Q>
Subject: Re: [lamps] 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 00:18:17 -0000

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> 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://www.ietf.org/mailman/listinfo/spasm>