New Issue: Purpose behind dup requirements?

[Scott de Deugd <dedeugd@us.ibm.com>]

Please defer discussions on this issue until a time this issue is accepted
and is assigned a number. 
  
Description: 
  
Document: DPWS Version 1.0 
Line number:  Line 245
Owner: Scott de Deugd 
  

Description: 
Editorial:
Section 3.6 says:
R0036: A SERVICE MAY reject a MIME SOAP
ENVELOPE if the Content-Transfer-Encoding header field mechanism of any
MIME part is not "binary".
R0037: A SERVICE MUST NOT send a MIME SOAP
ENVELOPE unless the Content-Transfer-Encoding header field mechanism of
every MIME part is "binary"

There are several requirements like this.
 Is the purpose behind this to allow a service to have more flexibility
than the client, which might be constrained?  
If so we should probably say this up front
so people don't view this as an inconsistency.


Proposed Resolution (changes in red):
Clarify