idnits 2.17.1 draft-terriberry-avp-codecs-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC3551], [RFC3711], [RFC4585], [RFC5124]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC3551, updated by this document, for RFC5378 checks: 1997-03-27) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 7, 2012) is 4279 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 avtcore T. Terriberry 3 Internet-Draft Mozilla Corporation 4 Updates: 3551 (if approved) August 7, 2012 5 Intended status: Standards Track 6 Expires: February 8, 2013 8 Update to Recommended Codecs for the AVP RTP Profile 9 draft-terriberry-avp-codecs-00 11 Abstract 13 [RFC3551] defines the AVP RTP profile, which is the basis for many 14 other profiles, such as SAVP [RFC3711], AVPF [RFC4585], and SAVPF 15 [RFC5124]. This document updates [RFC3551] (and by extension, the 16 profiles that build upon it) to reflect changes in audio codec usage 17 since the document was originally published. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on February 8, 2013. 36 Copyright Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 3. Updates to RFC 3551 . . . . . . . . . . . . . . . . . . . . . 5 56 3.1. Updates to Section 6 . . . . . . . . . . . . . . . . . . . 5 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 58 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 59 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 60 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 61 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 62 7.2. Informative References . . . . . . . . . . . . . . . . . . 9 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 65 1. Introduction 67 [RFC3551] says that audio applications operating under the AVP 68 profile SHOULD be able to send and receive PCMU and DVI4. However, 69 in practice, many RTP deployments do not support DVI4, and its 70 utility is limited in the presence of much more modern codecs. This 71 document updates the recommended audio codec selection for the AVP 72 profile to remove the SHOULD for DVI4. 74 2. Terminology 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 77 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 78 document are to be interpreted as described in [RFC2119]. 80 3. Updates to RFC 3551 82 The text of [RFC3551] is hereby updated as set forth below. 84 3.1. Updates to Section 6 86 In the final paragraph of Section 6, replace, "payload types 0 (PCMU) 87 and 5 (DVI4)," with "payload type 0 (PCMU)." Also, add a final 88 sentence to this paragraph that states, "Some environments may make 89 support for PCMU mandatory." 91 4. Security Considerations 93 This document does not introduce any new security considerations for 94 [RFC3551]. 96 5. IANA Considerations 98 This document has no actions for IANA. 100 6. Acknowledgments 102 Thanks to Colin Perkins for suggesting this update. 104 7. References 106 7.1. Normative References 108 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 109 Requirement Levels", BCP 14, RFC 2119, March 1997. 111 [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and 112 Video Conferences with Minimal Control", STD 65, RFC 3551, 113 July 2003. 115 7.2. Informative References 117 [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. 118 Norrman, "The Secure Real-time Transport Protocol (SRTP)", 119 RFC 3711, March 2004. 121 [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, 122 "Extended RTP Profile for Real-time Transport Control 123 Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, 124 July 2006. 126 [RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for 127 Real-time Transport Control Protocol (RTCP)-Based Feedback 128 (RTP/SAVPF)", RFC 5124, February 2008. 130 Author's Address 132 Timothy B. Terriberry 133 Mozilla Corporation 134 650 Castro Street 135 Mountain View, CA 94041 136 USA 138 Phone: +1 650 903-0800 139 Email: tterribe@xiph.org