Issue188

Issue Title Changes in Query handling policy
Document: GIST Protocol Specification v11 Section: 6.3
Category: Technical Priority: Should Fix
Status: Text Proposed

Created on 2007-02-21.14:51:39 by reh, last changed 2007-02-22.16:22:49.

Messages
msg526 Author: reh Date: 2007-02-22.16:22:41
Updated in version 12.

For simplicity, on the policy handling point, the state machines have been kept
roughly as they are; however, the following text added in 6.3:

"In principle, an implementation MAY change its policy on handling a Query
message at any time; however, the state machine descriptions here cover only the
case where the policy is fixed while waiting for a Confirm message."
msg514 Author: reh Date: 2007-02-21.14:51:39
From Adrian Farrel:

Can I change my mind about whether I want a Confirm 
while I am waiting for one? 
For example, in Awaiting Confirm state I may receive a 
new Query. Must I also set the R flag on the Response 
or can I clear the flag and move to Established state? 
 
Similarly, during the refresh processing (since the MA 
is now set up and I no longer need to see the Confirm) 
can I clear the R flag on refresh Responses? I think the 
state machine allows this. But once I am in Awaiting 
Refresh state, can I change my mind and send R=0 on my next Response?
History
Date User Action Args
2007-02-22 16:22:49rehsetstatus: No Discussion -> Text Proposed
2007-02-22 16:22:41rehsetmessages: + msg526
2007-02-21 14:51:39rehcreate