[siprec] RFC 8068 on Session Initiation Protocol (SIP) Recording Call Flows

rfc-editor@rfc-editor.org Tue, 28 February 2017 19:35 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E43981296A0; Tue, 28 Feb 2017 11:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lmv3Lb_iuKXl; Tue, 28 Feb 2017 11:35:56 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9855712969D; Tue, 28 Feb 2017 11:35:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 90D7DB80321; Tue, 28 Feb 2017 11:35:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170228193556.90D7DB80321@rfc-editor.org>
Date: Tue, 28 Feb 2017 11:35:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/siprec/1-u0U46AbSVfCL7n9clPlEvHQSs>
Cc: drafts-update-ref@iana.org, siprec@ietf.org, rfc-editor@rfc-editor.org
Subject: [siprec] RFC 8068 on Session Initiation Protocol (SIP) Recording Call Flows
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/siprec/>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 19:35:58 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8068

        Title:      Session Initiation Protocol (SIP) Recording 
                    Call Flows 
        Author:     R. Ravindranath, 
                    P. Ravindran,
                    P. Kyzivat
        Status:     Informational
        Stream:     IETF
        Date:       February 2017
        Mailbox:    rmohanr@cisco.com, 
                    partha@parthasarathi.co.in, 
                    pkyzivat@alum.mit.edu
        Pages:      34
        Characters: 65705
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-siprec-callflows-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8068

        DOI:        10.17487/RFC8068

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).

This document is a product of the SIP Recording Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC