idnits 2.17.1 draft-ietf-avtcore-avp-codecs-03.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 : ---------------------------------------------------------------------------- No issues found here. 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 (July 02, 2013) is 3941 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: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 avtcore T.B. Terriberry 3 Internet-Draft Mozilla Corporation 4 Updates: 3551 (if approved) July 02, 2013 5 Intended status: Standards Track 6 Expires: January 03, 2014 8 Update to Remove DVI4 from the Recommended Codecs for the RTP Profile 9 for Audio and Video Conferences with Minimal Control (RTP/AVP) 10 draft-ietf-avtcore-avp-codecs-03 12 Abstract 14 The RTP Profile for Audio and Video Conferences with Minimal Control 15 (RTP/AVP) is the basis for many other profiles, such as the Secure 16 Real-time Transport Protocol (RTP/SAVP), the Extended RTP Profile for 17 Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/ 18 AVPF), and the Extended Secure RTP Profile for RTCP-Based Feedback 19 (RTP/SAVPF). This document updates RFC 3551, the RTP/AVP profile 20 (and by extension, the profiles that build upon it) to reflect 21 changes in audio codec usage since the document was originally 22 published. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on January 03, 2014. 41 Copyright Notice 43 Copyright (c) 2013 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 60 3. Updates to RFC 3551 . . . . . . . . . . . . . . . . . . . . . 2 61 3.1. Updates to Section 6 . . . . . . . . . . . . . . . . . . 3 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 64 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 3 65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 7.1. Normative References . . . . . . . . . . . . . . . . . . 3 67 7.2. Informative References . . . . . . . . . . . . . . . . . 3 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 70 1. Introduction 72 [RFC3551] says that audio applications operating under the RTP/AVP 73 profile SHOULD be able to send and receive PCMU and DVI4. However, 74 in practice, many RTP deployments do not support DVI4, and there is 75 little reason to use it when much more modern codecs are available. 76 This document updates the recommended audio codec selection for the 77 RTP/AVP profile to remove the SHOULD for DVI4. By extension, this 78 also updates the profiles which build on RTP/AVP, including RTP/SAVP 79 [RFC3711], RTP/AVPF [RFC4585], and RTP/SAVPF [RFC5124]. 81 2. Terminology 83 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 84 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 85 document are to be interpreted as described in [RFC2119]. 87 3. Updates to RFC 3551 89 The following text of [RFC3551] is hereby updated as set forth below 90 in Section 3.1. 92 Audio applications operating under this profile SHOULD, at a 93 minimum, be able to send and/or receive payload types 0 (PCMU) and 94 5 (DVI4). This allows interoperability without format negotiation 95 and ensures successful negotiation with a conference control 96 protocol. 98 3.1. Updates to Section 6 100 In the final paragraph of Section 6, replace, "payload types 0 (PCMU) 101 and 5 (DVI4)," with "payload type 0 (PCMU)." Also, add a final 102 sentence to this paragraph that states, "Some environments 103 necessitate support for PCMU." This results in the following 104 paragraph: 106 Audio applications operating under this profile SHOULD, at a 107 minimum, be able to send and/or receive payload type 0 (PCMU). 108 This allows interoperability without format negotiation and 109 ensures successful negotiation with a conference control protocol. 110 Some environments necessitate support for PCMU. 112 4. Security Considerations 114 This document does not introduce any new security considerations for 115 [RFC3551]. 117 5. IANA Considerations 119 This document has no actions for IANA. 121 6. Acknowledgments 123 Thanks to Colin Perkins for suggesting this update. 125 7. References 127 7.1. Normative References 129 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 130 Requirement Levels", BCP 14, RFC 2119, March 1997. 132 [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and 133 Video Conferences with Minimal Control", STD 65, RFC 3551, 134 July 2003. 136 7.2. Informative References 138 [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. 139 Norrman, "The Secure Real-time Transport Protocol (SRTP)", 140 RFC 3711, March 2004. 142 [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, 143 "Extended RTP Profile for Real-time Transport Control 144 Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, July 145 2006. 147 [RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for 148 Real-time Transport Control Protocol (RTCP)-Based Feedback 149 (RTP/SAVPF)", RFC 5124, February 2008. 151 Author's Address 153 Timothy B. Terriberry 154 Mozilla Corporation 155 650 Castro Street 156 Mountain View, CA 94041 157 USA 159 Phone: +1 650 903-0800 160 Email: tterribe@xiph.org