
From nobody Sun Oct 23 17:45:02 2016
Return-Path: <alissa@cooperw.in>
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 BF8A1129447 for <siprec@ietfa.amsl.com>; Sun, 23 Oct 2016 17:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=hQUkCUY5; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=oRXAwgW0
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 IQrNH7ELpI_d for <siprec@ietfa.amsl.com>; Sun, 23 Oct 2016 17:45:00 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE765126D73 for <siprec@ietf.org>; Sun, 23 Oct 2016 17:44:59 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 51E3620863 for <siprec@ietf.org>; Sun, 23 Oct 2016 20:44:59 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 23 Oct 2016 20:44:59 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=ElA ZgyFrgm1zxxo9A0ppChP8+go=; b=hQUkCUY5yKcnCBzk9K4ISdzjzdHJn4wK5FL JthngWJsyucFVaX8s8keP8kiC8hTamjvjo5R4ptHtmos7l7M2ap6poelEYlAL0P9 mjlEeCa6KyLhqQNuInDEkMOWhdFQ2PJxQHaIB83HpbtDwfVVN02gL4XPkHjHRZgL Dr5xgsbo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=ElAZgyFrgm1zxxo9A0ppChP8+go=; b=oRXAw gW0jC05BmJOALtF3BIegKBOftCD4fh0mO5OP7L3CElePr88cbsnDOH3xiyTju0S9 hYtaMwD4he+jr8cpf7dHgen4nKzuhxZ2kpmo0Mgl+SDXN0VXR1u8RzKEW3hnIcM8 MkJmmQdh79oPYe2YxG7OpJeBoW4Is5NnB6V1f0=
X-Sasl-enc: 0k8EAjOBddWOEdpP+aJY1q0LqHWcOtXp2LUlbuy0ihLn 1477269898
Received: from sjc-alcoop-8813.cisco.com (unknown [128.107.241.181]) by mail.messagingengine.com (Postfix) with ESMTPA id C690AF29CB for <siprec@ietf.org>; Sun, 23 Oct 2016 20:44:58 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <813F4CF9-C798-4DCA-9D21-C14C12C1AA9D@cooperw.in>
Date: Sun, 23 Oct 2016 20:44:58 -0400
To: siprec@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/siprec/IehImNsoF30z3pOmYb5_MGFINbE>
Subject: [siprec] AD evaluation: draft-ietf-siprec-callflows-07
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: Mon, 24 Oct 2016 00:45:01 -0000

I have reviewed this draft in preparation for IETF last call. I believe =
it is ready for LC and will issue the request to start LC shortly. Below =
are some nits that should be resolved together with any last call =
comments:

=3D Section 3 =3D

s/sub-sections has/sub-sections have/

"In all these use-cases, the SRC is a B2BUA." --> But then you go on to =
talk about examples where the SRC is a UA. I think this sentence should =
be deleted.=20

=3D Section 3.1 =3D

The figure should have a caption.

s/may be a endpoint/may be an endpoint/

s/Special flows like Turret flows/Special flows like Turret flows (used =
on financial trading floors to manage call activity)./

=3D Section 3.3.2 =3D

s/Bob puts Alice hold/Bob puts Alice on hold/


Thanks,
Alissa=


From nobody Sun Oct 23 22:22:28 2016
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 A585F129466 for <siprec@ietfa.amsl.com>; Sun, 23 Oct 2016 22:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.952
X-Spam-Level: 
X-Spam-Status: No, score=-14.952 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.431, 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 MWI_a7POnPLm for <siprec@ietfa.amsl.com>; Sun, 23 Oct 2016 22:22:25 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C073129436 for <siprec@ietf.org>; Sun, 23 Oct 2016 22:22:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1277; q=dns/txt; s=iport; t=1477286545; x=1478496145; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=mtJKHAz8qg1pj3cnljIlsB6TlwT2SdcgW024uwJaX9E=; b=TmRIzxpPKRGZV6YgOrmAxSVCAIKbV6bDdKJVSHCFwDYZPzGLGCucRxYt jyh3csMMAB1p3YqaRudLy+c0mOpQ2JgIv7rIcxVfLLYSGWmpSd23Krvzv iT/3Jr9eSUKzGzYsm138+58zEjj21uoZUSsVUZpDAW8RbBK8253vZeg8p Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CSAQAOmg1Y/5hdJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgyoBAQEBAR1YfQcBjSyWfJQ/ggccC4UwSgKBaD8UAQIBAQEBAQEBYii?= =?us-ascii?q?EYgEBAQQBAQEkEzQXBAIBCBEDAQIfECcLHQgCBAESiFIOwhMBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBGQWLEoomBZoUAZASkAKNBoQAAR42XoUCcodBAX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.31,392,1473120000"; d="scan'208";a="338543296"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2016 05:22:24 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u9O5MOji001781 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 24 Oct 2016 05:22:24 GMT
Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 24 Oct 2016 01:22:23 -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.1210.000; Mon, 24 Oct 2016 01:22:23 -0400
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Alissa Cooper <alissa@cooperw.in>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] AD evaluation: draft-ietf-siprec-callflows-07
Thread-Index: AQHSLbaZ3cKCdmwiU0KvEAWoFD5W+g==
Date: Mon, 24 Oct 2016 05:22:23 +0000
Message-ID: <D4339850.6CE49%rmohanr@cisco.com>
References: <813F4CF9-C798-4DCA-9D21-C14C12C1AA9D@cooperw.in>
In-Reply-To: <813F4CF9-C798-4DCA-9D21-C14C12C1AA9D@cooperw.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.8.160830
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [72.163.172.135]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B615778BD7C4734C80A5DD3A10B95F59@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/siprec/C5SxieyCSM5Uj9lZVLXdurUYZ5U>
Subject: Re: [siprec] AD evaluation: draft-ietf-siprec-callflows-07
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: Mon, 24 Oct 2016 05:22:26 -0000

Thanks Alissa. Will take care of these nits.

Regards,
Ram

-----Original Message-----
From: siprec <siprec-bounces@ietf.org> on behalf of Alissa Cooper
<alissa@cooperw.in>
Date: Monday, 24 October 2016 at 6:14 AM
To: "siprec@ietf.org" <siprec@ietf.org>
Subject: [siprec] AD evaluation: draft-ietf-siprec-callflows-07

>I have reviewed this draft in preparation for IETF last call. I believe
>it is ready for LC and will issue the request to start LC shortly. Below
>are some nits that should be resolved together with any last call
>comments:
>
>=3D Section 3 =3D
>
>s/sub-sections has/sub-sections have/
>
>"In all these use-cases, the SRC is a B2BUA." --> But then you go on to
>talk about examples where the SRC is a UA. I think this sentence should
>be deleted.=20
>
>=3D Section 3.1 =3D
>
>The figure should have a caption.
>
>s/may be a endpoint/may be an endpoint/
>
>s/Special flows like Turret flows/Special flows like Turret flows (used
>on financial trading floors to manage call activity)./
>
>=3D Section 3.3.2 =3D
>
>s/Bob puts Alice hold/Bob puts Alice on hold/
>
>
>Thanks,
>Alissa
>_______________________________________________
>siprec mailing list
>siprec@ietf.org
>https://www.ietf.org/mailman/listinfo/siprec


From nobody Mon Oct 24 06:39:18 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: siprec@ietf.org
Delivered-To: siprec@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 03F7D1296D0; Mon, 24 Oct 2016 06:39:13 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <147731635297.15419.10341586950868522371.idtracker@ietfa.amsl.com>
Date: Mon, 24 Oct 2016 06:39:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/siprec/oxSvT7KuqcxXWK9DyKT_EIMSlag>
Cc: siprec@ietf.org, Andrew Hutton <andrew.hutton@unify.com>, draft-ietf-siprec-callflows@ietf.org, siprec-chairs@ietf.org
Subject: [siprec] Last Call: <draft-ietf-siprec-callflows-07.txt> (Session Initiation Protocol (SIP) Recording Call Flows) to Informational RFC
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
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: Mon, 24 Oct 2016 13:39:13 -0000

The IESG has received a request from the SIP Recording WG (siprec) to
consider the following document:
- 'Session Initiation Protocol (SIP) Recording Call Flows'
  <draft-ietf-siprec-callflows-07.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-11-27. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


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




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-siprec-callflows/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-siprec-callflows/ballot/


No IPR declarations have been submitted directly on this I-D.




