rfc9806.original.xml   rfc9806.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!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. <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
3) --> -ietf-sipcore-siprec-fix-mediatype-06" number="9806" category="std" consensus="t
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft rue" submissionType="IETF" updates="7866" obsoletes="" tocInclude="true" sortRef
-ietf-sipcore-siprec-fix-mediatype-06" category="std" consensus="true" submissio s="true" symRefs="true" version="3" xml:lang="en">
nType="IETF" updates="7866" tocInclude="true" sortRefs="true" symRefs="true" ver
sion="3">
<!-- xml2rfc v2v3 conversion 3.28.1 -->
<front> <front>
<title abbrev="Fix SIPREC Metadata Media Type">Updates to SIPREC correcting <title abbrev="Correct SIPREC Metadata Media Type">Updates to SIP-Based Medi
Metadata Media Type</title> a Recording (SIPREC) to Correct Metadata Media&nbsp;Type</title>
<seriesInfo name="Internet-Draft" value="draft-ietf-sipcore-siprec-fix-media <seriesInfo name="RFC" value="9806"/>
type-06"/>
<author fullname="Dan Mongrain"> <author fullname="Dan Mongrain">
<organization>Motorola Solutions</organization> <organization>Motorola Solutions</organization>
<address> <address>
<email>Dan.Mongrain@MotorolaSolutions.com</email> <email>Dan.Mongrain@MotorolaSolutions.com</email>
</address> </address>
</author> </author>
<date year="2025" month="May" day="02"/> <date year="2025" month="June"/>
<area>ART</area> <area>ART</area>
<workgroup>sipcore</workgroup> <workgroup>sipcore</workgroup>
<keyword>siprec</keyword> <keyword>siprec</keyword>
<keyword>errata</keyword> <keyword>errata</keyword>
<abstract> <abstract>
<?line 62?> <t>The SIP-based Media Recording (SIPREC) protocol is defined by both "Session I
nitiation Protocol (SIP) Recording Metadata" (RFC 7865) and "Session Recording P
<t>The SIP-based Media Recording (SIPREC) protocol is defined by both Session In rotocol" (RFC 7866). Unfortunately, both RFCs contradict each other regarding ho
itiation Protocol (SIP) Recording Metadata (RFC 7865) and Session Recording Prot w recording metadata is to be labeled. In addition, neither RFC registered the n
ocol (RFC 7866). Unfortunately, both RFCs contradict each other regarding how re ew media type. This document updates RFC 7866 to align with RFC 7865 when labeli
cording metadata is to be labeled. In addition, neither RFCs registered the new ng recording metadata and also registers the media type.</t>
media type. This document updates RFC 7866 to align with RFC 7865 when labeling
recording metadata and registers the new media type.</t>
</abstract> </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/bro
wse/sipcore/"/>.
Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/sipcore
/"/>.
</t>
</note>
</front> </front>
<middle> <middle>
<?line 66?>
<section anchor="introduction"> <section anchor="introduction">
<name>Introduction</name> <name>Introduction</name>
<t>SIP-based Media Recording (SIPREC) protocol is defined by <xref target= <t>The SIP-based Media Recording (SIPREC) protocol is defined by <xref tar
"RFC7865"/> and <xref target="RFC7866"/>. The former specifies the use of 'appli get="RFC7865"/> and <xref target="RFC7866"/>. The former specifies the use of "a
cation/rs-metadata+xml' when identifying metadata content, whereas the latter us pplication/rs-metadata+xml" when identifying metadata content, whereas the latte
es "application/rs-metadata". Since <xref target="RFC7865"/> defines SIPREC meta r uses "application/rs-metadata". Since <xref target="RFC7865"/> defines SIPREC
data, it was identified as normative, and <xref target="Err7987"/> was created a metadata, it was identified as normative, and <xref target="Err7987"/> was creat
gainst <xref target="RFC7866"/> to report the issue. This document resolves the ed against <xref target="RFC7866"/> to report the issue. This document resolves
errata.</t> the erratum.</t>
<t>In addition, as neither document registered the media type with IANA, t <t>In addition, neither document registered the media type with IANA; this
his document rectifies this gap.</t> document rectifies this gap.</t>
</section> </section>
<section anchor="updates-to-rfc-7866"> <section anchor="updates-to-rfc-7866">
<name>Updates to RFC 7866</name> <name>Updates to RFC 7866</name>
<t>Everywhere the following text occurs:</t> <t>Each instance of the following in <xref target="RFC7866"/>:</t>
<ul empty="true"> <blockquote>
<li> <t>application/rs-metadata</t>
<t>application/rs-metadata</t> </blockquote>
</li> <t>Is replaced with:</t>
</ul> <blockquote>
<t>Replace with:</t> <t>application/rs-metadata+xml</t>
<ul empty="true"> </blockquote>
<li>
<t>application/rs-metadata+xml</t>
</li>
</ul>
</section> </section>
<section anchor="securityconsiderations"> <section anchor="securityconsiderations">
<name>Security Considerations</name> <name>Security Considerations</name>
<t>The updates specified in this memo clarify inconsistencies in published documents with regards to identifying recording metadata. They do not introduce new security considerations beyond those listed in <xref target="RFC7866"/>.</t > <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>
<section anchor="iana-considerations"> <section anchor="iana-considerations">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<section anchor="media-type-registration"> <section anchor="media-type-registration">
<name>Media Type Registration</name> <name>Media Type Registration</name>
<t><xref target="RFC7865"/> defined a media type for use with specifying <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 XML data. This media type is to be used when specifying
recording metadata in SIPREC.</t> recording metadata in SIPREC.</t>
<t>Type name: application</t>
<t>Subtype name: rs-metadata+xml</t> <dl>
<t>Required parameters: N/A</t> <dt>Type name:</dt><dd>application</dd>
<t>Optional parameters: N/A</t> <dt>Subtype name:</dt><dd>rs-metadata+xml</dd>
<t>Encoding considerations: Same as encoding considerations of applicat <dt>Required parameters:</dt><dd>N/A</dd>
ion/xml as specified in <xref target="RFC7303"/>.</t> <dt>Optional parameters:</dt><dd>N/A</dd>
<t>Security considerations: N/A</t> <dt>Encoding considerations:</dt><dd>Same as encoding considerations
<t>Interoperability considerations: Please note that <xref target="RFC7 of "application/xml" as specified in <xref target="RFC7303"/>.</dd>
866"/> specified the use of "application/rs-metadata", which is obsoleted in fa <dt>Security considerations:</dt><dd>N/A</dd>
vour of "application/rs-metadata+xml".</t> <dt>Interoperability considerations:</dt><dd>Please note that <xref
<t>Published specification: <xref target="RFC7865"/> [RFC-to-be]</t> target="RFC7866"/> specifies the use of "application/rs-metadata",
<t>Applications which use this media type: SIPREC Clients (SRC) and Ser which has been replaced by "application/rs-metadata+xml" in RFC 9806.<
vers (SRS).</t> /dd>
<t>Fragment identifier considerations: N/A</t> <dt>Published specification:</dt><dd><xref target="RFC7865"/> [RFC9806
<t>Additional information:</t> ]</dd>
<ul empty="true"> <dt>Applications that use this media type:</dt><dd>Session Recording C
<li> lients (SRCs) and Session Recording Servers (SRSs).</dd>
<t>Deprecated alias names for this type: N/A</t> <dt>Fragment identifier considerations:</dt><dd>N/A</dd>
</li> <dt>Additional information:</dt><dd>
</ul> <t><br/></t>
<ul empty="true"> <dl spacing="compact">
<li> <dt>Deprecated alias names for this type:</dt><dd>N/A</dd>
<t>Magic number(s): N/A</t> <dt>Magic number(s):</dt><dd>N/A</dd>
</li> <dt>File extension(s):</dt><dd>N/A</dd>
</ul> <dt>Macintosh file type code(s):</dt><dd>N/A</dd>
<ul empty="true"> </dl>
<li> </dd>
<t>File extension(s): N/A</t> <dt>Person &amp; email address to contact for further information:</dt><
</li> dd>IETF SIPCORE Working Group (sipcore@ietf.org)</dd>
</ul> <dt>Intended usage:</dt><dd>COMMON</dd>
<ul empty="true"> <dt>Restrictions on usage:</dt><dd>There are no restrictions on where th
<li> is media type can be used.</dd>
<t>Macintosh file type code(s): N/A</t> <dt>Author:</dt><dd>IETF SIPCORE Working Group (sipcore@ietf.org)</dd>
</li> <dt>Change controller:</dt><dd>IETF</dd>
</ul> </dl>
<t>Person &amp; email address to contact for further information: IETF S
IPCORE Working Group (sipcore@ietf.org)</t>
<t>Intended usage: COMMON</t>
<t>Restrictions on usage: There are no restrictions on where this media
type can be used.</t>
<t>Author: IETF SIPCORE Working Group (sipcore@ietf.org)</t>
<t>Change controller: IETF</t>
</section> </section>
</section> </section>
</middle> </middle>
<back> <back>
<references anchor="sec-combined-references"> <references anchor="sec-combined-references">
<name>References</name> <name>References</name>
<references anchor="sec-normative-references"> <references anchor="sec-normative-references">
<name>Normative References</name> <name>Normative References</name>
<reference anchor="RFC7865"> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
<front> 865.xml"/>
<title>Session Initiation Protocol (SIP) Recording Metadata</title> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
<author fullname="R. Ravindranath" initials="R." surname="Ravindrana 866.xml"/>
th"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
<author fullname="P. Ravindran" initials="P." surname="Ravindran"/> 303.xml"/>
<author fullname="P. Kyzivat" initials="P." surname="Kyzivat"/>
<date month="May" year="2016"/>
<abstract>
<t>Session recording is a critical requirement in many communicati
ons environments, such as call centers and financial trading organizations. In s
ome of these environments, all calls must be recorded for regulatory, compliance
, and consumer protection reasons. The recording of a session is typically perfo
rmed by sending a copy of a media stream to a recording device. This document de
scribes the metadata model as viewed by the Session Recording Server (SRS) and t
he 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 Proto
col (SIP), the Session Description Protocol (SDP), and the Real-time Transport P
rotocol (RTP) for delivering real-time media and metadata from a Communication S
ession (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 Sessi
on Recording Client (SRC), which is on the path of the CS, and a Session Recordi
ng Server (SRS) at the recording device. This document considers only active rec
ording, where the SRC purposefully streams media to an SRS and all participating
user agents (UAs) are notified of the recording. Passive recording, where a rec
ording device detects media directly from the network (e.g., using port-mirrorin
g techniques), is outside the scope of this document. In addition, lawful interc
ept 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 -- applicatio
n/xml, application/xml-external-parsed-entity, and application/xml-dtd -- for us
e in exchanging network entities that are related to the Extensible Markup Langu
age (XML) while defining text/xml and text/ xml-external-parsed-entity as aliase
s for the respective application/ types. This specification also standardizes th
e '+xml' suffix for naming media types outside of these five types when those me
dia types represent XML MIME entities.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="7303"/>
<seriesInfo name="DOI" value="10.17487/RFC7303"/>
</reference>
</references> </references>
<references anchor="sec-informative-references"> <references anchor="sec-informative-references">
<name>Informative References</name> <name>Informative References</name>
<reference anchor="Err7987" target="https://www.rfc-editor.org/errata/ei d7987" quoteTitle="false"> <reference anchor="Err7987" target="https://www.rfc-editor.org/errata/ei d7987" quoteTitle="false">
<front> <front>
<title>Errata Report 7987</title> <title>Erratum ID 7987</title>
<author> <author>
<organization/> <organization>RFC Errata</organization>
</author> </author>
<date/>
</front> </front>
<refcontent>RFC 7866</refcontent> <refcontent>RFC 7866</refcontent>
</reference> </reference>
</references> </references>
</references> </references>
<?line 135?>
<section numbered="false" anchor="acknowledgments"> <section numbered="false" anchor="acknowledgments">
<name>Acknowledgments</name> <name>Acknowledgments</name>
<t>Acknowledgments to Brian Rosen for his guidance with writing my first i nternet draft using the new tools and for his thorough review. A sincere thank y ou to all of the reviewers for their valuable time which greatly enhanced this d ocument.</t> <t>Thank you to <contact fullname="Brian Rosen"/> for his guidance in writ ing my first Internet-Draft using the new tools and for his thorough review. A s incere thank you to all of the reviewers for their valuable time, which greatly enhanced this document.</t>
</section> </section>
</back> </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
</rfc> </rfc>
 End of changes. 18 change blocks. 
227 lines changed or deleted 82 lines changed or added

This html diff was produced by rfcdiff 1.48.