Subject: [rohc] SigComp ext - Shared Compression

From: "Lajos Zaccomer (ETH)" <[email-masked]>
Date: Wed, 10 Jul 2002 11:55:30 +0200

Hi,

I have some problem with interpreting the 4th step in the successful shared compression example in <draft-ietf-rohc-sigcomp-extended-04.txt> page 8. How will the compressor know about the "current decompressed message from Endpoint 1"? Handling that is the exclusive responsibility of the UDVM, isn't it? My idea is that the compressor will simply use the state belonging to the shared state id that it may learn from the state handler. Well, it should represent the last decompressed message. If my explanation is right, why do we need this overgeneralization; but if not, how should I interpret the compressor activity in such a case?

Thank you for all hints!

Best regards,

Zacco

_______________________________________________
Rohc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/rohc