draft-ietf-payload-rtp-aptx-03.txt   draft-ietf-payload-rtp-aptx-04.txt 
Internet-Draft J. Lindsay Internet-Draft J. Lindsay
A/V Transport Payloads Working Group H.Foerster A/V Transport Payloads Working Group H.Foerster
Intended status: Standards Track APT Ltd Intended status: Standards Track APT Ltd
Expires: April 21, 2014 October 22, 2013 Expires: May 04, 2014 November 05, 2013
RTP Payload Format for Standard apt-X and Enhanced apt-X Codecs RTP Payload Format for Standard apt-X and Enhanced apt-X Codecs
draft-ietf-payload-rtp-aptx-03 draft-ietf-payload-rtp-aptx-04
Abstract Abstract
This document specifies a scheme for packetizing Standard apt-X, or This document specifies a scheme for packetizing Standard apt-X, or
Enhanced apt-X, encoded audio data into Real-time Transport Protocol Enhanced apt-X, encoded audio data into Real-time Transport Protocol
(RTP) packets. The document describes a payload format that permits (RTP) packets. The document describes a payload format that permits
transmission of multiple related audio channels in a single RTP transmission of multiple related audio channels in a single RTP
payload, and a means of establishing Standard apt-X and Enhanced payload, and a means of establishing Standard apt-X and Enhanced
apt-X connections through the Session Description Protocol (SDP). apt-X connections through the Session Description Protocol (SDP).
skipping to change at page 1, line 44 skipping to change at page 1, line 44
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 21, 2014. This Internet-Draft will expire on May 04, 2014.
Submission Compliance for Internet-Drafts. Submission Compliance for Internet-Drafts.
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
skipping to change at page 9, line 19 skipping to change at page 9, line 19
sample for each audio channel. The encoder MUST be presented with sample for each audio channel. The encoder MUST be presented with
an integer number S of input audio samples, where S is an arbitrary an integer number S of input audio samples, where S is an arbitrary
multiple of 4. The encoder will produce exactly S/4 coded audio multiple of 4. The encoder will produce exactly S/4 coded audio
samples. Since each coded audio sample is either 16 or 24 bits, the samples. Since each coded audio sample is either 16 or 24 bits, the
amount of coded audio data produced upon each invocation of the amount of coded audio data produced upon each invocation of the
encoding process will be an integer number of bytes. RTP encoding process will be an integer number of bytes. RTP
packetization of the encoded data SHALL be on a byte-by-byte basis. packetization of the encoded data SHALL be on a byte-by-byte basis.
5.1. RTP Header Usage 5.1. RTP Header Usage
Utilisation of the Standard apt-X and Enhanced apt-X coding Utilization of the Standard apt-X and Enhanced apt-X coding
algorithms does not create any special requirements with respect to algorithms does not create any special requirements with respect to
the contents of the RTP packet header. Other RTP packet header the contents of the RTP packet header. Other RTP packet header
fields are defined as follows. fields are defined as follows.
o V - As per [RFC3550] o V - As per [RFC3550]
o P - As per [RFC3550] o P - As per [RFC3550]
o X - As per [RFC3550] o X - As per [RFC3550]
skipping to change at page 15, line 33 skipping to change at page 15, line 33
embedded-aux-channels: embedded-aux-channels:
Defines channels that carry embedded auxiliary data. Embedded- Defines channels that carry embedded auxiliary data. Embedded-
aux-channels are defined as a list of comma-separated values aux-channels are defined as a list of comma-separated values
that correspond to channel numbers in the range 1..channels. that correspond to channel numbers in the range 1..channels.
When a channel is stereo paired, embedded auxiliary data is When a channel is stereo paired, embedded auxiliary data is
shared across channels in the pair. The second channel as shared across channels in the pair. The second channel as
defined in stereo-channel-pairs MUST be specified in the defined in stereo-channel-pairs MUST be specified in the
embedded-autosync-channels list. embedded-autosync-channels list.
Encoding considerations: This type is only defined for transfer Encoding considerations: This media type is framed in RTP and
via RTP [RFC3550]. contains binary data; see Section 4.8 of [RFC6838].
Security considerations: See Section 5 of [RFC4855] and Section 4 Security considerations: See Section 5 of [RFC4855] and Section 4
of [RFC4856]. of [RFC4856].
Interoperability considerations: none Interoperability considerations: none
Published specification: RFC XXXX Published specification: RFC XXXX
Applications which use this media type: Audio streaming Applications which use this media type: Audio streaming
Fragment identifier considerations: None
Additional information: none Additional information: none
Person & email address to contact for further information: "John Person & email address to contact for further information: John
Lindsay email:lindsay@worldcastsystems.com" Lindsay email:lindsay@worldcastsystems.com
Intended usage: Common
Intended usage: RTP applications only Restrictions on usage: This media type depends on RTP framing,
and hence is only defined for transfer via RTP [RFC3550].
Author/Change controller: "IETF Payload Working Group delegated Author/Change controller: "IETF Payload Working Group delegated
from the IESG" from the IESG"
6.2. Mapping to SDP 6.2. Mapping to SDP
The information carried in the media type specification has a The information carried in the media type specification has a
specific mapping to fields in the Session Description Protocol (SDP) specific mapping to fields in the Session Description Protocol (SDP)
[RFC4566] that is commonly used to describe RTP sessions. When SDP [RFC4566] that is commonly used to describe RTP sessions. When SDP
is used to describe sessions the media type mappings are as follows. is used to describe sessions the media type mappings are as follows.
 End of changes. 8 change blocks. 
9 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/