[lamps] Support for working on the lightweight CMP profile

Russ Housley <housley@vigilsec.com> Mon, 27 May 2019 16:48 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 6C255120169 for <spasm@ietfa.amsl.com>; Mon, 27 May 2019 09:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.092
X-Spam-Level:
X-Spam-Status: No, score=0.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 RWH3iMmEyjuf for <spasm@ietfa.amsl.com>; Mon, 27 May 2019 09:48:33 -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 BD1D712015A for <spasm@ietf.org>; Mon, 27 May 2019 09:48:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id AFFA2300AA2 for <spasm@ietf.org>; Mon, 27 May 2019 12:29:15 -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 6gib_e00Av6W for <spasm@ietf.org>; Mon, 27 May 2019 12:29:13 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 387A930066E; Mon, 27 May 2019 12:29:13 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <29FAEBF1-2D67-469F-BE78-AF58F78D055E@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3DEE9E57-EF12-469E-B83A-8B43C79C4B0E"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 27 May 2019 12:48:30 -0400
In-Reply-To: <AM0PR10MB2402C7C1AAA09EABF047F0CEFE1D0@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM>
Cc: Tim Hollebeek <tim.hollebeek@digicert.com>
To: "spasm@ietf.org" <spasm@ietf.org>
References: <AM0PR10MB24028210BCE560C64195A74EFE320@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM> <AM0PR10MB2402B5BB06E4FB59A8ECB16BFE060@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM> <AM0PR10MB2402C7C1AAA09EABF047F0CEFE1D0@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/GX_ZgdfJy0sifZXKryQzbikF2HY>
Subject: [lamps] Support for working on the 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: Mon, 27 May 2019 16:48:37 -0000

Hendrik:

I see people speaking on both sides.  So, I am asking a few questions to see if there is enough support...

1) If this work is added to the charter, will you contribute to the document?

2) If this work is added to the charter, will you review to the document?

3) If this document is published as an RFC, will you implement it?

Russ


> On May 27, 2019, at 9:03 AM, Brockhaus, Hendrik <hendrik.brockhaus@siemens.com> wrote:
> 
> Hi Russ
>  
> Did you have the time to look into my mail below?
> I would like to push this topic further forward.
>  
> Hendrik
>  
> Von: Brockhaus, Hendrik (CT RDA ITS SEA-DE) 
> Gesendet: Montag, 20. Mai 2019 15:43
> An: Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>>
> Cc: Fries, Steffen (CT RDA ITS) <steffen.fries@siemens.com <mailto:steffen.fries@siemens.com>>; spasm@ietf.org <mailto:spasm@ietf.org>
> Betreff: AW: Proposed Re-Chartering Text for CMP updates and lightweight profile (RE: Follow-up on lightweight CMP profile)
>  
> Hi Russ
>  
> We discussed my proposal on the mailing list. I feel there is quite some support.
> Tomas, Max and Martin supported the activity. There were some questions and concerns from Panos, that I hopefully could clarify.
>  
> What is the next step?
>  
> Hendrik
>  
> Von: Spasm <spasm-bounces@ietf.org <mailto:spasm-bounces@ietf.org>> Im Auftrag von [ext] Brockhaus, Hendrik
> Gesendet: Mittwoch, 8. Mai 2019 11:10
> An: spasm@ietf.org <mailto:spasm@ietf.org>; Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>>
> Cc: Jim Schaad <ietf@augustcellars.com <mailto:ietf@augustcellars.com>>; Fries, Steffen (CT RDA ITS) <steffen.fries@siemens.com <mailto:steffen.fries@siemens.com>>
> Betreff: [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%7C743e39b041d4476e826a08d6d3950ad8%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C636929034414755277&sdata=PxGWfXa6%2FzuG2Pi844eXybqzfxwjQf0FAsc2YtDEYiM%3D&reserved=0>
>  
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org <mailto:Spasm@ietf.org>
> https://www.ietf.org/mailman/listinfo/spasm <https://www.ietf.org/mailman/listinfo/spasm>