Hi Henrik, The state machine matrix follows the current design of state machine. The "prov.rq" message sent at the Auto-provision state is for children, to propagate the provision request. In the current design, no prov.cf is returned to the requester at the time a prov.rq message is received if it is before the start-time. The SM silently transits to "Auto provision" and then transits to "Provisioning" at the start-time. It returns prov.cf or prov.fl when actual provisioning is succeeded/failed at the start-time. There is an argument on this matter as shown in: http://code.google.com/p/ogf-nsi-project/issues/detail?id=9&colspec=ID Type Status Priority Owner FoundInVersion FixedInVersion Summary The design may be changed after discussion. But at this moment, the SM matrix is right. Tomohiro 2011/9/30 Henrik Thostrup Jensen <htj@nordu.net>:
Hi again
On Fri, 30 Sep 2011, Tomohiro Kudoh wrote:
Regarding the provisioning timeing, for example,
start-time of this reservation was 19:51 after the hour.
Provision request was received at 19:34 after the hour. So, it is auto-provisioning.
Therefore, following the current state machine specification, a provision confirm is sent at the start-time, 19:51 after the hour.
OK, I am a bit confused here.
If I look at the state machine matrix, a provision request for a connection in reserved state should result in a transition to Auto-provision and emit a prov.rq message. AFAICT this is wrong.
The question is if there should be no message emitted (i.e., wait till the start_time event occurs, but there is no message emitted for that either). Alternatively (and this is what I _think_ is correct) is that a prov.cf message should be emitted.
Best regards, Henrik
Henrik Thostrup Jensen <htj at ndgf.org> NORDUnet / Nordic Data Grid Facility.