Changes are now in draft-06: URL: https://www.ietf.org/archive/id/draft-ietf-tls-tls13-pkcs1-06.txt Status: https://datatracker.ietf.org/doc/draft-ietf-tls-tls13-pkcs1/ HTML: https://www.ietf.org/archive/id/draft-ietf-tls-tls13-pkcs1-06.html HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-tls-tls13-pkcs1 Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-tls-tls13-pkcs1-06
On Mon, Oct 6, 2025 at 1:41 PM David Benjamin <[email protected]> wrote: > Whoops, thanks! I must have forgotten to put in a placeholder when > starting this and then it carried through. Trawled through my inbox... > I think I got everyone? > > https://github.com/tlswg/tls13-pkcs1/commit/b6ad09112e1132edc289ca020403610e007b42ee > > https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-tls-tls13-pkcs1&url_2=https://tlswg.github.io/tls13-pkcs1/draft-ietf-tls-tls13-pkcs1.txt > > (Happy to cut a new draft whenever's appropriate. By default I'll > snooze this a week or so, in case there are other last call comments > incoming.) > > > > On Sun, Oct 5, 2025 at 6:33 PM Rifaat Shekh-Yusef via Datatracker > <[email protected]> wrote: > > > > Document: draft-ietf-tls-tls13-pkcs1 > > Title: Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3 > > Reviewer: Rifaat Shekh-Yusef > > Review result: Has Nits > > > > I have reviewed this document as part of the security directorate's > > ongoing effort to review all IETF documents being processed by the > > IESG. These comments were written primarily for the benefit of the > > security area directors. Document editors and WG chairs should treat > > these comments just like any other last call comments. > > > > The summary of the review is Ready (with one nit) > > > > > > A well written document with clear security consideration section. > > > > The only comment I have is that I did not see an acknowledgment section. > > Few people provided feedback on the mailing list, and I think these > people should be acknowledged. > > > > > > > > > > >
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
