RFC 9806

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

📅 published June 2025, from ietf

RFC 9806: Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type 💖

Okay bestie, the title block first 🎀 This one is RFC 9806, written by D. Mongrain from Motorola Solutions, dated June 2025. It's a Standards Track doc 🔥, it updates RFC 7866 ✨, and the title block lists no obsoletes. The ISSN is 2070-1721 🧚

Abstract 🌸

SIPREC (SIP-based Media Recording) is defined by two RFCs: "Session Initiation Protocol (SIP) Recording Metadata" (RFC 7865) and "Session Recording Protocol" (RFC 7866). Here's the drama 😭 they disagree on how recording metadata gets labeled. Also, neither one ever registered the new media type. So this doc updates RFC 7866 so it matches RFC 7865 for the metadata labeling, and it finally registers the media type 💅

Status of This Memo 🦋

This is an Internet Standards Track document 🔥

It's a product of the Internet Engineering Task Force (IETF) and it represents the consensus of the IETF community. It got public review and was approved for publication by the Internet Engineering Steering Group (IESG). If you want more on Internet Standards, check Section 2 of RFC 7841 🧚

For the current status, any errata, and how to send feedback, go to https://www.rfc-editor.org/info/rfc9806 💜

Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved 🫶

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) as they stand on the publication date. Read those carefully, because they spell out your rights and restrictions for this doc 📜 Any Code Components pulled out of this document must include Revised BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come with no warranty, as described in the Revised BSD License ⚖️

Table of Contents 🗂️

1.  Introduction
2.  Updates to RFC 7866
3.  Security Considerations
4.  IANA Considerations
  4.1.  Media Type Registration
5.  References
  5.1.  Normative References
  5.2.  Informative References
Acknowledgments
Author's Address

1. Introduction ✨

SIPREC is defined by [RFC7865] and [RFC7866] 🎀 The first one says to use application/rs-metadata+xml when labeling metadata content, but the second one says application/rs-metadata. Since [RFC7865] is the one that actually defines SIPREC metadata, it got marked as normative. Someone filed [Err7987] against [RFC7866] to report the mismatch, and this document fixes that erratum 🔥

Also, neither document registered the media type with IANA. This doc closes that gap 💅

2. Updates to RFC 7866 🦋

Every instance of the following in [RFC7866]:

|  application/rs-metadata

gets replaced with:

|  application/rs-metadata+xml

3. Security Considerations 💀

The updates in this memo clarify inconsistencies in already-published documents about how recording metadata gets identified. ⚠️ They do not add any new security considerations beyond the ones already listed in [RFC7866]. No new threats, bestie. Just a cleaner label 🧚

4. IANA Considerations 🌸

4.1. Media Type Registration 💜

[RFC7865] defines a media type for specifying recording metadata in XML data. This is the media type you use when specifying recording metadata in SIPREC 🎀

Here's the registration template, verbatim:

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 [RFC7303].

Security considerations:  N/A

Interoperability considerations:  Please note that [RFC7866]
   specifies the use of "application/rs-metadata", which has been
   replaced by "application/rs-metadata+xml" in RFC 9806.

Published specification:  [RFC7865] [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

5. References 📚

5.1. Normative References 👑

5.2. Informative References 🧚

Acknowledgments 🫶

Thank you to Brian Rosen for guiding the author through writing their first Internet-Draft with the new tools, and for a super thorough review 💜 Big thanks to all the reviewers too, because their time made this doc way better 🌸

Author's Address 🎀

Dan Mongrain Motorola Solutions Email: Dan.Mongrain@MotorolaSolutions.com

That's the whole RFC, periodt! 🌈✨

📦 where this page comes from