Re: Fwd: [Nsis-imp] some problems with NSIS_0.3.0

[Bernd Schloer <bschloer at cs.uni-goettingen.de>]

Hi Liao Peizhen,

thank you for your patience!


1. On QNI-side (10.10.2.2) you sent a RESERVE with an RII-object to 10.10.1.1
and requested a RESPONSE by setting the ACK-Flag. The Finite State Machine (FSM)
went from ST_IDLE to ST_WR2.

2. On QNE-side (10.10.2.1) the RESERVE is received and forwarded to 10.10.1.1
over 10.10.1.2. The FSM goes from ST_IDLE to ST_STATEINST.

3. At QNR the RESERVE is received and because of the set ACK-Flag a RESPONSE is
sent back to the Initiator. The FSM goes from ST_IDLE into ST_STATEINST.

4. The QNE receives the RESPONSE and forwards it to the QNI.

5. The FSM of the QNI goes from ST_WR2 to ST_STATEINST. The reservation is
complete on the path.

So far the behaviour is as expected, but not 100% correct. At QNE we should
have built a new message out of the received one. We should have changed the
state to ST_WR2 and not to ST_INST. After receiving the RESPONSE from QNR the
QNE then should have changed to ST_INST.

Also the handling of the ACK-Flag and the RII-Object is in 0.3.0 not correct.
Version 0.4.0 has also on this improvements. On receiving an RII object the QNR
sends a RESPONSE back the QNI. On the receiving an ACK-Flag, a RESPONSE is sent
back to the previous node.


> the client can't get the response,Why?


The client in version 0.3.0 didn't check whether the reservation was successful
or not. Yesterday we released version 0.4.0 where this is fixed. The client
there has an output to the console whether the reservation was successful or
not.

I hope I could answer your question. If not your, questions are welcome.

Bernd


_______________________________________________
NSIS-imp mailing list
NSIS-imp at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/nsis-imp