RE: [provision] Austin F2F#1 Straw-man Agenda]

["Ranthidevan, Anand" <aranthidevan@jamcracker.com>]

Folks,

 

From our perspective, a good definition of DSML would be along the lines of:

 

DSML is "SPML" for Directory Servers

 

In December when we were talking about 'Resources' -- we did list Databases and Directories (now defined as a 'Provisioning Service Target or PST). We also decided that we will not worry about the exact semantics for each Resource. DSML is a good example of a pre-existing standard for the Directory Resource.

 

Net-net, my take is that we should look at SPML being able to wrap around a DSML message (when the Resource is a Directory), but otherwise, the scope and nature of SPML is very different, and as Yoav points out (and as the documents submitted so far reflect), covers a much broader spectrum.

 

-Anand

 

----Original Message-----
From: Yoav Kirsch [mailto:Yoav.Kirsch@businesslayers.com]
Sent: Thursday, February 07, 2002 12:43 PM
To: 'Gavenraj Sodhi'; Yoav Kirsch; Adrian Viego
Cc: 'provision@lists.oasis-open.org'
Subject: Re: [provision] Austin F2F#1 Straw-man Agenda]

 

DSML v2 is a Directory protocol and allows user to manipulate Directory entries through XML.

Provision protocol should support a much broader aspect. The provision protocol should support workflow features such as provision dates. (Do we need this resource now or can we wait for next month), Approval chain (who approve the provisioning), Billing information (we should support scenarios where the provision server actually charge for the resources that it supplies. This is the ASP model) and support Auditing and reporting functionalities.

Another difference is that provisioning activity may take few days. The protocol should support this and allows disconnected transaction between the client and the server.

In general I Think that the following protocols SOAP ,UDDI, ebXML , are closer to the SPML protocol and that we should use them as our starting point

 

Yoav Kirsch 

-------- Original Message --------

Subject:	Re: [provision] Austin F2F#1 Straw-man Agenda
Date:	Thu, 07 Feb 2002 08:10:33 -0500
From:	jbohren@opennetwork.com (Jeff Bohren)
Organization:	OpenNetwork Technologies, Inc.
CC:	provision@lists.oasis-open.org
References:	6244FCD1F88EC14BACDD2A319FD338242A61C5@hawaii.waveset.com"><6244FCD1F88EC14BACDD2A319FD338242A61C5@hawaii.waveset.com>

 
Although I will not be able to attend the F2F in Austin, I would like to make a proposal in refence to the "Core Protocol - Model Overview" section of the agenda.

I would like to propose that instead of creating another XML protocol for provisioning, that the SPML standard be based on the DSML V2 standard. I am suggesting that we use DSML V2 as the SPML protocol and define a set of schemas that define the provisioning model.

I believe that defining a Provisioning Model is going to be the most difficult task for this group, so by using a predefine protocol, we would be that must closer to a standard. So far I have not seen anything in the submitted use cases that could not be accomodated with DSML V2 as the protocol.

I apologize for making this proposal without being able to attend the F2F and discuss it. But I feel that it is important to put this forward if the group is going to be talking about the core protocol.

Jeff Bohren

Darran Rolls wrote:

Folks 

Below is a straw-man agenda for next weeks meeting. The general objective is to discuss develop and produce a body of technical requirements suitable to begin the analysis and development of the core protocol.  The general tone of the meeting is that of a guided open discussion. The intention is to produce a large list of technical requirements, issues and comments for presentation back to the list and committee members.

I have arranged for teleconference facilities in the room. There will also be IP available for everyone that needs it. Where applicable we can arrange Webex web conferencing for any remote members that want to connect and see any slides that might be available - I intend to have a summary presentation of the use cases and the Core Protocol Model overview – these would be suitable for “broadcast”.

If you are not attending but would like to dial-in for any part of the agenda please let me know in advance. Also, regardless of attendance, do feel free to suggest changes/amendments/additions – I’m doing the agenda because you are not ;-) 

Monday 11^th February 2002

9:00 Coffee 

9:30 Call to order

9:35 Review agenda – agree meeting objectives

9:45 Proposed f2f dates through July

10:00 Use case reviews

12:30 Lunch

1:30 Use case next steps

2:00 Core protocol - model overview

3:00 Coffee break

3:15 Requirements for authentication & authorization

5:00 Adjourn

7:30 Local dinner for anyone interested

Tuesday 12^th February 2002

8:30 Coffee

9:00 Call to order

9:05 Requirements for request/response message flows

10:30 Requirements for state & session management

11:30 Requirements for error handling and status reporting

12:30 Lunch

1:30 Requirements for dynamic schema discovery

2:30 Suggestions for sub-committees & next steps

3:00 Adjourn

Darran Rolls
MSIM  drolls_waveset@hotmail.com
AIM    drollswaveset
YIM    drolls_waveset 

PGP0x8AC67C6F
http://www.waveset.com/
drolls@waveset.com

--
Jeff Bohren
Product Architect
OpenNetwork Techologies
jbohren@opennetwork.com
(727) 561-9500x219