rfc9806.original   rfc9806.txt 
sipcore D. Mongrain Internet Engineering Task Force (IETF) D. Mongrain
Internet-Draft Motorola Solutions Request for Comments: 9806 Motorola Solutions
Updates: 7866 (if approved) 2 May 2025 Updates: 7866 June 2025
Intended status: Standards Track Category: Standards Track
Expires: 3 November 2025 ISSN: 2070-1721
Updates to SIPREC correcting Metadata Media Type Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata
draft-ietf-sipcore-siprec-fix-mediatype-06 Media Type
Abstract Abstract
The SIP-based Media Recording (SIPREC) protocol is defined by both The SIP-based Media Recording (SIPREC) protocol is defined by both
Session Initiation Protocol (SIP) Recording Metadata (RFC 7865) and "Session Initiation Protocol (SIP) Recording Metadata" (RFC 7865) and
Session Recording Protocol (RFC 7866). Unfortunately, both RFCs "Session Recording Protocol" (RFC 7866). Unfortunately, both RFCs
contradict each other regarding how recording metadata is to be contradict each other regarding how recording metadata is to be
labeled. In addition, neither RFCs registered the new media type. labeled. In addition, neither RFC registered the new media type.
This document updates RFC 7866 to align with RFC 7865 when labeling This document updates RFC 7866 to align with RFC 7865 when labeling
recording metadata and registers the new media type. recording metadata and also registers the media type.
About This Document
This note is to be removed before publishing as an RFC.
Status information for this document may be found at
https://datatracker.ietf.org/doc/draft-ietf-sipcore-siprec-fix-
mediatype/.
Discussion of this document takes place on the WG Working Group
mailing list (mailto:sipcore@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/browse/sipcore/. Subscribe at
https://www.ietf.org/mailman/listinfo/sipcore/.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document is a product of the Internet Engineering Task Force
Task Force (IETF). Note that other groups may also distribute (IETF). It represents the consensus of the IETF community. It has
working documents as Internet-Drafts. The list of current Internet- received public review and has been approved for publication by the
Drafts is at https://datatracker.ietf.org/drafts/current/. Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Internet-Drafts are draft documents valid for a maximum of six months Information about the current status of this document, any errata,
and may be updated, replaced, or obsoleted by other documents at any and how to provide feedback on it may be obtained at
time. It is inappropriate to use Internet-Drafts as reference https://www.rfc-editor.org/info/rfc9806.
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 3 November 2025.
Copyright Notice Copyright Notice
Copyright (c) 2025 IETF Trust and the persons identified as the Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
2. Updates to RFC 7866 . . . . . . . . . . . . . . . . . . . . . 2 2. Updates to RFC 7866
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 3. Security Considerations
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations
4.1. Media Type Registration . . . . . . . . . . . . . . . . . 3 4.1. Media Type Registration
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. References
5.1. Normative References . . . . . . . . . . . . . . . . . . 4 5.1. Normative References
5.2. Informative References . . . . . . . . . . . . . . . . . 4 5.2. Informative References
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 4 Acknowledgments
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 Author's Address
1. Introduction 1. Introduction
SIP-based Media Recording (SIPREC) protocol is defined by [RFC7865] The SIP-based Media Recording (SIPREC) protocol is defined by
and [RFC7866]. The former specifies the use of 'application/rs- [RFC7865] and [RFC7866]. The former specifies the use of
metadata+xml' when identifying metadata content, whereas the latter "application/rs-metadata+xml" when identifying metadata content,
uses "application/rs-metadata". Since [RFC7865] defines SIPREC whereas the latter uses "application/rs-metadata". Since [RFC7865]
metadata, it was identified as normative, and [Err7987] was created defines SIPREC metadata, it was identified as normative, and
against [RFC7866] to report the issue. This document resolves the [Err7987] was created against [RFC7866] to report the issue. This
errata. document resolves the erratum.
In addition, as neither document registered the media type with IANA, In addition, neither document registered the media type with IANA;
this document rectifies this gap. this document rectifies this gap.
2. Updates to RFC 7866 2. Updates to RFC 7866
Everywhere the following text occurs: Each instance of the following in [RFC7866]:
application/rs-metadata | application/rs-metadata
Replace with: Is replaced with:
application/rs-metadata+xml | application/rs-metadata+xml
3. Security Considerations 3. Security Considerations
The updates specified in this memo clarify inconsistencies in The updates specified in this memo clarify inconsistencies in
published documents with regards to identifying recording metadata. published documents with regard to identifying recording metadata.
They do not introduce new security considerations beyond those listed They do not introduce new security considerations beyond those listed
in [RFC7866]. in [RFC7866].
4. IANA Considerations 4. IANA Considerations
4.1. Media Type Registration 4.1. Media Type Registration
[RFC7865] defined a media type for use with specifying recording [RFC7865] defines a media type for use with specifying recording
metadata in XML data. This media type is to be used when specifying metadata in XML data. This media type is to be used when specifying
recording metadata in SIPREC. recording metadata in SIPREC.
Type name: application Type name: application
Subtype name: rs-metadata+xml Subtype name: rs-metadata+xml
Required parameters: N/A Required parameters: N/A
Optional parameters: N/A Optional parameters: N/A
Encoding considerations: Same as encoding considerations of Encoding considerations: Same as encoding considerations of
application/xml as specified in [RFC7303]. "application/xml" as specified in [RFC7303].
Security considerations: N/A Security considerations: N/A
Interoperability considerations: Please note that [RFC7866] specified Interoperability considerations: Please note that [RFC7866]
the use of "application/rs-metadata", which is obsoleted in favour of specifies the use of "application/rs-metadata", which has been
"application/rs-metadata+xml". replaced by "application/rs-metadata+xml" in RFC 9806.
Published specification: [RFC7865] [RFC-to-be] Published specification: [RFC7865] [RFC9806]
Applications which use this media type: SIPREC Clients (SRC) and Applications that use this media type: Session Recording Clients
Servers (SRS). (SRCs) and Session Recording Servers (SRSs).
Fragment identifier considerations: N/A Fragment identifier considerations: N/A
Additional information: Additional information:
Deprecated alias names for this type: N/A Deprecated alias names for this type: N/A
Magic number(s): N/A
Magic number(s): N/A File extension(s): N/A
File extension(s): N/A Macintosh file type code(s): N/A
Macintosh file type code(s): N/A
Person & email address to contact for further information: IETF Person & email address to contact for further information: IETF
SIPCORE Working Group (sipcore@ietf.org) SIPCORE Working Group (sipcore@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: There are no restrictions on where this media Restrictions on usage: There are no restrictions on where this media
type can be used. type can be used.
Author: IETF SIPCORE Working Group (sipcore@ietf.org) Author: IETF SIPCORE Working Group (sipcore@ietf.org)
Change controller: IETF Change controller: IETF
5. References 5. References
5.1. Normative References 5.1. Normative References
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
DOI 10.17487/RFC7303, July 2014, DOI 10.17487/RFC7303, July 2014,
<https://www.rfc-editor.org/rfc/rfc7303>. <https://www.rfc-editor.org/info/rfc7303>.
[RFC7865] Ravindranath, R., Ravindran, P., and P. Kyzivat, "Session [RFC7865] Ravindranath, R., Ravindran, P., and P. Kyzivat, "Session
Initiation Protocol (SIP) Recording Metadata", RFC 7865, Initiation Protocol (SIP) Recording Metadata", RFC 7865,
DOI 10.17487/RFC7865, May 2016, DOI 10.17487/RFC7865, May 2016,
<https://www.rfc-editor.org/rfc/rfc7865>. <https://www.rfc-editor.org/info/rfc7865>.
[RFC7866] Portman, L., Lum, H., Ed., Eckel, C., Johnston, A., and A. [RFC7866] Portman, L., Lum, H., Ed., Eckel, C., Johnston, A., and A.
Hutton, "Session Recording Protocol", RFC 7866, Hutton, "Session Recording Protocol", RFC 7866,
DOI 10.17487/RFC7866, May 2016, DOI 10.17487/RFC7866, May 2016,
<https://www.rfc-editor.org/rfc/rfc7866>. <https://www.rfc-editor.org/info/rfc7866>.
5.2. Informative References 5.2. Informative References
[Err7987] Errata Report 7987, RFC 7866, [Err7987] RFC Errata, Erratum ID 7987, RFC 7866,
<https://www.rfc-editor.org/errata/eid7987>. <https://www.rfc-editor.org/errata/eid7987>.
Acknowledgments Acknowledgments
Acknowledgments to Brian Rosen for his guidance with writing my first Thank you to Brian Rosen for his guidance in writing my first
internet draft using the new tools and for his thorough review. A Internet-Draft using the new tools and for his thorough review. A
sincere thank you to all of the reviewers for their valuable time sincere thank you to all of the reviewers for their valuable time,
which greatly enhanced this document. which greatly enhanced this document.
Author's Address Author's Address
Dan Mongrain Dan Mongrain
Motorola Solutions Motorola Solutions
Email: Dan.Mongrain@MotorolaSolutions.com Email: Dan.Mongrain@MotorolaSolutions.com
 End of changes. 40 change blocks. 
100 lines changed or deleted 85 lines changed or added

This html diff was produced by rfcdiff 1.48.