Issue98

Issue Title Negotiating MA_HOLD_TIME
Document: GIMPS Protocol Specification v08 Section: 4.4.3, 5.2.2
Category: Technical Priority: Must Fix
Status: Closed

Created on 2005-10-26.08:47:54 by reh, last changed 2005-12-01.19:20:09.

Messages
msg297 Author: reh Date: 2005-12-01.19:20:09
After some further discussion, an abbreviated Stack-Configuration-Data is now
mandatory in the first message (Confirm) on a new messaging association.
msg261 Author: reh Date: 2005-10-26.08:47:54
[originally raised by Thomas Herzog on the mailing list]

The MA-Hold-Time is only signalled in the SCD object which is sent in Query and
Response messages. However, a responder doing delayed state installation has to
configure a new messaging association based only on the information in the
Confirm, and so cannot recall the MA-Hold-Time value.

Proposed solution:
> i think the neatest solution here is to move the MA_HOLD_TIME to
> the NLI as an optional field there. the Q-node NLI is repeated in
> the confirm. i'd rather not repeat the whole stack-config-data,
> and the stack-proposal is for the 'wrong' node anyway. this is
> not quite as logically pure as the current structure, but is
> probably the right compromise between purity and sophistication.
> (the NLI is repeated in the confirm for precisely the reason that
> the R-node will have forgotten the original, so there is a match
> of purpose here). i will add a new issue for this.
Note that this would also need a flag in the header to indicate the presence of
such a field; we can also define a default value to use if it is not signalled
(rather than having an error about it not being present).
History
Date User Action Args
2005-12-01 19:20:09rehsetstatus: No Discussion -> Closed
messages: + msg297
2005-10-26 08:47:55rehcreate