sipcore

Internet Engineering Task Force (IETF)                       D. Mongrain
Internet-Draft
Request for Comments: 9806                            Motorola Solutions
Updates: 7866 (if approved)                                   2 May                                                  June 2025
Intended status:
Category: Standards Track
Expires: 3 November 2025
ISSN: 2070-1721

Updates to SIPREC correcting SIP-Based Media Recording (SIPREC) to Correct Metadata Media
                                  Type
               draft-ietf-sipcore-siprec-fix-mediatype-06

Abstract

   The SIP-based Media Recording (SIPREC) protocol is defined by both
   Session
   "Session Initiation Protocol (SIP) Recording Metadata Metadata" (RFC 7865) and
   Session
   "Session Recording Protocol Protocol" (RFC 7866).  Unfortunately, both RFCs
   contradict each other regarding how recording metadata is to be
   labeled.  In addition, neither RFCs RFC registered the new media type.
   This document updates RFC 7866 to align with RFC 7865 when labeling
   recording metadata and also registers the new 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

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list  It represents the consensus of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid the IETF community.  It has
   received public review and has been approved for a maximum 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 six months this document, any errata,
   and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."
   This Internet-Draft will expire on 3 November 2025.
   https://www.rfc-editor.org/info/rfc9806.

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 (https://trustee.ietf.org/
   license-info)
   (https://trustee.ietf.org/license-info) 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

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

1.  Introduction

   The SIP-based Media Recording (SIPREC) protocol is defined by
   [RFC7865] and [RFC7866].  The former specifies the use of 'application/rs-
   metadata+xml'
   "application/rs-metadata+xml" when identifying metadata content,
   whereas the latter uses "application/rs-metadata".  Since [RFC7865]
   defines SIPREC metadata, it was identified as normative, and
   [Err7987] was created against [RFC7866] to report the issue.  This
   document resolves the
   errata. erratum.

   In addition, as neither document registered the media type with IANA, IANA;
   this document rectifies this gap.

2.  Updates to RFC 7866

   Everywhere

   Each instance of the following text occurs: in [RFC7866]:

   |  application/rs-metadata
   Replace

   Is replaced with:

   |  application/rs-metadata+xml

3.  Security Considerations

   The updates specified in this memo clarify inconsistencies in
   published documents with regards regard to identifying recording metadata.
   They do not introduce new security considerations beyond those listed
   in [RFC7866].

4.  IANA Considerations

4.1.  Media Type Registration

   [RFC7865] defined 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
      "application/xml" as specified in [RFC7303].

   Security considerations:  N/A

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

   Published specification:  [RFC7865] [RFC-to-be] [RFC9806]

   Applications which that use this media type: SIPREC  Session Recording Clients (SRC)
      (SRCs) and Session Recording Servers (SRS). (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

   [RFC7303]  Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
              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
              Initiation Protocol (SIP) Recording Metadata", RFC 7865,
              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.
              Hutton, "Session Recording Protocol", RFC 7866,
              DOI 10.17487/RFC7866, May 2016,
              <https://www.rfc-editor.org/rfc/rfc7866>.
              <https://www.rfc-editor.org/info/rfc7866>.

5.2.  Informative References

   [Err7987]  Errata Report  RFC Errata, Erratum ID 7987, RFC 7866,
              <https://www.rfc-editor.org/errata/eid7987>.

Acknowledgments

   Acknowledgments

   Thank you to Brian Rosen for his guidance with in writing my first
   internet draft
   Internet-Draft using the new tools and for his thorough review.  A
   sincere thank you to all of the reviewers for their valuable time time,
   which greatly enhanced this document.

Author's Address

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