[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: FW: Active Issues for May 1 telecon
-----Original Message----- From: Hal Lockhart [mailto:hal.lockhart@entegrity.com] Sent: Tuesday, April 24, 2001 6:29 PM To: 'Eve L. Maler'; PATO,JOE (HP-PaloAlto,ex1) Cc: 'Jeff Hodges'; 'George_Robert_Blakley_III@tivoli.com'; 'Krishna Sankar'; 'Mishra, Prateek' Subject: Active Issues for May 1 telecon 1. Indexical Reference Problem The consensus is that there is no alternative in some environments, but we need to consider security threats carefully. There were some action items around requirements and terminology, but my sense is that we are done with this item. 2. MessageMeaning This led to general discussion of many undefined, but potentially useful definitions of terms. Eve seemed to be the main person who wanted to pursue this. 3. AuthZ Decision Assertions This is still open. Would it be better to discuss a specific design proposal or are there general issues that could profitably be discussed? 4. NoPassThruAuthnImpactsPEP2PDP (I renamed this to reflect what I think is Stephen's intent.) The decision to exclude Pass-Thru-AuthN may impact the ability to achieve PEP to PDP interoperability. Stephen to explain. 5. XMLAssertionGenerality Should be have one sort of Assertion with different contents (as current spec proposes) or a number of assertion types with codes and specified contents for each. A related issue is: should there be just one sort of assertion reference or more than one. Use of XML mechanisms, such as inheritance may be useful here. 6. Enveloped and Enveloping (and Detached) Not clear if this is a narrow technical issue about how SAML assertions get digitally signed or a broader issue about how SAML assertions relate to other, associated XML content. Those seem to me to be the top of the stack. Hal
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC