Real-time Transport Protocol: Revision history


For any version listed below, click on its date to view it. For more help, see Help:Page history and Help:Edit summary. (cur) = difference from current version, (prev) = difference from preceding version, m = minor edit, → = section edit, ← = automatic edit summary

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)

13 August 2024

8 July 2024

26 April 2024

3 February 2024

29 November 2023

25 November 2023

16 November 2023

12 November 2023

13 October 2023

14 August 2023

10 July 2023

5 July 2023

7 June 2023

16 May 2023

  • curprev 07:1607:16, 16 May 20231AmNobody24 talk contribsm 19,504 bytes −14,026 Rollback edit(s) by 2402:3A80:19E6:E933:0:0:0:2 (talk): Not providing a reliable source (RW 16.1) undo Tags: RW Rollback
  • curprev 06:4406:44, 16 May 20232402:3a80:19e6:e933::2 talk 33,530 bytes +84 →‎External links: "RTP". Network Protocols Handbook. Javvin Technologies. 2005. ISBN 978-0-9740945-2-6 undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 06:4306:43, 16 May 20232402:3a80:19e6:e933::2 talk 33,446 bytes +1,870 Wright, Gavin. "What is the Real-time Transport Protocol (RTP)?". TechTarget. Retrieved 2022-11-10. Perkins 2003. Daniel Hardy (2002). Network. De Boeck Université. p. 298. Perkins 2003, p. 55 Perkins 2003, p. 46 RFC 4571 Farrel, Adrian (2004). The Internet and its protocols. Morgan Kaufmann. p. 363. ISBN 978-1-55860-913-6. Ozaktas, Haldun M.; Levent Onural (2007). THREE-DIMENSIONAL TELEVISION. Springer. p. 356. ISBN 978-3-540-72531-2. Hogg, Scott. "What About Stream Control Transmiss... undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 06:4306:43, 16 May 20232402:3a80:19e6:e933::2 talk 31,576 bytes +304 →‎Notes: Bits are ordered most significant to least significant; bit offset 0 is the most significant bit of the first octet. Octets are transmitted in network order. Bit transmission order is medium dependent. RFC 7273 provides a means for signalling the relationship between media clocks of different streams. undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 06:4206:42, 16 May 20232402:3a80:19e6:e933::2 talk 31,272 bytes +1,010 →‎Standards documents: RFC 3550, Standard 64, RTP: A Transport Protocol for Real-Time Applications RFC 3551, Standard 65, RTP Profile for Audio and Video Conferences with Minimal Control RFC 4855, Media Type Registration of RTP Payload Formats RFC 4856, Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences RFC 7656, A Taxonomy of Semantics and Mechanisms for Real-Time Transport Protocol (RTP) Sources RFC 3190, RTP Payload Format for 12-bit DAT Audio a... undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 06:4206:42, 16 May 20232402:3a80:19e6:e933::2 talk 30,262 bytes +811 →‎Application design: A functional multimedia application requires other protocols and standards used in conjunction with RTP. Protocols such as SIP, Jingle, RTSP, H.225 and H.245 are used for session initiation, control and termination. Other standards, such as H.264, MPEG and H.263, are used for encoding the payload data as specified by the applicable RTP profile.[26] An RTP sender captures the multimedia data, then encodes, frames and transmits it as RTP packets with appropriate timesta... undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 06:4106:41, 16 May 20232402:3a80:19e6:e933::2 talk 29,451 bytes +3,556 →‎Packet header: RTP packets are created at the application layer and handed to the transport layer for delivery. Each unit of RTP media data created by an application begins with the RTP packet header. RTP packet header Offsets Octet 0 1 2 3 Octet Bit [a] 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 0 0 Version P X CC M PT Sequence number 4 32 Timestamp 8 64 SSRC identifier 12 96 CSRC identifiers ... 12+4×CC 96+32×CC Profile-specific extension head... undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 06:4006:40, 16 May 20232402:3a80:19e6:e933::2 talk 25,895 bytes +1,655 →‎Profiles and payload formats: RTP is designed to carry a multitude of multimedia formats, which permits the development of new formats without revising the RTP standard. To this end, the information required by a specific application of the protocol is not included in the generic RTP header. For each class of application (e.g., audio, video), RTP defines a profile and associated payload formats.[10] Every instantiation of RTP in a particular application requires a profile and payload form... undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 06:3906:39, 16 May 20232402:3a80:19e6:e933::2 talk 24,240 bytes +3,684 →‎Overview: The Internet Engineering Task Force (IETF) began developing RTP starting in 1992, along with the Session Announcement Protocol (SAP), the Session Description Protocol (SDP), and the Session Initiation Protocol (SIP).[2][page needed] RTP is designed for end-to-end, real-time transfer of streaming media. The protocol provides facilities for jitter compensation and detection of packet loss and out-of-order delivery, which are common especially during UDP transmissions on an IP net... undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 06:3806:38, 16 May 20232402:3a80:19e6:e933::2 talk 20,556 bytes +1,052 The Real-time Transport Protocol (RTP) is a network protocol for delivering audio and video over IP networks. RTP is used in communication and entertainment systems that involve streaming media, such as telephony, video teleconference applications including WebRTC, television services and web-based push-to-talk features. RTP typically runs over User Datagram Protocol (UDP). RTP is used in conjunction with the RTP Control Protocol (RTCP). While RTP carries the media streams (e.g., audio and v... undo Tags: Manual revert Reverted Mobile edit Mobile web edit

15 May 2023

12 May 2023

  • curprev 03:5403:54, 12 May 2023Nathan2055 talk contribsm 19,504 bytes −2,015 Reverted edits by 2402:3A80:19EC:999:0:0:0:2 (talk) to last version by Mtmoore321 undo Tags: Rollback Reverted
  • curprev 03:2703:27, 12 May 20232402:3a80:19ec:999::2 talk 21,519 bytes +305 →‎Notes: Bits are ordered most significant to least significant; bit offset 0 is the most significant bit of the first octet. Octets are transmitted in network order. Bit transmission order is medium dependent. RFC 7273 provides a means for signalling the relationship between media clocks of different streams. undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 03:2203:22, 12 May 20232402:3a80:19ec:999::2 talk 21,214 bytes +658 →‎Application design: A functional multimedia application requires other protocols and standards used in conjunction with RTP. Protocols such as SIP, Jingle, RTSP, H.225 and H.245 are used for session initiation, control and termination. Other standards, such as H.264, MPEG and H.263, are used for encoding the payload data as specified by the applicable RTP profile.[26] An RTP sender captures the multimedia data, then encodes, frames and transmits it as RTP packets with appropriate timesta... undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 03:1903:19, 12 May 20232402:3a80:19ec:999::2 talk 20,556 bytes +1,052 The Real-time Transport Protocol (RTP) is a network protocol for delivering audio and video over IP networks. RTP is used in communication and entertainment systems that involve streaming media, such as telephony, video teleconference applications including WebRTC, television services and web-based push-to-talk features. RTP typically runs over User Datagram Protocol (UDP). RTP is used in conjunction with the RTP Control Protocol (RTCP). While RTP carries the media streams (e.g., audio and v... undo Tags: Reverted Mobile edit Mobile web edit

16 February 2023

23 December 2022

24 November 2022

22 November 2022

10 November 2022

28 May 2022

25 May 2022

24 December 2021

16 December 2021

19 November 2021

1 November 2021

5 October 2021

22 September 2021

30 April 2021

19 April 2021

21 March 2021

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)