Re: [siprec] RFC 8068 on Session Initiation Protocol (SIP) Recording Call Flows
Leon Portman <leon.portman@gmail.com> Tue, 28 February 2017 21:17 UTC
Return-Path: <leon.portman@gmail.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 01F451296FD for <siprec@ietfa.amsl.com>; Tue, 28 Feb 2017 13:17:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 55KPDgJU-6XT for <siprec@ietfa.amsl.com>; Tue, 28 Feb 2017 13:17:18 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45E1A1296CD for <siprec@ietf.org>; Tue, 28 Feb 2017 13:17:18 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id 196so25980776wmm.1 for <siprec@ietf.org>; Tue, 28 Feb 2017 13:17:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=geVDIDr6r/f20VSbIZk30G7lMbFUt+0AtGjv/Uq+Iy8=; b=q59tORbqIUwp30XJezZm7d79dYG7rwhlXa0rdOnmYCFsbF2Xe+2iISC/rl0UnQQg31 JgJSBaVgSoF6GgBK6Z9UDUIulUWHJlP8DQ1xR/Ki9TY2SyrzpIxrfL7+KG14VSxlYFg6 coRbcQW8To9BX4RNty5qXTJqoFNFzBHLGbZQi5RyDKxlNfQ9OX/I+efxcrsENU3xNv4u UR9kElZnJB/71ifHsdGBeh/8rF/OR0BBD6JL8CglCiV/IxdhsQTDtsZyUUDXmRlPYOc8 vSFaOMSfskobte1VoM1iY3yBoLOwTQ7ISdncYOGe2froi4rfs/oM52NfD+kC9yvDdwih iMDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=geVDIDr6r/f20VSbIZk30G7lMbFUt+0AtGjv/Uq+Iy8=; b=k+26StVowCbpacHO41oUrFRnDM/KyyyQTKy1TJd0CN9KyhYIFaQYshjsQPtydpVNNe gDtBTjYlaPK1fcDnC21ewNQO395VJDDzHD8birl5TR6UR9GoFz6O69rivhKOpOljj3Pn MwryMO5XxmoJj2Ls1+plN02/qqImO7LRtOqc4gkfhDj0KAa9vL/lbMZJlyWnvgL/+gmo YD58urtDaCQtgTDGQCIhDUJOW7EPi4YQ2zq7sZPoWvBTFgCQ7hcOf5Svf2Jxnt8/z5yd RvyQvx7t+0ygFHBNsphjJej/dAh2uFlsp5v/00nY3d6VldgbJkkyAfJ22aRNhef50fzG 37Lg==
X-Gm-Message-State: AMke39kwmsrp6AOTKIYahwHJ4vzLPlk2l5VpV0sFtSyF51GO+px81ggbANlDpWGo7Y7BOg==
X-Received: by 10.28.111.75 with SMTP id k72mr481186wmc.39.1488316636798; Tue, 28 Feb 2017 13:17:16 -0800 (PST)
Received: from [10.0.0.6] (bzq-79-180-92-50.red.bezeqint.net. [79.180.92.50]) by smtp.gmail.com with ESMTPSA id p185sm1361021wme.20.2017.02.28.13.17.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Feb 2017 13:17:15 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Leon Portman <leon.portman@gmail.com>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <45D38D98-9911-4D20-8837-9A695CF54E16@cisco.com>
Date: Tue, 28 Feb 2017 23:17:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC02942D-DEB0-469F-9C83-8480AF98CC22@gmail.com>
References: <20170228193556.90D7DB80321@rfc-editor.org> <d581558f-fa24-b328-2cd3-459a41cf6277@comcast.net> <45D38D98-9911-4D20-8837-9A695CF54E16@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/siprec/tNR192KFFYyiWypXPoCWxcXACDY>
Cc: Paul Kyzivat <paul.kyzivat@comcast.net>, "siprec@ietf.org" <siprec@ietf.org>
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 21:17:20 -0000
great!!! Best Regards Leon > On 28 Feb 2017, at 22:25, Charles Eckel (eckelcu) <eckelcu@cisco.com> wrote: > > 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 > > > _______________________________________________ > siprec mailing list > siprec@ietf.org > https://www.ietf.org/mailman/listinfo/siprec
- [siprec] RFC 8068 on Session Initiation Protocol … rfc-editor
- Re: [siprec] RFC 8068 on Session Initiation Proto… Paul Kyzivat
- Re: [siprec] RFC 8068 on Session Initiation Proto… Charles Eckel (eckelcu)
- Re: [siprec] RFC 8068 on Session Initiation Proto… Leon Portman