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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Tue, 28 February 2017 20:25 UTC

Return-Path: <eckelcu@cisco.com>
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 F34B51296C7 for <siprec@ietfa.amsl.com>; Tue, 28 Feb 2017 12:25:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 RXmhbw3vBL9e for <siprec@ietfa.amsl.com>; Tue, 28 Feb 2017 12:25:54 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DAB21296C5 for <siprec@ietf.org>; Tue, 28 Feb 2017 12:25:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4574; q=dns/txt; s=iport; t=1488313554; x=1489523154; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=wQ05vmyVNBzPOhQEcbz8tXOu/RafpwWGRrRQjRNuN+E=; b=fIh3UY46emT/Xwf72ICCM6DjSK2GW1BcyzOqiFSU060+UdvrJKfr0nIL Nd1Pvg2BuGapkFtEvwt/SWOShtRnRBZWf+zrhlwy6AHJfdtjtjHCDuQZM DoMJ+CVwfPvQNu6Aw6MQYfiKccg/m927ZGXhJaWbrMwz0kBZSPzXZIHVS 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DPAQBB3LVY/4gNJK1dGQEBAQEBAQEBAQEBBwEBAQEBg1BhgQkHg1SKCJFEH5U1gg0fC4UuSgIaghQ/GAECAQEBAQEBAWIohHABAQEEAQEhERogFwQCAQgRAwECAQICCB4CAgIlCgEVCAgCBAESFAcCBIlWDrFFgiaLLgEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQuHRgiCYoE8gnkJFoMGLoIxBZVxhjIBhnOLOJEYkzEBHziBAVQVGCYRAYRKgXF1h0KBIYENAQEB
X-IronPort-AV: E=Sophos;i="5.35,221,1484006400"; d="scan'208";a="389948389"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Feb 2017 20:25:53 +0000
Received: from XCH-RCD-019.cisco.com (xch-rcd-019.cisco.com [173.37.102.29]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1SKPrwC005917 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 28 Feb 2017 20:25:53 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-019.cisco.com (173.37.102.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 28 Feb 2017 14:25:52 -0600
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Tue, 28 Feb 2017 14:25:52 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Paul Kyzivat <paul.kyzivat@comcast.net>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] RFC 8068 on Session Initiation Protocol (SIP) Recording Call Flows
Thread-Index: AQHSkfqMQGKIfBoxdEeFaxLgITJ/bqF+vDkA
Date: Tue, 28 Feb 2017 20:25:52 +0000
Message-ID: <45D38D98-9911-4D20-8837-9A695CF54E16@cisco.com>
References: <20170228193556.90D7DB80321@rfc-editor.org> <d581558f-fa24-b328-2cd3-459a41cf6277@comcast.net>
In-Reply-To: <d581558f-fa24-b328-2cd3-459a41cf6277@comcast.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.156.130.248]
Content-Type: text/plain; charset="utf-8"
Content-ID: <41570BBF6A51AF488DCF18E03E78B5A7@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/siprec/HpaoTdmJT1S2QEvnt_ucuRTcwE8>
Subject: Re: [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 20:25:56 -0000

Congrats everyone!

-----Original Message-----
From: "siprec-bounces@ietf.org" <siprec-bounces@ietf.org> on behalf of Paul Kyzivat <paul.kyzivat@comcast.net>
Date: Tuesday, February 28, 2017 at 11:40 AM
To: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] RFC 8068 on Session Initiation Protocol (SIP) Recording Call Flows

    DONE !!!!
    
    Thanks to all.
    
    	Paul
    
    On 2/28/17 2:35 PM, rfc-editor@rfc-editor.org wrote:
    > 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
    >
    >
    > _______________________________________________
    > siprec mailing list
    > siprec@ietf.org
    > https://www.ietf.org/mailman/listinfo/siprec
    >
    
    _______________________________________________
    siprec mailing list
    siprec@ietf.org
    https://www.ietf.org/mailman/listinfo/siprec