<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>draft-valin-celt-rtp-profile-01</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="draft-valin-celt-rtp-profile-01">
<meta name="keywords" content="I-D, Internet-Draft, CELT, RTP">
<meta name="generator" content="xml2rfc v1.33 (http://xml.resource.org/)">
<style type='text/css'><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: small; color: #000; background-color: #FFF;
margin: 2em;
}
h1, h2, h3, h4, h5, h6 {
font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
font-weight: bold; font-style: normal;
}
h1 { color: #900; background-color: transparent; text-align: right; }
h3 { color: #333; background-color: transparent; }
td.RFCbug {
font-size: x-small; text-decoration: none;
width: 30px; height: 30px; padding-top: 2px;
text-align: justify; vertical-align: middle;
background-color: #000;
}
td.RFCbug span.RFC {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: bold; color: #666;
}
td.RFCbug span.hotText {
font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: normal; text-align: center; color: #FFF;
}
table.TOCbug { width: 30px; height: 15px; }
td.TOCbug {
text-align: center; width: 30px; height: 15px;
color: #FFF; background-color: #900;
}
td.TOCbug a {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
font-weight: bold; font-size: x-small; text-decoration: none;
color: #FFF; background-color: transparent;
}
td.header {
font-family: arial, helvetica, sans-serif; font-size: x-small;
vertical-align: top; width: 33%;
color: #FFF; background-color: #666;
}
td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
td.author-text { font-size: x-small; }
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a { font-weight: bold; }
a:link { color: #900; background-color: transparent; }
a:visited { color: #633; background-color: transparent; }
a:active { color: #633; background-color: transparent; }
p { margin-left: 2em; margin-right: 2em; }
p.copyright { font-size: x-small; }
p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
ol.text { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
/* RFC-2629 <spanx>s and <artwork>s. */
em { font-style: italic; }
strong { font-weight: bold; }
dfn { font-weight: bold; font-style: normal; }
cite { font-weight: normal; font-style: normal; }
tt { color: #036; }
tt, pre, pre dfn, pre em, pre cite, pre span {
font-family: "Courier New", Courier, monospace; font-size: small;
}
pre {
text-align: left; padding: 4px;
color: #000; background-color: #CCC;
}
pre dfn { color: #900; }
pre em { color: #66F; background-color: #FFC; font-weight: normal; }
pre .key { color: #33C; font-weight: bold; }
pre .id { color: #900; }
pre .str { color: #000; background-color: #CFF; }
pre .val { color: #066; }
pre .rep { color: #909; }
pre .oth { color: #000; background-color: #FCF; }
pre .err { background-color: #FCC; }
/* RFC-2629 <texttable>s. */
table.all, table.full, table.headers, table.none {
font-size: small; text-align: center; border-width: 2px;
vertical-align: top; border-collapse: collapse;
}
table.all, table.full { border-style: solid; border-color: black; }
table.headers, table.none { border-style: none; }
th {
font-weight: bold; border-color: black;
border-width: 2px 2px 3px 2px;
}
table.all th, table.full th { border-style: solid; }
table.headers th { border-style: none none solid none; }
table.none th { border-style: none; }
table.all td {
border-style: solid; border-color: #333;
border-width: 1px 2px;
}
table.full td, table.headers td, table.none td { border-style: none; }
hr { height: 1px; }
hr.insert {
width: 80%; border-style: none; border-width: 0;
color: #CCC; background-color: #CCC;
}
--></style>
</head>
<body>
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<tr><td class="header">AVT Working Group</td><td class="header">J-M. Valin</td></tr>
<tr><td class="header">Internet-Draft</td><td class="header">Octasic Semiconductor</td></tr>
<tr><td class="header">Expires: May 24, 2009</td><td class="header">et. al.</td></tr>
<tr><td class="header"> </td><td class="header">November 20, 2008</td></tr>
</table></td></tr></table>
<h1><br />draft-valin-celt-rtp-profile-01<br />RTP Payload Format for the CELT Codec</h1>
<h3>Status of this Memo</h3>
<p>
This document is an Internet-Draft and is subject to all provisions
of Section 3 of RFC 3667.
By submitting this Internet-Draft,
each author represents that any applicable patent or other IPR claims of which
he or she is aware have been or will be disclosed,
and any of which he or she become aware will be disclosed,
in accordance with RFC 3668.</p>
<p>
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups.
Note that other groups may also distribute working documents as
Internet-Drafts.</p>
<p>
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any time.
It is inappropriate to use Internet-Drafts as reference material or to cite
them other than as “work in progress.”</p>
<p>
The list of current Internet-Drafts can be accessed at
<a href='http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/ietf/1id-abstracts.txt</a>.</p>
<p>
The list of Internet-Draft Shadow Directories can be accessed at
<a href='http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html</a>.</p>
<p>
This Internet-Draft will expire on May 24, 2009.</p>
<h3>Abstract</h3>
<p>
CELT is an open-source voice codec suitable for use in very low delay
Voice over IP (VoIP) type applications. This document describes the payload
format for CELT generated bit streams within an RTP packet. Also
included here are the necessary details for the use of CELT with
the Session Description Protocol (SDP). At the time of this writing, the CELT
bit-stream has NOT been finalized yet, and compatibility is usually broken with
every new release of the codec.
</p><a name="toc"></a><br /><hr />
<h3>Table of Contents</h3>
<p class="toc">
<a href="#Conventions used in this document">1.</a>
Conventions used in this document<br />
<a href="#Overview of the CELT Codec">2.</a>
Overview of the CELT Codec<br />
<a href="#RTP payload format for CELT">3.</a>
RTP payload format for CELT<br />
<a href="#RTP Header">4.</a>
RTP Header<br />
<a href="#CELT payload">5.</a>
CELT payload<br />
<a href="#Example CELT packet">6.</a>
Example CELT packet<br />
<a href="#Multiple CELT frames in a RTP packet">7.</a>
Multiple CELT frames in a RTP packet<br />
<a href="#MIME registration of CELT">8.</a>
MIME registration of CELT<br />
<a href="#SDP usage of CELT">9.</a>
SDP usage of CELT<br />
<a href="#Issues that need to be addressed">10.</a>
Issues that need to be addressed<br />
<a href="#RTP Payload Types">11.</a>
RTP Payload Types<br />
<a href="#Security Considerations">12.</a>
Security Considerations<br />
<a href="#Acknowledgments">13.</a>
Acknowledgments<br />
<a href="#rfc.references1">14.</a>
References<br />
<a href="#rfc.references1">14.1.</a>
Normative References<br />
<a href="#rfc.references2">14.2.</a>
Informative References<br />
<a href="#rfc.authors">§</a>
Authors' Addresses<br />
<a href="#rfc.copyright">§</a>
Intellectual Property and Copyright Statements<br />
</p>
<br clear="all" />
<a name="Conventions used in this document"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1"></a><h3>1.
Conventions used in this document</h3>
<p>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 <a class='info' href='#rfc2119'>[rfc2119]<span> (</span><span class='info'>Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” .</span><span>)</span></a>.
</p>
<a name="Overview of the CELT Codec"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2"></a><h3>2.
Overview of the CELT Codec</h3>
<p>
CELT stands for "Constrained Energy Lapped Transform". It applies some of the CELP principles, but does everything in the frequency domain, which removes some of the limitations of CELP. CELT is suitable for both speech and music and currently features:
</p>
<p>
</p>
<ul class="text">
<li>Ultra-low latency (typically from 3 to 9 ms)
</li>
<li>Full audio bandwidth (44.1 kHz and 48 kHz)
</li>
<li>Support for both voice and music
</li>
<li>Stereo support
</li>
<li>Packet loss concealment
</li>
<li>Constant bit-rates from 32 kbps to 128 kbps and above
</li>
<li>Free software/open-source
</li>
</ul><p>
</p>
<a name="RTP payload format for CELT"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3"></a><h3>3.
RTP payload format for CELT</h3>
<p>
For RTP based transportation of CELT encoded audio the standard
RTP header [2] is followed by one or more payload data blocks.
An optional padding terminator may also be used.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RTP Header |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| one or more frames of CELT .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| one or more frames of CELT .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre></div>
<a name="RTP Header"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.4"></a><h3>4.
RTP Header</h3>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=2|P|X| CC |M| PT | sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| synchronization source (SSRC) identifier |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| contributing source (CSRC) identifiers |
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre></div>
<p>
The RTP header begins with an octet of fields (V, P, X, and CC) to
support specialized RTP uses (see <a class='info' href='#rfc3550'>[rfc3550]<span> (</span><span class='info'>Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, “RTP: A Transport Protocol for real-time applications,” .</span><span>)</span></a> and <a class='info' href='#rfc3551'>[rfc3551]<span> (</span><span class='info'>Schulzrinne, H. and S. Casner, “RTP Profile for Audio and Video Conferences with Minimal Control.,” .</span><span>)</span></a> for details). For
CELT the following values are used.
</p>
<p>Version (V): 2 bits
</p>
<p>
This field identifies the version of RTP. The version
used by this specification is two <a class='info' href='#rfc3550'>[rfc3550]<span> (</span><span class='info'>Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, “RTP: A Transport Protocol for real-time applications,” .</span><span>)</span></a>.
</p>
<p>Padding (P): 1 bit
</p>
<p>
If the padding bit is set, the packet contains one or more
additional padding octets at the end which are not part of
the payload. P is set if the total packet size is less than
the MTU.
</p>
<p>Extension (X): 1 bit
</p>
<p>
If the extension, X, bit is set, the fixed header MUST be
followed by exactly one header extension, with a format defined
in Section 5.3.1. of <a class='info' href='#rfc3550'>[rfc3550]<span> (</span><span class='info'>Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, “RTP: A Transport Protocol for real-time applications,” .</span><span>)</span></a>.
</p>
<p>CSRC count (CC): 4 bits
</p>
<p>
The CSRC count contains the number of CSRC identifiers.
</p>
<p>Marker (M): 1 bit
</p>
<p>
The M bit indicates if the packet contains comfort noise. This
field is used in conjunction with the cng SDP attribute and is
detailed further in section 5 below. In normal usage this bit
is set if the packet contains comfort noise.
</p>
<p>Payload Type (PT): 7 bits
</p>
<p>
An RTP profile for a class of applications is expected to assign
a payload type for this format, or a dynamically allocated
payload type SHOULD be chosen which designates the payload as
CELT.
</p>
<p>Sequence number: 16 bits
</p>
<p>
The sequence number increments by one for each RTP data packet
sent, and may be used by the receiver to detect packet loss and
to restore packet sequence. This field is detailed further in
<a class='info' href='#rfc3550'>[rfc3550]<span> (</span><span class='info'>Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, “RTP: A Transport Protocol for real-time applications,” .</span><span>)</span></a>.
</p>
<p>Timestamp: 32 bits
</p>
<p>
A timestamp representing the sampling time of the first sample of
the first CELT packet in the RTP packet. The clock frequency
MUST be set to the sample rate of the encoded audio data.
CELT can use different frame sizes and a variable sampling rate clock.
The RTP timestamp MUST be in units of 1/X of a second where X
is the sample rate used.
</p>
<p>SSRC/CSRC identifiers:
</p>
<p>
These two fields, 32 bits each with one SSRC field and a maximum
of 16 CSRC fields, are as defined in <a class='info' href='#rfc3550'>[rfc3550]<span> (</span><span class='info'>Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, “RTP: A Transport Protocol for real-time applications,” .</span><span>)</span></a>.
</p>
<a name="CELT payload"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5"></a><h3>5.
CELT payload</h3>
<p>
For the purposes of packetizing the bit stream in RTP, it is only
necessary to consider the sequence of bits as output by the CELT
encoder <a class='info' href='#celt-website'>[celt‑website]<span> (</span><span class='info'>, “The CELT ultra-low delay audio codec,” .</span><span>)</span></a>, and present the same sequence to the decoder. The
payload format described here maintains this sequence.
</p>
<p>
A typical CELT frame, encoded at a high bitrate, is approx.
128 octets and the total number of CELT frames SHOULD be kept
less than the path MTU to prevent fragmentation. CELT frames MUST
NOT be fragmented across multiple RTP packets,
</p>
<p>
An RTP packet MAY contain CELT frames of the same bit rate or of
varying bit rates, since the bit-rate for a frame is implicitly
conveyed in band with the signal.
</p>
<p>
The encoding and decoding algorithm can change the bit rate at any
frame boundary, with the bit rate change notification provided
implicitly from the compressed frame size. No out-of-band
notification is required for the decoder to process changes in the
bit rate sent by the encoder.
</p>
<p>
It is RECOMMENDED that values of 32000, 44100 and 48000 be used
for most applications, unless a specific reason exists -- such as
requirements for a very specific packetization time. For example,
51200 Hz sampling may be useful to obtain a 5ms packetization time
with 256-sample frames.
</p>
<p>
The CELT codec always produces an integer number of bytes, so
no padding is ever required.
</p>
<a name="Example CELT packet"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.6"></a><h3>6.
Example CELT packet</h3>
<p>
In the example below we have a single CELT frame in the RTP packet.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=2|P|X| CC |M| PT | sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| synchronization source (SSRC) identifier |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| contributing source (CSRC) identifiers |
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ..celt data.. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ..celt data.. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre></div>
<a name="Multiple CELT frames in a RTP packet"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.7"></a><h3>7.
Multiple CELT frames in a RTP packet</h3>
<p>
The bit-rate used by CELT is implicitly determined by the size of the
compressed data. When more than one frame is encoded in the same packet,
it is not possible to determine the size of each encoded frame, so the
information must be explicitly encoded. If N frames are present in a
packet, N-1 values compressed frame sizes need to be encoded at the
beginning of the packet. Each size that is less than 255 bytes is encoded
in one byte. For sizes greater or equal to 255, a 0xff byte is encoded,
followed by the size-255. Multiple 0xff bytes are allowed if there are
more than 510 bytes transmitted. A size of zero indicates silence for the
current frame.
</p>
<p>
Below is an example of two CELT frames contained within one RTP
packet.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=2|P|X| CC |M| PT | sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| synchronization source (SSRC) identifier |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| contributing source (CSRC) identifiers |
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| length | ..celt data.. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ..celt data.. | ..celt data.. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ..celt data.. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre></div>
<a name="MIME registration of CELT"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.8"></a><h3>8.
MIME registration of CELT</h3>
<p>
Full definition of the MIME <a class='info' href='#rfc2045'>[rfc2045]<span> (</span><span class='info'>, “Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies,” .</span><span>)</span></a> type for CELT will be part of the Ogg
Vorbis MIME type definition application <a class='info' href='#rfc3534'>[rfc3534]<span> (</span><span class='info'>Walleij, L., “The application/ogg Media Type,” .</span><span>)</span></a>.
</p>
<p>MIME media type name: audio
</p>
<p>MIME subtype: celt
</p>
<p>Optional parameters:
</p>
<p>Required parameters: to be included in the Ogg MIME specification.
</p>
<p>Encoding considerations:
</p>
<p>Security Considerations:
</p>
<p>See Section 6 of RFC 3047.
</p>
<p>Interoperability considerations: none
</p>
<p>Published specification:
</p>
<p>Applications which use this media type:
</p>
<p>Additional information: none
</p>
<p>Person & email address to contact for further information:<br />
<br />
</p>
<blockquote class="text">
<p>Jean-Marc Valin <jean-marc.valin@octasic.com>
</p>
</blockquote><p>
</p>
<p>Intended usage: COMMON
</p>
<p>Author/Change controller:
</p>
<p>
</p>
<blockquote class="text">
<p>Author: Jean-Marc Valin <jean-marc.valin@octasic.com>
</p>
<p>Change controller: Jean-Marc Valin <jean-marc.valin@octasic.com>
</p>
<p>Change controller: IETF AVT Working Group
</p>
</blockquote><p>
</p>
<p>
This transport type signifies that the content is to be interpreted
according to this document if the contents are transmitted over RTP.
Should this transport type appear over a lossless streaming protocol
such as TCP, the content encapsulation should be interpreted as an
Ogg Stream in accordance with <a class='info' href='#rfc3534'>[rfc3534]<span> (</span><span class='info'>Walleij, L., “The application/ogg Media Type,” .</span><span>)</span></a>, with the exception that the
content of the Ogg Stream may be assumed to be CELT audio and
CELT audio only.
</p>
<a name="SDP usage of CELT"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.9"></a><h3>9.
SDP usage of CELT</h3>
<p>
When conveying information by SDP <a class='info' href='#rfc2327'>[rfc2327]<span> (</span><span class='info'>Jacobson, V. and M. Handley, “SDP: Session Description Protocol,” .</span><span>)</span></a>, the encoding name MUST be
set to "CELT". An example of the media representation in SDP for
offering a single channel of CELT at 48000 samples per second might
be:
</p><br />
<br />
<blockquote class="text">
<p>m=audio 8088 RTP/AVP 97
</p>
<p>a=rtpmap:97 CELT/48000
</p>
</blockquote>
<p>
Note that the RTP payload type code of 97 is defined in this media
definition to be 'mapped' to the CELT codec at a 48kHz sampling
frequency using the 'a=rtpmap' line. Any number from 96 to 127
could have been chosen (the allowed range for dynamic types).
</p>
<p>
The value of the sampling frequency is typically between 32000 and 48000 Hz.
</p>
<p>
If for some reason the offerer has bandwidth limitations, the client
may use the "b=" header, as explained in SDP <a class='info' href='#rfc2327'>[rfc2327]<span> (</span><span class='info'>Jacobson, V. and M. Handley, “SDP: Session Description Protocol,” .</span><span>)</span></a>. The following example
illustrates the case where the offerer cannot receive more than
10 kbit/s.
</p><br />
<br />
<blockquote class="text">
<p>m=audio 8088 RTP/AVP 97
</p>
<p>b=AS:10
</p>
<p>a=rtmap:97 CELT/48000
</p>
</blockquote>
<p>
In this case, if the remote part agrees, it should configure its
CELT encoder so that it does not use modes that produce more than
10 kbit/s. Note that the "b=" constraint also applies on all
payload types that may be proposed in the media line ("m=").
</p>
<p>
An other way to make recommendations to the remote CELT encoder
is to use its specific parameters via the a=fmtp: directive. The
following parameters are defined for use in this way:
</p><br />
<br />
<blockquote class="text">
<p>fsize: duration of each frame in samples (default is 256).<br />
<br />
</p>
<p>nframes: number of frames per packet (default is 1).<br />
<br />
</p>
<p>vbr: variable bit rate - either 'on' 'off' or 'vad'
(defaults to off). If on, variable bit rate is
enabled. If off, disabled.<br />
<br />
</p>
</blockquote>
<p>Examples:
</p><br />
<br />
<blockquote class="text">
<p>m=audio 8008 RTP/AVP 97
</p>
<p>a=rtpmap:97 CELT/44100
</p>
<p>a=fmtp:97 fsize=512;nframes=2
</p>
</blockquote>
<p>
This examples illustrate an offerer that wishes to receive
a CELT stream at 44100 Hz, by packing two 512-sample frames in each packet.
</p>
<p>
Several CELT specific parameters can be given in a single
a=fmtp line provided that they are separated by a semi-colon.
</p>
<p>
Care must be taken when setting the value of fsize and nframes so that the
RTP packet size does not exceed the path MTU.
</p>
<a name="Issues that need to be addressed"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.10"></a><h3>10.
Issues that need to be addressed</h3>
<p>
Do we allow "custom modes" where the entire mode data could be transmitted in
an initialization packet?
</p>
<p>
How do we minimize the possibility of encoder-decoder mode mismatch
</p>
<p>
Do we support more than 2 channels (and how)?
</p>
<a name="RTP Payload Types"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.11"></a><h3>11.
RTP Payload Types</h3>
<p>
Dynamic payload type codes MUST be negotiated 'out-of-band'
for the assignment of a dynamic payload type from the
range of 96-127.
</p>
<a name="Security Considerations"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.12"></a><h3>12.
Security Considerations</h3>
<p>
RTP packets using the payload format defined in this specification
are subject to the security considerations discussed in the RTP
specification <a class='info' href='#rfc3550'>[rfc3550]<span> (</span><span class='info'>Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, “RTP: A Transport Protocol for real-time applications,” .</span><span>)</span></a>, and any appropriate RTP profile. This implies
that confidentiality of the media streams is achieved by encryption.
Because the data compression used with this payload format is applied
end-to-end, encryption may be performed after compression so there is
no conflict between the two operations.
</p>
<p>
A potential denial-of-service threat exists for data encodings using
compression techniques that have non-uniform receiver-end
computational load. The attacker can inject pathological datagrams
into the stream which are complex to decode and cause the receiver to
be overloaded. However, this encoding does not exhibit any
significant non-uniformity.
</p>
<p>
As with any IP-based protocol, in some circumstances a receiver may
be overloaded simply by the receipt of too many packets, either
desired or undesired. Network-layer authentication may be used to
discard packets from undesired sources, but the processing cost of
the authentication itself may be too high.
</p>
<a name="Acknowledgments"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.13"></a><h3>13.
Acknowledgments</h3>
<p>
The authors would also like to thank the following members of the
CELT and AVT communities for their input:
</p>
<a name="rfc.references"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.14"></a><h3>14.
References</h3>
<a name="rfc.references1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>14.1. Normative References</h3>
<table width="99%" border="0">
<tr><td class="author-text" valign="top"><a name="rfc2119">[rfc2119]</a></td>
<td class="author-text">Bradner, S., “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>,” RFC 2119.</td></tr>
<tr><td class="author-text" valign="top"><a name="rfc3550">[rfc3550]</a></td>
<td class="author-text">Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, “<a href="http://tools.ietf.org/html/rfc3550">RTP: A Transport Protocol for real-time applications</a>,” RFC 3550.</td></tr>
<tr><td class="author-text" valign="top"><a name="rfc2045">[rfc2045]</a></td>
<td class="author-text">“<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>,” RFC 2045.</td></tr>
<tr><td class="author-text" valign="top"><a name="rfc2327">[rfc2327]</a></td>
<td class="author-text">Jacobson, V. and M. Handley, “<a href="http://tools.ietf.org/html/rfc2327">SDP: Session Description Protocol</a>,” RFC 2327.</td></tr>
<tr><td class="author-text" valign="top"><a name="H323">[H323]</a></td>
<td class="author-text">“Packet-based Multimedia Communications Systems,” ITU-T Recommendation H.323.</td></tr>
<tr><td class="author-text" valign="top"><a name="H245">[H245]</a></td>
<td class="author-text">“Control of communications between Visual Telephone Systems and Terminal Equipment,” ITU-T Recommendation H.245.</td></tr>
<tr><td class="author-text" valign="top"><a name="rfc3551">[rfc3551]</a></td>
<td class="author-text">Schulzrinne, H. and S. Casner, “<a href="http://tools.ietf.org/html/rfc3551">RTP Profile for Audio and Video Conferences with Minimal Control.</a>,” RFC 3551.</td></tr>
<tr><td class="author-text" valign="top"><a name="rfc3534">[rfc3534]</a></td>
<td class="author-text">Walleij, L., “<a href="http://tools.ietf.org/html/rfc3534">The application/ogg Media Type</a>,” RFC 3534.</td></tr>
</table>
<a name="rfc.references2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>14.2. Informative References</h3>
<table width="99%" border="0">
<tr><td class="author-text" valign="top"><a name="celt-website">[celt-website]</a></td>
<td class="author-text">“The CELT ultra-low delay audio codec,” CELT website http://www.celt-codec.org/.</td></tr>
</table>
<a name="rfc.authors"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>Authors' Addresses</h3>
<table width="99%" border="0" cellpadding="0" cellspacing="0">
<tr><td class="author-text"> </td>
<td class="author-text">Jean-Marc Valin</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Octasic Semiconductor</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">4101, Molson Street, suite 300</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Montreal, Quebec H1Y 3L1</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Canada</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:jean-marc.valin@octasic.com">jean-marc.valin@octasic.com</a></td></tr>
<tr cellpadding="3"><td> </td><td> </td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">et al.</td></tr>
</table>
<a name="rfc.copyright"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>Full Copyright Statement</h3>
<p class='copyright'>
Copyright © The IETF Trust (2008).</p>
<p class='copyright'>
This document is subject to the rights,
licenses and restrictions contained in BCP 78,
and except as set forth therein,
the authors retain all their rights.</p>
<p class='copyright'>
This document and the information contained herein are provided
on an “AS IS” basis and THE CONTRIBUTOR,
THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST
AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.</p>
<h3>Intellectual Property</h3>
<p class='copyright'>
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology
described in this document or the extent to which any license
under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any
such rights.
Information on the procedures with respect to
rights in RFC documents can be found in BCP 78 and BCP 79.</p>
<p class='copyright'>
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available,
or the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or
users of this specification can be obtained from the IETF on-line IPR
repository at <a href='http://www.ietf.org/ipr'>http://www.ietf.org/ipr</a>.</p>
<p class='copyright'>
The IETF invites any interested party to bring to its attention
any copyrights,
patents or patent applications,
or other
proprietary rights that may cover technology that may be required
to implement this standard.
Please address the information to the IETF at <a href='mailto:ietf-ipr@ietf.org'>ietf-ipr@ietf.org</a>.</p>
</body></html>