Re: [siprec] FW: RFC 7866 on Session Recording Protocol

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Wed, 01 June 2016 16:03 UTC

Return-Path: <rmohanr@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 0876112B061 for <siprec@ietfa.amsl.com>; Wed, 1 Jun 2016 09:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 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=-1.426, 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 UgurDAnXnVI0 for <siprec@ietfa.amsl.com>; Wed, 1 Jun 2016 09:02:59 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F32312D5D6 for <siprec@ietf.org>; Wed, 1 Jun 2016 09:02:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6520; q=dns/txt; s=iport; t=1464796966; x=1466006566; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=6L8jlX8dyr6bgXnBNuvc7wPMycGKuHnpRVEntJ/DFM4=; b=fBwBhlN8y1DTnKECIfvaT8W1SXDEIGenu/Y4oePsA1e0WtTeLpgyrVzB 7B8b7SPbnHN8Grf5eiHW73VGEdSsP/3Y8dh+l5PNjiWeLEUn9n5VuI50k rPh1Az0IHX5TwOTzUvbXZ8DxhkUtVezy2WZ2QDKm+6KQf+4x45wMEQlyA Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AWAgAVBk9X/4YNJK1cgz1WfQauIYtvAQ2BehcLhSVKAhyBFDgUAQEBAQEBAWUnhEUBAQEEAQEBIBEaIBcEAgEGAhEDAQEBAwIIGwMCAgIfBgoBFAEHAQgCBAESFAYBAgSHdAMXDpJCnR2NHQ2EHwEBAQEBAQEBAQEBAQEBAQEBAQEBARyBAYhwgQOBOYEKgV4JFoMBglkFmAQzAYV/hieBeYFphE+IZIYzgTGHZwEeAQFCghOBWm4BiQE2fwEBAQ
X-IronPort-AV: E=Sophos;i="5.26,401,1459814400"; d="scan'208";a="278935886"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Jun 2016 16:02:45 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u51G2jtd010855 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 1 Jun 2016 16:02:45 GMT
Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 1 Jun 2016 12:02:44 -0400
Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1104.009; Wed, 1 Jun 2016 12:02:44 -0400
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Leon Portman <leon.portman@gmail.com>, "Hutton, Andrew" <andrew.hutton@unify.com>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] FW: RFC 7866 on Session Recording Protocol
Thread-Index: AQHRvB8Iko29epLFq0y3A5tmbeLRbA==
Date: Wed, 01 Jun 2016 16:02:44 +0000
Message-ID: <D375045C.5E4FB%rmohanr@cisco.com>
References: <9F33F40F6F2CD847824537F3C4E37DDF2611DD8D@MCHP04MSX.global-ad.net> <198E65B5-9AC6-4222-825F-55AE101A98D3@gmail.com>
In-Reply-To: <198E65B5-9AC6-4222-825F-55AE101A98D3@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.87.58]
Content-Type: text/plain; charset="utf-8"
Content-ID: <41225A99FE978042B892BE448A0B2ACB@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/4ZWUn56pdJ5SgqO-0sr-7u6wVjQ>
Subject: Re: [siprec] FW: RFC 7866 on Session Recording Protocol
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: Wed, 01 Jun 2016 16:03:02 -0000

Yes. It took a while for sure.
I will be in Berlin and we should meet up to celebrate :)

Ram

-----Original Message-----
From: siprec <siprec-bounces@ietf.org> on behalf of Leon Portman
<leon.portman@gmail.com>
Date: Wednesday, 1 June 2016 at 7:10 PM
To: "Hutton, Andrew" <andrew.hutton@unify.com>
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] FW:  RFC 7866 on Session Recording Protocol

>Yes, it is. It took a while :)
>
>
>Best Regards 
>
>Leon
>
>> On 1 ביוני 2016, at 16:24, Hutton, Andrew <andrew.hutton@unify.com>
>>wrote:
>> 
>> Great news it's been a bit of a journey but with RFC 7865 and 7866
>>being published we are almost done.
>> 
>> We should have a bit of a celebration in Berlin if any of you are
>>around.
>> 
>> Regards
>> Andy (SIPREC Co-chair).
>> 
>> 
>> 
>> 
>> -----Original Message-----
>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of
>>rfc-editor@rfc-editor.org
>> Sent: 01 June 2016 01:42
>> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
>> Cc: drafts-update-ref@iana.org; siprec@ietf.org;
>>rfc-editor@rfc-editor.org
>> Subject: [siprec] RFC 7866 on Session Recording Protocol
>> 
>> A new Request for Comments is now available in online RFC libraries.
>> 
>> 
>>        RFC 7866
>> 
>>        Title:      Session Recording Protocol
>>        Author:     L. Portman, H. Lum, Ed.,
>>                    C. Eckel, A. Johnston, A. Hutton
>>        Status:     Standards Track
>>        Stream:     IETF
>>        Date:       May 2016
>>        Mailbox:    leon.portman@gmail.com,
>>                    henry.lum@genesyslab.com,
>>                    eckelcu@cisco.com,
>>                    alan.b.johnston@gmail.com,
>>                    andrew.hutton@unify.com
>>        Pages:      45
>>        Characters: 104535
>>        Updates/Obsoletes/SeeAlso:   None
>> 
>>        I-D Tag:    draft-ietf-siprec-protocol-18.txt
>> 
>>        URL:        https://www.rfc-editor.org/info/rfc7866
>> 
>>        DOI:        http://dx.doi.org/10.17487/RFC7866
>> 
>> This document specifies the use of the Session Initiation Protocol
>> (SIP), the Session Description Protocol (SDP), and the Real-time
>> Transport Protocol (RTP) for delivering real-time media and metadata
>> from a Communication Session (CS) to a recording device.  The Session
>> Recording Protocol specifies the use of SIP, SDP, and RTP to
>> establish a Recording Session (RS) between the Session Recording
>> Client (SRC), which is on the path of the CS, and a Session Recording
>> Server (SRS) at the recording device.  This document considers only
>> active recording, where the SRC purposefully streams media to an SRS
>> and all participating user agents (UAs) are notified of the
>> recording.  Passive recording, where a recording device detects media
>> directly from the network (e.g., using port-mirroring techniques), is
>> outside the scope of this document.  In addition, lawful intercept is
>> outside the scope of this document.
>> 
>> This document is a product of the SIP Recording Working Group of the
>>IETF.
>> 
>> This is now a Proposed Standard.
>> 
>> STANDARDS TRACK: This document specifies an Internet Standards Track
>> protocol for the Internet community, and requests discussion and
>>suggestions
>> for improvements.  Please refer to the current edition of the Official
>> Internet Protocol Standards (https://www.rfc-editor.org/standards) for
>>the 
>> standardization state and status of this protocol.  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
>
>_______________________________________________
>siprec mailing list
>siprec@ietf.org
>https://www.ietf.org/mailman/listinfo/siprec