[Nsi-wg] Specification Completion - suggestions
Inder Monga
imonga at es.net
Wed Mar 9 08:55:27 CST 2011
Open Issues and plan for spec completion
Deliverable for March 30th
completed WSDL(s) for NSI-WG
Web Services Framework
What WS Standards are needed
Prefer WS-Addressing for async bi-directional communication
Security
Message Primitives
Attribute details
completed connection services architecture doc
2. Completed WSDL(s) for NSI-WG
Message Primitives
Message attributes
3. Open Issues before spec complete
Message Primitives
Agreed upon behavior for Request, Provision, Release
Finalize
Cancel Confirm?
Query (Management message)
Notify (for Asynchronous PA -> RA notification)
Modify (not in this spec, to be discussed after this version of spec is done?)
STP definition and architecture -
Should we do STP later?
For demo specification
Requestor will specify complete end-point
The aggregator will know what to do
Service Definition
Basic List of attributes
Questions
* Is Service Definition a template or not?
* Do we support optional network specific features?
---
Inder Monga
imonga at es.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/nsi-wg/attachments/20110309/19d8f652/attachment.html
More information about the nsi-wg
mailing list