2013-04-19 Registry closed; see , Section 3 The RFC "RTP Profile for Audio and Video Conferences with Minimal Control" specifies an initial set "payload types". This list maintains and extends that list. 0 PCMU A 8000 1 1 Reserved 2 Reserved 3 GSM A 8000 1 4 G723 A 8000 1 5 DVI4 A 8000 1 6 DVI4 A 16000 1 7 LPC A 8000 1 8 PCMA A 8000 1 9 G722 A 8000 1 10 L16 A 44100 2 11 L16 A 44100 1 12 QCELP A 8000 1 13 CN A 8000 1 14 MPA A 90000 15 G728 A 8000 1 16 DVI4 A 11025 1 17 DVI4 A 22050 1 18 G729 A 8000 1 19 Reserved A 20 Unassigned A 21 Unassigned A 22 Unassigned A 23 Unassigned A 24 Unassigned V 25 CelB V 90000 26 JPEG V 90000 27 Unassigned V 28 nv V 90000 29 Unassigned V 30 Unassigned V 31 H261 V 90000 32 MPV V 90000 33 MP2T AV 90000 34 H263 V 90000 35-71 Unassigned ? 72-76 Reserved for RTCP conflict avoidance 77-95 Unassigned ? 96-127 dynamic ? Standards Action Process or expert approval Steve Casner In addition to the RTP payload formats (encodings) listed in the RTP Payload Types table, there are additional payload formats that do not have static RTP payload types assigned but instead use dynamic payload type number assignment. Each payload format is named by a registered media subtype as listed in the following table. As new payload formats are specified, their registered media subtypes should be added to this table. In addition, for the payload formats listed in the RTP Payload Types table above, the "encoding name" is also registered as a media subtype under the media type "audio" or "video". The clock rate and number of channels shown here are the normal values for those payload formats that have a normal value. Both type and subtype names are case-insensitive as defined in RFC4288. Registration procedures and a registration template can be found in application 1d-interleaved-parityfec application h224 4800 application parityfec application raptorfec application rtx application smpte336m application ulpfec audio 1d-interleaved-parityfec audio 32kadpcm 8000 audio ac3 audio AMR 8000 audio AMR-WB 16000 audio amr-wb+ 72000 audio atrac3 44100 audio ATRAC-ADVANCED-LOSSLESS audio atrac-x audio BV16 8000 audio BV32 16000 audio clearmode 8000 1 audio CN audio DAT12 audio dsr-es201108 audio dsr-es202050 8000 audio dsr-es202211 8000 audio dsr-es202212 8000 audio DV audio eac3 audio EVRC 8000 1 audio EVRC0 8000 1 audio EVRC1 8000 1 audio EVRCB 8000 1 audio EVRCB0 8000 1 audio EVRCB1 8000 1 audio EVRCWB audio EVRCWB0 audio EVRCWB1 audio fwdred audio g719 48000 audio G7221 16000 1 audio G726-16 8000 1 audio G726-24 8000 1 audio G726-32 8000 1 audio G726-40 8000 1 audio G729D 8000 1 audio G729E 8000 1 audio GSM-EFR 8000 1 audio L8 audio raptorfec audio RED audio rtx audio VDVI 1 audio L20 audio L24 audio MP4A-LATM audio mpa-robust 90000 audio parityfec audio SMV 8000 1 audio SMV0 8000 1 audio t140c audio t38 audio telephone-event audio tone audio DVI4 audio G722 audio G723 audio G728 audio G729 audio GSM audio L16 audio LPC audio PCMA audio PCMU audio G7291 16000 audio GSM-HR-08 8000 audio iLBC 8000 audio ip-mr_v2.5 16000 audio MPA 90000 audio mpeg4-generic audio PCMA-WB 16000 audio PCMU-WB 16000 audio QCELP audio rtp-midi audio speex audio uemclip audio ulpfec audio VMR-WB 16000 audio vorbis audio vorbis-config text 1d-interleaved-parityfec text fwdred text parityfec text raptorfec text red 1000 text rtx text t140 1000 text ulpfec video BMPEG 90000 video 1d-interleaved-parityfec video 3gpp-tt video BT656 90000 video celB video DV 90000 video H261 video H263 90000 video H263-1998 90000 video H263-2000 90000 video H264 video H264-RCDO 90000 video H264-SVC video JPEG video JPEG2000 video MP1S 90000 video MP2P 90000 video MP2T video MP4V-ES 90000 video mpeg4-generic video MPV video nv video parityfec video pointer 90000 video raptorfec video raw 90000 video rtx video SMPTE292M video ulpfec video vc1 90000 Steve Casner, Magnus Westerlund The RFC "RTP: A Transport Protocol for Real-Time Applications" specifies an initial set of "control packet types" for RTCP. This list maintains and extends that list. 1-191 Specification required or expert review 194-199 Specification required or expert review If 200-223 is fully occupied 200-223 Specification required or expert review Primary Assignments range 224-254 Specification required or expert review 0 Reserved 1-191 Unassigned 192 Reserved (Historic-FIR) 193 Reserved (Historic-NACK) 194 SMPTETC SMPTE time-code mapping 195 IJ Extended inter-arrival jitter report 196-199 Unassigned 200 SR sender report 201 RR receiver report 202 SDES source description 203 BYE goodbye 204 APP application-defined 205 RTPFB Generic RTP Feedback 206 PSFB Payload-specific 207 XR extended report 208 AVB AVB RTCP packet "Standard for Layer 3 Transport Protocol for Time Sensitive Applications in Local Area Networks." Work in progress. 209 RSI Receiver Summary Information 210 TOKEN Port Mapping 211-254 Unassigned 255 Reserved Specification Required or Expert Review The RFC "RTP: A Transport Protocol for Real-Time Applications" specifies an initial set of "item types" for the RTCP SDES control packet. This list maintains and extends that list. 0 END end of SDES list 1 CNAME canonical name 2 NAME user name 3 EMAIL user's electronic mail address 4 PHONE user's phone number 5 LOC geographic user location 6 TOOL name of application or tool 7 NOTE notice about the source 8 PRIV private extensions 9 H323-CADDR H.323 callable address 10 APSI Application Specific Identifier 11-255 Unassigned IETF Review 0 Reserved 1 Port Mapping Request 2 Port Mapping Response 3 Token Verification Request 4 Token Verification Failure 5-30 Unassigned 31 Reserved Standards Action Process or expert approval Steve Casner RTP/AVP RTP/SAVP RTP/AVPF RTP/SAVPF Specification Required 1 Generic NACK Generic negative acknowledgement 2 Reserved 3 TMMBR Temporary Maximum Media Stream Bit Rate Request 4 TMMBN Temporary Maximum Media Stream Bit Rate Notification 5 RTCP-SR-REQ RTCP Rapid Resynchronisation Request 6 RAMS Rapid Acquisition of Multicast Sessions 7 TLLEI Transport-Layer Third-Party Loss Early Indication 8 RTCP-ECN-FB RTCP ECN Feedback 9-30 Unassigned 31 Extension Reserved for future extensions Specification Required 1 PLI Picture Loss Indication 2 SLI Slice Loss Indication 3 RPSI Reference Picture Selection Indication 4 FIR Full Intra Request Command 5 TSTR Temporal-Spatial Trade-off Request 6 TSTN Temporal-Spatial Trade-off Notification 7 VBCM Video Back Channel Message 8 PSLEI Payload-Specific Third-Party Loss Early Indication 9-14 Unassigned 15 AFB Application Layer Feedback 16-30 Unassigned 31 Extension Reserved for future extensions Expert Review Magnus Westerlund, Stephen Casner For extensions defined in RFCs, the URI is recommended to be of the form urn:ietf:params:rtp-hdrext:, and the formal reference is the RFC number of the RFC documenting the extension. urn:ietf:params:rtp-hdrext:toffset Transmission Time offsets urn:ietf:params:rtp-hdrext:smpte-tc SMPTE time-code mapping urn:ietf:params:rtp-hdrext:ntp-64 Synchronisation metadata: 64-bit timestamp format IETF Audio/Video Transport Working Group urn:ietf:params:rtp-hdrext:ntp-56 Synchronisation metadata: 56-bit timestamp format IETF Audio/Video Transport Working Group urn:ietf:params:rtp-hdrext:ssrc-audio-level Audio Level urn:ietf:params:rtp-hdrext:csrc-audio-level Mixer-to-client audio level indicators urn:ietf:params:rtp-hdrext:encrypt Encrypted extension header element Specification Required 0 IPv4 Address IPv4 Feedback Target Address 1 IPv6 Address IPv6 Feedback Target Address 2 DNS Name DNS Name indicating Feedback Target Address 3 Reserved Reserved for Assignment by Standards Action 4 Loss Loss distribution 5 Jitter Jitter distribution 6 RTT Round-trip time distribution 7 Cumulative loss Cumulative loss distribution 8 Collisions SSRC Collision list 9 Reserved Reserved for Assignment by Standards Action 10 Stats General statistics 11 RTCP BW RTCP Bandwidth indication 12 Group Info RTCP Group and Average Packet size Specification Required 0 Reserved 1 RAMS Request 2 RAMS Information 3 RAMS Termination 4-254 Unassigned 255 Reserved Specification Required 0 Reserved 1 Requested Media Sender SSRC(s) 2 Min RAMS Buffer Fill Requirement 3 Max RAMS Buffer Fill Requirement 4 Max Receive Bitrate 5 Request for Preamble Only 6 Supported Enterprise Number(s) 7-30 Unassigned 31 Media Sender SSRC 32 RTP Seqnum of the First Packet 33 Earliest Multicast Join Time 34 Burst Duration 35 Max Transmit Bitrate 36-60 Unassigned 61 Extended RTP Seqnum of First Multicast Packet 62-127 Unassigned 128-254 Reserved for Private Use 255 Reserved Specification Required New response codes should be classified following the guidelines below: 1xx Informational 2xx Success 3xx Redirection 4xx RTP Receiver (RTP_Rx) Error 5xx Burst/Retransmission Source (BRS) Error 0 A private response code is included in the message 100 Parameter update for RAMS session 200 RAMS request has been accepted 201 Unicast burst has been completed 400 Invalid RAMS-R message syntax 401 Invalid min buffer requirement in RAMS-R message 402 Invalid max buffer requirement in RAMS-R message 403 Insufficient max bitrate requirement in RAMS-R message 404 Invalid RAMS-T message syntax 405 Invalid Token 500 An unspecified BRS internal error has occurred 501 BRS has insufficient bandwidth to start RAMS session 502 Burst is terminated due to network congestion 503 BRS has insufficient CPU cycles to start RAMS session 504 RAMS functionality is not available on BRS 505 RAMS functionality is not available for RTP_Rx 506 RAMS functionality is not available for the requested multicast stream 507 BRS has no valid starting point available for the requested multicast stream 508 BRS has no reference information available for the requested multicast stream 509 BRS has no RTP stream matching the requested SSRC 510 RAMS request to acquire the entire session has been denied 511 Only the preamble information is sent 512 RAMS request has been denied due to a policy Chunrong Zhu mailto:Chunrong_Zhu&ccm.jf.intel.com 1996-06 Emil Ivov mailto:emcho&jitsi.org 2011-12 Jonathan Lennox mailto:jonathan&vidyo.com 2013-02-12 Joseph Di Pol mailto:Joe.Dipol&eng.sun.com 1996-05 Unkown mailto:singer&apple.com Thomas Schierl mailto:ts&thomas-schierl.de Vineet Kumar mailto:Vineet_Kumar&ccm.jf.intel.com 1997-01