184.108.40.206 Receiving a Data Packet Containing an ASF File Header
If the value of the UDP-Selected variable is 0, the client MUST perform the steps in section 220.127.116.11. The client MUST verify that the Data packet contains an ASF file header (as specified in section 2.2.2) and that it adheres to the syntax specified in section 2.2.2. If the packet does not adhere to the syntax, the client SHOULD treat this as an error.
The client MUST accumulate the ASF file header data in the Payload field until it receives a Data packet in which the value AFFlags field is 0x08 or 0x0C.
If the client does not receive a Data packet in which the AFFlags field value is 0x08 or 0x0C, or if a Data packet that contains part of the ASF file header is still missing, which can be determined by inspecting the LocationId field of the Data packets, then the client MUST wait for another Data packet that contains an ASF file header to be received. Then it MUST process the rules (as specified in section 18.104.22.168) again.
Otherwise, the value of the State variable in the abstract data model MUST be set to READY, and if the Header timer is running, it MUST be stopped.
The ASF file header MUST be reassembled from the Payload field of multiple Data packets, if necessary, and SHOULD be delivered to the higher layer.
If the value of the UDP-Selected variable is 0, the client MUST wait for a LinkMacToViewerPing message.