> On Apr 11, 2023, at 12:50, Salz, Rich <rs...@akamai.com> wrote: > > I am commenting on 8447bis. This document is just about ready to move > forward, but two fixes are needed. > > Why there are Notes still in the doc (e.g., near end of section 6 it says > about weaker elliptic curves) and think those should be resolved, one way or > another, before advancing out of the WG.
There were still notes in s5 and s6 to draw attention to cipher suite listing in light of I-D.ietf-tls-deprecate-obsolete-kex and I guess now John’s I-D too. Joe and I will circle with those authors to make sure we have the appropriate coverage. > Sec 7 adds a note that says the experts "will highly encourage registrants to > provide a link" while Sec 13 says experts "ensure the specification is > publicly available." So is that SHOULD or MUST? (And s/highly/strongly/ IMO) I can get behind s/highly/strongly: https://github.com/tlswg/rfc8447bis/pull/39 This tweak was introduced as a result of discussions in Philly (IETF115) to address David Schinazi’s comment at the mic. If I remember correctly, the discussion was that there’s not really a concern about exhausting the registry space because it’s a “string" registry, but we still wanted the DEs to make sure the structure is followed, i.e., "EXPORTER:” is included. So … in some respects I think of it as a SHOULD, but then that does clash with s13. I guess the question is as DE, is the guidance going to lead to problems? > A nit, this line appears multiple times: > Setting a "Recommended" column value to Y or D requires Standards > There should probably be quotes around the letters Y and D, for consistency > with other text. I hope I got ‘em all here: https://github.com/tlswg/rfc8447bis/pull/38 Cheers, > A post IETF 116 bump to make sure folks get their reviews in. If you look at > the diffs from RFC 8446 you can see not that much has changed. We will also > take “I read it and it looks good” response. > > > Cheers, > spt > > >> On Mar 28, 2023, at 21:00, Christopher Wood <c...@heapingbits.net >> <mailto:c...@heapingbits.net>> wrote: >> >> As mentioned during yesterday's meeting, this email starts the working group >> last call for "The Transport Layer Security (TLS) Protocol Version 1.3" and >> "IANA Registry Updates for TLS and DTLS” I-Ds, located here: >> >> - >> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-tls-rfc8446bis__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrgSyiMh7$ >> >> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-tls-rfc8446bis__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrgSyiMh7$> >> >> - >> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-tls-rfc8447bis__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrjrMdAm2$ >> >> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-tls-rfc8447bis__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrjrMdAm2$> >> >> >> The WG Last Call will end on April 18, 2023. >> >> Please review the documents and submit issues or pull requests via the >> GitHub repositories, which can be found at: >> >> - >> https://urldefense.com/v3/__https://github.com/tlswg/tls13-spec__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrj6Gs5p8$ >> >> <https://urldefense.com/v3/__https://github.com/tlswg/tls13-spec__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrj6Gs5p8$> >> >> - >> https://urldefense.com/v3/__https://github.com/tlswg/rfc8447bis__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrpamqVl6$ >> >> <https://urldefense.com/v3/__https://github.com/tlswg/rfc8447bis__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrpamqVl6$> >> >> >> Alternatively, you can also send your comments to tls@ietf.org >> <mailto:tls@ietf.org>. >> >> Thanks, >> Chris >> _______________________________________________ >> TLS mailing list >> TLS@ietf.org <mailto:TLS@ietf.org> >> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/tls__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrjkidxUX$ >> >> <https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/tls__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrjkidxUX$> >> > > > _______________________________________________ > TLS mailing list > TLS@ietf.org <mailto:TLS@ietf.org> > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/tls__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrjkidxUX$ > > <https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/tls__;!!GjvTz_vk!Ulz2iHrqiHDTnXaSY0-d3Vo3dX-wtwR6OtahB_aLeEKhAfPj4rRfFY4jViJ3R9YUrjkidxUX$> > > > > _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
