On Monday 16 November 2015 15:16:50 Eric Rescorla wrote: > PR: https://github.com/tlswg/tls13-spec/pull/345 > > Per discussion in Yokohama, I have rewritten the IANA considerations > section so that the 16-bit code spaces are "Specification Required" > and they have a "Recommended" column. > > 1. The Cipher Suites "Recommended" column was populated based on > the Standards Track RFCs listed in the document (and I removed the > others).
> > 2. The Extensions "Recommended"column was populated by taking all > the Standards Track RFCs and marking them "Yes" and marking > others "No". I recognize that this probably marks a bunch of > extensions which we actually don't love as "Yes" (and perhaps others > as "No") and if people want to move some from one column to another, > that seems like a great mailing list discussion which I will let the > chairs drive. why max_fragment_length [RFC6066] is not to be supported in TLSv1.3? https://tools.ietf.org/html/draft-ietf-dice-profile-17#section-15 states that this is a MUST for IoT TLS profile -- Regards, Hubert Kario Senior Quality Engineer, QE BaseOS Security team Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
