<?xml version='1.0' encoding='utf-8'?>

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-sipcore-siprec-fix-mediatype-06" number="9806" category="std" consensus="true" submissionType="IETF" updates="7866" obsoletes="" tocInclude="true" sortRefs="true" symRefs="true" version="3" xml:lang="en">

  <front>
    <title abbrev="Correct SIPREC Metadata Media Type">Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media&nbsp;Type</title>
    <seriesInfo name="RFC" value="9806"/>
    <author fullname="Dan Mongrain">
      <organization>Motorola Solutions</organization>
      <address>
        <email>Dan.Mongrain@MotorolaSolutions.com</email>
      </address>
    </author>
    <date year="2025" month="June"/>
    <area>ART</area>
    <workgroup>sipcore</workgroup>
    <keyword>siprec</keyword>
    <keyword>errata</keyword>
    <abstract>
<t>The SIP-based Media Recording (SIPREC) protocol is defined by both "Session Initiation Protocol (SIP) Recording Metadata" (RFC 7865) and "Session Recording Protocol" (RFC 7866). Unfortunately, both RFCs contradict each other regarding how recording metadata is to be labeled. In addition, neither RFC registered the new media type. This document updates RFC 7866 to align with RFC 7865 when labeling recording metadata and also registers the media type.</t>
    </abstract>
  </front>
  <middle>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The SIP-based Media Recording (SIPREC) protocol is defined by <xref target="RFC7865"/> and <xref target="RFC7866"/>. The former specifies the use of "application/rs-metadata+xml" when identifying metadata content, whereas the latter uses "application/rs-metadata". Since <xref target="RFC7865"/> defines SIPREC metadata, it was identified as normative, and <xref target="Err7987"/> was created against <xref target="RFC7866"/> to report the issue. This document resolves the erratum.</t>
      <t>In addition, neither document registered the media type with IANA; this document rectifies this gap.</t>
    </section>
    <section anchor="updates-to-rfc-7866">
      <name>Updates to RFC 7866</name>
      <t>Each instance of the following in <xref target="RFC7866"/>:</t>
      <blockquote>
	<t>application/rs-metadata</t>
      </blockquote>
      <t>Is replaced with:</t>
      <blockquote>
	<t>application/rs-metadata+xml</t>
      </blockquote>
    </section>
    <section anchor="securityconsiderations">
      <name>Security Considerations</name>
      <t>The updates specified in this memo clarify inconsistencies in published documents with regard to identifying recording metadata. They do not introduce new security considerations beyond those listed in <xref target="RFC7866"/>.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="media-type-registration">
        <name>Media Type Registration</name>
        <t><xref target="RFC7865"/> defines a media type for use with specifying recording metadata in XML data.  This media type is to be used when specifying recording metadata in SIPREC.</t>

	<dl>
          <dt>Type name:</dt><dd>application</dd>
          <dt>Subtype name:</dt><dd>rs-metadata+xml</dd>
          <dt>Required parameters:</dt><dd>N/A</dd>
          <dt>Optional parameters:</dt><dd>N/A</dd>
          <dt>Encoding considerations:</dt><dd>Same as encoding considerations
          of "application/xml" as specified in <xref target="RFC7303"/>.</dd>
          <dt>Security considerations:</dt><dd>N/A</dd>
          <dt>Interoperability considerations:</dt><dd>Please note that <xref
          target="RFC7866"/> specifies the use of "application/rs-metadata",
          which has been replaced by "application/rs-metadata+xml" in RFC 9806.</dd>
          <dt>Published specification:</dt><dd><xref target="RFC7865"/> [RFC9806]</dd>
          <dt>Applications that use this media type:</dt><dd>Session Recording Clients (SRCs) and Session Recording Servers (SRSs).</dd>
          <dt>Fragment identifier considerations:</dt><dd>N/A</dd>
          <dt>Additional information:</dt><dd>
          <t><br/></t>
	  <dl spacing="compact">
            <dt>Deprecated alias names for this type:</dt><dd>N/A</dd>
            <dt>Magic number(s):</dt><dd>N/A</dd>
            <dt>File extension(s):</dt><dd>N/A</dd>
            <dt>Macintosh file type code(s):</dt><dd>N/A</dd>
          </dl>
	</dd>
        <dt>Person &amp; email address to contact for further information:</dt><dd>IETF SIPCORE Working Group (sipcore@ietf.org)</dd>
        <dt>Intended usage:</dt><dd>COMMON</dd>
        <dt>Restrictions on usage:</dt><dd>There are no restrictions on where this media type can be used.</dd>
        <dt>Author:</dt><dd>IETF SIPCORE Working Group (sipcore@ietf.org)</dd>
        <dt>Change controller:</dt><dd>IETF</dd>
	</dl>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7865.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7866.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7303.xml"/>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="Err7987" target="https://www.rfc-editor.org/errata/eid7987" quoteTitle="false">
          <front>
            <title>Erratum ID 7987</title>
            <author>
              <organization>RFC Errata</organization>
            </author>
          </front>
          <refcontent>RFC 7866</refcontent>
        </reference>
      </references>
    </references>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>Thank you to <contact fullname="Brian Rosen"/> for his guidance in writing my first Internet-Draft using the new tools and for his thorough review. A sincere thank you to all of the reviewers for their valuable time, which greatly enhanced this document.</t>
    </section>
  </back>

</rfc>
