RE: [rohc] TCP compression profile

["Lars-Erik Jonsson (EAB)" <Lars-Erik.Jonsson@epl.ericsson.se>]

> > > The main piece currently missing from the drafts is a description
> > > of how to encode each field in the TCP/IP header, so we've added a
> > > very simple proposal for this based on the current behavior draft.
> > 
> > How to encode the original fields are rather well "suggested" in the
> > behavior draft
> 
> This certainly seems to be the case based on our initial test 
> TCP flows. One interesting open issue, however, is the level of
> complexity needed in the final TCP encoding.  Our current
> implementation only uses a very basic set of packet formats,
> designed specifically to be human-readable.

Are these documented anywhere?


> If we choose the former approach then the notation defines
> which encoding methods are applied to which fields (including
> the "control" fields not present in the original TCP/IP header).
> To get  from this to "bits on the wire", we just need to
> define a library of 4 or 5 basic encoding methods for the
> notation to use.

I do not follow this. Can you maybe clarify better how this
would be done? In principle? How do you capture all functional
design decisions? Interaction with the context, feedback handling,
trade-offs between optimizing for the most common cases, the
average header size, etc?


BR
/L-E
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc