Re: [security-services] Roles for SAML 2.0 Metadata

[Anthony Nadalin <drsecure@us.ibm.com>]

> if you have any specific alternative solution proposals, now is exactly the time to bring them forward.

yep, seems like we crossed , I'm trying to understand enough to make a well throughout proposal. I'm leaning towards the profiles actually defining the "roles" and not the metadata specification.

Anthony Nadalin | work 512.436.9568 | cell 512.289.4122
"Eve L. Maler" <Eve.Maler@Sun.COM>

"Eve L. Maler" <Eve.Maler@Sun.COM> 12/30/2003 10:12 AM

To: Anthony Nadalin/Austin/IBM@IBMUS cc: security-services@lists.oasis-open.org Subject: Re: [security-services] Roles for SAML 2.0 Metadata

Aha, I think we got tangled up in "analysis" vs. "design" perspectives
here.  We did indeed accept this work item and the associated use cases,
but it's true that we have not yet done any final acceptance of the
solution proposal.  So if you have any specific alternative solution
proposals, now is exactly the time to bring them forward.

Jahan was asked to publish the list of participants/roles we're
considering, which is sort of like a finer-grained use case discussion.
 It sounds like you prefer a design solution where the list of roles
somehow becomes irrelevant.  Again, a specific proposal will allow the
TC as a whole to judge whether your approach meets the accepted use
cases better than the existing solution proposal.

Eve

Anthony Nadalin wrote:

>  >Given our decisions already made to date on this work item, what's up
> for grabs now is not *why* to do things this way, but rather *which*
> config >data to cover for now.
>
> I disagree, just because someone else did it this way is no reason to
> accept, so I believe all items are still up for grabs.
>
> Anthony Nadalin | work 512.436.9568 | cell 512.289.4122
--
Eve Maler                                        +1 781 442 3190
Sun Microsystems                            cell +1 781 354 9441
Web Products, Technologies, and Standards    eve.maler @ sun.com


To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/security-services/members/leave_workgroup.php.