RE: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)

> The minimum hash size of 9 bytes only applies to algorithms (and other
kinds of
> state information) that are downloaded to the UDVM and stored on the fly.
In
> the case of well-known algorithms that have been documented somewhere the
> state identifier for the algorithm can be any length and any value - after
all
> there's no point keeping an algorithm secret if it's in an Internet Draft!
>
> For example, the following list of 1-byte state identifiers might be
reserved:
>
> ID    Corresponding algorithm
>
> 0          UNCOMPRESSED
> 1          DEFLATE
> 2          LZO
> 3          LZJH
> 4          EPIC
> :            :
>
> The IETF doesn't need to define the above list - the task can be left to
3GPP,
> if they believe the effort to be worthwhile.

Richard,

this is not state referencing in the sense it is being used in the UDVM
draft.
(It's not a hash, either.)
I'm not quite sure I understand your mechanism, but it seems to be the
worst-of-worlds between the existing state identifier mechanism and a
registration-based mechanism, in the sense that it inherits all problems of
both and then some more.

I'm strongly opposed to adding new mechanisms of this kind at this stage.
(I also have a lot of problems with the approach, which I already have
detailed on this list, but this does not matter at this point.)

Gruesse, Carsten

PS.: As with all messages on Sigcomp this week, the above was written with
my WG member hat on; as I'm getting involved in the details, I'll have to
leave the WG hat to Lars-Erik on this.

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