RE: [rohc] TCP/IP EPIC profile

Hi all, 

> > [Mark]
> > Ok, see my discussion above for one way to support such a flag.
> >
> > Also, consider the following fragment of EPIC-speak...
> >
> > A_and_B = AB_1(50%) | AB_2(50%)
> >
> > AB_1 = XXXX
> >         YYYY
> >
> > AB_2 = PPPP
> >         QQQQ
> >
> > which says that if A is encoded as XXXX then B is encoded as
> > YYYY (and
> > this happens 50% of the time), but if A is encoded as PPPP then B is
> > encoded as QQQQ (and this happens 50% of the time).
> >
> [Hongbin]
> Great idea! Such a simple format is really what we need! However, you
need
> 'otherwise' to simply the enumeration of all possible, however,
ignorable
> (from the point of overall performance) combinations of encodings of
these
> fields (there may exist {A:XXXX B:QQQQ} or {A:PPPP B:YYYY}).
> 

Yes, the extension for supporting correlation can really enhance the
expression ability of EPIC-LITE. For ROHC-TCP case, we can combine
bulk-data-co, bulk-ack-co, interactive-co to a more intuitionistic
representation.

Since this group wants to use EPIC-LITE as a "generic compressed format
generator" for use in ROHC profile standardization, it would be better
that EPIC-LITE can provide more convenience and intuitionistic way for
developers to write the profile.

BR,
Qian

_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc