draft-ietf-payload-rtp-aptx-04.txt   draft-ietf-payload-rtp-aptx-05.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: May 04, 2014 November 05, 2013 Expires: Aug 05, 2014 February 05, 2014
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-04 draft-ietf-payload-rtp-aptx-05
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 May 04, 2014. This Internet-Draft will expire on Aug 05, 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) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 20, line 4 skipping to change at page 19, line 28
However, the Standard apt-X and Enhanced apt-X audio coding However, the Standard apt-X and Enhanced apt-X audio coding
algorithms do not exhibit any significant non-uniformity. As with algorithms do not exhibit any significant non-uniformity. As with
any IP-based protocol, in some circumstances a receiver may be any IP-based protocol, in some circumstances a receiver may be
overloaded simply by the receipt of too many packets, either desired overloaded simply by the receipt of too many packets, either desired
or undesired. Network-layer authentication may be used to discard or undesired. Network-layer authentication may be used to discard
packets from undesired sources, but the processing cost of the packets from undesired sources, but the processing cost of the
authentication itself may be too high. In a multicast environment, authentication itself may be too high. In a multicast environment,
pruning of specific sources may be implemented in future versions of pruning of specific sources may be implemented in future versions of
IGMP [RFC3376] and in multicast routing protocols to allow a receiver IGMP [RFC3376] and in multicast routing protocols to allow a receiver
to select which sources are allowed to reach it. to select which sources are allowed to reach it.
[draft-ietf-avtcore-srtp-vbr-audio] has highlighted potential
security vulnerabilities of Variable Bit Rate (VBR) codecs using
Secure RTP transmission methods. As the Standard apt-X and Enhanced
apt-X codecs are Constant Bit Rate (CBR) codecs, this security
vulnerability is therefore not applicable.
9. Acknowledgements 9. Acknowledgements
This specification was facilitated by earlier documents produced by This specification was facilitated by earlier documents produced by
Greg Massey, David Trainer, James Hunter and Derrick Rea along with Greg Massey, David Trainer, James Hunter and Derrick Rea along with
practical tests carried out by Paul McCambridge of APT Ltd. practical tests carried out by Paul McCambridge of APT Ltd.
10. References 10. References
10.1. Normative References 10.1. Normative References
skipping to change at page 21, line 38 skipping to change at page 21, line 38
[RFC2198] Perkins, C., Kouvelas, I., Hodson, O., Hardman, V., [RFC2198] Perkins, C., Kouvelas, I., Hodson, O., Hardman, V.,
Handley, M., Bolot, J., Vega-Garcia, A., and S. Fosse- Handley, M., Bolot, J., Vega-Garcia, A., and S. Fosse-
Parisis, "RTP Payload for Redundant Audio Data", RFC 2198, Parisis, "RTP Payload for Redundant Audio Data", RFC 2198,
September 1997. September 1997.
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, October 2002. 3", RFC 3376, October 2002.
[RFC6838] Freed, N.,J. Klensin, and T. Hansen, "Media Type [RFC6838] Freed, N.,J. Klensin, and T. Hansen, "Media Type
Specifications andRegistration Procedures", BCP 13, Specifications and Registration Procedures", BCP 13,
RFC 6838, January 2013. RFC 6838, January 2013.
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, February 2007. Formats", RFC 4855, February 2007.
[RFC4856] Casner, S., "Media Type Registration of Payload Formats in [RFC4856] Casner, S., "Media Type Registration of Payload Formats in
the RTP Profile for Audio and Video Conferences", the RTP Profile for Audio and Video Conferences",
RFC 4856, February 2007. RFC 4856, February 2007.
[RFC5109] Li, A., "RTP Payload Format for Generic Forward Error [RFC5109] Li, A., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, December 2007. Correction", RFC 5109, December 2007.
[draft-ietf-avtcore-srtp-vbr-audio] Perkins, C., Valins, JM.,
"Guidelines for the Use of Variable Bit Rate Audio with
Secure RTP", draft-ietf-avtcore-srtp-vbr-audio, March 2012.
11. Authors' Addresses 11. Authors' Addresses
John Lindsay John Lindsay
APT Ltd APT Ltd
729 Springfield Road 729 Springfield Road
Belfast Belfast
Northern Ireland Northern Ireland
BT12 7FP BT12 7FP
UK UK
 End of changes. 7 change blocks. 
5 lines changed or deleted 14 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/