Protocol Action: 'Updates to SIPREC correcting Metadata Media Type' to Proposed Standard (draft-ietf-sipcore-siprec-fix-mediatype-06.txt)

The IESG <iesg-secretary@ietf.org> Mon, 12 May 2025 19:07 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from [10.244.8.181] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 4915B27B1665; Mon, 12 May 2025 12:07:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Updates to SIPREC correcting Metadata Media Type' to Proposed Standard (draft-ietf-sipcore-siprec-fix-mediatype-06.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 12.39.2
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <174707684909.1663713.6332308776610832944@dt-datatracker-58d4498dbd-6gzjf>
Date: Mon, 12 May 2025 12:07:29 -0700
Message-ID-Hash: IV25ZE4YLTXP7DTTVR4CIGESJW2UNLEG
X-Message-ID-Hash: IV25ZE4YLTXP7DTTVR4CIGESJW2UNLEG
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, draft-ietf-sipcore-siprec-fix-mediatype@ietf.org, pkyzivat@alum.mit.edu, rfc-editor@rfc-editor.org, sipcore-chairs@ietf.org, sipcore@ietf.org
X-Mailman-Version: 3.3.9rc6
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/yZFiJh0wlBc-jwgARLSRrYPmAy0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

The IESG has approved the following document:
- 'Updates to SIPREC correcting Metadata Media Type'
  (draft-ietf-sipcore-siprec-fix-mediatype-06.txt) as Proposed Standard

This document is the product of the Session Initiation Protocol Core Working
Group.

The IESG contact persons are Andy Newton and Orie Steele.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-siprec-fix-mediatype/




Technical Summary

   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.

Working Group Summary

   SIPREC is mandatory to implement in Public Safety (as per the National
   Emergency Number Association (NENA) standard NENA i3 Standard for Next
   Generation 9-1-1, NENA-STA-010.3f-2021. That standard calls out the relevant
   IETF standards, including RFCs 7865 and 7866, the targets of this document.
   Just a few people handle most of the interaction with IETF.

   Four people in addition to the author expressed interest in having the document
   adopted. After adoption two people, plus this sipcore chairs, supported it
   progressing. No one was opposed. (There was one editorial comment, which has
   been addressed.)

Document Quality

   SIPREC is extensively implemented by both 9-1-1 call handling systems (CHS) and
   media logging vendors. The author reports being aware of ten commercial
   implementations. The problem addressed by this document was discovered in NENA
   industry collaboration events.

   Also, the protocol very likely has a relatively high adoption in enterprise
   call center recording technologies as some of the same vendors are involved and
   there are no known competing IP-based protocols for this purpose.

   This document was reviewed by the media-type designated experts on the media-types
   mailing list with a request date of 1 April 2025.

Personnel

   The Document Shepherd for this document is Paul Kyzivat. The Responsible
   Area Director is Andy Newton.