This document is relevant to the TLS working because it reserves a large portion of the TLS content type space. The values 0-19 and 64-255 cannot be used without checking for conflicts with SRTP-DTLS's wacky demultiplexing scheme. In TLS 1.3 we will move more encrypted content types which should limit the impact this unfortunate design on TLS evolution, but the working group should be aware of this.
Cheers, Joe On Wed, Jan 27, 2016 at 1:39 AM, Magnus Westerlund < magnus.westerl...@ericsson.com> wrote: > AVTCORE and TLS, > > TLS WG, you are included in this WG last call, as this document affects > the TLS ContentType IANA registry. > > This email starts a two week WG last call, that ends on the 10th of > February. The intended status of this document is standards track (Proposed > Standard). > > The document can be retrieved here: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-rfc5764-mux-fixes/ > > Cheers > > Magnus Westerlund > > ---------------------------------------------------------------------- > Services, Media and Network features, Ericsson Research EAB/TXM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > Färögatan 6 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden | mailto: magnus.westerl...@ericsson.com > ---------------------------------------------------------------------- > > _______________________________________________ > 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
