This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3952 - Change optional example from MTOM to security (Guidelines and Primer)
Summary: Change optional example from MTOM to security (Guidelines and Primer)
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Primer (show other bugs)
Version: FPWD
Hardware: Macintosh All
: P2 normal
Target Milestone: ---
Assignee: Frederick Hirsch
QA Contact: Web Services Policy WG QA List
Depends on:
Reported: 2006-11-04 16:01 UTC by Frederick Hirsch
Modified: 2006-12-06 17:52 UTC (History)
0 users

See Also:


Description Frederick Hirsch 2006-11-04 16:01:41 UTC
Target: Guidelines, primer


MTOM is a very bad example for optionality since it raises ambiguities depending on message flow. Best practices might suggest using different endpoints for with and without MTOM. Reason is that MTOM assertion mandates usage of MTOM on both requests and responses, so request without MTOM is ambiguous, is it a message that wouldn't naturally use MTOM, is it in error, or does it signal desire not to use MTOM.

Change to example using WS-SecurityPolicy, for example that messages optionally may need timestamp using Timestamp assertion.

Test: review guidelines and primer.
Comment 1 Daniel Roth 2006-12-06 17:52:18 UTC
Proposal updated as attached to
See resolution at