Hi John and all, I think "timer" should not be directly included in the input alphabet of messaging state machines. "start time" and "end time" is managed by ultimate-providers/NRMs. However, as you pointed out, there should be a way to notify "provisioning end time" from the ultimate-providers to upstream NSAs. In the update state machines at the gridforge (which Guy announced yesterday), "provisioning end time" is notified by a "cncl.cf" message. That is, an ultimate provider sends a "cncl.cf" message when provisioning end time comes, even if it has not received a "cncl.rq" message. Please take a look at the ultimate provider's state machine (figure 9) too. BTW, I made a state transition table of PA/RA state machines (attached), to consider all possible cases comprehensively. Questions: 1. Don't we need to consider "cancel failure"? 2. What if unexpected input comes? ("N/A" boxes in the table) Are they all errors? If they are errors, what should the SM do? Tomohiro On Wed, 01 Jun 2011 17:12:01 +0200 (CEST) John MacAuley <john.macauley@surfnet.nl> wrote:

Peoples,

I modified Jerry's state machine based on some discussions in Prague. I added "provision_end" time as an event to go from any state to cancelling.

I have also added a provision pending state. Does this make sense?

John

----- Original Message -----

...

From: "Jerry Sobieski" <jerry@nordu.net> To: nsi-wg@ogf.org Sent: Wednesday, June 1, 2011 10:14:58 AM Subject: [Nsi-wg] State Machine

_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg

Hi John, provision_complete and cancel_complete message initiated by Figure.9 state machine, which are translated to prov.cf and cncl.cf by the PA state machine (Figure 4) works as "start time" and "end time" notifications respectively. If you have time, could we exchange IM over skype. I've sent a contact request to you. Tomohiro On Mon, 6 Jun 2011 09:34:27 -0400 John MacAuley <john.macauley@surfnet.nl> wrote:

Tomohiro,

In this state machine what are the internal messages associated with the timers "start time" of a reservation and the "end time" of the reservation?

Thank you, John.

On 2011-06-03, at 6:06 AM, Tomohiro Kudoh wrote:

...

Hi John and all,

I think "timer" should not be directly included in the input alphabet of messaging state machines. "start time" and "end time" is managed by ultimate-providers/NRMs.

However, as you pointed out, there should be a way to notify "provisioning end time" from the ultimate-providers to upstream NSAs.

In the update state machines at the gridforge (which Guy announced yesterday), "provisioning end time" is notified by a "cncl.cf" message. That is, an ultimate provider sends a "cncl.cf" message when provisioning end time comes, even if it has not received a "cncl.rq" message.

Please take a look at the ultimate provider's state machine (figure 9) too.

BTW, I made a state transition table of PA/RA state machines (attached), to consider all possible cases comprehensively.

Questions: 1. Don't we need to consider "cancel failure"? 2. What if unexpected input comes? ("N/A" boxes in the table) Are they all errors? If they are errors, what should the SM do?

Tomohiro

On Wed, 01 Jun 2011 17:12:01 +0200 (CEST) John MacAuley <john.macauley@surfnet.nl> wrote:

...

Peoples,

I modified Jerry's state machine based on some discussions in Prague. I added "provision_end" time as an event to go from any state to cancelling.

I have also added a provision pending state. Does this make sense?

John

----- Original Message -----

...

From: "Jerry Sobieski" <jerry@nordu.net> To: nsi-wg@ogf.org Sent: Wednesday, June 1, 2011 10:14:58 AM Subject: [Nsi-wg] State Machine

_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg

<MSG-SM.xlsx>