[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [provision] Charter...
This revision looks good. One small addition: in the second paragraph we should include "modification" to the list -- wherein we can make changes to attributes without having to de-provision and re-provision again. (SPML requests will facilitate the creation, activation, modification, suspension, enablement and deletion of data on managed Provisioning Service Targets.) Thanks, -Anand [Anand Ranthidevan] Product Manager - Jamcracker, Inc. aranthidevan@jamcracker.com https://www.jamcracker.com -----Original Message----- From: Darran Rolls Sent: Fri 1/4/2002 11:14 AM To: Ranthidevan, Anand; Jeff Bohren; provision@lists.oasis-open.org Cc: Subject: RE: [provision] Charter... On the basis that we have received no further comments on the charter, I have taken Anan’s revision and merged it with the specific terms from the draft glossary. In summary I’ve made the following changes: * Changed the definition of what we’ll be exchanging information about in line glossary terms * Change the wording around the scenarios to better fit with the rest of the document * Removed the “core schema” bullet 1 for “common schematic” – I don’t believe we could definitively say that we will have a common schema for all resources On the basis that we do intend to vote on the charter at Monday’s committee call, please comment back before Sunday if these changes need further revision. Please also forward any other agenda items for Mondays call before EOD today. ---------------------------------------------------- The purpose of the OASIS Provisioning Services Technical Committee (PSTC) is to define an XML-based framework for exchanging information between Provisioning Service Points. This framework will be referred to as the Service Provisioning Markup Language (SPML). The Technical Committee will develop an open specification addressing the required semantics for provisioning Service Points to exchange requests relating to managed Provisioning Service Targets. SPML requests will facilitate the creation, activation, suspension, enablement and deletion of data on managed Provisioning Service Targets. The finished specification is expected to include (but is not limited to) core XML schemas for the following: 1) Query and exchange of available Provisioning Service Targets 2) Query and exchange of available Provisioning Service Target attributes and options 3) Query and exchange of available Provisioning Service Targets instance identities 4) Query and exchange of Provisioning Service Targets hierarchies 5) Request and response for specific provisioning requests The specification is expected to facilitate (but is not limited to) the following SPML exchanges: 1) Exchange of provisioning requests between Provisioning Service Points within a single organization 2) Exchange of provisioning requests between Provisioning Service Points hosted by 3rd party providers, aggregators and ASPs 3) Exchange of provisioning requests between Provisioning Service Points with support for chained or forwarded requests SPML will assume a pre-existing trust model between participating Provisioning Service Points and will utilize available security mechanisms for encryption and message integrity. The SPML specification will be developed with consideration of the following existing specifications (which are of public knowledge -- accessible and freely distributed): Active Digital Profile (ADPr), eXtensible Resource Provisioning Management (XRPM), and Information Technology Markup Language (ITML). The goal of the Technical Committee (subject to revision) is to submit a Specification (including Use Cases & Requirements, Information Model, Protocols, Bindings, and Conformance) to the OASIS Membership for its approval by September 2002. ---------------------------------------------------- Darran Rolls MSIM drolls_waveset@hotmail.com AIM drollswaveset YIM drolls_waveset PGP 0x8AC67C6F http://www.waveset.com/ <htp://www.waveset.com> drolls@waveset.com <mailto:drolls@waveset.com> -----Original Message----- From: Ranthidevan, Anand [mailto:aranthidevan@jamcracker.com] Sent: Thursday, January 03, 2002 8:13 PM To: Jeff Bohren; provision@lists.oasis-open.org Subject: RE: [provision] Charter... Based on our discussions on 12/17 and 12/10 (where issues like not having phrases like "end-to-end" in the charter, inclusion of the organization/user identities, and the hosted model, etc. ), I'd like to propose the following modified version for the charter: ------------------------------------------------------------------------ ------------ The purpose of the OASIS Provisioning Services Technical Committee (PSTC) is to define an XML-based framework for exchanging *identity* and *resource* provisioning information. This framework will be referred to as the Service Provisioning Markup Language (SPML). The Technical Committee will develop an open specification addressing the required semantics to exchange identity related requests (where an identity could be organizations, groups, or users) between cooperating provisioning resources. A resource could be any application or system capable of consuming a well-formed SPML request. A Provisioning Request will include actions like: provision, activate, amend, suspend, enable, and delete. The scenarios SPML will cover include (but are not limited to): 1) Provisioning any internal resource within an organization 2) Provisioning any external resource hosted by 3rd party providers, aggregators, ASPs, etc. 3) Providing a Hosted SPML-based provisioning service that can act as an intermediary between two or more systems. The finished specification is expected to include (but is not limited to) core XML schemas for the following: 1) Defining a common schematic to describe a Resource -- including its configurable parameters. 2) Query and exchange of available resources that can be provisioned for an identity 3) Query and exchange of available resource attributes and options 4) Query and exchange of available identities and information pertaining to each identity 5) Query and exchange of resource hierarchies 6) Request and response for specific provisioning messages SPML will assume a pre-existing trust model between participating resources and will utilize available security mechanisms for encryption and message integrity. The SPML specification will be developed with consideration of the following existing specifications (which are of public knowledge -- accessible and freely distributed): Active Digital Profile (ADPr), eXtensible Resource Provisioning Management (XRPM), and Information Technology Markup Language (ITML). The goal of the Technical Committee (subject to revision) is to submit a Specification (including Use Cases & Requirements, Information Model, Protocols, Bindings, and Conformance) to the OASIS Membership for its approval by September 2002. ------------------------------------------------------------------------ ------------ Thanks, -Anand [Anand Ranthidevan] Product Manager - Jamcracker, Inc. http://www.jamcracker.com -----Original Message----- From: Jeff Bohren Sent: Thu 1/3/2002 6:22 AM To: provision@lists.oasis-open.org Cc: Subject: [provision] Charter... I the last meeting I proposed that we vote on the charter in the meeting on jan 7th. From the discussions so far I see no reason the charter last propsed by Darran can not meet our needs. I would like to have this added to the agenda for the meeting. If we can not reach quorum on the 7th, then we should schedule an e-mail vote on this following the meeting. The last draft I saw of this was: ------------------------------------------------------------------------ The purpose of the OASIS Provisioning Services Technical Committee (PSTC) is to define an XML-based framework for exchanging user, resource and service provisioning information. This framework is commonly referred to as the Service Provisioning Markup Language (SPML). The Technical Committee will develop an end-to-end, open specification addressing the required semantics to exchange requests between cooperating provisioning services. A provisioning service is defined as any infrastructure component capable of consuming well formed SPML request. The finished specification is expected to include (but is not limited to) core XML schemas for the following: * Query and exchange of available resources to provision to * Query and exchange of available resource attributes * Query and exchange of available resource identities * Query and exchange of resource hierarchies * Request and response for specific provisioning requests The following are also initial assumptions relating to the scope and nature of the SPML framework: * SPML assumes a pre-existing trust model between the SPML requestor and the SPML compliant service * Encryption and message integrity should be available at the session level (via SSL/TSL) and at the individual element level though XML-Encryption and XML- Signatures The SPML specification will be developed with consideration of the following existing specifications (which are of public knowledge, accessible, and freely distributed). * Active Digital Profile (ADPr) * eXtensible Resource Provisioning Management (XRPM) * Information Technology Markup Language (ITML) The PSTC will produce a set of one or more Committee Specifications that will cover the following (all of which are to be examined with respect to security considerations): * Use cases and requirements * Information model * Protocol(s) * Bindings * Conformance The goal of the committee (subject to revision) is to submit a Specification to the OASIS membership for its approval by September of 2002. -------------------------------------------------------- -- Jeff Bohren Product Architect OpenNetwork Techologies jbohren@opennetwork.com (727) 561-9500x219 ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC