SwA Interop Scenarios

All,

Right now I am planning three simple interop scenarios for the SwA profile.
Right now I am leaving the headers out of scope until we decide on how to
handle them exactly.

I am proposing the following three scenarios. Please let me know if you have
any comments or concerns about these. These are a good starting point and I
anticipate we will add more variables based on demand:

Scenario #1: Attachment Signature where the attachment content type is fixed
at image/jpeg and the reference mechanism is Content-Id. The signature will
be based on an X.509 certificate

Scenario #2: Attachment Encryption where the attachment content type is
fixed at image/jpeg using a shared secret for encryption, which is wrapped
with a public key. Content-Id is used for the reference mechanism.

Scenario #3: Attachment Signature + Encryption where the content type is
fixed at text/xml. Similar mechanisms as above for keys and algorithms.

Regards,

Blake