[rohc] TCP/IP EPIC profile

[Julije Ozegovic <[e-mail]>]

Dear ROHCers,

here we include "expanded" TCP/IP profile as published in

TCP/IP Header Compression for ROHC (ROHC-TCP)
<draft-ietf-rohc-tcp-00.txt>

The purpose of this posting is to point out the complexity of 
whole thing, regarding the fact that almost every line of 
profile ends up with (at least) one data structure in end user 
application.

The questions are:
    do we really want this?
    do we really need this?
    is it worth the effort?
    is it applicable to target machine (GSM)?
    do we really need (48+2)*60=3000 formats?

Besides this, comments about inconsistencies of the profile are 
listed inline.

We also want to raise discussion about usage of FORMAT method.

The questions are:

    - what about difference in FORMAT structure
      between CO and IR/DYN packets,
      shouldn't they be the same (by EPIC draft)?

    - what about usage of IRREGULAR method in all sets
      (except last one where it should be used),
      this way first set will always be selected

    - what about syntax and usage of FORMAT SELECTOR,
      it is actually not needed (can be identified from
      ID-bits of IR/DYN packet)

Best regards,
Julije Ozegovic