Top Qs
Timeline
Chat
Perspective

RTP payload formats

Multimedia information signaling From Wikipedia, the free encyclopedia

Remove ads

The Real-time Transport Protocol (RTP) specifies a general-purpose data format and network protocol for transmitting digital media streams on Internet Protocol (IP) networks. The details of media encoding, such as signal sampling rate, frame size and timing, are specified in an RTP payload format. The format parameters of the RTP payload are typically communicated between transmission endpoints with the Session Description Protocol (SDP), but other protocols, such as the Extensible Messaging and Presence Protocol (XMPP) may be used.

Remove ads

Payload types and formats

The technical parameters of payload formats for audio and video streams are standardised. The standard also describes the process of registering new payload types with IANA.

  • RFC 3550 – RTP: A Transport Protocol for Real-Time Applications,[1] Internet Standard 64.
  • RFC 3551 – RTP Profile for Audio and Video Conferences with Minimal Control,[2] Internet Standard 65.
  • RFC 3611 – RTP Control Protocol Extended Reports (RTCP XR),[3] Proposed Standard.
  • RFC 4856 – Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences,[4] Proposed Standard.
Remove ads

Text messaging payload types

Payload formats and types for text messaging are defined in the following specifications:

  • RFC 4103 – RTP Payload for Text Conversation,[5] Proposed Standard. Obsoletes RFC 2793. Updated by RFC 9071.
  • RFC 9071 – RTP-Mixer Formatting of Multiparty Real-Time Text,[6] Proposed Standard.

MIDI payload types

Payload formats and types for MIDI are defined in the following specifications:

Audio and video payload types

Summarize
Perspective

Payload formats and types for audio and video are defined in the following specifications:

  • RFC 2029 – RTP Payload Format of Sun's CellB Video Encoding,[9] Proposed Standard.
  • RFC 2190 – RTP Payload Format for H.263 Video Streams,[10] Historic.
  • RFC 2198 – RTP Payload for Redundant Audio Data,[11] Proposed Standard.
  • RFC 2250 – RTP Payload Format for MPEG1/MPEG2 Video,[12] Proposed Standard.
  • RFC 2343 – RTP Payload Format for Bundled MPEG,[13] Experimental.
  • RFC 2435 – RTP Payload Format for JPEG-compressed Video,[14] Proposed Standard.
  • RFC 2586 – The Audio/L16 MIME content type,[15] Informational.
  • RFC 2658 – RTP Payload Format for PureVoice(tm) Audio,[16] Proposed Standard.
  • RFC 3190 – RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio,[17] Proposed Standard.
  • RFC 3389 – Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN),[18] Proposed Standard.
  • RFC 3497 – RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M Video,[19] Informational.
  • RFC 3640 – RTP Payload Format for Transport of MPEG-4 Elementary Streams,[20] Proposed Standard.
  • RFC 3952 – Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) Speech,[21] Experimental.
  • RFC 4175 – RTP Payload Format for Uncompressed Video,[22] Proposed Standard.
  • RFC 4184 – RTP Payload Format for AC-3 Audio,[23] Proposed Standard.
  • RFC 4352 – RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio Codec,[24] Proposed Standard.
  • RFC 4587 – RTP Payload Format for H.261 Video Streams,[25] Proposed Standard.
  • RFC 4598 – Real-time Transport Protocol (RTP) Payload Format for Enhanced AC-3 (E-AC-3) Audio,[26] Proposed Standard.
  • RFC 4629 – RTP Payload Format for ITU-T Rec. H.263 Video,[27] Proposed Standard.
  • RFC 4733 – RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals,[28] Proposed Standard.
  • RFC 4749 – RTP Payload Format for the G.729.1 Audio Codec,[29] Proposed Standard.
  • RFC 4788 – Enhancements to RTP Payload Formats for EVRC Family Codecs,[30] Proposed Standard.
  • RFC 4867 – RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs,[31] Proposed Standard.
  • RFC 5188 – RTP Payload Format for the Enhanced Variable Rate Wideband Codec (EVRC-WB) and the Media Subtype Updates for EVRC-B Codec,[32] Proposed Standard.
  • RFC 5215 – RTP Payload Format for Vorbis Encoded Audio,[33] Proposed Standard.
  • RFC 5371 – RTP Payload Format for JPEG 2000 Video Streams,[34] Proposed Standard.
  • RFC 5391 – RTP Payload Format for ITU-T Recommendation G.711.1,[35] Proposed Standard.
  • RFC 5404 – RTP Payload Format for G.719,[36] Proposed Standard.
  • RFC 5574 – RTP Payload Format for the Speex Codec,[37] Proposed Standard.
  • RFC 5577 – RTP Payload Format for ITU-T Recommendation G.722.1,[38] Proposed Standard.
  • RFC 5584 – RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) Family,[39] Proposed Standard.
  • RFC 5686 – RTP Payload Format for mU-law EMbedded Codec for Low-delay IP Communication (UEMCLIP) Speech Codec,[40] Proposed Standard.
  • RFC 5993 – RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR),[41] Proposed Standard.
  • RFC 6184 – RTP Payload Format for H.264 Video,[42] Proposed Standard.
  • RFC 6190 – RTP Payload Format for Scalable Video Coding,[43] Proposed Standard.
  • RFC 6416 – RTP Payload Format for MPEG-4 Audio/Visual Streams,[44] Proposed Standard.
  • RFC 6469 – RTP Payload Format for DV (IEC 61834) Video,[45] Proposed Standard.
  • RFC 7310 – RTP Payload Format for Standard apt-X and Enhanced apt-X Codecs,[46] Proposed Standard.
  • RFC 7587 – RTP Payload Format for the Opus Speech and Audio Codec,[47] Proposed Standard.
  • RFC 7741 – RTP Payload Format for VP8 Video,[48] Proposed Standard.
  • RFC 7798 – RTP Payload Format for High Efficiency Video Coding (HEVC),[49] Proposed Standard.
  • RFC 9134 – RTP Payload Format for ISO/IEC 21122 (JPEG XS),[50] Proposed Standard.
  • RFC 9607 – RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec,[51] Proposed Standard.
  • RFC 9628 – RTP Payload Format for VP9 Video,[52] Proposed Standard.

Payload identifiers 96–127 are used for payloads defined dynamically during a session. It is recommended to dynamically assign port numbers, although port numbers 5004 and 5005 have been registered for use of the profile when a dynamically assigned port is not required.

Applications should always support PCMU (payload type 0). Previously, DVI4 (payload type 5) was also recommended, but this was removed in 2013.[53]

More information Payload type (PT), Name ...
  1. [N 1]
    The "clock rate" is the rate at which the timestamp in the RTP header is incremented, which need not be the same as the codec's sampling rate. For instance, video codecs typically use a clock rate of 90000 so their frames can be more precisely aligned with the RTCP NTP timestamp, even though video sampling rates are typically in the range of 1–60 samples per second.
  2. [N 2]
    Although the sampling rate for G.722 is 16000, its clock rate is 8000 to remain backwards compatible with RFC 1890, which incorrectly used this value.[2]: 14 
  3. [N 3]
    Because Opus can change sampling rates dynamically, its clock rate is fixed at 48000, even when the codec will be operated at a lower sampling rate. The maxplaybackrate and sprop-maxcapturerate parameters in SDP can be used to indicate hints/preferences about the maximum sampling rate to encode/decode.
  4. [N 4]
    For aptX, the packetization interval must be rounded down to the nearest packet interval that can contain an integer number of samples. So at sampling rates of 11025, 22050, or 44100, a packetization rate of "4" is rounded down to 3.99.
Remove ads

See also

References

External links

Loading content...
Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.

Remove ads