|
|
|
|
|
|
|
|
|
|
| Last Update: Sep 1, 2010
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC2029
10/1996
(6 p.)
pdf(2p)
|
M. Speer
D. Hoffman |
|
RTP Payload Format of Sun's CellB Video Encoding |
This memo describes a packetization scheme for the CellB video
encoding. The scheme proposed allows applications to transport CellB
video flows over protocols used by RTP. This document is meant for
implementors of video applications that want to use RTP and CellB.
The Cell image compression algorithm is a variable bit-rate video
coding scheme. It provides "high" quality, low bit-rate image
compression at low computational cost. The bytestream that is
produced by the Cell encoder consists of instructional codes and
information about the compressed image.
Currently, there are two versions of the Cell compression technology:
CellA and CellB. CellA is primarily designed for the encoding of
stored video intended for local display, and will not be discussed in
this memo.
CellB, derived from CellA, has been optimized for network-based video
applications. It is computationally symmetric in both encode and
decode. CellB utilizes a fixed colormap and vector quantization
techniques in the YUV color space to achieve compression.
The "video/CelB" media type has been registered in RFC3555, section 4.2.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC2190
09/1997
(12 p.)
pdf(2p)
|
C. Zhu |
|
RTP Payload Format for H.263 Video Streams |
|
This document specifies the payload format for encapsulating an H.263
bitstream in the Real-Time Transport Protocol (RTP). Three modes are
defined for the H.263 payload header. An RTP packet can use one of
the three modes for H.263 video streams depending on the desired
network packet size and H.263 encoding options employed. The shortest
H.263 payload header (mode A) supports fragmentation at Group of
Block (GOB) boundaries. The long H.263 payload headers (mode B and C)
support fragmentation at Macroblock (MB) boundaries.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC2198
09/1997
(11 p.)
pdf(2p)
|
C. Perkins
I. Kouvelas
O. Hodson
V. Hardman
M. Handley
J.C. Bolot
A. Vega-Garcia
S. Fosse-Parisis |
|
RTP Payload for Redundant Audio Data |
|
This document describes a payload format for use with the real-time
transport protocol (RTP), version 2, for encoding redundant audio
data. The primary motivation for the scheme described herein is the
development of audio conferencing tools for use with lossy packet
networks such as the Internet Mbone, although this scheme is not
limited to such applications.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC2250
01/1998
(16 p.)
pdf(2p)
|
D. Hoffman
G. Fernando
V. Goyal
M. Civanlar |
|
RTP Payload Format for MPEG1/MPEG2 Video |
This memo describes a packetization scheme for MPEG video and audio
streams. The scheme proposed can be used to transport such a video
or audio flow over the transport protocols supported by RTP. Two
approaches are described. The first is designed to support maximum
interoperability with MPEG System environments. The second is
designed to provide maximum compatibility with other RTP-encapsulated
media streams and future conference control work of the IETF.
This memo is a revision of RFC 2038, an Internet standards track
protocol. In this revision, the packet loss resilience mechanisms in
Section 3.4 were extended to include additional picture header
information required for MPEG2. A new section on security
considerations for this payload type is added.
The "video/MPV", "video/MP2T", "video/MP1S", "video/MP2P" media types have been registered in RFC3555, section 4.2.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC2343
05/1998
(8 p.)
pdf(2p)
|
M. Civanlar
G. Cash
B. Haskell |
|
RTP Payload Format for Bundled MPEG |
This document describes a payload type for bundled, MPEG-2 encoded
video and audio data that may be used with RTP, version 2. Bundling
has some advantages for this payload type particularly when it is
used for video-on-demand applications. This payload type may be used
when its advantages are important enough to sacrifice the modularity
of having separate audio and video streams.
The "video/BMPEG" media type has been registered in RFC3555, section 4.2.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC2354
06/1998
(12 p.)
pdf(2p)
|
C. Perkins
O. Hodson |
|
Options for Repair of Streaming Media |
|
This document summarizes a range of possible techniques for the
repair of continuous media streams subject to packet loss. The
techniques discussed include redundant transmission, retransmission,
interleaving and forward error correction. The range of
applicability of these techniques is noted, together with the
protocol requirements and dependencies.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC2431
10/1998
(10 p.)
pdf(2p)
|
D. Tynan |
|
RTP Payload Format for BT.656 Video Encoding |
This document specifies the RTP payload format for encapsulating ITU
Recommendation BT.656-3 video streams in the Real-Time Transport
Protocol (RTP). Each RTP packet contains all or a portion of one
scan line as defined by ITU Recommendation BT.601-5, and includes
fragmentation, decoding and positioning information.
This document describes a scheme to packetize uncompressed, studio-quality
video streams as defined by BT.656 for transport using RTP.
A BT.656 video stream is defined by ITU-R Recommendation
BT.656-3, as a means of interconnecting digital television
equipment operating on the 525-line or 625-line standards, and
complying with the 4:2:2 encoding parameters as defined in ITU-R
Recommendation BT.601-5 (formerly CCIR-601), Part A.
The "video/BT656" media type has been registered in RFC3555, section 4.2.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC2435
10/1998
(27 p.)
pdf(2p)
|
L. Berc
W. Fenner
R. Frederick
S. McCanne
P. Stewart |
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC2736
12/1999
(10 p.)
pdf(2p)
|
M. Handley
C. Perkins |
|
Guidelines for Writers of RTP Payload Format Specifications |
This document provides general guidelines aimed at assisting the
authors of RTP Payload Format specifications in deciding on good
formats. These guidelines attempt to capture some of the experience
gained with RTP as it evolved during its development.
The principles outlined in this document are applicable to almost all
data types, but are framed in examples of audio and video codecs for
clarity.
|
|
|
| |
| List |
Status: | Best Current Practice (BCP: 36) |
|
|
|
|
|
|
|
|
| | |
RFC2762
02/2000
(12 p.)
pdf(2p)
|
J. Rosenberg
H. Schulzrinne |
|
Sampling of the Group Membership in RTP |
|
In large multicast groups, the size of the group membership table
maintained by RTP (Real Time Transport Protocol) participants may
become unwieldy, particularly for embedded devices with limited
memory and processing power. This document discusses mechanisms for
sampling of this group membership table in order to reduce the memory
requirements. Several mechanisms are proposed, and the performance of
each is considered.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC2862
06/2000
(7 p.)
pdf(2p)
|
M. Civanlar
G. Cash |
|
RTP Payload Format for Real-Time Pointers |
This document describes an RTP payload format for transporting
the coordinates of a dynamic pointer that may be used during a
presentation. Although a mouse can be used as the pointer, this
payload format is not intended and may not have all functionalities
needed to implement a general mouse event transmission mechanism.
The "video/pointer" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3016
11/2000
(21 p.)
pdf(2p)
|
Y. Kikuchi
T. Nomura
S. Fukunaga
Y. Matsui
H. Kimata |
|
RTP Payload Format for MPEG-4 Audio/Visual Streams |
This document describes Real-Time Transport Protocol (RTP) payload
formats for carrying each of MPEG-4 Audio and MPEG-4 Visual
bitstreams without using MPEG-4 Systems. For the purpose of directly
mapping MPEG-4 Audio/Visual bitstreams onto RTP packets, it provides
specifications for the use of RTP header fields and also specifies
fragmentation rules. It also provides specifications for
Multipurpose Internet Mail Extensions (MIME) type registrations and
the use of Session Description Protocol (SDP).
The "video/MP4V-ES" media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3158
08/2001
(22 p.)
pdf(2p)
|
C. Perkins
J. Rosenberg
H. Schulzrinne |
|
RTP Testing Strategies |
This memo describes a possible testing strategy for RTP (real-time
transport protocol) implementations.
This memo describes a possible testing strategy for RTP
implementations. The tests are intended to help demonstrate
interoperability of multiple implementations, and to illustrate
common implementation errors. They are not intended to be an
exhaustive set of tests and passing these tests does not necessarily
imply conformance to the complete RTP specification.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC3189
01/2002
(13 p.)
pdf(2p)
|
K. Kobayashi
A. Ogawa
S. Casner
C. Bormann |
|
RTP Payload Format for DV (IEC 61834) Video |
This document specifies the packetization scheme for encapsulating
the compressed digital video data streams commonly known as "DV" into
a payload format for the Real-Time Transport Protocol (RTP).
This document specifies payload formats for encapsulating both
consumer- and professional-use DV format data streams into the Real-time
Transport Protocol (RTP), version 2. DV compression audio
and video formats were designed for helical-scan magnetic tape media.
The DV standards for consumer-market devices, the IEC 61883 and 61834
series, cover many aspects of consumer-use digital video, including
mechanical specifications of a cassette, magnetic recording format,
error correction on the magnetic tape, DCT video encoding format, and
audio encoding format. The digital interface part of IEC 61883
defines an interface on an IEEE 1394 network. This
specification set supports several video formats: SD-VCR (Standard
Definition), HD-VCR (High Definition), SDL-VCR (Standard Definition -
Long), PALPlus, DVB (Digital Video Broadcast) and ATV (Advanced
Television). North American formats are indicated with a number of
lines and "/60", while European formats use "/50". DV standards
extended for professional use were published by SMPTE as 306M and
314M, for different sampling systems, higher color resolution, and
faster bit rates.
The "DV" MIME subtype has been registered by IANA for both the "audio" and "video" MIME types.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3190
01/2002
(17 p.)
pdf(2p)
|
K. Kobayashi
A. Ogawa
S. Casner
C. Bormann |
|
RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio |
This document specifies a packetization scheme for encapsulating
12-bit nonlinear, 20-bit linear, and 24-bit linear audio data streams
using the Real-time Transport Protocol (RTP). This document also
specifies the format of a Session Description Protocol (SDP)
parameter to indicate when audio data is preemphasized before
sampling. The parameter may be used with other audio payload
formats, in particular L16 (16-bit linear).
The "audio/DAT12", "audio/L20", and "audio/L24", MIME media types have been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3389
09/2002
(8 p.)
pdf(2p)
|
R. Zopf |
|
RTP Payload for Comfort Noise (CN) |
This document describes a Real-time Transport Protocol (RTP) payload
format for transporting comfort noise (CN). The CN payload type is
primarily for use with audio codecs that do not support comfort noise
as part of the codec itself such as ITU-T Recommendations G.711,
G.726, G.727, G.728, and G.722.
The "audio/CN" media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3497
03/2003
(12 p.)
pdf(2p)
|
L. Gharai
C. Perkins
G. Goncher
A. Mankin |
|
RTP Payload Format for SMPTE 292M Video |
This memo specifies an RTP payload format for encapsulating
uncompressed High Definition Television (HDTV) as defined by the
Society of Motion Picture and Television Engineers (SMPTE) standard,
SMPTE 292M. SMPTE is the main standardizing body in the motion
imaging industry and the SMPTE 292M standard defines a bit-serial
digital interface for local area HDTV transport.
The "video/SMPTE292M" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3545
07/2003
(22 p.)
pdf(2p)
|
T. Koren
S. Casner
J. Geevarghese
B. Thompson
P. Ruddy |
|
Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and Reordering |
|
This document describes a header compression scheme for point to
point links with packet loss and long delays. It is based on
Compressed Real-time Transport Protocol (CRTP), the IP/UDP/RTP header
compression described in RFC2508. CRTP does not perform well on
such links: packet loss results in context corruption and due to the
long delay, many more packets are discarded before the context is
repaired. To correct the behavior of CRTP over such links, a few
extensions to the protocol are specified here. The extensions aim to
reduce context corruption by changing the way the compressor updates
the context at the decompressor: updates are repeated and include
updates to full and differential context parameters. With these
extensions, CRTP performs well over links with packet loss, packet
reordering and long delays.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3550
07/2003
(104 p.)
pdf(2p)
|
H. Schulzrinne
S. Casner
R. Frederick
V. Jacobson |
| RTP: A Transport Protocol for
Real-Time Applications |
|
This memorandum describes RTP, the real-time transport protocol. RTP
provides end-to-end network transport functions suitable for
applications transmitting real-time data, such as audio, video or
simulation data, over multicast or unicast network services. RTP
does not address resource reservation and does not guarantee
quality-of-service for real-time services. The data transport is
augmented by a control protocol (RTCP) to allow monitoring of the
data delivery in a manner scalable to large multicast networks, and
to provide minimal control and identification functionality. RTP and
RTCP are designed to be independent of the underlying transport and
network layers. The protocol supports the use of RTP-level
translators and mixers.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC3551
07/2003
(44 p.)
pdf(2p)
|
H. Schulzrinne
S. Casner |
| RTP Profile for Audio and Video
Conferences with Minimal Control |
This document describes a profile called "RTP/AVP" for the use of the
real-time transport protocol (RTP), version 2, and the associated
control protocol, RTCP, within audio and video multiparticipant
conferences with minimal control. It provides interpretations of
generic fields within the RTP specification suitable for audio and
video conferences. In particular, this document defines a set of
default mappings from payload type numbers to encodings.
This document also describes how audio and video data may be carried
within RTP. It defines a set of standard encodings and their names
when used within RTP. The descriptions provide pointers to reference
implementations and the detailed standards. This document is meant
as an aid for implementors of audio, video and other real-time
multimedia applications.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC3556
07/2003
(8 p.)
pdf(2p)
|
S. Casner |
|
SDP Bandwidth Modifiers for RTCP Bandwidth |
|
This document defines an extension to the Session Description
Protocol (SDP) to specify two additional modifiers for the bandwidth
attribute. These modifiers may be used to specify the bandwidth
allowed for RTP Control Protocol (RTCP) packets in a Real-time
Transport Protocol (RTP) session.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3557
07/2003
(15 p.)
pdf(2p)
|
Q. Xie |
|
RTP Payload Format for ETSI ES 201 108 DSR Encoding |
This document specifies an RTP payload format for encapsulating
European Telecommunications Standards Institute (ETSI) European
Standard (ES) 201 108 front-end signal processing feature streams for
distributed speech recognition (DSR) systems.
The "audio/dsr-es201108" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3558
07/2003
(23 p.)
pdf(2p)
|
A. Li |
|
RTP Payload Format for Enhanced Variable Rate Codecs (EVRC)
and Selectable Mode Vocoders (SMV) |
This document describes the RTP payload format for Enhanced Variable
Rate Codec (EVRC) Speech and Selectable Mode Vocoder (SMV) Speech.
Two sub-formats are specified for different application scenarios. A
bundled/interleaved format is included to reduce the effect of packet
loss on speech quality and amortize the overhead of the RTP header
over more than one speech frame. A non-bundled format is also
supported for conversational applications.
The following media types have been registered by the IANA:
"audio/EVRC"
"audio/EVRC0"
"audio/SMV"
"audio/SMV0"
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC3611
11/2003
(55 p.)
pdf(2p)
|
T. Friedman
R. Caceres
A. Clark |
|
RTP Control Protocol Extended Reports (RTCP XR) |
|
This document defines the Extended Report (XR) packet type for the
RTP Control Protocol (RTCP), and defines how the use of XR packets
can be signaled by an application if it employs the Session
Description Protocol (SDP). XR packets are composed of report
blocks, and seven block types are defined here. The purpose of the
extended reporting format is to convey information that supplements
the six statistics that are contained in the report blocks used by
RTCP's Sender Report (SR) and Receiver Report (RR) packets. Some
applications, such as multicast inference of network characteristics
(MINC) or voice over IP (VoIP) monitoring, require other and more
detailed statistics. In addition to the block types defined here,
additional block types may be defined in the future by adhering to
the framework that this document provides.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3640
11/2003
(43 p.)
pdf(2p)
|
J. van der Meer
D. Mackie
V. Swaminathan
D. Singer
P. Gentric |
|
RTP Payload Format for Transport of MPEG-4 Elementary Streams |
The Motion Picture Experts Group (MPEG) Committee (ISO/IEC JTC1/SC29
WG11) is a working group in ISO that produced the MPEG-4 standard.
MPEG defines tools to compress content such as audio-visual
information into elementary streams. This specification defines a
simple, but generic RTP payload format for transport of any non-multiplexed
MPEG-4 elementary stream.
The "mpeg4-generic"" MIME subtype has been registered by the IANA; it can be used with the
"video" or "audio" or "application" MIME type.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3711
03/2004
(56 p.)
pdf(2p)
|
M. Baugher
D. McGrew
M. Naslund
E. Carrara
K. Norrman |
|
The Secure Real-time Transport Protocol (SRTP) |
|
This document describes the Secure Real-time Transport Protocol
(SRTP), a profile of the Real-time Transport Protocol (RTP), which
can provide confidentiality, message authentication, and replay
protection to the RTP traffic and to the control traffic for RTP, the
Real-time Transport Control Protocol (RTCP).
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC3839
07/2004
(7 p.)
pdf(2p)
|
R. Castagno
D. Singer |
|
MIME Type Registrations for 3GPP Multimedia files |
This document serves to register and document the standard MIME types
associated with the 3GPP (3rd Generation Partnership Project) multimedia file format, which is part of the
family based on the ISO Media File Format.
The 3GPP for third-generation
cellular telephony has defined a standard file format to contain
audio/visual sequences which may be downloaded to cellular phones
[3GPP TS 26.244].
At the time of writing, the 3GPP file format (3GP) can
contain H.263 or MPEG-4 video, and AMR narrow-band speech, AMR wide-band
speech, or AAC audio, and 3GPP timed text.
The "audio/3gpp" and "video/3gpp" MIME media types have been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC3951
12/2004
(194 p.)
pdf(2p)
|
S. Andersen
A. Duric
H. Astrom
R. Hagen
W. Kleijn
J. Linden |
|
Internet Low Bit Rate Codec (iLBC) |
|
This document specifies a speech codec suitable for robust voice
communication over IP. The codec is developed by Global IP Sound
(GIPS). It is designed for narrow band speech and results in a
payload bit rate of 13.33 kbit/s for 30 ms frames and 15.20 kbit/s
for 20 ms frames. The codec enables graceful speech quality
degradation in the case of lost frames, which occurs in connection
with lost or delayed IP packets.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC3952
12/2004
(13 p.)
pdf(2p)
|
A. Duric
S. Andersen |
|
RTP Payload Format for internet Low Bit Rate Codec (iLBC) Speech |
This document describes the Real-time Transport Protocol (RTP)
payload format for the internet Low Bit Rate Codec (iLBC) Speech
developed by Global IP Sound (GIPS). Also, within the document there
are included necessary details for the use of iLBC with MIME and
Session Description Protocol (SDP).
The "audio/iLBC" media type has been registered by the IANA.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC3984
02/2005
(83 p.)
pdf(2p)
|
S. Wenger
M.M. Hannuksela
T. Stockhammer
M. Westerlund
D. Singer |
|
RTP Payload Format for H.264 Video |
This memo describes an RTP Payload format for the ITU-T
Recommendation H.264 video codec and the technically identical
ISO/IEC International Standard 14496-10 video codec. The RTP payload
format allows for packetization of one or more Network Abstraction
Layer Units (NALUs), produced by an H.264 video encoder, in each RTP
payload. The payload format has wide applicability, as it supports
applications from simple low bit-rate conversational usage, to
Internet video streaming with interleaved transmission, to high bit-rate
video-on-demand.
The H.264 video codec has a very broad application range that covers
all forms of digital compressed video from, low bit-rate Internet
streaming applications to HDTV broadcast and Digital Cinema
applications with nearly lossless coding. Compared to the current
state of technology, the overall performance of H.264 is such that
bit rate savings of 50% or more are reported. Digital Satellite TV
quality, for example, was reported to be achievable at 1.5 Mbit/s,
compared to the current operation point of MPEG 2 video at around 3.5
Mbit/s.
The "video/H264" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4060
05/2005
(19 p.)
pdf(2p)
|
Q. Xie
D. Pearce |
|
RTP Payload Formats for ETSI ES 202 050, ES 202 211, and ES 202 212 DSR Encoding |
This document specifies RTP payload formats for encapsulating
European Telecommunications Standards Institute (ETSI) European
Standard ES 202 050 DSR Advanced Front-end (AFE), ES 202 211 DSR
Extended Front-end (XFE), and ES 202 212 DSR Extended Advanced
Front-end (XAFE) signal processing feature streams for distributed
speech recognition (DSR) systems.
The following MIME media types have been registered by the IANA:
"audio/dsr-es202050"
"audio/dsr-es202211"
"audio/dsr-es202212"
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4103
06/2005
(20 p.)
pdf(2p)
|
G. Hellstrom
P. Jones |
|
RTP Payload for Text Conversation |
This memo describes how to carry real-time
text conversation session contents in RTP packets. Text conversation
session contents are specified in ITU-T Recommendation T.140.
One payload format is described for transmitting text on a separate
RTP session dedicated for the transmission of text.
This RTP payload description recommends a method to include redundant
text from already transmitted packets in order to reduce the risk of
text loss caused by packet loss.
The "text/t140" media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
Obsoletes: RFC 2793 |
|
|
|
|
|
|
|
|
| | |
RFC4170
11/2005
(24 p.)
pdf(2p)
|
B. Thompson
T. Koren
D. Wing |
|
Tunneling Multiplexed Compressed RTP (TCRTP) |
|
This document describes a method to improve the bandwidth utilization
of RTP streams over network paths that carry multiple Real-time
Transport Protocol (RTP) streams in parallel between two endpoints,
as in voice trunking. The method combines standard protocols that
provide compression, multiplexing, and tunneling over a network path
for the purpose of reducing the bandwidth used when multiple RTP
streams are carried over that path.
|
|
|
| |
| List |
Status: | Best Current Practice (BCP: 110) |
|
|
|
|
|
|
|
|
| | |
RFC4175
09/2005
(18 p.)
pdf(2p)
|
L. Gharai
C. Perkins |
|
RTP Payload Format for Uncompressed Video |
This memo specifies a packetization scheme for encapsulating
uncompressed video into a payload format for the Real-time Transport
Protocol, RTP. It supports a range of standard- and high-definition
video formats, including common television formats such as ITU
BT.601, and standards from the Society of Motion Picture and
Television Engineers (SMPTE), such as SMPTE 274M and SMPTE 296M. The
format is designed to be applicable and extensible to new video
formats as they are developed.
The "video/raw" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4184
10/2005
(13 p.)
pdf(2p)
|
B. Link
T. Hager
J. Flaks |
|
RTP Payload Format for AC-3 Audio |
This document describes an RTP payload format for transporting audio
data using the AC-3 audio compression standard. AC-3 is a high
quality, multichannel audio coding system that is used for United
States HDTV, DVD, cable television, satellite television and other
media. The RTP payload format presented in this document includes
support for data fragmentation.
AC-3 is designed to encode multiple channels of audio into a low bit-rate
format. AC-3 achieves its large compression ratios via encoding a
multiplicity of channels as a single entity. Dolby Digital, which is
a branded version of AC-3, encodes up to 5.1 channels of audio.
AC-3 has been adopted as an audio compression scheme for many
consumer and professional applications. It is a mandatory audio
codec for DVD-video, Advanced Television Standards Committee (ATSC)
digital terrestrial television and Digital Living Network Alliance
(DLNA) home networking, as well as an optional multichannel audio
format for DVD-audio.
There is a need to stream AC-3 data over IP networks. The Internet
Real Time Protocol (RTP) provides a mechanism for stream
synchronization and hence serves as the best transport solution for
AC-3, which is primarily used in audio-for-video applications.
Applications for streaming AC-3 include streaming movies from a home
media server to a display, video on demand, and multichannel Internet
radio.
The "audio/ac3" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4247
11/2005
(11 p.)
pdf(2p)
|
J. Ash
B. Goode
J. Hand
R. Zhang |
|
Requirements for Header Compression over MPLS |
|
Voice over IP (VoIP) typically uses the encapsulation
voice/RTP/UDP/IP. When MPLS labels are added, this becomes
voice/RTP/UDP/IP/MPLS-labels. For an MPLS VPN, the packet header is
typically 48 bytes, while the voice payload is often no more than 30
bytes, for example. Header compression can significantly reduce the
overhead through various compression mechanisms, such as enhanced
compressed RTP (ECRTP) and robust header compression (ROHC). We
consider using MPLS to route compressed packets over an MPLS Label
Switched Path (LSP) without compression/decompression cycles at each
router. This approach can increase the bandwidth efficiency as well
as processing scalability of the maximum number of simultaneous flows
that use header compression at each router. In this document, we
give a problem statement, goals and requirements, and an example
scenario.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC4298
12/2005
(14 p.)
pdf(2p)
|
J.-H. Chen
W. Lee
J. Thyssen |
|
RTP Payload Format for BroadVoice Speech Codecs |
This document describes the RTP payload format for the BroadVoice(R)
narrowband and wideband speech codecs. The narrowband codec, called
BroadVoice16, or BV16, has been selected by CableLabs as a mandatory
codec in PacketCable 1.5 and has a CableLabs specification. The
document also provides specifications for the use of BroadVoice with
MIME and the Session Description Protocol (SDP).
The "audio/BV16" and "audio/BV32" media types have been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4348
01/2006
(32 p.)
pdf(2p)
|
S. Ahmadi |
|
RTP Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec |
This document specifies a real-time transport protocol (RTP) payload
format to be used for the Variable-Rate Multimode Wideband (VMR-WB)
speech codec. The payload format is designed to be able to
interoperate with existing VMR-WB transport formats on non-IP
networks. A media type registration is included for VMR-WB RTP
payload format.
VMR-WB is a variable-rate multimode wideband speech codec that has a
number of operating modes, one of which is interoperable with AMR-WB
[RFC4867] audio codec at certain rates. Therefore, provisions
have been made in this document to facilitate and simplify data
packet exchange between VMR-WB and AMR-WB in the interoperable mode
with no transcoding function involved.
The "audio/VMR-WB" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4351
01/2006
(20 p.)
pdf(2p)
|
G. Hellstrom
P. Jones |
|
RTP Payload for Text Conversation Interleaved in an Audio Stream |
This memo describes how to carry real-time text conversation session
contents in RTP packets. Text conversation session contents are
specified in ITU-T Recommendation T.140.
One payload format is described for transmitting audio and text data
within a single RTP session.
This RTP payload description recommends a method to include redundant
text from already transmitted packets in order to reduce the risk of
text loss caused by packet loss.
The "audio/t140c" media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4352
01/2006
(38 p.)
pdf(2p)
|
J. Sjoberg
M. Westerlund
A. Lakaniemi
S. Wenger |
|
RTP Payload Format for the
Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio Codec |
This document specifies a Real-time Transport Protocol (RTP) payload
format for Extended Adaptive Multi-Rate Wideband (AMR-WB+) encoded
audio signals. The AMR-WB+ codec is an audio extension of the AMR-WB
speech codec. It encompasses the AMR-WB frame types and a number of
new frame types designed to support high-quality music and speech. A
media type registration for AMR-WB+ is included in this
specification.
The "audio/amr-wb+" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4393
03/2006
(7 p.)
pdf(2p)
|
H. Garudadri |
|
MIME Type Registrations for 3GPP2 Multimedia Files |
This document serves to register and document the standard MIME types
associated with the 3GPP2 multimedia file format, which is part of
the family based on the ISO Media File Format.
The "audio/3gpp2" and "video/3gpp2" MIME media types have been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4396
02/2006
(66 p.)
pdf(2p)
|
J. Rey
Y. Matsui |
|
RTP Payload Format 3GPP Timed Text |
This document specifies an RTP payload format for the transmission of
3GPP (3rd Generation Partnership Project) timed text
[3GPP TS 26.245].
3GPP timed
text is a time-lined, decorated text media format with defined
storage in a 3GP file. Timed Text can be synchronized with
audio/video contents and used in applications such as captioning,
titling, and multimedia presentations. In the following sections,
the problems of streaming timed text are addressed, and a payload
format for streaming 3GPP timed text over RTP is specified.
The "video/3gpp-tt" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4424
02/2006
(8 p.)
pdf(2p)
|
S. Ahmadi |
|
RTP Payload Format for the
Variable-Rate Multimode Wideband (VMR-WB) Extension Audio Codec |
This document is an addendum to RFC4348, which specifies the RTP
payload format for the Variable-Rate Multimode Wideband (VMR-WB)
speech codec. This document specifies some updates in RFC4348 to
enable support for the new operating mode of VMR-WB standard (i.e.,
VMR-WB mode 4). These updates do not affect the existing modes of
VMR-WB already specified in RFC4348.
The payload formats and their associated parameters, as well as all
provisions, restrictions, use cases, features, etc., that are
specified in RFC4348 are applicable to the new operating mode with
no exception.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4425
02/2006
(36 p.)
pdf(2p)
|
A. Klemets |
|
RTP Payload Format for Video Codec 1 (VC-1) |
This memo specifies an RTP payload format for encapsulating Video
Codec 1 (VC-1) compressed bit streams, as defined by the Society of
Motion Picture and Television Engineers (SMPTE) standard, SMPTE 421M.
SMPTE is the main standardizing body in the motion imaging industry,
and the SMPTE 421M standard defines a compressed video bit stream
format and decoding process for television.
The "video/vc1" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4573
07/2006
(7 p.)
pdf(2p)
|
R. Even
A. Lochbaum |
|
MIME Type Registration for RTP Payload Format for H.224 |
|
In conversational video applications, far-end camera control protocol
is used by participants to control the remote camera. The protocol
that is commonly used is ITU H.281 over H.224. The document
registers the "application/H224" media type. It defines the syntax and the
semantics of the Session Description Protocol (SDP) parameters needed
to support far-end camera control protocol using H.224.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4585
07/2006
(51 p.)
pdf(2p)
|
J. Ott
S. Wenger
N. Sato
C. Burmeister
J. Rey |
|
Extended RTP Profile for
RTCP-Based Feedback (RTP/AVPF) |
|
Real-time media streams that use RTP are, to some degree, resilient
against packet losses. Receivers may use the base mechanisms of the
Real-time Transport Control Protocol (RTCP) to report packet
reception statistics and thus allow a sender to adapt its
transmission behavior in the mid-term. This is the sole means for
feedback and feedback-based error repair (besides a few codec-specific
mechanisms). This document defines an extension to the
Audio-visual Profile (AVP) that enables receivers to provide,
statistically, more immediate feedback to the senders and thus allows
for short-term adaptation and efficient feedback-based repair
mechanisms to be implemented. This early feedback profile (AVPF)
maintains the AVP bandwidth constraints for RTCP and preserves
scalability to large groups.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC4586
07/2006
(28 p.)
pdf(2p)
|
C. Burmeister
R. Hakenberg
A. Miyazaki
J. Ott
N. Sato
S. Fukunaga |
|
Extended RTP Profile for RTCP-Based Feedback:
Results of the Timing Rule Simulations |
|
This document describes the results achieved when simulating the
timing rules of the Extended RTP Profile for Real-time Transport
Control Protocol (RTCP)-Based Feedback, denoted AVPF. Unicast and
multicast topologies are considered as well as several protocol and
environment configurations. The results show that the timing rules
result in better performance regarding feedback delay and still
preserve the well-accepted RTP rules regarding allowed bit rates for
control traffic.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC4587
08/2006
(17 p.)
pdf(2p)
|
R. Even |
|
RTP Payload Format for H.261 Video Streams |
This memo describes a scheme to packetize an H.261 video stream for
transport using the Real-time Transport Protocol, RTP, with any of
the underlying protocols that carry RTP.
The memo also describes the syntax and semantics of the Session
Description Protocol (SDP) parameters needed to support the H.261
video codec. A media type registration is included for this payload
format.
The "video/H261" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
Obsoletes: RFC 2032 |
|
|
|
|
|
|
|
|
| | |
RFC4588
07/2006
(35 p.)
pdf(2p)
|
J. Rey
D. Leon
A. Miyazaki
V. Varsa
R. Hakenberg |
|
RTP Retransmission Payload Format |
|
RTP retransmission is an effective packet loss recovery technique for
real-time applications with relaxed delay bounds. This document
describes an RTP payload format for performing retransmissions.
Retransmitted RTP packets are sent in a separate stream from the
original RTP stream. It is assumed that feedback from receivers to
senders is available. In particular, it is assumed that Real-time
Transport Control Protocol (RTCP) feedback as defined in the extended
RTP profile for RTCP-based feedback (denoted RTP/AVPF) is available
in this memo.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4598
07/2006
(17 p.)
pdf(2p)
|
B. Link |
|
RTP Payload Format for Enhanced AC-3 (E-AC-3) Audio |
This document describes a Real-time Transport Protocol (RTP) payload
format for transporting Enhanced AC-3 (E-AC-3) encoded audio data.
E-AC-3 is a high-quality, multichannel audio coding format and is an
extension of the AC-3 audio coding format, which is used in US High-Definition
Television (HDTV), DVD, cable and satellite television,
and other media. E-AC-3 is an optional audio format in US and world
wide digital television and high-definition DVD formats. The RTP
payload format as presented in this document includes support for
data fragmentation.
The Enhanced AC-3 (E-AC-3) [ETSI TS 102 366] audio coding system is built on a
foundation of AC-3. It is an enhancement and extension to AC-3,
which is an existing audio coding standard commonly used for DVD,
broadcast, cable, and satellite television content. E-AC-3 is
designed to enable operation at both higher and lower data rates than
AC-3, provide expanded channel configurations, and provide greater
flexibility for carriage of multiple audio program elements. The
relationship between E-AC-3 and AC-3 provides for low-loss, low-cost
conversion between the two and makes E-AC-3 especially suitable in
applications that require compatibility with the existing broadcast-reception
and audio/video decoding infrastructure. Dolby Digital
Plus is a branded version of Enhanced AC-3.
E-AC-3 has been standardized within both the European
Telecommunications Standards Institute (ETSI) and the Advanced
Television Systems Committee (ATSC). It is an optional audio format
for use in US (ATSC) and Digital Video Broadcasting (DVB) television
transmission. It is also a required audio format for use in the High
Definition (HD)-DVD optical-storage media format and included in the
Blu-ray Disc format.
There is a need to stream E-AC-3 content over IP networks. E-AC-3 is
primarily used in audio-for-video applications, so RTP serves well as
a transport solution with its mechanism for synchronizing streams.
Applications for streaming E-AC-3 include Internet Protocol
television (IPTV), video on demand, interactive features of next
generation DVD formats, and transfer of movies across a home network.
The "audio/eac3" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4612
08/2006
(8 p.)
pdf(2p)
|
P. Jones
H. Tamura |
|
Real-Time Facsimile (T.38) - audio/t38 MIME Sub-type Registration |
ITU-T Recommendation T.38 defines the Internet Facsimile Protocol
(IFP) for carriage of facsimile data over IP networks. As one
option, IFP packets may be carried within an RTP stream, either
as the only content within the media stream or switched with other
audio payload types.
This memo provides rationale for using RTP as a transport for fax
signaling and specifies the "audio/t38" MIME type associated with said signaling.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC4629
01/2007
(29 p.)
pdf(2p)
|
J. Ott
C. Bormann
G. Sullivan
S. Wenger
R. Even |
|
RTP Payload Format for ITU-T Rec. H.263 Video |
This document describes a scheme to packetize an H.263 video stream
for transport using the Real-time Transport Protocol (RTP) with any
of the underlying protocols that carry RTP.
The document also describes the syntax and semantics of the Session
Description Protocol (SDP) parameters needed to support the H.263
video codec.
This document updates the "video/H263-1998" and
"video/H263-2000" media types defined in RFC3555, section 4.2.
|
|
|
| |
| List |
Status: | Proposed Standard |
Obsoletes: RFC 2429 | Updates: RFC 3555 |
|
|
|
|
|
|
|
|
| | |
RFC4695
11/2006
(169 p.)
pdf(2p)
|
J. Lazzaro
J. Wawrzynek |
|
RTP Payload Format for MIDI (Musical Instrument Digital Interface) |
This memo describes a Real-time Transport Protocol (RTP) payload
format for the MIDI command
language. The format encodes all commands that may legally appear on
a MIDI 1.0 DIN cable. The format is suitable for interactive
applications (such as network musical performance) and content-delivery
applications (such as file streaming). The format may be
used over unicast and multicast UDP and TCP, and it defines tools for
graceful recovery from packet loss. Stream behavior, including the
MIDI rendering method, may be customized during session setup. The
format also serves as a mode for the mpeg4-generic format, to support
the MPEG 4 Audio Object Types for General MIDI, Downloadable Sounds
Level 2, and Structured Audio.
The "audio/rtp-midi" and "audio/asc" media types have been registered by the IANA, as well as
the "rtp-midi" value for the "mode" parameter of the "mpeg4-generic" media type, defined in RFC3640.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4696
11/2006
(38 p.)
pdf(2p)
|
J. Lazzaro
J. Wawrzynek |
|
An Implementation Guide for RTP MIDI |
|
This memo offers non-normative implementation guidance for the Real-time
Protocol (RTP) MIDI (Musical Instrument Digital Interface)
payload format. The memo presents its advice in the context of a
network musical performance application. In this application two
musicians, located in different physical locations, interact over a
network to perform as they would if located in the same room.
Underlying the performances are RTP MIDI sessions over unicast UDP.
Algorithms for sending and receiving recovery journals (the
resiliency structure for the payload format) are described in detail.
Although the memo focuses on network musical performance, the
presented implementation advice is relevant to other RTP MIDI
applications.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC4733
12/2006
(49 p.)
pdf(2p)
|
H. Schulzrinne
T. Taylor |
|
RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals |
This memo describes how to carry dual-tone multifrequency (DTMF)
signalling, other tone signals, and telephony events in RTP packets.
It obsoletes RFC 2833.
This memo captures and expands upon the basic framework defined in
RFC 2833, but retains only the most basic event codes. It sets up an
IANA registry to which other event code assignments may be added.
Companion documents add event codes to this registry relating to
modem, fax, text telephony, and channel-associated signalling events.
The remainder of the event codes defined in RFC 2833 are
conditionally reserved in case other documents revive their use.
This document provides a number of clarifications to the original
document. However, it specifically differs from RFC 2833 by removing
the requirement that all compliant implementations support the DTMF
events. Instead, compliant implementations taking part in
out-of-band negotiations of media stream content indicate what events
they support. This memo adds three new procedures to the RFC 2833
framework: subdivision of long events into segments, reporting of
multiple events in a single packet, and the concept and reporting of
state events.
The "audio/telephone-event" and "audio/tone" media types have been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
Obsoletes: RFC 2833 |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
Obsoletes: RFC 2833 | Updates: RFC 4733 |
|
|
|
|
|
|
|
|
| | |
RFC4749
10/2006
(13 p.)
pdf(2p)
|
A. Sollaud |
|
RTP Payload Format for the G.729.1 Audio Codec |
This document specifies a Real-time Transport Protocol (RTP) payload
format to be used for the International Telecommunication Union
(ITU-T) G.729.1 audio codec.
G.729.1 is an 8-32 kbps scalable wideband (50-7000 Hz) speech and
audio coding algorithm interoperable with G.729, G.729 Annex A, and
G.729 Annex B. It provides a standardized solution for packetized
voice applications that allows a smooth transition from narrowband to
wideband telephony.
The "audio/G7291" media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4788
01/2007
(22 p.)
pdf(2p)
|
Q. Xie
R. Kapoor |
|
Enhancements to RTP Payload Formats for EVRC Family Codecs |
This document updates the Enhanced Variable Rate Codec (EVRC) RTP
payload formats defined in
RFC3558 with several enhancements and
extensions. In particular, it defines support for the header-free
and interleaved/bundled packet formats for the EVRC-B codec, a new
compact bundled format for the EVRC and EVRC-B codecs, as well as
discontinuous transmission (DTX) support for EVRC and EVRC-B-encoded
speech transported via RTP. Voice over IP (VoIP) applications
operating over low bandwidth dial-up and wireless networks require
such enhancements for efficient use of the bandwidth.
The following media types have been registered by the IANA:
"audio/EVRC1"
"audio/EVRCB"
"audio/EVRCB0"
"audio/EVRCB1"
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC4855
02/2007
(11 p.)
pdf(2p)
|
S. Casner |
|
Media Type Registration of RTP Payload Formats |
|
This document specifies the procedure to register RTP payload formats
as audio, video, or other media subtype names. This is useful in a
text-based format description or control protocol to identify the
type of an RTP transmission.
|
|
|
| |
| List |
Status: | Proposed Standard |
Obsoletes: RFC 3555 |
|
|
|
|
|
|
|
|
| | |
RFC4856
03/2007
(29 p.)
pdf(2p)
|
S. Casner |
|
Media Type Registration of Payload Formats in the
RTP Profile for Audio and Video Conferences |
This document specifies media type registrations for the RTP payload
formats defined in the RTP Profile for Audio and Video Conferences.
Some of these may also be used for transfer modes other than RTP.
This document updates the media type registrations listed below to
conform to the revised registration format specified in RFC 4288 and
RFC4855. Some media type registrations
contained in RFC3555 are omitted from this document; the existing
registrations for those types continue to be valid until updated by
other RFCs. There are no new registrations contained here.
| | | |
audio/DVI4
audio/G722
audio/G723
audio/G726-16
audio/G726-24
audio/G726-32
audio/G726-40
|
audio/G728
audio/G729
audio/G729D
audio/G729E
audio/GSM
audio/GSM-EFR
audio/L8
|
audio/L16
audio/LPC
audio/PCMA
audio/PCMU
audio/VDVI
video/nv
|
|
|
|
| |
| List |
Status: | Proposed Standard |
Obsoletes: RFC 3555 |
|
|
|
|
|
|
|
|
| | |
RFC4867
04/2007
(59 p.)
pdf(2p)
|
J. Sjoberg
M. Westerlund
A. Lakaniemi
Q. Xie |
|
RTP Payload Format and File Storage Format for the
AMR and AMR-WB Audio Codecs |
This document specifies a Real-time Transport Protocol (RTP) payload
format to be used for Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate
Wideband (AMR-WB) encoded speech signals. The payload format is
designed to be able to interoperate with existing AMR and AMR-WB
transport formats on non-IP networks. In addition, a file format is
specified for transport of AMR and AMR-WB speech data in storage mode
applications such as email. Two separate media type registrations
are included, one for AMR and one for AMR-WB, specifying use of both
the RTP payload format and the storage format.
The following MIME media types have been registered by the IANA:
"audio/AMR"
"audio/AMR-WB"
|
|
|
| |
| List |
Status: | Proposed Standard |
Obsoletes: RFC 3267 |
|
|
|
|
|
|
|
|
| | |
RFC4901
06/2007
(34 p.)
pdf(2p)
|
J. Ash
J. Hand
A. Malis |
|
Protocol Extensions for Header Compression over MPLS |
|
This specification defines how to use Multi-Protocol Label Switching
(MPLS) to route Header-Compressed (HC) packets over an MPLS label
switched path. HC can significantly reduce packet-header overhead
and, in combination with MPLS, can also increases bandwidth
efficiency and processing scalability in terms of the maximum number
of simultaneous compressed flows that use HC at each router). Here
we define how MPLS pseudowires are used to transport the HC context
and control messages between the ingress and egress MPLS label
switching routers. This is defined for a specific set of existing HC
mechanisms that might be used, for example, to support voice over IP.
This specification also describes extension mechanisms to allow
support for future, as yet to be defined, HC protocols. In this
specification, each HC protocol operates independently over a single
pseudowire instance, very much as it would over a single point-to-point
link.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5093
12/2007
(8 p.)
pdf(2p)
|
G. Hunt |
|
BT's eXtended Network Quality RTP Control Protocol Extended Reports
(RTCP XR XNQ) |
|
This document describes an RTCP XR report block, which reports packet
transport parameters. The report block was developed by BT for pre-standards
use in BT's next-generation network. This document has
been produced to describe the report block in sufficient detail to
register the block type with IANA in accordance with the
Specification Required policy of RFC 3611. This specification does
not standardise the new report block for use outside BT's network.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC5104
02/2008
(64 p.)
pdf(2p)
|
S. Wenger
U. Chandra
M. Westerlund
B. Burman |
|
Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF) |
This document specifies a few extensions to the messages defined in
the Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls.
The extensions discussed are messages related to the ITU-T Rec. H.271
Video Back Channel, Full Intra Request, Temporary Maximum Media
Stream Bit Rate, and Temporal-Spatial Trade-off.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5109
12/2007
(44 p.)
pdf(2p)
|
A. Li |
|
RTP Payload Format for Generic Forward Error Correction |
|
This document specifies a payload format for generic Forward Error
Correction (FEC) for media data encapsulated in RTP. It is based on
the exclusive-or (parity) operation. The payload format described in
this document allows end systems to apply protection using various
protection lengths and levels, in addition to using various
protection group sizes to adapt to different media and channel
characteristics. It enables complete recovery of the protected
packets or partial recovery of the critical parts of the payload
depending on the packet loss situation. This scheme is completely
compatible with non-FEC-capable hosts, so the receivers in a
multicast group that do not implement FEC can still work by simply
ignoring the protection data. This specification obsoletes RFC 2733
and RFC 3009. The FEC specified in this document is not backward
compatible with RFC 2733 and RFC 3009.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5117
01/2008
(21 p.)
pdf(2p)
|
M. Westerlund
S. Wenger |
|
RTP Topologies |
|
This document discusses multi-endpoint topologies used in Real-time
Transport Protocol (RTP)-based environments. In particular,
centralized topologies commonly employed in the video conferencing
industry are mapped to the RTP terminology.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5188
02/2008
(25 p.)
pdf(2p)
|
QH. Desineni
Q. Xie |
|
RTP Payload Format for the Enhanced Variable Rate Wideband Codec (EVRC-WB)
and the Media Subtype Updates for EVRC-B Codec |
This document specifies Real-time Transport Protocol (RTP) payload
formats to be used for the Enhanced Variable Rate Wideband Codec
(EVRC-WB) and updates the media type registrations for EVRC-B codec.
Several media type registrations are included for EVRC-WB RTP payload
formats. In addition, a file format is specified for transport of
EVRC-WB speech data in storage mode applications such as email.
The following media types have been registered by the IANA:
"audio/EVRCWB"
"audio/EVRCWB0"
"audio/EVRCWB1"
"audio/EVRCB"
"audio/EVRCB0"
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC5215
08/2008
(26 p.)
pdf(2p)
|
L. Barbato |
|
RTP Payload Format for Vorbis Encoded Audio |
This document describes an RTP payload format for transporting Vorbis
encoded audio. It details the RTP encapsulation mechanism for raw
Vorbis data and the delivery mechanisms for the decoder probability
model (referred to as a codebook), as well as other setup
information.
Also included within this memo are media type registrations and the
details necessary for the use of Vorbis with the Session Description
Protocol (SDP).
The "audio/vorbis" MIME media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5219
02/2008
(22 p.)
pdf(2p)
|
R. Finlayson |
|
A More Loss-Tolerant RTP Payload Format for MP3 Audio |
This document describes an RTP (Real-Time Protocol) payload format
for transporting MPEG (Moving Picture Experts Group) 1 or 2, layer
III audio (commonly known as "MP3"). This format is an alternative
to that described in RFC2250, and performs better if there is packet
loss. This document obsoletes RFC 3119, correcting typographical
errors in the "SDP usage" section and pseudo-code appendices.
The "audio/mpa-robust" media type has been registered by the IANA.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5244
06/2008
(23 p.)
pdf(2p)
|
H. Schulzrinne
T. Taylor |
|
Definition of Events for Channel-Oriented Telephony Signalling |
|
This memo updates RFC4733 to add event codes for telephony signals
used for channel-associated signalling when carried in the telephony
event RTP payload. It supersedes and adds to the original assignment
of event codes for this purpose in Section 3.14 of RFC 2833. As
documented in Appendix A of RFC4733, some of the RFC 2833 events
have been deprecated because their specification was ambiguous,
erroneous, or redundant. In fact, the degree of change from Section
3.14 of RFC 2833 is such that implementations of the present document
will be fully backward compatible with RFC 2833 implementations only
in the case of full ABCD-bit signalling. This document expands and
improves the coverage of signalling systems compared to RFC 2833.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC5285
07/2008
(17 p.)
pdf(2p)
|
D. Singer
H. Desineni |
|
A General Mechanism for RTP Header Extensions |
|
This document provides a general mechanism to use the header
extension feature of RTP (the Real-Time Transport Protocol). It
provides the option to use a small number of small extensions in each
RTP packet, where the universe of possible extensions is large and
registration is de-centralized. The actual extensions in use in a
session are signaled in the setup information for that session.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5371
10/2008
(31 p.)
pdf(2p)
|
S. Futemma
E. Itakura
A. Leung |
|
RTP Payload Format for JPEG 2000 Video Streams |
|
This memo describes an RTP payload format for the ISO/IEC
International Standard 15444-1 | ITU-T Rec. T.800, better known as
JPEG 2000. JPEG 2000 features are considered in the design of this
payload format. JPEG 2000 is a truly scalable compression technology
allowing applications to encode once and decode many different ways.
The JPEG 2000 video stream is formed by extending from a single image
to a series of JPEG 2000 images.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5372
10/2008
(26 p.)
pdf(2p)
|
A. Leung
S. Futemma
E. Itakura |
|
Payload Format for JPEG 2000 Video:
Extensions for Scalability and Main Header Recovery |
This memo describes extended uses for the payload header in "RTP
Payload Format for JPEG 2000 Video Streams" as specified in RFC 5371,
for better support of JPEG 2000 features such as scalability and main
header recovery.
This memo must be accompanied with a complete implementation of "RTP
Payload Format for JPEG 2000 Video Streams". That document is a
complete description of the payload header and signaling, this
document only describes additional processing for the payload header.
There is an additional media type and Session Description Protocol
(SDP) marker signaling for implementations of this document.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5404
01/2009
(27 p.)
pdf(2p)
|
M. Westerlund
I. Johansson |
|
RTP Payload Format for G.719 |
|
This document specifies the payload format for packetization of the
G.719 full-band codec encoded audio signals into the Real-time
Transport Protocol (RTP). The payload format supports transmission
of multiple channels, multiple frames per payload, and interleaving.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5450
03/2009
(8 p.)
pdf(2p)
|
D. Singer
H. Desineni |
|
Transmission Time Offsets in RTP Streams |
|
This document describes a method to inform Real-time Transport
Protocol (RTP) clients when RTP packets are transmitted at a time
other than their 'nominal' transmission time. It also provides a
mechanism to provide improved inter-arrival jitter reports from the
clients, that take into account the reported transmission times.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5484
03/2009
(13 p.)
pdf(2p)
|
D. Singer |
|
Associating Time-Codes with RTP Streams |
|
This document describes a mechanism for associating %time-codes, as
defined by the Society of Motion Picture and Television Engineers
(SMPTE), with media streams in a way that is independent of the RTP
payload format of the media stream itself.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5506
04/2009
(17 p.)
pdf(2p)
|
I. Johansson
M. Westerlund |
|
Support for Reduced-Size RTCP: Opportunities and Consequences |
|
This memo discusses benefits and issues that arise when allowing
Real-time Transport Protocol (RTCP) packets to be transmitted with
reduced size. The size can be reduced if the rules on how to create
compound packets outlined in RFC 3550 are removed or changed. Based
on that analysis, this memo defines certain changes to the rules to
allow feedback messages to be sent as Reduced-Size RTCP packets under
certain conditions when using the RTP/AVPF (Real-time Transport
Protocol / Audio-Visual Profile with Feedback) profile (RFC 4585).
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC5574
06/2009
(14 p.)
pdf(2p)
|
G. Herlein
J. Valin
A. Heggestad
A. Moizard |
|
RTP Payload Format for the Speex Codec |
|
Speex is an open-source voice codec suitable for use in VoIP (Voice
over IP) type applications. This document describes the payload
format for Speex-generated bit streams within an RTP packet. Also
included here are the necessary details for the use of Speex with the
Session Description Protocol (SDP).
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5577
07/2009
(11 p.)
pdf(2p)
|
P. Luthi
R. Even |
|
RTP Payload Format for ITU-T Recommendation G.722.1 |
|
International Telecommunication Union (ITU-T) Recommendation G.722.1
is a wide-band audio codec. This document describes the payload
format for including G.722.1-generated bit streams within an RTP
packet. The document also describes the syntax and semantics of the
Session Description Protocol (SDP) parameters needed to support
G.722.1 audio codec.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5584
07/2009
(30 p.)
pdf(2p)
|
M. Hatanaka
J. Matsumoto |
|
RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) Family |
|
This document describes an RTP payload format for efficient and
flexible transporting of audio data encoded with the Adaptive
TRansform Audio Coding (ATRAC) family of codecs. Recent enhancements
to the ATRAC family of codecs support high-quality audio coding with
multiple channels. The RTP payload format as presented in this
document also includes support for data fragmentation, elementary
redundancy measures, and a variation on scalable streaming.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5669
08/2010
(13 p.)
pdf(2p)
|
S. Yoon
J. Kim
H. Park
H. Jeong
Y. Won |
|
The SEED Cipher Algorithm and its use with SRTP |
|
This document describes the use of the SEED block cipher algorithm in
the Secure Real-time Transport Protocol (SRTP) for providing
confidentiality for Real-time Transport Protocol (RTP) traffic
and for the control traffic for RTP, the Real-time Transport Control
Protocol (RTCP).
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5691
10/2009
(12 p.)
pdf(2p)
|
F. de Bont
S. Doehla
M. Schmidt
R. Sperschneider |
|
RTP Payload Format for Elementary Streams with MPEG Surround Multi-Channel Audio |
|
This memo describes extensions for the RTP payload format defined in
RFC 3640 for the transport of MPEG Surround multi-channel audio.
Additional Media Type parameters are defined to signal backwards-compatible
transmission inside an MPEG-4 Audio elementary stream. In
addition, a layered transmission scheme that doesn't use the MPEG-4
systems framework is presented to transport an MPEG Surround
elementary stream via RTP in parallel with an RTP stream containing
the downmixed audio data.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5725
02/2010
(9 p.)
pdf(2p)
|
A. Begen
D. Hsu
M. Lague |
|
Post-Repair Loss RLE Report Block Type for RTCP Extended Reports (XRs) |
|
This document defines a new report block type within the framework of
RTP Control Protocol (RTCP) Extended Reports (XRs). One of the
initial XR report block types is the Loss Run Length Encoding (RLE)
Report Block. This report conveys information regarding the
individual Real-time Transport Protocol (RTP) packet receipt and loss
events experienced during the RTCP interval preceding the
transmission of the report. The new report, which is referred to as
the Post-repair Loss RLE report, carries information regarding the
packets that remain lost after all loss-repair methods are applied.
By comparing the RTP packet receipts/losses before and after the loss
repair is completed, one can determine the effectiveness of the loss-repair
methods in an aggregated fashion. This document also defines
the signaling of the Post-repair Loss RLE report in the Session
Description Protocol (SDP).
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5760
02/2010
(66 p.)
pdf(2p)
|
J. Ott
J. Chesterfield
E. Schooler |
|
RTCP Extensions for Single-Source Multicast Sessions with Unicast Feedback |
|
This document specifies an extension to the Real-time Transport
Control Protocol (RTCP) to use unicast feedback to a multicast
sender. The proposed extension is useful for single-source multicast
sessions such as Source-Specific Multicast (SSM) communication where
the traditional model of many-to-many group communication is either
not available or not desired. In addition, it can be applied to any
group that might benefit from a sender-controlled summarized
reporting mechanism.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5761
04/2010
(13 p.)
pdf(2p)
|
C. Perkins
M. Westerlund |
|
Multiplexing RTP Data and Control Packets on a Single Port |
|
This memo discusses issues that arise when multiplexing RTP data
packets and RTP Control Protocol (RTCP) packets on a single UDP port.
It updates RFC 3550 and RFC 3551 to describe when such multiplexing
is and is not appropriate, and it explains how the Session
Description Protocol (SDP) can be used to signal multiplexed
sessions.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
