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

 


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

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


Subject: RE: [security-services] Agenda for 28-Oct SSTC con-call


Rob,

Could we spend some time discussing how we will 
prioritize work items (and use-cases) on November 11.

- prateek 

-----Original Message-----
From: Philpott, Robert
To: 'security-services@lists.oasis-open.org'
Sent: 10/27/2003 5:46 PM
Subject: [security-services] Agenda for 28-Oct SSTC con-call

The dial-in # is: (865) 673-3239. The access code is: 238-3466#.
Commands are *6 (mute), *7 (unmute), and ** (menu).

 

1.	Roll call
2.	Agenda bashing
3.	Accept minutes from 14-Oct SSTC con-call

a.
http://lists.oasis-open.org/archives/security-services/200310/msg00102.h
tml
<http://lists.oasis-open.org/archives/security-services/200310/msg00102.
html> 

4.	Summarize Oct 22-24 SSTC Face-to-Face

a.	Partial minutes:
http://lists.oasis-open.org/archives/security-services/200310/msg00182.h
tml
<http://lists.oasis-open.org/archives/security-services/200310/msg00182.
html> 

                                                               i.
Friday afternoon (10/24) minutes are being cleaned up and will be sent
out soon...

b.	Many issues and action items described in the minutes - Not yet
entered into Kavi.
c.	Votes/Concensus items:

                                                               i.
Target for next V2.0 f2f is week of Jan 12th

                                                             ii.
Motion: SAML TC recommends that XACML TC derive types from SAML schema,
saml:statement and samlp:query to support authorization decision, and
that liaison be established to follow up on this.  Passed unanimously

5.	Next steps:

a.	Review published list of Use Cases and vote for final inclusion
in V2.0 at 11-Sept con-call.

6.	Action Item Review (from Kavi - some were dealt with at the
F2F):

 


Report created 27 October 2003 05:51pm EST


 


#0072: Authentication Context


Owner: Jeff Hodges


Status: Open


Assigned: 16 Sep 2003


Due: ---


Comments:
Prateek Mishra 2003-09-16 12:11 GMT
Main task is to approrpiately move Liberty AuthContext specification
into OASIS (so it becomes a standard). 

Jeff will ping Paul Madsen to see if he is interested.


  _____  


#0069: Baseline Attribute Namespaces


Owner: Bob Morgan


Status: Open


Assigned: 16 Sep 2003


Due: ---


Comments:
Prateek Mishra 2003-09-16 12:01 GMT
Use-case discussed at F2F and generally supported. Waiting for solution
proposal.

For example, a DSML or X.500 profile for a person's attributes expressed
in SAML.


  _____  


#0068: Delegation and Intermediaries


Owner: Bob Morgan


Status: Open


Assigned: 16 Sep 2003


Due: ---


Comments:
Prateek Mishra 2003-09-16 11:58 GMT
Delegation and Intermediaries
Use cases that support arbitrary multi-hop delegation. Liberty WSF
supports one-hop impersonation. The relationship of this to WSS needs to
be sorted out. This relates to the Fidelity need for a WSRP profile.
This is related to W-11. The item "multi-participant transactional
workflows" was folded into this one.

Prateek Mishra 2003-09-16 11:59 GMT

WAITING for Use-Case proposal.


  _____  


#0073: Extract enhancement requests from current issues list


Owner: Eve Maler


Status: Open


Assigned: 16 Sep 2003


Due: ---


Comments:


  _____  


#0082: Promised V2.0 Changes


Owner: Eve Maler


Status: Open


Assigned: 16 Sep 2003


Due: ---


Comments:
Prateek Mishra 2003-09-16 18:23 GMT
Removing (core)
Removing (core)
Removing deprecated NameIdentifier URIs (core)
Requiring URI references to be absolute (core)
Disallowing as the only child of a SOAP (bindings)
Removing deprecated artifact URI (bindings)


  _____  


#0070: SAML as a SASL security mechanism


Owner: Bob Morgan


Status: Open


Assigned: 16 Sep 2003


Due: ---


Comments:
Prateek Mishra 2003-09-16 12:04 GMT
Active work item -- waiting solution proposal.

Defining SAML as a SASL security mechanism.

Prateek Mishra 2003-09-16 18:09 GMT
Re-spun title of action item.


  _____  


#0076: XACML Proposal for Policy Transport


Owner: Hal Lockhart


Status: Open


Assigned: 16 Sep 2003


Due: ---


Comments:
Prateek Mishra 2003-09-16 14:39 GMT
Waiting on a solution proposal. 

XACML has asked for a SAML-based solution to transporting requests for
policies and the policies themselves.

 



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