Re: [lamps] Draft IETF 118 Agenda for LAMPS

[Russ Housley <[e-mail]>]

I think it would be helpful to capture a bit of design rationale (maybe in an appendix).  At first scan, this seems similar to RFC 5697.  I think I understand the differences, but it would be better to write down the ones that drove you to write the document.

Russ

> On Oct 27, 2023, at 1:36 PM, John Gray <John.Gray=[e-mail]> wrote:
> 
> We would also like a slot for this draft as well:
>  
> https://www.ietf.org/id/draft-lamps-okubo-certdiscovery-00.html
>  
> Cheers,
>  
> John Gray
>  
>  
> From: Spasm <[e-mail] <mailto:[e-mail]>> On Behalf Of Mike Ounsworth
> Sent: Friday, October 27, 2023 1:06 PM
> To: Tim Hollebeek <tim.hollebeek=[e-mail] <mailto:tim.hollebeek=[e-mail]>>; David Hook <[e-mail] <mailto:[e-mail]>>
> Cc: SPASM <[e-mail] <mailto:[e-mail]>>
> Subject: [EXTERNAL] Re: [lamps] Draft IETF 118 Agenda for LAMPS
>  
> Hi Tim, Add to agenda please: draft-ounsworth-pq-composite-sigs (John) draft-ounsworth-lamps-cms-dhkem (Mike) – this is an ECDH-KEM sister to 5990 and a necessary dependency of draft-ietf-lamps-composite-kem. I can do a slide on it during 
> Hi Tim,
>  
> Add to agenda please:
>  
> draft-ounsworth-pq-composite-sigs (John)
> draft-ounsworth-lamps-cms-dhkem (Mike) – this is an ECDH-KEM sister to 5990 and a necessary dependency of draft-ietf-lamps-composite-kem. I can do a slide on it during the composite-kem presentation if you prefer that over a separate presentation, but it should probably be on the agenda regardless.
> draft-ounsworth-lamps-pq-external-pubkeys (Mike; or maybe I’ll throw @David Hook <mailto:[e-mail]> under the bus to present this one since it’s his customer that asked for this to be implemented in BouncyCastle)
>  
>  
> ---
> Mike Ounsworth
>  
> From: Spasm <[e-mail] <mailto:[e-mail]>> On Behalf Of Tim Hollebeek
> Sent: Friday, October 27, 2023 10:56 AM
> To: Brockhaus, Hendrik <hendrik.brockhaus=[e-mail] <mailto:hendrik.brockhaus=[e-mail]>>
> Cc: SPASM <[e-mail] <mailto:[e-mail]>>; Tschofenig, Hannes <[e-mail] <mailto:[e-mail]>>
> Subject: [EXTERNAL] Re: [lamps] Draft IETF 118 Agenda for LAMPS
>  
> Added to the agenda.  We might not get to it, but we’ll do our best.  There are a lot of items, but many of them are small and have pretty straightforward statuses.  We also allocated quite a bit of time to LAMPS to accommodate all the work that is going on (3 hours across 2 sessions).
>  
> -Tim
>  
> From: Brockhaus, Hendrik <hendrik.brockhaus=[e-mail] <mailto:hendrik.brockhaus=[e-mail]>> 
> Sent: Friday, October 27, 2023 3:47 AM
> To: Tim Hollebeek <[e-mail] <mailto:[e-mail]>>
> Cc: SPASM <[e-mail] <mailto:[e-mail]>>; Tschofenig, Hannes <[e-mail] <mailto:[e-mail]>>
> Subject: AW: Draft IETF 118 Agenda for LAMPS
>  
> Hello Tim
>  
> Hannes and I would like to present draft-tschofenig-lamps-nonce-cmp-est.
> Can you add this to the agenda or do we already have too many topics.
>  
> Hendrik
>  
> Von: Spasm <[e-mail] <mailto:[e-mail]>> Im Auftrag von Tim Hollebeek
> Gesendet: Donnerstag, 26. Oktober 2023 17:33
> An: SPASM <[e-mail] <mailto:[e-mail]>>
> Betreff: [lamps] Draft IETF 118 Agenda for LAMPS
>  
> LAMPS WG Agenda at IETF 118 -- Monday, 6 November 2023 at 17:30 local and Wednesday, 8 November 2023 at 14:30 local
>  
> 0)  Minute Taker, Jabber Scribe, Bluesheets
>  
> 1)  Agenda Bash
>  
> 2)  Recently Published RFCs
>     a)  draft-ietf-lamps-caa-issuemail published as RFC 9495
>  
> 3)  With the IESG or the RFC Editor
>     a)  draft-ietf-lamps-cmp-algorithms (Hendrik, Hans, Mike, John)
>     b)  draft-ietf-lamps-cmp-updates (Hendrik, David, John)
>     c)  draft-ietf-lamps-lightweight-cmp-profile (Hendrik, Steffen, David)
>     f)  draft-ietf-lamps-cms-kemri (Russ, John, Tomo)
>     g)  draft-ietf-lamps-nf-eku (Tirumal, Jani, Daniel)                        
>  
> 4)  Active PKIX-related Documents
>     a)  draft-ietf-lamps-rfc4210bis (Hendrik, David, Mike, John)
>     b)  draft-ietf-lamps-rfc6712bis (Hendrik, David, Mike, John)
>     c)  draft-ietf-lamps-pkcs12-pbmac1 (Hubert)
>     d)  draft-ietf-lamps-rfc7030-csrattrs (Michael)
>     e)  draft-ietf-lamps-key-attestation-ext (Carl, Sean)                       [replace or merge with draft-ietf-lamps-csr-attestation?]
>     f)  draft-ietf-lamps-dilithium-certificates (Jake, Panos, Sean, Bas)
>     g)  draft-ietf-lamps-kyber-certificates (Sean, Panos, Jake, Bas)
>     h)  draft-ietf-lamps-cert-binding-for-multi-auth (Alie, Rebecca, Mike)      [WGLC requested]
>     j)  draft-ietf-lamps-x509-policy-graph (David)
>     k)  draft-ietf-lamps-csr-attestation (Mike)
>     a)  draft-ietf-lamps-rfc5019bis (Corey)                    
>  
> 5)  Active S/MIME-related Documents
>     e)  draft-ietf-lamps-header-protection (DKG, Alexey, Bernie)                [in WG Last Call]
>     a)  draft-ietf-lamps-cms-kyber (Ludovic, Julien, Mike)
>     b)  draft-ietf-lamps-cms-sphincs-plus (Russ, Scott, Panos, Bas)
>     d)  draft-ietf-lamps-rfc5990bis (Russ)                                      [WGLC requested]
>     e)  draft-ietf-lamps-pq-composite-kem (Mike, John)
>     f)  draft-ietf-lamps-e2e-mail-guidance (DKG)                                [In WGLC, issues being resolved]
>     g)  draft-ietf-lamps-rfc8398bis/draft-ietf-lamps-rfc8399bis (Alexey, Wei, Corey)
>  
> 6)  Under consideration for adoption
>     b)  draft-mpalmer-key-compromise-attestation (Matt)
>     c)  CMC-bis: draft-mandel-lamps-rfc5272bis, draft-mandel-lamps-rfc5273bis, draft-mandel-lamps-rfc5274bis (Sean)
>     d)  draft-housley-lamps-cms-sha3-hash (Russ)                                [Adoption call requested]
>  
> 7)  Wrap up
> Any email and files/attachments transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.
> _______________________________________________
> Spasm mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/spasm