> On 24 Feb 2017, at 7:38, Joseph Salowey <j...@salowey.net> wrote: > > The difference between what is defined in 1.3 and this document is the 256 > bit CCM cipher suites. The document does not specify cipher suites for TLS > 1.3. > > Is it important for TLS 1.3 to have support for these cipher suites? > > If it is then we either need to add the cipher suites to this document or to > TLS 1.3. At this point I would like to minimize the changes to 1.3, so I'm > advocating that if the AES-256-CCM ciphers are necessary we update the > current document instead of TLS 1.3.
I’d like to push back on that. It’s literally adding one or two lines (do we need a 256-bit version with an 8-byte tag?) to a table in Appendix A.4. The alternative is to make this document apply to 1.3. Assuming 256-bit AES-CCM suites are needed, I think the better place to put them is in the TLS 1.3 document. Yoav
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
