<Li> Sequence number: (16 bits) The sequence number is incremented by one for each RTP data packet sent and is to be used by the receiver to detect packet loss and to restore packet sequence . The RTP does not specify any action on packet loss; it is left to the application to take appropriate action . For example, video applications may play the last known frame in place of the missing frame . According to RFC 3550, the initial value of the sequence number should be random to make known - plaintext attacks on encryption more difficult . RTP provides no guarantee of delivery, but the presence of sequence numbers makes it possible to detect missing packets . </Li> <Li> Timestamp: (32 bits) Used to enable the receiver to play back the received samples at appropriate intervals . When several media streams are present, the timestamps are independent in each stream, and may not be relied upon for media synchronization . The granularity of the timing is application specific . For example, an audio application that samples data once every 125 μs (8 kHz, a common sample rate in digital telephony) would use that value as its clock resolution . The clock granularity is one of the details that is specified in the RTP profile for an application . </Li> <Li> SSRC: (32 bits) Synchronization source identifier uniquely identifies the source of a stream . The synchronization sources within the same RTP session will be unique . </Li> <Li> CSRC: (32 bits each) Contributing source IDs enumerate contributing sources to a stream which has been generated from multiple sources . </Li>

Which of the following is the common protocol for network transmissions