[Nsi-wg] revised slides/ call notes
John Vollbrecht
jrv at internet2.edu
Wed Nov 11 10:25:24 CST 2009
At our call today were Guy, Chin, Tomohiro, Jerry, Joan, Inder and my
self.
1) we discussed the model of what we are now calling a NS Actor/
Component. We defined the components of this as
NSI -- Network Service Interface
Provider agent - provider side of NSI
Requestor agent - requestor side of NSI
NS Actor - set of actors that perform act as a whole. Includes one or
more NS agents/ 0 or 1 provider agents, 0 to N requestor agents
Actor may be renamed Component -- to be discussed in future
We agreed on these names based on Joan's description of web services
definitions. Joan will provide a writeup and pointer(s) to this for
the doc.
Attached is a modified ppt that includes these names as I understand
them. This is based on a version I got from Joan and modified a bit
more. Comments and corrections please.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NSI-authority-NSActor.v2.11.11.09.ppt
Type: application/vnd.ms-powerpoint
Size: 98816 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/nsi-wg/attachments/20091111/51e64eae/attachment-0001.ppt
-------------- next part --------------
2) we discussed in the PPTs I sent the role of aggregation/
coordination module. This requests resources from other agents and
returns them with appropriate parameters to the requestor. The
resource returned by the Provider agent includes all the resources
aggregated by the aggregation/coordination module.
3) we discussed the diagram that Chin sent out with functional
modules. There was a lot of discussion about this, and Chin suggested
that we focus in the short term on defining elements and put the
diagram on hold till we get farther on this. People liked the
concept of the document and that it helped discussion, but now needs
to be revised. Every one should send comments to Chin on this.
-- some comments I remember:
a) Part of Authentication and authorization may need to be part of NSI
interface. Other parts may be in RMM agent and in Actor support
modules.
b) aggregation/ coordination module should be added to the diagram
c) message interpretation/ analysis should probably be included
somewhere - the concept that there might be simple/ loose/ strict
requests.
There will be a protocol meeting at SC at 2PM PT Tuesday next week.
The next regular call will be Wed Nov 25 at 9ET.
John
More information about the nsi-wg
mailing list