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: RE: [security-services] Bindings and Profiles errata


Rob -
Items 1-3 have already been reported by Fredrick Hirsch of Nokia and exist in the current draft of the errata document. I have added items 4 and 5.
 
Thanks,
Jahan

----------------
Jahan Moreh
Chief Security Architect
310.286.3070

-----Original Message-----
From: Philpott, Robert [mailto:rphilpott@rsasecurity.com]
Sent: Tuesday, January 21, 2003 1:55 PM
To: 'security-services@lists.oasis-open.org'
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

 

 

----------------
Jahan Moreh
Chief Security Architect
310.286.3070

-----Original Message-----
From: Jahan Moreh [mailto:jmoreh@sigaba.com]
Sent: Wednesday, January 22, 2003 3:23 PM
To: Philpott, Robert; 'security-services@lists.oasis-open.org'
Subject: RE: [security-services] Bindings and Profiles errata

Rob -
Items 1-3 have already been reported by Fredrick Hirsch of Nokia and exist in the current draft of the errata document. I have added items 4 and 5.
 
Thanks,
Jahan
 
 

----------------
Jahan Moreh
Chief Security Architect
310.286.3070

-----Original Message-----
From: Philpott, Robert [mailto:rphilpott@rsasecurity.com]
Sent: Tuesday, January 21, 2003 1:55 PM
To: 'security-services@lists.oasis-open.org'
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