Protokol Transpor Waktu Nyata: Perbedaan antara revisi
Konten dihapus Konten ditambahkan
Rescuing 0 sources and tagging 1 as dead.) #IABot (v2.0.9.3 |
→Packet Header RTP: replace 404 link into new link with a good article and same topic Tag: Dikembalikan kemungkinan spam pranala VisualEditor |
||
Baris 54:
* '''PT (Payload Type)''': (7 bits) Indicates the format of the payload and determines its interpretation by the application. This is specified by an RTP profile. For example, see ''RTP Profile for audio and video conferences with minimal control'' (RFC 3551).<ref>{{harvnb|Perkins|2003|p=59}}</ref>
* '''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.<ref name="peterson_432">Peterson, p.[http://books.google.com/books?id=zGVVuO-6w3IC&pg=PA432 432]{{Pranala mati|date=Februari 2023 |bot=InternetArchiveBot |fix-attempted=yes }}</ref> According to RFC 3550, the initial value of the sequence number should be random to make [[known-plaintext attack]]s on [[encryption]] more difficult.<ref name=RFC3550/>{{rp|13}} RTP provides no guarantee of delivery, but the presence of sequence numbers makes it possible to detect missing packets.<ref name="Hardy_298"/>
* '''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 [https://rtprajahoki89.live/ RTP] profile for an application.<ref name="peterson_432"/>
* '''SSRC''': (32 bits) Synchronization source identifier uniquely identifies the source of a stream. The synchronization sources within the same RTP session will be unique.<ref name=RFC3550/>{{rp|15}}
* '''CSRC''': (32 bits each) Contributing source IDs enumerate contributing sources to a stream which has been generated from multiple sources.<ref name=RFC3550/>{{rp|15}}
| |||