[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[rohc] RE: State acknowledgement.

 
Hi Ranjith,
 
It's up to you to construct the feedback string.  It can be whatever you want -- the example in RFC 3321 is, if I remember correctly, using the state hash, but it doesn't have to be that.
 
In your example, compressor A would know the SMS at B (it has to know this for the secure reference principle to work) and so knows which states will be created (and which will be deleted).  A can work this out from the state-creation rules.
 
Cheers,
 
Mark.
 
PS -- your disclaimer states that this is proprietary information, which doesn't really fit with this being a public mailing list...
 
 
-----Original Message-----
From: Ranjith.V at aricent.com [mailto:Ranjith.V at aricent.com]
Sent: 27 July 2007 07:47
To: West, Mark
Cc: rohc at ietf.org
Subject: State acknowledgement.



Hi West,

If a Compressor A requests Decompressor B to create a  Bytecode state, Dynamic state and a  USD state then how decompressor B acknowledges of these states to A.

I know about  feedback mechanisam . My doubt is about  what will be the feedback string...?

Suppose decompressor B have enoughs SMS to create Bytecode state, Dynamic state and it is not for USD state then how it informs about saved states and unsaved states to compressor A...?



Thanks and Regards
Ranjith Reddy. V
Extn: 9134
Location : F4-122

***********************  Aricent- Confidential   *********************** 
"DISCLAIMER: This message is proprietary to Aricent 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. Aricent 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
Rohc at ietf.org
https://www1.ietf.org/mailman/listinfo/rohc