idnits 2.17.1 draft-ietf-avt-rtp-mime-06.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 3555 5 Title: MIME Type Registration of RTP Payload Formats 6 Author(s): S. Casner, P. Hoschka 7 Status: Standards Track 8 Date: July 2003 9 Mailbox: casner@acm.org, ph@w3.org 10 Pages: 45 11 Characters: 56618 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-avt-rtp-mime-06.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3555.txt 18 This document defines the procedure to register RTP Payload Formats 19 as audio, video or other MIME subtype names. This is useful in a 20 text-based format or control protocol to identify the type of an 21 RTP transmission. This document also registers all the RTP payload 22 formats defined in the RTP Profile for Audio and Video Conferences 23 as MIME subtypes. Some of these may also be used for transfer 24 modes other than RTP. 26 This document is a product of the Audio/Video Transport Working Group 27 of the IETF. 29 This is now a Proposed Standard Protocol. 31 This document specifies an Internet standards track protocol for 32 the Internet community, and requests discussion and suggestions 33 for improvements. Please refer to the current edition of the 34 "Internet Official Protocol Standards" (STD 1) for the 35 standardization state and status of this protocol. Distribution 36 of this memo is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.