Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type
updates
- rfc-7866 — Session Recording Protocol
Extracted elements (7)
RFC 7865 was identified as normative for SIPREC metadata (it defines the metadata format), so when the two RFCs contradicted each other on media type labeling, RFC 7866 was updated to align with RFC 7865 rather than vice versa.
RFC 9806 resolves Erratum ID 7987 against RFC 7866, which reported that RFC 7866 used 'application/rs-metadata' while RFC 7865 (the normative metadata specification) used 'application/rs-metadata+xml'. Every instance of 'application/rs-metadata' in RFC 7866 is replaced with 'application/rs-metadata+xml'.
RFC 7866 previously specified 'application/rs-metadata', which has been replaced by 'application/rs-metadata+xml' in RFC 9806. Implementations that used the old media type label from RFC 7866 must be updated to use 'application/rs-metadata+xml'.
Each instance of 'application/rs-metadata' in RFC 7866 MUST be replaced with 'application/rs-metadata+xml' to align with the media type defined in RFC 7865.
The media type 'application/rs-metadata+xml' is the correct label for SIPREC recording metadata content, as defined in RFC 7865. It is used by Session Recording Clients (SRCs) and Session Recording Servers (SRSs) when identifying metadata in XML form.
IANA registration of the 'application/rs-metadata+xml' media type. Type: application, subtype: rs-metadata+xml, no required or optional parameters, encoding follows 'application/xml' per RFC 7303, intended usage COMMON, change controller IETF.
The updates in RFC 9806 only clarify inconsistencies in media type labeling and do not introduce any new security considerations beyond those already listed in RFC 7866.