Last Call: <draft-ietf-siprec-callflows-07.txt> (Session Initiation Protocol (SIP) Recording Call Flows) to Informational RFC

The IESG <> Mon, 24 October 2016 13:39 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 03F7D1296D0; Mon, 24 Oct 2016 06:39:13 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-siprec-callflows-07.txt> (Session Initiation Protocol (SIP) Recording Call Flows) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 24 Oct 2016 06:39:12 -0700
Archived-At: <>
Cc:, Andrew Hutton <>,,
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 24 Oct 2016 13:39:13 -0000

The IESG has received a request from the SIP Recording WG (siprec) to
consider the following document:
- 'Session Initiation Protocol (SIP) Recording Call Flows'
  <draft-ietf-siprec-callflows-07.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2016-11-27. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   Session recording is a critical requirement in many communications
   environments, such as call centers and financial trading
   organizations.  In some of these environments, all calls must be
   recorded for regulatory, compliance, and consumer protection reasons.
   The recording of a session is typically performed by sending a copy
   of a media stream to a recording device.  This document lists call
   flows with metadata snapshots sent from a Session Recording
   Client(SRC) to a Session Recording Server(SRS).

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.