On Dec 2, 2009, at 2:24 AM, Inder Monga wrote:

John,

For discussion tomorrow, a few questions:

1. We have narrowed down the definition of the Network Service Interface as an interface just to request transport connections. I think we need to be a bit careful of this narrowing of definition "•NSI is the protocol that allows a user to request a transport connection from a provider (but not limited to)

I think it is limited. My take is that not limiting it makes defining it much harder. What else do you think should be an NSI protocol?

2. Do we need transport user and transport provider definitions? I am not sure what purpose that serves...why not network services user and network services provider?

I think the service is transport. Probably this goes with the above question.

3.Slide 5:Actor may include multiple agents with interfaces to services managing other resources such as storage or compute"

If the context is NS Actor, then it does not seem likely it will be managing other resources like compute and storage? (ref slide 5 and 6) There is a concept of multi-resource scheduler/actor, but that would be different from NS actor

4. Brokers and Wholesalers: Are we going out of scope by talking about different resources other than the network? Do we need to define these concepts within NSI? This has to do with defining trust and authorization capabilites. I

the point is that and Actor may have multiple roles, one of which is NS actor when talking about an NS interface. think it useful to point out different ways that Actors might behave so that one can think about trust and authorization in a flexible way. The need for them in NSI is to be sure that the NSI interface can support them if it need fields to carry attributes, parameters, in different ways. John

Thanks, Inder

On Dec 1, 2009, at 2:32 PM, John Vollbrecht wrote:

...

<NSI.overview.path.agent.11.30.09.ppt>

On Dec 2, 2009, at 2:33 AM, Inder Monga wrote:

For discussion tomorrow - a possible variation could be:

Network Service Plane: defined as a set of abstract network capabilities offered as a service to authorized user entities. The set of services include, but are not limited to, connection provisioning, topology , monitoring , measurement services. The user entities could include external users, applications, management stations, etc.

I think this is an interesting take. My thinking is that there is a service plane that has lots of services that can be used by an actor. NS provider is one of these services. Putting together an actor may include using multiple providers as well as multiple other services. The set of services used by an actor is not limited to whatever is defined in NSI. What I think, but am not sure of, is that there is an OGF wg that is dealing with network information services. This would be the place I think some of your examples would go.

Network Service Interface: An interface between a network service requestor and a network service plane to request network services. For NSI 1.0, we are limiting the services possible be requested to the connection provisioning services.

I would say (as before) that I think it should be limited for the long term as well.

Network Service Actor: an entity that includes an agent to get or provide network services using the twork Service Interface (which in the first instantiation only supports connections or connection reservations).

Again, I see NS Actor as a role for an Actor which may have other roles. John

Thanks, Inder

On Dec 1, 2009, at 2:32 PM, John Vollbrecht wrote:

...

Attached is a revised set of slides based on comments to the ones I sent a yesterday.

We will have a call tomorrow at 9 ET

Call infoCall: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0155180

Tentative Agenda -- please suggest changes on line or on the call --

we can pick from the following or added suggestions

-overview of slides -- how can they be used to help build the document - issues from Guy's list

- discuss naming agent, actor, provider agent/ actor, requestor agent/actor ports, subports, connections, segments, links service/control, data/transport planes I am thinking we should see if we have consensus on these names. If so hopefully it can be fast. If not I think we should identify where differences are and take it to email or skype chat

- agent finding description -- going from path finding to authorizing path segments This is not really in scope for NSI, but I think we need to talk about it and how it fits in our Recommendation I would like to take this to email or skype if necessary as well

- Chin's diagram

- NS provider Actor as service provider how service provider fits with GMPLS Also how requestor fits with applications/ middleware

<NSI.overview.path.agent.11.30.09.ppt> _______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg