[TLS]Re: Working Group Last Call for Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
WGLC closes out today. spt > On Jun 3, 2024, at 11:43, Sean Turner wrote: > > Hi! WGLC ends on Wednesday. I know this I-D is not all that exciting and > most of the “discussion" was about whether to adopt the I-D at all, but it > would be great if we had a couple of more people chime in. If you remember, > when we used the show of hands tool to help determine whether there was > consensus to adopt this draft there were 36 who wanted it adopted. > > spt > >> On May 28, 2024, at 09:44, Sean Turner wrote: >> >> Just a reminder that this WGLC is still ongoing. >> >> spt >> >>> On May 22, 2024, at 10:14, Sean Turner wrote: >>> >>> This email starts the working group last call for "Legacy RSASSA-PKCS1-v1_5 >>> codepoints for TLS 1.3” I-D, located here: >>> >>> https://datatracker.ietf.org/doc/draft-ietf-tls-tls13-pkcs1/ >>> >>> The WG Last Call will end 5 June 2024 @ 2359 UTC. >>> >>> Please review the I-D and submit issues and pull requests via the GitHub >>> repository that can be found at: >>> >>> https://github.com/tlswg/tls13-pkcs1 >>> >>> Alternatively, you can also send your comments to tls@ietf.org. >>> >>> Thanks, >>> spt >> > ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
[TLS]Re: Working Group Last Call for Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
Hi! WGLC ends on Wednesday. I know this I-D is not all that exciting and most of the “discussion" was about whether to adopt the I-D at all, but it would be great if we had a couple of more people chime in. If you remember, when we used the show of hands tool to help determine whether there was consensus to adopt this draft there were 36 who wanted it adopted. spt > On May 28, 2024, at 09:44, Sean Turner wrote: > > Just a reminder that this WGLC is still ongoing. > > spt > >> On May 22, 2024, at 10:14, Sean Turner wrote: >> >> This email starts the working group last call for "Legacy RSASSA-PKCS1-v1_5 >> codepoints for TLS 1.3” I-D, located here: >> >> https://datatracker.ietf.org/doc/draft-ietf-tls-tls13-pkcs1/ >> >> The WG Last Call will end 5 June 2024 @ 2359 UTC. >> >> Please review the I-D and submit issues and pull requests via the GitHub >> repository that can be found at: >> >> https://github.com/tlswg/tls13-pkcs1 >> >> Alternatively, you can also send your comments to tls@ietf.org. >> >> Thanks, >> spt > ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
[TLS]Re: Working Group Last Call for Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
Just a reminder that this WGLC is still ongoing. spt > On May 22, 2024, at 10:14, Sean Turner wrote: > > This email starts the working group last call for "Legacy RSASSA-PKCS1-v1_5 > codepoints for TLS 1.3” I-D, located here: > > https://datatracker.ietf.org/doc/draft-ietf-tls-tls13-pkcs1/ > > The WG Last Call will end 5 June 2024 @ 2359 UTC. > > Please review the I-D and submit issues and pull requests via the GitHub > repository that can be found at: > > https://github.com/tlswg/tls13-pkcs1 > > Alternatively, you can also send your comments to tls@ietf.org. > > Thanks, > spt ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
[TLS]Re: Working Group Last Call for Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
+1 what Rich said. Not a deal-breaker for me either way, but I would prefer "N", initially. Cheers, Andrei -Original Message- From: Salz, Rich Sent: Wednesday, May 22, 2024 7:26 AM To: Sean Turner ; TLS List Subject: [EXTERNAL] [TLS]Re: Working Group Last Call for Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3 > This email starts the working group last call for "Legacy RSASSA-PKCS1-v1_5 > codepoints for TLS 1.3” I-D, located here: No comments, ship it. > The only comment/question I have about this I-D (and I hope this is not too > much of a bikeshed) is whether the Recommended column should be “D” instead > of “N”. I think that would be a mistake as it makes the vast deployment of existing TPM machines nonconformant. In a few years, maybe. For now, not-recommended is strong enough. ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
[TLS]Re: Working Group Last Call for Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
> On May 22, 2024, at 10:28, David Benjamin wrote: > > On Wed, May 22, 2024 at 10:27 AM Salz, Rich > wrote: > > This email starts the working group last call for "Legacy RSASSA-PKCS1-v1_5 > > codepoints for TLS 1.3” I-D, located here: > > No comments, ship it. > > > The only comment/question I have about this I-D (and I hope this is not too > > much of a bikeshed) is whether the Recommended column should be “D” instead > > of “N”. > > I think that would be a mistake as it makes the vast deployment of existing > TPM machines nonconformant. In a few years, maybe. For now, not-recommended > is strong enough. > > (I don't have strong feelings on this and am happy to defer this to what > everyone else wants. Just briefly noting that "N" in the document isn't an > explicit preference here. "D" just didn't exist at the time the document was > written.) I figured this was the case. Part of the reason for raising this point now is to tell the IESG that we actually thought about it when somebody asks about whether we considered “D”. spt ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
[TLS]Re: Working Group Last Call for Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
On Wed, May 22, 2024 at 10:27 AM Salz, Rich wrote: > > This email starts the working group last call for "Legacy > RSASSA-PKCS1-v1_5 codepoints for TLS 1.3” I-D, located here: > > No comments, ship it. > > > The only comment/question I have about this I-D (and I hope this is not > too much of a bikeshed) is whether the Recommended column should be “D” > instead of “N”. > > I think that would be a mistake as it makes the vast deployment of > existing TPM machines nonconformant. In a few years, maybe. For now, > not-recommended is strong enough. > (I don't have strong feelings on this and am happy to defer this to what everyone else wants. Just briefly noting that "N" in the document isn't an explicit preference here. "D" just didn't exist at the time the document was written.) David ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
[TLS]Re: Working Group Last Call for Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
> This email starts the working group last call for "Legacy RSASSA-PKCS1-v1_5 > codepoints for TLS 1.3” I-D, located here: No comments, ship it. > The only comment/question I have about this I-D (and I hope this is not too > much of a bikeshed) is whether the Recommended column should be “D” instead > of “N”. I think that would be a mistake as it makes the vast deployment of existing TPM machines nonconformant. In a few years, maybe. For now, not-recommended is strong enough. ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
[TLS]Re: Working Group Last Call for Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
> On May 22, 2024, at 10:14, Sean Turner wrote: > > This email starts the working group last call for "Legacy RSASSA-PKCS1-v1_5 > codepoints for TLS 1.3” I-D, located here: > > https://datatracker.ietf.org/doc/draft-ietf-tls-tls13-pkcs1/ > > The WG Last Call will end 5 June 2024 @ 2359 UTC. > > Please review the I-D and submit issues and pull requests via the GitHub > repository that can be found at: > > https://github.com/tlswg/tls13-pkcs1 > > Alternatively, you can also send your comments to tls@ietf.org. The only comment/question I have about this I-D (and I hope this is not too much of a bikeshed) is whether the Recommended column should be “D” instead of “N”. spt ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
