RE: [wss] SwA profile Issue 364 action for TC members

["Brian LaMacchia" <bal@exchange.microsoft.com>]

What do you believe should be the mandatory-to-implement processing
behavior for XML attachments?  It sounds like you're advocating leaving
the behavior unspecified and thus application-dependent.  That's not
going to get you interoperability.  The SwA profile needs to specify a
single, interoperable, mandatory-to-implement behavior for processing
XML attachments that does not depend on any knowledge about the behavior
of intermediaries.  A further profile could certainly say something like
the sender has the option of using an alternative canonicalization
algorithm if the sender knows the behavior of all the intermediaries
that are going to touch the message, but that can't be your
mandatory-to-implement-for-interop behavior.

					--bal 

-----Original Message-----
From: Rich Salz [mailto:rsalz@datapower.com] 
Sent: Thursday, May 05, 2005 10:24 AM
To: Frederick.Hirsch@nokia.com
Cc: wss@lists.oasis-open.org
Subject: Re: [wss] SwA profile Issue 364 action for TC members

An application that knows how its messages are being passed around can 
either avoid the cost of canonicalization, or avoid the risk of message 
modification as appropriate.  An application that doesn't know can 
always add a c14n transform.

More explicit "rules" seem like a matter left to profiling.

	/r$

-- 
Rich Salz, Chief Security Architect
DataPower Technology                           http://www.datapower.com
XS40 XML Security Gateway   http://www.datapower.com/products/xs40.html

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php