Subject: RE: [rohc] question about SMS

From: "Surtees, Abigail" <[email-masked]>
Date: Fri, 11 Nov 2005 13:44:29 -0000

Hi Carrie, Rasheed,

Carrie is right that the compressor needs to save state items so that it
knows the identifier to reference at the decompressor.  An
implementation can set the decompressor SMS on a per compartment basis.
If it is using an SMS value other than the default, the decompressor
should advertise the SMS that it is using to the remote compressor.  The
remote compressor must keep track of the state items that are at the
decompressor, to ensure that it doesn't try to access state that is not
present at the decompressor.  Exactly how to do this is an
implementation decision, but the compressor must be able to know when
state will have been pushed out of the decompressor compartment and it
must know the correct state identifier to use (which means mirroring the
state that is stored at the decompressor which will not necessarily be
the message).

I hope this helps,

Best regards,

Abbie

> 
> Hi, experts,
> 
> The SMS is one of the SigComp parameters that are sent
> in the returned_parameters_location in SigComp message.
> And the SMS is per-compartment basis. In case of dynamic
> compression, compressor also needs to save state items,
> shall this SMS be used also for state items save in compressor,
> or it is only used for state items saved in decompressor?
> 
> <answer> In case of dynamic compression, the compressor only 
> needs to save
> the uncompressed message
> and use it in the compression of the subsequest messages to 
> that particular
> end point. The SMS should be used
> for state items saved at the decompressor only.
> 
> Regards,
> Carrie
> 
> _______________________________________________
> Rohc mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/rohc
> 
> 
> 
> ***********************  FSS-Unclassified   ***********************
> "DISCLAIMER: This message is proprietary to Hughes Software 
> Systems Limited
> (HSS) and is intended solely for the use of the individual to 
> whom it is
> addressed. It may contain  privileged or confidential information and
> should not be circulated or used for any purpose other than 
> for what it is
> intended. If you have received this message in error, please 
> notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, 
> copying, altering, or
> disclosing the contents of this message. HSS accepts no 
> responsibility for
> loss or damage arising from the use of the information 
> transmitted by this
> email including damage from virus."
> 
> 
> _______________________________________________
> Rohc mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/rohc
> 

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