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: Agenda for SSTC Conference call, July 27


> Dial in info: +1 865 673 6950 #351-8396
 
1. Accept minutes from July 20 conference call
 
http://lists.oasis-open.org/archives/security-services/200407/msg00134.html
<http://lists.oasis-open.org/archives/security-services/200407/msg00134.html
> 
 
 
2.  Status of last call review
 
 
a. Proposal to extend meta-data with attribute values
 
http://lists.oasis-open.org/archives/security-services/200407/msg00127.html
<http://lists.oasis-open.org/archives/security-services/200407/msg00127.html
> 
 
b. Comments on sstc-saml-core-2.0-draft-17.pdf
 
http://lists.oasis-open.org/archives/security-services/200407/msg00128.html
<http://lists.oasis-open.org/archives/security-services/200407/msg00128.html
> 
 
c. Corrections to Sstc-saml-bindings-2.0-draft-16.pdf
 
http://lists.oasis-open.org/archives/security-services/200407/msg00136.html
<http://lists.oasis-open.org/archives/security-services/200407/msg00136.html
> 
 
d. detailed comments on sec 4.2 Enhanced Client and Proxy (ECP)
Profileofsstc-saml-profiles-2.0-draft-17
 
http://lists.oasis-open.org/archives/security-services/200407/msg00144.html
<http://lists.oasis-open.org/archives/security-services/200407/msg00144.html
> 
 
3. New drafts
 
SAML 2.0 Technical Overview uploaded
http://lists.oasis-open.org/archives/security-services/200407/msg00133.html
<http://lists.oasis-open.org/archives/security-services/200407/msg00133.html
> 
 
sstc-saml-2.0-issues-draft-13-diff.pdf uploaded
http://lists.oasis-open.org/archives/security-services/200407/msg00126.html
<http://lists.oasis-open.org/archives/security-services/200407/msg00126.html
> 
 
4. Open AIs
#0188: Update conformance document with focus call input	
Owner: Prateek Mishra	
Status: Open	
Assigned: 26 Jul 2004	
Due: ---	
Comments:
Prateek Mishra 2004-07-27 03:27 GMT
http://lists.oasis-open.org/archives/security-services/200407/msg00134.html


  _____  

#0187: Broaden Conformance Introduction	
Owner: Eve Maler	
Status: Open	
Assigned: 26 Jul 2004	
Due: ---	
Comments:
Prateek Mishra 2004-07-27 03:25 GMT
AI: Eve to write up a text section and a suggested new title for the 

Conformance document, reflecting this wider role, and post these to the 

list.	

  _____  

#0186: Proper use of URIs results in uniqueness	
Owner: Scott Cantor	
Status: Open	
Assigned: 26 Jul 2004	
Due: ---	
Comments:
Prateek Mishra 2004-07-27 03:23 GMT
AI: Scott add something to Core around our use of URIs as identifiers in 

the spec, to explain that proper use of URIs results in uniqueness.	

  _____  

#0185: Rationalize presence of empty elements in schema	
Owner: Scott Cantor	
Status: Open	
Assigned: 26 Jul 2004	
Due: ---	
Comments:
Prateek Mishra 2004-07-27 03:22 GMT
Scott to rationalize presence of empty elements in 

empty types in the schemas.	

  _____  

#0184: Send SSTC response to Thomas Grss paper to the author	
Owner: 	
Status: Open	
Assigned: 23 Jul 2004	
Due: ---	
Comments:
Rob Philpott 2004-07-23 17:11 GMT
Per 20-July con-call: AI: ultimately to provide a formal response to Thomas
Gross.	

  _____  

#0183: Comment s solicited on John Linn response to Thomas Gross paper	
Owner: Prateek Mishra	
Status: Open	
Assigned: 23 Jul 2004	
Due: 23 Jul 2004	
Comments:
Rob Philpott 2004-07-23 17:10 GMT
Per 20-July con-call: Prateek (by July 23) to comment on the draft of John
Linn's draft of our response to the Thomas Gross security analysis.	

  _____  

#0182: Use Conform. doc as entry point to docs	
Owner: Eve Maler	
Status: Open	
Assigned: 23 Jul 2004	
Due: ---	
Comments:
Rob Philpott 2004-07-23 16:59 GMT
Per 20-July con-call:
AI: Eve to write up a text section and a suggested new title for the
Conformance document, reflecting this wider role (make the Conformance doc
the official entry point of the doc set), and post these to the list.	

  _____  

#0181: Explain that proper use of URIs results in uniqueness	
Owner: Scott Cantor	
Status: Open	
Assigned: 23 Jul 2004	
Due: ---	
Comments:
Rob Philpott 2004-07-23 16:46 GMT
Per 20-July con-call:
AI: Scott add something to Core around our use of URIs as identifiers in the
spec, to explain that proper use of URIs results in uniqueness.	

  _____  

#0180: Need to update SAML server trust document	
Owner: Jeff Hodges	
Status: Open	
Assigned: 12 Jul 2004	
Due: ---	
Comments:
Rob Philpott 2004-07-20 01:59 GMT
Original AI was for Eve to follow up with Jeff to determine whether he would
be updating this doc. That was done.

Discussion of this AI on 13-Jul indicates that the update will be a post 2.0
deliverable. Reassigned AI to Jeff for now.	

  _____  

#0179: Does conformance meet pki-cross-domain-profile-draft-01.doc
requirements?	
Owner: Rick Randall	
Status: Open	
Assigned: 12 Jul 2004	
Due: ---	
Comments:
Prateek Mishra 2004-07-12 21:47 GMT
CHeck conformance document to see if it captures the desired functionality
described in this document.	

  _____  

#0176: Provide sequence diagrams for profiles	
Owner: Jeff Hodges	
Status: Open	
Assigned: 23 Jun 2004	
Due: ---	
Comments:
Rob Philpott 2004-06-23 20:14 GMT
as discussed at F2F #5.

Diagram for BAP sent to list.

Rob Philpott 2004-07-23 17:03 GMT
20-July: Jeff - Will finish this week.	

  _____  

#0175: Add Security Context to glossary	
Owner: Jeff Hodges	
Status: Open	
Assigned: 23 Jun 2004	
Due: ---	
Comments:
Rob Philpott 2004-06-23 20:12 GMT
as discussed at F2F #5

Rob Philpott 2004-07-23 17:04 GMT
20-July: Jeff - Will finish this week.	

  _____  

#0166: Investigate use of Wiki from teh web site	
Owner: Scott Cantor	
Status: Open	
Assigned: 22 Jun 2004	
Due: ---	
Comments:
Rob Philpott 2004-06-22 16:40 GMT
Scott will investigate the establishment of a wiki for SSTC use to be linked
from the SSTC web site.	

  _____  

#0163: Need process for submission of profiles/authn context classes, etc.

Owner: Rob Philpott	
Status: Open	
Assigned: 22 Jun 2004	
Due: ---	
Comments:
Rob Philpott 2004-06-22 16:29 GMT
On the web site, we need to state what the process is for submitting and
dealing with additional authn context classes, new profile documents, etc.

Rob Philpott 2004-06-23 16:03 GMT
Note that this is different from AI 164 for SCott and John K to propose text
within the spec documents that points to the web site.	

  _____  

#0160: Separate Privacy concerns language from Element/Attribute
descriptions	
Owner: Prateek Mishra	
Status: Open	
Assigned: 30 Apr 2004	
Due: ---	
Comments:
Prateek Mishra 2004-04-30 18:14 GMT
Jeff H - We need to highlight privacy considerations related to core, could
be notes in core, could be section. 
*** AI: Prateek - will generate list potential changes from core

Rob Philpott 2004-07-23 17:05 GMT
20-July: Still open. Eve: Note that the explanation of constraints on
session indexes now includes a rationale along these lines.	

  _____  

#0158: Propose changes to definition of Federation in glossary	
Owner: Prateek Mishra	
Status: Open	
Assigned: 30 Apr 2004	
Due: ---	
Comments:
Rob Philpott 2004-07-23 17:05 GMT
20-July: Still open. Prateek will send thoughts to the list.	

  _____  

#0157: Define Binding and Profile in Glossary	
Owner: Jeff Hodges	
Status: Open	
Assigned: 30 Apr 2004	
Due: ---	
Comments:
Prateek Mishra 2004-04-30 18:10 GMT
o "atomic unit of interoperability" proposed	

  _____  

#0144: Explain optional subject decision	
Owner: Eve Maler	
Status: Open	
Assigned: 29 Apr 2004	
Due: ---	
Comments:
Prateek Mishra 2004-04-29 21:51 GMT
*** AI: Eve: Optional subject implemented in core spec prose. Schema shows
that subject is optional. 

o Eve: Has wanted to create a rationale for some of the decisions made on
spec. Decision on subject less statements is a good example of what needs to
be documented. Making an explicit design decision that is not really
explicit on. By choosing to add prose to core spec we're making a stealth
abstract profile (generic design decision) that applies to all explicit
profiles. 

o Scott: data model (design) decision to require subjects in all SAML
statements.

Rob Philpott 2004-07-20 02:05 GMT
13-Jul con-call minutes note that the issue should be closed. and that Eve
"may work on commentary".

Rob Philpott 2004-07-23 17:02 GMT
20July con-call:
Eve: The thought here was that we may have an optional post-V2.1 deliverable
that explains the "XML rationales" for various things. 

JohnK: But there are selected places in the actual specs where it would be
helpful; he has suggested these. Eve: Let's treat these comments one by one,
then.	

  _____  

#0125: Propose language to explain that AuthNResponse may contain attribute
statements	
Owner: Prateek Mishra	
Status: Open	
Assigned: 16 Feb 2004	
Due: ---	
Comments:
Prateek Mishra 2004-02-16 14:46 GMT
Easy to do but needs proposal on validity of assertion life-times as well.


  _____  

#0123: Obtain MIME type registration for HTTP lookup of SAML	
Owner: Jeff Hodges	
Status: Open	
 
 
 
 
 
 
 


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