Proposed text for Base64-specific optimization

At the f2f I took an action item to propose text that would more clearly
indicate that our optimizations are, at least for the moment, only for data
that appears in the infoset as base64Binary.  The attached html file has
proposed changes, highlighted as marked revisions (blue).

In the intersest of full disclosure, there are a few other editorial
changes in this version.  I had started hacking on these in my role as an
MTOM editor on the plane to France, and decided to leave them in this copy.
I think it will be clear which changes are related specifically to my
action and which don't.  The ones that don't have no official status.
Insofar as they are indeed editorial I may propose to the other editors
that we adopt some, but as always comments are welcome.  If any concerns
are expressed by WG members about any of these we will definitely hold off.

Bottom line:  the majority are base64-related, and those are the ones you
should focus on.  Comments on the others are welcome.

I notice in the agenda for tomorrow that Gudge is listed as co-actionee on
this.  I hadn't realized that, and he hasn't seen this.  So, he may or may
not agree.  Finally, the action is listed in relation to issue 432, but
this text deals only with the part of 432 that has specifically to do with
base64, which I believe was the scope of my action.  I believe my action is
thus fulfilled, but I don't think we can close 432 based on this text
alone.  Thanks!

(See attached file: SOAP Message Transmission Optimization Mechanism w Noah
Edits for Issue 432.htm)

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------