Yes. Microsoft provided some technical details at:

   http://support.microsoft.com/kb/317611

The issue has potential impact to Network Nodes that meet all the following conditions:

1. The node is based on the .NET 1.1 platforms.

2. The node performs document validations using the .NET XmlValidatingReader.

3. The node supports new dataflows that use the Shared Schema Component 2.0.

We believe that only a few nodes may fail into this category. But if your node does, you may either:

1. Upgrade to .NET 2.0 and use XmlTextReader with XmlReaderSettings for XML schema validations.

2. Temporarily disable validation of document for the dataflow that uses SCC 2.0 .

3. Uses the Exchange Network QA server (https://tools.epacdxnode.net) and services for XML validation.

to get around the chameleon namespace issue.

Thanks,

Yunhao