Re: [TLS] WG last call of draft-ietf-avtcore-rfc5764-mux-fixes-05

2016-02-07 Thread Dave Garrett
Permanently gobbling up the majority of the codespace feels like excessive force here. For TLS 1.3, the first byte will always be one of alert(21), handshake(22), or application_data(23), even for custom types. The stated type for TLSCiphertext has been frozen to application_data(23) with the

Re: [TLS] WG last call of draft-ietf-avtcore-rfc5764-mux-fixes-05

2016-02-07 Thread Joseph Salowey
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