[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [security-services] editorial comments summary
Below is a list of messages from the security-services and security-services-comment list that ostensibly constitute unimplemented "editorial comments". These are nominally NOT "technical issues". Hal will be issuing a new version of draft-sstc-saml-issues-xx (-09) in which he will include the "technical issues" identified since the issuance of draft-sstc-saml-issues-08 (nominally since the beginning of Last Call). Where (if) Hal's list and this list overlap, we should consider those items as ISSUES. I culled these messages from the date range of: 11-Mar-2002 back to 5-Feb-2002. I may have missed some things, if you feel you've made an editorial suggestion that never got implemented, now's the time to speak up. thanks, JeffH ----- editorial comment on core-27 (#1) http://lists.oasis-open.org/archives/security-services/200203/msg00021.html Editorial comment #2 on bindings-model-11 http://lists.oasis-open.org/archives/security-services/200203/msg00003.html Editorial comment on bindings-model-11 http://lists.oasis-open.org/archives/security-services/200202/msg00181.html RE: Missing changes to schema and core-doc http://lists.oasis-open.org/archives/security-services/200202/msg00109.html [suggestion on how to explain "Error.Receiver.ResourceNotRecognized"] Changes for Core 26 http://lists.oasis-open.org/archives/security-services/200202/msg00063.html [item (4): IPv6 (ostensibly to be applied in or around line 704 of core-27)] Text for Spec: SAML Philosophy http://lists.oasis-open.org/archives/security-services/200202/msg00041.html Status of and recommendation on SAML version info http://lists.oasis-open.org/archives/security-services/200202/msg00033.html [is this one really an ISSUE, and is it an "agreed-to but unimplemented" one?] From.. Live ISSUEs from Eve http://lists.oasis-open.org/archives/security-services/200203/msg00042.html ..we have these items.. ELM-6. Refer to URI references ELM-7. Talk about SAML authorities/responders and requesters [tho there is a related technical issue to this one in terms of changing the <StatusCode> element values of "Receiver" and "Sender" to match what's discussed in ELM-7. It's item (2) in.. Status code clarifications/cleanup http://lists.oasis-open.org/archives/security-services/200202/msg00160.html ]. ELM-10. Not discussed but a purely editorial matter; should be done. From.. SAP Comments On SAML Core-27 andBindings-11 http://lists.oasis-open.org/archives/security-services-comment/200202/msg00008.html RE: ... SAP Comme ntsOn SAML Core-27 and Bindings-11 (Hal Lockhart) http://lists.oasis-open.org/archives/security-services/200203/msg00049.html RE: ... SAP Comme ntsOn SAML Core-27 and Bindings-11 (Prateek Mishra) http://lists.oasis-open.org/archives/security-services/200203/msg00045.html ..we have these items.. SAP-3. Core Document. Line # 366. Element "AssertionID" should be "AssertionIDReference". SAP-4. [need to alter spec language to account for "Assertion(s) containing FooStatement(s)" rather than simply stating "Foo Assertion(s)"] SAP-15 (2) [see Hal's response] "subject element of authentication statements" rather than "subject element of returned assertions". See SAP-4. SAP-20 Core Document. Line # 1381. "Message Integrity" should be changed to "Assertion Integrity". SAP-21 Core Document. Line # 1433. [ #1434 s/applies /applies to/ ] SAP-23 Core Document. Line # 1622. "ActionNamespace" should be changed to "Action Namespace" SAP-25 Bindings & Profiles Doc. Line # 339. [will be Fixed in bindings-12.] SAP-26 Bindings & Profiles Doc. Line # 346. [will be Fixed in bindings-12.] --- end
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC