wdiff rfc9806.original.xml rfc9806.xml

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

<!-- [rfced] *AD - This document references the following erratum report:
https://www.rfc-editor.org/errata/eid7987.

This erratum is currently in Reported state. The Web Portion of the Style Guide
(https://www.rfc-editor.org/styleguide/part2/#ref_errata) states, "Errata in
the Reported state should not be referenced; they are not considered stable."
The RPC strongly recommends that a referenced erratum report be either
Verified or Held for Document Update.

As AD, would you address this erratum report?
-->

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 3.2.3) -->
<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"> version="3" xml:lang="en">
<!-- xml2rfc v2v3 conversion 3.28.1 [rfced] Please note that the title of the document has been updated as
follows. Abbreviations have been expanded per Section 3.6 of RFC 7322 ("RFC
Style Guide"), and we updated "correcting" to "to Correct". Please review.

Original:
  Updates to SIPREC correcting Metadata Media Type

Current:
  Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type
-->

  <front>
    <title abbrev="Fix abbrev="Correct SIPREC Metadata Media Type">Updates to SIPREC correcting SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-sipcore-siprec-fix-mediatype-06"/> 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="May" day="02"/> month="June"/>
    <area>ART</area>
    <workgroup>sipcore</workgroup>
    <keyword>siprec</keyword>
    <keyword>errata</keyword>
    <abstract>
      <?line 62?>
<t>The SIP-based Media Recording (SIPREC) protocol is defined by both Session "Session Initiation Protocol (SIP) Recording Metadata Metadata" (RFC 7865) and Session "Session Recording Protocol Protocol" (RFC 7866). Unfortunately, both RFCs contradict each other regarding how recording metadata is to be labeled. In addition, neither RFCs RFC registered the new media type. This document updates RFC 7866 to align with RFC 7865 when labeling recording metadata and also registers the new media type.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-sipcore-siprec-fix-mediatype/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        WG Working Group mailing list (<eref target="mailto:sipcore@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/sipcore/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/sipcore/"/>.
      </t>
    </note>
  </front>
  <middle>
    <?line 66?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>SIP-based
      <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' "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 errata.</t> erratum.</t>
      <t>In addition, as neither document registered the media type with IANA, IANA; this document rectifies this gap.</t>
    </section>
    <section anchor="updates-to-rfc-7866">
      <name>Updates to RFC 7866</name>
      <t>Everywhere
      <t>Each instance of the following text occurs:</t>
      <ul empty="true">
        <li> in <xref target="RFC7866"/>:</t>
      <blockquote>
	<t>application/rs-metadata</t>
        </li>
      </ul>
      <t>Replace
      </blockquote>
      <t>Is replaced with:</t>
      <ul empty="true">
        <li>
      <blockquote>
	<t>application/rs-metadata+xml</t>
        </li>
      </ul>
      </blockquote>
    </section>
    <section anchor="securityconsiderations">
      <name>Security Considerations</name>
      <t>The updates specified in this memo clarify inconsistencies in published documents with regards 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"/> defined 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>
        <t>Type name:  application</t>
        <t>Subtype name:  rs-metadata+xml</t>
        <t>Required parameters:  N/A</t>
        <t>Optional parameters:  N/A</t>
        <t>Encoding considerations:  Same

<!-- [rfced] We made some changes in the media type template in Section 4.1
Please review and let us know any concerns. Note that we will ask IANA to
update the template at
https://www.iana.org/assignments/media-types/application/rs-metadata+xml
to match the edited document prior to publication.
-->
	<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 "application/xml" as specified in <xref target="RFC7303"/>.</t>
        <t>Security considerations:  N/A</t>
        <t>Interoperability considerations:  Please target="RFC7303"/>.</dd>
          <dt>Security considerations:</dt><dd>N/A</dd>
          <dt>Interoperability considerations:</dt><dd>Please note that <xref
          target="RFC7866"/> specified specifies the use of "application/rs-metadata",
          which is obsoleted has been replaced by "application/rs-metadata+xml" in favour of "application/rs-metadata+xml".</t>
        <t>Published specification:  <xref RFC 9806.</dd>
          <dt>Published specification:</dt><dd><xref target="RFC7865"/> [RFC-to-be]</t>
        <t>Applications which [RFC9806]</dd>
          <dt>Applications that use this media type:  SIPREC type:</dt><dd>Session Recording Clients (SRC) (SRCs) and Session Recording Servers (SRS).</t>
        <t>Fragment (SRSs).</dd>
          <dt>Fragment identifier considerations:  N/A</t>
        <t>Additional information:</t>
        <ul empty="true">
          <li>
            <t>Deprecated considerations:</dt><dd>N/A</dd>
          <dt>Additional information:</dt><dd>
          <t><br/></t>
	  <dl spacing="compact">
            <dt>Deprecated alias names for this type:  N/A</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>Magic number(s):  N/A</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>File extension(s):  N/A</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>Macintosh 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):  N/A</t>
          </li>
        </ul>
        <t>Person code(s):</dt><dd>N/A</dd>
          </dl>
	</dd>
        <dt>Person &amp; email address to contact for further information: IETF information:</dt><dd>IETF SIPCORE Working Group (sipcore@ietf.org)</t>
        <t>Intended usage:  COMMON</t>
        <t>Restrictions (sipcore@ietf.org)</dd>
        <dt>Intended usage:</dt><dd>COMMON</dd>
        <dt>Restrictions on usage:  There usage:</dt><dd>There are no restrictions on where this media type can be used.</t>
        <t>Author:  IETF used.</dd>
        <dt>Author:</dt><dd>IETF SIPCORE Working Group (sipcore@ietf.org)</t>
        <t>Change controller:  IETF</t> (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>
        <reference anchor="RFC7865">
          <front>
            <title>Session Initiation Protocol (SIP) Recording Metadata</title>
            <author fullname="R. Ravindranath" initials="R." surname="Ravindranath"/>
            <author fullname="P. Ravindran" initials="P." surname="Ravindran"/>
            <author fullname="P. Kyzivat" initials="P." surname="Kyzivat"/>
            <date month="May" year="2016"/>
            <abstract>
              <t>Session recording is a critical requirement in many communications environments, such as call centers and financial trading organizations. In some of these environments, all calls must be recorded for regulatory, compliance, and consumer protection reasons. The recording of a session is typically performed by sending a copy of a media stream to a recording device. This document describes the metadata model as viewed by the Session Recording Server (SRS) and the recording metadata format.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7865"/>
          <seriesInfo name="DOI" value="10.17487/RFC7865"/>
        </reference>
        <reference anchor="RFC7866">
          <front>
            <title>Session Recording Protocol</title>
            <author fullname="L. Portman" initials="L." surname="Portman"/>
            <author fullname="H. Lum" initials="H." role="editor" surname="Lum"/>
            <author fullname="C. Eckel" initials="C." surname="Eckel"/>
            <author fullname="A. Johnston" initials="A." surname="Johnston"/>
            <author fullname="A. Hutton" initials="A." surname="Hutton"/>
            <date month="May" year="2016"/>
            <abstract>
              <t>This document specifies the use of the Session Initiation Protocol (SIP), the Session Description Protocol (SDP), and the Real-time Transport Protocol (RTP) for delivering real-time media and metadata from a Communication Session (CS) to a recording device. The Session Recording Protocol specifies the use of SIP, SDP, and RTP to establish a Recording Session (RS) between the Session Recording Client (SRC), which is on the path of the CS, and a Session Recording Server (SRS) at the recording device. This document considers only active recording, where the SRC purposefully streams media to an SRS and all participating user agents (UAs) are notified of the recording. Passive recording, where a recording device detects media directly from the network (e.g., using port-mirroring techniques), is outside the scope of this document. In addition, lawful intercept is outside the scope of this document.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7866"/>
          <seriesInfo name="DOI" value="10.17487/RFC7866"/>
        </reference>
        <reference anchor="RFC7303">
          <front>
            <title>XML Media Types</title>
            <author fullname="H. Thompson" initials="H." surname="Thompson"/>
            <author fullname="C. Lilley" initials="C." surname="Lilley"/>
            <date month="July" year="2014"/>
            <abstract>
              <t>This specification standardizes three media types -- application/xml, application/xml-external-parsed-entity, and application/xml-dtd -- for use in exchanging network entities that are related to the Extensible Markup Language (XML) while defining text/xml and text/ xml-external-parsed-entity as aliases for the respective application/ types. This specification also standardizes the '+xml' suffix for naming media types outside of these five types when those media types represent XML MIME entities.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7303"/>
          <seriesInfo name="DOI" value="10.17487/RFC7303"/>
        </reference>
        <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>Errata Report
            <title>Erratum ID 7987</title>
            <author>
              <organization/>
              <organization>RFC Errata</organization>
            </author>
            <date/>
          </front>
          <refcontent>RFC 7866</refcontent>
        </reference>
      </references>
    </references>
    <?line 135?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>Acknowledgments
      <t>Thank you to Brian Rosen <contact fullname="Brian Rosen"/> for his guidance with in writing my first internet draft Internet-Draft using the new tools and for his thorough review. A sincere thank you to all of the reviewers for their valuable time time, which greatly enhanced this document.</t>
    </section>
  </back>
<!-- ##markdown-source:
H4sIAAAAAAAAA51YbW8jtxH+LkD/YSoDPRvVSgccepco6SGKzw4MxGdDdpAW
RT9wdymJMEUqXK516sH/vc8MubLkyEjbL3dacjh85u2ZoYui6PdOTk7wD125
qIPTsfgU1DzStQoPtd84utertVVRQ4bFZtqplaa4NA3NjdU0D35FNZ8poq99
sfVtYJFiHXz0lbejVU3R00JHaqIKUdcjVpSuEWVzH1YqEjQOkqLvOyUfi+83
Pjwsgm/X+C1L0DcYZTSXPpBxJhplqdGxXQ8JR8k7uyWntVysaxOBF9eY0EQq
ra8eyM/xqW3dCJYblh9EE60eyLmGD5aaqqVyC11/R7W2OmoaqLIM+nFAZs4X
BZIzjLxZ+hBF2dRtyeO+QJWHT12kSjlWxkB0PaSyjaJbBT1vLTkf+TbjYvB1
W0EuBB8SsDvP7hGgtDHW8jnYSaqNHi4zlbJAXrfBuEVyACPD5VuCdmpdNqDz
1yfv3sDRrrJtDWuKt28HBBcOCo5wE2GXy66yEmcB8bMqtW12WwgW/RdhyioT
jgahKLesjFVE7614GA6Am/CDV6s2BPbWow6N8e472AOIta9Y3YDvJf1FIRl1
Z809J2HM+cmXNPQQ1IrTtgjzakLLGNfNZDxemLhsy1HlV+NKlX68L8WK/oGc
4SAFDVWVFjiAYkLyRI42rRNeRbWZ4weDTakrbjoXV+/cB7AIPlvCBkKoWu78
h2Q/HX1ZWTHq79c/D0nHajQanSXDuCAlsSY0+GVdsx9Zx93V7eziHFkFP1WR
I36to8K2wo/aKLrfrvWg30s5irOX5kt36LhkBdULH7YTVGbd7/V72duTHGCj
47xozBpXav4f9xZz86VYsZIIHcXb9/1emyBO6MM37/HZtOXKNGw4S0zo6uL+
kuiElG08QBlX67XGPy4OhjTgovAB9csfV9Mf8R8n5NXs/hIAXbsqdZgQkOGK
CRB718CrLW6LoQUpwc53MDloNaHp7L7f2yUijErI+70HvcVyjfNUULJDfqLS
4BMo0a5l7UT55K8/8UfC/ysUsrN/4i1eXiljd8p/YB+NfFjwjgrV8jnrWI5X
zKMedVJjXhiXwW8aPc4qxux5VDQYRBCyJiJQg02x+ITMvPZuEZRxaQ+KlDP/
BgF4N8EePOitAlvYlpeaJKUTUBwfdcd/6GR3olwUfL+TtATUCX/1e8bN91aI
LkL48O03HyZJNXgcfI5odrZuNpsRiqlI4RRLk3PH2tR8cJAPprS+kD00kzVY
k3g/baPAMmnmi4hml+c5sfhL0oDmyCWdFn5rfdRZa17u94qiIFU2Magq8vc9
6g6FUJSKiSiVwEzD9zUH9jTVyBl1HYv5vNZz44S1qASb052WlEab5G7DrqPb
TpwVnO0p3BXbaQb/1zNSrt7peJZ8VtGZeTaiX9j1sXUw1W6H6XpsN9JPgqpN
FUkr0EnqMkEvVNK29Bt8dbpXHQrTdTPLRI5mACNI1YgUwAzR74zokSugzDQY
BLh1wmlOb0iKXWphlBgXJNGumPxy4e9CxNcoaxYOvSphFuNps9QuXc64jiBk
53Q3N8cu7oK6MnVtJcQysEjDZCt45f8P8NevfwJWhvr0JFh2C++fntjoxNrw
UbPWlUE/TiDRcXiQeKPWa4tWzEDGoSk6s/4Chn+TjDdMd2a+PbA6Z/qQRcBf
SSdaGZyQmtngFcWDEd2hh+tD4MmgpmP8TnhIGH820J4xGNiMr129D7PFucCh
iIUrAIosuQBroIvveyR1bqlcRgyub3+XGkE33j5mPyUmkCAeZB7DyMm3d/Ag
AZ9zIOXU1fTzdJimz70jVeyCgvWFWo9Shuz1zmcW6fcuMGFsxee5IVvrNxyZ
iJZNvsIg0gj99HsfX4lA2p3lcYGRCW2+Js6ZkCDdaWg3cUvn4F5EJIhsQ19P
mrxTHWw8dfTV1VqXgXWax2DvSq88Veg0yC8e7fg8POgq9giE1m1pTbPEic5j
TfJlIg5xz35+/r4+pQQwZnqZVZ8HVS7SDjYd4gbdbL3jGHoUiWVAgvigslKn
OZGgvnCIbJzsTSsoZ06MtM27R3If6bqfMDxccYmKsclvrxjIyDCGUTI2pfKe
oh2ByhwrBf2H6lIViokCP7Vy2ksQ4ay2jHu7R1Jmpn9rDVfDWmFo1UyQEPw8
nvLmzZoV4e1zbPMCqSCwDiMDgTt+dKH49HEJ5rT9ROZBVb3IvOz9d2/f5Tje
Hc+DZzjyvvRrbJTGHhW8tSBBzTnGhalekM7z9XvU+zpFMqsa9EjEzpfgIp0T
cK4e+d2Gs68dZc8PxKbbXeXky6s8cR0S7z/xE2/fotT/4lPTZ7VNBsFo42FS
cRgSUZ9bIzV5ejc77+aEwI8gXrk7EySXQS2E63YkHl519DTzK9JiN8QBtPDT
J82zb2J2a5h/kQqNVIrgy8iypo/XamEqSkP4aXO2t3N58MI53LtWFTjCN8v0
DpIER6LpA6lbGIhR6M9pSuWmgJYhdcZtEXObgJq3QdrDviHpQQHnnd/MLg6n
czp9OZWfdamHB0eNOKgF23d+c3198zmVFzjFVDnv3U7iXtoDv10dN7tDoa53
HLJEfuUzR0jMpmmip/8db35JyriH5qQ7Jd0UVKrqITHntHpwfoOZTrIDrPl1
kqKl678NZBweSAd5Icdu/hGPLoyioGcnrpbW2ZpaudzRaIN6Flrb5j+dmPwn
ovQ6hKXSNPO0lh71nL6dNjbftwtuNI9Gb0Y0xaMJ2sV3yj3Im1pGRsv1yIqS
JOd+SkltAj0q26qSE8mAtlJBLXg8sVsw2JLx1ocTAdz/H7tmeufaEgAA [rfced] FYI - We have added expansions for the following abbreviations
per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each
expansion in the document carefully to ensure correctness.

Session Recording Clients (SRCs)
Session Recording Servers (SRSs)
-->

<!-- [rfced] Please review the "Inclusive Language" portion of the online
Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
and let us know if any changes are needed.  Updates of this nature typically
result in more precise language, which is helpful for readers.

Note that our script did not flag any words in particular, but this should
still be reviewed as a best practice.
-->

</rfc>