| Internet-Draft | Fix SIPREC Metadata Media Type | December 2024 |
| Mongrain | Expires 5 June 2025 | [Page] |
SIP-based Media Recording (SIPREC) protocol is defined by both RFC 7865 and RFC 7866. Unfortunately both RFCs contradict each other regarding how recording metadata is to be labeled. In addition, neither RFCs registered the new media type. This document updates RFC 7866 to align with RFC 7865 when labeling recording metadata and registers the new media type.¶
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-mongrain-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/.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents 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 5 June 2025.¶
Copyright (c) 2024 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) 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.¶
SIPREC is defined by [RFC7865] and [RFC7866]. The former specifies the use of 'application/rs-metadata+xml' when identifying metadata content whereas the latter uses "application/rs-metadata". And since neither documents registered the media type with IANA, this document does.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
Everywhere the following text occurs:¶
application/rs-metadata¶
Replace with:¶
application/rs-metadata+xml¶
The updates specified in this memo clarifies inconsistencies in published documents with regards to identifying recording metadata. It introduces no new security considerations beyond those listed in [RFC7866].¶
[RFC7865] defined a MIME media type for use with specifying recording metadata in XML data. This media type MUST 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 [RFC7303].¶
Security considerations: See Section 4.¶
Interoperability considerations: Please note that [RFC7866] specified the use of "application/rs-metadata", which this document corrects.¶
Published specification: [RFC7865]¶
Applications which use this media type: SIPREC Clients (SRC) and Servers (SRS).¶
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¶
Acknowledgments to Brian Rosen for his guidance with writing my first internet draft using the new tools and for his review.¶