"RTCP Extensions for Single-Source Multicast Sessions with Unicast Feedback", Joerg Ott, 7-Jan-08. ( bytes)

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. Ott et al. Internet Draft - Expires July 2008 [page 1] RTCP with Unicast Feedback

"RTP Payload Format for JPEG 2000 Video Streams", Satoshi Futemma, 24-Apr-08. ( bytes)

This memo describes an RTP payload format for the ISO/IEC International Standard 15444-1 | ITU-T Rec. T.800, otherwise 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. JPEG 2000 video stream is formed by extending from a single image to a series of JPEG 2000 images.

"RTP Payload Format for Adaptive TRansform Acoustic Coding (ATRAC) Family", Jun Matsumoto, Mitsuyuki Hatanaka, 8-Apr-08. ( bytes)

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.

"Definition of Events For Channel-Oriented Telephony Signalling", Tom Taylor, Henning Schulzrinne, 7-Jun-07. ( bytes)

This memo updates RFC 4733 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 RFC 2833 section 3.14. As documented in Appendix A of RFC 4733, certain of the RFC 2833 events have been deprecated, because their specification was ambiguous, erroneous or redundant. In fact, the degree of change from RFC 2833 section 3.14 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. The positive benefits of the present document are an expanded coverage of signalling systems and a more carefully specified and documented coverage of signalling systems covered by RFC 2833.

"Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery", Andrew Leung, 24-Apr-08. ( bytes)

This memo describes extended uses for payload header in RFC document: "RTP Payload Format for JPEG 2000 Video Streams." 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 SDP marker signaling for implementations of this document.

"A general mechanism for RTP Header Extensions", David Singer, HariKishan Desineni, 11-Mar-08. ( bytes)

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.

"Associating Time-codes with RTP streams", David Singer, 11-Mar-08. ( bytes)

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.

"RTP Payload Format for the Speex Codec", Greg Herlein, Jean-Marc Valin, Alfred Heggestad, Aymeric Moizard, 16-Feb-08. ( bytes)

Speex is an open-source voice codec suitable for use in Voice over IP (VoIP) 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).Editors Note All references to RFC XXXX are to be replaced by references to the RFC number of this memo, when published.

"RTP Payload Format for Vorbis Encoded Audio", Luca Barbato, 19-Feb-08. ( bytes)

This document describes an RTP payload format for transporting Vorbis encoded audio. It details the RTP encapsulation mechanism for raw Vorbis data and details the delivery mechanisms for the decoder probability model, referred to as a codebook and 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).

"How to Write an RTP Payload Format", Magnus Westerlund, 25-Feb-08. ( bytes)

This document contains information on how to best write an RTP payload format. Reading tips, design practices, and practical tips on how to quickly and with good results produce an RTP payload format specification. A template is also included with instructions that can be used when writing an RTP payload format.

"Transmission Time offsets in RTP streams", David Singer, HariKishan Desineni, 11-Mar-08. ( bytes)

This document describes a method to inform 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.

"Multiplexing RTP Data and Control Packets on a Single Port", Colin Perkins, Magnus Westerlund, 6-Aug-07. ( bytes)

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 to describe when such multiplexing is, and is not, appropriate, and explains how the Session Description Protocol (SDP) can be used to signal multiplexed sessions.

"RTCP XR - Video Metrics Report Blocks", Alan Clark, Amy Pendleton, 19-Nov-07. ( bytes)

This document defines extensions to the RTCP XR extended report packet type blocks to support the monitoring of video over IP for IPTV and videoconferencing endpoint reporting.

"RTP Payload Format for SVC Video", Stephan Wenger, Ye-Kui Wang, Thomas Schierl, 25-Feb-08. ( bytes)

This memo describes an RTP payload format for scalable video coding (SVC) defined in_Annex G of the ITU-T Recommendation H.264 video codec which is technically identical to Amendment 3 of ISO/IEC International Standard 14496-10. The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units, produced by the video encoder, in each RTP packet payload. The payload format has wide applicability, such as low bit-rate conversational, Internet video streaming, or high bit-rate entertainment quality video.

"RTP Payload Format for MIDI", John Lazzaro, John Wawrzynek, 14-Feb-08. ( bytes)

This memo describes a Real-time Transport Protocol (RTP) payload format for the MIDI (Musical Instrument Digital Interface) 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.

"RTCP HR - High Resolution VoIP Metrics Report Blocks", Alan Clark, Geoff Hunt, Amy Pendleton, Rajesh Kumar, Kevin Connor, 25-Feb-08. ( bytes)

This document defines extensions to the RTCP XR extended report packet type blocks to support Voice over IP (VoIP) monitoring for services that require higher resolution or more detailed metrics than those supported by RFC3611.

"RTP Payload Format for DV (IEC 61834) Video", Katsushi Kobayashi, Kazuhiro Mishima, Stephen Casner, Carsten Bormann, 24-Mar-08. ( bytes)

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 Obsoletes RFC 3189.

"RTP payload format for mU-law EMbedded Codec for Low-delay IP communication (UEMCLIP) speech codec", Yusuke Hiwasaki, Hitoshi Ohmuro, 25-Feb-08. ( bytes)

This document describes the RTP payload format of a mU-law EMbedded Coder for Low-delay IP communication (UEMCLIP), an enhanced speech codec of ITU-T G.711. The bitstream has a scalable structure with an embedded u-law bitstream, also known as PCMU, thus providing a handy transcoding operation between narrowband and wideband speech.

"Application Mechanism for maintaining alive the Network Address Translator (NAT) mappings associated to RTP flows.", Xavier Marjou, Aurelien Sollaud, 8-Apr-08. ( bytes)

This document lists the different mechanisms that enable applications using Real-time Transport Protocol (RTP) to maintain their RTP Network Address Translator (NAT) mappings alive. It also makes a recommendation for a preferred mechanism. This document is not applicable to Interactive Connectivity Establishment (ICE) agents.

"Parameters for Static Macroblocks and Aspect Ratio in the RTP Payload Format for H.264 Video", Tom Kristensen, Roni Even, 30-Jan-08. ( bytes)

This document updates RFC 3984. It defines new optional parameters addressing recent extensions currently supported in H.323 systems: The signalling of the maximum rate of static macroblocks a decoder is able to process. The signalling of the sample aspect ratio supported by the sender or the receiver.

"Datagram Transport Layer Security (DTLS) Extension to Establish Keys for Secure Real-time Transport Protocol (SRTP)", David McGrew, Eric Rescorla, 25-Feb-08. ( bytes)

This document describes a Datagram Transport Layer Security (DTLS) extension to establish keys for secure RTP (SRTP) and secure RTP Control Protocol (SRTCP) flows. DTLS keying happens on the media path, independent of any out-of-band signalling channel present.

"RTCP XR - Audio Metrics Report Block", Alan Clark, Amy Pendleton, 19-Nov-07. ( bytes)

This document defines extensions to the RTCP XR extended report packet type blocks to support the performance monitoring of audio streams transmitted using RTP.

"Forward-shifted RTP Redundancy Payload Support", Qiaobing Xie, Joe Schumacher, 17-Mar-08. ( bytes)

This document defines a simple enhancement to RFC 2198 to support RTP sessions with forward-shifted redundant encodings, i.e., redundant data is sent before the corresponding primary data. Forward-shifted redundancy can be used to conceal losses of a large number of consecutive media frames (e.g., consecutive loss of seconds or even tens of seconds of media).

"The SEED Cipher Algorithm and Its Use with the Secure Real-time Transport Protocol (SRTP)", Intellectual Property, 2-May-08. ( bytes)

This document describes the use of SEED block cipher algorithm in the Secure Real-time Transport Protocol (SRTP) for confidentiality to the RTP traffic and to the control traffic for RTP, the Real-time Transport Control Protocol (RTCP).

"Support for non-compound RTCP, opportunities and consequences", Ingemar Johansson, 24-Apr-08. ( bytes)

This memo discusses benefits and issues that arise when allowing RTCP packets to be transmitted as non-compound packets, i.e not follow the rules of RFC 3550. Based on that analysis this memo proposes changes to the rules to allow feedback messages to be sent as non-compound RTCP packets when using the RTP AVPF profile (RFC 4585) under certain conditions.

"RTP Payload Format for H.264 RCDO Video", Tom Kristensen, 27-Dec-07. ( bytes)

This memo describes an RTP Payload format for the Reduced-Complexity Decoding Operation (RCDO) for H.264 Baseline profile bitstreams, as specified in H.241. RCDO reduces the decoding cost and resource consumption of the video processing. The RTP Payload format is based on the description in RFC 3984.

"G.729.1 RTP Payload Format update: DTX support", Aurelien Sollaud, 8-Feb-08. ( bytes)

This document updates the Real-time Transport Protocol (RTP) payload format to be used for the International Telecommunication Union (ITU-T) Recommendation G.729.1 audio codec. It adds Discontinuous Transmission (DTX) support to the RFC 4749 specification, in a backward-compatible way. An updated media type registration is included for this payload format.

"RTP Payload Format for ITU-T Recommendation G.711.1", Aurelien Sollaud, 28-Apr-08. ( bytes)

This document specifies a Real-time Transport Protocol (RTP) payload format to be used for the International Telecommunication Union (ITU-T) G.711.1 audio codec. Two media type registrations are also included.

"RTP Payload Format for SPIRIT IP-MR Speech Codec Software", Andrey Setsko, 4-Apr-08. ( bytes)

This document specifies the payload format for packetization of SPIRIT IP-MR encoded speech signals into the Real-time Transport Protocol (RTP). The payload format supports transmission of multiple frames per payload, introduced redundancy for robustness against packet loss, and payload format extension for future versions compatibility.

Return to Internet-Draft directory.

Return to IETF home page.