Update to Recommended Codecs for the AVP RTP Profile
draft-ietf-avtcore-avp-codecs-00

The information below is for an old version of the document
Document Type Active Internet-Draft (avtcore WG)
Last updated 2013-01-20
Replaces draft-terriberry-avp-codecs
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
avtcore                                                  T.B. Terriberry
Internet-Draft                                       Mozilla Corporation
Updates: 3551 (if approved)                             January 20, 2013
Intended status: Standards Track
Expires: July 24, 2013

          Update to Recommended Codecs for the AVP RTP Profile
                    draft-ietf-avtcore-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 July 24, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Terriberry               Expires July 24, 2013                  [Page 1]
Internet-Draft                 AVP Codecs                   January 2013

   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
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Updates to RFC 3551 . . . . . . . . . . . . . . . . . . . . .   2
     3.1.  Updates to Section 6  . . . . . . . . . . . . . . . . . .   2
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   3
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

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.

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].

3.  Updates to RFC 3551

   The text of [RFC3551] is hereby updated as set forth below.

3.1.  Updates to Section 6

Terriberry               Expires July 24, 2013                  [Page 2]
Internet-Draft                 AVP Codecs                   January 2013

   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."

4.  Security Considerations

   This document does not introduce any new security considerations for
   [RFC3551].

5.  IANA Considerations

   This document has no actions for IANA.

6.  Acknowledgments

   Thanks to Colin Perkins for suggesting this update.
Show full document text