Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type Motorola Solutions
Dan.Mongrain@MotorolaSolutions.com
ART sipcore siprec errata 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.
Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .
Copyright Notice Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.
Table of Contents
  • .  Introduction
  • .  Updates to RFC 7866
  • .  Security Considerations
  • .  IANA Considerations
    • .  Media Type Registration
  • .  References
    • .  Normative References
    • .  Informative References
  • Acknowledgments
  • Author's Address
Introduction The SIP-based Media Recording (SIPREC) protocol is defined by and . The former specifies the use of "application/rs-metadata+xml" when identifying metadata content, whereas the latter uses "application/rs-metadata". Since defines SIPREC metadata, it was identified as normative, and was created against to report the issue. This document resolves the erratum. In addition, neither document registered the media type with IANA; this document rectifies this gap.
Updates to RFC 7866 Each instance of the following in :
application/rs-metadata
Is replaced with:
application/rs-metadata+xml
Security Considerations 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 .
IANA Considerations
Media Type Registration 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.
Type name:
application
Subtype name:
rs-metadata+xml
Required parameters:
N/A
Optional parameters:
N/A
Encoding considerations:
Same as encoding considerations of "application/xml" as specified in .
Security considerations:
N/A
Interoperability considerations:
Please note that specifies the use of "application/rs-metadata", which has been replaced by "application/rs-metadata+xml" in RFC 9806.
Published specification:
[RFC9806]
Applications that use this media type:
Session Recording Clients (SRCs) and Session Recording Servers (SRSs).
Fragment identifier considerations:
N/A
Additional information:
Deprecated alias names for this type:
N/A
Magic number(s):
N/A
File extension(s):
N/A
Macintosh file type code(s):
N/A
Person & email address to contact for further information:
IETF SIPCORE Working Group (sipcore@ietf.org)
Intended usage:
COMMON
Restrictions on usage:
There are no restrictions on where this media type can be used.
Author:
IETF SIPCORE Working Group (sipcore@ietf.org)
Change controller:
IETF
 References Normative References XML Media Types 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. Session Initiation Protocol (SIP) Recording Metadata 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. Session Recording Protocol 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. Informative References Erratum ID 7987 RFC Errata RFC 7866
Acknowledgments Thank you to 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.
Author's Address Motorola Solutions
Dan.Mongrain@MotorolaSolutions.com