3.2.5.1.3 De-Serializing the Message Content

An implementation MUST use the Content Type retrieved from the message to identify the serialization format of the message content as specified in the following table.

Content Type	Serialization format specification	Mapping section
Binary format identifier	Binary format as specified in [MS-NRBF]	Section 3.1.5.1
SOAP format identifier	SOAP format as specified in [SOAP1.1]	Section 3.1.5.2

The message content MUST be de-serialized to produce the Server Type or Server Interface name, Remote Method name, Input Arguments, Call Context, and the Method Signature. If the message content does not conform to the structure specified in the appropriate serialization format specification (as specified in the preceding table) or if mapping (as specified in the preceding table) the data from the serialization stream to the Remoting Data Model resulted in an error, then a SerializationException instance MUST be constructed as specified in Constructing SerializationException (section 3.2.5.1.7.1) and the Exception MUST be returned to the client. The Exception message SHOULD convey the nature of the structural error. If the Data Values in the message content contain ObjRefs they MUST be resolved as specified in Resolving Object Reference (section 3.1.5.3).