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] | [Elist Home]


Subject: [security-services] Bindings and Profiles errata


  1. Line 258: s/Section 3.1.2.2/Section 3.1.3.2/
  2. Line 263: s/Section 3.1.2.3/Section 3.1.3.3/
  3. Line 267: s/Section 3.1.2.4/Section 3.1.3.4/
  4. Line 291: The section number is not bolded as are all other section numbers.
  5. Section 5.3: Even though it isn't explicitly stated, I have been assuming that the "...:cm:artifact-01" refers to a type 1 artifact.  If so, doesn't there need to be a corresponding confirmation method identifier for "...:cm:artifact-02"?  Is there really a need to distinguish the artifact types (i.e. "just use "...:cm:artifact")?  We should also be explicit as to whether providing the actual artifact in the ConfirmationData is required, optional, or not permitted - Which is it?

 

Rob Philpott
RSA Security Inc.
The Most Trusted Name in e-Security
Tel: 781-515-7115
Mobile: 617-510-0893
Fax: 781-515-7020
mailto:rphilpott@rsasecurity.com

 



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


Powered by eList eXpress LLC