3.1.5.4 Receiving an RTP packet
The client MUST process the RTP packet in accordance with the rules in [DLNA] guideline 7.4.85.
The SSRC field in the RTP packet header SHOULD be mapped to the stream that it belongs to using the mapping provided by the Ssrc-list variable. If the value of the SSRC field cannot be found in the Ssrc-list variable, the RTP packet SHOULD be discarded and no further processing done on the packet.
If an RTP packet contains the ASF Payload Extension System extension specified in section 2.2.1.1 and the Extension-info variable contains information pertaining to the same stream that the RTP packet belongs to, then the client SHOULD parse the ASF Payload Extension System extension.
The RTP packet, and any Payload Extension System data extracted from the RTP packet, SHOULD be made available to the higher layer.
The client MUST now continue with standard RTSP and RTP protocol usage. Standard RTSP and RTP protocol usage involves processing additional RTSP responses, processing ANNOUNCE requests, and processing RTP packets and RTCP packets, as specified in [DLNA] and [RFC2326]. The following Microsoft Extensions apply:
For any RTSP response that is received, the rules in section 3.1.5.3 MUST be followed.
When RTP packets are received, the rules in the current section MUST be followed.
If an ANNOUNCE request is received, the rules in section 3.1.5.5 MUST be followed.
The client MUST also be prepared for a higher layer to request a DLNA Media Operation, as specified in section 3.1.4.3.