Re: Service Provisioning [was: FW: [members] SPML v2.0 Submitted for OASIS Standard]

Romascanu, Dan (Dan) wrote:
> Interesting. 
>
> Did anybody do a comparative analysis between SPML and Netconf? If
> somebody is asking when to use SPML and when to use Netconf, what is the
> answer? 
>
>   

I looked over this document:
http://docs.oasis-open.org/provision/spml-2.0-cd-01/pstc-spml2-cd-01.html

It looks pretty complete, and complex.
There is familiar terminology, like "targets" and "capabilities".
There are more powerful abstractions, like "batch", and it
is more object-oriented than netconf (which tries to be content-neutral).

There appears to be implementations from 3 companies,
all authors of SPML.  (BMC, Tripod, Sun)

It comes down to how much NM do you want to pay for.
IMO, netconf is more suited to embedded devices which are 
resource-sensitive,
and do other things besides NM as their primary function.
SPML looks more suited to open systems, like Sun workstations,
with lots of resources for NM (probably the primary function of the WS).

> Dan
>   

Andy

>
>  
>  
>
>   
>> -----Original Message-----
>> From: [email protected] 
>> [mailto:[email protected]] On Behalf Of Wijnen, Bert (Bert)
>> Sent: Wednesday, March 01, 2006 11:20 AM
>> To: Ops-Nm (E-mail)
>> Subject: Service Provisioning [was: FW: [members] SPML v2.0 
>> Submitted for OASIS Standard]
>>
>> FYI and possible comment
>>
>> Bert
>>
>> -----Original Message-----
>> From: Mary McRae [mailto:[email protected]]
>> Sent: Wednesday, March 01, 2006 03:33
>> To: [email protected]; [email protected]
>> Subject: [members] SPML v2.0 Submitted for OASIS Standard
>>
>>
>> OASIS Members:
>>
>> The OASIS Provisioning Services Technical Committee has 
>> submitted the following specification set, which is an 
>> approved Committee Specification, to be considered as an 
>> OASIS Standard:
>>
>> Service Provisioning Markup Language (SPML) v2.0 Service 
>> Provisioning Markup Language (SPML) v2.0 - DSML v2.0 Profile 
>> Service Provisioning Markup Language (SPML) v2.0 - XSD Profile
>>
>> The TC's submission is attached below.
>>
>> In accordance with the OASIS Technical Committee Process, the 
>> specification has already gone through a 60 day public review period:
>>
>> http://lists.oasis-open.org/archives/tc-announce/200510/msg00003.html
>>
>> OASIS members now have until the 15th of March to familiarize 
>> themselves with the submission below. OASIS members should 
>> give their input on this question to the voting 
>> representative of their organization.
>>
>> By the 16th of the month we will send out a Call For Vote to 
>> the voting representatives of the OASIS member organizations, 
>> who will have until the end of the month to cast their 
>> ballots on whether this Committee Specification should be 
>> approved as an OASIS Standard.
>>
>> The normative TC Process for approval of Committee 
>> Specifications as OASIS Standards is found at
>> http://www.oasis-open.org/committees/process.php#3.4
>>
>> Any statements related to the IPR of this specification are posted at:
>> http://www.oasis-open.org/committees/provision/ipr.php
>>
>> Mary
>>
>> Mary P McRae
>> Manager of TC Administration, OASIS
>> email: [email protected]
>> phone: 603.232.9090
>>
>> -----------------------
>>
>> PS TC Submission for SPML 2.0
>>
>> 1. Links to the approved Committee Specification in the TC's 
>> document repository, and any appropriate supplemental 
>> documentation for the specification, both of which must be 
>> written using the OASIS templates. The specification may not 
>> have been changed between its approval as a Committee 
>> Specification and its submission to OASIS for consideration 
>> as an OASIS Standard, except for the changes on the title 
>> page and running footer noting the approval status and date 
>>  
>> SPML 2.0 Package - 
>> http://www.oasis-open.org/committees/download.php/16695/pstc-s
>>     
> pml-2.0-cs-01.zip
>         
> 2. The editable version of all files that are part of the Committee
> Specification; 
>
> SPML 2.0 Package -
> http://www.oasis-open.org/committees/download.php/16695/pstc-spml-2.0-cs
> -01.zip
>
>
> 3. Certification by the TC that all schema and XML instances included in
> the specification, whether by inclusion or reference, including
> fragments of such, are well formed, and that all expressions are valid; 
>    
> The XML examples in the documents and the SPML 2.0 schema are
> well-formed. We have run all of the examples through an XML
> well-formedness checker. 
>
> 4. A clear English-language summary of the specification; 
>        
> The specifications describe a mechanism for provisioning users,
> accounts, and services using SOAP web services. The specifications
> include the basic Service Provisioning Markup Language 2.0 specification
> as well as two profiles that define provisioning data models. One
> profile, the DSML Profile, defines a DSML v2 based provisioning data
> model. The other, the XSD Profile, defines an XSD based provisioning
> data model.
>
> 5. A statement regarding the relationship of this specification to
> similar work of other OASIS TCs or other standards developing
> organizations; 
>        
> This work builds upon, but does not attempt to duplicate, the work of
> Several standards efforts. Including: 
>
>  DSML v2 (OASIS Directory Services TC)
>  SAML 1.1, 2.0 (OASIS SS TC)
>
> 6. Certification by at least three OASIS member organizations that they
> are successfully using the specification; 
>        
> Certifications have been received from the following companies. We are
> including URLs that point to the certification statements in the e-mail
> archive. 
>
> BMC Software - 
> http://lists.oasis-open.org/archives/provision/200601/msg00001.html   
>
> Tripod Technology Group -
> http://lists.oasis-open.org/archives/provision/200601/msg00013.html 
>
> Sun Microsystems - 
> http://lists.oasis-open.org/archives/provision/200601/msg00014.html     
>
> 7.  The beginning and ending dates of the public review(s), a pointer to
> the announcement of the public review(s), and a pointer to an account of
> each of the comments/issues raised during the public review period(s),
> along with its resolution; 
>      
> The Public Review began on 03 October 2005 and ended on 02 December
> 2005.
>
> Here is the announcement of the Public Review
> http://www.oasis-open.org/archives/members/200510/msg00003.html.  
>
> The PS TC address all issues raised during the public review period.
> This is found at:
> http://www.oasis-open.org/committees/download.php/16502/Comments%20from%
> 20review%20period.doc.
>
> 8. An account of and results of the voting to approve the specification
> as a Committee Specification, including the date of the ballot and a
> pointer to the ballot; 
>       
> The Committee Specification Ballot was created on 26 Jan 2006 
> The results were 10=Yes (91%), 0=No, 0=Abstain   
> The TC had 11 voting members
> The ballot is here: 
> http://www.oasis-open.org/committees/ballot.php?id=945. 
>
> 9. An account of or pointer to votes and comments received in any
> earlier attempts to standardize substantially the same specification,
> together with the originating TC's response to each comment; 
>      
> This is the first attempt to standardize the SPML 2.0 specification. 
>
> 10. A pointer to the publicly visible comments archive for the
> originating TC;
>      
> http://lists.oasis-open.org/archives/provision-comment/  
>
> 11. A pointer to any minority reports submitted by one or more Members
> who did not vote in favor of approving the Committee Specification,
> which report may include statements regarding why the member voted
> against the specification or that the member believes that Substantive
> Changes were made which have not gone through public review; or
> certification by the Chair that no minority reports exist. 
>
> No such reports have been submitted.
>
>
> ---------------------------------------------------------------------
> This email list is used solely by OASIS for official consortium
> communications. Opt-out requests may be sent to
> [email protected], however, all members are strongly
> encouraged to maintain a subscription to this list.
>
>
>
>
>
>