[siprec] RFC 7245 on An Architecture for Media Recording Using the Session Initiation Protocol

rfc-editor@rfc-editor.org Thu, 22 May 2014 01:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B9B41A002E; Wed, 21 May 2014 18:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 dLhrJUOBa4PB; Wed, 21 May 2014 18:40:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5DBFE1A0029; Wed, 21 May 2014 18:40:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EB92A18000D; Wed, 21 May 2014 18:39:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140522013948.EB92A18000D@rfc-editor.org>
Date: Wed, 21 May 2014 18:39:48 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/dTvJUq18h7getYOqqTrkvBP1chw
Cc: drafts-update-ref@iana.org, siprec@ietf.org, rfc-editor@rfc-editor.org
Subject: [siprec] RFC 7245 on An Architecture for Media Recording Using the Session Initiation Protocol
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 22 May 2014 01:40:05 -0000

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

        
        RFC 7245

        Title:      An Architecture for Media Recording 
                    Using the Session Initiation Protocol 
        Author:     A. Hutton, Ed., L. Portman, Ed.,
                    R. Jain, K. Rehor
        Status:     Informational
        Stream:     IETF
        Date:       May 2014
        Mailbox:    andrew.hutton@unify.com, 
                    leon.portman@gmail.com, 
                    rajnish.jain@outlook.com,
                    krehor@cisco.com
        Pages:      16
        Characters: 34314
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-siprec-architecture-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7245.txt

Session recording is a critical requirement in many communications
environments such as call centers and financial trading.  In some of
these environments, all calls must be recorded for regulatory,
compliance, and consumer protection reasons.  Recording of a session
is typically performed by sending a copy of a media stream to a
recording device.  This document describes architectures for
deploying session recording solutions in an environment that is based
on the Session Initiation Protocol (SIP).

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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