Hi Inder,

But in the future, we may have services like point-to-multipoint (i.e.
virtual network) service, which will have temporal aspects too.

So, I believe "temporal aspects" is generic to (not all but) multiple
services, and putting it to the generic architecture part is better for
future extension of NSI.

Tomohiro

On Sun, 20 Jun 2010 13:41:48 -0700
Inder Monga <imonga@es.net> wrote:

Dear Tomohiro,

We decided to take out the temporal aspects from the generic architecture and move it into the Connection Service discussion. The reason being that the NSI protocol message exchanges did not require a time synchronization. They mostly depend on state machines and relative timing.

Inder

On Jun 20, 2010, at 1:32 PM, Tomohiro Kudoh wrote:

Hi all,

I could not hear the later part of the previous session clearly, so

maybe I miss the point, but:

- if request path is hierarchical, service instances also have

hierarchical relationship. That is, a service instance is created for

each provider along the path.

- temporal aspects may exist not only for the connection service but

also for other (to be defined) services.

Tomohiro

_______________________________________________

nsi-wg mailing list

nsi-wg@ogf.org

http://www.ogf.org/mailman/listinfo/nsi-wg

---

Inder Monga http://100gbs.lbl.gov

imonga@es.net http://www.es.net

(510) 499 8065 (c)

(510) 486 6531 (o)