OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

provision message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [provision] Interop working group call


Wednesday, 10AM CST  is ok.

As for adding an "SPML multiplexer" :

Technically speaking, I feel it adds more complexity and additional failure
point thus it increases the integration efforts required and risks for
success for the interop. 
As for the concept, I do believe adding another component undermines the
interoperability promise of SPML as it does not demonstrate how PSFT is
interoperable as RA with multiple vendors PSPs and I prefer to have in the
interop a scenario that matches the original model suggested by SPML which
is cleaner and easier to explain to the visitors. 

Doron

Doron Cohen
BMC Software

-----Original Message-----
From: Darran Rolls [mailto:Darran.Rolls@waveset.com] 
Sent: Tuesday, May 20, 2003 12:33 AM
To: provision@lists.oasis-open.org
Cc: Glenn_sulzberg@peoplesoft.com; sam.tang@mycroftinc.com
Subject: [provision] Interop working group call


As discussed on today's call we need to quickly convene a working group call
to iron out a new scenario for the interop.  I propose we do this at 10am
central Wednesday 5/21.  I know there is no way this time is going to work
for everyone; we need Glenn, Sam and those committee members that want to
help drive this re-work.  Take a cold hard look at your calendars and let me
know if this will work. 

As a pre-curser to this call I have an idea.  In the real world, an SPML
compliant PSFT would not operate as a full PSP (doing service/rules/role
based provisioning out to digital and no-digital resources).  It would
likely send its SPML event to a PSP for onward processing and all that jazz.
Because we have many different vendors and applications participating in
this event, it arguably does not make sense for the PSFT implementation to
be responsible for managing the host of asynchronous events needed for the
interop.  

It might make sense for Mycroft to be the (for want of a better term) "fan
out module" that takes this single event and propagates it to all the
PSP/PST's at the event.  In effect Mycroft would be developing a limited
functionality PSP that would be vendor/product/solution independent.  This
module would serve as an SPML multiplexer, supplying the glue to make the
scenario work.

Something along these lines would allow us to show a scenario that includes
PSFT, Mycroft and the current list of PSP/PST vendors to be shown all
working together.

Food for thought - let me know about Wednesday.

Thanks

=========================================================
Darran Rolls                      http://www.waveset.com
Waveset Technologies Inc          drolls@waveset.com 
512) 657 8360                     
=========================================================


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]