Re: [core] draft-bormann-core-coap-tcp

[Andrew Mcgregor <[e-mail]>]

I would very much like to support the use of minion in coap-over-tcp, that
will give a very simple deployment path in a very wide variety of
situations.


On 1 August 2013 00:52, Carsten Bormann <[e-mail]> wrote:

> > I read your coap-tcp draft but I missed any text on TCP header size
> reduction.
>
>
> (If you mean as in RFC 6846 header compression, this should be orthogonal.)
>
> A reduced CoAP header is defined in the coap-over-websockets draft and I
> didn't see a need to invent another one, even though I'm not sure I like
> the version used in coap-over-websockets.
>
> Clearly, we would like to have a common way of compactifying the CoAP
> header for the reliable, connection-oriented transports, if we don't decide
> to stick with the 4-byte header (which is a bit awkward as it's not clear
> what to put into the message-ID field).
>
> This very moment I'm listening to the MINION talk by Janardhan Iyengar.
> I reference MINION as one possible approach for framing in the
> coap-over-tcp draft.
>
> Grüße, Carsten
>
> _______________________________________________
> core mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/core
>



-- 
Andrew McGregor | SRE | [e-mail] | [phone]