[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-rx] State tables rev of July 25
On the MakeConnection tables I think the table labeled RMS is really RMD, and likewise the RMS table is the RMD. I don’t think there is anything to say about the non-response situation here, maybe [none].
The other changes look good to me.
Regarding your new question, no. I think there are a number of blanks where that would not make sense. I think leaving it as is with the explanation that it is not normal protocol behavior is sufficient.
I have incorporated the results of the resolution last meeting to the message number rollover discussion.
We will need to update these tables when there is a resolution to the expiry issue which hopefully will occur this week.
There has also been an attempt made to incorporate the results of make connection to fulfill my action item on that subject.
Since Make Connection is not related solely to a specific sequence, it did not fit into the fabric of the other state tables previously submitted.
I chose to add a couple more tables to demonstrate a simplistic underlying message transfer engine. Section 3.7 is not clear (to me) as to what conditions cause the initiation of polling, what might trigger a specific poll (interval or event), or how long such polling might continue.
I also do not see what the negative response to a poll might be and what the RMD might do upon receipt of the negative (or non) response.
So please take it for now for discussion and hopefully out of the fire there might be found an answer or two.
There has been a new event added to the RMD table indicating the receipt of an invalid acknowledgement fault. In Section 4 the fault is described but I cannot locate what its implications might be.
All of the blank cells in the table are unspecified behavior in the specification. Should they be filled with “generate Sequence Terminated Fault”?