I misdirected you with the name it should be draft-ietf-tls-tls13-pkcs1, can you please submit under this name? It would be better to have in the tlswg repo, we'll follow up offline.
Thanks, Joe On Wed, Nov 29, 2023 at 9:41 AM David Benjamin <david...@chromium.org> wrote: > Done, although I'm not sure if I got all the metadata right. (How does one > mark it as replacing the old one?) > https://datatracker.ietf.org/doc/draft-tls-tls13-pkcs1/ > > The GitHub is still under my account, but happy to move it to the TLSWG if > preferred. (How would we go about doing that?) > > On Wed, Nov 29, 2023 at 11:07 AM Joseph Salowey <j...@salowey.net> wrote: > >> The adoption call for this draft has completed. There is sufficient >> interest in the draft and no objections. Authors, please submit this draft >> with the file name draft-tls-tls13-pkcs1-00.txt. >> >> Cheers, >> Joe >> >> On Mon, Nov 6, 2023 at 9:25 AM Joseph Salowey <j...@salowey.net> wrote: >> >>> At the TLS meeting at IETF 118 there was significant support for the >>> draft Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3 >>> <https://datatracker.ietf.org/doc/draft-davidben-tls13-pkcs1/01/> ( >>> https://datatracker.ietf.org/doc/draft-davidben-tls13-pkcs1/01/) This >>> call is to confirm this on the list. Please indicate if you support the >>> adoption of this draft and are willing to review and contribute text. If >>> you do not support adoption of this draft please indicate why. This call >>> will close on November 27, 2023. >>> >>> Thanks, >>> >>> Sean, Chris and Joe >>> >> _______________________________________________ >> TLS mailing list >> TLS@ietf.org >> https://www.ietf.org/mailman/listinfo/tls >> >
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
