Registration of the text/red MIME Sub-Type
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 4102.
|Last updated||2013-03-02 (Latest revision 2004-05-19)|
|RFC stream||Internet Engineering Task Force (IETF)|
|Additional resources||Mailing list discussion|
|IESG||IESG state||RFC 4102 (Proposed Standard)|
|Responsible AD||Allison J. Mankin|
|Send notices email@example.com, firstname.lastname@example.org|
Network Working Group Internet Draft P. Jones <draft-ietf-avt-text-red-05.txt> Cisco Systems, Inc. Expires: October 2004 May 2004 Registration of the text/red MIME Sub-Type Status of this Memo By submitting this Internet-Draft, I (we) certify that any applicable patent or other IPR claims of which I am (we are) aware have been disclosed and any of which I (we) become aware will be disclosed, in accordance with RFC 3668 (BCP 79). By submitting this Internet-Draft, I (we) accept the provisions of Section 3 of RFC 3667 (BCP 78). Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This document is a submission of the IETF AVT WG. Comments should be directed to the AVT WG mailing list, email@example.com. Abstract This document defines the text/red MIME sub-type. The actual RTP packetization for this MIME type is specified in RFC 2198. [Note to RFC Editor: All references to RFC XXXX are to be replaced by references to the RFC number of this memo when published.] 1. Introduction Jones Expires - October 2004 [Page 1] =0C Registration of the text/red MIME Sub-Type April 2004 Text is an important component of any multimedia communication system. Like audio, the transport of text can benefit from the use of redundancy in order to improve reliability and end-user experience. RFC 2198  defines an RTP  payload format for redundant audio data. The format defined in that document is quite suitable for providing redundancy for text, as well as audio. RFC 2793  specifies one usage of RFC 2198 and the text/red MIME type for the transport of redundant text data. This memo provides the MIME sub-type registration information for text/red. While this document focuses on the use of this MIME sub- type in SDP , the application of this MIME sub-type is not restricted to SDP. 2. Conventions used in this document 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 RFC 2119 . 3. IANA Considerations One new MIME sub-type is to be registered, as described below: MIME media type name: text MIME subtype name: RED Required parameters: rate: the RTP clock rate of the payload carried within the RTP packet. Typically, this rate is 1000, but other rates MAY be specified. This parameter MUST be set equal to the clock rate of the text payload format carried as the primary encoding. pt: a comma-separated ordered list of RTP payload types enumerating the primary, secondary, etc., in accordance with RFC 2198. Because comma is a special character, the list MUST be a quoted-string (enclosed in double quotes). For static payload types, each list element is simply the type number. For dynamic payload types, each list element is a mapping of the dynamic payload type number to an embedded MIME content- type specification for the payload format corresponding to the dynamic payload type. The format of the mapping is: dynamic-payload-type "=3D" content-type Jones Expires - October 2004 [Page 2] =0C Registration of the text/red MIME Sub-Type April 2004 If the content-type string includes a comma, then the content- type string MUST be a quoted-string. If the content-type string does not include a comma, it MAY still be quoted. Since it is part of the list which must itself be a quoted-string, that means the quotation marks MUST be quoted with backslash quoting as specified in RFC 2045 . If the content-type string itself contains a quoted-string, then the requirement for backslash quoting is recursively applied. Optional parameters: ptime, maxptime Encoding considerations: This type is only defined for transfer via RTP. Security considerations: Refer to section 5 of RFC XXXX. Interoperability considerations: none Published specification: RFC 2198 Applications which use this media type: Text streaming and conferencing tools. Additional information: none Person & email address to contact for further information: Paul E. Jones E-mail: firstname.lastname@example.org Intended usage: COMMON Author / Change controller: Paul E. Jones | IETF avt WG email@example.com | 4. Mapping to SDP Parameters The information carried in the MIME media type specification has a specific mapping to fields in the Session Description Protocol (SDP) , which is commonly used to describe RTP sessions. When SDP is used to specify sessions employing the RFC 2198 in a text session, the mapping is as follows: - The MIME type ("text") goes in SDP "m=3D" as the media name. - The value of the parameter "rate" goes in SDP "a=3Drtpmap". - The MIME subtype (RED) goes in SDP "a=3Drtpmap" as the encoding name. Jones Expires - October 2004 [Page 3] =0C Registration of the text/red MIME Sub-Type April 2004 - The parameters "ptime" and "maxptime" go in the SDP "a=3Dptime" and "a=3Dmaxptime" attributes, respectively. - The pt parameter is mapped to an a=3Dfmtp attribute by eliminating the parameter name (pt) and changing the commas to slashes. For example, 'pt=3D"101,102"' maps to 'a=3Dfmtp:99 101/102', where = '99' is the payload type of the redundancy frames. Note that the single quote marks (') used in this example is not present in the actual message encoding, but is present here only for readability. The level of redundancy is shown by the number of elements in the payload type list. Any dynamic payload type in the list MUST be represented by its payload type number and not by its content-type. The mapping of payload types to the content-type is done using the normal SDP procedures with "a=3Drtpmap". An example of SDP is: m=3Dtext 11000 RTP/AVP 98 100 a=3Drtpmap:98 t140/1000 a=3Drtpmap:100 red/1000 a=3Dfmtp:100 98/98 For each redundancy payload type defined, the ordering of the primary and redundancy encoding(s) is fixed. If more than one combination of primary and redundancy encoding(s) is desired, multiple redundancy payload types needs to be defined. 5. Security Considerations The security considerations listed in RFC 2198 apply. Further, it should be understood that text data, perhaps even more so than audio data, is susceptible to unwanted modification that may lead to undesired results. To prevent modification of the primary, secondary or header information, payload integrity protection over at least the complete RTP packet is RECOMMENDED, for example using SRTP . 6. Normative References  Perkins, C., et al., "RTP Payload for Redundant Audio Data", RFC 2198, September 1997.  Schulzrinne, et al., "RTP: A Transport Protocol for Real-Time Applications", RFC 3550, July 2003.  Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997. Jones Expires - October 2004 [Page 4] =0C Registration of the text/red MIME Sub-Type April 2004  Freed, N., Borenstein, N., "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.  Handley, M., Jackson, V., "SDP: Session Description Protocol", RFC 2327, April 1998.  Casner, S., Hoschka, P., "MIME Type Registration of RTP Payload Formats", RFC 3555, July 2003. 7. Informative References  Hellstrom, G., "RTP Payload for Text Conversation", RFC 2793, May 2000.  Baugher, et al., "The Secure Real-time Transport Protocol", RFC 3711, March 2004. 8. Author's Address Paul E. Jones Cisco Systems, Inc. 7025 Kit Creek Rd. Research Triangle Park, NC 27709, USA Phone: +1 919 392 6948 Email: firstname.lastname@example.org 9. Full Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Disclaimer This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property Jones Expires - October 2004 [Page 5] =0C Registration of the text/red MIME Sub-Type April 2004 The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- email@example.com. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Jones Expires - October 2004 [Page 6] =0C