Open brianraymor opened 8 years ago
https://trac.tools.ietf.org/wg/core/trac/ticket/400#comment:2
This would be covered by the Max-Message-Size option in draft-bormann-core-sig-01
https://trac.tools.ietf.org/wg/core/trac/ticket/400#comment:3
The text should clearly explain that people will create two incompatible CoAP worlds when they get comfortable with large message sizes for CoAP-over-TCP, just because they can.
A requirement should be that there can exist a simply proxy that translates between CoAP-over-TCP/TLS and CoAP-over-UDP/DTLS without any interoperability issues between constrained CoAP nodes and the powerful CoAP-over-TCP nodes.
Captured from Ticket 400:
Section 4.1 discusses the effect of having CoAP over TCP/TLS on potential message sizes. But we are not really giving guidance here on whether we want to use this potential capability.
If we want to open this up, we probably also need to include message sizes in the settings/capabilities mechanism