Re: [lamps] DRAFT LAMPS Agenda for IETF 114

Russ Housley <housley@vigilsec.com> Mon, 18 July 2022 14:54 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 BE93DC15A730 for <spasm@ietfa.amsl.com>; Mon, 18 Jul 2022 07:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ouOL96FuC4Ne for <spasm@ietfa.amsl.com>; Mon, 18 Jul 2022 07:53:58 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB893C14CF0F for <spasm@ietf.org>; Mon, 18 Jul 2022 07:53:46 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 150C416BF26; Mon, 18 Jul 2022 10:53:44 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 021AB16C03B; Mon, 18 Jul 2022 10:53:43 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <AB126236-D280-4922-A711-CE4C2948C6B3@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A5C81E0B-CFFC-495C-8768-98B39ACD3055"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Mon, 18 Jul 2022 10:53:43 -0400
In-Reply-To: <CADqLbzJjBpPF+6bZ2E2r_eXKFmzCcd5i8H_ZV7O0Dg9Kg+i1xw@mail.gmail.com>
Cc: LAMPS <spasm@ietf.org>
To: Dmitry Belyavsky <beldmit@gmail.com>, Hubert Kario <hkario@redhat.com>
References: <4026D3B2-9390-484F-8A10-43E135441998@vigilsec.com> <CADqLbzJjBpPF+6bZ2E2r_eXKFmzCcd5i8H_ZV7O0Dg9Kg+i1xw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/WFhFWSOV0lggOQe1HTxApQCO9U0>
Subject: Re: [lamps] DRAFT LAMPS Agenda for IETF 114
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
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, 18 Jul 2022 14:54:01 -0000

Dmitry and Hubert:

I can add you to the end, but I really think that we are going to have a hard time getting through the existing agenda items.  If we do not make it to the end, then we will schedule a virtual interim session in September.

Russ


> On Jul 18, 2022, at 10:35 AM, Dmitry Belyavsky <beldmit@gmail.com> wrote:
> 
> Dear Russ,
> 
> Could you please give a timeslot for presenting the https://datatracker.ietf.org/doc/draft-kario-pkcs12-pbmac1/ <https://datatracker.ietf.org/doc/draft-kario-pkcs12-pbmac1/> ?
> Unfortunately, it was missed in the draft agenda.
> 
> Many thanks in advance!
> 
> 
> On Fri, Jul 8, 2022 at 8:37 PM Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>> wrote:
> Please review and comment.
> 
> Our expectation is that none of the document in in group 2 will need more than two minutes to provide status since the changes have already been described on the mail list.
> 
> Our goal is to push the documents in groups 3 and 4 to closure; it is clear that the PQC-related documents are going to start consuming a lot of time now that NIST has announce the first set of algorithms.
> 
> For the LAMPS WG Chairs,
>   Russ
> 
> - - - - - - - 
> 
> LAMPS WG Agenda at IETF 114 -- 27 July 2022 at 10:00 EDT
> 
> 0)  Minute Taker, Jabber Scribe, Bluesheets
> 
> 1)  Agenda Bash
> 
> 2)  With the IESG or the RFC Editor
>     a)  draft-ietf-lamps-documentsigning-eku (Tadahiko, Tomofumi, Sean)
>     b)  draft-mtis-lamps-8410-ku-clarifications (Sean, Simon, Daniel, Tadahiko)
>     c)  draft-ietf-lamps-cmp-algorithms (Hendrik, Hans, Mike, John)
>     d)  draft-ietf-lamps-cmp-updates (Hendrik, David)
>     e)  draft-ietf-lamps-lightweight-cmp-profile (Hendrik, Steffen, David)
> 
> 3)  Active PKIX-related Documents
>     a)  draft-ietf-lamps-rfc3709bis (Stefan, Russ, Trevor, Leonard)
> 
> 4)  Active S/MIME-related Documents
>     a)  draft-ietf-lamps-header-protection (DKG, Alexey, Bernie)
>     b)  draft-ietf-lamps-e2e-mail-guidance (DKG)
> 
> 5)  Under consideration for adoption
>     a)  draft-richardson-lamps-rfc7030-csrattrs (Michael)
>     b)  draft-housley-lamps-3g-nftypes (Russ, Sean, John, Daniel)
>     c)  draft-wallace-lamps-key-attestation-ext (Carl, Sean)
>     d)  draft-turner-lamps-nist-pqc-kem-certificates (Sean, Panos, Jake, Bas)
>     e)  draft-perret-prat-lamps-cms-pq-kem (Ludovic, Julien, Mike)
>     f)  draft-ounsworth-pq-composite-keys (Mike, Max, Jan)
>     g)  draft-ounsworth-pq-composite-sigs (Mike, Max)
>     h)  draft-becker-guthrie-cert-binding-for-multi-auth (Alie, Rebecca, Mike)
>     i)  draft-uni-qsckeys (Christine, Silvio, Basil, Tamas, Michael, Dieter, Joppe)
> 
> 6)  Wrap up
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org <mailto:Spasm@ietf.org>
> https://www.ietf.org/mailman/listinfo/spasm <https://www.ietf.org/mailman/listinfo/spasm>
> 
> 
> -- 
> SY, Dmitry Belyavsky
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm