Internet DRAFT - draft-terriberry-avp-codecs
draft-terriberry-avp-codecs
avtcore T. Terriberry
Internet-Draft Mozilla Corporation
Updates: 3551 (if approved) August 7, 2012
Intended status: Standards Track
Expires: February 8, 2013
Update to Recommended Codecs for the AVP RTP Profile
draft-terriberry-avp-codecs-00
Abstract
[RFC3551] defines the AVP RTP profile, which is the basis for many
other profiles, such as SAVP [RFC3711], AVPF [RFC4585], and SAVPF
[RFC5124]. This document updates [RFC3551] (and by extension, the
profiles that build upon it) to reflect changes in audio codec usage
since the document was originally published.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on February 8, 2013.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
Terriberry Expires February 8, 2013 [Page 1]
Internet-Draft AVP Codecs August 2012
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Updates to RFC 3551 . . . . . . . . . . . . . . . . . . . . . 5
3.1. Updates to Section 6 . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10
Terriberry Expires February 8, 2013 [Page 2]
Internet-Draft AVP Codecs August 2012
1. Introduction
[RFC3551] says that audio applications operating under the AVP
profile SHOULD be able to send and receive PCMU and DVI4. However,
in practice, many RTP deployments do not support DVI4, and its
utility is limited in the presence of much more modern codecs. This
document updates the recommended audio codec selection for the AVP
profile to remove the SHOULD for DVI4.
Terriberry Expires February 8, 2013 [Page 3]
Internet-Draft AVP Codecs August 2012
2. Terminology
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 [RFC2119].
Terriberry Expires February 8, 2013 [Page 4]
Internet-Draft AVP Codecs August 2012
3. Updates to RFC 3551
The text of [RFC3551] is hereby updated as set forth below.
3.1. Updates to Section 6
In the final paragraph of Section 6, replace, "payload types 0 (PCMU)
and 5 (DVI4)," with "payload type 0 (PCMU)." Also, add a final
sentence to this paragraph that states, "Some environments may make
support for PCMU mandatory."
Terriberry Expires February 8, 2013 [Page 5]
Internet-Draft AVP Codecs August 2012
4. Security Considerations
This document does not introduce any new security considerations for
[RFC3551].
Terriberry Expires February 8, 2013 [Page 6]
Internet-Draft AVP Codecs August 2012
5. IANA Considerations
This document has no actions for IANA.
Terriberry Expires February 8, 2013 [Page 7]
Internet-Draft AVP Codecs August 2012
6. Acknowledgments
Thanks to Colin Perkins for suggesting this update.
Terriberry Expires February 8, 2013 [Page 8]
Internet-Draft AVP Codecs August 2012
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and
Video Conferences with Minimal Control", STD 65, RFC 3551,
July 2003.
7.2. Informative References
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)",
RFC 3711, March 2004.
[RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,
"Extended RTP Profile for Real-time Transport Control
Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585,
July 2006.
[RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for
Real-time Transport Control Protocol (RTCP)-Based Feedback
(RTP/SAVPF)", RFC 5124, February 2008.
Terriberry Expires February 8, 2013 [Page 9]
Internet-Draft AVP Codecs August 2012
Author's Address
Timothy B. Terriberry
Mozilla Corporation
650 Castro Street
Mountain View, CA 94041
USA
Phone: +1 650 903-0800
Email: tterribe@xiph.org
Terriberry Expires February 8, 2013 [Page 10]
