Thanks for presenting this work. I really like this and I think it'd be really useful for the use cases we have (IoT, M2M).
One comment: from a quick skimming of the draft, I'm not sure I understand what the stated expectations on the transport layer are? Since it's cTLS and not cDTLS I'd have thought it's the same as TLS (in-order & reliable) but then I got confused reading section 3.2 [1]: "The CTLS Record Layer assumes that records are externally framed (i.e., that the length is already known because it is carried in a UDP datagram or the like)" On Jabber Ben suggested that one could put CoAP between UDP and cTLS to get in-order & reliable delivery with a datagram transport, but then I'm not sure what the advantage would be since we'd be trading 2 bytes of TLSPlaintext.length with 4 bytes (minimum) of CoAP header? From the Jabber discussion, my current understanding is that there are 2 assumptions: a) the transport is in-order & reliable, and 2) there is one TLS record per transport layer packet. Is that the correct interpretation? If it is, is it not too restrictive a requirement? Cheers, thanks [1] https://tools.ietf.org/html/draft-rescorla-tls-ctls-02#section-3.2 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
