Registration of the text/red MIME Sub-Type

Network Working Group                                           P. Jones
Request for Comments: 4102                           Cisco Systems, Inc.
Category: Standards Track                                      June 2005


               <span class="h1">Registration of the text/red MIME Sub-Type</span>

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document defines the text/red MIME sub-type.  "Red" is short for
   redundant.  The actual RTP packetization for this MIME type is
   specified in <a href="./rfc2198">RFC 2198</a>.

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   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.

   <a href="./rfc2198">RFC 2198</a> [<a href="#ref-1" title=""RTP Payload for Redundant Audio Data"">1</a>] defines an RTP [<a href="#ref-2" title=""RTP: A Transport Protocol for Real-Time Applications"">2</a>] payload format for redundant audio
   data.  The format defined in that document is quite suitable for
   providing redundancy for text, as well as audio.

   <a href="./rfc4103">RFC 4103</a> [<a href="#ref-8" title=""RTP Payload for Text Conversation"">8</a>] specifies one usage of <a href="./rfc2198">RFC 2198</a> 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 [<a href="#ref-5" title=""SDP: Session Description Protocol"">5</a>], the application of this MIME sub-type is not
   restricted to SDP.








<span class="grey">Jones                       Standards Track                     [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc4102">RFC 4102</a>                 text/red MIME Sub-Type                June 2005</span>


<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Conventions Used in This Document</span>

   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 <a href="./rfc2119">RFC 2119</a> [<a href="#ref-3" title=""Key words for use in RFCs to Indicate Requirement Levels"">3</a>].

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  IANA Considerations</span>

   One new MIME sub-type has been registered by the IANA, 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 <a href="./rfc2198">RFC</a>
      <a href="./rfc2198">2198</a>.  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 "=" content-type

      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.  Because it is
      part of the list, which must itself be a quoted-string, the
      quotation marks MUST be quoted with backslash quoting as specified
      in <a href="./rfc2045">RFC 2045</a> [<a href="#ref-4" title=""Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"">4</a>].  If the content-type string itself contains a
      quoted-string, then the requirement for backslash quoting is
      recursively applied.

   Optional parameters: ptime, maxptime (these attributes are originally
      defined in <a href="./rfc2327">RFC 2327</a> [<a href="#ref-5" title=""SDP: Session Description Protocol"">5</a>] and <a href="./rfc3267">RFC 3267</a> [<a href="#ref-6" title=""Real- Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs"">6</a>], respectively)

   Restrictions on Usage:
      This type is defined only for transfer via RTP.
      It shall not be defined for a storage format.



<span class="grey">Jones                       Standards Track                     [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc4102">RFC 4102</a>                 text/red MIME Sub-Type                June 2005</span>


   Encoding considerations:
      See restrictions on Usage above; this section is included per
      the requirements in <a href="./rfc3555">RFC 3555</a> [<a href="#ref-7" title=""MIME Type Registration of RTP Payload Formats"">7</a>].

   Security considerations: Refer to <a href="./rfc4102#section-5">section 5 of RFC 4102</a>.

   Interoperability considerations: none

   Published specification: <a href="./rfc2198">RFC 2198</a>

   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: [email protected]

   Intended usage: COMMON

   Author:
      Paul E. Jones
      [email protected]

   Change Controller:
      AVT Working Group delegated from the IESG

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Mapping to SDP Parameters</span>

   The information carried in the MIME media type specification has a
   specific mapping to fields in the Session Description Protocol (SDP)
   [<a href="#ref-5" title=""SDP: Session Description Protocol"">5</a>], which is commonly used to describe RTP sessions.  When SDP is
   used to specify sessions employing the <a href="./rfc2198">RFC 2198</a> in a text session,
   the mapping is as follows:

   -  The MIME type ("text") goes in SDP "m=" as the media name.

   -  The value of the parameter "rate" goes in SDP "a=rtpmap".

   -  The MIME subtype (RED) goes in SDP "a=rtpmap" as the encoding
      name.

   -  The parameters "ptime" and "maxptime" go in the SDP "a=ptime" and
      "a=maxptime" attributes, respectively.






<span class="grey">Jones                       Standards Track                     [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc4102">RFC 4102</a>                 text/red MIME Sub-Type                June 2005</span>


   -  The pt parameter is mapped to an a=fmtp attribute by eliminating
      the parameter name (pt) and changing the commas to slashes.  For
      example, 'pt="101,102"' maps to 'a=fmtp:99 101/102', where = '99'
      is the payload type of the redundancy frames.  Note that the
      single quote marks (') used in this example are not present in the
      actual message encoding, but are 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=rtpmap".

   An example of SDP is:

        m=text 11000 RTP/AVP 98 100
        a=rtpmap:98 t140/1000
        a=rtpmap:100 red/1000
        a=fmtp: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.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Security Considerations</span>

   The security considerations listed in <a href="./rfc2198">RFC 2198</a> 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 [<a href="#ref-9" title=""The Secure Real-time Transport Protocol (SRTP)"">9</a>].
















<span class="grey">Jones                       Standards Track                     [Page 4]</span>

<span id="page-5" ></span>
<span class="grey"><a href="./rfc4102">RFC 4102</a>                 text/red MIME Sub-Type                June 2005</span>


<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Normative References</span>

   [<a id="ref-1">1</a>] Perkins, C., Kouvelas, I., Hodson, O., Hardman, V., Handley, M.,
       Bolot, J., Vega-Garcia, A., and S. Fosse-Parisis, "RTP Payload
       for Redundant Audio Data", <a href="./rfc2198">RFC 2198</a>, September 1997.

   [<a id="ref-2">2</a>] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
       "RTP: A Transport Protocol for Real-Time Applications", STD 64,
       <a href="./rfc3550">RFC 3550</a>, July 2003.

   [<a id="ref-3">3</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
       Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-4">4</a>] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
       Extensions (MIME) Part One: Format of Internet Message Bodies",
       <a href="./rfc2045">RFC 2045</a>, November 1996.

   [<a id="ref-5">5</a>] Handley, M., Jackson, V., "SDP: Session Description Protocol",
       <a href="./rfc2327">RFC 2327</a>, April 1998.

   [<a id="ref-6">6</a>] Sjoberg, J., Westerlund, M., Lakaniemi, A., and Q. Xie, "Real-
       Time Transport Protocol (RTP) Payload Format and File Storage
       Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate
       Wideband (AMR-WB) Audio Codecs", <a href="./rfc3267">RFC 3267</a>, June 2002.

   [<a id="ref-7">7</a>] Casner, S. and P. Hoschka, "MIME Type Registration of RTP Payload
       Formats", <a href="./rfc3555">RFC 3555</a>, July 2003.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Informative References</span>

   [<a id="ref-8">8</a>] Hellstrom, G. and P. Jones, "RTP Payload for Text Conversation",
       <a href="./rfc4103">RFC 4103</a>, June 2005.

   [<a id="ref-9">9</a>] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
       Norrman, "The Secure Real-time Transport Protocol (SRTP)", <a href="./rfc3711">RFC</a>
       <a href="./rfc3711">3711</a>, March 2004.

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: [email protected]





<span class="grey">Jones                       Standards Track                     [Page 5]</span>

<span id="page-6" ></span>
<span class="grey"><a href="./rfc4102">RFC 4102</a>                 text/red MIME Sub-Type                June 2005</span>


Full Copyright Statement

   Copyright (C) The Internet Society (2005).

   This document is subject to the rights, licenses and restrictions
   contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
   retain all their rights.

   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

   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 <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.

   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
   <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.

   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 protected].

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.







Jones                       Standards Track                     [Page 6]