RE: [wss] Additional SwA Interop Issues

["Blake Dournaee" <blake@sarvega.com>]

Paul –

 

I believe that Frederick has already added text to the latest draft of SwA Profile for issue #1

 

For issue #2, this was a typo in the examples used in the SwA Profile Interoperability Scenarios. The Id for <EncryptedData> should not have had a wsu: prefix. I don’t believe we need clarifying text unless others disagree with me.

 

Thanks,

 

Blake

 

---

From: Paul Cotton [mailto:pcotton@microsoft.com]
Sent: Tuesday, November 16, 2004 6:43 PM
To: Blake Dournaee
Cc: wss@lists.oasis-open.org
Subject: RE: [wss] Additional SwA Interop Issues

 

> 1.  The Specification of MimeType attribute is optional when content as well as headers of the attachment are being encrypted. The phrasing in the current draft of SwA Profile makes it seem that MimeType is required for either transforms (Section 4.4.2, Step 4)

 

Can you propose exact replacement text that is acceptable to the Interop participants to fix this issue?

 

 

>2. The Id Attribute for <EncrryptedData> should not have a namespace qualifier (e.g. “wsu”) because it falls under the XML Encryption spec and not WS-Security

 

Does this mistake occur in any examples in the specification or was just an error in one of the implementations?  If the latter I wonder what if anything we need to do in the spec?  Again is there specific additional text that you would propose?

 

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Nepean, Ontario K2E 6A3
Tel: (613) 225-5445 Fax: (425) 936-7329
mailto:pcotton@microsoft.com

 

---

From: Blake Dournaee [mailto:blake@sarvega.com]
Sent: November 16, 2004 5:33 PM
To: wss@lists.oasis-open.org
Subject: [wss] Additional SwA Interop Issues

 

All,

 

Here are two more minor issues that we encountered during the first interoperability event:

 

1. The Specification of MimeType attribute is optional when content as well as headers of the attachment are being encrypted. The phrasing in the current draft of SwA Profile makes it seem that MimeType is required for either transforms (Section 4.4.2, Step 4)
2. The Id Attribute for <EncrryptedData> should not have a namespace qualifier (e.g. “wsu”) because it falls under the XML Encryption spec and not WS-Security

 

Thanks,

 

Blake Dournaee

Senior Security Architect

Sarvega, Inc.