idnits 2.17.1 draft-ietf-avt-rtp-amr-13.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3267 5 Title: Real-Time Transport Protocol (RTP) Payload Format 6 and File Storage Format for the Adaptive 7 Multi-Rate (AMR) and Adaptive Multi-Rate Wideband 8 (AMR-WB) Audio Codecs 9 Author(s): J. Sjoberg, M. Westerlund, A. Lakaniemi, Q. Xie 10 Status: Standards Track 11 Date: June 2002 12 Mailbox: Johan.Sjoberg@ericsson.com, 13 Magnus.Westerlund@ericsson.com, 14 ari.lakaniemi@nokia.com, qxie1@email.mot.com 15 Pages: 49 16 Characters: 110652 17 Updates/Obsoletes/SeeAlso: None 19 I-D Tag: draft-ietf-avt-rtp-amr-13.txt 21 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3267.txt 23 This document specifies a real-time transport protocol (RTP) 24 payload format to be used for Adaptive Multi-Rate (AMR) and 25 Adaptive Multi-Rate Wideband (AMR-WB) encoded speech 26 signals. The payload format is designed to be able to interoperate 27 with existing AMR and AMR-WB transport formats on non-IP 28 networks. In addition, a file format is specified for transport of 29 AMR and AMR-WB speech data in storage mode applications such as 30 email. Two separate MIME type registrations are included, one for 31 AMR and one for AMR-WB, specifying use of both the RTP payload 32 format and the storage format. 34 This document is a product of the Audio/Video Transport Working Group 35 of the IETF. 37 This is now a Proposed Standard Protocol. 39 This document specifies an Internet standards track protocol for 40 the Internet community, and requests discussion and suggestions 41 for improvements. Please refer to the current edition of the 42 "Internet Official Protocol Standards" (STD 1) for the 43 standardization state and status of this protocol. Distribution 44 of this memo is unlimited. 46 This announcement is sent to the IETF list and the RFC-DIST list. 47 Requests to be added to or deleted from the IETF distribution list 48 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 49 added to or deleted from the RFC-DIST distribution list should 50 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 52 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 53 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 54 help: ways_to_get_rfcs. For example: 56 To: rfc-info@RFC-EDITOR.ORG 57 Subject: getting rfcs 59 help: ways_to_get_rfcs 61 Requests for special distribution should be addressed to either the 62 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 63 specifically noted otherwise on the RFC itself, all RFCs are for 64 unlimited distribution.echo 65 Submissions for Requests for Comments should be sent to 66 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 67 Authors, for further information.