
From Henry.Lum@alcatel-lucent.com  Tue Mar  1 09:12:14 2011
Return-Path: <Henry.Lum@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 274293A69B2 for <siprec@core3.amsl.com>; Tue,  1 Mar 2011 09:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vosQN3Z7ivsI for <siprec@core3.amsl.com>; Tue,  1 Mar 2011 09:12:13 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 412523A69F8 for <siprec@ietf.org>; Tue,  1 Mar 2011 09:12:12 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p21HDDTG010772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <siprec@ietf.org>; Tue, 1 Mar 2011 11:13:14 -0600 (CST)
Received: from relay-out2.dc (relay-out2.dc.genesyslab.com [172.22.68.188]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p21HDBCh013958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <siprec@ietf.org>; Tue, 1 Mar 2011 11:13:13 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out2.dc (8.13.8+Sun/8.13.8) with ESMTP id p21HDBKS003027 for <siprec@ietf.org>; Tue, 1 Mar 2011 09:13:11 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.93]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Mar 2011 09:13:11 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Tue, 1 Mar 2011 09:13:11 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Version Notification for draft-portman-siprec-protocol-03 
Thread-Index: AcvYM3sxqcWx8xd4TLKF+49QTrDGQgAAAi+Q
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: <siprec@ietf.org>
X-OriginalArrivalTime: 01 Mar 2011 17:13:11.0429 (UTC) FILETIME=[F1596350:01CBD833]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: [siprec] FW: New Version Notification for draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Mar 2011 17:12:14 -0000

QSBuZXcgdmVyc2lvbiBoYXMgYmVlbiBzdWJtaXR0ZWQgdG8gYWRkcmVzcyB0aGUgb3V0c3RhbmRp
bmcgaXNzdWVzIGFuZCBpbmNsdWRlIGV4dGVuc2lvbnMgZm9yIHRoZSBuZXcgd29yZGluZyBmb3Ig
UkVRLTAxNyBhbmQgUkVRLTAxOC4NCg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtcG9ydG1hbi1zaXByZWMtcHJvdG9jb2wvDQoNClJlZ2FyZHMsDQpIZW5yeQ0KDQotLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSUVURiBJLUQgU3VibWlzc2lvbiBUb29sIFtt
YWlsdG86aWRzdWJtaXNzaW9uQGlldGYub3JnXSANClNlbnQ6IFR1ZXNkYXksIE1hcmNoIDAxLCAy
MDExIDEyOjA5IFBNDQpUbzogSGVucnkgTHVtDQpDYzogbGVvbi5wb3J0bWFuQG5pY2UuY29tOyBh
bGFuLmIuam9obnN0b25AZ21haWwuY29tOyBhbmRyZXcuaHV0dG9uQHNpZW1lbnMtZW50ZXJwcmlz
ZS5jb20NClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtcG9ydG1h
bi1zaXByZWMtcHJvdG9jb2wtMDMgDQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXBv
cnRtYW4tc2lwcmVjLXByb3RvY29sLTAzLnR4dCBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0
dGVkIGJ5IEhlbnJ5IEx1bSBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoNCkZp
bGVuYW1lOgkgZHJhZnQtcG9ydG1hbi1zaXByZWMtcHJvdG9jb2wNClJldmlzaW9uOgkgMDMNClRp
dGxlOgkJIFRoZSBTSVAtYmFzZWQgTWVkaWEgUmVjb3JkaW5nIFByb3RvY29sIChTSVBSRUMpDQpD
cmVhdGlvbl9kYXRlOgkgMjAxMS0wMy0wMQ0KV0cgSUQ6CQkgSW5kZXBlbmRlbnQgU3VibWlzc2lv
bg0KTnVtYmVyX29mX3BhZ2VzOiAyMA0KDQpBYnN0cmFjdDoNClNJUFJFQyBTZXNzaW9uIFJlY29y
ZGluZyBQcm90b2NvbCBpcyB1c2VkIGZvciBlc3RhYmxpc2hpbmcgcmVjb3JkaW5nDQpzZXNzaW9u
IGFuZCByZXBvcnRpbmcgb2YgdGhlIG1ldGFkYXRhIG9mIHRoZSBjb21tdW5pY2F0aW9uIHNlc3Np
b24uDQoNClRoaXMgZG9jdW1lbnQgc3BlY2lmaWVzIHRoZSBTSVBSRUMgUHJvdG9jb2wgKFNJUFJF
QykuICBTSVBSRUMgaXMgdXNlZA0KYmV0d2VlbiBTZXNzaW9uIFJlY29yZGluZyBDbGllbnQgKFNS
QykgYW5kIFNlc3Npb24gUmVjb3JkaW5nIFNlcnZlcg0KKFNSUykuDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgDQoNCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQuDQoNCg0KDQoJCQkJCQ0KLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KQ09O
RklERU5USUFMSVRZIE5PVElDRTogVGhpcyBlLW1haWwgYW5kIGFueSBmaWxlcyBhdHRhY2hlZCBt
YXkgY29udGFpbiBjb25maWRlbnRpYWwgYW5kIHByb3ByaWV0YXJ5IGluZm9ybWF0aW9uIG9mIEFs
Y2F0ZWwtTHVjZW50IGFuZC9vciBpdHMgYWZmaWxpYXRlZCBlbnRpdGllcy4gQWNjZXNzIGJ5IHRo
ZSBpbnRlbmRlZCByZWNpcGllbnQgb25seSBpcyBhdXRob3JpemVkLiBBbnkgbGlhYmlsaXR5IGFy
aXNpbmcgZnJvbSBhbnkgcGFydHkgYWN0aW5nLCBvciByZWZyYWluaW5nIGZyb20gYWN0aW5nLCBv
biBhbnkgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgZS1tYWlsIGlzIGhlcmVieSBleGNs
dWRlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgcGxlYXNlIG5vdGlm
eSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5LCBkZXN0cm95IHRoZSBvcmlnaW5hbCB0cmFuc21pc3Np
b24gYW5kIGl0cyBhdHRhY2htZW50cyBhbmQgZG8gbm90IGRpc2Nsb3NlIHRoZSBjb250ZW50cyB0
byBhbnkgb3RoZXIgcGVyc29uLCB1c2UgaXQgZm9yIGFueSBwdXJwb3NlLCBvciBzdG9yZSBvciBj
b3B5IHRoZSBpbmZvcm1hdGlvbiBpbiBhbnkgbWVkaXVtLiBDb3B5cmlnaHQgaW4gdGhpcyBlLW1h
aWwgYW5kIGFueSBhdHRhY2htZW50cyBiZWxvbmdzIHRvIEFsY2F0ZWwtTHVjZW50IGFuZC9vciBp
dHMgYWZmaWxpYXRlZCBlbnRpdGllcy4NCgkJCQkJDQo=

From pkyzivat@cisco.com  Tue Mar  1 10:50:29 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 843B43A6A31 for <siprec@core3.amsl.com>; Tue,  1 Mar 2011 10:50:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.55
X-Spam-Level: 
X-Spam-Status: No, score=-110.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mLUrACbrFUb for <siprec@core3.amsl.com>; Tue,  1 Mar 2011 10:50:28 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 7B6983A6A16 for <siprec@ietf.org>; Tue,  1 Mar 2011 10:50:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=2876; q=dns/txt; s=iport; t=1299005492; x=1300215092; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=99kFaWb8ZwdkarHyCKclrAZtPTVaTHTO/Pqram8iyfM=; b=fPKDTKmnbBxfUbBpaYttB+sEzghs6A+F89tlywa3nJ6RPTq79NTsqGjZ /In5JkdTroZbT5cEzxREZFFnZNh1gdzYlQKPqthdlVOwdfxLu9eXpSlTj jX01FQgcn5Bw0lkYqM5MSUWn+NIkFaGs7+MAAvCcvZfQ94lfeH3sY2hVA Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkUBAOLObE2rR7H+/2dsb2JhbACXej+OFnSgVpwchWEEhRKHDYNAgxQ
X-IronPort-AV: E=Sophos;i="4.62,248,1297036800"; d="scan'208";a="337176178"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 01 Mar 2011 18:50:14 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p21IoD8i015232 for <siprec@ietf.org>; Tue, 1 Mar 2011 18:50:14 GMT
Message-ID: <4D6D3FE5.9000902@cisco.com>
Date: Tue, 01 Mar 2011 13:50:13 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: siprec@ietf.org
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com>
In-Reply-To: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] FW: New Version Notification for	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Mar 2011 18:50:29 -0000

Thanks Henry.

One comment/question:

Is there a reason to use an Info package for Requesting for metadata 
snapshot? Since we are already defining c-d recording-session and 
passing bodies in invite/update for it, is there a reason not to use the 
same mechanism to send error notifications/snapshop requests?

(I'm thinking just using a different content-type for this, and of 
course sending it from SRS to SRC.)

Also, we could consider permitting (not requiring) this in the responses 
to the messages containing metadata.

	Thanks,
	Paul


On 3/1/2011 12:13 PM, Henry Lum wrote:
> A new version has been submitted to address the outstanding issues and include extensions for the new wording for REQ-017 and REQ-018.
>
> https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
>
> Regards,
> Henry
>
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: Tuesday, March 01, 2011 12:09 PM
> To: Henry Lum
> Cc: leon.portman@nice.com; alan.b.johnston@gmail.com; andrew.hutton@siemens-enterprise.com
> Subject: New Version Notification for draft-portman-siprec-protocol-03
>
>
> A new version of I-D, draft-portman-siprec-protocol-03.txt has been successfully submitted by Henry Lum and posted to the IETF repository.
>
> Filename:	 draft-portman-siprec-protocol
> Revision:	 03
> Title:		 The SIP-based Media Recording Protocol (SIPREC)
> Creation_date:	 2011-03-01
> WG ID:		 Independent Submission
> Number_of_pages: 20
>
> Abstract:
> SIPREC Session Recording Protocol is used for establishing recording
> session and reporting of the metadata of the communication session.
>
> This document specifies the SIPREC Protocol (SIPREC).  SIPREC is used
> between Session Recording Client (SRC) and Session Recording Server
> (SRS).
>
>
>
> The IETF Secretariat.
>
>
>
> 					
> -------------------------------------------------------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.
> 					
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>

From Henry.Lum@alcatel-lucent.com  Tue Mar  1 11:32:03 2011
Return-Path: <Henry.Lum@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86F933A6A81 for <siprec@core3.amsl.com>; Tue,  1 Mar 2011 11:32:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-8ACkUTJ4a4 for <siprec@core3.amsl.com>; Tue,  1 Mar 2011 11:32:02 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 5EED03A6A82 for <siprec@ietf.org>; Tue,  1 Mar 2011 11:32:01 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p21JX4p3021651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 1 Mar 2011 13:33:04 -0600 (CST)
Received: from relay-out1.dc.genesyslab.com (relay-out1.dc.genesyslab.com [172.22.68.187]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p21JX2Ke002231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 1 Mar 2011 13:33:04 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.dc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id p21JX0Is011602; Tue, 1 Mar 2011 11:33:01 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.93]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Mar 2011 11:33:00 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 1 Mar 2011 11:32:59 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com>
In-Reply-To: <4D6D3FE5.9000902@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New Version Notificationfor	draft-portman-siprec-protocol-03
Thread-Index: AcvYQbNW+nce0F8JRE+losKTZIqUSQAAsfXQ
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com> <4D6D3FE5.9000902@cisco.com>
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 01 Mar 2011 19:33:00.0949 (UTC) FILETIME=[79E48C50:01CBD847]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [siprec] FW: New Version Notificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 01 Mar 2011 19:32:03 -0000

When there is an UPDATE transaction collision, you will have to make
both SRC and SRS to wait a while before being able to send UPDATE again.
Since SRC is normally the side initiating the SIP dialog, it is the
owner of the Call-ID and will come second after the SRS has a chance to
resend the UPDATE. In that case, does the SRC keep the existing UPDATE
or send a new snapshot as requested by the SRS? The SRC also need to
keep track of metadata changes while waiting for the timer. I worry that
it will make the solution more complicated than just using an INFO for
snapshot request and minimize the collision problem.

Regards,
Henry

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
> Sent: Tuesday, March 01, 2011 1:50 PM
> To: siprec@ietf.org
> Subject: Re: [siprec] FW: New Version Notificationfor draft-portman-
> siprec-protocol-03
>=20
> Thanks Henry.
>=20
> One comment/question:
>=20
> Is there a reason to use an Info package for Requesting for metadata
> snapshot? Since we are already defining c-d recording-session and
> passing bodies in invite/update for it, is there a reason not to use
> the
> same mechanism to send error notifications/snapshop requests?
>=20
> (I'm thinking just using a different content-type for this, and of
> course sending it from SRS to SRC.)
>=20
> Also, we could consider permitting (not requiring) this in the
> responses
> to the messages containing metadata.
>=20
> 	Thanks,
> 	Paul
>=20
>=20
> On 3/1/2011 12:13 PM, Henry Lum wrote:
> > A new version has been submitted to address the outstanding issues
> and include extensions for the new wording for REQ-017 and REQ-018.
> >
> > https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
> >
> > Regards,
> > Henry
> >
> > -----Original Message-----
> > From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> > Sent: Tuesday, March 01, 2011 12:09 PM
> > To: Henry Lum
> > Cc: leon.portman@nice.com; alan.b.johnston@gmail.com;
> andrew.hutton@siemens-enterprise.com
> > Subject: New Version Notification for draft-portman-siprec-protocol-
> 03
> >
> >
> > A new version of I-D, draft-portman-siprec-protocol-03.txt has been
> successfully submitted by Henry Lum and posted to the IETF repository.
> >
> > Filename:	 draft-portman-siprec-protocol
> > Revision:	 03
> > Title:		 The SIP-based Media Recording Protocol (SIPREC)
> > Creation_date:	 2011-03-01
> > WG ID:		 Independent Submission
> > Number_of_pages: 20
> >
> > Abstract:
> > SIPREC Session Recording Protocol is used for establishing recording
> > session and reporting of the metadata of the communication session.
> >
> > This document specifies the SIPREC Protocol (SIPREC).  SIPREC is
used
> > between Session Recording Client (SRC) and Session Recording Server
> > (SRS).
> >
> >
> >
> > The IETF Secretariat.
> >
> >
> >
> >
> >
---------------------------------------------------------------------
> ----------------------------------------------
> > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> contain confidential and proprietary information of Alcatel-Lucent
> and/or its affiliated entities. Access by the intended recipient only
> is authorized. Any liability arising from any party acting, or
> refraining from acting, on any information contained in this e-mail is
> hereby excluded. If you are not the intended recipient, please notify
> the sender immediately, destroy the original transmission and its
> attachments and do not disclose the contents to any other person, use
> it for any purpose, or store or copy the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
> and/or its affiliated entities.
> >
> > _______________________________________________
> > 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

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From pkyzivat@cisco.com  Tue Mar  1 17:08:46 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 079913A6A30 for <siprec@core3.amsl.com>; Tue,  1 Mar 2011 17:08:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.552
X-Spam-Level: 
X-Spam-Status: No, score=-110.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TlhJiQQCMyno for <siprec@core3.amsl.com>; Tue,  1 Mar 2011 17:08:44 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 9DA233A6A21 for <siprec@ietf.org>; Tue,  1 Mar 2011 17:08:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=5757; q=dns/txt; s=iport; t=1299028189; x=1300237789; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ClglcYe+LAmXXqkpQLGJBIIDrbJOawHU8i53XD14quc=; b=GCepsGmUlgrI/5bwFKLFnDB2LFLszTpQbBXdP9wi3dPfhk4Iy4fx5SNi +hfy6aZ6m0vsxXFhdFH+CdC6reGnxaiNfEKvd4sx7W3Y+xKDpa0nUUcm6 joY2JCnbCvBLaef9YOBJrlDULqTx9Zw4WLw706Omnm5qZUz/nPK+oWRuc Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvkAAHonbU1AZnwN/2dsb2JhbACXfo5WdKIim3eFYQSFEocNg0CDFA
X-IronPort-AV: E=Sophos;i="4.62,250,1297036800"; d="scan'208";a="221687732"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 02 Mar 2011 01:09:48 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p2219m6D021455; Wed, 2 Mar 2011 01:09:48 GMT
Message-ID: <4D6D98DC.8080008@cisco.com>
Date: Tue, 01 Mar 2011 20:09:48 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Henry Lum <Henry.Lum@alcatel-lucent.com>
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com> <4D6D3FE5.9000902@cisco.com> <059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com>
In-Reply-To: <059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New Version Notificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 01:08:46 -0000

On 3/1/2011 2:32 PM, Henry Lum wrote:
> When there is an UPDATE transaction collision, you will have to make
> both SRC and SRS to wait a while before being able to send UPDATE again.
> Since SRC is normally the side initiating the SIP dialog, it is the
> owner of the Call-ID and will come second after the SRS has a chance to
> resend the UPDATE. In that case, does the SRC keep the existing UPDATE
> or send a new snapshot as requested by the SRS? The SRC also need to
> keep track of metadata changes while waiting for the timer. I worry that
> it will make the solution more complicated than just using an INFO for
> snapshot request and minimize the collision problem.

OK, collision on update is a *possibility*.
I guess the question is whether that justifies implementing an entirely 
different mechanism just for the rare error message.

I expect that the likelihood of collision is pretty slim, given that 
messages from the SRS to the SRC will be very infrequent, and if the 
message comes shortly after a metadata is received from the SRC, there 
may be little likelihood that the SRC will be sending more metadata so 
soon. And even if we don't use UPDATE for this, the SRC, like any UA, 
needs to be prepared to cope with a collision of this sort.

But I don't feel *too* strongly about this.

	Thanks,
	Paul

> Regards,
> Henry
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Paul Kyzivat
>> Sent: Tuesday, March 01, 2011 1:50 PM
>> To: siprec@ietf.org
>> Subject: Re: [siprec] FW: New Version Notificationfor draft-portman-
>> siprec-protocol-03
>>
>> Thanks Henry.
>>
>> One comment/question:
>>
>> Is there a reason to use an Info package for Requesting for metadata
>> snapshot? Since we are already defining c-d recording-session and
>> passing bodies in invite/update for it, is there a reason not to use
>> the
>> same mechanism to send error notifications/snapshop requests?
>>
>> (I'm thinking just using a different content-type for this, and of
>> course sending it from SRS to SRC.)
>>
>> Also, we could consider permitting (not requiring) this in the
>> responses
>> to the messages containing metadata.
>>
>> 	Thanks,
>> 	Paul
>>
>>
>> On 3/1/2011 12:13 PM, Henry Lum wrote:
>>> A new version has been submitted to address the outstanding issues
>> and include extensions for the new wording for REQ-017 and REQ-018.
>>>
>>> https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
>>>
>>> Regards,
>>> Henry
>>>
>>> -----Original Message-----
>>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
>>> Sent: Tuesday, March 01, 2011 12:09 PM
>>> To: Henry Lum
>>> Cc: leon.portman@nice.com; alan.b.johnston@gmail.com;
>> andrew.hutton@siemens-enterprise.com
>>> Subject: New Version Notification for draft-portman-siprec-protocol-
>> 03
>>>
>>>
>>> A new version of I-D, draft-portman-siprec-protocol-03.txt has been
>> successfully submitted by Henry Lum and posted to the IETF repository.
>>>
>>> Filename:	 draft-portman-siprec-protocol
>>> Revision:	 03
>>> Title:		 The SIP-based Media Recording Protocol (SIPREC)
>>> Creation_date:	 2011-03-01
>>> WG ID:		 Independent Submission
>>> Number_of_pages: 20
>>>
>>> Abstract:
>>> SIPREC Session Recording Protocol is used for establishing recording
>>> session and reporting of the metadata of the communication session.
>>>
>>> This document specifies the SIPREC Protocol (SIPREC).  SIPREC is
> used
>>> between Session Recording Client (SRC) and Session Recording Server
>>> (SRS).
>>>
>>>
>>>
>>> The IETF Secretariat.
>>>
>>>
>>>
>>>
>>>
> ---------------------------------------------------------------------
>> ----------------------------------------------
>>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may
>> contain confidential and proprietary information of Alcatel-Lucent
>> and/or its affiliated entities. Access by the intended recipient only
>> is authorized. Any liability arising from any party acting, or
>> refraining from acting, on any information contained in this e-mail is
>> hereby excluded. If you are not the intended recipient, please notify
>> the sender immediately, destroy the original transmission and its
>> attachments and do not disclose the contents to any other person, use
>> it for any purpose, or store or copy the information in any medium.
>> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
>> and/or its affiliated entities.
>>>
>>> _______________________________________________
>>> 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
>
> 					
> -------------------------------------------------------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.
> 					
>

From partr@cisco.com  Wed Mar  2 03:21:21 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB5D73A676A for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 03:21:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.957
X-Spam-Level: 
X-Spam-Status: No, score=-9.957 tagged_above=-999 required=5 tests=[AWL=0.642,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 98aeteLZx7lo for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 03:21:20 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 78F333A65A5 for <siprec@ietf.org>; Wed,  2 Mar 2011 03:21:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=3473; q=dns/txt; s=iport; t=1299064946; x=1300274546; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=e7BpoEtCMEXa3zIkhuwsz2C8UmWe+8G/1lCY7WAim18=; b=MeB19B8n797I2VMIlJ+dAMWrCIgPG1yh3VTl0rTmUzBBHapiL2TQ2epm U4Vyu2KshEN8MKs0sBmg9vF4Fvcft2GrvEUrpsJV+Rzsoo+SzCSP8FtHD wUjp8QWL2ONvE+KCOp8aBQEadxTU8Jqe7q3sVJkBr+tzq+d1Xnl8ILior w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8AAH22bU1AaMHG/2dsb2JhbACYAY5WdKE3m2uFYQSFFYpX
X-IronPort-AV: E=Sophos;i="4.62,252,1297036800"; d="scan'208";a="665083664"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-6.cisco.com with ESMTP; 02 Mar 2011 11:22:24 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p22BKdSX022917; Wed, 2 Mar 2011 11:22:18 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Mar 2011 16:52:14 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 2 Mar 2011 16:52:14 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904A63B12@XMB-BGL-411.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Metadata XML document error representation for whole	doc or for portion of doc
Thread-Index: AcvXW03ON+nfMVCWQ8GPwSpOJaYBQQABrURQAABGHZAAWAW2sA==
References: <A11921905DA1564D9BCF64A6430A62390293A665@XMB-BGL-411.cisco.com><4D67EC69.7080507@cisco.com><059AF07365DC474393A19A3AF187DF7406BADEA6@NAHALD.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2BAA742@MCHP058A.global-ad.net><4D6BBDAE.3020808@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE02F@NAHALD.us.int.genesyslab.com> <07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Henry Lum" <Henry.Lum@alcatel-lucent.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 02 Mar 2011 11:22:14.0298 (UTC) FILETIME=[14BBEFA0:01CBD8CC]
Cc: siprec@ietf.org
Subject: Re: [siprec] Metadata XML document error representation for whole	doc or for portion of doc
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 11:21:21 -0000

Hi all,

Thanks for your opinion and suggestion. From this mail thread, it is
clear that there is no known usecase for error indication to the portion
of the Metadata XML document but the error response *MUST* be send back
by SRS to SRC through application (SIP) mechanism. I'll update -01
version of draft-ram-siprec-metadata-format-00 based on this conclusion.


Thanks
Partha  =20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Leon Portman
Sent: Monday, February 28, 2011 9:48 PM
To: Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
Cc: siprec@ietf.org
Subject: Re: [siprec] Metadata XML document error representation
forwhole doc or for portion of doc

+1

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Henry Lum
Sent: Monday, February 28, 2011 6:13 PM
To: Paul Kyzivat; Elwell, John
Cc: siprec@ietf.org
Subject: Re: [siprec] Metadata XML document error representation for
whole doc or for portion of doc


=20
> >> We are also thinking of providing the SRS with a mechanism to=20
> >> request the SRC to ask for the current snapshot
> so
> >> that the SRC/SRS can reset the states in the case where SRS is in a

> >> really bad state. By doing so, we may be able to avoid providing
> nack
> >> responses and avoid using a chatty protocol.
> > [JRE] Yes, and the request to resend full metadata could optionally
> include some sort of error report that gave rise to the request. That=20
> error report could, for example, include the sequence number of the=20
> metadata update that was found to be in error.
>=20
> That is sort of what I had in mind about getting the two sides in
sync.
> But we will have to think more about exactly what it means.
> At best I think it will describe the *current* state of things in this

> RS, without regard to what has happened in the past.
>=20
> Even that may present some technical challenges. But we should keep=20
> this desire in mind.

[[hlum]] I agree it would be reasonable for the SRC to send the current
state as a snapshot and forget what happened previously. The subsequent
sequence numbers only refers to the current snapshot rather than the
original one, so in a way we are resetting the sequence number.

				=09
------------------------------------------------------------------------
-------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary information of Alcatel-Lucent and/or its
affiliated entities. Access by the intended recipient only is
authorized. Any liability arising from any party acting, or refraining
from acting, on any information contained in this e-mail is hereby
excluded. If you are not the intended recipient, please notify the
sender immediately, destroy the original transmission and its
attachments and do not disclose the contents to any other person, use it
for any purpose, or store or copy the information in any medium.
Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
				=09
_______________________________________________
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

From trac+siprec@trac.tools.ietf.org  Wed Mar  2 03:25:00 2011
Return-Path: <trac+siprec@trac.tools.ietf.org>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1286C3A6403 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 03:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vSIQP7yye54X for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 03:24:59 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 277E13A65A5 for <siprec@ietf.org>; Wed,  2 Mar 2011 03:24:59 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac+siprec@trac.tools.ietf.org>) id 1PukBt-0003Cj-Ck; Wed, 02 Mar 2011 03:26:01 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "siprec issue tracker" <trac+siprec@trac.tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: leon.portman@nice.com, john.elwell@siemens-enterprise.com
X-Trac-Project: siprec
Date: Wed, 02 Mar 2011 11:26:01 -0000
X-URL: http://tools.ietf.org/siprec/
X-Trac-Ticket-URL: https://wiki.tools.ietf.org/wg/siprec/trac/ticket/64#comment:1
Message-ID: <084.f734498f9edc6005628f69105fe0c1ec@trac.tools.ietf.org>
References: <075.d0db8f34c277334b137156e493ae53f5@trac.tools.ietf.org>
X-Trac-Ticket-ID: 64
In-Reply-To: <075.d0db8f34c277334b137156e493ae53f5@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: leon.portman@nice.com, john.elwell@siemens-enterprise.com, siprec@ietf.org
X-SA-Exim-Mail-From: trac+siprec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
X-Mailman-Approved-At: Wed, 02 Mar 2011 03:29:30 -0800
Cc: siprec@ietf.org
Subject: Re: [siprec] #64: REQ-015/REQ-016 and cancelling a recording
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 11:25:00 -0000

#64: REQ-015/REQ-016 and cancelling a recording

Changes (by john.elwell@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 There have been no objections to deleting REQ-015 and REQ-016 and adding a
 new requirement:
 "REQ-xxx The mechanism MUST support a means to stop the recording". The
 editor should go ahead and make this change to the working draft.

 John (as chair)

-- 
------------------------------------------------+---------------------------
 Reporter:  john.elwell@…                       |        Owner:  leon.portman@…       
     Type:  defect                              |       Status:  closed               
 Priority:  major                               |    Milestone:                       
Component:  Requirements                        |      Version:                       
 Severity:  In WG Last Call                     |   Resolution:  fixed                
 Keywords:                                      |  
------------------------------------------------+---------------------------

Ticket URL: <https://wiki.tools.ietf.org/wg/siprec/trac/ticket/64#comment:1>
siprec <http://tools.ietf.org/siprec/>


From trac+siprec@trac.tools.ietf.org  Wed Mar  2 03:32:03 2011
Return-Path: <trac+siprec@trac.tools.ietf.org>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F5D23A67A7 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 03:32:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LvR5U3N+cFeH for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 03:32:02 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id B5F733A6C26 for <siprec@ietf.org>; Wed,  2 Mar 2011 03:32:02 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac+siprec@trac.tools.ietf.org>) id 1PukIl-00081J-9t; Wed, 02 Mar 2011 03:33:07 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "siprec issue tracker" <trac+siprec@trac.tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: krehor@cisco.com, john.elwell@siemens-enterprise.com
X-Trac-Project: siprec
Date: Wed, 02 Mar 2011 11:33:07 -0000
X-URL: http://tools.ietf.org/siprec/
X-Trac-Ticket-URL: https://wiki.tools.ietf.org/wg/siprec/trac/ticket/65#comment:1
Message-ID: <084.523d179944ba60574120a60c3bdb48f3@trac.tools.ietf.org>
References: <075.bbb33f46ac9ce9e91b16799102ac4fb6@trac.tools.ietf.org>
X-Trac-Ticket-ID: 65
In-Reply-To: <075.bbb33f46ac9ce9e91b16799102ac4fb6@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: krehor@cisco.com, john.elwell@siemens-enterprise.com, siprec@ietf.org
X-SA-Exim-Mail-From: trac+siprec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: siprec@ietf.org
Subject: Re: [siprec] #65: Extension of REQ-017 concerning preference to record/not record
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 11:32:03 -0000

#65: Extension of REQ-017 concerning preference to record/not record

Changes (by john.elwell@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 A have seen no objections to the proposal to replace REQ-017 with the
 following two new requirements:
 "REQ-yyy The mechanism MUST support a means for a recording-aware UA
 involved in a CS to request at session establishment time that the CS
 should be recorded or should not be recorded, the honoring of such a
 request being dependent on policy."
 "REQ-zzz The mechanism MUST support a means for a recording-aware UA
 involved in a CS to request during a session that the recording of the CS
 should be started, paused, resumed or stopped, the honoring of such a
 request being dependent on policy."
 The editor should go ahead and make this change to the working draft.

 John (as chair)

-- 
------------------------------------------------+---------------------------
 Reporter:  john.elwell@…                       |        Owner:  krehor@…        
     Type:  defect                              |       Status:  closed          
 Priority:  major                               |    Milestone:                  
Component:  Requirements                        |      Version:                  
 Severity:  In WG Last Call                     |   Resolution:  fixed           
 Keywords:                                      |  
------------------------------------------------+---------------------------

Ticket URL: <https://wiki.tools.ietf.org/wg/siprec/trac/ticket/65#comment:1>
siprec <http://tools.ietf.org/siprec/>


From john.elwell@siemens-enterprise.com  Wed Mar  2 03:40:14 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A76D13A6B63 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 03:40:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.62
X-Spam-Level: 
X-Spam-Status: No, score=-102.62 tagged_above=-999 required=5 tests=[AWL=-0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2quVQHxCJCPm for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 03:40:13 -0800 (PST)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 325063A679F for <siprec@ietf.org>; Wed,  2 Mar 2011 03:40:12 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3600987; Wed, 2 Mar 2011 12:41:17 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id D327B1EB82AB; Wed,  2 Mar 2011 12:41:17 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 2 Mar 2011 12:41:17 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, siprec issue tracker <trac@tools.ietf.org>
Date: Wed, 2 Mar 2011 12:41:16 +0100
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
Thread-Index: AcvM6cpYQ57UUrunTBCS241IKWnf7AGlK6VwAAa0NbAA8LDpEAABtcZQAFregeA=
Message-ID: <A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org> <07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com>
Keywords: SIPREC
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 11:40:14 -0000

In the interests of getting the requirements document finished, I will set =
a short deadline for this remaining issue. If I have not heard any objectio=
ns to the proposal below by 2011-03-07 I will ask the editor to adopt this =
new text and publish -07.

John (as chair)

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 28 February 2011 16:17
> To: Elwell, John; siprec issue tracker
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018 on indications to participants
>=20
> +1
>=20
> Leon
>=20
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
> Sent: Monday, February 28, 2011 5:35 PM
> To: Leon Portman; siprec issue tracker
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018 on indications to participants
>=20
> There has been little discussion on this, apart from support=20
> from Leon. The existing text says:
> "REQ-018 The mechanism MUST provide a means of indicating to the
>    participants involved in a CS that their session is being recorded.
>=20
>    Examples include: inject tones into the CS from the SRC, play a
>    message at the beginning of a session, a visual indicator on a
>    display, etc."
>=20
> I would suggest the following text:
> "REQ-018 The mechanism MUST provide a means of indicating to=20
> the participants involved in a CS that their session is being=20
> recorded. Although this can be accomplished using existing=20
> SIP techniques for playing an in-band tone, announcement or=20
> other media to participants, the mechanism is required also=20
> to provide an indication to recording-aware UAs for=20
> appropriate rendering at the user interface."
>=20
> John (as individual)=20
>=20
> > -----Original Message-----
> > From: Elwell, John
> > Sent: 23 February 2011 20:36
> > To: 'Leon Portman'; siprec issue tracker
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018=20
> > on indications to participants
> >=20
> > My feeling too.
> >=20
> > John (as individual)
> >=20
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 23 February 2011 17:25
> > > To: siprec issue tracker; Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
> > > REQ-018 on indications to participants
> > >=20
> > > Because supporting of siprec-aware UA indication will=20
> require some=20
> > > additional protocol changes for CS, we probably should have a=20
> > > separate requirement for that
> > >=20
> > > Leon
> > >=20
> > > -----Original Message-----
> > > From: siprec issue tracker [mailto:trac@tools.ietf.org]
> > > Sent: Tuesday, February 15, 2011 10:24 AM
> > > To: Leon Portman; john.elwell@siemens-enterprise.com
> > > Cc: siprec@ietf.org
> > > Subject: [siprec] Requirements #66 (new): Clarification of
> > > REQ-018 on indications to participants
> > >=20
> > > #66: Clarification of REQ-018 on indications to participants
> > >=20
> > >  REQ-018 can be satisfied in general by playing media to=20
> > > participants, but  do we need a more specific=20
> requirement, e.g., for=20
> > > siprec-aware UAs to know  whether the CS is being recorded or not?
> > >=20
> > >  John
> > >=20
> > > --
> > > ------------------------------------------------+-------------
> > > ----------
> > > ------------------------------------------------+----
> > >  Reporter:  john.elwell@...                       |      =20
> > > Owner:  leon.portman@...      =20
> > >      Type:  defect                              |     =20
> > > Status:  new                 =20
> > >  Priority:  major                               |  =20
> > > Milestone:                      =20
> > > Component:  Requirements                        |    =20
> > > Version:                      =20
> > >  Severity:  In WG Last Call                     |   =20
> > > Keywords:                      =20
> > > ------------------------------------------------+-------------
> > > ----------
> > > ------------------------------------------------+----
> > >=20
> > > Ticket URL: <https://trac.tools.ietf.org/wg/siprec/trac/ticket/66>
> > > siprec <http://tools.ietf.org/siprec/>
> > >=20
> > >=20
> =

From partr@cisco.com  Wed Mar  2 05:46:31 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAD383A6802 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 05:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.038
X-Spam-Level: 
X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[AWL=0.561, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id muIFyM8fxAxY for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 05:46:30 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 9AAE93A67B7 for <siprec@ietf.org>; Wed,  2 Mar 2011 05:46:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=5513; q=dns/txt; s=iport; t=1299073656; x=1300283256; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=LJeKJ+Xd3Unxy3jYvpNsFKXLh8moV119VOOsbGHlIf4=; b=SlK8ocIVK7oTN0KOnA0Q14WWszBPLnA5y4hKN0+/GhFaIEa2ZuPys2xf HlBy4IK99q6MH6Je8Kt/VkVrIJX4dTNAlZoWdb3seRtYKocPq52PgWKch TsK5iHyVF68qCahzlnJXMWqSeCW2Yt5EFwzBXgW8fn3uRo4PyEQsQhtBV w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8AAF/ZbU1AaMHG/2dsb2JhbACYAY5WdKFym3eFYQSFFYpX
X-IronPort-AV: E=Sophos;i="4.62,253,1297036800"; d="scan'208";a="411672398"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-1.cisco.com with ESMTP; 02 Mar 2011 13:47:35 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p22DlXaS016378; Wed, 2 Mar 2011 13:47:34 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Mar 2011 19:17:33 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 2 Mar 2011 19:17:33 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904A63B8A@XMB-BGL-411.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Synchronous vs Asynchronous Error handling
Thread-Index: AcvXW03ON+nfMVCWQ8GPwSpOJaYBQQABrURQAABGHZAAXlVssA==
References: <A11921905DA1564D9BCF64A6430A62390293A665@XMB-BGL-411.cisco.com><4D67EC69.7080507@cisco.com><059AF07365DC474393A19A3AF187DF7406BADEA6@NAHALD.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2BAA742@MCHP058A.global-ad.net><4D6BBDAE.3020808@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE02F@NAHALD.us.int.genesyslab.com> <07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Henry Lum" <Henry.Lum@alcatel-lucent.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 02 Mar 2011 13:47:33.0727 (UTC) FILETIME=[61EB36F0:01CBD8E0]
Cc: siprec@ietf.org
Subject: [siprec] Synchronous vs Asynchronous Error handling
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 13:46:31 -0000

Hi all,=20

Another issue discussed as part of the below mail thread is whether
metadata (XML+SDP) error has to be responded synchronously (SIP
Request/[SIP provisional response]/SIP Response) or asynchronously(SIP
Request/SIP Response/SIP Error request/SIP Error response).

Synchronous Error handling:
>From SRC perspective, synchronous error handling is simple to implement
as there is no extra context or state to be maintained about the earlier
SIP transactions.=20

In SRS, SDP Metadata portion *MUST* be processed in synchronously to
meet offer/answer model requirement. Now the question is whether XML
takes so much of a time wherein the error MUST be handled asynchronous?
The simple SRS will be able to send provisional response and respond
back final response once the complete XML check is done. My reasoning is
so because B2BUA normally handles INVITE/RE-INVITE in a way that send
(100 trying) provisional response to the incoming dialog side, send
INVITE/RE-INVITE to the outgoing dialog side which may take upto 32 sec
delay to respond and forwards 200 OK to incoming dialog side once it is
received from outgoing dialog side and it is well working deployed
model. Please let me know in which situation this mechanism has issues
specific to SIPREC & XML.

Asynchronous Error handling:
Here as well in SRS, SDP Metadata portion *MUST* be processed in
synchronously to meet offer/answer model requirement.=20
 =20
Two cases exists from SRC perspective.
1) In case the sequence number has to be maintained by SRC for
asynchronous error handling, then it *MAY* require SRC to maintain the
earlier transaction which is overkill as SRC will not keep track or
record its previous state.=20

2) In most of the scenario, it is not possible to re-record but it is
only possible to re-sync. In case the motivation of asynchronous error
is to re-sync metadata by SRS to SRC, it is very similar to SRS
requesting for current complete metadata (SDP+XML) from SRC. On
receiving re-sync request, SRC has to trigger the complete metadata
towards SRS. The sequence number from SRS *MAY* be used for logging
purpose if required.=20

Please let me know which one of the above asynchronous behavior is
expected from SRC. Also, instead of asynchronous error message, do you
wish to create re-sync request mechanism from SRS which may be used for
error or other purpose as well.

Thanks
Partha

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Leon Portman
Sent: Monday, February 28, 2011 9:48 PM
To: Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
Cc: siprec@ietf.org
Subject: Re: [siprec] Metadata XML document error representation
forwhole doc or for portion of doc

+1

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Henry Lum
Sent: Monday, February 28, 2011 6:13 PM
To: Paul Kyzivat; Elwell, John
Cc: siprec@ietf.org
Subject: Re: [siprec] Metadata XML document error representation for
whole doc or for portion of doc


=20
> >> We are also thinking of providing the SRS with a mechanism to=20
> >> request the SRC to ask for the current snapshot
> so
> >> that the SRC/SRS can reset the states in the case where SRS is in a

> >> really bad state. By doing so, we may be able to avoid providing
> nack
> >> responses and avoid using a chatty protocol.
> > [JRE] Yes, and the request to resend full metadata could optionally
> include some sort of error report that gave rise to the request. That=20
> error report could, for example, include the sequence number of the=20
> metadata update that was found to be in error.
>=20
> That is sort of what I had in mind about getting the two sides in
sync.
> But we will have to think more about exactly what it means.
> At best I think it will describe the *current* state of things in this

> RS, without regard to what has happened in the past.
>=20
> Even that may present some technical challenges. But we should keep=20
> this desire in mind.

[[hlum]] I agree it would be reasonable for the SRC to send the current
state as a snapshot and forget what happened previously. The subsequent
sequence numbers only refers to the current snapshot rather than the
original one, so in a way we are resetting the sequence number.

				=09
------------------------------------------------------------------------
-------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary information of Alcatel-Lucent and/or its
affiliated entities. Access by the intended recipient only is
authorized. Any liability arising from any party acting, or refraining
from acting, on any information contained in this e-mail is hereby
excluded. If you are not the intended recipient, please notify the
sender immediately, destroy the original transmission and its
attachments and do not disclose the contents to any other person, use it
for any purpose, or store or copy the information in any medium.
Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
				=09
_______________________________________________
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

From Henry.Lum@alcatel-lucent.com  Wed Mar  2 08:43:43 2011
Return-Path: <Henry.Lum@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32A383A681E for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 08:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MP6vY811Avmm for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 08:43:41 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 7F6B23A67A5 for <siprec@ietf.org>; Wed,  2 Mar 2011 08:43:40 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p22Gifr3022821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Mar 2011 10:44:41 -0600 (CST)
Received: from relay-out1.dc.genesyslab.com (relay-out1.dc.genesyslab.com [172.22.68.187]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p22GidUa024211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Mar 2011 10:44:41 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.dc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id p22GidpO023878; Wed, 2 Mar 2011 08:44:39 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.93]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Mar 2011 08:44:39 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 2 Mar 2011 08:44:38 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7406BAE5C6@NAHALD.us.int.genesyslab.com>
In-Reply-To: <4D6D98DC.8080008@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New Version Notificationfor	draft-portman-siprec-protocol-03
Thread-Index: AcvYdoq1VttmMUOCSj+I/EBWiH/OmQAgjaaA
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com> <4D6D3FE5.9000902@cisco.com> <059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com> <4D6D98DC.8080008@cisco.com>
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 02 Mar 2011 16:44:39.0146 (UTC) FILETIME=[1F297CA0:01CBD8F9]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New Version Notificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 16:43:43 -0000

I don't feel strongly too about using INFO so I am open to using UPDATE
if the group feels that it is okay for SRC/SRS to deal with the
consequences of UPDATE collision.

Henry

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Tuesday, March 01, 2011 8:10 PM
> To: Henry Lum
> Cc: siprec@ietf.org
> Subject: Re: [siprec] FW: New Version Notificationfor draft-portman-
> siprec-protocol-03
>=20
>=20
>=20
> On 3/1/2011 2:32 PM, Henry Lum wrote:
> > When there is an UPDATE transaction collision, you will have to make
> > both SRC and SRS to wait a while before being able to send UPDATE
> again.
> > Since SRC is normally the side initiating the SIP dialog, it is the
> > owner of the Call-ID and will come second after the SRS has a chance
> to
> > resend the UPDATE. In that case, does the SRC keep the existing
> UPDATE
> > or send a new snapshot as requested by the SRS? The SRC also need to
> > keep track of metadata changes while waiting for the timer. I worry
> that
> > it will make the solution more complicated than just using an INFO
> for
> > snapshot request and minimize the collision problem.
>=20
> OK, collision on update is a *possibility*.
> I guess the question is whether that justifies implementing an
entirely
> different mechanism just for the rare error message.
>=20
> I expect that the likelihood of collision is pretty slim, given that
> messages from the SRS to the SRC will be very infrequent, and if the
> message comes shortly after a metadata is received from the SRC, there
> may be little likelihood that the SRC will be sending more metadata so
> soon. And even if we don't use UPDATE for this, the SRC, like any UA,
> needs to be prepared to cope with a collision of this sort.
>=20
> But I don't feel *too* strongly about this.
>=20
> 	Thanks,
> 	Paul
>=20
> > Regards,
> > Henry
> >
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> >> Behalf Of Paul Kyzivat
> >> Sent: Tuesday, March 01, 2011 1:50 PM
> >> To: siprec@ietf.org
> >> Subject: Re: [siprec] FW: New Version Notificationfor
draft-portman-
> >> siprec-protocol-03
> >>
> >> Thanks Henry.
> >>
> >> One comment/question:
> >>
> >> Is there a reason to use an Info package for Requesting for
metadata
> >> snapshot? Since we are already defining c-d recording-session and
> >> passing bodies in invite/update for it, is there a reason not to
use
> >> the
> >> same mechanism to send error notifications/snapshop requests?
> >>
> >> (I'm thinking just using a different content-type for this, and of
> >> course sending it from SRS to SRC.)
> >>
> >> Also, we could consider permitting (not requiring) this in the
> >> responses
> >> to the messages containing metadata.
> >>
> >> 	Thanks,
> >> 	Paul
> >>
> >>
> >> On 3/1/2011 12:13 PM, Henry Lum wrote:
> >>> A new version has been submitted to address the outstanding issues
> >> and include extensions for the new wording for REQ-017 and REQ-018.
> >>>
> >>> https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
> >>>
> >>> Regards,
> >>> Henry
> >>>
> >>> -----Original Message-----
> >>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> >>> Sent: Tuesday, March 01, 2011 12:09 PM
> >>> To: Henry Lum
> >>> Cc: leon.portman@nice.com; alan.b.johnston@gmail.com;
> >> andrew.hutton@siemens-enterprise.com
> >>> Subject: New Version Notification for draft-portman-siprec-
> protocol-
> >> 03
> >>>
> >>>
> >>> A new version of I-D, draft-portman-siprec-protocol-03.txt has
been
> >> successfully submitted by Henry Lum and posted to the IETF
> repository.
> >>>
> >>> Filename:	 draft-portman-siprec-protocol
> >>> Revision:	 03
> >>> Title:		 The SIP-based Media Recording Protocol (SIPREC)
> >>> Creation_date:	 2011-03-01
> >>> WG ID:		 Independent Submission
> >>> Number_of_pages: 20
> >>>
> >>> Abstract:
> >>> SIPREC Session Recording Protocol is used for establishing
> recording
> >>> session and reporting of the metadata of the communication
session.
> >>>
> >>> This document specifies the SIPREC Protocol (SIPREC).  SIPREC is
> > used
> >>> between Session Recording Client (SRC) and Session Recording
Server
> >>> (SRS).
> >>>
> >>>
> >>>
> >>> The IETF Secretariat.
> >>>
> >>>
> >>>
> >>>
> >>>
> >
---------------------------------------------------------------------
> >> ----------------------------------------------
> >>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> >> contain confidential and proprietary information of Alcatel-Lucent
> >> and/or its affiliated entities. Access by the intended recipient
> only
> >> is authorized. Any liability arising from any party acting, or
> >> refraining from acting, on any information contained in this e-mail
> is
> >> hereby excluded. If you are not the intended recipient, please
> notify
> >> the sender immediately, destroy the original transmission and its
> >> attachments and do not disclose the contents to any other person,
> use
> >> it for any purpose, or store or copy the information in any medium.
> >> Copyright in this e-mail and any attachments belongs to Alcatel-
> Lucent
> >> and/or its affiliated entities.
> >>>
> >>> _______________________________________________
> >>> 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
> >
> >
> >
---------------------------------------------------------------------
> ----------------------------------------------
> > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> contain confidential and proprietary information of Alcatel-Lucent
> and/or its affiliated entities. Access by the intended recipient only
> is authorized. Any liability arising from any party acting, or
> refraining from acting, on any information contained in this e-mail is
> hereby excluded. If you are not the intended recipient, please notify
> the sender immediately, destroy the original transmission and its
> attachments and do not disclose the contents to any other person, use
> it for any purpose, or store or copy the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
> and/or its affiliated entities.
> >
> >

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From john.elwell@siemens-enterprise.com  Wed Mar  2 08:54:43 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7650F3A67B8 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 08:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.619
X-Spam-Level: 
X-Spam-Status: No, score=-102.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CsBOl30noVAo for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 08:54:42 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 78B7A3A67B3 for <siprec@ietf.org>; Wed,  2 Mar 2011 08:54:42 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3597855 for siprec@ietf.org; Wed, 2 Mar 2011 17:55:47 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 3CD501EB82B4 for <siprec@ietf.org>; Wed,  2 Mar 2011 17:55:47 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 2 Mar 2011 17:55:47 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Wed, 2 Mar 2011 17:55:45 +0100
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qA==
Message-ID: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 16:54:43 -0000

draft-ietf-siprec-architecture has not moved forward much in recent months,=
 waiting for progress on solutions to help confirm the architecture. Now wo=
uld be an excellent time for people to raise any issues that can perhaps be=
 addressed by the editor before the cut-off (2011-03-14) or discussed in Pr=
ague.

John
 =

From Dave.d.Smith@alcatel-lucent.com  Wed Mar  2 11:56:09 2011
Return-Path: <Dave.d.Smith@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36DEA3A687E for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 11:56:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dvT3mFmV12oC for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 11:56:08 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 14C2B3A686D for <siprec@ietf.org>; Wed,  2 Mar 2011 11:56:08 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p22JvCmG022639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Mar 2011 13:57:14 -0600 (CST)
Received: from relay-out1.dc.genesyslab.com (relay-out1.dc.genesyslab.com [172.22.68.187]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p22Jv9ng029816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Mar 2011 13:57:11 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.dc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id p22Jv62t023587; Wed, 2 Mar 2011 11:57:07 -0800 (PST)
Received: from SARUMAN.us.int.genesyslab.com ([192.168.20.90]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Mar 2011 11:57:06 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 2 Mar 2011 11:57:06 -0800
Message-ID: <CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
Thread-Index: AcvM6cpYQ57UUrunTBCS241IKWnf7AGlK6VwAAa0NbAA8LDpEAABtcZQAFregeAADuqSkA==
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net>
From: "Dave Smith" <Dave.d.Smith@alcatel-lucent.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Leon Portman" <Leon.Portman@nice.com>, "siprec issue tracker" <trac@tools.ietf.org>
X-OriginalArrivalTime: 02 Mar 2011 19:57:06.0744 (UTC) FILETIME=[02111B80:01CBD914]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 19:56:09 -0000

I do have an input to this requirement. =20

I agree that the system should be able to provide an indication to
recording-aware UAs that recording is currently occurring (for
appropriate rendering at the user interface). =20
I also believe that the system should be able to provide a "tone" to CS
participants to indicate that recording is currently occurring
(specifically, a distinct "beep tone" signal that is repeated at regular
intervals during the course of the telephone conversation when the
recording device is in use); note that this is consistent with existing
methods from FCC Rules Regarding Telephone Company Recording of
Interstate or International Wireline Telephone Conversations. =20
But I do not see a reason to mention "announcements", or "other media"
in this requirement. =20
=20
Therefore, I recommend the following wording for REQ-018:  =20

"REQ-018 The mechanism MUST provide a means of indicating to the
participants involved in a CS that their session is being recorded.  To
support this the mechanism MUST provide a means of playing a repeatable
tone to CS participants, and also the mechanism MUST provide a means to
indicate to recording-aware UAs that recording is currently occurring
(for appropriate rendering at the user interface)."

Regards,
Dave

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Elwell, John
Sent: Wednesday, March 02, 2011 3:41 AM
To: Leon Portman; siprec issue tracker
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018
on indications to participants

In the interests of getting the requirements document finished, I will
set a short deadline for this remaining issue. If I have not heard any
objections to the proposal below by 2011-03-07 I will ask the editor to
adopt this new text and publish -07.

John (as chair)

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 28 February 2011 16:17
> To: Elwell, John; siprec issue tracker
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018 on indications to participants
>=20
> +1
>=20
> Leon
>=20
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
> Sent: Monday, February 28, 2011 5:35 PM
> To: Leon Portman; siprec issue tracker
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018 on indications to participants
>=20
> There has been little discussion on this, apart from support=20
> from Leon. The existing text says:
> "REQ-018 The mechanism MUST provide a means of indicating to the
>    participants involved in a CS that their session is being recorded.
>=20
>    Examples include: inject tones into the CS from the SRC, play a
>    message at the beginning of a session, a visual indicator on a
>    display, etc."
>=20
> I would suggest the following text:
> "REQ-018 The mechanism MUST provide a means of indicating to=20
> the participants involved in a CS that their session is being=20
> recorded. Although this can be accomplished using existing=20
> SIP techniques for playing an in-band tone, announcement or=20
> other media to participants, the mechanism is required also=20
> to provide an indication to recording-aware UAs for=20
> appropriate rendering at the user interface."
>=20
> John (as individual)=20
>=20
> > -----Original Message-----
> > From: Elwell, John
> > Sent: 23 February 2011 20:36
> > To: 'Leon Portman'; siprec issue tracker
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018=20
> > on indications to participants
> >=20
> > My feeling too.
> >=20
> > John (as individual)
> >=20
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 23 February 2011 17:25
> > > To: siprec issue tracker; Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
> > > REQ-018 on indications to participants
> > >=20
> > > Because supporting of siprec-aware UA indication will=20
> require some=20
> > > additional protocol changes for CS, we probably should have a=20
> > > separate requirement for that
> > >=20
> > > Leon
> > >=20
> > > -----Original Message-----
> > > From: siprec issue tracker [mailto:trac@tools.ietf.org]
> > > Sent: Tuesday, February 15, 2011 10:24 AM
> > > To: Leon Portman; john.elwell@siemens-enterprise.com
> > > Cc: siprec@ietf.org
> > > Subject: [siprec] Requirements #66 (new): Clarification of
> > > REQ-018 on indications to participants
> > >=20
> > > #66: Clarification of REQ-018 on indications to participants
> > >=20
> > >  REQ-018 can be satisfied in general by playing media to=20
> > > participants, but  do we need a more specific=20
> requirement, e.g., for=20
> > > siprec-aware UAs to know  whether the CS is being recorded or not?
> > >=20
> > >  John
> > >=20
> > > --
> > > ------------------------------------------------+-------------
> > > ----------
> > > ------------------------------------------------+----
> > >  Reporter:  john.elwell@...                       |      =20
> > > Owner:  leon.portman@...      =20
> > >      Type:  defect                              |     =20
> > > Status:  new                 =20
> > >  Priority:  major                               |  =20
> > > Milestone:                      =20
> > > Component:  Requirements                        |    =20
> > > Version:                      =20
> > >  Severity:  In WG Last Call                     |   =20
> > > Keywords:                      =20
> > > ------------------------------------------------+-------------
> > > ----------
> > > ------------------------------------------------+----
> > >=20
> > > Ticket URL: <https://trac.tools.ietf.org/wg/siprec/trac/ticket/66>
> > > siprec <http://tools.ietf.org/siprec/>
> > >=20
> > >=20
>=20
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From pkyzivat@cisco.com  Wed Mar  2 13:41:32 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2325A3A68C7 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 13:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.555
X-Spam-Level: 
X-Spam-Status: No, score=-110.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5OMnyPOk+57a for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 13:41:30 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 023AD3A68C6 for <siprec@ietf.org>; Wed,  2 Mar 2011 13:41:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=7688; q=dns/txt; s=iport; t=1299102157; x=1300311757; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=YQ/oG2urMReX9wDl5VEljilDRCls8PcnHQF49N0hHbk=; b=gl/hDTfFCR2eeMrGapGmiglvu2vzSdvXYx3FDEpU0873Y6s9qNQqBtJ+ ceRiDH0Fs7WR2fv4pWCO/EtQ52aG2CeiNIqYocWhTmnNYlg36XVrS8R6D OAeAPj35tYD2RC/Jg95K/4saVW5axkFQPzvPsH3H46FsQrMjvARcGOdcN I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAAO5Ibk1AZnwM/2dsb2JhbACYGI5YdKJ4nASFYQSFF4cPg0A
X-IronPort-AV: E=Sophos;i="4.62,255,1297036800"; d="scan'208";a="222032445"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 02 Mar 2011 21:42:31 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p22LgUMH004333 for <siprec@ietf.org>; Wed, 2 Mar 2011 21:42:30 GMT
Message-ID: <4D6EB9C6.6080505@cisco.com>
Date: Wed, 02 Mar 2011 16:42:30 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: siprec@ietf.org
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com>	<A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net> <CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com>
In-Reply-To: <CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 21:41:32 -0000

Dave,

I recognize that there are environments where this audible tone is a 
requirement. And also environments where it is not, or that there is 
some *other* requirement.

My question is whether rendering such things is "part of the mechanism", 
or simply something that some SRCs must be able to do.

Making this part of the mechanism begs the question of "what mechanism". 
There are mechanisms for capturing the media for recording that do not 
have a device in place that can insert something into the media. Making 
this a requirement on the mechanism would exclude using those techniques.

	Thanks,
	Paul

On 3/2/2011 2:57 PM, Dave Smith wrote:
> I do have an input to this requirement.
>
> I agree that the system should be able to provide an indication to
> recording-aware UAs that recording is currently occurring (for
> appropriate rendering at the user interface).
> I also believe that the system should be able to provide a "tone" to CS
> participants to indicate that recording is currently occurring
> (specifically, a distinct "beep tone" signal that is repeated at regular
> intervals during the course of the telephone conversation when the
> recording device is in use); note that this is consistent with existing
> methods from FCC Rules Regarding Telephone Company Recording of
> Interstate or International Wireline Telephone Conversations.
> But I do not see a reason to mention "announcements", or "other media"
> in this requirement.
>
> Therefore, I recommend the following wording for REQ-018:
>
> "REQ-018 The mechanism MUST provide a means of indicating to the
> participants involved in a CS that their session is being recorded.  To
> support this the mechanism MUST provide a means of playing a repeatable
> tone to CS participants, and also the mechanism MUST provide a means to
> indicate to recording-aware UAs that recording is currently occurring
> (for appropriate rendering at the user interface)."
>
> Regards,
> Dave
>
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
> Of Elwell, John
> Sent: Wednesday, March 02, 2011 3:41 AM
> To: Leon Portman; siprec issue tracker
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018
> on indications to participants
>
> In the interests of getting the requirements document finished, I will
> set a short deadline for this remaining issue. If I have not heard any
> objections to the proposal below by 2011-03-07 I will ask the editor to
> adopt this new text and publish -07.
>
> John (as chair)
>
>> -----Original Message-----
>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>> Sent: 28 February 2011 16:17
>> To: Elwell, John; siprec issue tracker
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>> of REQ-018 on indications to participants
>>
>> +1
>>
>> Leon
>>
>> -----Original Message-----
>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>> Sent: Monday, February 28, 2011 5:35 PM
>> To: Leon Portman; siprec issue tracker
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>> of REQ-018 on indications to participants
>>
>> There has been little discussion on this, apart from support
>> from Leon. The existing text says:
>> "REQ-018 The mechanism MUST provide a means of indicating to the
>>     participants involved in a CS that their session is being recorded.
>>
>>     Examples include: inject tones into the CS from the SRC, play a
>>     message at the beginning of a session, a visual indicator on a
>>     display, etc."
>>
>> I would suggest the following text:
>> "REQ-018 The mechanism MUST provide a means of indicating to
>> the participants involved in a CS that their session is being
>> recorded. Although this can be accomplished using existing
>> SIP techniques for playing an in-band tone, announcement or
>> other media to participants, the mechanism is required also
>> to provide an indication to recording-aware UAs for
>> appropriate rendering at the user interface."
>>
>> John (as individual)
>>
>>> -----Original Message-----
>>> From: Elwell, John
>>> Sent: 23 February 2011 20:36
>>> To: 'Leon Portman'; siprec issue tracker
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>> of REQ-018
>>> on indications to participants
>>>
>>> My feeling too.
>>>
>>> John (as individual)
>>>
>>>> -----Original Message-----
>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>> Sent: 23 February 2011 17:25
>>>> To: siprec issue tracker; Elwell, John
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
>>>> REQ-018 on indications to participants
>>>>
>>>> Because supporting of siprec-aware UA indication will
>> require some
>>>> additional protocol changes for CS, we probably should have a
>>>> separate requirement for that
>>>>
>>>> Leon
>>>>
>>>> -----Original Message-----
>>>> From: siprec issue tracker [mailto:trac@tools.ietf.org]
>>>> Sent: Tuesday, February 15, 2011 10:24 AM
>>>> To: Leon Portman; john.elwell@siemens-enterprise.com
>>>> Cc: siprec@ietf.org
>>>> Subject: [siprec] Requirements #66 (new): Clarification of
>>>> REQ-018 on indications to participants
>>>>
>>>> #66: Clarification of REQ-018 on indications to participants
>>>>
>>>>   REQ-018 can be satisfied in general by playing media to
>>>> participants, but  do we need a more specific
>> requirement, e.g., for
>>>> siprec-aware UAs to know  whether the CS is being recorded or not?
>>>>
>>>>   John
>>>>
>>>> --
>>>> ------------------------------------------------+-------------
>>>> ----------
>>>> ------------------------------------------------+----
>>>>   Reporter:  john.elwell@...                       |
>>>> Owner:  leon.portman@...
>>>>       Type:  defect                              |
>>>> Status:  new
>>>>   Priority:  major                               |
>>>> Milestone:
>>>> Component:  Requirements                        |
>>>> Version:
>>>>   Severity:  In WG Last Call                     |
>>>> Keywords:
>>>> ------------------------------------------------+-------------
>>>> ----------
>>>> ------------------------------------------------+----
>>>>
>>>> Ticket URL:<https://trac.tools.ietf.org/wg/siprec/trac/ticket/66>
>>>> siprec<http://tools.ietf.org/siprec/>
>>>>
>>>>
>>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>
> 					
> -------------------------------------------------------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.
> 					
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>

From Dave.d.Smith@alcatel-lucent.com  Wed Mar  2 16:49:13 2011
Return-Path: <Dave.d.Smith@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAB863A6919 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 16:49:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anBOuOZbJCb0 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 16:49:12 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 60D333A691B for <siprec@ietf.org>; Wed,  2 Mar 2011 16:49:09 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p230oEeL015988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Mar 2011 18:50:14 -0600 (CST)
Received: from relay-out2.dc (relay-out2.dc.genesyslab.com [172.22.68.188]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p230oCVK030030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Mar 2011 18:50:14 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out2.dc (8.13.8+Sun/8.13.8) with ESMTP id p230oCUW008662; Wed, 2 Mar 2011 16:50:12 -0800 (PST)
Received: from SARUMAN.us.int.genesyslab.com ([192.168.20.90]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Mar 2011 16:50:12 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 2 Mar 2011 16:50:10 -0800
Message-ID: <CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com>
In-Reply-To: <4D6EB9C6.6080505@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
Thread-Index: AcvZIsMupwyKe3g7RkebFBv7ajZMAwAEetuQ
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com>	<A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com> <4D6EB9C6.6080505@cisco.com>
From: "Dave Smith" <Dave.d.Smith@alcatel-lucent.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 03 Mar 2011 00:50:12.0099 (UTC) FILETIME=[F3C15530:01CBD93C]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 00:49:14 -0000

I think the solution should be able to support these functionalities:
	1.  playing a repeatable tone to CS participants
	2.  indicate to recording-aware UAs that recording is currently
occurring

Although there may be other things that could be done, I believe that
these functionalities are reasonable and sufficient, and would be
universally accepted, and that both are required in order to be able to
addresss most use cases for indicating to the participants involved in a
CS that their session is being recorded.  =20

I am not sure of what the last paragraph of your response is about
exactly.  A solution to this req't needs to be worked out in another
SIPREC Draft; my current thoughts are that since the SRC is handling and
in the path of CS UA media and is already communicating with these UAs,
probably an SRC-based solution could be more easily used to solve this
req't. =20

Regards,
Dave


-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Paul Kyzivat
Sent: Wednesday, March 02, 2011 1:43 PM
To: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018
on indications to participants

Dave,

I recognize that there are environments where this audible tone is a=20
requirement. And also environments where it is not, or that there is=20
some *other* requirement.

My question is whether rendering such things is "part of the mechanism",

or simply something that some SRCs must be able to do.

Making this part of the mechanism begs the question of "what mechanism".

There are mechanisms for capturing the media for recording that do not=20=

have a device in place that can insert something into the media. Making=20=

this a requirement on the mechanism would exclude using those
techniques.

	Thanks,
	Paul

On 3/2/2011 2:57 PM, Dave Smith wrote:
> I do have an input to this requirement.
>
> I agree that the system should be able to provide an indication to
> recording-aware UAs that recording is currently occurring (for
> appropriate rendering at the user interface).
> I also believe that the system should be able to provide a "tone" to
CS
> participants to indicate that recording is currently occurring
> (specifically, a distinct "beep tone" signal that is repeated at
regular
> intervals during the course of the telephone conversation when the
> recording device is in use); note that this is consistent with
existing
> methods from FCC Rules Regarding Telephone Company Recording of
> Interstate or International Wireline Telephone Conversations.
> But I do not see a reason to mention "announcements", or "other media"
> in this requirement.
>
> Therefore, I recommend the following wording for REQ-018:
>
> "REQ-018 The mechanism MUST provide a means of indicating to the
> participants involved in a CS that their session is being recorded.
To
> support this the mechanism MUST provide a means of playing a
repeatable
> tone to CS participants, and also the mechanism MUST provide a means
to
> indicate to recording-aware UAs that recording is currently occurring
> (for appropriate rendering at the user interface)."
>
> Regards,
> Dave
>
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf
> Of Elwell, John
> Sent: Wednesday, March 02, 2011 3:41 AM
> To: Leon Portman; siprec issue tracker
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018
> on indications to participants
>
> In the interests of getting the requirements document finished, I will
> set a short deadline for this remaining issue. If I have not heard any
> objections to the proposal below by 2011-03-07 I will ask the editor
to
> adopt this new text and publish -07.
>
> John (as chair)
>
>> -----Original Message-----
>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>> Sent: 28 February 2011 16:17
>> To: Elwell, John; siprec issue tracker
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>> of REQ-018 on indications to participants
>>
>> +1
>>
>> Leon
>>
>> -----Original Message-----
>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>> Sent: Monday, February 28, 2011 5:35 PM
>> To: Leon Portman; siprec issue tracker
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>> of REQ-018 on indications to participants
>>
>> There has been little discussion on this, apart from support
>> from Leon. The existing text says:
>> "REQ-018 The mechanism MUST provide a means of indicating to the
>>     participants involved in a CS that their session is being
recorded.
>>
>>     Examples include: inject tones into the CS from the SRC, play a
>>     message at the beginning of a session, a visual indicator on a
>>     display, etc."
>>
>> I would suggest the following text:
>> "REQ-018 The mechanism MUST provide a means of indicating to
>> the participants involved in a CS that their session is being
>> recorded. Although this can be accomplished using existing
>> SIP techniques for playing an in-band tone, announcement or
>> other media to participants, the mechanism is required also
>> to provide an indication to recording-aware UAs for
>> appropriate rendering at the user interface."
>>
>> John (as individual)
>>
>>> -----Original Message-----
>>> From: Elwell, John
>>> Sent: 23 February 2011 20:36
>>> To: 'Leon Portman'; siprec issue tracker
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>> of REQ-018
>>> on indications to participants
>>>
>>> My feeling too.
>>>
>>> John (as individual)
>>>
>>>> -----Original Message-----
>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>> Sent: 23 February 2011 17:25
>>>> To: siprec issue tracker; Elwell, John
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
>>>> REQ-018 on indications to participants
>>>>
>>>> Because supporting of siprec-aware UA indication will
>> require some
>>>> additional protocol changes for CS, we probably should have a
>>>> separate requirement for that
>>>>
>>>> Leon
>>>>
>>>> -----Original Message-----
>>>> From: siprec issue tracker [mailto:trac@tools.ietf.org]
>>>> Sent: Tuesday, February 15, 2011 10:24 AM
>>>> To: Leon Portman; john.elwell@siemens-enterprise.com
>>>> Cc: siprec@ietf.org
>>>> Subject: [siprec] Requirements #66 (new): Clarification of
>>>> REQ-018 on indications to participants
>>>>
>>>> #66: Clarification of REQ-018 on indications to participants
>>>>
>>>>   REQ-018 can be satisfied in general by playing media to
>>>> participants, but  do we need a more specific
>> requirement, e.g., for
>>>> siprec-aware UAs to know  whether the CS is being recorded or not?
>>>>
>>>>   John
>>>>
>>>> --
>>>> ------------------------------------------------+-------------
>>>> ----------
>>>> ------------------------------------------------+----
>>>>   Reporter:  john.elwell@...                       |
>>>> Owner:  leon.portman@...
>>>>       Type:  defect                              |
>>>> Status:  new
>>>>   Priority:  major                               |
>>>> Milestone:
>>>> Component:  Requirements                        |
>>>> Version:
>>>>   Severity:  In WG Last Call                     |
>>>> Keywords:
>>>> ------------------------------------------------+-------------
>>>> ----------
>>>> ------------------------------------------------+----
>>>>
>>>> Ticket URL:<https://trac.tools.ietf.org/wg/siprec/trac/ticket/66>
>>>> siprec<http://tools.ietf.org/siprec/>
>>>>
>>>>
>>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>
> 				=09
>
------------------------------------------------------------------------
-------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary information of Alcatel-Lucent and/or its
affiliated entities. Access by the intended recipient only is
authorized. Any liability arising from any party acting, or refraining
from acting, on any information contained in this e-mail is hereby
excluded. If you are not the intended recipient, please notify the
sender immediately, destroy the original transmission and its
attachments and do not disclose the contents to any other person, use it
for any purpose, or store or copy the information in any medium.
Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
> 				=09
> _______________________________________________
> 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

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From pkyzivat@cisco.com  Wed Mar  2 18:40:16 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24B1C3A6937 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 18:40:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.557
X-Spam-Level: 
X-Spam-Status: No, score=-110.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnsSas1iyPEx for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 18:40:14 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 398003A6927 for <siprec@ietf.org>; Wed,  2 Mar 2011 18:40:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=11538; q=dns/txt; s=iport; t=1299120081; x=1300329681; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=GA9InWSAv39fh8wZTB2ps4tTr64NtMx9THPyGjc3KAM=; b=gS2TILZsoOcUX0DSQXtMLr0W6VonVXEhDt/zmCnwYiXSztbs+vEUBvjp HMqvAQOIh1BcCmMFfI62STyGMyewZAJyf80/JDgh8z3HZNgTvKFe9J2tx Qaw0GLX0beHY6sqYnIC2icgC50/ipLnbPqRgj4S3lA4t+ytHjS186vm4f k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMAAE6Obk1AZnwN/2dsb2JhbACYG45YdKIsm3+FYQSFF4cPg0A
X-IronPort-AV: E=Sophos;i="4.62,256,1297036800"; d="scan'208";a="221728670"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 03 Mar 2011 02:41:20 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p232fKdX015803; Thu, 3 Mar 2011 02:41:20 GMT
Message-ID: <4D6EFFD0.7070109@cisco.com>
Date: Wed, 02 Mar 2011 21:41:20 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Dave Smith <Dave.d.Smith@alcatel-lucent.com>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com>	<A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com> <4D6EB9C6.6080505@cisco.com> <CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com>
In-Reply-To: <CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 02:40:16 -0000

On 3/2/2011 7:50 PM, Dave Smith wrote:
> I think the solution should be able to support these functionalities:
> 	1.  playing a repeatable tone to CS participants
> 	2.  indicate to recording-aware UAs that recording is currently
> occurring
>
> Although there may be other things that could be done, I believe that
> these functionalities are reasonable and sufficient, and would be
> universally accepted, and that both are required in order to be able to
> addresss most use cases for indicating to the participants involved in a
> CS that their session is being recorded.

> I am not sure of what the last paragraph of your response is about
> exactly.  A solution to this req't needs to be worked out in another
> SIPREC Draft; my current thoughts are that since the SRC is handling and
> in the path of CS UA media and is already communicating with these UAs,
> probably an SRC-based solution could be more easily used to solve this
> req't.

I'll try to elaborate:

I'm not informed of the specific legalities involved, but am of the 
impression that they vary widely. There are certainly contexts in which 
no audible indication need be played. (E.g. call centers, at least in 
some places.) In some cases this is dealt with by playing a general 
disclaimer at the beginning of the call, and/or having a contractual 
relationship by which this isn't required.

In such environments the SRC may not need any way of injecting an 
audible indication that recording is going on.

And there are ways an SRC could get the media for recording that don't 
provide a way to inject these tones. (E.g. a media *relay* may fork the 
media, but not be able to alter it.)

If you combine these things, you can end up with mechanisms for 
implementing the SRC function that are *incapable* of satisfying your 
proposed requirement, and yet are perfectly suitable for the intended 
recording task. I don't want to rule those out as valid implementations 
of siprec.

I'm fine with having the tone generation as an *option*, and one that 
may be absolutely required in *some* markets. If you have a business 
that requires this tone generation then you will buy a product that 
supports it.

	Thanks,
	Paul

> Regards,
> Dave
>
>
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
> Of Paul Kyzivat
> Sent: Wednesday, March 02, 2011 1:43 PM
> To: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018
> on indications to participants
>
> Dave,
>
> I recognize that there are environments where this audible tone is a
> requirement. And also environments where it is not, or that there is
> some *other* requirement.
>
> My question is whether rendering such things is "part of the mechanism",
>
> or simply something that some SRCs must be able to do.
>
> Making this part of the mechanism begs the question of "what mechanism".
>
> There are mechanisms for capturing the media for recording that do not
> have a device in place that can insert something into the media. Making
> this a requirement on the mechanism would exclude using those
> techniques.
>
> 	Thanks,
> 	Paul
>
> On 3/2/2011 2:57 PM, Dave Smith wrote:
>> I do have an input to this requirement.
>>
>> I agree that the system should be able to provide an indication to
>> recording-aware UAs that recording is currently occurring (for
>> appropriate rendering at the user interface).
>> I also believe that the system should be able to provide a "tone" to
> CS
>> participants to indicate that recording is currently occurring
>> (specifically, a distinct "beep tone" signal that is repeated at
> regular
>> intervals during the course of the telephone conversation when the
>> recording device is in use); note that this is consistent with
> existing
>> methods from FCC Rules Regarding Telephone Company Recording of
>> Interstate or International Wireline Telephone Conversations.
>> But I do not see a reason to mention "announcements", or "other media"
>> in this requirement.
>>
>> Therefore, I recommend the following wording for REQ-018:
>>
>> "REQ-018 The mechanism MUST provide a means of indicating to the
>> participants involved in a CS that their session is being recorded.
> To
>> support this the mechanism MUST provide a means of playing a
> repeatable
>> tone to CS participants, and also the mechanism MUST provide a means
> to
>> indicate to recording-aware UAs that recording is currently occurring
>> (for appropriate rendering at the user interface)."
>>
>> Regards,
>> Dave
>>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf
>> Of Elwell, John
>> Sent: Wednesday, March 02, 2011 3:41 AM
>> To: Leon Portman; siprec issue tracker
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018
>> on indications to participants
>>
>> In the interests of getting the requirements document finished, I will
>> set a short deadline for this remaining issue. If I have not heard any
>> objections to the proposal below by 2011-03-07 I will ask the editor
> to
>> adopt this new text and publish -07.
>>
>> John (as chair)
>>
>>> -----Original Message-----
>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>> Sent: 28 February 2011 16:17
>>> To: Elwell, John; siprec issue tracker
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>>> of REQ-018 on indications to participants
>>>
>>> +1
>>>
>>> Leon
>>>
>>> -----Original Message-----
>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>>> Sent: Monday, February 28, 2011 5:35 PM
>>> To: Leon Portman; siprec issue tracker
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>>> of REQ-018 on indications to participants
>>>
>>> There has been little discussion on this, apart from support
>>> from Leon. The existing text says:
>>> "REQ-018 The mechanism MUST provide a means of indicating to the
>>>      participants involved in a CS that their session is being
> recorded.
>>>
>>>      Examples include: inject tones into the CS from the SRC, play a
>>>      message at the beginning of a session, a visual indicator on a
>>>      display, etc."
>>>
>>> I would suggest the following text:
>>> "REQ-018 The mechanism MUST provide a means of indicating to
>>> the participants involved in a CS that their session is being
>>> recorded. Although this can be accomplished using existing
>>> SIP techniques for playing an in-band tone, announcement or
>>> other media to participants, the mechanism is required also
>>> to provide an indication to recording-aware UAs for
>>> appropriate rendering at the user interface."
>>>
>>> John (as individual)
>>>
>>>> -----Original Message-----
>>>> From: Elwell, John
>>>> Sent: 23 February 2011 20:36
>>>> To: 'Leon Portman'; siprec issue tracker
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>>> of REQ-018
>>>> on indications to participants
>>>>
>>>> My feeling too.
>>>>
>>>> John (as individual)
>>>>
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>> Sent: 23 February 2011 17:25
>>>>> To: siprec issue tracker; Elwell, John
>>>>> Cc: siprec@ietf.org
>>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
>>>>> REQ-018 on indications to participants
>>>>>
>>>>> Because supporting of siprec-aware UA indication will
>>> require some
>>>>> additional protocol changes for CS, we probably should have a
>>>>> separate requirement for that
>>>>>
>>>>> Leon
>>>>>
>>>>> -----Original Message-----
>>>>> From: siprec issue tracker [mailto:trac@tools.ietf.org]
>>>>> Sent: Tuesday, February 15, 2011 10:24 AM
>>>>> To: Leon Portman; john.elwell@siemens-enterprise.com
>>>>> Cc: siprec@ietf.org
>>>>> Subject: [siprec] Requirements #66 (new): Clarification of
>>>>> REQ-018 on indications to participants
>>>>>
>>>>> #66: Clarification of REQ-018 on indications to participants
>>>>>
>>>>>    REQ-018 can be satisfied in general by playing media to
>>>>> participants, but  do we need a more specific
>>> requirement, e.g., for
>>>>> siprec-aware UAs to know  whether the CS is being recorded or not?
>>>>>
>>>>>    John
>>>>>
>>>>> --
>>>>> ------------------------------------------------+-------------
>>>>> ----------
>>>>> ------------------------------------------------+----
>>>>>    Reporter:  john.elwell@...                       |
>>>>> Owner:  leon.portman@...
>>>>>        Type:  defect                              |
>>>>> Status:  new
>>>>>    Priority:  major                               |
>>>>> Milestone:
>>>>> Component:  Requirements                        |
>>>>> Version:
>>>>>    Severity:  In WG Last Call                     |
>>>>> Keywords:
>>>>> ------------------------------------------------+-------------
>>>>> ----------
>>>>> ------------------------------------------------+----
>>>>>
>>>>> Ticket URL:<https://trac.tools.ietf.org/wg/siprec/trac/ticket/66>
>>>>> siprec<http://tools.ietf.org/siprec/>
>>>>>
>>>>>
>>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>>
>> 					
>>
> ------------------------------------------------------------------------
> -------------------------------------------
>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
> confidential and proprietary information of Alcatel-Lucent and/or its
> affiliated entities. Access by the intended recipient only is
> authorized. Any liability arising from any party acting, or refraining
> from acting, on any information contained in this e-mail is hereby
> excluded. If you are not the intended recipient, please notify the
> sender immediately, destroy the original transmission and its
> attachments and do not disclose the contents to any other person, use it
> for any purpose, or store or copy the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
> and/or its affiliated entities.
>> 					
>> _______________________________________________
>> 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
>
> 					
> -------------------------------------------------------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.
> 					
>

From Leon.Portman@nice.com  Wed Mar  2 23:30:31 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FA813A6924 for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 23:30:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1+XP2vV33SQj for <siprec@core3.amsl.com>; Wed,  2 Mar 2011 23:30:29 -0800 (PST)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id F261D3A68EC for <siprec@ietf.org>; Wed,  2 Mar 2011 23:30:25 -0800 (PST)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Thu, 3 Mar 2011 09:31:31 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, Dave Smith <Dave.d.Smith@alcatel-lucent.com>
Date: Thu, 3 Mar 2011 09:31:30 +0200
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
Thread-Index: AcvZTH+Vs7u6urhTT2Km7kQw3BSzZAAKEM4g
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com> <4D6EB9C6.6080505@cisco.com> <CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com> <4D6EFFD0.7070109@cisco.com>
In-Reply-To: <4D6EFFD0.7070109@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 07:30:31 -0000

I agree with Paul. In the environment where SRC cannot inject any audio int=
o the CS, best practice is to have IVR or Voice Portal to make such announc=
ement.=20

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Paul Kyzivat
Sent: Thursday, March 03, 2011 4:41 AM
To: Dave Smith
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on i=
ndications to participants



On 3/2/2011 7:50 PM, Dave Smith wrote:
> I think the solution should be able to support these functionalities:
> 	1.  playing a repeatable tone to CS participants
> 	2.  indicate to recording-aware UAs that recording is currently=20
> occurring
>
> Although there may be other things that could be done, I believe that=20
> these functionalities are reasonable and sufficient, and would be=20
> universally accepted, and that both are required in order to be able=20
> to addresss most use cases for indicating to the participants involved=20
> in a CS that their session is being recorded.

> I am not sure of what the last paragraph of your response is about=20
> exactly.  A solution to this req't needs to be worked out in another=20
> SIPREC Draft; my current thoughts are that since the SRC is handling=20
> and in the path of CS UA media and is already communicating with these=20
> UAs, probably an SRC-based solution could be more easily used to solve=20
> this req't.

I'll try to elaborate:

I'm not informed of the specific legalities involved, but am of the impress=
ion that they vary widely. There are certainly contexts in which no audible=
 indication need be played. (E.g. call centers, at least in some places.) I=
n some cases this is dealt with by playing a general disclaimer at the begi=
nning of the call, and/or having a contractual relationship by which this i=
sn't required.

In such environments the SRC may not need any way of injecting an audible i=
ndication that recording is going on.

And there are ways an SRC could get the media for recording that don't prov=
ide a way to inject these tones. (E.g. a media *relay* may fork the media, =
but not be able to alter it.)

If you combine these things, you can end up with mechanisms for implementin=
g the SRC function that are *incapable* of satisfying your proposed require=
ment, and yet are perfectly suitable for the intended recording task. I don=
't want to rule those out as valid implementations of siprec.

I'm fine with having the tone generation as an *option*, and one that may b=
e absolutely required in *some* markets. If you have a business that requir=
es this tone generation then you will buy a product that supports it.

	Thanks,
	Paul

> Regards,
> Dave
>
>
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> Behalf Of Paul Kyzivat
> Sent: Wednesday, March 02, 2011 1:43 PM
> To: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018=20
> on indications to participants
>
> Dave,
>
> I recognize that there are environments where this audible tone is a=20
> requirement. And also environments where it is not, or that there is=20
> some *other* requirement.
>
> My question is whether rendering such things is "part of the=20
> mechanism",
>
> or simply something that some SRCs must be able to do.
>
> Making this part of the mechanism begs the question of "what mechanism".
>
> There are mechanisms for capturing the media for recording that do not=20
> have a device in place that can insert something into the media.=20
> Making this a requirement on the mechanism would exclude using those=20
> techniques.
>
> 	Thanks,
> 	Paul
>
> On 3/2/2011 2:57 PM, Dave Smith wrote:
>> I do have an input to this requirement.
>>
>> I agree that the system should be able to provide an indication to=20
>> recording-aware UAs that recording is currently occurring (for=20
>> appropriate rendering at the user interface).
>> I also believe that the system should be able to provide a "tone" to
> CS
>> participants to indicate that recording is currently occurring=20
>> (specifically, a distinct "beep tone" signal that is repeated at
> regular
>> intervals during the course of the telephone conversation when the=20
>> recording device is in use); note that this is consistent with
> existing
>> methods from FCC Rules Regarding Telephone Company Recording of=20
>> Interstate or International Wireline Telephone Conversations.
>> But I do not see a reason to mention "announcements", or "other media"
>> in this requirement.
>>
>> Therefore, I recommend the following wording for REQ-018:
>>
>> "REQ-018 The mechanism MUST provide a means of indicating to the=20
>> participants involved in a CS that their session is being recorded.
> To
>> support this the mechanism MUST provide a means of playing a
> repeatable
>> tone to CS participants, and also the mechanism MUST provide a means
> to
>> indicate to recording-aware UAs that recording is currently occurring=20
>> (for appropriate rendering at the user interface)."
>>
>> Regards,
>> Dave
>>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf
>> Of Elwell, John
>> Sent: Wednesday, March 02, 2011 3:41 AM
>> To: Leon Portman; siprec issue tracker
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Requirements #66 (new): Clarification of=20
>> REQ-018 on indications to participants
>>
>> In the interests of getting the requirements document finished, I=20
>> will set a short deadline for this remaining issue. If I have not=20
>> heard any objections to the proposal below by 2011-03-07 I will ask=20
>> the editor
> to
>> adopt this new text and publish -07.
>>
>> John (as chair)
>>
>>> -----Original Message-----
>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>> Sent: 28 February 2011 16:17
>>> To: Elwell, John; siprec issue tracker
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
>>> REQ-018 on indications to participants
>>>
>>> +1
>>>
>>> Leon
>>>
>>> -----Original Message-----
>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>>> Sent: Monday, February 28, 2011 5:35 PM
>>> To: Leon Portman; siprec issue tracker
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
>>> REQ-018 on indications to participants
>>>
>>> There has been little discussion on this, apart from support from=20
>>> Leon. The existing text says:
>>> "REQ-018 The mechanism MUST provide a means of indicating to the
>>>      participants involved in a CS that their session is being
> recorded.
>>>
>>>      Examples include: inject tones into the CS from the SRC, play a
>>>      message at the beginning of a session, a visual indicator on a
>>>      display, etc."
>>>
>>> I would suggest the following text:
>>> "REQ-018 The mechanism MUST provide a means of indicating to the=20
>>> participants involved in a CS that their session is being recorded.=20
>>> Although this can be accomplished using existing SIP techniques for=20
>>> playing an in-band tone, announcement or other media to=20
>>> participants, the mechanism is required also to provide an=20
>>> indication to recording-aware UAs for appropriate rendering at the=20
>>> user interface."
>>>
>>> John (as individual)
>>>
>>>> -----Original Message-----
>>>> From: Elwell, John
>>>> Sent: 23 February 2011 20:36
>>>> To: 'Leon Portman'; siprec issue tracker
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>>> of REQ-018
>>>> on indications to participants
>>>>
>>>> My feeling too.
>>>>
>>>> John (as individual)
>>>>
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>> Sent: 23 February 2011 17:25
>>>>> To: siprec issue tracker; Elwell, John
>>>>> Cc: siprec@ietf.org
>>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
>>>>> REQ-018 on indications to participants
>>>>>
>>>>> Because supporting of siprec-aware UA indication will
>>> require some
>>>>> additional protocol changes for CS, we probably should have a=20
>>>>> separate requirement for that
>>>>>
>>>>> Leon
>>>>>
>>>>> -----Original Message-----
>>>>> From: siprec issue tracker [mailto:trac@tools.ietf.org]
>>>>> Sent: Tuesday, February 15, 2011 10:24 AM
>>>>> To: Leon Portman; john.elwell@siemens-enterprise.com
>>>>> Cc: siprec@ietf.org
>>>>> Subject: [siprec] Requirements #66 (new): Clarification of
>>>>> REQ-018 on indications to participants
>>>>>
>>>>> #66: Clarification of REQ-018 on indications to participants
>>>>>
>>>>>    REQ-018 can be satisfied in general by playing media to=20
>>>>> participants, but  do we need a more specific
>>> requirement, e.g., for
>>>>> siprec-aware UAs to know  whether the CS is being recorded or not?
>>>>>
>>>>>    John
>>>>>
>>>>> --
>>>>> ------------------------------------------------+-------------
>>>>> ----------
>>>>> ------------------------------------------------+----
>>>>>    Reporter:  john.elwell@...                       |
>>>>> Owner:  leon.portman@...
>>>>>        Type:  defect                              |
>>>>> Status:  new
>>>>>    Priority:  major                               |
>>>>> Milestone:
>>>>> Component:  Requirements                        |
>>>>> Version:
>>>>>    Severity:  In WG Last Call                     |
>>>>> Keywords:
>>>>> ------------------------------------------------+-------------
>>>>> ----------
>>>>> ------------------------------------------------+----
>>>>>
>>>>> Ticket URL:<https://trac.tools.ietf.org/wg/siprec/trac/ticket/66>
>>>>> siprec<http://tools.ietf.org/siprec/>
>>>>>
>>>>>
>>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>>
>> 				=09
>>
> ----------------------------------------------------------------------
> --
> -------------------------------------------
>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may=20
>> contain
> confidential and proprietary information of Alcatel-Lucent and/or its=20
> affiliated entities. Access by the intended recipient only is=20
> authorized. Any liability arising from any party acting, or refraining=20
> from acting, on any information contained in this e-mail is hereby=20
> excluded. If you are not the intended recipient, please notify the=20
> sender immediately, destroy the original transmission and its=20
> attachments and do not disclose the contents to any other person, use=20
> it for any purpose, or store or copy the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent=20
> and/or its affiliated entities.
>> 				=09
>> _______________________________________________
>> 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
>
> 				=09
> ----------------------------------------------------------------------
> ---------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affilia=
ted entities. Access by the intended recipient only is authorized. Any liab=
ility arising from any party acting, or refraining from acting, on any info=
rmation contained in this e-mail is hereby excluded. If you are not the int=
ended recipient, please notify the sender immediately, destroy the original=
 transmission and its attachments and do not disclose the contents to any o=
ther person, use it for any purpose, or store or copy the information in an=
y medium. Copyright in this e-mail and any attachments belongs to Alcatel-L=
ucent and/or its affiliated entities.
> 				=09
>
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From Dave.d.Smith@alcatel-lucent.com  Thu Mar  3 00:28:28 2011
Return-Path: <Dave.d.Smith@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 744B93A6981 for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 00:28:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vUlkQJojKTpU for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 00:28:26 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 8F97A3A694D for <siprec@ietf.org>; Thu,  3 Mar 2011 00:28:26 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p238TCNI005945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 Mar 2011 02:29:12 -0600 (CST)
Received: from relay-out1.dc.genesyslab.com (relay-out1.dc.genesyslab.com [172.22.68.187]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p238TAFV017251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Mar 2011 02:29:12 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.dc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id p238T8ko009343; Thu, 3 Mar 2011 00:29:09 -0800 (PST)
Received: from SARUMAN.us.int.genesyslab.com ([192.168.20.90]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Mar 2011 00:29:09 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Mar 2011 00:29:07 -0800
Message-ID: <CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
Thread-Index: AcvZTH+Vs7u6urhTT2Km7kQw3BSzZAAKEM4gAACNCkA=
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com> <4D6EFFD0.7070109@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com>
From: "Dave Smith" <Dave.d.Smith@alcatel-lucent.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 03 Mar 2011 08:29:09.0525 (UTC) FILETIME=[11571450:01CBD97D]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 08:28:28 -0000

I fully agree that an IVR solution (play an announcement) is an
acceptable method that is used today to inform a caller. =20
I was introducing this req't (#1 below) in order to improve on that. =20

Do we absolutely need #1 - probably not.  Do we absolutely need #2 -
probably not also.

It seems that you are indicating that at least for #1 a solution is
difficult to provide and would restrict the SRC solution significantly,
so we should not include it. =20
I am wondering if that is also the case for #2.    =20

I don't think we need to mention any "optional" solutions in the req't.


Regards,
Dave

-----Original Message-----
From: Leon Portman [mailto:Leon.Portman@nice.com]=20
Sent: Wednesday, March 02, 2011 11:32 PM
To: Paul Kyzivat; Dave Smith
Cc: siprec@ietf.org
Subject: RE: [siprec] Requirements #66 (new): Clarification of REQ-018
on indications to participants

I agree with Paul. In the environment where SRC cannot inject any audio
into the CS, best practice is to have IVR or Voice Portal to make such
announcement.=20

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Paul Kyzivat
Sent: Thursday, March 03, 2011 4:41 AM
To: Dave Smith
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018
on indications to participants



On 3/2/2011 7:50 PM, Dave Smith wrote:
> I think the solution should be able to support these functionalities:
> 	1.  playing a repeatable tone to CS participants
> 	2.  indicate to recording-aware UAs that recording is currently=20
> occurring
>
> Although there may be other things that could be done, I believe that=20=

> these functionalities are reasonable and sufficient, and would be=20
> universally accepted, and that both are required in order to be able=20=

> to addresss most use cases for indicating to the participants involved

> in a CS that their session is being recorded.

> I am not sure of what the last paragraph of your response is about=20
> exactly.  A solution to this req't needs to be worked out in another=20=

> SIPREC Draft; my current thoughts are that since the SRC is handling=20=

> and in the path of CS UA media and is already communicating with these

> UAs, probably an SRC-based solution could be more easily used to solve

> this req't.

I'll try to elaborate:

I'm not informed of the specific legalities involved, but am of the
impression that they vary widely. There are certainly contexts in which
no audible indication need be played. (E.g. call centers, at least in
some places.) In some cases this is dealt with by playing a general
disclaimer at the beginning of the call, and/or having a contractual
relationship by which this isn't required.

In such environments the SRC may not need any way of injecting an
audible indication that recording is going on.

And there are ways an SRC could get the media for recording that don't
provide a way to inject these tones. (E.g. a media *relay* may fork the
media, but not be able to alter it.)

If you combine these things, you can end up with mechanisms for
implementing the SRC function that are *incapable* of satisfying your
proposed requirement, and yet are perfectly suitable for the intended
recording task. I don't want to rule those out as valid implementations
of siprec.

I'm fine with having the tone generation as an *option*, and one that
may be absolutely required in *some* markets. If you have a business
that requires this tone generation then you will buy a product that
supports it.

	Thanks,
	Paul

> Regards,
> Dave
>
>
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> Behalf Of Paul Kyzivat
> Sent: Wednesday, March 02, 2011 1:43 PM
> To: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018

> on indications to participants
>
> Dave,
>
> I recognize that there are environments where this audible tone is a=20=

> requirement. And also environments where it is not, or that there is=20=

> some *other* requirement.
>
> My question is whether rendering such things is "part of the=20
> mechanism",
>
> or simply something that some SRCs must be able to do.
>
> Making this part of the mechanism begs the question of "what
mechanism".
>
> There are mechanisms for capturing the media for recording that do not

> have a device in place that can insert something into the media.=20
> Making this a requirement on the mechanism would exclude using those=20=

> techniques.
>
> 	Thanks,
> 	Paul
>
> On 3/2/2011 2:57 PM, Dave Smith wrote:
>> I do have an input to this requirement.
>>
>> I agree that the system should be able to provide an indication to=20
>> recording-aware UAs that recording is currently occurring (for=20
>> appropriate rendering at the user interface).
>> I also believe that the system should be able to provide a "tone" to
> CS
>> participants to indicate that recording is currently occurring=20
>> (specifically, a distinct "beep tone" signal that is repeated at
> regular
>> intervals during the course of the telephone conversation when the=20
>> recording device is in use); note that this is consistent with
> existing
>> methods from FCC Rules Regarding Telephone Company Recording of=20
>> Interstate or International Wireline Telephone Conversations.
>> But I do not see a reason to mention "announcements", or "other
media"
>> in this requirement.
>>
>> Therefore, I recommend the following wording for REQ-018:
>>
>> "REQ-018 The mechanism MUST provide a means of indicating to the=20
>> participants involved in a CS that their session is being recorded.
> To
>> support this the mechanism MUST provide a means of playing a
> repeatable
>> tone to CS participants, and also the mechanism MUST provide a means
> to
>> indicate to recording-aware UAs that recording is currently occurring

>> (for appropriate rendering at the user interface)."
>>
>> Regards,
>> Dave
>>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf
>> Of Elwell, John
>> Sent: Wednesday, March 02, 2011 3:41 AM
>> To: Leon Portman; siprec issue tracker
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Requirements #66 (new): Clarification of=20
>> REQ-018 on indications to participants
>>
>> In the interests of getting the requirements document finished, I=20
>> will set a short deadline for this remaining issue. If I have not=20
>> heard any objections to the proposal below by 2011-03-07 I will ask=20=

>> the editor
> to
>> adopt this new text and publish -07.
>>
>> John (as chair)
>>
>>> -----Original Message-----
>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>> Sent: 28 February 2011 16:17
>>> To: Elwell, John; siprec issue tracker
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
>>> REQ-018 on indications to participants
>>>
>>> +1
>>>
>>> Leon
>>>
>>> -----Original Message-----
>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>>> Sent: Monday, February 28, 2011 5:35 PM
>>> To: Leon Portman; siprec issue tracker
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
>>> REQ-018 on indications to participants
>>>
>>> There has been little discussion on this, apart from support from=20
>>> Leon. The existing text says:
>>> "REQ-018 The mechanism MUST provide a means of indicating to the
>>>      participants involved in a CS that their session is being
> recorded.
>>>
>>>      Examples include: inject tones into the CS from the SRC, play a
>>>      message at the beginning of a session, a visual indicator on a
>>>      display, etc."
>>>
>>> I would suggest the following text:
>>> "REQ-018 The mechanism MUST provide a means of indicating to the=20
>>> participants involved in a CS that their session is being recorded.=20=

>>> Although this can be accomplished using existing SIP techniques for=20=

>>> playing an in-band tone, announcement or other media to=20
>>> participants, the mechanism is required also to provide an=20
>>> indication to recording-aware UAs for appropriate rendering at the=20=

>>> user interface."
>>>
>>> John (as individual)
>>>
>>>> -----Original Message-----
>>>> From: Elwell, John
>>>> Sent: 23 February 2011 20:36
>>>> To: 'Leon Portman'; siprec issue tracker
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>>> of REQ-018
>>>> on indications to participants
>>>>
>>>> My feeling too.
>>>>
>>>> John (as individual)
>>>>
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>> Sent: 23 February 2011 17:25
>>>>> To: siprec issue tracker; Elwell, John
>>>>> Cc: siprec@ietf.org
>>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
>>>>> REQ-018 on indications to participants
>>>>>
>>>>> Because supporting of siprec-aware UA indication will
>>> require some
>>>>> additional protocol changes for CS, we probably should have a=20
>>>>> separate requirement for that
>>>>>
>>>>> Leon
>>>>>
>>>>> -----Original Message-----
>>>>> From: siprec issue tracker [mailto:trac@tools.ietf.org]
>>>>> Sent: Tuesday, February 15, 2011 10:24 AM
>>>>> To: Leon Portman; john.elwell@siemens-enterprise.com
>>>>> Cc: siprec@ietf.org
>>>>> Subject: [siprec] Requirements #66 (new): Clarification of
>>>>> REQ-018 on indications to participants
>>>>>
>>>>> #66: Clarification of REQ-018 on indications to participants
>>>>>
>>>>>    REQ-018 can be satisfied in general by playing media to=20
>>>>> participants, but  do we need a more specific
>>> requirement, e.g., for
>>>>> siprec-aware UAs to know  whether the CS is being recorded or not?
>>>>>
>>>>>    John
>>>>>
>>>>> --
>>>>> ------------------------------------------------+-------------
>>>>> ----------
>>>>> ------------------------------------------------+----
>>>>>    Reporter:  john.elwell@...                       |
>>>>> Owner:  leon.portman@...
>>>>>        Type:  defect                              |
>>>>> Status:  new
>>>>>    Priority:  major                               |
>>>>> Milestone:
>>>>> Component:  Requirements                        |
>>>>> Version:
>>>>>    Severity:  In WG Last Call                     |
>>>>> Keywords:
>>>>> ------------------------------------------------+-------------
>>>>> ----------
>>>>> ------------------------------------------------+----
>>>>>
>>>>> Ticket URL:<https://trac.tools.ietf.org/wg/siprec/trac/ticket/66>
>>>>> siprec<http://tools.ietf.org/siprec/>
>>>>>
>>>>>
>>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>>
>> 				=09
>>
> ----------------------------------------------------------------------
> --
> -------------------------------------------
>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may=20
>> contain
> confidential and proprietary information of Alcatel-Lucent and/or its=20=

> affiliated entities. Access by the intended recipient only is=20
> authorized. Any liability arising from any party acting, or refraining

> from acting, on any information contained in this e-mail is hereby=20
> excluded. If you are not the intended recipient, please notify the=20
> sender immediately, destroy the original transmission and its=20
> attachments and do not disclose the contents to any other person, use=20=

> it for any purpose, or store or copy the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent

> and/or its affiliated entities.
>> 				=09
>> _______________________________________________
>> 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
>
> 				=09
> ----------------------------------------------------------------------
> ---------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary information of Alcatel-Lucent and/or its
affiliated entities. Access by the intended recipient only is
authorized. Any liability arising from any party acting, or refraining
from acting, on any information contained in this e-mail is hereby
excluded. If you are not the intended recipient, please notify the
sender immediately, destroy the original transmission and its
attachments and do not disclose the contents to any other person, use it
for any purpose, or store or copy the information in any medium.
Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
> 				=09
>
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From john.elwell@siemens-enterprise.com  Thu Mar  3 01:13:35 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 656003A69A2 for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 01:13:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.618
X-Spam-Level: 
X-Spam-Status: No, score=-102.618 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RmnnRBo5ByqC for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 01:13:34 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 597853A69A1 for <siprec@ietf.org>; Thu,  3 Mar 2011 01:13:33 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3604956; Thu, 3 Mar 2011 10:14:20 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id AFFDD1EB82AE; Thu,  3 Mar 2011 10:14:16 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 3 Mar 2011 10:14:16 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Dave Smith <Dave.d.Smith@alcatel-lucent.com>, Leon Portman <Leon.Portman@nice.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Thu, 3 Mar 2011 10:14:15 +0100
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
Thread-Index: AcvZTH+Vs7u6urhTT2Km7kQw3BSzZAAKEM4gAACNCkAAAjkN0A==
Message-ID: <A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com> <4D6EFFD0.7070109@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com> <CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com>
In-Reply-To: <CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on	indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 09:13:35 -0000

Concerning #1, I agree we need to be able to accommodate the different requ=
irements of different regions, countries, business sectors, etc.. Sometimes=
 this might involve playing a tone (e.g., a repeated beep) for the duration=
 of recording, and sometimes this might involve an announcement at the begi=
nning of the session, which will suffice whether or not recording actually =
takes place during the session. Basically, since not all users will use sip=
rec-aware UAs, particularly PSTN users, the only solution is for the SRC to=
 arrange that the appropriate tone or announcement is injected into the aud=
io stream when required. If the SRC itself is able to do this, we don't nee=
d a SIP solution. If the SRC uses a media server to do this, existing SIP/S=
DP mechanisms will cater for this. I don't anticipate siprec providing new =
mechanisms for this. It is really just a case of not preventing the use of =
such mechanisms. How about the following text?

"REQ-x1 The mechanism MUST NOT prevent the application of tones or announce=
ments during recording or at the start of a CS to support legal or policy r=
equirements for notifying participants that the call is being recorded or m=
ay be recorded."

Concerning #2, I see this more of a courtesy thing, rather than a legal thi=
ng. Most web-based conference applications give a visual indication of whet=
her the conference is being recorded, achieved using web technology. Where =
this is not available, it would be useful if siprec-aware UAs in the CS cou=
ld be advised when recording is taking place so that they can give an appro=
priate indication to the user. I can see a number of reasons for this:
- It provides the possibility of alternative modes for hearing-impaired use=
rs.
- It gives more precise information in cases where an SRC-injected announce=
ment is given only at the start of the call.
- It provides feedback to users who have requested that recording be starte=
d / stopped / paused / resumed.
- It gives an explicit indication to users who might not understand the mea=
ning of an injected tone.
- It is independent of medium type (audio, video, real-time text, fax...).
- Potentially its granularity could be on a per medium basis, although I wo=
uld prefer to leave that as an option for the solution, rather than making =
a requirement.

So how about the following text?

"REQ-x2 The mechanism MUST provide a means of indicating to recording-aware=
 UAs whether recording is taking place, for appropriate rendering at the us=
er interface.

John (as individual)

> >>> participants involved in a CS that their session is being=20
> recorded.=20
> >>> Although this can be accomplished using existing SIP=20
> techniques for=20
> >>> playing an in-band tone, announcement or other media to=20
> >>> participants, the mechanism is required also to provide an=20
> >>> indication to recording-aware UAs for appropriate=20
> rendering at the=20
> >>> user interface."

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
> Sent: 03 March 2011 08:29
> To: Leon Portman; Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018 on indications to participants
>=20
> I fully agree that an IVR solution (play an announcement) is an
> acceptable method that is used today to inform a caller. =20
> I was introducing this req't (#1 below) in order to improve on that. =20
>=20
> Do we absolutely need #1 - probably not.  Do we absolutely need #2 -
> probably not also.
>=20
> It seems that you are indicating that at least for #1 a solution is
> difficult to provide and would restrict the SRC solution=20
> significantly,
> so we should not include it. =20
> I am wondering if that is also the case for #2.    =20
>=20
> I don't think we need to mention any "optional" solutions in=20
> the req't.
>=20
>=20
> Regards,
> Dave
>=20
> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: Wednesday, March 02, 2011 11:32 PM
> To: Paul Kyzivat; Dave Smith
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification of REQ-018
> on indications to participants
>=20
> I agree with Paul. In the environment where SRC cannot inject=20
> any audio
> into the CS, best practice is to have IVR or Voice Portal to make such
> announcement.=20
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf
> Of Paul Kyzivat
> Sent: Thursday, March 03, 2011 4:41 AM
> To: Dave Smith
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018
> on indications to participants
>=20
>=20
>=20
> On 3/2/2011 7:50 PM, Dave Smith wrote:
> > I think the solution should be able to support these=20
> functionalities:
> > 	1.  playing a repeatable tone to CS participants
> > 	2.  indicate to recording-aware UAs that recording is currently=20
> > occurring
> >
> > Although there may be other things that could be done, I=20
> believe that=20
> > these functionalities are reasonable and sufficient, and would be=20
> > universally accepted, and that both are required in order=20
> to be able=20
> > to addresss most use cases for indicating to the=20
> participants involved
>=20
> > in a CS that their session is being recorded.
>=20
> > I am not sure of what the last paragraph of your response is about=20
> > exactly.  A solution to this req't needs to be worked out=20
> in another=20
> > SIPREC Draft; my current thoughts are that since the SRC is=20
> handling=20
> > and in the path of CS UA media and is already communicating=20
> with these
>=20
> > UAs, probably an SRC-based solution could be more easily=20
> used to solve
>=20
> > this req't.
>=20
> I'll try to elaborate:
>=20
> I'm not informed of the specific legalities involved, but am of the
> impression that they vary widely. There are certainly=20
> contexts in which
> no audible indication need be played. (E.g. call centers, at least in
> some places.) In some cases this is dealt with by playing a general
> disclaimer at the beginning of the call, and/or having a contractual
> relationship by which this isn't required.
>=20
> In such environments the SRC may not need any way of injecting an
> audible indication that recording is going on.
>=20
> And there are ways an SRC could get the media for recording that don't
> provide a way to inject these tones. (E.g. a media *relay*=20
> may fork the
> media, but not be able to alter it.)
>=20
> If you combine these things, you can end up with mechanisms for
> implementing the SRC function that are *incapable* of satisfying your
> proposed requirement, and yet are perfectly suitable for the intended
> recording task. I don't want to rule those out as valid=20
> implementations
> of siprec.
>=20
> I'm fine with having the tone generation as an *option*, and one that
> may be absolutely required in *some* markets. If you have a business
> that requires this tone generation then you will buy a product that
> supports it.
>=20
> 	Thanks,
> 	Paul
>=20
> > Regards,
> > Dave
> >
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > Behalf Of Paul Kyzivat
> > Sent: Wednesday, March 02, 2011 1:43 PM
> > To: siprec@ietf.org
> > Subject: Re: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018
>=20
> > on indications to participants
> >
> > Dave,
> >
> > I recognize that there are environments where this audible=20
> tone is a=20
> > requirement. And also environments where it is not, or that=20
> there is=20
> > some *other* requirement.
> >
> > My question is whether rendering such things is "part of the=20
> > mechanism",
> >
> > or simply something that some SRCs must be able to do.
> >
> > Making this part of the mechanism begs the question of "what
> mechanism".
> >
> > There are mechanisms for capturing the media for recording=20
> that do not
>=20
> > have a device in place that can insert something into the media.=20
> > Making this a requirement on the mechanism would exclude=20
> using those=20
> > techniques.
> >
> > 	Thanks,
> > 	Paul
> >
> > On 3/2/2011 2:57 PM, Dave Smith wrote:
> >> I do have an input to this requirement.
> >>
> >> I agree that the system should be able to provide an indication to=20
> >> recording-aware UAs that recording is currently occurring (for=20
> >> appropriate rendering at the user interface).
> >> I also believe that the system should be able to provide a=20
> "tone" to
> > CS
> >> participants to indicate that recording is currently occurring=20
> >> (specifically, a distinct "beep tone" signal that is repeated at
> > regular
> >> intervals during the course of the telephone conversation when the=20
> >> recording device is in use); note that this is consistent with
> > existing
> >> methods from FCC Rules Regarding Telephone Company Recording of=20
> >> Interstate or International Wireline Telephone Conversations.
> >> But I do not see a reason to mention "announcements", or "other
> media"
> >> in this requirement.
> >>
> >> Therefore, I recommend the following wording for REQ-018:
> >>
> >> "REQ-018 The mechanism MUST provide a means of indicating to the=20
> >> participants involved in a CS that their session is being recorded.
> > To
> >> support this the mechanism MUST provide a means of playing a
> > repeatable
> >> tone to CS participants, and also the mechanism MUST=20
> provide a means
> > to
> >> indicate to recording-aware UAs that recording is=20
> currently occurring
>=20
> >> (for appropriate rendering at the user interface)."
> >>
> >> Regards,
> >> Dave
> >>
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf
> >> Of Elwell, John
> >> Sent: Wednesday, March 02, 2011 3:41 AM
> >> To: Leon Portman; siprec issue tracker
> >> Cc: siprec@ietf.org
> >> Subject: Re: [siprec] Requirements #66 (new): Clarification of=20
> >> REQ-018 on indications to participants
> >>
> >> In the interests of getting the requirements document finished, I=20
> >> will set a short deadline for this remaining issue. If I have not=20
> >> heard any objections to the proposal below by 2011-03-07 I=20
> will ask=20
> >> the editor
> > to
> >> adopt this new text and publish -07.
> >>
> >> John (as chair)
> >>
> >>> -----Original Message-----
> >>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> >>> Sent: 28 February 2011 16:17
> >>> To: Elwell, John; siprec issue tracker
> >>> Cc: siprec@ietf.org
> >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
> >>> REQ-018 on indications to participants
> >>>
> >>> +1
> >>>
> >>> Leon
> >>>
> >>> -----Original Message-----
> >>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> >>> Sent: Monday, February 28, 2011 5:35 PM
> >>> To: Leon Portman; siprec issue tracker
> >>> Cc: siprec@ietf.org
> >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
> >>> REQ-018 on indications to participants
> >>>
> >>> There has been little discussion on this, apart from support from=20
> >>> Leon. The existing text says:
> >>> "REQ-018 The mechanism MUST provide a means of indicating to the
> >>>      participants involved in a CS that their session is being
> > recorded.
> >>>
> >>>      Examples include: inject tones into the CS from the=20
> SRC, play a
> >>>      message at the beginning of a session, a visual=20
> indicator on a
> >>>      display, etc."
> >>>
> >>> I would suggest the following text:
> >>> "REQ-018 The mechanism MUST provide a means of indicating to the=20
> >>> participants involved in a CS that their session is being=20
> recorded.=20
> >>> Although this can be accomplished using existing SIP=20
> techniques for=20
> >>> playing an in-band tone, announcement or other media to=20
> >>> participants, the mechanism is required also to provide an=20
> >>> indication to recording-aware UAs for appropriate=20
> rendering at the=20
> >>> user interface."
> >>>
> >>> John (as individual)
> =

From Leon.Portman@nice.com  Thu Mar  3 07:23:20 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 701BF3A69F8 for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 07:23:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VFQtg9AItudK for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 07:23:18 -0800 (PST)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 041BD3A68AD for <siprec@ietf.org>; Thu,  3 Mar 2011 07:23:18 -0800 (PST)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Thu, 3 Mar 2011 17:24:24 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, Dave Smith <Dave.d.Smith@alcatel-lucent.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Thu, 3 Mar 2011 17:24:22 +0200
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
Thread-Index: AcvZTH+Vs7u6urhTT2Km7kQw3BSzZAAKEM4gAACNCkAAAjkN0AANwi0g
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com> <4D6EFFD0.7070109@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com> <CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com> <A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on	indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 15:23:20 -0000

I agree with your points. Just generic question, do we really need a requir=
ement for mechanism not to prevent something? It can be lot of things like =
encryption, codec negotiation, ability to transfer call etc.

Leon

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Thursday, March 03, 2011 11:14 AM
To: Dave Smith; Leon Portman; Paul Kyzivat
Cc: siprec@ietf.org
Subject: RE: [siprec] Requirements #66 (new): Clarification of REQ-018 on i=
ndications to participants

Concerning #1, I agree we need to be able to accommodate the different requ=
irements of different regions, countries, business sectors, etc.. Sometimes=
 this might involve playing a tone (e.g., a repeated beep) for the duration=
 of recording, and sometimes this might involve an announcement at the begi=
nning of the session, which will suffice whether or not recording actually =
takes place during the session. Basically, since not all users will use sip=
rec-aware UAs, particularly PSTN users, the only solution is for the SRC to=
 arrange that the appropriate tone or announcement is injected into the aud=
io stream when required. If the SRC itself is able to do this, we don't nee=
d a SIP solution. If the SRC uses a media server to do this, existing SIP/S=
DP mechanisms will cater for this. I don't anticipate siprec providing new =
mechanisms for this. It is really just a case of not preventing the use of =
such mechanisms. How about the following text?

"REQ-x1 The mechanism MUST NOT prevent the application of tones or announce=
ments during recording or at the start of a CS to support legal or policy r=
equirements for notifying participants that the call is being recorded or m=
ay be recorded."

Concerning #2, I see this more of a courtesy thing, rather than a legal thi=
ng. Most web-based conference applications give a visual indication of whet=
her the conference is being recorded, achieved using web technology. Where =
this is not available, it would be useful if siprec-aware UAs in the CS cou=
ld be advised when recording is taking place so that they can give an appro=
priate indication to the user. I can see a number of reasons for this:
- It provides the possibility of alternative modes for hearing-impaired use=
rs.
- It gives more precise information in cases where an SRC-injected announce=
ment is given only at the start of the call.
- It provides feedback to users who have requested that recording be starte=
d / stopped / paused / resumed.
- It gives an explicit indication to users who might not understand the mea=
ning of an injected tone.
- It is independent of medium type (audio, video, real-time text, fax...).
- Potentially its granularity could be on a per medium basis, although I wo=
uld prefer to leave that as an option for the solution, rather than making =
a requirement.

So how about the following text?

"REQ-x2 The mechanism MUST provide a means of indicating to recording-aware=
 UAs whether recording is taking place, for appropriate rendering at the us=
er interface.

John (as individual)

> >>> participants involved in a CS that their session is being
> recorded.=20
> >>> Although this can be accomplished using existing SIP
> techniques for
> >>> playing an in-band tone, announcement or other media to=20
> >>> participants, the mechanism is required also to provide an=20
> >>> indication to recording-aware UAs for appropriate
> rendering at the
> >>> user interface."

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
> Sent: 03 March 2011 08:29
> To: Leon Portman; Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018 on indications to participants
>=20
> I fully agree that an IVR solution (play an announcement) is an
> acceptable method that is used today to inform a caller. =20
> I was introducing this req't (#1 below) in order to improve on that. =20
>=20
> Do we absolutely need #1 - probably not.  Do we absolutely need #2 -
> probably not also.
>=20
> It seems that you are indicating that at least for #1 a solution is
> difficult to provide and would restrict the SRC solution=20
> significantly,
> so we should not include it. =20
> I am wondering if that is also the case for #2.    =20
>=20
> I don't think we need to mention any "optional" solutions in=20
> the req't.
>=20
>=20
> Regards,
> Dave
>=20
> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: Wednesday, March 02, 2011 11:32 PM
> To: Paul Kyzivat; Dave Smith
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification of REQ-018
> on indications to participants
>=20
> I agree with Paul. In the environment where SRC cannot inject=20
> any audio
> into the CS, best practice is to have IVR or Voice Portal to make such
> announcement.=20
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf
> Of Paul Kyzivat
> Sent: Thursday, March 03, 2011 4:41 AM
> To: Dave Smith
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018
> on indications to participants
>=20
>=20
>=20
> On 3/2/2011 7:50 PM, Dave Smith wrote:
> > I think the solution should be able to support these=20
> functionalities:
> > 	1.  playing a repeatable tone to CS participants
> > 	2.  indicate to recording-aware UAs that recording is currently=20
> > occurring
> >
> > Although there may be other things that could be done, I=20
> believe that=20
> > these functionalities are reasonable and sufficient, and would be=20
> > universally accepted, and that both are required in order=20
> to be able=20
> > to addresss most use cases for indicating to the=20
> participants involved
>=20
> > in a CS that their session is being recorded.
>=20
> > I am not sure of what the last paragraph of your response is about=20
> > exactly.  A solution to this req't needs to be worked out=20
> in another=20
> > SIPREC Draft; my current thoughts are that since the SRC is=20
> handling=20
> > and in the path of CS UA media and is already communicating=20
> with these
>=20
> > UAs, probably an SRC-based solution could be more easily=20
> used to solve
>=20
> > this req't.
>=20
> I'll try to elaborate:
>=20
> I'm not informed of the specific legalities involved, but am of the
> impression that they vary widely. There are certainly=20
> contexts in which
> no audible indication need be played. (E.g. call centers, at least in
> some places.) In some cases this is dealt with by playing a general
> disclaimer at the beginning of the call, and/or having a contractual
> relationship by which this isn't required.
>=20
> In such environments the SRC may not need any way of injecting an
> audible indication that recording is going on.
>=20
> And there are ways an SRC could get the media for recording that don't
> provide a way to inject these tones. (E.g. a media *relay*=20
> may fork the
> media, but not be able to alter it.)
>=20
> If you combine these things, you can end up with mechanisms for
> implementing the SRC function that are *incapable* of satisfying your
> proposed requirement, and yet are perfectly suitable for the intended
> recording task. I don't want to rule those out as valid=20
> implementations
> of siprec.
>=20
> I'm fine with having the tone generation as an *option*, and one that
> may be absolutely required in *some* markets. If you have a business
> that requires this tone generation then you will buy a product that
> supports it.
>=20
> 	Thanks,
> 	Paul
>=20
> > Regards,
> > Dave
> >
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > Behalf Of Paul Kyzivat
> > Sent: Wednesday, March 02, 2011 1:43 PM
> > To: siprec@ietf.org
> > Subject: Re: [siprec] Requirements #66 (new): Clarification=20
> of REQ-018
>=20
> > on indications to participants
> >
> > Dave,
> >
> > I recognize that there are environments where this audible=20
> tone is a=20
> > requirement. And also environments where it is not, or that=20
> there is=20
> > some *other* requirement.
> >
> > My question is whether rendering such things is "part of the=20
> > mechanism",
> >
> > or simply something that some SRCs must be able to do.
> >
> > Making this part of the mechanism begs the question of "what
> mechanism".
> >
> > There are mechanisms for capturing the media for recording=20
> that do not
>=20
> > have a device in place that can insert something into the media.=20
> > Making this a requirement on the mechanism would exclude=20
> using those=20
> > techniques.
> >
> > 	Thanks,
> > 	Paul
> >
> > On 3/2/2011 2:57 PM, Dave Smith wrote:
> >> I do have an input to this requirement.
> >>
> >> I agree that the system should be able to provide an indication to=20
> >> recording-aware UAs that recording is currently occurring (for=20
> >> appropriate rendering at the user interface).
> >> I also believe that the system should be able to provide a=20
> "tone" to
> > CS
> >> participants to indicate that recording is currently occurring=20
> >> (specifically, a distinct "beep tone" signal that is repeated at
> > regular
> >> intervals during the course of the telephone conversation when the=20
> >> recording device is in use); note that this is consistent with
> > existing
> >> methods from FCC Rules Regarding Telephone Company Recording of=20
> >> Interstate or International Wireline Telephone Conversations.
> >> But I do not see a reason to mention "announcements", or "other
> media"
> >> in this requirement.
> >>
> >> Therefore, I recommend the following wording for REQ-018:
> >>
> >> "REQ-018 The mechanism MUST provide a means of indicating to the=20
> >> participants involved in a CS that their session is being recorded.
> > To
> >> support this the mechanism MUST provide a means of playing a
> > repeatable
> >> tone to CS participants, and also the mechanism MUST=20
> provide a means
> > to
> >> indicate to recording-aware UAs that recording is=20
> currently occurring
>=20
> >> (for appropriate rendering at the user interface)."
> >>
> >> Regards,
> >> Dave
> >>
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf
> >> Of Elwell, John
> >> Sent: Wednesday, March 02, 2011 3:41 AM
> >> To: Leon Portman; siprec issue tracker
> >> Cc: siprec@ietf.org
> >> Subject: Re: [siprec] Requirements #66 (new): Clarification of=20
> >> REQ-018 on indications to participants
> >>
> >> In the interests of getting the requirements document finished, I=20
> >> will set a short deadline for this remaining issue. If I have not=20
> >> heard any objections to the proposal below by 2011-03-07 I=20
> will ask=20
> >> the editor
> > to
> >> adopt this new text and publish -07.
> >>
> >> John (as chair)
> >>
> >>> -----Original Message-----
> >>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> >>> Sent: 28 February 2011 16:17
> >>> To: Elwell, John; siprec issue tracker
> >>> Cc: siprec@ietf.org
> >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
> >>> REQ-018 on indications to participants
> >>>
> >>> +1
> >>>
> >>> Leon
> >>>
> >>> -----Original Message-----
> >>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> >>> Sent: Monday, February 28, 2011 5:35 PM
> >>> To: Leon Portman; siprec issue tracker
> >>> Cc: siprec@ietf.org
> >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of=20
> >>> REQ-018 on indications to participants
> >>>
> >>> There has been little discussion on this, apart from support from=20
> >>> Leon. The existing text says:
> >>> "REQ-018 The mechanism MUST provide a means of indicating to the
> >>>      participants involved in a CS that their session is being
> > recorded.
> >>>
> >>>      Examples include: inject tones into the CS from the=20
> SRC, play a
> >>>      message at the beginning of a session, a visual=20
> indicator on a
> >>>      display, etc."
> >>>
> >>> I would suggest the following text:
> >>> "REQ-018 The mechanism MUST provide a means of indicating to the=20
> >>> participants involved in a CS that their session is being=20
> recorded.=20
> >>> Although this can be accomplished using existing SIP=20
> techniques for=20
> >>> playing an in-band tone, announcement or other media to=20
> >>> participants, the mechanism is required also to provide an=20
> >>> indication to recording-aware UAs for appropriate=20
> rendering at the=20
> >>> user interface."
> >>>
> >>> John (as individual)
>=20

From john.elwell@siemens-enterprise.com  Thu Mar  3 09:16:09 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11A953A6830 for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 09:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.618
X-Spam-Level: 
X-Spam-Status: No, score=-102.618 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G74jGmOxjFTe for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 09:16:07 -0800 (PST)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id D055E3A69F0 for <siprec@ietf.org>; Thu,  3 Mar 2011 09:16:06 -0800 (PST)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3622890; Thu, 3 Mar 2011 18:17:09 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 423C323F028E; Thu,  3 Mar 2011 18:17:09 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 3 Mar 2011 18:17:09 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, Dave Smith <Dave.d.Smith@alcatel-lucent.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Thu, 3 Mar 2011 18:17:07 +0100
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018 on indications to participants
Thread-Index: AcvZTH+Vs7u6urhTT2Km7kQw3BSzZAAKEM4gAACNCkAAAjkN0AANwi0gAAObWlA=
Message-ID: <A444A0F8084434499206E78C106220CA06C2C5086D@MCHP058A.global-ad.net>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com> <4D6EFFD0.7070109@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com> <CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com> <A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 on	indications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 17:16:09 -0000

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 03 March 2011 15:24
> To: Elwell, John; Dave Smith; Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification
> of REQ-018 on indications to participants
>
> I agree with your points. Just generic question, do we really
> need a requirement for mechanism not to prevent something? It
> can be lot of things like encryption, codec negotiation,
> ability to transfer call etc.
[JRE] It is certainly worth questioning whether we need REQ-x1 below. On th=
e one hand, SIPREC is unlikely to specify anything that would prevent this =
existing capability. In fact it would be quite hard for SIPREC to specify s=
omething that would prevent the application of tones of announcement. Of co=
urse, there might be things that could be done at deployment time to preven=
t it (e.g., encryption), but that is not SIPREC's problem. However, I would=
 still be inclined to keep it. In particular, the Privacy Considerations se=
ction has a statement: "Therefore this document contains requirements for b=
eing able to notify users that a call is being recorded ...". I don't think=
 REQ-x2 alone would be sufficient to satisfy that, so if we were to remove =
REQ-x1 we would have to revisit the Privacy Considerations text, which I wo=
uld be very reluctant to do. So I would like to keep REQ-x1 or something si=
milar.

John (as individual)

>
> Leon
>
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 03, 2011 11:14 AM
> To: Dave Smith; Leon Portman; Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification
> of REQ-018 on indications to participants
>
> Concerning #1, I agree we need to be able to accommodate the
> different requirements of different regions, countries,
> business sectors, etc.. Sometimes this might involve playing
> a tone (e.g., a repeated beep) for the duration of recording,
> and sometimes this might involve an announcement at the
> beginning of the session, which will suffice whether or not
> recording actually takes place during the session. Basically,
> since not all users will use siprec-aware UAs, particularly
> PSTN users, the only solution is for the SRC to arrange that
> the appropriate tone or announcement is injected into the
> audio stream when required. If the SRC itself is able to do
> this, we don't need a SIP solution. If the SRC uses a media
> server to do this, existing SIP/SDP mechanisms will cater for
> this. I don't anticipate siprec providing new mechanisms for
> this. It is really just a case of not preventing the use of
> such mechanisms. How about the following text?
>
> "REQ-x1 The mechanism MUST NOT prevent the application of
> tones or announcements during recording or at the start of a
> CS to support legal or policy requirements for notifying
> participants that the call is being recorded or may be recorded."
>
> Concerning #2, I see this more of a courtesy thing, rather
> than a legal thing. Most web-based conference applications
> give a visual indication of whether the conference is being
> recorded, achieved using web technology. Where this is not
> available, it would be useful if siprec-aware UAs in the CS
> could be advised when recording is taking place so that they
> can give an appropriate indication to the user. I can see a
> number of reasons for this:
> - It provides the possibility of alternative modes for
> hearing-impaired users.
> - It gives more precise information in cases where an
> SRC-injected announcement is given only at the start of the call.
> - It provides feedback to users who have requested that
> recording be started / stopped / paused / resumed.
> - It gives an explicit indication to users who might not
> understand the meaning of an injected tone.
> - It is independent of medium type (audio, video, real-time
> text, fax...).
> - Potentially its granularity could be on a per medium basis,
> although I would prefer to leave that as an option for the
> solution, rather than making a requirement.
>
> So how about the following text?
>
> "REQ-x2 The mechanism MUST provide a means of indicating to
> recording-aware UAs whether recording is taking place, for
> appropriate rendering at the user interface.
>
> John (as individual)
>
> > >>> participants involved in a CS that their session is being
> > recorded.
> > >>> Although this can be accomplished using existing SIP
> > techniques for
> > >>> playing an in-band tone, announcement or other media to
> > >>> participants, the mechanism is required also to provide an
> > >>> indication to recording-aware UAs for appropriate
> > rendering at the
> > >>> user interface."
>
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
> > Sent: 03 March 2011 08:29
> > To: Leon Portman; Paul Kyzivat
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > of REQ-018 on indications to participants
> >
> > I fully agree that an IVR solution (play an announcement) is an
> > acceptable method that is used today to inform a caller.
> > I was introducing this req't (#1 below) in order to improve
> on that.
> >
> > Do we absolutely need #1 - probably not.  Do we absolutely need #2 -
> > probably not also.
> >
> > It seems that you are indicating that at least for #1 a solution is
> > difficult to provide and would restrict the SRC solution
> > significantly,
> > so we should not include it.
> > I am wondering if that is also the case for #2.
> >
> > I don't think we need to mention any "optional" solutions in
> > the req't.
> >
> >
> > Regards,
> > Dave
> >
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Wednesday, March 02, 2011 11:32 PM
> > To: Paul Kyzivat; Dave Smith
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Requirements #66 (new): Clarification
> of REQ-018
> > on indications to participants
> >
> > I agree with Paul. In the environment where SRC cannot inject
> > any audio
> > into the CS, best practice is to have IVR or Voice Portal
> to make such
> > announcement.
> >
> > Leon
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf
> > Of Paul Kyzivat
> > Sent: Thursday, March 03, 2011 4:41 AM
> > To: Dave Smith
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Requirements #66 (new): Clarification
> of REQ-018
> > on indications to participants
> >
> >
> >
> > On 3/2/2011 7:50 PM, Dave Smith wrote:
> > > I think the solution should be able to support these
> > functionalities:
> > >   1.  playing a repeatable tone to CS participants
> > >   2.  indicate to recording-aware UAs that recording is currently
> > > occurring
> > >
> > > Although there may be other things that could be done, I
> > believe that
> > > these functionalities are reasonable and sufficient, and would be
> > > universally accepted, and that both are required in order
> > to be able
> > > to addresss most use cases for indicating to the
> > participants involved
> >
> > > in a CS that their session is being recorded.
> >
> > > I am not sure of what the last paragraph of your response
> is about
> > > exactly.  A solution to this req't needs to be worked out
> > in another
> > > SIPREC Draft; my current thoughts are that since the SRC is
> > handling
> > > and in the path of CS UA media and is already communicating
> > with these
> >
> > > UAs, probably an SRC-based solution could be more easily
> > used to solve
> >
> > > this req't.
> >
> > I'll try to elaborate:
> >
> > I'm not informed of the specific legalities involved, but am of the
> > impression that they vary widely. There are certainly
> > contexts in which
> > no audible indication need be played. (E.g. call centers,
> at least in
> > some places.) In some cases this is dealt with by playing a general
> > disclaimer at the beginning of the call, and/or having a contractual
> > relationship by which this isn't required.
> >
> > In such environments the SRC may not need any way of injecting an
> > audible indication that recording is going on.
> >
> > And there are ways an SRC could get the media for recording
> that don't
> > provide a way to inject these tones. (E.g. a media *relay*
> > may fork the
> > media, but not be able to alter it.)
> >
> > If you combine these things, you can end up with mechanisms for
> > implementing the SRC function that are *incapable* of
> satisfying your
> > proposed requirement, and yet are perfectly suitable for
> the intended
> > recording task. I don't want to rule those out as valid
> > implementations
> > of siprec.
> >
> > I'm fine with having the tone generation as an *option*,
> and one that
> > may be absolutely required in *some* markets. If you have a business
> > that requires this tone generation then you will buy a product that
> > supports it.
> >
> >     Thanks,
> >     Paul
> >
> > > Regards,
> > > Dave
> > >
> > >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Paul Kyzivat
> > > Sent: Wednesday, March 02, 2011 1:43 PM
> > > To: siprec@ietf.org
> > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > of REQ-018
> >
> > > on indications to participants
> > >
> > > Dave,
> > >
> > > I recognize that there are environments where this audible
> > tone is a
> > > requirement. And also environments where it is not, or that
> > there is
> > > some *other* requirement.
> > >
> > > My question is whether rendering such things is "part of the
> > > mechanism",
> > >
> > > or simply something that some SRCs must be able to do.
> > >
> > > Making this part of the mechanism begs the question of "what
> > mechanism".
> > >
> > > There are mechanisms for capturing the media for recording
> > that do not
> >
> > > have a device in place that can insert something into the media.
> > > Making this a requirement on the mechanism would exclude
> > using those
> > > techniques.
> > >
> > >   Thanks,
> > >   Paul
> > >
> > > On 3/2/2011 2:57 PM, Dave Smith wrote:
> > >> I do have an input to this requirement.
> > >>
> > >> I agree that the system should be able to provide an
> indication to
> > >> recording-aware UAs that recording is currently occurring (for
> > >> appropriate rendering at the user interface).
> > >> I also believe that the system should be able to provide a
> > "tone" to
> > > CS
> > >> participants to indicate that recording is currently occurring
> > >> (specifically, a distinct "beep tone" signal that is repeated at
> > > regular
> > >> intervals during the course of the telephone
> conversation when the
> > >> recording device is in use); note that this is consistent with
> > > existing
> > >> methods from FCC Rules Regarding Telephone Company Recording of
> > >> Interstate or International Wireline Telephone Conversations.
> > >> But I do not see a reason to mention "announcements", or "other
> > media"
> > >> in this requirement.
> > >>
> > >> Therefore, I recommend the following wording for REQ-018:
> > >>
> > >> "REQ-018 The mechanism MUST provide a means of indicating to the
> > >> participants involved in a CS that their session is
> being recorded.
> > > To
> > >> support this the mechanism MUST provide a means of playing a
> > > repeatable
> > >> tone to CS participants, and also the mechanism MUST
> > provide a means
> > > to
> > >> indicate to recording-aware UAs that recording is
> > currently occurring
> >
> > >> (for appropriate rendering at the user interface)."
> > >>
> > >> Regards,
> > >> Dave
> > >>
> > >> -----Original Message-----
> > >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf
> > >> Of Elwell, John
> > >> Sent: Wednesday, March 02, 2011 3:41 AM
> > >> To: Leon Portman; siprec issue tracker
> > >> Cc: siprec@ietf.org
> > >> Subject: Re: [siprec] Requirements #66 (new): Clarification of
> > >> REQ-018 on indications to participants
> > >>
> > >> In the interests of getting the requirements document
> finished, I
> > >> will set a short deadline for this remaining issue. If I
> have not
> > >> heard any objections to the proposal below by 2011-03-07 I
> > will ask
> > >> the editor
> > > to
> > >> adopt this new text and publish -07.
> > >>
> > >> John (as chair)
> > >>
> > >>> -----Original Message-----
> > >>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> > >>> Sent: 28 February 2011 16:17
> > >>> To: Elwell, John; siprec issue tracker
> > >>> Cc: siprec@ietf.org
> > >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
> > >>> REQ-018 on indications to participants
> > >>>
> > >>> +1
> > >>>
> > >>> Leon
> > >>>
> > >>> -----Original Message-----
> > >>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > >>> Sent: Monday, February 28, 2011 5:35 PM
> > >>> To: Leon Portman; siprec issue tracker
> > >>> Cc: siprec@ietf.org
> > >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
> > >>> REQ-018 on indications to participants
> > >>>
> > >>> There has been little discussion on this, apart from
> support from
> > >>> Leon. The existing text says:
> > >>> "REQ-018 The mechanism MUST provide a means of indicating to the
> > >>>      participants involved in a CS that their session is being
> > > recorded.
> > >>>
> > >>>      Examples include: inject tones into the CS from the
> > SRC, play a
> > >>>      message at the beginning of a session, a visual
> > indicator on a
> > >>>      display, etc."
> > >>>
> > >>> I would suggest the following text:
> > >>> "REQ-018 The mechanism MUST provide a means of
> indicating to the
> > >>> participants involved in a CS that their session is being
> > recorded.
> > >>> Although this can be accomplished using existing SIP
> > techniques for
> > >>> playing an in-band tone, announcement or other media to
> > >>> participants, the mechanism is required also to provide an
> > >>> indication to recording-aware UAs for appropriate
> > rendering at the
> > >>> user interface."
> > >>>
> > >>> John (as individual)
> >
>

From Dave.d.Smith@alcatel-lucent.com  Thu Mar  3 09:37:10 2011
Return-Path: <Dave.d.Smith@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B639A3A69FD for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 09:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kuEynRHJEeNL for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 09:37:09 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id C809E3A6838 for <siprec@ietf.org>; Thu,  3 Mar 2011 09:37:08 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p23HcAOX007239 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 Mar 2011 11:38:10 -0600 (CST)
Received: from relay-out1.wc.genesyslab.com (relay-out1.wc.genesyslab.com [172.22.70.114]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p23Hc8BH018100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Mar 2011 11:38:09 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.wc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id p23Hc6Gr003324; Thu, 3 Mar 2011 09:38:09 -0800 (PST)
Received: from SARUMAN.us.int.genesyslab.com ([192.168.20.90]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Mar 2011 09:38:04 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Mar 2011 09:38:03 -0800
Message-ID: <CD2DE94B86B69443B53711F606FCAE120862E4B7@SARUMAN.us.int.genesyslab.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA06C2C5086D@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018 onindications to participants
Thread-Index: AcvZTH+Vs7u6urhTT2Km7kQw3BSzZAAKEM4gAACNCkAAAjkN0AANwi0gAAObWlAAAPSOQA==
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com><4D6EFFD0.7070109@cisco.com><07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com> <CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com> <A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA06C2C5086D@MCHP058A.global-ad.net>
From: "Dave Smith" <Dave.d.Smith@alcatel-lucent.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Leon Portman" <Leon.Portman@nice.com>, "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 03 Mar 2011 17:38:04.0800 (UTC) FILETIME=[C04B3800:01CBD9C9]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018 onindications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 17:37:10 -0000

Thanks for the detailed inputs/explanations.  I agree with the
recommendations for using REQ-x1 and -x2.

Regards,
Dave

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Thursday, March 03, 2011 9:17 AM
To: Leon Portman; Dave Smith; Paul Kyzivat
Cc: siprec@ietf.org
Subject: RE: [siprec] Requirements #66 (new): Clarification of REQ-018
onindications to participants



> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 03 March 2011 15:24
> To: Elwell, John; Dave Smith; Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification
> of REQ-018 on indications to participants
>
> I agree with your points. Just generic question, do we really
> need a requirement for mechanism not to prevent something? It
> can be lot of things like encryption, codec negotiation,
> ability to transfer call etc.
[JRE] It is certainly worth questioning whether we need REQ-x1 below. On
the one hand, SIPREC is unlikely to specify anything that would prevent
this existing capability. In fact it would be quite hard for SIPREC to
specify something that would prevent the application of tones of
announcement. Of course, there might be things that could be done at
deployment time to prevent it (e.g., encryption), but that is not
SIPREC's problem. However, I would still be inclined to keep it. In
particular, the Privacy Considerations section has a statement:
"Therefore this document contains requirements for being able to notify
users that a call is being recorded ...". I don't think REQ-x2 alone
would be sufficient to satisfy that, so if we were to remove REQ-x1 we
would have to revisit the Privacy Considerations text, which I would be
very reluctant to do. So I would like to keep REQ-x1 or something
similar.

John (as individual)

>
> Leon
>
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 03, 2011 11:14 AM
> To: Dave Smith; Leon Portman; Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification
> of REQ-018 on indications to participants
>
> Concerning #1, I agree we need to be able to accommodate the
> different requirements of different regions, countries,
> business sectors, etc.. Sometimes this might involve playing
> a tone (e.g., a repeated beep) for the duration of recording,
> and sometimes this might involve an announcement at the
> beginning of the session, which will suffice whether or not
> recording actually takes place during the session. Basically,
> since not all users will use siprec-aware UAs, particularly
> PSTN users, the only solution is for the SRC to arrange that
> the appropriate tone or announcement is injected into the
> audio stream when required. If the SRC itself is able to do
> this, we don't need a SIP solution. If the SRC uses a media
> server to do this, existing SIP/SDP mechanisms will cater for
> this. I don't anticipate siprec providing new mechanisms for
> this. It is really just a case of not preventing the use of
> such mechanisms. How about the following text?
>
> "REQ-x1 The mechanism MUST NOT prevent the application of
> tones or announcements during recording or at the start of a
> CS to support legal or policy requirements for notifying
> participants that the call is being recorded or may be recorded."
>
> Concerning #2, I see this more of a courtesy thing, rather
> than a legal thing. Most web-based conference applications
> give a visual indication of whether the conference is being
> recorded, achieved using web technology. Where this is not
> available, it would be useful if siprec-aware UAs in the CS
> could be advised when recording is taking place so that they
> can give an appropriate indication to the user. I can see a
> number of reasons for this:
> - It provides the possibility of alternative modes for
> hearing-impaired users.
> - It gives more precise information in cases where an
> SRC-injected announcement is given only at the start of the call.
> - It provides feedback to users who have requested that
> recording be started / stopped / paused / resumed.
> - It gives an explicit indication to users who might not
> understand the meaning of an injected tone.
> - It is independent of medium type (audio, video, real-time
> text, fax...).
> - Potentially its granularity could be on a per medium basis,
> although I would prefer to leave that as an option for the
> solution, rather than making a requirement.
>
> So how about the following text?
>
> "REQ-x2 The mechanism MUST provide a means of indicating to
> recording-aware UAs whether recording is taking place, for
> appropriate rendering at the user interface.
>
> John (as individual)
>
> > >>> participants involved in a CS that their session is being
> > recorded.
> > >>> Although this can be accomplished using existing SIP
> > techniques for
> > >>> playing an in-band tone, announcement or other media to
> > >>> participants, the mechanism is required also to provide an
> > >>> indication to recording-aware UAs for appropriate
> > rendering at the
> > >>> user interface."
>
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
> > Sent: 03 March 2011 08:29
> > To: Leon Portman; Paul Kyzivat
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > of REQ-018 on indications to participants
> >
> > I fully agree that an IVR solution (play an announcement) is an
> > acceptable method that is used today to inform a caller.
> > I was introducing this req't (#1 below) in order to improve
> on that.
> >
> > Do we absolutely need #1 - probably not.  Do we absolutely need #2 -
> > probably not also.
> >
> > It seems that you are indicating that at least for #1 a solution is
> > difficult to provide and would restrict the SRC solution
> > significantly,
> > so we should not include it.
> > I am wondering if that is also the case for #2.
> >
> > I don't think we need to mention any "optional" solutions in
> > the req't.
> >
> >
> > Regards,
> > Dave
> >
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Wednesday, March 02, 2011 11:32 PM
> > To: Paul Kyzivat; Dave Smith
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Requirements #66 (new): Clarification
> of REQ-018
> > on indications to participants
> >
> > I agree with Paul. In the environment where SRC cannot inject
> > any audio
> > into the CS, best practice is to have IVR or Voice Portal
> to make such
> > announcement.
> >
> > Leon
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf
> > Of Paul Kyzivat
> > Sent: Thursday, March 03, 2011 4:41 AM
> > To: Dave Smith
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Requirements #66 (new): Clarification
> of REQ-018
> > on indications to participants
> >
> >
> >
> > On 3/2/2011 7:50 PM, Dave Smith wrote:
> > > I think the solution should be able to support these
> > functionalities:
> > >   1.  playing a repeatable tone to CS participants
> > >   2.  indicate to recording-aware UAs that recording is currently
> > > occurring
> > >
> > > Although there may be other things that could be done, I
> > believe that
> > > these functionalities are reasonable and sufficient, and would be
> > > universally accepted, and that both are required in order
> > to be able
> > > to addresss most use cases for indicating to the
> > participants involved
> >
> > > in a CS that their session is being recorded.
> >
> > > I am not sure of what the last paragraph of your response
> is about
> > > exactly.  A solution to this req't needs to be worked out
> > in another
> > > SIPREC Draft; my current thoughts are that since the SRC is
> > handling
> > > and in the path of CS UA media and is already communicating
> > with these
> >
> > > UAs, probably an SRC-based solution could be more easily
> > used to solve
> >
> > > this req't.
> >
> > I'll try to elaborate:
> >
> > I'm not informed of the specific legalities involved, but am of the
> > impression that they vary widely. There are certainly
> > contexts in which
> > no audible indication need be played. (E.g. call centers,
> at least in
> > some places.) In some cases this is dealt with by playing a general
> > disclaimer at the beginning of the call, and/or having a contractual
> > relationship by which this isn't required.
> >
> > In such environments the SRC may not need any way of injecting an
> > audible indication that recording is going on.
> >
> > And there are ways an SRC could get the media for recording
> that don't
> > provide a way to inject these tones. (E.g. a media *relay*
> > may fork the
> > media, but not be able to alter it.)
> >
> > If you combine these things, you can end up with mechanisms for
> > implementing the SRC function that are *incapable* of
> satisfying your
> > proposed requirement, and yet are perfectly suitable for
> the intended
> > recording task. I don't want to rule those out as valid
> > implementations
> > of siprec.
> >
> > I'm fine with having the tone generation as an *option*,
> and one that
> > may be absolutely required in *some* markets. If you have a business
> > that requires this tone generation then you will buy a product that
> > supports it.
> >
> >     Thanks,
> >     Paul
> >
> > > Regards,
> > > Dave
> > >
> > >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Paul Kyzivat
> > > Sent: Wednesday, March 02, 2011 1:43 PM
> > > To: siprec@ietf.org
> > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > of REQ-018
> >
> > > on indications to participants
> > >
> > > Dave,
> > >
> > > I recognize that there are environments where this audible
> > tone is a
> > > requirement. And also environments where it is not, or that
> > there is
> > > some *other* requirement.
> > >
> > > My question is whether rendering such things is "part of the
> > > mechanism",
> > >
> > > or simply something that some SRCs must be able to do.
> > >
> > > Making this part of the mechanism begs the question of "what
> > mechanism".
> > >
> > > There are mechanisms for capturing the media for recording
> > that do not
> >
> > > have a device in place that can insert something into the media.
> > > Making this a requirement on the mechanism would exclude
> > using those
> > > techniques.
> > >
> > >   Thanks,
> > >   Paul
> > >
> > > On 3/2/2011 2:57 PM, Dave Smith wrote:
> > >> I do have an input to this requirement.
> > >>
> > >> I agree that the system should be able to provide an
> indication to
> > >> recording-aware UAs that recording is currently occurring (for
> > >> appropriate rendering at the user interface).
> > >> I also believe that the system should be able to provide a
> > "tone" to
> > > CS
> > >> participants to indicate that recording is currently occurring
> > >> (specifically, a distinct "beep tone" signal that is repeated at
> > > regular
> > >> intervals during the course of the telephone
> conversation when the
> > >> recording device is in use); note that this is consistent with
> > > existing
> > >> methods from FCC Rules Regarding Telephone Company Recording of
> > >> Interstate or International Wireline Telephone Conversations.
> > >> But I do not see a reason to mention "announcements", or "other
> > media"
> > >> in this requirement.
> > >>
> > >> Therefore, I recommend the following wording for REQ-018:
> > >>
> > >> "REQ-018 The mechanism MUST provide a means of indicating to the
> > >> participants involved in a CS that their session is
> being recorded.
> > > To
> > >> support this the mechanism MUST provide a means of playing a
> > > repeatable
> > >> tone to CS participants, and also the mechanism MUST
> > provide a means
> > > to
> > >> indicate to recording-aware UAs that recording is
> > currently occurring
> >
> > >> (for appropriate rendering at the user interface)."
> > >>
> > >> Regards,
> > >> Dave
> > >>
> > >> -----Original Message-----
> > >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf
> > >> Of Elwell, John
> > >> Sent: Wednesday, March 02, 2011 3:41 AM
> > >> To: Leon Portman; siprec issue tracker
> > >> Cc: siprec@ietf.org
> > >> Subject: Re: [siprec] Requirements #66 (new): Clarification of
> > >> REQ-018 on indications to participants
> > >>
> > >> In the interests of getting the requirements document
> finished, I
> > >> will set a short deadline for this remaining issue. If I
> have not
> > >> heard any objections to the proposal below by 2011-03-07 I
> > will ask
> > >> the editor
> > > to
> > >> adopt this new text and publish -07.
> > >>
> > >> John (as chair)
> > >>
> > >>> -----Original Message-----
> > >>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> > >>> Sent: 28 February 2011 16:17
> > >>> To: Elwell, John; siprec issue tracker
> > >>> Cc: siprec@ietf.org
> > >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
> > >>> REQ-018 on indications to participants
> > >>>
> > >>> +1
> > >>>
> > >>> Leon
> > >>>
> > >>> -----Original Message-----
> > >>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > >>> Sent: Monday, February 28, 2011 5:35 PM
> > >>> To: Leon Portman; siprec issue tracker
> > >>> Cc: siprec@ietf.org
> > >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
> > >>> REQ-018 on indications to participants
> > >>>
> > >>> There has been little discussion on this, apart from
> support from
> > >>> Leon. The existing text says:
> > >>> "REQ-018 The mechanism MUST provide a means of indicating to the
> > >>>      participants involved in a CS that their session is being
> > > recorded.
> > >>>
> > >>>      Examples include: inject tones into the CS from the
> > SRC, play a
> > >>>      message at the beginning of a session, a visual
> > indicator on a
> > >>>      display, etc."
> > >>>
> > >>> I would suggest the following text:
> > >>> "REQ-018 The mechanism MUST provide a means of
> indicating to the
> > >>> participants involved in a CS that their session is being
> > recorded.
> > >>> Although this can be accomplished using existing SIP
> > techniques for
> > >>> playing an in-band tone, announcement or other media to
> > >>> participants, the mechanism is required also to provide an
> > >>> indication to recording-aware UAs for appropriate
> > rendering at the
> > >>> user interface."
> > >>>
> > >>> John (as individual)
> >
>

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From eckelcu@cisco.com  Thu Mar  3 12:03:46 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 696AC3A69FA for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 12:03:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkfQ+iTS6z4w for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 12:03:44 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 980853A6964 for <siprec@ietf.org>; Thu,  3 Mar 2011 12:03:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=18327; q=dns/txt; s=iport; t=1299182692; x=1300392292; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=kUTgk1cAqoUUFiWc5n+oYtnxsFXQE5fZf4YvO5CYvXc=; b=FNk3NA8lzY3UjhVxA+zYBIZA76gS6TRsYeE1BHmxeBMCnSvGuw9Ato2z FiszYRkEDjNQ14/qX86A7Mv9GhRbSc3nqr94Sh7rzebVXZ5aGytI/Kpdp BxlejTMdqilyWCniA9K4CfOV9xaRp04N2/2WZ6h3e2kGntsxwIDDlUV4W M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvgAALeDb02rR7Hu/2dsb2JhbACYII5HdKIPnCKFYQSFGopa
X-IronPort-AV: E=Sophos;i="4.62,259,1297036800"; d="scan'208";a="338854031"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 03 Mar 2011 20:04:37 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p23K4XmK011455; Thu, 3 Mar 2011 20:04:37 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Mar 2011 12:04:36 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Mar 2011 12:04:35 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB97EC@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <CD2DE94B86B69443B53711F606FCAE120862E4B7@SARUMAN.us.int.genesyslab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018onindications to participants
Thread-Index: AcvZTH+Vs7u6urhTT2Km7kQw3BSzZAAKEM4gAACNCkAAAjkN0AANwi0gAAObWlAAAPSOQAAEo2QA
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com><4D6EFFD0.7070109@cisco.com><07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com><CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C5086D@MCHP058A.global-ad.net> <CD2DE94B86B69443B53711F606FCAE120862E4B7@SARUMAN.us.int.genesyslab.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Dave Smith" <Dave.d.Smith@alcatel-lucent.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Leon Portman" <Leon.Portman@nice.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 03 Mar 2011 20:04:36.0763 (UTC) FILETIME=[38B64EB0:01CBD9DE]
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018onindications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 20:03:46 -0000

Just to clarify, is the decision therefore that Req. #18 will be updated
as proposed by John?=20

> > > >>> I would suggest the following text:
> > > >>> "REQ-018 The mechanism MUST provide a means of
> > indicating to the
> > > >>> participants involved in a CS that their session is being
> > > recorded.
> > > >>> Although this can be accomplished using existing SIP
> > > techniques for
> > > >>> playing an in-band tone, announcement or other media to
> > > >>> participants, the mechanism is required also to provide an
> > > >>> indication to recording-aware UAs for appropriate
> > > rendering at the
> > > >>> user interface."

If I am interpreting this correctly, playing of a tone or an
announcement is an option, not a required form of indication, and some
other indication may be communicated from the SRC to a recording aware
UA that results in the UA producing an indication of recording that is
possibly NOT audible, for example. The choice of the actual rendering of
this indication by the UA is left entirely to the UA. Is that correct?

Thanks,
Charles


> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Dave Smith
> Sent: Thursday, March 03, 2011 9:38 AM
> To: Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification of
REQ-018onindications to participants
>=20
> Thanks for the detailed inputs/explanations.  I agree with the
> recommendations for using REQ-x1 and -x2.
>=20
> Regards,
> Dave
>=20
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 03, 2011 9:17 AM
> To: Leon Portman; Dave Smith; Paul Kyzivat
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification of REQ-018
> onindications to participants
>=20
>=20
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 03 March 2011 15:24
> > To: Elwell, John; Dave Smith; Paul Kyzivat
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > of REQ-018 on indications to participants
> >
> > I agree with your points. Just generic question, do we really
> > need a requirement for mechanism not to prevent something? It
> > can be lot of things like encryption, codec negotiation,
> > ability to transfer call etc.
> [JRE] It is certainly worth questioning whether we need REQ-x1 below.
On
> the one hand, SIPREC is unlikely to specify anything that would
prevent
> this existing capability. In fact it would be quite hard for SIPREC to
> specify something that would prevent the application of tones of
> announcement. Of course, there might be things that could be done at
> deployment time to prevent it (e.g., encryption), but that is not
> SIPREC's problem. However, I would still be inclined to keep it. In
> particular, the Privacy Considerations section has a statement:
> "Therefore this document contains requirements for being able to
notify
> users that a call is being recorded ...". I don't think REQ-x2 alone
> would be sufficient to satisfy that, so if we were to remove REQ-x1 we
> would have to revisit the Privacy Considerations text, which I would
be
> very reluctant to do. So I would like to keep REQ-x1 or something
> similar.
>=20
> John (as individual)
>=20
> >
> > Leon
> >
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Thursday, March 03, 2011 11:14 AM
> > To: Dave Smith; Leon Portman; Paul Kyzivat
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > of REQ-018 on indications to participants
> >
> > Concerning #1, I agree we need to be able to accommodate the
> > different requirements of different regions, countries,
> > business sectors, etc.. Sometimes this might involve playing
> > a tone (e.g., a repeated beep) for the duration of recording,
> > and sometimes this might involve an announcement at the
> > beginning of the session, which will suffice whether or not
> > recording actually takes place during the session. Basically,
> > since not all users will use siprec-aware UAs, particularly
> > PSTN users, the only solution is for the SRC to arrange that
> > the appropriate tone or announcement is injected into the
> > audio stream when required. If the SRC itself is able to do
> > this, we don't need a SIP solution. If the SRC uses a media
> > server to do this, existing SIP/SDP mechanisms will cater for
> > this. I don't anticipate siprec providing new mechanisms for
> > this. It is really just a case of not preventing the use of
> > such mechanisms. How about the following text?
> >
> > "REQ-x1 The mechanism MUST NOT prevent the application of
> > tones or announcements during recording or at the start of a
> > CS to support legal or policy requirements for notifying
> > participants that the call is being recorded or may be recorded."
> >
> > Concerning #2, I see this more of a courtesy thing, rather
> > than a legal thing. Most web-based conference applications
> > give a visual indication of whether the conference is being
> > recorded, achieved using web technology. Where this is not
> > available, it would be useful if siprec-aware UAs in the CS
> > could be advised when recording is taking place so that they
> > can give an appropriate indication to the user. I can see a
> > number of reasons for this:
> > - It provides the possibility of alternative modes for
> > hearing-impaired users.
> > - It gives more precise information in cases where an
> > SRC-injected announcement is given only at the start of the call.
> > - It provides feedback to users who have requested that
> > recording be started / stopped / paused / resumed.
> > - It gives an explicit indication to users who might not
> > understand the meaning of an injected tone.
> > - It is independent of medium type (audio, video, real-time
> > text, fax...).
> > - Potentially its granularity could be on a per medium basis,
> > although I would prefer to leave that as an option for the
> > solution, rather than making a requirement.
> >
> > So how about the following text?
> >
> > "REQ-x2 The mechanism MUST provide a means of indicating to
> > recording-aware UAs whether recording is taking place, for
> > appropriate rendering at the user interface.
> >
> > John (as individual)
> >
> > > >>> participants involved in a CS that their session is being
> > > recorded.
> > > >>> Although this can be accomplished using existing SIP
> > > techniques for
> > > >>> playing an in-band tone, announcement or other media to
> > > >>> participants, the mechanism is required also to provide an
> > > >>> indication to recording-aware UAs for appropriate
> > > rendering at the
> > > >>> user interface."
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
> > > Sent: 03 March 2011 08:29
> > > To: Leon Portman; Paul Kyzivat
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > > of REQ-018 on indications to participants
> > >
> > > I fully agree that an IVR solution (play an announcement) is an
> > > acceptable method that is used today to inform a caller.
> > > I was introducing this req't (#1 below) in order to improve
> > on that.
> > >
> > > Do we absolutely need #1 - probably not.  Do we absolutely need #2
-
> > > probably not also.
> > >
> > > It seems that you are indicating that at least for #1 a solution
is
> > > difficult to provide and would restrict the SRC solution
> > > significantly,
> > > so we should not include it.
> > > I am wondering if that is also the case for #2.
> > >
> > > I don't think we need to mention any "optional" solutions in
> > > the req't.
> > >
> > >
> > > Regards,
> > > Dave
> > >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: Wednesday, March 02, 2011 11:32 PM
> > > To: Paul Kyzivat; Dave Smith
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > of REQ-018
> > > on indications to participants
> > >
> > > I agree with Paul. In the environment where SRC cannot inject
> > > any audio
> > > into the CS, best practice is to have IVR or Voice Portal
> > to make such
> > > announcement.
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf
> > > Of Paul Kyzivat
> > > Sent: Thursday, March 03, 2011 4:41 AM
> > > To: Dave Smith
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > of REQ-018
> > > on indications to participants
> > >
> > >
> > >
> > > On 3/2/2011 7:50 PM, Dave Smith wrote:
> > > > I think the solution should be able to support these
> > > functionalities:
> > > >   1.  playing a repeatable tone to CS participants
> > > >   2.  indicate to recording-aware UAs that recording is
currently
> > > > occurring
> > > >
> > > > Although there may be other things that could be done, I
> > > believe that
> > > > these functionalities are reasonable and sufficient, and would
be
> > > > universally accepted, and that both are required in order
> > > to be able
> > > > to addresss most use cases for indicating to the
> > > participants involved
> > >
> > > > in a CS that their session is being recorded.
> > >
> > > > I am not sure of what the last paragraph of your response
> > is about
> > > > exactly.  A solution to this req't needs to be worked out
> > > in another
> > > > SIPREC Draft; my current thoughts are that since the SRC is
> > > handling
> > > > and in the path of CS UA media and is already communicating
> > > with these
> > >
> > > > UAs, probably an SRC-based solution could be more easily
> > > used to solve
> > >
> > > > this req't.
> > >
> > > I'll try to elaborate:
> > >
> > > I'm not informed of the specific legalities involved, but am of
the
> > > impression that they vary widely. There are certainly
> > > contexts in which
> > > no audible indication need be played. (E.g. call centers,
> > at least in
> > > some places.) In some cases this is dealt with by playing a
general
> > > disclaimer at the beginning of the call, and/or having a
contractual
> > > relationship by which this isn't required.
> > >
> > > In such environments the SRC may not need any way of injecting an
> > > audible indication that recording is going on.
> > >
> > > And there are ways an SRC could get the media for recording
> > that don't
> > > provide a way to inject these tones. (E.g. a media *relay*
> > > may fork the
> > > media, but not be able to alter it.)
> > >
> > > If you combine these things, you can end up with mechanisms for
> > > implementing the SRC function that are *incapable* of
> > satisfying your
> > > proposed requirement, and yet are perfectly suitable for
> > the intended
> > > recording task. I don't want to rule those out as valid
> > > implementations
> > > of siprec.
> > >
> > > I'm fine with having the tone generation as an *option*,
> > and one that
> > > may be absolutely required in *some* markets. If you have a
business
> > > that requires this tone generation then you will buy a product
that
> > > supports it.
> > >
> > >     Thanks,
> > >     Paul
> > >
> > > > Regards,
> > > > Dave
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
On
> > > > Behalf Of Paul Kyzivat
> > > > Sent: Wednesday, March 02, 2011 1:43 PM
> > > > To: siprec@ietf.org
> > > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > > of REQ-018
> > >
> > > > on indications to participants
> > > >
> > > > Dave,
> > > >
> > > > I recognize that there are environments where this audible
> > > tone is a
> > > > requirement. And also environments where it is not, or that
> > > there is
> > > > some *other* requirement.
> > > >
> > > > My question is whether rendering such things is "part of the
> > > > mechanism",
> > > >
> > > > or simply something that some SRCs must be able to do.
> > > >
> > > > Making this part of the mechanism begs the question of "what
> > > mechanism".
> > > >
> > > > There are mechanisms for capturing the media for recording
> > > that do not
> > >
> > > > have a device in place that can insert something into the media.
> > > > Making this a requirement on the mechanism would exclude
> > > using those
> > > > techniques.
> > > >
> > > >   Thanks,
> > > >   Paul
> > > >
> > > > On 3/2/2011 2:57 PM, Dave Smith wrote:
> > > >> I do have an input to this requirement.
> > > >>
> > > >> I agree that the system should be able to provide an
> > indication to
> > > >> recording-aware UAs that recording is currently occurring (for
> > > >> appropriate rendering at the user interface).
> > > >> I also believe that the system should be able to provide a
> > > "tone" to
> > > > CS
> > > >> participants to indicate that recording is currently occurring
> > > >> (specifically, a distinct "beep tone" signal that is repeated
at
> > > > regular
> > > >> intervals during the course of the telephone
> > conversation when the
> > > >> recording device is in use); note that this is consistent with
> > > > existing
> > > >> methods from FCC Rules Regarding Telephone Company Recording of
> > > >> Interstate or International Wireline Telephone Conversations.
> > > >> But I do not see a reason to mention "announcements", or "other
> > > media"
> > > >> in this requirement.
> > > >>
> > > >> Therefore, I recommend the following wording for REQ-018:
> > > >>
> > > >> "REQ-018 The mechanism MUST provide a means of indicating to
the
> > > >> participants involved in a CS that their session is
> > being recorded.
> > > > To
> > > >> support this the mechanism MUST provide a means of playing a
> > > > repeatable
> > > >> tone to CS participants, and also the mechanism MUST
> > > provide a means
> > > > to
> > > >> indicate to recording-aware UAs that recording is
> > > currently occurring
> > >
> > > >> (for appropriate rendering at the user interface)."
> > > >>
> > > >> Regards,
> > > >> Dave
> > > >>
> > > >> -----Original Message-----
> > > >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
On
> > > > Behalf
> > > >> Of Elwell, John
> > > >> Sent: Wednesday, March 02, 2011 3:41 AM
> > > >> To: Leon Portman; siprec issue tracker
> > > >> Cc: siprec@ietf.org
> > > >> Subject: Re: [siprec] Requirements #66 (new): Clarification of
> > > >> REQ-018 on indications to participants
> > > >>
> > > >> In the interests of getting the requirements document
> > finished, I
> > > >> will set a short deadline for this remaining issue. If I
> > have not
> > > >> heard any objections to the proposal below by 2011-03-07 I
> > > will ask
> > > >> the editor
> > > > to
> > > >> adopt this new text and publish -07.
> > > >>
> > > >> John (as chair)
> > > >>
> > > >>> -----Original Message-----
> > > >>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > >>> Sent: 28 February 2011 16:17
> > > >>> To: Elwell, John; siprec issue tracker
> > > >>> Cc: siprec@ietf.org
> > > >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
> > > >>> REQ-018 on indications to participants
> > > >>>
> > > >>> +1
> > > >>>
> > > >>> Leon
> > > >>>
> > > >>> -----Original Message-----
> > > >>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > >>> Sent: Monday, February 28, 2011 5:35 PM
> > > >>> To: Leon Portman; siprec issue tracker
> > > >>> Cc: siprec@ietf.org
> > > >>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
> > > >>> REQ-018 on indications to participants
> > > >>>
> > > >>> There has been little discussion on this, apart from
> > support from
> > > >>> Leon. The existing text says:
> > > >>> "REQ-018 The mechanism MUST provide a means of indicating to
the
> > > >>>      participants involved in a CS that their session is being
> > > > recorded.
> > > >>>
> > > >>>      Examples include: inject tones into the CS from the
> > > SRC, play a
> > > >>>      message at the beginning of a session, a visual
> > > indicator on a
> > > >>>      display, etc."
> > > >>>
> > > >>> I would suggest the following text:
> > > >>> "REQ-018 The mechanism MUST provide a means of
> > indicating to the
> > > >>> participants involved in a CS that their session is being
> > > recorded.
> > > >>> Although this can be accomplished using existing SIP
> > > techniques for
> > > >>> playing an in-band tone, announcement or other media to
> > > >>> participants, the mechanism is required also to provide an
> > > >>> indication to recording-aware UAs for appropriate
> > > rendering at the
> > > >>> user interface."
> > > >>>
> > > >>> John (as individual)
> > >
> >
>=20
>=20
>
------------------------------------------------------------------------
------------------------------
> -------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary
> information of Alcatel-Lucent and/or its affiliated entities. Access
by the intended recipient only is
> authorized. Any liability arising from any party acting, or refraining
from acting, on any information
> contained in this e-mail is hereby excluded. If you are not the
intended recipient, please notify the
> sender immediately, destroy the original transmission and its
attachments and do not disclose the
> contents to any other person, use it for any purpose, or store or copy
the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From eckelcu@cisco.com  Thu Mar  3 13:54:22 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 026743A68CE for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 13:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wn4lvRk9JeK2 for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 13:54:20 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 6E8A13A68B0 for <siprec@ietf.org>; Thu,  3 Mar 2011 13:54:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=9420; q=dns/txt; s=iport; t=1299189328; x=1300398928; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=lrUJ2GMR65xw10E718z0dp72aaV2ZA0tKcEiaii/SJE=; b=aFi455Ta0NaD88PaEt8J7Q5pJOf+UhUXClonCXh8IkuVF8M+5EoxSmTD N44lym3f9Z6qEQETK04GJ/hApSukaE8H4vJhB9+BoMImE/e95ee5Ng3EN vPrnYK+XTJaFYncHHn9/W4GNU3EWyJRkgCbVb9GpR89fqGoach7q/Owh9 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvgAAMacb02rR7Hu/2dsb2JhbACYIY5GdKJsnBiFYQSFGopagxI
X-IronPort-AV: E=Sophos;i="4.62,260,1297036800"; d="scan'208";a="269130150"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 03 Mar 2011 21:55:28 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p23LtS3o012389; Thu, 3 Mar 2011 21:55:28 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Mar 2011 13:55:28 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Mar 2011 13:55:26 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB987B@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <059AF07365DC474393A19A3AF187DF7406BAE5C6@NAHALD.us.int.genesyslab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
Thread-Index: AcvYdoq1VttmMUOCSj+I/EBWiH/OmQAgjaaAADyUJVA=
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com><4D6D3FE5.9000902@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com><4D6D98DC.8080008@cisco.com> <059AF07365DC474393A19A3AF187DF7406BAE5C6@NAHALD.us.int.genesyslab.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Henry Lum" <Henry.Lum@alcatel-lucent.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 03 Mar 2011 21:55:28.0374 (UTC) FILETIME=[B5619960:01CBD9ED]
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 21:54:22 -0000

I think it is better to stick to using UPDATE and not introduce a need
to use INFO. I would also expect that using re-INVITE instead of UPDATE,
though not explicitly recommended, would work as well. What drives this
is the inclusion of the newly defined tags and the actual metadata.

Section 5 reads,
  =20
   The SRC must be able to accept re-INVITE from SRS with the updated
   SDP as part of the session timer mechanism.

What is the purpose of stating this? I agree the SRC needs to be able to
accept a re-INVITE with updated or non-updated SDP from the SRS. It also
needs to be able to receive an UPDATE with updated or non-updated SDP.
This appears to me to be independent of using session timer, and I do
not believe we are mandating support for session timer either.

In section 6.2, what does the "record" attribute and the defined
"indication" attribute give us that we do not already have using
sendonly and inactive, where off/pause maps to inactive and on maps to
sendonly?

In section 6.3, recording preference, do we really need pause and
resume? I am thinking record and norecord may be sufficient.

Cheers,
Charles


> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Henry Lum
> Sent: Wednesday, March 02, 2011 8:45 AM
> To: Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] FW: New VersionNotificationfor
draft-portman-siprec-protocol-03
>=20
> I don't feel strongly too about using INFO so I am open to using
UPDATE
> if the group feels that it is okay for SRC/SRS to deal with the
> consequences of UPDATE collision.
>=20
> Henry
>=20
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: Tuesday, March 01, 2011 8:10 PM
> > To: Henry Lum
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] FW: New Version Notificationfor draft-portman-
> > siprec-protocol-03
> >
> >
> >
> > On 3/1/2011 2:32 PM, Henry Lum wrote:
> > > When there is an UPDATE transaction collision, you will have to
make
> > > both SRC and SRS to wait a while before being able to send UPDATE
> > again.
> > > Since SRC is normally the side initiating the SIP dialog, it is
the
> > > owner of the Call-ID and will come second after the SRS has a
chance
> > to
> > > resend the UPDATE. In that case, does the SRC keep the existing
> > UPDATE
> > > or send a new snapshot as requested by the SRS? The SRC also need
to
> > > keep track of metadata changes while waiting for the timer. I
worry
> > that
> > > it will make the solution more complicated than just using an INFO
> > for
> > > snapshot request and minimize the collision problem.
> >
> > OK, collision on update is a *possibility*.
> > I guess the question is whether that justifies implementing an
> entirely
> > different mechanism just for the rare error message.
> >
> > I expect that the likelihood of collision is pretty slim, given that
> > messages from the SRS to the SRC will be very infrequent, and if the
> > message comes shortly after a metadata is received from the SRC,
there
> > may be little likelihood that the SRC will be sending more metadata
so
> > soon. And even if we don't use UPDATE for this, the SRC, like any
UA,
> > needs to be prepared to cope with a collision of this sort.
> >
> > But I don't feel *too* strongly about this.
> >
> > 	Thanks,
> > 	Paul
> >
> > > Regards,
> > > Henry
> > >
> > >> -----Original Message-----
> > >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > >> Behalf Of Paul Kyzivat
> > >> Sent: Tuesday, March 01, 2011 1:50 PM
> > >> To: siprec@ietf.org
> > >> Subject: Re: [siprec] FW: New Version Notificationfor
> draft-portman-
> > >> siprec-protocol-03
> > >>
> > >> Thanks Henry.
> > >>
> > >> One comment/question:
> > >>
> > >> Is there a reason to use an Info package for Requesting for
> metadata
> > >> snapshot? Since we are already defining c-d recording-session and
> > >> passing bodies in invite/update for it, is there a reason not to
> use
> > >> the
> > >> same mechanism to send error notifications/snapshop requests?
> > >>
> > >> (I'm thinking just using a different content-type for this, and
of
> > >> course sending it from SRS to SRC.)
> > >>
> > >> Also, we could consider permitting (not requiring) this in the
> > >> responses
> > >> to the messages containing metadata.
> > >>
> > >> 	Thanks,
> > >> 	Paul
> > >>
> > >>
> > >> On 3/1/2011 12:13 PM, Henry Lum wrote:
> > >>> A new version has been submitted to address the outstanding
issues
> > >> and include extensions for the new wording for REQ-017 and
REQ-018.
> > >>>
> > >>> https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
> > >>>
> > >>> Regards,
> > >>> Henry
> > >>>
> > >>> -----Original Message-----
> > >>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> > >>> Sent: Tuesday, March 01, 2011 12:09 PM
> > >>> To: Henry Lum
> > >>> Cc: leon.portman@nice.com; alan.b.johnston@gmail.com;
> > >> andrew.hutton@siemens-enterprise.com
> > >>> Subject: New Version Notification for draft-portman-siprec-
> > protocol-
> > >> 03
> > >>>
> > >>>
> > >>> A new version of I-D, draft-portman-siprec-protocol-03.txt has
> been
> > >> successfully submitted by Henry Lum and posted to the IETF
> > repository.
> > >>>
> > >>> Filename:	 draft-portman-siprec-protocol
> > >>> Revision:	 03
> > >>> Title:		 The SIP-based Media Recording Protocol (SIPREC)
> > >>> Creation_date:	 2011-03-01
> > >>> WG ID:		 Independent Submission
> > >>> Number_of_pages: 20
> > >>>
> > >>> Abstract:
> > >>> SIPREC Session Recording Protocol is used for establishing
> > recording
> > >>> session and reporting of the metadata of the communication
> session.
> > >>>
> > >>> This document specifies the SIPREC Protocol (SIPREC).  SIPREC is
> > > used
> > >>> between Session Recording Client (SRC) and Session Recording
> Server
> > >>> (SRS).
> > >>>
> > >>>
> > >>>
> > >>> The IETF Secretariat.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >
> ---------------------------------------------------------------------
> > >> ----------------------------------------------
> > >>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > >> contain confidential and proprietary information of
Alcatel-Lucent
> > >> and/or its affiliated entities. Access by the intended recipient
> > only
> > >> is authorized. Any liability arising from any party acting, or
> > >> refraining from acting, on any information contained in this
e-mail
> > is
> > >> hereby excluded. If you are not the intended recipient, please
> > notify
> > >> the sender immediately, destroy the original transmission and its
> > >> attachments and do not disclose the contents to any other person,
> > use
> > >> it for any purpose, or store or copy the information in any
medium.
> > >> Copyright in this e-mail and any attachments belongs to Alcatel-
> > Lucent
> > >> and/or its affiliated entities.
> > >>>
> > >>> _______________________________________________
> > >>> 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
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > ----------------------------------------------
> > > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > contain confidential and proprietary information of Alcatel-Lucent
> > and/or its affiliated entities. Access by the intended recipient
only
> > is authorized. Any liability arising from any party acting, or
> > refraining from acting, on any information contained in this e-mail
is
> > hereby excluded. If you are not the intended recipient, please
notify
> > the sender immediately, destroy the original transmission and its
> > attachments and do not disclose the contents to any other person,
use
> > it for any purpose, or store or copy the information in any medium.
> > Copyright in this e-mail and any attachments belongs to
Alcatel-Lucent
> > and/or its affiliated entities.
> > >
> > >
>=20
>=20
>
------------------------------------------------------------------------
------------------------------
> -------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary
> information of Alcatel-Lucent and/or its affiliated entities. Access
by the intended recipient only is
> authorized. Any liability arising from any party acting, or refraining
from acting, on any information
> contained in this e-mail is hereby excluded. If you are not the
intended recipient, please notify the
> sender immediately, destroy the original transmission and its
attachments and do not disclose the
> contents to any other person, use it for any purpose, or store or copy
the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From eckelcu@cisco.com  Thu Mar  3 15:40:32 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99E223A6872 for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 15:40:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mw1axiUfkU7a for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 15:40:31 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 364DA3A6816 for <siprec@ietf.org>; Thu,  3 Mar 2011 15:40:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=7040; q=dns/txt; s=iport; t=1299195699; x=1300405299; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=1gEsJu/aCScRpvAOuPbCX+vJmWLLqYVpeHoybiVh+Rk=; b=QPXI1+Br9uvLE/RtRYkoCZ0pSRN2t+boR5HZoWQCeunzPZyQnAvXT1CF K7HWDEEyia7ohVmjsh1thtrEp57kuSoI74Be1zKFv2UZ4BdpBi7uZHlAm elgpqTW20HCIV3xWnMOGxKzMc1uB0+NikLDdQRphruMvpkJch6Jh1iMVR 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvgAABe2b02rR7Hu/2dsb2JhbACYIY5GdKImnBKCfoJjBIUailo
X-IronPort-AV: E=Sophos;i="4.62,261,1297036800"; d="scan'208";a="273403865"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 03 Mar 2011 23:41:39 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p23Nfdir013159; Thu, 3 Mar 2011 23:41:39 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Mar 2011 15:41:39 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Mar 2011 15:41:38 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB991A@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904A63B8A@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Synchronous vs Asynchronous Error handling
Thread-Index: AcvXW03ON+nfMVCWQ8GPwSpOJaYBQQABrURQAABGHZAAXlVssABHvlPg
References: <A11921905DA1564D9BCF64A6430A62390293A665@XMB-BGL-411.cisco.com><4D67EC69.7080507@cisco.com><059AF07365DC474393A19A3AF187DF7406BADEA6@NAHALD.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2BAA742@MCHP058A.global-ad.net><4D6BBDAE.3020808@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE02F@NAHALD.us.int.genesyslab.com><07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A623904A63B8A@XMB-BGL-411.cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, "Henry Lum" <Henry.Lum@alcatel-lucent.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 03 Mar 2011 23:41:39.0556 (UTC) FILETIME=[8AE6D240:01CBD9FC]
Cc: siprec@ietf.org
Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Mar 2011 23:40:32 -0000

Hi Partha,

I think we need both. If the error is detected in SDP processing,
handling it in the SIP response synchronously makes sense. If the error
is detected in the metadata processing, it would ideally be handled in
the SIP response synchronously, but it may result in a subsequent
request being sent to indicate and/or recover from the error. Errors may
also be encountered independent of any SIP request processing, and those
will need to be handled asynchronously.
So I think we need both, and how much of the XML to process
synchronously is up to the answerer. Ideally we will structure the XML
such that it is as clear and efficient as possible to identify the XML
that directly impacts the SDP. This will facilitate synchronous
responses.

Cheers,
Charles=20

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Parthasarathi R (partr)
> Sent: Wednesday, March 02, 2011 5:48 AM
> To: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: [siprec] Synchronous vs Asynchronous Error handling
>=20
> Hi all,
>=20
> Another issue discussed as part of the below mail thread is whether
> metadata (XML+SDP) error has to be responded synchronously (SIP
> Request/[SIP provisional response]/SIP Response) or asynchronously(SIP
> Request/SIP Response/SIP Error request/SIP Error response).
>=20
> Synchronous Error handling:
> From SRC perspective, synchronous error handling is simple to
implement
> as there is no extra context or state to be maintained about the
earlier
> SIP transactions.
>=20
> In SRS, SDP Metadata portion *MUST* be processed in synchronously to
> meet offer/answer model requirement. Now the question is whether XML
> takes so much of a time wherein the error MUST be handled
asynchronous?
> The simple SRS will be able to send provisional response and respond
> back final response once the complete XML check is done. My reasoning
is
> so because B2BUA normally handles INVITE/RE-INVITE in a way that send
> (100 trying) provisional response to the incoming dialog side, send
> INVITE/RE-INVITE to the outgoing dialog side which may take upto 32
sec
> delay to respond and forwards 200 OK to incoming dialog side once it
is
> received from outgoing dialog side and it is well working deployed
> model. Please let me know in which situation this mechanism has issues
> specific to SIPREC & XML.
>=20
> Asynchronous Error handling:
> Here as well in SRS, SDP Metadata portion *MUST* be processed in
> synchronously to meet offer/answer model requirement.
>=20
> Two cases exists from SRC perspective.
> 1) In case the sequence number has to be maintained by SRC for
> asynchronous error handling, then it *MAY* require SRC to maintain the
> earlier transaction which is overkill as SRC will not keep track or
> record its previous state.
>=20
> 2) In most of the scenario, it is not possible to re-record but it is
> only possible to re-sync. In case the motivation of asynchronous error
> is to re-sync metadata by SRS to SRC, it is very similar to SRS
> requesting for current complete metadata (SDP+XML) from SRC. On
> receiving re-sync request, SRC has to trigger the complete metadata
> towards SRS. The sequence number from SRS *MAY* be used for logging
> purpose if required.
>=20
> Please let me know which one of the above asynchronous behavior is
> expected from SRC. Also, instead of asynchronous error message, do you
> wish to create re-sync request mechanism from SRS which may be used
for
> error or other purpose as well.
>=20
> Thanks
> Partha
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf
> Of Leon Portman
> Sent: Monday, February 28, 2011 9:48 PM
> To: Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Metadata XML document error representation
> forwhole doc or for portion of doc
>=20
> +1
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf
> Of Henry Lum
> Sent: Monday, February 28, 2011 6:13 PM
> To: Paul Kyzivat; Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Metadata XML document error representation for
> whole doc or for portion of doc
>=20
>=20
>=20
> > >> We are also thinking of providing the SRS with a mechanism to
> > >> request the SRC to ask for the current snapshot
> > so
> > >> that the SRC/SRS can reset the states in the case where SRS is in
a
>=20
> > >> really bad state. By doing so, we may be able to avoid providing
> > nack
> > >> responses and avoid using a chatty protocol.
> > > [JRE] Yes, and the request to resend full metadata could
optionally
> > include some sort of error report that gave rise to the request.
That
> > error report could, for example, include the sequence number of the
> > metadata update that was found to be in error.
> >
> > That is sort of what I had in mind about getting the two sides in
> sync.
> > But we will have to think more about exactly what it means.
> > At best I think it will describe the *current* state of things in
this
>=20
> > RS, without regard to what has happened in the past.
> >
> > Even that may present some technical challenges. But we should keep
> > this desire in mind.
>=20
> [[hlum]] I agree it would be reasonable for the SRC to send the
current
> state as a snapshot and forget what happened previously. The
subsequent
> sequence numbers only refers to the current snapshot rather than the
> original one, so in a way we are resetting the sequence number.
>=20
>=20
>
------------------------------------------------------------------------
> -------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
> confidential and proprietary information of Alcatel-Lucent and/or its
> affiliated entities. Access by the intended recipient only is
> authorized. Any liability arising from any party acting, or refraining
> from acting, on any information contained in this e-mail is hereby
> excluded. If you are not the intended recipient, please notify the
> sender immediately, destroy the original transmission and its
> attachments and do not disclose the contents to any other person, use
it
> for any purpose, or store or copy the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
> and/or its affiliated entities.
>=20
> _______________________________________________
> 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

From pkyzivat@cisco.com  Thu Mar  3 17:35:55 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A90673A65A5 for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 17:35:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.233
X-Spam-Level: 
X-Spam-Status: No, score=-110.233 tagged_above=-999 required=5 tests=[AWL=-0.234, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1XUQL2tgUzF for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 17:35:54 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id BB3453A6855 for <siprec@ietf.org>; Thu,  3 Mar 2011 17:35:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=7798; q=dns/txt; s=iport; t=1299202622; x=1300412222; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=bfJetsAPweJQEXNhGDzebHQNIIMoWiLstLkOM3Ers+0=; b=ewnKS8oGhCyoS1xvHTp4NrQzMH9FvhFZclES7+iDU8kuSXVy3kC6/ZKd 0PlTUDiu98cS/SGxkf5AEDO9KqhYkUclHGq9ACcoDUxbkDXzTDWamHdr2 JHrMyK2BIOifOsKIY48F8ibLejXXEA0AYW7p1LeeZIHOolLw5IcDuSjH/ Y=;
X-IronPort-AV: E=Sophos;i="4.62,261,1297036800"; d="scan'208";a="222455311"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 04 Mar 2011 01:37:02 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p241b1QW017928; Fri, 4 Mar 2011 01:37:01 GMT
Message-ID: <4D70423D.7030202@cisco.com>
Date: Thu, 03 Mar 2011 20:37:01 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <A11921905DA1564D9BCF64A6430A62390293A665@XMB-BGL-411.cisco.com><4D67EC69.7080507@cisco.com><059AF07365DC474393A19A3AF187DF7406BADEA6@NAHALD.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2BAA742@MCHP058A.global-ad.net><4D6BBDAE.3020808@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE02F@NAHALD.us.int.genesyslab.com><07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A623904A63B8A@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB991A@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB991A@xmb-sjc-234.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Leon Portman <Leon.Portman@nice.com>, Henry Lum <Henry.Lum@alcatel-lucent.com>, siprec@ietf.org
Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 01:35:55 -0000

Charles,

Its my expectation that none of the metadata *need* be processed in 
order to answer an sdp offer. However the sdp will typically be required 
to supplement the metadata processing. So it likely will be necessary to 
queue the xml+sdp for later processing as metadata.

One might want to make decisions about how to construct the answer (e.g. 
whether to accept or reject a media stream) based on the xml metadata. 
If one is capable of doing all the processing synchronously in order to 
do so, go for it. But nobody should be forced to do that.

	Thanks,
	Paul

On 3/3/2011 6:41 PM, Charles Eckel (eckelcu) wrote:
> Hi Partha,
>
> I think we need both. If the error is detected in SDP processing,
> handling it in the SIP response synchronously makes sense. If the error
> is detected in the metadata processing, it would ideally be handled in
> the SIP response synchronously, but it may result in a subsequent
> request being sent to indicate and/or recover from the error. Errors may
> also be encountered independent of any SIP request processing, and those
> will need to be handled asynchronously.
> So I think we need both, and how much of the XML to process
> synchronously is up to the answerer. Ideally we will structure the XML
> such that it is as clear and efficient as possible to identify the XML
> that directly impacts the SDP. This will facilitate synchronous
> responses.
>
> Cheers,
> Charles
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Parthasarathi R (partr)
>> Sent: Wednesday, March 02, 2011 5:48 AM
>> To: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
>> Cc: siprec@ietf.org
>> Subject: [siprec] Synchronous vs Asynchronous Error handling
>>
>> Hi all,
>>
>> Another issue discussed as part of the below mail thread is whether
>> metadata (XML+SDP) error has to be responded synchronously (SIP
>> Request/[SIP provisional response]/SIP Response) or asynchronously(SIP
>> Request/SIP Response/SIP Error request/SIP Error response).
>>
>> Synchronous Error handling:
>>  From SRC perspective, synchronous error handling is simple to
> implement
>> as there is no extra context or state to be maintained about the
> earlier
>> SIP transactions.
>>
>> In SRS, SDP Metadata portion *MUST* be processed in synchronously to
>> meet offer/answer model requirement. Now the question is whether XML
>> takes so much of a time wherein the error MUST be handled
> asynchronous?
>> The simple SRS will be able to send provisional response and respond
>> back final response once the complete XML check is done. My reasoning
> is
>> so because B2BUA normally handles INVITE/RE-INVITE in a way that send
>> (100 trying) provisional response to the incoming dialog side, send
>> INVITE/RE-INVITE to the outgoing dialog side which may take upto 32
> sec
>> delay to respond and forwards 200 OK to incoming dialog side once it
> is
>> received from outgoing dialog side and it is well working deployed
>> model. Please let me know in which situation this mechanism has issues
>> specific to SIPREC&  XML.
>>
>> Asynchronous Error handling:
>> Here as well in SRS, SDP Metadata portion *MUST* be processed in
>> synchronously to meet offer/answer model requirement.
>>
>> Two cases exists from SRC perspective.
>> 1) In case the sequence number has to be maintained by SRC for
>> asynchronous error handling, then it *MAY* require SRC to maintain the
>> earlier transaction which is overkill as SRC will not keep track or
>> record its previous state.
>>
>> 2) In most of the scenario, it is not possible to re-record but it is
>> only possible to re-sync. In case the motivation of asynchronous error
>> is to re-sync metadata by SRS to SRC, it is very similar to SRS
>> requesting for current complete metadata (SDP+XML) from SRC. On
>> receiving re-sync request, SRC has to trigger the complete metadata
>> towards SRS. The sequence number from SRS *MAY* be used for logging
>> purpose if required.
>>
>> Please let me know which one of the above asynchronous behavior is
>> expected from SRC. Also, instead of asynchronous error message, do you
>> wish to create re-sync request mechanism from SRS which may be used
> for
>> error or other purpose as well.
>>
>> Thanks
>> Partha
>>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf
>> Of Leon Portman
>> Sent: Monday, February 28, 2011 9:48 PM
>> To: Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Metadata XML document error representation
>> forwhole doc or for portion of doc
>>
>> +1
>>
>> Leon
>>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf
>> Of Henry Lum
>> Sent: Monday, February 28, 2011 6:13 PM
>> To: Paul Kyzivat; Elwell, John
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Metadata XML document error representation for
>> whole doc or for portion of doc
>>
>>
>>
>>>>> We are also thinking of providing the SRS with a mechanism to
>>>>> request the SRC to ask for the current snapshot
>>> so
>>>>> that the SRC/SRS can reset the states in the case where SRS is in
> a
>>
>>>>> really bad state. By doing so, we may be able to avoid providing
>>> nack
>>>>> responses and avoid using a chatty protocol.
>>>> [JRE] Yes, and the request to resend full metadata could
> optionally
>>> include some sort of error report that gave rise to the request.
> That
>>> error report could, for example, include the sequence number of the
>>> metadata update that was found to be in error.
>>>
>>> That is sort of what I had in mind about getting the two sides in
>> sync.
>>> But we will have to think more about exactly what it means.
>>> At best I think it will describe the *current* state of things in
> this
>>
>>> RS, without regard to what has happened in the past.
>>>
>>> Even that may present some technical challenges. But we should keep
>>> this desire in mind.
>>
>> [[hlum]] I agree it would be reasonable for the SRC to send the
> current
>> state as a snapshot and forget what happened previously. The
> subsequent
>> sequence numbers only refers to the current snapshot rather than the
>> original one, so in a way we are resetting the sequence number.
>>
>>
>>
> ------------------------------------------------------------------------
>> -------------------------------------------
>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
>> confidential and proprietary information of Alcatel-Lucent and/or its
>> affiliated entities. Access by the intended recipient only is
>> authorized. Any liability arising from any party acting, or refraining
>> from acting, on any information contained in this e-mail is hereby
>> excluded. If you are not the intended recipient, please notify the
>> sender immediately, destroy the original transmission and its
>> attachments and do not disclose the contents to any other person, use
> it
>> for any purpose, or store or copy the information in any medium.
>> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
>> and/or its affiliated entities.
>>
>> _______________________________________________
>> 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
>

From john.elwell@siemens-enterprise.com  Thu Mar  3 23:38:59 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 107E03A6955 for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 23:38:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.617
X-Spam-Level: 
X-Spam-Status: No, score=-102.617 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tl5mmKLFwTOL for <siprec@core3.amsl.com>; Thu,  3 Mar 2011 23:38:57 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 6FF7F3A6965 for <siprec@ietf.org>; Thu,  3 Mar 2011 23:38:56 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3619993; Fri, 4 Mar 2011 08:39:45 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id B9EE71EB82AB; Fri,  4 Mar 2011 08:39:45 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 4 Mar 2011 08:39:45 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Dave Smith <Dave.d.Smith@alcatel-lucent.com>, Leon Portman <Leon.Portman@nice.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
Date: Fri, 4 Mar 2011 08:39:43 +0100
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018onindications to participants
Thread-Index: AcvZTH+Vs7u6urhTT2Km7kQw3BSzZAAKEM4gAACNCkAAAjkN0AANwi0gAAObWlAAAPSOQAAEo2QAABjA5SA=
Message-ID: <A444A0F8084434499206E78C106220CA06C2C5096C@MCHP058A.global-ad.net>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com><4D6EFFD0.7070109@cisco.com><07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com><CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C5086D@MCHP058A.global-ad.net> <CD2DE94B86B69443B53711F606FCAE120862E4B7@SARUMAN.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB97EC@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB97EC@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018onindications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 07:38:59 -0000

Charles,

The text you quote is not the latest proposal. You will see below a later p=
roposal for two separate requirements REQ-x1 and REQ-x2 to replace REQ-018.=
 I understand Dave was agreeing with those new requirements. I reproduce th=
e new proposal here:

"REQ-x1 The mechanism MUST NOT prevent the application of tones or announce=
ments during recording or at the start of a CS to support legal or policy r=
equirements for notifying participants that the call is being recorded or m=
ay be recorded."

"REQ-x2 The mechanism MUST provide a means of indicating to recording-aware=
 UAs whether recording is taking place, for appropriate rendering at the us=
er interface.

John


> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: 03 March 2011 20:05
> To: Dave Smith; Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification
> of REQ-018onindications to participants
>
> Just to clarify, is the decision therefore that Req. #18 will
> be updated
> as proposed by John?
>
> > > > >>> I would suggest the following text:
> > > > >>> "REQ-018 The mechanism MUST provide a means of
> > > indicating to the
> > > > >>> participants involved in a CS that their session is being
> > > > recorded.
> > > > >>> Although this can be accomplished using existing SIP
> > > > techniques for
> > > > >>> playing an in-band tone, announcement or other media to
> > > > >>> participants, the mechanism is required also to provide an
> > > > >>> indication to recording-aware UAs for appropriate
> > > > rendering at the
> > > > >>> user interface."
>
> If I am interpreting this correctly, playing of a tone or an
> announcement is an option, not a required form of indication, and some
> other indication may be communicated from the SRC to a recording aware
> UA that results in the UA producing an indication of recording that is
> possibly NOT audible, for example. The choice of the actual
> rendering of
> this indication by the UA is left entirely to the UA. Is that correct?
>
> Thanks,
> Charles
>
>
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Dave Smith
> > Sent: Thursday, March 03, 2011 9:38 AM
> > To: Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Requirements #66 (new): Clarification of
> REQ-018onindications to participants
> >
> > Thanks for the detailed inputs/explanations.  I agree with the
> > recommendations for using REQ-x1 and -x2.
> >
> > Regards,
> > Dave
> >
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Thursday, March 03, 2011 9:17 AM
> > To: Leon Portman; Dave Smith; Paul Kyzivat
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Requirements #66 (new): Clarification
> of REQ-018
> > onindications to participants
> >
> >
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 03 March 2011 15:24
> > > To: Elwell, John; Dave Smith; Paul Kyzivat
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > > of REQ-018 on indications to participants
> > >
> > > I agree with your points. Just generic question, do we really
> > > need a requirement for mechanism not to prevent something? It
> > > can be lot of things like encryption, codec negotiation,
> > > ability to transfer call etc.
> > [JRE] It is certainly worth questioning whether we need
> REQ-x1 below.
> On
> > the one hand, SIPREC is unlikely to specify anything that would
> prevent
> > this existing capability. In fact it would be quite hard
> for SIPREC to
> > specify something that would prevent the application of tones of
> > announcement. Of course, there might be things that could be done at
> > deployment time to prevent it (e.g., encryption), but that is not
> > SIPREC's problem. However, I would still be inclined to keep it. In
> > particular, the Privacy Considerations section has a statement:
> > "Therefore this document contains requirements for being able to
> notify
> > users that a call is being recorded ...". I don't think REQ-x2 alone
> > would be sufficient to satisfy that, so if we were to
> remove REQ-x1 we
> > would have to revisit the Privacy Considerations text, which I would
> be
> > very reluctant to do. So I would like to keep REQ-x1 or something
> > similar.
> >
> > John (as individual)
> >
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > Sent: Thursday, March 03, 2011 11:14 AM
> > > To: Dave Smith; Leon Portman; Paul Kyzivat
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > > of REQ-018 on indications to participants
> > >
> > > Concerning #1, I agree we need to be able to accommodate the
> > > different requirements of different regions, countries,
> > > business sectors, etc.. Sometimes this might involve playing
> > > a tone (e.g., a repeated beep) for the duration of recording,
> > > and sometimes this might involve an announcement at the
> > > beginning of the session, which will suffice whether or not
> > > recording actually takes place during the session. Basically,
> > > since not all users will use siprec-aware UAs, particularly
> > > PSTN users, the only solution is for the SRC to arrange that
> > > the appropriate tone or announcement is injected into the
> > > audio stream when required. If the SRC itself is able to do
> > > this, we don't need a SIP solution. If the SRC uses a media
> > > server to do this, existing SIP/SDP mechanisms will cater for
> > > this. I don't anticipate siprec providing new mechanisms for
> > > this. It is really just a case of not preventing the use of
> > > such mechanisms. How about the following text?
> > >
> > > "REQ-x1 The mechanism MUST NOT prevent the application of
> > > tones or announcements during recording or at the start of a
> > > CS to support legal or policy requirements for notifying
> > > participants that the call is being recorded or may be recorded."
> > >
> > > Concerning #2, I see this more of a courtesy thing, rather
> > > than a legal thing. Most web-based conference applications
> > > give a visual indication of whether the conference is being
> > > recorded, achieved using web technology. Where this is not
> > > available, it would be useful if siprec-aware UAs in the CS
> > > could be advised when recording is taking place so that they
> > > can give an appropriate indication to the user. I can see a
> > > number of reasons for this:
> > > - It provides the possibility of alternative modes for
> > > hearing-impaired users.
> > > - It gives more precise information in cases where an
> > > SRC-injected announcement is given only at the start of the call.
> > > - It provides feedback to users who have requested that
> > > recording be started / stopped / paused / resumed.
> > > - It gives an explicit indication to users who might not
> > > understand the meaning of an injected tone.
> > > - It is independent of medium type (audio, video, real-time
> > > text, fax...).
> > > - Potentially its granularity could be on a per medium basis,
> > > although I would prefer to leave that as an option for the
> > > solution, rather than making a requirement.
> > >
> > > So how about the following text?
> > >
> > > "REQ-x2 The mechanism MUST provide a means of indicating to
> > > recording-aware UAs whether recording is taking place, for
> > > appropriate rendering at the user interface.
> > >
> > > John (as individual)
> > >
> > > > >>> participants involved in a CS that their session is being
> > > > recorded.
> > > > >>> Although this can be accomplished using existing SIP
> > > > techniques for
> > > > >>> playing an in-band tone, announcement or other media to
> > > > >>> participants, the mechanism is required also to provide an
> > > > >>> indication to recording-aware UAs for appropriate
> > > > rendering at the
> > > > >>> user interface."
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
> > > > Sent: 03 March 2011 08:29
> > > > To: Leon Portman; Paul Kyzivat
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > > > of REQ-018 on indications to participants
> > > >
> > > > I fully agree that an IVR solution (play an announcement) is an
> > > > acceptable method that is used today to inform a caller.
> > > > I was introducing this req't (#1 below) in order to improve
> > > on that.
> > > >
> > > > Do we absolutely need #1 - probably not.  Do we
> absolutely need #2
> -
> > > > probably not also.
> > > >
> > > > It seems that you are indicating that at least for #1 a solution
> is
> > > > difficult to provide and would restrict the SRC solution
> > > > significantly,
> > > > so we should not include it.
> > > > I am wondering if that is also the case for #2.
> > > >
> > > > I don't think we need to mention any "optional" solutions in
> > > > the req't.
> > > >
> > > >
> > > > Regards,
> > > > Dave
> > > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: Wednesday, March 02, 2011 11:32 PM
> > > > To: Paul Kyzivat; Dave Smith
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > > of REQ-018
> > > > on indications to participants
> > > >
> > > > I agree with Paul. In the environment where SRC cannot inject
> > > > any audio
> > > > into the CS, best practice is to have IVR or Voice Portal
> > > to make such
> > > > announcement.
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org] On Behalf
> > > > Of Paul Kyzivat
> > > > Sent: Thursday, March 03, 2011 4:41 AM
> > > > To: Dave Smith
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > > of REQ-018
> > > > on indications to participants
> > > >
> > > >
> > > >
> > > > On 3/2/2011 7:50 PM, Dave Smith wrote:
> > > > > I think the solution should be able to support these
> > > > functionalities:
> > > > >   1.  playing a repeatable tone to CS participants
> > > > >   2.  indicate to recording-aware UAs that recording is
> currently
> > > > > occurring
> > > > >
> > > > > Although there may be other things that could be done, I
> > > > believe that
> > > > > these functionalities are reasonable and sufficient, and would
> be
> > > > > universally accepted, and that both are required in order
> > > > to be able
> > > > > to addresss most use cases for indicating to the
> > > > participants involved
> > > >
> > > > > in a CS that their session is being recorded.
> > > >
> > > > > I am not sure of what the last paragraph of your response
> > > is about
> > > > > exactly.  A solution to this req't needs to be worked out
> > > > in another
> > > > > SIPREC Draft; my current thoughts are that since the SRC is
> > > > handling
> > > > > and in the path of CS UA media and is already communicating
> > > > with these
> > > >
> > > > > UAs, probably an SRC-based solution could be more easily
> > > > used to solve
> > > >
> > > > > this req't.
> > > >
> > > > I'll try to elaborate:
> > > >
> > > > I'm not informed of the specific legalities involved, but am of
> the
> > > > impression that they vary widely. There are certainly
> > > > contexts in which
> > > > no audible indication need be played. (E.g. call centers,
> > > at least in
> > > > some places.) In some cases this is dealt with by playing a
> general
> > > > disclaimer at the beginning of the call, and/or having a
> contractual
> > > > relationship by which this isn't required.
> > > >
> > > > In such environments the SRC may not need any way of
> injecting an
> > > > audible indication that recording is going on.
> > > >
> > > > And there are ways an SRC could get the media for recording
> > > that don't
> > > > provide a way to inject these tones. (E.g. a media *relay*
> > > > may fork the
> > > > media, but not be able to alter it.)
> > > >
> > > > If you combine these things, you can end up with mechanisms for
> > > > implementing the SRC function that are *incapable* of
> > > satisfying your
> > > > proposed requirement, and yet are perfectly suitable for
> > > the intended
> > > > recording task. I don't want to rule those out as valid
> > > > implementations
> > > > of siprec.
> > > >
> > > > I'm fine with having the tone generation as an *option*,
> > > and one that
> > > > may be absolutely required in *some* markets. If you have a
> business
> > > > that requires this tone generation then you will buy a product
> that
> > > > supports it.
> > > >
> > > >     Thanks,
> > > >     Paul
> > > >
> > > > > Regards,
> > > > > Dave
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> On
> > > > > Behalf Of Paul Kyzivat
> > > > > Sent: Wednesday, March 02, 2011 1:43 PM
> > > > > To: siprec@ietf.org
> > > > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > > > of REQ-018
> > > >
> > > > > on indications to participants
> > > > >
> > > > > Dave,
> > > > >
> > > > > I recognize that there are environments where this audible
> > > > tone is a
> > > > > requirement. And also environments where it is not, or that
> > > > there is
> > > > > some *other* requirement.
> > > > >
> > > > > My question is whether rendering such things is "part of the
> > > > > mechanism",
> > > > >
> > > > > or simply something that some SRCs must be able to do.
> > > > >
> > > > > Making this part of the mechanism begs the question of "what
> > > > mechanism".
> > > > >
> > > > > There are mechanisms for capturing the media for recording
> > > > that do not
> > > >
> > > > > have a device in place that can insert something into
> the media.
> > > > > Making this a requirement on the mechanism would exclude
> > > > using those
> > > > > techniques.
> > > > >
> > > > >   Thanks,
> > > > >   Paul
> > > > >
> > > > > On 3/2/2011 2:57 PM, Dave Smith wrote:
> > > > >> I do have an input to this requirement.
> > > > >>
> > > > >> I agree that the system should be able to provide an
> > > indication to
> > > > >> recording-aware UAs that recording is currently
> occurring (for
> > > > >> appropriate rendering at the user interface).
> > > > >> I also believe that the system should be able to provide a
> > > > "tone" to
> > > > > CS
> > > > >> participants to indicate that recording is currently
> occurring
> > > > >> (specifically, a distinct "beep tone" signal that is repeated
> at
> > > > > regular
> > > > >> intervals during the course of the telephone
> > > conversation when the
> > > > >> recording device is in use); note that this is
> consistent with
> > > > > existing
> > > > >> methods from FCC Rules Regarding Telephone Company
> Recording of
> > > > >> Interstate or International Wireline Telephone Conversations.
> > > > >> But I do not see a reason to mention
> "announcements", or "other
> > > > media"
> > > > >> in this requirement.
> > > > >>
> > > > >> Therefore, I recommend the following wording for REQ-018:
> > > > >>
> > > > >> "REQ-018 The mechanism MUST provide a means of indicating to
> the
> > > > >> participants involved in a CS that their session is
> > > being recorded.
> > > > > To
> > > > >> support this the mechanism MUST provide a means of playing a
> > > > > repeatable
> > > > >> tone to CS participants, and also the mechanism MUST
> > > > provide a means
> > > > > to
> > > > >> indicate to recording-aware UAs that recording is
> > > > currently occurring
> > > >
> > > > >> (for appropriate rendering at the user interface)."
> > > > >>
> > > > >> Regards,
> > > > >> Dave
> > > > >>
> > > > >> -----Original Message-----
> > > > >> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org]
> On
> > > > > Behalf
> > > > >> Of Elwell, John
> > > > >> Sent: Wednesday, March 02, 2011 3:41 AM
> > > > >> To: Leon Portman; siprec issue tracker
> > > > >> Cc: siprec@ietf.org
> > > > >> Subject: Re: [siprec] Requirements #66 (new):
> Clarification of
> > > > >> REQ-018 on indications to participants
> > > > >>
> > > > >> In the interests of getting the requirements document
> > > finished, I
> > > > >> will set a short deadline for this remaining issue. If I
> > > have not
> > > > >> heard any objections to the proposal below by 2011-03-07 I
> > > > will ask
> > > > >> the editor
> > > > > to
> > > > >> adopt this new text and publish -07.
> > > > >>
> > > > >> John (as chair)
> > > > >>
> > > > >>> -----Original Message-----
> > > > >>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > >>> Sent: 28 February 2011 16:17
> > > > >>> To: Elwell, John; siprec issue tracker
> > > > >>> Cc: siprec@ietf.org
> > > > >>> Subject: RE: [siprec] Requirements #66 (new):
> Clarification of
> > > > >>> REQ-018 on indications to participants
> > > > >>>
> > > > >>> +1
> > > > >>>
> > > > >>> Leon
> > > > >>>
> > > > >>> -----Original Message-----
> > > > >>> From: Elwell, John
> [mailto:john.elwell@siemens-enterprise.com]
> > > > >>> Sent: Monday, February 28, 2011 5:35 PM
> > > > >>> To: Leon Portman; siprec issue tracker
> > > > >>> Cc: siprec@ietf.org
> > > > >>> Subject: RE: [siprec] Requirements #66 (new):
> Clarification of
> > > > >>> REQ-018 on indications to participants
> > > > >>>
> > > > >>> There has been little discussion on this, apart from
> > > support from
> > > > >>> Leon. The existing text says:
> > > > >>> "REQ-018 The mechanism MUST provide a means of indicating to
> the
> > > > >>>      participants involved in a CS that their
> session is being
> > > > > recorded.
> > > > >>>
> > > > >>>      Examples include: inject tones into the CS from the
> > > > SRC, play a
> > > > >>>      message at the beginning of a session, a visual
> > > > indicator on a
> > > > >>>      display, etc."
> > > > >>>
> > > > >>> I would suggest the following text:
> > > > >>> "REQ-018 The mechanism MUST provide a means of
> > > indicating to the
> > > > >>> participants involved in a CS that their session is being
> > > > recorded.
> > > > >>> Although this can be accomplished using existing SIP
> > > > techniques for
> > > > >>> playing an in-band tone, announcement or other media to
> > > > >>> participants, the mechanism is required also to provide an
> > > > >>> indication to recording-aware UAs for appropriate
> > > > rendering at the
> > > > >>> user interface."
> > > > >>>
> > > > >>> John (as individual)
> > > >
> > >
> >
> >
> >
> --------------------------------------------------------------
> ----------
> ------------------------------
> > -------------
> > CONFIDENTIALITY NOTICE: This e-mail and any files attached
> may contain
> confidential and proprietary
> > information of Alcatel-Lucent and/or its affiliated entities. Access
> by the intended recipient only is
> > authorized. Any liability arising from any party acting, or
> refraining
> from acting, on any information
> > contained in this e-mail is hereby excluded. If you are not the
> intended recipient, please notify the
> > sender immediately, destroy the original transmission and its
> attachments and do not disclose the
> > contents to any other person, use it for any purpose, or
> store or copy
> the information in any medium.
> > Copyright in this e-mail and any attachments belongs to
> Alcatel-Lucent
> and/or its affiliated entities.
> >
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
>

From eckelcu@cisco.com  Fri Mar  4 08:50:46 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63FD03A69E0 for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 08:50:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7gPeE0UVRuv for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 08:50:43 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id B11F43A69BC for <siprec@ietf.org>; Fri,  4 Mar 2011 08:50:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=21890; q=dns/txt; s=iport; t=1299257513; x=1300467113; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=YFmrrzbF9GeS5mzSFMLQMFZJZ5RrVEsH7c4NjY2rScw=; b=c6PfFGplpU4buki7D7oDDOUs7nxOUXAirB0wmbwudXFk49DrnhIXVD5H ehqmFM176dQqO2/3VfT48PcUF/o5Xjq+xoaPaDLMHlXXmEe9IhzSCxl+s ioC8xxCHRI/4WmV02IgBQuVgJOJuKpJszQM9q2l0ZOdunexXHPikqZtFP U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgABAMumcE2rRN+K/2dsb2JhbACYJ448dKNMm2qFYQSFHIpc
X-IronPort-AV: E=Sophos;i="4.62,264,1297036800"; d="scan'208";a="317245856"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-2.cisco.com with ESMTP; 04 Mar 2011 16:51:52 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p24GpqMR022139; Fri, 4 Mar 2011 16:51:52 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Mar 2011 08:51:52 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Mar 2011 08:51:51 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9A8D@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA06C2C5096C@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018onindications to participants
Thread-Index: AcvZTH+Vs7u6urhTT2Km7kQw3BSzZAAKEM4gAACNCkAAAjkN0AANwi0gAAObWlAAAPSOQAAEo2QAABjA5SAAE2kDIA==
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com><4D6EFFD0.7070109@cisco.com><07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com><CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C5086D@MCHP058A.global-ad.net> <CD2DE94B86B69443B53711F606FCAE120862E4B7@SARUMAN.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB97EC@xmb-sjc-234.amer.cisc o.com> < A444A0F8084434499206E78C106220CA06C2C5096C@MCHP058A.global-ad.net>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Dave Smith" <Dave.d.Smith@alcatel-lucent.com>, "Leon Portman" <Leon.Portman@nice.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Mar 2011 16:51:52.0637 (UTC) FILETIME=[765E76D0:01CBDA8C]
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018onindications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 16:50:46 -0000

Works for me.=20
Sorry I missed it in the thread, and thanks for clarifying.

Cheers,
Charles

> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 03, 2011 11:40 PM
> To: Charles Eckel (eckelcu); Dave Smith; Leon Portman; Paul Kyzivat
(pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Requirements #66 (new): Clarification of
REQ-018onindications to participants
>=20
> Charles,
>=20
> The text you quote is not the latest proposal. You will see below a
later proposal for two separate
> requirements REQ-x1 and REQ-x2 to replace REQ-018. I understand Dave
was agreeing with those new
> requirements. I reproduce the new proposal here:
>=20
> "REQ-x1 The mechanism MUST NOT prevent the application of tones or
announcements during recording or
> at the start of a CS to support legal or policy requirements for
notifying participants that the call
> is being recorded or may be recorded."
>=20
> "REQ-x2 The mechanism MUST provide a means of indicating to
recording-aware UAs whether recording is
> taking place, for appropriate rendering at the user interface.
>=20
> John
>=20
>=20
> > -----Original Message-----
> > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > Sent: 03 March 2011 20:05
> > To: Dave Smith; Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > of REQ-018onindications to participants
> >
> > Just to clarify, is the decision therefore that Req. #18 will
> > be updated
> > as proposed by John?
> >
> > > > > >>> I would suggest the following text:
> > > > > >>> "REQ-018 The mechanism MUST provide a means of
> > > > indicating to the
> > > > > >>> participants involved in a CS that their session is being
> > > > > recorded.
> > > > > >>> Although this can be accomplished using existing SIP
> > > > > techniques for
> > > > > >>> playing an in-band tone, announcement or other media to
> > > > > >>> participants, the mechanism is required also to provide an
> > > > > >>> indication to recording-aware UAs for appropriate
> > > > > rendering at the
> > > > > >>> user interface."
> >
> > If I am interpreting this correctly, playing of a tone or an
> > announcement is an option, not a required form of indication, and
some
> > other indication may be communicated from the SRC to a recording
aware
> > UA that results in the UA producing an indication of recording that
is
> > possibly NOT audible, for example. The choice of the actual
> > rendering of
> > this indication by the UA is left entirely to the UA. Is that
correct?
> >
> > Thanks,
> > Charles
> >
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Dave Smith
> > > Sent: Thursday, March 03, 2011 9:38 AM
> > > To: Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Requirements #66 (new): Clarification of
> > REQ-018onindications to participants
> > >
> > > Thanks for the detailed inputs/explanations.  I agree with the
> > > recommendations for using REQ-x1 and -x2.
> > >
> > > Regards,
> > > Dave
> > >
> > > -----Original Message-----
> > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > Sent: Thursday, March 03, 2011 9:17 AM
> > > To: Leon Portman; Dave Smith; Paul Kyzivat
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > of REQ-018
> > > onindications to participants
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: 03 March 2011 15:24
> > > > To: Elwell, John; Dave Smith; Paul Kyzivat
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > > > of REQ-018 on indications to participants
> > > >
> > > > I agree with your points. Just generic question, do we really
> > > > need a requirement for mechanism not to prevent something? It
> > > > can be lot of things like encryption, codec negotiation,
> > > > ability to transfer call etc.
> > > [JRE] It is certainly worth questioning whether we need
> > REQ-x1 below.
> > On
> > > the one hand, SIPREC is unlikely to specify anything that would
> > prevent
> > > this existing capability. In fact it would be quite hard
> > for SIPREC to
> > > specify something that would prevent the application of tones of
> > > announcement. Of course, there might be things that could be done
at
> > > deployment time to prevent it (e.g., encryption), but that is not
> > > SIPREC's problem. However, I would still be inclined to keep it.
In
> > > particular, the Privacy Considerations section has a statement:
> > > "Therefore this document contains requirements for being able to
> > notify
> > > users that a call is being recorded ...". I don't think REQ-x2
alone
> > > would be sufficient to satisfy that, so if we were to
> > remove REQ-x1 we
> > > would have to revisit the Privacy Considerations text, which I
would
> > be
> > > very reluctant to do. So I would like to keep REQ-x1 or something
> > > similar.
> > >
> > > John (as individual)
> > >
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > > Sent: Thursday, March 03, 2011 11:14 AM
> > > > To: Dave Smith; Leon Portman; Paul Kyzivat
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > > > of REQ-018 on indications to participants
> > > >
> > > > Concerning #1, I agree we need to be able to accommodate the
> > > > different requirements of different regions, countries,
> > > > business sectors, etc.. Sometimes this might involve playing
> > > > a tone (e.g., a repeated beep) for the duration of recording,
> > > > and sometimes this might involve an announcement at the
> > > > beginning of the session, which will suffice whether or not
> > > > recording actually takes place during the session. Basically,
> > > > since not all users will use siprec-aware UAs, particularly
> > > > PSTN users, the only solution is for the SRC to arrange that
> > > > the appropriate tone or announcement is injected into the
> > > > audio stream when required. If the SRC itself is able to do
> > > > this, we don't need a SIP solution. If the SRC uses a media
> > > > server to do this, existing SIP/SDP mechanisms will cater for
> > > > this. I don't anticipate siprec providing new mechanisms for
> > > > this. It is really just a case of not preventing the use of
> > > > such mechanisms. How about the following text?
> > > >
> > > > "REQ-x1 The mechanism MUST NOT prevent the application of
> > > > tones or announcements during recording or at the start of a
> > > > CS to support legal or policy requirements for notifying
> > > > participants that the call is being recorded or may be
recorded."
> > > >
> > > > Concerning #2, I see this more of a courtesy thing, rather
> > > > than a legal thing. Most web-based conference applications
> > > > give a visual indication of whether the conference is being
> > > > recorded, achieved using web technology. Where this is not
> > > > available, it would be useful if siprec-aware UAs in the CS
> > > > could be advised when recording is taking place so that they
> > > > can give an appropriate indication to the user. I can see a
> > > > number of reasons for this:
> > > > - It provides the possibility of alternative modes for
> > > > hearing-impaired users.
> > > > - It gives more precise information in cases where an
> > > > SRC-injected announcement is given only at the start of the
call.
> > > > - It provides feedback to users who have requested that
> > > > recording be started / stopped / paused / resumed.
> > > > - It gives an explicit indication to users who might not
> > > > understand the meaning of an injected tone.
> > > > - It is independent of medium type (audio, video, real-time
> > > > text, fax...).
> > > > - Potentially its granularity could be on a per medium basis,
> > > > although I would prefer to leave that as an option for the
> > > > solution, rather than making a requirement.
> > > >
> > > > So how about the following text?
> > > >
> > > > "REQ-x2 The mechanism MUST provide a means of indicating to
> > > > recording-aware UAs whether recording is taking place, for
> > > > appropriate rendering at the user interface.
> > > >
> > > > John (as individual)
> > > >
> > > > > >>> participants involved in a CS that their session is being
> > > > > recorded.
> > > > > >>> Although this can be accomplished using existing SIP
> > > > > techniques for
> > > > > >>> playing an in-band tone, announcement or other media to
> > > > > >>> participants, the mechanism is required also to provide an
> > > > > >>> indication to recording-aware UAs for appropriate
> > > > > rendering at the
> > > > > >>> user interface."
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
> > > > > Sent: 03 March 2011 08:29
> > > > > To: Leon Portman; Paul Kyzivat
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > > > > of REQ-018 on indications to participants
> > > > >
> > > > > I fully agree that an IVR solution (play an announcement) is
an
> > > > > acceptable method that is used today to inform a caller.
> > > > > I was introducing this req't (#1 below) in order to improve
> > > > on that.
> > > > >
> > > > > Do we absolutely need #1 - probably not.  Do we
> > absolutely need #2
> > -
> > > > > probably not also.
> > > > >
> > > > > It seems that you are indicating that at least for #1 a
solution
> > is
> > > > > difficult to provide and would restrict the SRC solution
> > > > > significantly,
> > > > > so we should not include it.
> > > > > I am wondering if that is also the case for #2.
> > > > >
> > > > > I don't think we need to mention any "optional" solutions in
> > > > > the req't.
> > > > >
> > > > >
> > > > > Regards,
> > > > > Dave
> > > > >
> > > > > -----Original Message-----
> > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > Sent: Wednesday, March 02, 2011 11:32 PM
> > > > > To: Paul Kyzivat; Dave Smith
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Requirements #66 (new): Clarification
> > > > of REQ-018
> > > > > on indications to participants
> > > > >
> > > > > I agree with Paul. In the environment where SRC cannot inject
> > > > > any audio
> > > > > into the CS, best practice is to have IVR or Voice Portal
> > > > to make such
> > > > > announcement.
> > > > >
> > > > > Leon
> > > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > > > > [mailto:siprec-bounces@ietf.org] On Behalf
> > > > > Of Paul Kyzivat
> > > > > Sent: Thursday, March 03, 2011 4:41 AM
> > > > > To: Dave Smith
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > > > of REQ-018
> > > > > on indications to participants
> > > > >
> > > > >
> > > > >
> > > > > On 3/2/2011 7:50 PM, Dave Smith wrote:
> > > > > > I think the solution should be able to support these
> > > > > functionalities:
> > > > > >   1.  playing a repeatable tone to CS participants
> > > > > >   2.  indicate to recording-aware UAs that recording is
> > currently
> > > > > > occurring
> > > > > >
> > > > > > Although there may be other things that could be done, I
> > > > > believe that
> > > > > > these functionalities are reasonable and sufficient, and
would
> > be
> > > > > > universally accepted, and that both are required in order
> > > > > to be able
> > > > > > to addresss most use cases for indicating to the
> > > > > participants involved
> > > > >
> > > > > > in a CS that their session is being recorded.
> > > > >
> > > > > > I am not sure of what the last paragraph of your response
> > > > is about
> > > > > > exactly.  A solution to this req't needs to be worked out
> > > > > in another
> > > > > > SIPREC Draft; my current thoughts are that since the SRC is
> > > > > handling
> > > > > > and in the path of CS UA media and is already communicating
> > > > > with these
> > > > >
> > > > > > UAs, probably an SRC-based solution could be more easily
> > > > > used to solve
> > > > >
> > > > > > this req't.
> > > > >
> > > > > I'll try to elaborate:
> > > > >
> > > > > I'm not informed of the specific legalities involved, but am
of
> > the
> > > > > impression that they vary widely. There are certainly
> > > > > contexts in which
> > > > > no audible indication need be played. (E.g. call centers,
> > > > at least in
> > > > > some places.) In some cases this is dealt with by playing a
> > general
> > > > > disclaimer at the beginning of the call, and/or having a
> > contractual
> > > > > relationship by which this isn't required.
> > > > >
> > > > > In such environments the SRC may not need any way of
> > injecting an
> > > > > audible indication that recording is going on.
> > > > >
> > > > > And there are ways an SRC could get the media for recording
> > > > that don't
> > > > > provide a way to inject these tones. (E.g. a media *relay*
> > > > > may fork the
> > > > > media, but not be able to alter it.)
> > > > >
> > > > > If you combine these things, you can end up with mechanisms
for
> > > > > implementing the SRC function that are *incapable* of
> > > > satisfying your
> > > > > proposed requirement, and yet are perfectly suitable for
> > > > the intended
> > > > > recording task. I don't want to rule those out as valid
> > > > > implementations
> > > > > of siprec.
> > > > >
> > > > > I'm fine with having the tone generation as an *option*,
> > > > and one that
> > > > > may be absolutely required in *some* markets. If you have a
> > business
> > > > > that requires this tone generation then you will buy a product
> > that
> > > > > supports it.
> > > > >
> > > > >     Thanks,
> > > > >     Paul
> > > > >
> > > > > > Regards,
> > > > > > Dave
> > > > > >
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: siprec-bounces@ietf.org
[mailto:siprec-bounces@ietf.org]
> > On
> > > > > > Behalf Of Paul Kyzivat
> > > > > > Sent: Wednesday, March 02, 2011 1:43 PM
> > > > > > To: siprec@ietf.org
> > > > > > Subject: Re: [siprec] Requirements #66 (new): Clarification
> > > > > of REQ-018
> > > > >
> > > > > > on indications to participants
> > > > > >
> > > > > > Dave,
> > > > > >
> > > > > > I recognize that there are environments where this audible
> > > > > tone is a
> > > > > > requirement. And also environments where it is not, or that
> > > > > there is
> > > > > > some *other* requirement.
> > > > > >
> > > > > > My question is whether rendering such things is "part of the
> > > > > > mechanism",
> > > > > >
> > > > > > or simply something that some SRCs must be able to do.
> > > > > >
> > > > > > Making this part of the mechanism begs the question of "what
> > > > > mechanism".
> > > > > >
> > > > > > There are mechanisms for capturing the media for recording
> > > > > that do not
> > > > >
> > > > > > have a device in place that can insert something into
> > the media.
> > > > > > Making this a requirement on the mechanism would exclude
> > > > > using those
> > > > > > techniques.
> > > > > >
> > > > > >   Thanks,
> > > > > >   Paul
> > > > > >
> > > > > > On 3/2/2011 2:57 PM, Dave Smith wrote:
> > > > > >> I do have an input to this requirement.
> > > > > >>
> > > > > >> I agree that the system should be able to provide an
> > > > indication to
> > > > > >> recording-aware UAs that recording is currently
> > occurring (for
> > > > > >> appropriate rendering at the user interface).
> > > > > >> I also believe that the system should be able to provide a
> > > > > "tone" to
> > > > > > CS
> > > > > >> participants to indicate that recording is currently
> > occurring
> > > > > >> (specifically, a distinct "beep tone" signal that is
repeated
> > at
> > > > > > regular
> > > > > >> intervals during the course of the telephone
> > > > conversation when the
> > > > > >> recording device is in use); note that this is
> > consistent with
> > > > > > existing
> > > > > >> methods from FCC Rules Regarding Telephone Company
> > Recording of
> > > > > >> Interstate or International Wireline Telephone
Conversations.
> > > > > >> But I do not see a reason to mention
> > "announcements", or "other
> > > > > media"
> > > > > >> in this requirement.
> > > > > >>
> > > > > >> Therefore, I recommend the following wording for REQ-018:
> > > > > >>
> > > > > >> "REQ-018 The mechanism MUST provide a means of indicating
to
> > the
> > > > > >> participants involved in a CS that their session is
> > > > being recorded.
> > > > > > To
> > > > > >> support this the mechanism MUST provide a means of playing
a
> > > > > > repeatable
> > > > > >> tone to CS participants, and also the mechanism MUST
> > > > > provide a means
> > > > > > to
> > > > > >> indicate to recording-aware UAs that recording is
> > > > > currently occurring
> > > > >
> > > > > >> (for appropriate rendering at the user interface)."
> > > > > >>
> > > > > >> Regards,
> > > > > >> Dave
> > > > > >>
> > > > > >> -----Original Message-----
> > > > > >> From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org]
> > On
> > > > > > Behalf
> > > > > >> Of Elwell, John
> > > > > >> Sent: Wednesday, March 02, 2011 3:41 AM
> > > > > >> To: Leon Portman; siprec issue tracker
> > > > > >> Cc: siprec@ietf.org
> > > > > >> Subject: Re: [siprec] Requirements #66 (new):
> > Clarification of
> > > > > >> REQ-018 on indications to participants
> > > > > >>
> > > > > >> In the interests of getting the requirements document
> > > > finished, I
> > > > > >> will set a short deadline for this remaining issue. If I
> > > > have not
> > > > > >> heard any objections to the proposal below by 2011-03-07 I
> > > > > will ask
> > > > > >> the editor
> > > > > > to
> > > > > >> adopt this new text and publish -07.
> > > > > >>
> > > > > >> John (as chair)
> > > > > >>
> > > > > >>> -----Original Message-----
> > > > > >>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > >>> Sent: 28 February 2011 16:17
> > > > > >>> To: Elwell, John; siprec issue tracker
> > > > > >>> Cc: siprec@ietf.org
> > > > > >>> Subject: RE: [siprec] Requirements #66 (new):
> > Clarification of
> > > > > >>> REQ-018 on indications to participants
> > > > > >>>
> > > > > >>> +1
> > > > > >>>
> > > > > >>> Leon
> > > > > >>>
> > > > > >>> -----Original Message-----
> > > > > >>> From: Elwell, John
> > [mailto:john.elwell@siemens-enterprise.com]
> > > > > >>> Sent: Monday, February 28, 2011 5:35 PM
> > > > > >>> To: Leon Portman; siprec issue tracker
> > > > > >>> Cc: siprec@ietf.org
> > > > > >>> Subject: RE: [siprec] Requirements #66 (new):
> > Clarification of
> > > > > >>> REQ-018 on indications to participants
> > > > > >>>
> > > > > >>> There has been little discussion on this, apart from
> > > > support from
> > > > > >>> Leon. The existing text says:
> > > > > >>> "REQ-018 The mechanism MUST provide a means of indicating
to
> > the
> > > > > >>>      participants involved in a CS that their
> > session is being
> > > > > > recorded.
> > > > > >>>
> > > > > >>>      Examples include: inject tones into the CS from the
> > > > > SRC, play a
> > > > > >>>      message at the beginning of a session, a visual
> > > > > indicator on a
> > > > > >>>      display, etc."
> > > > > >>>
> > > > > >>> I would suggest the following text:
> > > > > >>> "REQ-018 The mechanism MUST provide a means of
> > > > indicating to the
> > > > > >>> participants involved in a CS that their session is being
> > > > > recorded.
> > > > > >>> Although this can be accomplished using existing SIP
> > > > > techniques for
> > > > > >>> playing an in-band tone, announcement or other media to
> > > > > >>> participants, the mechanism is required also to provide an
> > > > > >>> indication to recording-aware UAs for appropriate
> > > > > rendering at the
> > > > > >>> user interface."
> > > > > >>>
> > > > > >>> John (as individual)
> > > > >
> > > >
> > >
> > >
> > >
> > --------------------------------------------------------------
> > ----------
> > ------------------------------
> > > -------------
> > > CONFIDENTIALITY NOTICE: This e-mail and any files attached
> > may contain
> > confidential and proprietary
> > > information of Alcatel-Lucent and/or its affiliated entities.
Access
> > by the intended recipient only is
> > > authorized. Any liability arising from any party acting, or
> > refraining
> > from acting, on any information
> > > contained in this e-mail is hereby excluded. If you are not the
> > intended recipient, please notify the
> > > sender immediately, destroy the original transmission and its
> > attachments and do not disclose the
> > > contents to any other person, use it for any purpose, or
> > store or copy
> > the information in any medium.
> > > Copyright in this e-mail and any attachments belongs to
> > Alcatel-Lucent
> > and/or its affiliated entities.
> > >
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
> >

From eckelcu@cisco.com  Fri Mar  4 09:21:00 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1914128C0CF for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 09:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ujZtU1zFrOy for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 09:20:58 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 37A7228C0CE for <siprec@ietf.org>; Fri,  4 Mar 2011 09:20:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=8950; q=dns/txt; s=iport; t=1299259327; x=1300468927; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=X6WA6eTMPQOPDBWWY8yTS3EfGaxMik6bnJeEIFQbuno=; b=h5oh/VQ7ALA2cJ9zjaBA3gR1CggVm/LwuBZUkjvAcbw72bI3hGfsN6FY gQai+PE7KlVD8BC2RAOo5/z17aJPoU5YmcJ/cnruj8DQNDVOM364iyLwN VsFPa33QS6AJC1dKqVCp+3RMa+Ww3YVx6p6rzPrMskOq+2L7naoMIBHk+ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkBAN2tcE2rRN+K/2dsb2JhbACYJ448dKNJm2aCfoJjBIUcilw
X-IronPort-AV: E=Sophos;i="4.62,264,1297036800"; d="scan'208";a="317254462"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-2.cisco.com with ESMTP; 04 Mar 2011 17:22:07 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p24HM7Zk010314; Fri, 4 Mar 2011 17:22:07 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Mar 2011 09:22:07 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Mar 2011 09:22:06 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9A9F@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <4D70423D.7030202@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Synchronous vs Asynchronous Error handling
Thread-Index: AcvaDK93E6JOkiLqT3qHAAA3inpMbwAg1MSQ
References: <A11921905DA1564D9BCF64A6430A62390293A665@XMB-BGL-411.cisco.com><4D67EC69.7080507@cisco.com><059AF07365DC474393A19A3AF187DF7406BADEA6@NAHALD.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2BAA742@MCHP058A.global-ad.net><4D6BBDAE.3020808@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE02F@NAHALD.us.int.genesyslab.com><07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A623904A63B8A@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB991A@xmb-sjc-234.amer.cisco.com> <4D70423D.7030202@cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Mar 2011 17:22:07.0402 (UTC) FILETIME=[B00DA0A0:01CBDA90]
Cc: Leon Portman <Leon.Portman@nice.com>, Henry Lum <Henry.Lum@alcatel-lucent.com>, siprec@ietf.org
Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 17:21:00 -0000

Hi Paul,

I think we are both saying the same thing, but let me make sure. In
cases in which processing everything synchronously is not feasible, an
implementation MUST send an SDP answer synchronously in order to
complete the existing SIP transaction, then complete the processing of
the metadata asynchronously, and if required, MAY send an offer in
another SIP transaction to address and changes required.

Cheers,
Charles

> -----Original Message-----
> From: Paul Kyzivat (pkyzivat)
> Sent: Thursday, March 03, 2011 5:37 PM
> To: Charles Eckel (eckelcu)
> Cc: Parthasarathi R (partr); Leon Portman; Henry Lum; Elwell, John;
siprec@ietf.org
> Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
>=20
> Charles,
>=20
> Its my expectation that none of the metadata *need* be processed in
> order to answer an sdp offer. However the sdp will typically be
required
> to supplement the metadata processing. So it likely will be necessary
to
> queue the xml+sdp for later processing as metadata.
>=20
> One might want to make decisions about how to construct the answer
(e.g.
> whether to accept or reject a media stream) based on the xml metadata.
> If one is capable of doing all the processing synchronously in order
to
> do so, go for it. But nobody should be forced to do that.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/3/2011 6:41 PM, Charles Eckel (eckelcu) wrote:
> > Hi Partha,
> >
> > I think we need both. If the error is detected in SDP processing,
> > handling it in the SIP response synchronously makes sense. If the
error
> > is detected in the metadata processing, it would ideally be handled
in
> > the SIP response synchronously, but it may result in a subsequent
> > request being sent to indicate and/or recover from the error. Errors
may
> > also be encountered independent of any SIP request processing, and
those
> > will need to be handled asynchronously.
> > So I think we need both, and how much of the XML to process
> > synchronously is up to the answerer. Ideally we will structure the
XML
> > such that it is as clear and efficient as possible to identify the
XML
> > that directly impacts the SDP. This will facilitate synchronous
> > responses.
> >
> > Cheers,
> > Charles
> >
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Parthasarathi R (partr)
> >> Sent: Wednesday, March 02, 2011 5:48 AM
> >> To: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
> >> Cc: siprec@ietf.org
> >> Subject: [siprec] Synchronous vs Asynchronous Error handling
> >>
> >> Hi all,
> >>
> >> Another issue discussed as part of the below mail thread is whether
> >> metadata (XML+SDP) error has to be responded synchronously (SIP
> >> Request/[SIP provisional response]/SIP Response) or
asynchronously(SIP
> >> Request/SIP Response/SIP Error request/SIP Error response).
> >>
> >> Synchronous Error handling:
> >>  From SRC perspective, synchronous error handling is simple to
> > implement
> >> as there is no extra context or state to be maintained about the
> > earlier
> >> SIP transactions.
> >>
> >> In SRS, SDP Metadata portion *MUST* be processed in synchronously
to
> >> meet offer/answer model requirement. Now the question is whether
XML
> >> takes so much of a time wherein the error MUST be handled
> > asynchronous?
> >> The simple SRS will be able to send provisional response and
respond
> >> back final response once the complete XML check is done. My
reasoning
> > is
> >> so because B2BUA normally handles INVITE/RE-INVITE in a way that
send
> >> (100 trying) provisional response to the incoming dialog side, send
> >> INVITE/RE-INVITE to the outgoing dialog side which may take upto 32
> > sec
> >> delay to respond and forwards 200 OK to incoming dialog side once
it
> > is
> >> received from outgoing dialog side and it is well working deployed
> >> model. Please let me know in which situation this mechanism has
issues
> >> specific to SIPREC&  XML.
> >>
> >> Asynchronous Error handling:
> >> Here as well in SRS, SDP Metadata portion *MUST* be processed in
> >> synchronously to meet offer/answer model requirement.
> >>
> >> Two cases exists from SRC perspective.
> >> 1) In case the sequence number has to be maintained by SRC for
> >> asynchronous error handling, then it *MAY* require SRC to maintain
the
> >> earlier transaction which is overkill as SRC will not keep track or
> >> record its previous state.
> >>
> >> 2) In most of the scenario, it is not possible to re-record but it
is
> >> only possible to re-sync. In case the motivation of asynchronous
error
> >> is to re-sync metadata by SRS to SRC, it is very similar to SRS
> >> requesting for current complete metadata (SDP+XML) from SRC. On
> >> receiving re-sync request, SRC has to trigger the complete metadata
> >> towards SRS. The sequence number from SRS *MAY* be used for logging
> >> purpose if required.
> >>
> >> Please let me know which one of the above asynchronous behavior is
> >> expected from SRC. Also, instead of asynchronous error message, do
you
> >> wish to create re-sync request mechanism from SRS which may be used
> > for
> >> error or other purpose as well.
> >>
> >> Thanks
> >> Partha
> >>
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf
> >> Of Leon Portman
> >> Sent: Monday, February 28, 2011 9:48 PM
> >> To: Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
> >> Cc: siprec@ietf.org
> >> Subject: Re: [siprec] Metadata XML document error representation
> >> forwhole doc or for portion of doc
> >>
> >> +1
> >>
> >> Leon
> >>
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf
> >> Of Henry Lum
> >> Sent: Monday, February 28, 2011 6:13 PM
> >> To: Paul Kyzivat; Elwell, John
> >> Cc: siprec@ietf.org
> >> Subject: Re: [siprec] Metadata XML document error representation
for
> >> whole doc or for portion of doc
> >>
> >>
> >>
> >>>>> We are also thinking of providing the SRS with a mechanism to
> >>>>> request the SRC to ask for the current snapshot
> >>> so
> >>>>> that the SRC/SRS can reset the states in the case where SRS is
in
> > a
> >>
> >>>>> really bad state. By doing so, we may be able to avoid providing
> >>> nack
> >>>>> responses and avoid using a chatty protocol.
> >>>> [JRE] Yes, and the request to resend full metadata could
> > optionally
> >>> include some sort of error report that gave rise to the request.
> > That
> >>> error report could, for example, include the sequence number of
the
> >>> metadata update that was found to be in error.
> >>>
> >>> That is sort of what I had in mind about getting the two sides in
> >> sync.
> >>> But we will have to think more about exactly what it means.
> >>> At best I think it will describe the *current* state of things in
> > this
> >>
> >>> RS, without regard to what has happened in the past.
> >>>
> >>> Even that may present some technical challenges. But we should
keep
> >>> this desire in mind.
> >>
> >> [[hlum]] I agree it would be reasonable for the SRC to send the
> > current
> >> state as a snapshot and forget what happened previously. The
> > subsequent
> >> sequence numbers only refers to the current snapshot rather than
the
> >> original one, so in a way we are resetting the sequence number.
> >>
> >>
> >>
> >
------------------------------------------------------------------------
> >> -------------------------------------------
> >> CONFIDENTIALITY NOTICE: This e-mail and any files attached may
contain
> >> confidential and proprietary information of Alcatel-Lucent and/or
its
> >> affiliated entities. Access by the intended recipient only is
> >> authorized. Any liability arising from any party acting, or
refraining
> >> from acting, on any information contained in this e-mail is hereby
> >> excluded. If you are not the intended recipient, please notify the
> >> sender immediately, destroy the original transmission and its
> >> attachments and do not disclose the contents to any other person,
use
> > it
> >> for any purpose, or store or copy the information in any medium.
> >> Copyright in this e-mail and any attachments belongs to
Alcatel-Lucent
> >> and/or its affiliated entities.
> >>
> >> _______________________________________________
> >> 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
> >

From Henry.Lum@alcatel-lucent.com  Fri Mar  4 09:28:15 2011
Return-Path: <Henry.Lum@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 95C143A683C for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 09:28:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2VwmSoeSQj01 for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 09:28:13 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 602343A687E for <siprec@ietf.org>; Fri,  4 Mar 2011 09:28:13 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p24HTJrh006666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 4 Mar 2011 11:29:19 -0600 (CST)
Received: from relay-out1.dc.genesyslab.com (relay-out1.dc.genesyslab.com [172.22.68.187]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p24HTHNq024193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 4 Mar 2011 11:29:19 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.dc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id p24HTHof004565; Fri, 4 Mar 2011 09:29:17 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.93]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Mar 2011 09:29:17 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Mar 2011 09:29:16 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7406C36B5D@NAHALD.us.int.genesyslab.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB987B@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
Thread-Index: AcvYdoq1VttmMUOCSj+I/EBWiH/OmQAgjaaAADyUJVAAKMzRwA==
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com><4D6D3FE5.9000902@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com><4D6D98DC.8080008@cisco.com> <059AF07365DC474393A19A3AF187DF7406BAE5C6@NAHALD.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB987B@xmb-sjc-234.amer.cisco.com>
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Mar 2011 17:29:17.0089 (UTC) FILETIME=[B02AA910:01CBDA91]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 17:28:15 -0000

Please see inline.

> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: Thursday, March 03, 2011 4:55 PM
> To: Henry Lum; Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] FW: New VersionNotificationfor draft-portman-
> siprec-protocol-03
>=20
> I think it is better to stick to using UPDATE and not introduce a need
> to use INFO. I would also expect that using re-INVITE instead of
> UPDATE,
> though not explicitly recommended, would work as well. What drives
this
> is the inclusion of the newly defined tags and the actual metadata.
>=20
[[hlum]] Okay - let's hear if there are supporters for INFO before
making a change.

> Section 5 reads,
>=20
>    The SRC must be able to accept re-INVITE from SRS with the updated
>    SDP as part of the session timer mechanism.
>=20
> What is the purpose of stating this?=20
> I agree the SRC needs to be able
> to
> accept a re-INVITE with updated or non-updated SDP from the SRS. It
> also
> needs to be able to receive an UPDATE with updated or non-updated SDP.
> This appears to me to be independent of using session timer, and I do
> not believe we are mandating support for session timer either.

[[hlum]] Perhaps the wording may be a bit too explicit, but the
intention is that a recording session should use session timer since the
SRS never sends any media to the SRC and the SRC needs a way to tell
that the SRS is still around. I don't think session timer needs to be
mandated but I think it is recommended that we use it.

>=20
> In section 6.2, what does the "record" attribute and the defined
> "indication" attribute give us that we do not already have using
> sendonly and inactive, where off/pause maps to inactive and on maps to
> sendonly?

[[hlum]] a=3Dsendrev/sendonly/recvonly describes the directionality of th=
e
actual media stream in the CS. What we want is an indication on the CS
media streams where recording is actually taking place or not, and that
should not involve changing the directionality of the actual media
stream.

On the recording session media streams, we do use a=3Dsendrecv/sendonly t=
o
indicate pause/resume.=20

>=20
> In section 6.3, recording preference, do we really need pause and
> resume? I am thinking record and norecord may be sufficient.
>=20
[[hlum]] The current consensus for the new wording of REQ-017 includes
pause and resume:

"REQ-zzz The mechanism MUST support a means for a recording-aware UA
involved in a CS to request during a session that the recording of the
CS should be started, paused, resumed or stopped, the honoring of such a
request being dependent on policy."

> Cheers,
> Charles
>=20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Henry Lum
> > Sent: Wednesday, March 02, 2011 8:45 AM
> > To: Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] FW: New VersionNotificationfor
> draft-portman-siprec-protocol-03
> >
> > I don't feel strongly too about using INFO so I am open to using
> UPDATE
> > if the group feels that it is okay for SRC/SRS to deal with the
> > consequences of UPDATE collision.
> >
> > Henry
> >
> > > -----Original Message-----
> > > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > > Sent: Tuesday, March 01, 2011 8:10 PM
> > > To: Henry Lum
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] FW: New Version Notificationfor draft-
> portman-
> > > siprec-protocol-03
> > >
> > >
> > >
> > > On 3/1/2011 2:32 PM, Henry Lum wrote:
> > > > When there is an UPDATE transaction collision, you will have to
> make
> > > > both SRC and SRS to wait a while before being able to send
UPDATE
> > > again.
> > > > Since SRC is normally the side initiating the SIP dialog, it is
> the
> > > > owner of the Call-ID and will come second after the SRS has a
> chance
> > > to
> > > > resend the UPDATE. In that case, does the SRC keep the existing
> > > UPDATE
> > > > or send a new snapshot as requested by the SRS? The SRC also
need
> to
> > > > keep track of metadata changes while waiting for the timer. I
> worry
> > > that
> > > > it will make the solution more complicated than just using an
> INFO
> > > for
> > > > snapshot request and minimize the collision problem.
> > >
> > > OK, collision on update is a *possibility*.
> > > I guess the question is whether that justifies implementing an
> > entirely
> > > different mechanism just for the rare error message.
> > >
> > > I expect that the likelihood of collision is pretty slim, given
> that
> > > messages from the SRS to the SRC will be very infrequent, and if
> the
> > > message comes shortly after a metadata is received from the SRC,
> there
> > > may be little likelihood that the SRC will be sending more
metadata
> so
> > > soon. And even if we don't use UPDATE for this, the SRC, like any
> UA,
> > > needs to be prepared to cope with a collision of this sort.
> > >
> > > But I don't feel *too* strongly about this.
> > >
> > > 	Thanks,
> > > 	Paul
> > >
> > > > Regards,
> > > > Henry
> > > >
> > > >> -----Original Message-----
> > > >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> On
> > > >> Behalf Of Paul Kyzivat
> > > >> Sent: Tuesday, March 01, 2011 1:50 PM
> > > >> To: siprec@ietf.org
> > > >> Subject: Re: [siprec] FW: New Version Notificationfor
> > draft-portman-
> > > >> siprec-protocol-03
> > > >>
> > > >> Thanks Henry.
> > > >>
> > > >> One comment/question:
> > > >>
> > > >> Is there a reason to use an Info package for Requesting for
> > metadata
> > > >> snapshot? Since we are already defining c-d recording-session
> and
> > > >> passing bodies in invite/update for it, is there a reason not
to
> > use
> > > >> the
> > > >> same mechanism to send error notifications/snapshop requests?
> > > >>
> > > >> (I'm thinking just using a different content-type for this, and
> of
> > > >> course sending it from SRS to SRC.)
> > > >>
> > > >> Also, we could consider permitting (not requiring) this in the
> > > >> responses
> > > >> to the messages containing metadata.
> > > >>
> > > >> 	Thanks,
> > > >> 	Paul
> > > >>
> > > >>
> > > >> On 3/1/2011 12:13 PM, Henry Lum wrote:
> > > >>> A new version has been submitted to address the outstanding
> issues
> > > >> and include extensions for the new wording for REQ-017 and
> REQ-018.
> > > >>>
> > > >>>
https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
> > > >>>
> > > >>> Regards,
> > > >>> Henry
> > > >>>
> > > >>> -----Original Message-----
> > > >>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> > > >>> Sent: Tuesday, March 01, 2011 12:09 PM
> > > >>> To: Henry Lum
> > > >>> Cc: leon.portman@nice.com; alan.b.johnston@gmail.com;
> > > >> andrew.hutton@siemens-enterprise.com
> > > >>> Subject: New Version Notification for draft-portman-siprec-
> > > protocol-
> > > >> 03
> > > >>>
> > > >>>
> > > >>> A new version of I-D, draft-portman-siprec-protocol-03.txt has
> > been
> > > >> successfully submitted by Henry Lum and posted to the IETF
> > > repository.
> > > >>>
> > > >>> Filename:	 draft-portman-siprec-protocol
> > > >>> Revision:	 03
> > > >>> Title:		 The SIP-based Media Recording Protocol
> (SIPREC)
> > > >>> Creation_date:	 2011-03-01
> > > >>> WG ID:		 Independent Submission
> > > >>> Number_of_pages: 20
> > > >>>
> > > >>> Abstract:
> > > >>> SIPREC Session Recording Protocol is used for establishing
> > > recording
> > > >>> session and reporting of the metadata of the communication
> > session.
> > > >>>
> > > >>> This document specifies the SIPREC Protocol (SIPREC).  SIPREC
> is
> > > > used
> > > >>> between Session Recording Client (SRC) and Session Recording
> > Server
> > > >>> (SRS).
> > > >>>
> > > >>>
> > > >>>
> > > >>> The IETF Secretariat.
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >
> >
---------------------------------------------------------------------
> > > >> ----------------------------------------------
> > > >>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > > >> contain confidential and proprietary information of
> Alcatel-Lucent
> > > >> and/or its affiliated entities. Access by the intended
recipient
> > > only
> > > >> is authorized. Any liability arising from any party acting, or
> > > >> refraining from acting, on any information contained in this
> e-mail
> > > is
> > > >> hereby excluded. If you are not the intended recipient, please
> > > notify
> > > >> the sender immediately, destroy the original transmission and
> its
> > > >> attachments and do not disclose the contents to any other
> person,
> > > use
> > > >> it for any purpose, or store or copy the information in any
> medium.
> > > >> Copyright in this e-mail and any attachments belongs to
Alcatel-
> > > Lucent
> > > >> and/or its affiliated entities.
> > > >>>
> > > >>> _______________________________________________
> > > >>> 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
> > > >
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > ----------------------------------------------
> > > > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > > contain confidential and proprietary information of Alcatel-Lucent
> > > and/or its affiliated entities. Access by the intended recipient
> only
> > > is authorized. Any liability arising from any party acting, or
> > > refraining from acting, on any information contained in this
e-mail
> is
> > > hereby excluded. If you are not the intended recipient, please
> notify
> > > the sender immediately, destroy the original transmission and its
> > > attachments and do not disclose the contents to any other person,
> use
> > > it for any purpose, or store or copy the information in any
medium.
> > > Copyright in this e-mail and any attachments belongs to
> Alcatel-Lucent
> > > and/or its affiliated entities.
> > > >
> > > >
> >
> >
> >
>
-----------------------------------------------------------------------
> -
> ------------------------------
> > -------------
> > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> contain
> confidential and proprietary
> > information of Alcatel-Lucent and/or its affiliated entities. Access
> by the intended recipient only is
> > authorized. Any liability arising from any party acting, or
> refraining
> from acting, on any information
> > contained in this e-mail is hereby excluded. If you are not the
> intended recipient, please notify the
> > sender immediately, destroy the original transmission and its
> attachments and do not disclose the
> > contents to any other person, use it for any purpose, or store or
> copy
> the information in any medium.
> > Copyright in this e-mail and any attachments belongs to Alcatel-
> Lucent
> and/or its affiliated entities.
> >
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From Henry.Lum@alcatel-lucent.com  Fri Mar  4 09:39:32 2011
Return-Path: <Henry.Lum@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89ECB28B56A for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 09:39:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qZ-YBSNubYN for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 09:39:31 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 223C13A67F1 for <siprec@ietf.org>; Fri,  4 Mar 2011 09:39:31 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p24Hecr8019046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 4 Mar 2011 11:40:39 -0600 (CST)
Received: from relay-out2.dc (relay-out2.dc.genesyslab.com [172.22.68.188]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p24HebF1032278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 4 Mar 2011 11:40:38 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out2.dc (8.13.8+Sun/8.13.8) with ESMTP id p24Hea8U024143; Fri, 4 Mar 2011 09:40:36 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.93]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Mar 2011 09:40:36 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Mar 2011 09:40:36 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7406C36B68@NAHALD.us.int.genesyslab.com>
In-Reply-To: <4D70423D.7030202@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Synchronous vs Asynchronous Error handling
Thread-Index: AcvaDKuEWDOXgWbeSi2vsnbpua5CXgAhZ5sw
References: <A11921905DA1564D9BCF64A6430A62390293A665@XMB-BGL-411.cisco.com><4D67EC69.7080507@cisco.com><059AF07365DC474393A19A3AF187DF7406BADEA6@NAHALD.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2BAA742@MCHP058A.global-ad.net><4D6BBDAE.3020808@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE02F@NAHALD.us.int.genesyslab.com><07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A623904A63B8A@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB991A@xmb-sjc-234.amer.cisco.com> <4D70423D.7030202@cisco.com>
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
X-OriginalArrivalTime: 04 Mar 2011 17:40:36.0523 (UTC) FILETIME=[45240FB0:01CBDA93]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: Leon Portman <Leon.Portman@nice.com>, siprec@ietf.org
Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 17:39:32 -0000

SDP processing and metadata processing should be handled independently
and that you can still answer the SDP without requiring metadata to be
processed first. Even though metadata is referencing the label attribute
in the SDP, SDP is not dependent on the metadata.

I also agree that if the SRS can actually interpret and process metadata
in the UPDATE/INVITE request, then it is up to the implementation to do
so. I think what's more important is that we should not need a positive
acknowledgement from the SRS before SRC sends the next metadata update
so that the protocol does not become too chatty. The only
acknowledgement the SRC needs is that the message is received by the SRS
by way of getting a final response in the INVITE/UPDATE.

Regards,
Henry

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Thursday, March 03, 2011 8:37 PM
> To: Charles Eckel (eckelcu)
> Cc: Parthasarathi R (partr); Leon Portman; Henry Lum; Elwell, John;
> siprec@ietf.org
> Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
>=20
> Charles,
>=20
> Its my expectation that none of the metadata *need* be processed in
> order to answer an sdp offer. However the sdp will typically be
> required
> to supplement the metadata processing. So it likely will be necessary
> to
> queue the xml+sdp for later processing as metadata.
>=20
> One might want to make decisions about how to construct the answer
> (e.g.
> whether to accept or reject a media stream) based on the xml metadata.
> If one is capable of doing all the processing synchronously in order
to
> do so, go for it. But nobody should be forced to do that.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/3/2011 6:41 PM, Charles Eckel (eckelcu) wrote:
> > Hi Partha,
> >
> > I think we need both. If the error is detected in SDP processing,
> > handling it in the SIP response synchronously makes sense. If the
> error
> > is detected in the metadata processing, it would ideally be handled
> in
> > the SIP response synchronously, but it may result in a subsequent
> > request being sent to indicate and/or recover from the error. Errors
> may
> > also be encountered independent of any SIP request processing, and
> those
> > will need to be handled asynchronously.
> > So I think we need both, and how much of the XML to process
> > synchronously is up to the answerer. Ideally we will structure the
> XML
> > such that it is as clear and efficient as possible to identify the
> XML
> > that directly impacts the SDP. This will facilitate synchronous
> > responses.
> >
> > Cheers,
> > Charles
> >
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Parthasarathi R (partr)
> >> Sent: Wednesday, March 02, 2011 5:48 AM
> >> To: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
> >> Cc: siprec@ietf.org
> >> Subject: [siprec] Synchronous vs Asynchronous Error handling
> >>
> >> Hi all,
> >>
> >> Another issue discussed as part of the below mail thread is whether
> >> metadata (XML+SDP) error has to be responded synchronously (SIP
> >> Request/[SIP provisional response]/SIP Response) or
> asynchronously(SIP
> >> Request/SIP Response/SIP Error request/SIP Error response).
> >>
> >> Synchronous Error handling:
> >>  From SRC perspective, synchronous error handling is simple to
> > implement
> >> as there is no extra context or state to be maintained about the
> > earlier
> >> SIP transactions.
> >>
> >> In SRS, SDP Metadata portion *MUST* be processed in synchronously
to
> >> meet offer/answer model requirement. Now the question is whether
XML
> >> takes so much of a time wherein the error MUST be handled
> > asynchronous?
> >> The simple SRS will be able to send provisional response and
respond
> >> back final response once the complete XML check is done. My
> reasoning
> > is
> >> so because B2BUA normally handles INVITE/RE-INVITE in a way that
> send
> >> (100 trying) provisional response to the incoming dialog side, send
> >> INVITE/RE-INVITE to the outgoing dialog side which may take upto 32
> > sec
> >> delay to respond and forwards 200 OK to incoming dialog side once
it
> > is
> >> received from outgoing dialog side and it is well working deployed
> >> model. Please let me know in which situation this mechanism has
> issues
> >> specific to SIPREC&  XML.
> >>
> >> Asynchronous Error handling:
> >> Here as well in SRS, SDP Metadata portion *MUST* be processed in
> >> synchronously to meet offer/answer model requirement.
> >>
> >> Two cases exists from SRC perspective.
> >> 1) In case the sequence number has to be maintained by SRC for
> >> asynchronous error handling, then it *MAY* require SRC to maintain
> the
> >> earlier transaction which is overkill as SRC will not keep track or
> >> record its previous state.
> >>
> >> 2) In most of the scenario, it is not possible to re-record but it
> is
> >> only possible to re-sync. In case the motivation of asynchronous
> error
> >> is to re-sync metadata by SRS to SRC, it is very similar to SRS
> >> requesting for current complete metadata (SDP+XML) from SRC. On
> >> receiving re-sync request, SRC has to trigger the complete metadata
> >> towards SRS. The sequence number from SRS *MAY* be used for logging
> >> purpose if required.
> >>
> >> Please let me know which one of the above asynchronous behavior is
> >> expected from SRC. Also, instead of asynchronous error message, do
> you
> >> wish to create re-sync request mechanism from SRS which may be used
> > for
> >> error or other purpose as well.
> >>
> >> Thanks
> >> Partha
> >>
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf
> >> Of Leon Portman
> >> Sent: Monday, February 28, 2011 9:48 PM
> >> To: Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
> >> Cc: siprec@ietf.org
> >> Subject: Re: [siprec] Metadata XML document error representation
> >> forwhole doc or for portion of doc
> >>
> >> +1
> >>
> >> Leon
> >>
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf
> >> Of Henry Lum
> >> Sent: Monday, February 28, 2011 6:13 PM
> >> To: Paul Kyzivat; Elwell, John
> >> Cc: siprec@ietf.org
> >> Subject: Re: [siprec] Metadata XML document error representation
for
> >> whole doc or for portion of doc
> >>
> >>
> >>
> >>>>> We are also thinking of providing the SRS with a mechanism to
> >>>>> request the SRC to ask for the current snapshot
> >>> so
> >>>>> that the SRC/SRS can reset the states in the case where SRS is
in
> > a
> >>
> >>>>> really bad state. By doing so, we may be able to avoid providing
> >>> nack
> >>>>> responses and avoid using a chatty protocol.
> >>>> [JRE] Yes, and the request to resend full metadata could
> > optionally
> >>> include some sort of error report that gave rise to the request.
> > That
> >>> error report could, for example, include the sequence number of
the
> >>> metadata update that was found to be in error.
> >>>
> >>> That is sort of what I had in mind about getting the two sides in
> >> sync.
> >>> But we will have to think more about exactly what it means.
> >>> At best I think it will describe the *current* state of things in
> > this
> >>
> >>> RS, without regard to what has happened in the past.
> >>>
> >>> Even that may present some technical challenges. But we should
keep
> >>> this desire in mind.
> >>
> >> [[hlum]] I agree it would be reasonable for the SRC to send the
> > current
> >> state as a snapshot and forget what happened previously. The
> > subsequent
> >> sequence numbers only refers to the current snapshot rather than
the
> >> original one, so in a way we are resetting the sequence number.
> >>
> >>
> >>
> >
---------------------------------------------------------------------
> ---
> >> -------------------------------------------
> >> CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> contain
> >> confidential and proprietary information of Alcatel-Lucent and/or
> its
> >> affiliated entities. Access by the intended recipient only is
> >> authorized. Any liability arising from any party acting, or
> refraining
> >> from acting, on any information contained in this e-mail is hereby
> >> excluded. If you are not the intended recipient, please notify the
> >> sender immediately, destroy the original transmission and its
> >> attachments and do not disclose the contents to any other person,
> use
> > it
> >> for any purpose, or store or copy the information in any medium.
> >> Copyright in this e-mail and any attachments belongs to Alcatel-
> Lucent
> >> and/or its affiliated entities.
> >>
> >> _______________________________________________
> >> 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
> >

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From eckelcu@cisco.com  Fri Mar  4 09:45:29 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 262913A67F1 for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 09:45:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.566
X-Spam-Level: 
X-Spam-Status: No, score=-10.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SRd04twU-RkG for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 09:45:27 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 7B34B28B56A for <siprec@ietf.org>; Fri,  4 Mar 2011 09:45:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=14162; q=dns/txt; s=iport; t=1299260797; x=1300470397; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=GhTl9ibGoVVlZ5CxpZ5VlCZlW0toT11z33bd6+4S1cs=; b=bZitQyz+lMudeEJDDpmNFOxRyTAMpwocz+9bTT0L+eng7meQQ0vwccNu et3yl0Cz+evcflaDa6O+yo5B8NWaI9Awop3Bd1fxfjKGT1azgAcMkWuEt BSRrDCg3ygLkDo5Tb2Kv8xIff9oNqGinK42CTC5bnIXh/VW1XHIbF5VCr M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkBAGO0cE2rRN+K/2dsb2JhbACYJ448dKNXm2qFYQSFHIpcgxQ
X-IronPort-AV: E=Sophos;i="4.62,264,1297036800"; d="scan'208";a="273779787"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-3.cisco.com with ESMTP; 04 Mar 2011 17:46:36 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p24HkaXx025113; Fri, 4 Mar 2011 17:46:36 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Mar 2011 09:46:36 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Mar 2011 09:46:35 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9ABD@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <059AF07365DC474393A19A3AF187DF7406C36B5D@NAHALD.us.int.genesyslab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
Thread-Index: AcvYdoq1VttmMUOCSj+I/EBWiH/OmQAgjaaAADyUJVAAKMzRwAAA9vCQ
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com><4D6D3FE5.9000902@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com><4D6D98DC.8080008@cisco.com> <059AF07365DC474393A19A3AF187DF7406BAE5C6@NAHALD.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB987B@xmb-sjc-234.amer.cisco.com> <059AF07365DC474393A19A3AF187DF7406C36B5D@NAHALD.us.int.genesyslab.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Henry Lum" <Henry.Lum@alcatel-lucent.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Mar 2011 17:46:36.0550 (UTC) FILETIME=[1BBBD260:01CBDA94]
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 17:45:29 -0000

Hi Henry,

Please see inline.

> -----Original Message-----
> From: Henry Lum [mailto:Henry.Lum@alcatel-lucent.com]
> Sent: Friday, March 04, 2011 9:29 AM
> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] FW: New VersionNotificationfor
draft-portman-siprec-protocol-03
>=20
> Please see inline.
>=20
> > -----Original Message-----
> > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > Sent: Thursday, March 03, 2011 4:55 PM
> > To: Henry Lum; Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] FW: New VersionNotificationfor draft-portman-
> > siprec-protocol-03
> >
> > I think it is better to stick to using UPDATE and not introduce a
need
> > to use INFO. I would also expect that using re-INVITE instead of
> > UPDATE,
> > though not explicitly recommended, would work as well. What drives
> this
> > is the inclusion of the newly defined tags and the actual metadata.
> >
> [[hlum]] Okay - let's hear if there are supporters for INFO before
> making a change.

Okay.

> > Section 5 reads,
> >
> >    The SRC must be able to accept re-INVITE from SRS with the
updated
> >    SDP as part of the session timer mechanism.
> >
> > What is the purpose of stating this?
> > I agree the SRC needs to be able
> > to
> > accept a re-INVITE with updated or non-updated SDP from the SRS. It
> > also
> > needs to be able to receive an UPDATE with updated or non-updated
SDP.
> > This appears to me to be independent of using session timer, and I
do
> > not believe we are mandating support for session timer either.
>=20
> [[hlum]] Perhaps the wording may be a bit too explicit, but the
> intention is that a recording session should use session timer since
the
> SRS never sends any media to the SRC and the SRC needs a way to tell
> that the SRS is still around. I don't think session timer needs to be
> mandated but I think it is recommended that we use it.

I am not a fan of that. I think session timer is optional. What is
mandatory in my opinion is that the SRS sends RTCP messages, and that
lets you know if is there and receiving the media. It also should do
something to make sure the RTP port does not get closed by a
firewall/NAT, and there are several mechanisms for that. That said, this
is not specific to SIPREC, so I do not think we need explicit
requirements, but if we are providing recommendations those are the one
I suggest providing.

> >
> > In section 6.2, what does the "record" attribute and the defined
> > "indication" attribute give us that we do not already have using
> > sendonly and inactive, where off/pause maps to inactive and on maps
to
> > sendonly?
>=20
> [[hlum]] a=3Dsendrev/sendonly/recvonly describes the directionality of
the
> actual media stream in the CS. What we want is an indication on the CS
> media streams where recording is actually taking place or not, and
that
> should not involve changing the directionality of the actual media
> stream.
> On the recording session media streams, we do use =
a=3Dsendrecv/sendonly
to
> indicate pause/resume.

I see. This is really needed between the UA and the SRC, even if not
needed between the SRC and the SRS.
=20
> >
> > In section 6.3, recording preference, do we really need pause and
> > resume? I am thinking record and norecord may be sufficient.
> >
> [[hlum]] The current consensus for the new wording of REQ-017 includes
> pause and resume:
>=20
> "REQ-zzz The mechanism MUST support a means for a recording-aware UA
> involved in a CS to request during a session that the recording of the
> CS should be started, paused, resumed or stopped, the honoring of such
a
> request being dependent on policy."

Here as well, it may not be needed between the SRC and the SRS, but
between a UA and a SRC, is that correct.

Thanks,
Charles

> > Cheers,
> > Charles
> >
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Henry Lum
> > > Sent: Wednesday, March 02, 2011 8:45 AM
> > > To: Paul Kyzivat (pkyzivat)
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] FW: New VersionNotificationfor
> > draft-portman-siprec-protocol-03
> > >
> > > I don't feel strongly too about using INFO so I am open to using
> > UPDATE
> > > if the group feels that it is okay for SRC/SRS to deal with the
> > > consequences of UPDATE collision.
> > >
> > > Henry
> > >
> > > > -----Original Message-----
> > > > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > > > Sent: Tuesday, March 01, 2011 8:10 PM
> > > > To: Henry Lum
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] FW: New Version Notificationfor draft-
> > portman-
> > > > siprec-protocol-03
> > > >
> > > >
> > > >
> > > > On 3/1/2011 2:32 PM, Henry Lum wrote:
> > > > > When there is an UPDATE transaction collision, you will have
to
> > make
> > > > > both SRC and SRS to wait a while before being able to send
> UPDATE
> > > > again.
> > > > > Since SRC is normally the side initiating the SIP dialog, it
is
> > the
> > > > > owner of the Call-ID and will come second after the SRS has a
> > chance
> > > > to
> > > > > resend the UPDATE. In that case, does the SRC keep the
existing
> > > > UPDATE
> > > > > or send a new snapshot as requested by the SRS? The SRC also
> need
> > to
> > > > > keep track of metadata changes while waiting for the timer. I
> > worry
> > > > that
> > > > > it will make the solution more complicated than just using an
> > INFO
> > > > for
> > > > > snapshot request and minimize the collision problem.
> > > >
> > > > OK, collision on update is a *possibility*.
> > > > I guess the question is whether that justifies implementing an
> > > entirely
> > > > different mechanism just for the rare error message.
> > > >
> > > > I expect that the likelihood of collision is pretty slim, given
> > that
> > > > messages from the SRS to the SRC will be very infrequent, and if
> > the
> > > > message comes shortly after a metadata is received from the SRC,
> > there
> > > > may be little likelihood that the SRC will be sending more
> metadata
> > so
> > > > soon. And even if we don't use UPDATE for this, the SRC, like
any
> > UA,
> > > > needs to be prepared to cope with a collision of this sort.
> > > >
> > > > But I don't feel *too* strongly about this.
> > > >
> > > > 	Thanks,
> > > > 	Paul
> > > >
> > > > > Regards,
> > > > > Henry
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: siprec-bounces@ietf.org
[mailto:siprec-bounces@ietf.org]
> > On
> > > > >> Behalf Of Paul Kyzivat
> > > > >> Sent: Tuesday, March 01, 2011 1:50 PM
> > > > >> To: siprec@ietf.org
> > > > >> Subject: Re: [siprec] FW: New Version Notificationfor
> > > draft-portman-
> > > > >> siprec-protocol-03
> > > > >>
> > > > >> Thanks Henry.
> > > > >>
> > > > >> One comment/question:
> > > > >>
> > > > >> Is there a reason to use an Info package for Requesting for
> > > metadata
> > > > >> snapshot? Since we are already defining c-d recording-session
> > and
> > > > >> passing bodies in invite/update for it, is there a reason not
> to
> > > use
> > > > >> the
> > > > >> same mechanism to send error notifications/snapshop requests?
> > > > >>
> > > > >> (I'm thinking just using a different content-type for this,
and
> > of
> > > > >> course sending it from SRS to SRC.)
> > > > >>
> > > > >> Also, we could consider permitting (not requiring) this in
the
> > > > >> responses
> > > > >> to the messages containing metadata.
> > > > >>
> > > > >> 	Thanks,
> > > > >> 	Paul
> > > > >>
> > > > >>
> > > > >> On 3/1/2011 12:13 PM, Henry Lum wrote:
> > > > >>> A new version has been submitted to address the outstanding
> > issues
> > > > >> and include extensions for the new wording for REQ-017 and
> > REQ-018.
> > > > >>>
> > > > >>>
> https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
> > > > >>>
> > > > >>> Regards,
> > > > >>> Henry
> > > > >>>
> > > > >>> -----Original Message-----
> > > > >>> From: IETF I-D Submission Tool
[mailto:idsubmission@ietf.org]
> > > > >>> Sent: Tuesday, March 01, 2011 12:09 PM
> > > > >>> To: Henry Lum
> > > > >>> Cc: leon.portman@nice.com; alan.b.johnston@gmail.com;
> > > > >> andrew.hutton@siemens-enterprise.com
> > > > >>> Subject: New Version Notification for draft-portman-siprec-
> > > > protocol-
> > > > >> 03
> > > > >>>
> > > > >>>
> > > > >>> A new version of I-D, draft-portman-siprec-protocol-03.txt
has
> > > been
> > > > >> successfully submitted by Henry Lum and posted to the IETF
> > > > repository.
> > > > >>>
> > > > >>> Filename:	 draft-portman-siprec-protocol
> > > > >>> Revision:	 03
> > > > >>> Title:		 The SIP-based Media Recording Protocol
> > (SIPREC)
> > > > >>> Creation_date:	 2011-03-01
> > > > >>> WG ID:		 Independent Submission
> > > > >>> Number_of_pages: 20
> > > > >>>
> > > > >>> Abstract:
> > > > >>> SIPREC Session Recording Protocol is used for establishing
> > > > recording
> > > > >>> session and reporting of the metadata of the communication
> > > session.
> > > > >>>
> > > > >>> This document specifies the SIPREC Protocol (SIPREC).
SIPREC
> > is
> > > > > used
> > > > >>> between Session Recording Client (SRC) and Session Recording
> > > Server
> > > > >>> (SRS).
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> The IETF Secretariat.
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > >> ----------------------------------------------
> > > > >>> CONFIDENTIALITY NOTICE: This e-mail and any files attached
may
> > > > >> contain confidential and proprietary information of
> > Alcatel-Lucent
> > > > >> and/or its affiliated entities. Access by the intended
> recipient
> > > > only
> > > > >> is authorized. Any liability arising from any party acting,
or
> > > > >> refraining from acting, on any information contained in this
> > e-mail
> > > > is
> > > > >> hereby excluded. If you are not the intended recipient,
please
> > > > notify
> > > > >> the sender immediately, destroy the original transmission and
> > its
> > > > >> attachments and do not disclose the contents to any other
> > person,
> > > > use
> > > > >> it for any purpose, or store or copy the information in any
> > medium.
> > > > >> Copyright in this e-mail and any attachments belongs to
> Alcatel-
> > > > Lucent
> > > > >> and/or its affiliated entities.
> > > > >>>
> > > > >>> _______________________________________________
> > > > >>> 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
> > > > >
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > ----------------------------------------------
> > > > > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > > > contain confidential and proprietary information of
Alcatel-Lucent
> > > > and/or its affiliated entities. Access by the intended recipient
> > only
> > > > is authorized. Any liability arising from any party acting, or
> > > > refraining from acting, on any information contained in this
> e-mail
> > is
> > > > hereby excluded. If you are not the intended recipient, please
> > notify
> > > > the sender immediately, destroy the original transmission and
its
> > > > attachments and do not disclose the contents to any other
person,
> > use
> > > > it for any purpose, or store or copy the information in any
> medium.
> > > > Copyright in this e-mail and any attachments belongs to
> > Alcatel-Lucent
> > > > and/or its affiliated entities.
> > > > >
> > > > >
> > >
> > >
> > >
> >
>
-----------------------------------------------------------------------
> > -
> > ------------------------------
> > > -------------
> > > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > contain
> > confidential and proprietary
> > > information of Alcatel-Lucent and/or its affiliated entities.
Access
> > by the intended recipient only is
> > > authorized. Any liability arising from any party acting, or
> > refraining
> > from acting, on any information
> > > contained in this e-mail is hereby excluded. If you are not the
> > intended recipient, please notify the
> > > sender immediately, destroy the original transmission and its
> > attachments and do not disclose the
> > > contents to any other person, use it for any purpose, or store or
> > copy
> > the information in any medium.
> > > Copyright in this e-mail and any attachments belongs to Alcatel-
> > Lucent
> > and/or its affiliated entities.
> > >
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
>=20
>=20
>
------------------------------------------------------------------------
------------------------------
> -------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary
> information of Alcatel-Lucent and/or its affiliated entities. Access
by the intended recipient only is
> authorized. Any liability arising from any party acting, or refraining
from acting, on any information
> contained in this e-mail is hereby excluded. If you are not the
intended recipient, please notify the
> sender immediately, destroy the original transmission and its
attachments and do not disclose the
> contents to any other person, use it for any purpose, or store or copy
the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
>=20

From Henry.Lum@alcatel-lucent.com  Fri Mar  4 10:01:43 2011
Return-Path: <Henry.Lum@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE4883A6830 for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 10:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rT1dE9LAn9Z6 for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 10:01:42 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 08DFB3A6818 for <siprec@ietf.org>; Fri,  4 Mar 2011 10:01:41 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p24I2l6Z005750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 4 Mar 2011 12:02:48 -0600 (CST)
Received: from relay-out1.dc.genesyslab.com (relay-out1.dc.genesyslab.com [172.22.68.187]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p24I2jLY021813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 4 Mar 2011 12:02:47 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.dc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id p24I2j8L009614; Fri, 4 Mar 2011 10:02:45 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.93]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Mar 2011 10:02:45 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Mar 2011 10:02:44 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7406C36B88@NAHALD.us.int.genesyslab.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9ABD@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
Thread-Index: AcvYdoq1VttmMUOCSj+I/EBWiH/OmQAgjaaAADyUJVAAKMzRwAAA9vCQAAC4CSA=
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com><4D6D3FE5.9000902@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com><4D6D98DC.8080008@cisco.com> <059AF07365DC474393A19A3AF187DF7406BAE5C6@NAHALD.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB987B@xmb-sjc-234.amer.cisco.com> <059AF07365DC474393A19A3AF187DF7406C36B5D@NAHALD.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9ABD@xmb-sjc-234.amer.cisco.com>
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Mar 2011 18:02:45.0327 (UTC) FILETIME=[5D2B75F0:01CBDA96]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 18:01:44 -0000

Inline.

> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: Friday, March 04, 2011 12:47 PM
> To: Henry Lum; Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] FW: New VersionNotificationfor draft-portman-
> siprec-protocol-03
>=20
> Hi Henry,
>=20
> Please see inline.
>=20
> > -----Original Message-----
> > From: Henry Lum [mailto:Henry.Lum@alcatel-lucent.com]
> > Sent: Friday, March 04, 2011 9:29 AM
> > To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] FW: New VersionNotificationfor
> draft-portman-siprec-protocol-03
> >
> > Please see inline.
> >
> > > -----Original Message-----
> > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > Sent: Thursday, March 03, 2011 4:55 PM
> > > To: Henry Lum; Paul Kyzivat (pkyzivat)
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] FW: New VersionNotificationfor
draft-portman-
> > > siprec-protocol-03
> > >
> > > I think it is better to stick to using UPDATE and not introduce a
> need
> > > to use INFO. I would also expect that using re-INVITE instead of
> > > UPDATE,
> > > though not explicitly recommended, would work as well. What drives
> > this
> > > is the inclusion of the newly defined tags and the actual
metadata.
> > >
> > [[hlum]] Okay - let's hear if there are supporters for INFO before
> > making a change.
>=20
> Okay.
>=20
> > > Section 5 reads,
> > >
> > >    The SRC must be able to accept re-INVITE from SRS with the
> updated
> > >    SDP as part of the session timer mechanism.
> > >
> > > What is the purpose of stating this?
> > > I agree the SRC needs to be able
> > > to
> > > accept a re-INVITE with updated or non-updated SDP from the SRS.
It
> > > also
> > > needs to be able to receive an UPDATE with updated or non-updated
> SDP.
> > > This appears to me to be independent of using session timer, and I
> do
> > > not believe we are mandating support for session timer either.
> >
> > [[hlum]] Perhaps the wording may be a bit too explicit, but the
> > intention is that a recording session should use session timer since
> the
> > SRS never sends any media to the SRC and the SRC needs a way to tell
> > that the SRS is still around. I don't think session timer needs to
be
> > mandated but I think it is recommended that we use it.
>=20
> I am not a fan of that. I think session timer is optional. What is
> mandatory in my opinion is that the SRS sends RTCP messages, and that
> lets you know if is there and receiving the media. It also should do
> something to make sure the RTP port does not get closed by a
> firewall/NAT, and there are several mechanisms for that. That said,
> this
> is not specific to SIPREC, so I do not think we need explicit
> requirements, but if we are providing recommendations those are the
one
> I suggest providing.

[[hlum]] Agreed that this problem is not specific to SIPREC. The SRS
does not send RTP to the SRC so I don't think it matters when that RTP
port gets closed, but it makes sense to for SRS to send RTCP messages to
the SRC to acknowledge receipt of recorded media. Do we need to mandate
this?

>=20
> > >
> > > In section 6.2, what does the "record" attribute and the defined
> > > "indication" attribute give us that we do not already have using
> > > sendonly and inactive, where off/pause maps to inactive and on
maps
> to
> > > sendonly?
> >
> > [[hlum]] a=3Dsendrev/sendonly/recvonly describes the directionality o=
f
> the
> > actual media stream in the CS. What we want is an indication on the
> CS
> > media streams where recording is actually taking place or not, and
> that
> > should not involve changing the directionality of the actual media
> > stream.
> > On the recording session media streams, we do use
a=3Dsendrecv/sendonly
> to
> > indicate pause/resume.
>=20
> I see. This is really needed between the UA and the SRC, even if not
> needed between the SRC and the SRS.
>=20
> > >
> > > In section 6.3, recording preference, do we really need pause and
> > > resume? I am thinking record and norecord may be sufficient.
> > >
> > [[hlum]] The current consensus for the new wording of REQ-017
> includes
> > pause and resume:
> >
> > "REQ-zzz The mechanism MUST support a means for a recording-aware UA
> > involved in a CS to request during a session that the recording of
> the
> > CS should be started, paused, resumed or stopped, the honoring of
> such
> a
> > request being dependent on policy."
>=20
> Here as well, it may not be needed between the SRC and the SRS, but
> between a UA and a SRC, is that correct.
>=20
[[hlum]] Yes this mechanism is only for recording-aware UA in the CS.

> Thanks,
> Charles
>=20
> > > Cheers,
> > > Charles
> > >
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
On
> > > Behalf Of Henry Lum
> > > > Sent: Wednesday, March 02, 2011 8:45 AM
> > > > To: Paul Kyzivat (pkyzivat)
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] FW: New VersionNotificationfor
> > > draft-portman-siprec-protocol-03
> > > >
> > > > I don't feel strongly too about using INFO so I am open to using
> > > UPDATE
> > > > if the group feels that it is okay for SRC/SRS to deal with the
> > > > consequences of UPDATE collision.
> > > >
> > > > Henry
> > > >
> > > > > -----Original Message-----
> > > > > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > > > > Sent: Tuesday, March 01, 2011 8:10 PM
> > > > > To: Henry Lum
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] FW: New Version Notificationfor draft-
> > > portman-
> > > > > siprec-protocol-03
> > > > >
> > > > >
> > > > >
> > > > > On 3/1/2011 2:32 PM, Henry Lum wrote:
> > > > > > When there is an UPDATE transaction collision, you will have
> to
> > > make
> > > > > > both SRC and SRS to wait a while before being able to send
> > UPDATE
> > > > > again.
> > > > > > Since SRC is normally the side initiating the SIP dialog, it
> is
> > > the
> > > > > > owner of the Call-ID and will come second after the SRS has
a
> > > chance
> > > > > to
> > > > > > resend the UPDATE. In that case, does the SRC keep the
> existing
> > > > > UPDATE
> > > > > > or send a new snapshot as requested by the SRS? The SRC also
> > need
> > > to
> > > > > > keep track of metadata changes while waiting for the timer.
I
> > > worry
> > > > > that
> > > > > > it will make the solution more complicated than just using
an
> > > INFO
> > > > > for
> > > > > > snapshot request and minimize the collision problem.
> > > > >
> > > > > OK, collision on update is a *possibility*.
> > > > > I guess the question is whether that justifies implementing an
> > > > entirely
> > > > > different mechanism just for the rare error message.
> > > > >
> > > > > I expect that the likelihood of collision is pretty slim,
given
> > > that
> > > > > messages from the SRS to the SRC will be very infrequent, and
> if
> > > the
> > > > > message comes shortly after a metadata is received from the
> SRC,
> > > there
> > > > > may be little likelihood that the SRC will be sending more
> > metadata
> > > so
> > > > > soon. And even if we don't use UPDATE for this, the SRC, like
> any
> > > UA,
> > > > > needs to be prepared to cope with a collision of this sort.
> > > > >
> > > > > But I don't feel *too* strongly about this.
> > > > >
> > > > > 	Thanks,
> > > > > 	Paul
> > > > >
> > > > > > Regards,
> > > > > > Henry
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org]
> > > On
> > > > > >> Behalf Of Paul Kyzivat
> > > > > >> Sent: Tuesday, March 01, 2011 1:50 PM
> > > > > >> To: siprec@ietf.org
> > > > > >> Subject: Re: [siprec] FW: New Version Notificationfor
> > > > draft-portman-
> > > > > >> siprec-protocol-03
> > > > > >>
> > > > > >> Thanks Henry.
> > > > > >>
> > > > > >> One comment/question:
> > > > > >>
> > > > > >> Is there a reason to use an Info package for Requesting for
> > > > metadata
> > > > > >> snapshot? Since we are already defining c-d recording-
> session
> > > and
> > > > > >> passing bodies in invite/update for it, is there a reason
> not
> > to
> > > > use
> > > > > >> the
> > > > > >> same mechanism to send error notifications/snapshop
> requests?
> > > > > >>
> > > > > >> (I'm thinking just using a different content-type for this,
> and
> > > of
> > > > > >> course sending it from SRS to SRC.)
> > > > > >>
> > > > > >> Also, we could consider permitting (not requiring) this in
> the
> > > > > >> responses
> > > > > >> to the messages containing metadata.
> > > > > >>
> > > > > >> 	Thanks,
> > > > > >> 	Paul
> > > > > >>
> > > > > >>
> > > > > >> On 3/1/2011 12:13 PM, Henry Lum wrote:
> > > > > >>> A new version has been submitted to address the
outstanding
> > > issues
> > > > > >> and include extensions for the new wording for REQ-017 and
> > > REQ-018.
> > > > > >>>
> > > > > >>>
> > https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
> > > > > >>>
> > > > > >>> Regards,
> > > > > >>> Henry
> > > > > >>>
> > > > > >>> -----Original Message-----
> > > > > >>> From: IETF I-D Submission Tool
> [mailto:idsubmission@ietf.org]
> > > > > >>> Sent: Tuesday, March 01, 2011 12:09 PM
> > > > > >>> To: Henry Lum
> > > > > >>> Cc: leon.portman@nice.com; alan.b.johnston@gmail.com;
> > > > > >> andrew.hutton@siemens-enterprise.com
> > > > > >>> Subject: New Version Notification for
draft-portman-siprec-
> > > > > protocol-
> > > > > >> 03
> > > > > >>>
> > > > > >>>
> > > > > >>> A new version of I-D, draft-portman-siprec-protocol-03.txt
> has
> > > > been
> > > > > >> successfully submitted by Henry Lum and posted to the IETF
> > > > > repository.
> > > > > >>>
> > > > > >>> Filename:	 draft-portman-siprec-protocol
> > > > > >>> Revision:	 03
> > > > > >>> Title:		 The SIP-based Media Recording Protocol
> > > (SIPREC)
> > > > > >>> Creation_date:	 2011-03-01
> > > > > >>> WG ID:		 Independent Submission
> > > > > >>> Number_of_pages: 20
> > > > > >>>
> > > > > >>> Abstract:
> > > > > >>> SIPREC Session Recording Protocol is used for establishing
> > > > > recording
> > > > > >>> session and reporting of the metadata of the communication
> > > > session.
> > > > > >>>
> > > > > >>> This document specifies the SIPREC Protocol (SIPREC).
> SIPREC
> > > is
> > > > > > used
> > > > > >>> between Session Recording Client (SRC) and Session
> Recording
> > > > Server
> > > > > >>> (SRS).
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>> The IETF Secretariat.
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >
> > > >
> >
---------------------------------------------------------------------
> > > > > >> ----------------------------------------------
> > > > > >>> CONFIDENTIALITY NOTICE: This e-mail and any files attached
> may
> > > > > >> contain confidential and proprietary information of
> > > Alcatel-Lucent
> > > > > >> and/or its affiliated entities. Access by the intended
> > recipient
> > > > > only
> > > > > >> is authorized. Any liability arising from any party acting,
> or
> > > > > >> refraining from acting, on any information contained in
this
> > > e-mail
> > > > > is
> > > > > >> hereby excluded. If you are not the intended recipient,
> please
> > > > > notify
> > > > > >> the sender immediately, destroy the original transmission
> and
> > > its
> > > > > >> attachments and do not disclose the contents to any other
> > > person,
> > > > > use
> > > > > >> it for any purpose, or store or copy the information in any
> > > medium.
> > > > > >> Copyright in this e-mail and any attachments belongs to
> > Alcatel-
> > > > > Lucent
> > > > > >> and/or its affiliated entities.
> > > > > >>>
> > > > > >>> _______________________________________________
> > > > > >>> 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
> > > > > >
> > > > > >
> > > > > >
> > > >
> >
---------------------------------------------------------------------
> > > > > ----------------------------------------------
> > > > > > CONFIDENTIALITY NOTICE: This e-mail and any files attached
> may
> > > > > contain confidential and proprietary information of
> Alcatel-Lucent
> > > > > and/or its affiliated entities. Access by the intended
> recipient
> > > only
> > > > > is authorized. Any liability arising from any party acting, or
> > > > > refraining from acting, on any information contained in this
> > e-mail
> > > is
> > > > > hereby excluded. If you are not the intended recipient, please
> > > notify
> > > > > the sender immediately, destroy the original transmission and
> its
> > > > > attachments and do not disclose the contents to any other
> person,
> > > use
> > > > > it for any purpose, or store or copy the information in any
> > medium.
> > > > > Copyright in this e-mail and any attachments belongs to
> > > Alcatel-Lucent
> > > > > and/or its affiliated entities.
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> > >
> >
>
-----------------------------------------------------------------------
> > > -
> > > ------------------------------
> > > > -------------
> > > > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > > contain
> > > confidential and proprietary
> > > > information of Alcatel-Lucent and/or its affiliated entities.
> Access
> > > by the intended recipient only is
> > > > authorized. Any liability arising from any party acting, or
> > > refraining
> > > from acting, on any information
> > > > contained in this e-mail is hereby excluded. If you are not the
> > > intended recipient, please notify the
> > > > sender immediately, destroy the original transmission and its
> > > attachments and do not disclose the
> > > > contents to any other person, use it for any purpose, or store
or
> > > copy
> > > the information in any medium.
> > > > Copyright in this e-mail and any attachments belongs to Alcatel-
> > > Lucent
> > > and/or its affiliated entities.
> > > >
> > > > _______________________________________________
> > > > siprec mailing list
> > > > siprec@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/siprec
> >
> >
> >
>
-----------------------------------------------------------------------
> -
> ------------------------------
> > -------------
> > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> contain
> confidential and proprietary
> > information of Alcatel-Lucent and/or its affiliated entities. Access
> by the intended recipient only is
> > authorized. Any liability arising from any party acting, or
> refraining
> from acting, on any information
> > contained in this e-mail is hereby excluded. If you are not the
> intended recipient, please notify the
> > sender immediately, destroy the original transmission and its
> attachments and do not disclose the
> > contents to any other person, use it for any purpose, or store or
> copy
> the information in any medium.
> > Copyright in this e-mail and any attachments belongs to Alcatel-
> Lucent
> and/or its affiliated entities.
> >

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From pkyzivat@cisco.com  Fri Mar  4 10:10:37 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 081E43A677C for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 10:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.228
X-Spam-Level: 
X-Spam-Status: No, score=-110.228 tagged_above=-999 required=5 tests=[AWL=-0.229, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XvW61jy0Q5Dx for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 10:10:34 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 65C643A6838 for <siprec@ietf.org>; Fri,  4 Mar 2011 10:10:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=9113; q=dns/txt; s=iport; t=1299262304; x=1300471904; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=TDjsJkPvcd1+0P8U6mIbLYTZ5CCt+TvnbhMHoZQ+s48=; b=X8egmQ0bAkDtS8xQ0QDh9Xdw7PRjsTh24De3gD8FPbkvBQHru/leKN0H 3SnM4mtVfe2E/H9M8RqP3lFLjzbdHNq6GasAgnMLVlBfEnJs0/lSw1pTc 5trQ1vWCRXUEivxlirDvUFfFRT8sW4pCgXt1z0JtWgOzXo4s0v7Pjof1q c=;
X-IronPort-AV: E=Sophos;i="4.62,264,1297036800"; d="scan'208";a="222665444"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 04 Mar 2011 18:11:43 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p24IBhVR003152; Fri, 4 Mar 2011 18:11:43 GMT
Message-ID: <4D712B5F.40805@cisco.com>
Date: Fri, 04 Mar 2011 13:11:43 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <A11921905DA1564D9BCF64A6430A62390293A665@XMB-BGL-411.cisco.com><4D67EC69.7080507@cisco.com><059AF07365DC474393A19A3AF187DF7406BADEA6@NAHALD.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2BAA742@MCHP058A.global-ad.net><4D6BBDAE.3020808@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE02F@NAHALD.us.int.genesyslab.com><07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A623904A63B8A@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB991A@xmb-sjc-234.amer.cisco.com> <4D70423D.7030202@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9A9F@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9A9F@xmb-sjc-234.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Leon Portman <Leon.Portman@nice.com>, Henry Lum <Henry.Lum@alcatel-lucent.com>, siprec@ietf.org
Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 18:10:37 -0000

yes

On 3/4/2011 12:22 PM, Charles Eckel (eckelcu) wrote:
> Hi Paul,
>
> I think we are both saying the same thing, but let me make sure. In
> cases in which processing everything synchronously is not feasible, an
> implementation MUST send an SDP answer synchronously in order to
> complete the existing SIP transaction, then complete the processing of
> the metadata asynchronously, and if required, MAY send an offer in
> another SIP transaction to address and changes required.
>
> Cheers,
> Charles
>
>> -----Original Message-----
>> From: Paul Kyzivat (pkyzivat)
>> Sent: Thursday, March 03, 2011 5:37 PM
>> To: Charles Eckel (eckelcu)
>> Cc: Parthasarathi R (partr); Leon Portman; Henry Lum; Elwell, John;
> siprec@ietf.org
>> Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
>>
>> Charles,
>>
>> Its my expectation that none of the metadata *need* be processed in
>> order to answer an sdp offer. However the sdp will typically be
> required
>> to supplement the metadata processing. So it likely will be necessary
> to
>> queue the xml+sdp for later processing as metadata.
>>
>> One might want to make decisions about how to construct the answer
> (e.g.
>> whether to accept or reject a media stream) based on the xml metadata.
>> If one is capable of doing all the processing synchronously in order
> to
>> do so, go for it. But nobody should be forced to do that.
>>
>> 	Thanks,
>> 	Paul
>>
>> On 3/3/2011 6:41 PM, Charles Eckel (eckelcu) wrote:
>>> Hi Partha,
>>>
>>> I think we need both. If the error is detected in SDP processing,
>>> handling it in the SIP response synchronously makes sense. If the
> error
>>> is detected in the metadata processing, it would ideally be handled
> in
>>> the SIP response synchronously, but it may result in a subsequent
>>> request being sent to indicate and/or recover from the error. Errors
> may
>>> also be encountered independent of any SIP request processing, and
> those
>>> will need to be handled asynchronously.
>>> So I think we need both, and how much of the XML to process
>>> synchronously is up to the answerer. Ideally we will structure the
> XML
>>> such that it is as clear and efficient as possible to identify the
> XML
>>> that directly impacts the SDP. This will facilitate synchronous
>>> responses.
>>>
>>> Cheers,
>>> Charles
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf Of Parthasarathi R (partr)
>>>> Sent: Wednesday, March 02, 2011 5:48 AM
>>>> To: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
>>>> Cc: siprec@ietf.org
>>>> Subject: [siprec] Synchronous vs Asynchronous Error handling
>>>>
>>>> Hi all,
>>>>
>>>> Another issue discussed as part of the below mail thread is whether
>>>> metadata (XML+SDP) error has to be responded synchronously (SIP
>>>> Request/[SIP provisional response]/SIP Response) or
> asynchronously(SIP
>>>> Request/SIP Response/SIP Error request/SIP Error response).
>>>>
>>>> Synchronous Error handling:
>>>>   From SRC perspective, synchronous error handling is simple to
>>> implement
>>>> as there is no extra context or state to be maintained about the
>>> earlier
>>>> SIP transactions.
>>>>
>>>> In SRS, SDP Metadata portion *MUST* be processed in synchronously
> to
>>>> meet offer/answer model requirement. Now the question is whether
> XML
>>>> takes so much of a time wherein the error MUST be handled
>>> asynchronous?
>>>> The simple SRS will be able to send provisional response and
> respond
>>>> back final response once the complete XML check is done. My
> reasoning
>>> is
>>>> so because B2BUA normally handles INVITE/RE-INVITE in a way that
> send
>>>> (100 trying) provisional response to the incoming dialog side, send
>>>> INVITE/RE-INVITE to the outgoing dialog side which may take upto 32
>>> sec
>>>> delay to respond and forwards 200 OK to incoming dialog side once
> it
>>> is
>>>> received from outgoing dialog side and it is well working deployed
>>>> model. Please let me know in which situation this mechanism has
> issues
>>>> specific to SIPREC&   XML.
>>>>
>>>> Asynchronous Error handling:
>>>> Here as well in SRS, SDP Metadata portion *MUST* be processed in
>>>> synchronously to meet offer/answer model requirement.
>>>>
>>>> Two cases exists from SRC perspective.
>>>> 1) In case the sequence number has to be maintained by SRC for
>>>> asynchronous error handling, then it *MAY* require SRC to maintain
> the
>>>> earlier transaction which is overkill as SRC will not keep track or
>>>> record its previous state.
>>>>
>>>> 2) In most of the scenario, it is not possible to re-record but it
> is
>>>> only possible to re-sync. In case the motivation of asynchronous
> error
>>>> is to re-sync metadata by SRS to SRC, it is very similar to SRS
>>>> requesting for current complete metadata (SDP+XML) from SRC. On
>>>> receiving re-sync request, SRC has to trigger the complete metadata
>>>> towards SRS. The sequence number from SRS *MAY* be used for logging
>>>> purpose if required.
>>>>
>>>> Please let me know which one of the above asynchronous behavior is
>>>> expected from SRC. Also, instead of asynchronous error message, do
> you
>>>> wish to create re-sync request mechanism from SRS which may be used
>>> for
>>>> error or other purpose as well.
>>>>
>>>> Thanks
>>>> Partha
>>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf
>>>> Of Leon Portman
>>>> Sent: Monday, February 28, 2011 9:48 PM
>>>> To: Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] Metadata XML document error representation
>>>> forwhole doc or for portion of doc
>>>>
>>>> +1
>>>>
>>>> Leon
>>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf
>>>> Of Henry Lum
>>>> Sent: Monday, February 28, 2011 6:13 PM
>>>> To: Paul Kyzivat; Elwell, John
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] Metadata XML document error representation
> for
>>>> whole doc or for portion of doc
>>>>
>>>>
>>>>
>>>>>>> We are also thinking of providing the SRS with a mechanism to
>>>>>>> request the SRC to ask for the current snapshot
>>>>> so
>>>>>>> that the SRC/SRS can reset the states in the case where SRS is
> in
>>> a
>>>>
>>>>>>> really bad state. By doing so, we may be able to avoid providing
>>>>> nack
>>>>>>> responses and avoid using a chatty protocol.
>>>>>> [JRE] Yes, and the request to resend full metadata could
>>> optionally
>>>>> include some sort of error report that gave rise to the request.
>>> That
>>>>> error report could, for example, include the sequence number of
> the
>>>>> metadata update that was found to be in error.
>>>>>
>>>>> That is sort of what I had in mind about getting the two sides in
>>>> sync.
>>>>> But we will have to think more about exactly what it means.
>>>>> At best I think it will describe the *current* state of things in
>>> this
>>>>
>>>>> RS, without regard to what has happened in the past.
>>>>>
>>>>> Even that may present some technical challenges. But we should
> keep
>>>>> this desire in mind.
>>>>
>>>> [[hlum]] I agree it would be reasonable for the SRC to send the
>>> current
>>>> state as a snapshot and forget what happened previously. The
>>> subsequent
>>>> sequence numbers only refers to the current snapshot rather than
> the
>>>> original one, so in a way we are resetting the sequence number.
>>>>
>>>>
>>>>
>>>
> ------------------------------------------------------------------------
>>>> -------------------------------------------
>>>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> contain
>>>> confidential and proprietary information of Alcatel-Lucent and/or
> its
>>>> affiliated entities. Access by the intended recipient only is
>>>> authorized. Any liability arising from any party acting, or
> refraining
>>>> from acting, on any information contained in this e-mail is hereby
>>>> excluded. If you are not the intended recipient, please notify the
>>>> sender immediately, destroy the original transmission and its
>>>> attachments and do not disclose the contents to any other person,
> use
>>> it
>>>> for any purpose, or store or copy the information in any medium.
>>>> Copyright in this e-mail and any attachments belongs to
> Alcatel-Lucent
>>>> and/or its affiliated entities.
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>

From eckelcu@cisco.com  Fri Mar  4 10:13:54 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5850A3A6982 for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 10:13:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.569
X-Spam-Level: 
X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VdfniPrgYA8E for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 10:13:52 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 49AF93A6838 for <siprec@ietf.org>; Fri,  4 Mar 2011 10:13:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=18079; q=dns/txt; s=iport; t=1299262502; x=1300472102; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=56JIF2kVqGFNcVc+mo1znUw37iRj4DGjScp2yqlAHhs=; b=YdljDNOaiO/4QLgmNFn/1hqyyoapA8+9EcOfapjgIsxNtL1+7C4xEt+J 2XxW0OmxKVV4N5L4/aRq2ohNzhkH47fQLJrNlzPNvKvCr730ky3BTLWwv 945LlzKp5cC9da8C0c/IO+3xtTqpkh4kQfm/ixWnBRA+jztAxB5Dc7yab U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkBAGy7cE2rRN+K/2dsb2JhbACYJ448dKNDm2uFYQSFHIpcgxQ
X-IronPort-AV: E=Sophos;i="4.62,264,1297036800"; d="scan'208";a="273791705"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-3.cisco.com with ESMTP; 04 Mar 2011 18:15:01 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p24IF1q4011509; Fri, 4 Mar 2011 18:15:01 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Mar 2011 10:15:01 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Mar 2011 10:15:00 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9B09@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <059AF07365DC474393A19A3AF187DF7406C36B88@NAHALD.us.int.genesyslab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
Thread-Index: AcvYdoq1VttmMUOCSj+I/EBWiH/OmQAgjaaAADyUJVAAKMzRwAAA9vCQAAC4CSAAAKdlAA==
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com><4D6D3FE5.9000902@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com><4D6D98DC.8080008@cisco.com> <059AF07365DC474393A19A3AF187DF7406BAE5C6@NAHALD.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB987B@xmb-sjc-234.amer.cisco.com> <059AF07365DC474393A19A3AF187DF7406C36B5D@NAHALD.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9ABD@xmb-sjc-234.amer.cisco.com> <059AF07365DC474393A19A3AF187DF7406C36B88@NAHALD.us.int.genesyslab.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Henry Lum" <Henry.Lum@alcatel-lucent.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Mar 2011 18:15:01.0051 (UTC) FILETIME=[13B208B0:01CBDA98]
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 18:13:54 -0000

Please see inline.

> -----Original Message-----
> From: Henry Lum [mailto:Henry.Lum@alcatel-lucent.com]
> Sent: Friday, March 04, 2011 10:03 AM
> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] FW: New VersionNotificationfor
draft-portman-siprec-protocol-03
>=20
> Inline.
>=20
> > -----Original Message-----
> > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > Sent: Friday, March 04, 2011 12:47 PM
> > To: Henry Lum; Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] FW: New VersionNotificationfor draft-portman-
> > siprec-protocol-03
> >
> > Hi Henry,
> >
> > Please see inline.
> >
> > > -----Original Message-----
> > > From: Henry Lum [mailto:Henry.Lum@alcatel-lucent.com]
> > > Sent: Friday, March 04, 2011 9:29 AM
> > > To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat)
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] FW: New VersionNotificationfor
> > draft-portman-siprec-protocol-03
> > >
> > > Please see inline.
> > >
> > > > -----Original Message-----
> > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > Sent: Thursday, March 03, 2011 4:55 PM
> > > > To: Henry Lum; Paul Kyzivat (pkyzivat)
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] FW: New VersionNotificationfor
> draft-portman-
> > > > siprec-protocol-03
> > > >
> > > > I think it is better to stick to using UPDATE and not introduce
a
> > need
> > > > to use INFO. I would also expect that using re-INVITE instead of
> > > > UPDATE,
> > > > though not explicitly recommended, would work as well. What
drives
> > > this
> > > > is the inclusion of the newly defined tags and the actual
> metadata.
> > > >
> > > [[hlum]] Okay - let's hear if there are supporters for INFO before
> > > making a change.
> >
> > Okay.
> >
> > > > Section 5 reads,
> > > >
> > > >    The SRC must be able to accept re-INVITE from SRS with the
> > updated
> > > >    SDP as part of the session timer mechanism.
> > > >
> > > > What is the purpose of stating this?
> > > > I agree the SRC needs to be able
> > > > to
> > > > accept a re-INVITE with updated or non-updated SDP from the SRS.
> It
> > > > also
> > > > needs to be able to receive an UPDATE with updated or
non-updated
> > SDP.
> > > > This appears to me to be independent of using session timer, and
I
> > do
> > > > not believe we are mandating support for session timer either.
> > >
> > > [[hlum]] Perhaps the wording may be a bit too explicit, but the
> > > intention is that a recording session should use session timer
since
> > the
> > > SRS never sends any media to the SRC and the SRC needs a way to
tell
> > > that the SRS is still around. I don't think session timer needs to
> be
> > > mandated but I think it is recommended that we use it.
> >
> > I am not a fan of that. I think session timer is optional. What is
> > mandatory in my opinion is that the SRS sends RTCP messages, and
that
> > lets you know if is there and receiving the media. It also should do
> > something to make sure the RTP port does not get closed by a
> > firewall/NAT, and there are several mechanisms for that. That said,
> > this
> > is not specific to SIPREC, so I do not think we need explicit
> > requirements, but if we are providing recommendations those are the
> one
> > I suggest providing.
>=20
> [[hlum]] Agreed that this problem is not specific to SIPREC. The SRS
> does not send RTP to the SRC so I don't think it matters when that RTP
> port gets closed, but it makes sense to for SRS to send RTCP messages
to
> the SRC to acknowledge receipt of recorded media. Do we need to
mandate
> this?

RFC 3550 already mandates RTCP. We could reference
draft-marjou-behave-app-rtp-keepalive and RFC 5761, but I do not think
we need to mandate this.

Cheers,
Charles

> >
> > > >
> > > > In section 6.2, what does the "record" attribute and the defined
> > > > "indication" attribute give us that we do not already have using
> > > > sendonly and inactive, where off/pause maps to inactive and on
> maps
> > to
> > > > sendonly?
> > >
> > > [[hlum]] a=3Dsendrev/sendonly/recvonly describes the =
directionality
of
> > the
> > > actual media stream in the CS. What we want is an indication on
the
> > CS
> > > media streams where recording is actually taking place or not, and
> > that
> > > should not involve changing the directionality of the actual media
> > > stream.
> > > On the recording session media streams, we do use
> a=3Dsendrecv/sendonly
> > to
> > > indicate pause/resume.
> >
> > I see. This is really needed between the UA and the SRC, even if not
> > needed between the SRC and the SRS.
> >
> > > >
> > > > In section 6.3, recording preference, do we really need pause
and
> > > > resume? I am thinking record and norecord may be sufficient.
> > > >
> > > [[hlum]] The current consensus for the new wording of REQ-017
> > includes
> > > pause and resume:
> > >
> > > "REQ-zzz The mechanism MUST support a means for a recording-aware
UA
> > > involved in a CS to request during a session that the recording of
> > the
> > > CS should be started, paused, resumed or stopped, the honoring of
> > such
> > a
> > > request being dependent on policy."
> >
> > Here as well, it may not be needed between the SRC and the SRS, but
> > between a UA and a SRC, is that correct.
> >
> [[hlum]] Yes this mechanism is only for recording-aware UA in the CS.
>
> > Thanks,
> > Charles
> >
> > > > Cheers,
> > > > Charles
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> On
> > > > Behalf Of Henry Lum
> > > > > Sent: Wednesday, March 02, 2011 8:45 AM
> > > > > To: Paul Kyzivat (pkyzivat)
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] FW: New VersionNotificationfor
> > > > draft-portman-siprec-protocol-03
> > > > >
> > > > > I don't feel strongly too about using INFO so I am open to
using
> > > > UPDATE
> > > > > if the group feels that it is okay for SRC/SRS to deal with
the
> > > > > consequences of UPDATE collision.
> > > > >
> > > > > Henry
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > > > > > Sent: Tuesday, March 01, 2011 8:10 PM
> > > > > > To: Henry Lum
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] FW: New Version Notificationfor draft-
> > > > portman-
> > > > > > siprec-protocol-03
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 3/1/2011 2:32 PM, Henry Lum wrote:
> > > > > > > When there is an UPDATE transaction collision, you will
have
> > to
> > > > make
> > > > > > > both SRC and SRS to wait a while before being able to send
> > > UPDATE
> > > > > > again.
> > > > > > > Since SRC is normally the side initiating the SIP dialog,
it
> > is
> > > > the
> > > > > > > owner of the Call-ID and will come second after the SRS
has
> a
> > > > chance
> > > > > > to
> > > > > > > resend the UPDATE. In that case, does the SRC keep the
> > existing
> > > > > > UPDATE
> > > > > > > or send a new snapshot as requested by the SRS? The SRC
also
> > > need
> > > > to
> > > > > > > keep track of metadata changes while waiting for the
timer.
> I
> > > > worry
> > > > > > that
> > > > > > > it will make the solution more complicated than just using
> an
> > > > INFO
> > > > > > for
> > > > > > > snapshot request and minimize the collision problem.
> > > > > >
> > > > > > OK, collision on update is a *possibility*.
> > > > > > I guess the question is whether that justifies implementing
an
> > > > > entirely
> > > > > > different mechanism just for the rare error message.
> > > > > >
> > > > > > I expect that the likelihood of collision is pretty slim,
> given
> > > > that
> > > > > > messages from the SRS to the SRC will be very infrequent,
and
> > if
> > > > the
> > > > > > message comes shortly after a metadata is received from the
> > SRC,
> > > > there
> > > > > > may be little likelihood that the SRC will be sending more
> > > metadata
> > > > so
> > > > > > soon. And even if we don't use UPDATE for this, the SRC,
like
> > any
> > > > UA,
> > > > > > needs to be prepared to cope with a collision of this sort.
> > > > > >
> > > > > > But I don't feel *too* strongly about this.
> > > > > >
> > > > > > 	Thanks,
> > > > > > 	Paul
> > > > > >
> > > > > > > Regards,
> > > > > > > Henry
> > > > > > >
> > > > > > >> -----Original Message-----
> > > > > > >> From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org]
> > > > On
> > > > > > >> Behalf Of Paul Kyzivat
> > > > > > >> Sent: Tuesday, March 01, 2011 1:50 PM
> > > > > > >> To: siprec@ietf.org
> > > > > > >> Subject: Re: [siprec] FW: New Version Notificationfor
> > > > > draft-portman-
> > > > > > >> siprec-protocol-03
> > > > > > >>
> > > > > > >> Thanks Henry.
> > > > > > >>
> > > > > > >> One comment/question:
> > > > > > >>
> > > > > > >> Is there a reason to use an Info package for Requesting
for
> > > > > metadata
> > > > > > >> snapshot? Since we are already defining c-d recording-
> > session
> > > > and
> > > > > > >> passing bodies in invite/update for it, is there a reason
> > not
> > > to
> > > > > use
> > > > > > >> the
> > > > > > >> same mechanism to send error notifications/snapshop
> > requests?
> > > > > > >>
> > > > > > >> (I'm thinking just using a different content-type for
this,
> > and
> > > > of
> > > > > > >> course sending it from SRS to SRC.)
> > > > > > >>
> > > > > > >> Also, we could consider permitting (not requiring) this
in
> > the
> > > > > > >> responses
> > > > > > >> to the messages containing metadata.
> > > > > > >>
> > > > > > >> 	Thanks,
> > > > > > >> 	Paul
> > > > > > >>
> > > > > > >>
> > > > > > >> On 3/1/2011 12:13 PM, Henry Lum wrote:
> > > > > > >>> A new version has been submitted to address the
> outstanding
> > > > issues
> > > > > > >> and include extensions for the new wording for REQ-017
and
> > > > REQ-018.
> > > > > > >>>
> > > > > > >>>
> > > https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
> > > > > > >>>
> > > > > > >>> Regards,
> > > > > > >>> Henry
> > > > > > >>>
> > > > > > >>> -----Original Message-----
> > > > > > >>> From: IETF I-D Submission Tool
> > [mailto:idsubmission@ietf.org]
> > > > > > >>> Sent: Tuesday, March 01, 2011 12:09 PM
> > > > > > >>> To: Henry Lum
> > > > > > >>> Cc: leon.portman@nice.com; alan.b.johnston@gmail.com;
> > > > > > >> andrew.hutton@siemens-enterprise.com
> > > > > > >>> Subject: New Version Notification for
> draft-portman-siprec-
> > > > > > protocol-
> > > > > > >> 03
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> A new version of I-D,
draft-portman-siprec-protocol-03.txt
> > has
> > > > > been
> > > > > > >> successfully submitted by Henry Lum and posted to the
IETF
> > > > > > repository.
> > > > > > >>>
> > > > > > >>> Filename:	 draft-portman-siprec-protocol
> > > > > > >>> Revision:	 03
> > > > > > >>> Title:		 The SIP-based Media Recording Protocol
> > > > (SIPREC)
> > > > > > >>> Creation_date:	 2011-03-01
> > > > > > >>> WG ID:		 Independent Submission
> > > > > > >>> Number_of_pages: 20
> > > > > > >>>
> > > > > > >>> Abstract:
> > > > > > >>> SIPREC Session Recording Protocol is used for
establishing
> > > > > > recording
> > > > > > >>> session and reporting of the metadata of the
communication
> > > > > session.
> > > > > > >>>
> > > > > > >>> This document specifies the SIPREC Protocol (SIPREC).
> > SIPREC
> > > > is
> > > > > > > used
> > > > > > >>> between Session Recording Client (SRC) and Session
> > Recording
> > > > > Server
> > > > > > >>> (SRS).
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> The IETF Secretariat.
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > >> ----------------------------------------------
> > > > > > >>> CONFIDENTIALITY NOTICE: This e-mail and any files
attached
> > may
> > > > > > >> contain confidential and proprietary information of
> > > > Alcatel-Lucent
> > > > > > >> and/or its affiliated entities. Access by the intended
> > > recipient
> > > > > > only
> > > > > > >> is authorized. Any liability arising from any party
acting,
> > or
> > > > > > >> refraining from acting, on any information contained in
> this
> > > > e-mail
> > > > > > is
> > > > > > >> hereby excluded. If you are not the intended recipient,
> > please
> > > > > > notify
> > > > > > >> the sender immediately, destroy the original transmission
> > and
> > > > its
> > > > > > >> attachments and do not disclose the contents to any other
> > > > person,
> > > > > > use
> > > > > > >> it for any purpose, or store or copy the information in
any
> > > > medium.
> > > > > > >> Copyright in this e-mail and any attachments belongs to
> > > Alcatel-
> > > > > > Lucent
> > > > > > >> and/or its affiliated entities.
> > > > > > >>>
> > > > > > >>> _______________________________________________
> > > > > > >>> 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
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > ----------------------------------------------
> > > > > > > CONFIDENTIALITY NOTICE: This e-mail and any files attached
> > may
> > > > > > contain confidential and proprietary information of
> > Alcatel-Lucent
> > > > > > and/or its affiliated entities. Access by the intended
> > recipient
> > > > only
> > > > > > is authorized. Any liability arising from any party acting,
or
> > > > > > refraining from acting, on any information contained in this
> > > e-mail
> > > > is
> > > > > > hereby excluded. If you are not the intended recipient,
please
> > > > notify
> > > > > > the sender immediately, destroy the original transmission
and
> > its
> > > > > > attachments and do not disclose the contents to any other
> > person,
> > > > use
> > > > > > it for any purpose, or store or copy the information in any
> > > medium.
> > > > > > Copyright in this e-mail and any attachments belongs to
> > > > Alcatel-Lucent
> > > > > > and/or its affiliated entities.
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
-----------------------------------------------------------------------
> > > > -
> > > > ------------------------------
> > > > > -------------
> > > > > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > > > contain
> > > > confidential and proprietary
> > > > > information of Alcatel-Lucent and/or its affiliated entities.
> > Access
> > > > by the intended recipient only is
> > > > > authorized. Any liability arising from any party acting, or
> > > > refraining
> > > > from acting, on any information
> > > > > contained in this e-mail is hereby excluded. If you are not
the
> > > > intended recipient, please notify the
> > > > > sender immediately, destroy the original transmission and its
> > > > attachments and do not disclose the
> > > > > contents to any other person, use it for any purpose, or store
> or
> > > > copy
> > > > the information in any medium.
> > > > > Copyright in this e-mail and any attachments belongs to
Alcatel-
> > > > Lucent
> > > > and/or its affiliated entities.
> > > > >
> > > > > _______________________________________________
> > > > > siprec mailing list
> > > > > siprec@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/siprec
> > >
> > >
> > >
> >
>
-----------------------------------------------------------------------
> > -
> > ------------------------------
> > > -------------
> > > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > contain
> > confidential and proprietary
> > > information of Alcatel-Lucent and/or its affiliated entities.
Access
> > by the intended recipient only is
> > > authorized. Any liability arising from any party acting, or
> > refraining
> > from acting, on any information
> > > contained in this e-mail is hereby excluded. If you are not the
> > intended recipient, please notify the
> > > sender immediately, destroy the original transmission and its
> > attachments and do not disclose the
> > > contents to any other person, use it for any purpose, or store or
> > copy
> > the information in any medium.
> > > Copyright in this e-mail and any attachments belongs to Alcatel-
> > Lucent
> > and/or its affiliated entities.
> > >
>=20
>=20
>
------------------------------------------------------------------------
------------------------------
> -------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary
> information of Alcatel-Lucent and/or its affiliated entities. Access
by the intended recipient only is
> authorized. Any liability arising from any party acting, or refraining
from acting, on any information
> contained in this e-mail is hereby excluded. If you are not the
intended recipient, please notify the
> sender immediately, destroy the original transmission and its
attachments and do not disclose the
> contents to any other person, use it for any purpose, or store or copy
the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
>=20

From pkyzivat@cisco.com  Fri Mar  4 10:17:03 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBCD228C0D9 for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 10:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.523
X-Spam-Level: 
X-Spam-Status: No, score=-110.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ehb2gTNSaYNJ for <siprec@core3.amsl.com>; Fri,  4 Mar 2011 10:17:03 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 12BA528C0CF for <siprec@ietf.org>; Fri,  4 Mar 2011 10:17:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=675; q=dns/txt; s=iport; t=1299262692; x=1300472292; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WfpgooQ69Lxn03x/rNEkdiWL/MnDFjYrrVsEDv2Hto8=; b=LiUjBYshHyRsgmhd3D46pnzDJToImrAf/tvKBV0fuWFTYHAgvmA5urXR FrnHhcv8QsFJLfdg7KJA+fWE/GuiLX2No2CryV4ixVJ9ZU8nGu+mCEI9C BP4hjT3OdVokpX5TKjl1S60pgducF+XUsHwXqXAO3FECad8pvX7ilaX8m M=;
X-IronPort-AV: E=Sophos;i="4.62,264,1297036800"; d="scan'208";a="339500597"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 04 Mar 2011 18:18:12 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p24IICfB015134; Fri, 4 Mar 2011 18:18:12 GMT
Message-ID: <4D712CE3.60009@cisco.com>
Date: Fri, 04 Mar 2011 13:18:11 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Henry Lum <Henry.Lum@alcatel-lucent.com>
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com><4D6D3FE5.9000902@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com><4D6D98DC.8080008@cisco.com> <059AF07365DC474393A19A3AF187DF7406BAE5C6@NAHALD.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB987B@xmb-sjc-234.amer.cisco.com> <059AF07365DC474393A19A3AF187DF7406C36B5D@NAHALD.us.int.genesyslab.com>
In-Reply-To: <059AF07365DC474393A19A3AF187DF7406C36B5D@NAHALD.us.int.genesyslab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: New VersionNotificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 18:17:04 -0000

On 3/4/2011 12:29 PM, Henry Lum wrote:

> [[hlum]] Perhaps the wording may be a bit too explicit, but the
> intention is that a recording session should use session timer since the
> SRS never sends any media to the SRC and the SRC needs a way to tell
> that the SRS is still around. I don't think session timer needs to be
> mandated but I think it is recommended that we use it.

I will repeat the mantra I have been issuing periodically for years:

Session timer is supported by UAs for the benefit of *proxies*!

UAs don't *need* session timer - they can independently send a request 
any time they wonder if the other end is still live.

	Thanks,
	Paul

From acooper@cdt.org  Sat Mar  5 12:05:52 2011
Return-Path: <acooper@cdt.org>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 294513A6AB6 for <siprec@core3.amsl.com>; Sat,  5 Mar 2011 12:05:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level: 
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EIbx4v9rIq0U for <siprec@core3.amsl.com>; Sat,  5 Mar 2011 12:05:50 -0800 (PST)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by core3.amsl.com (Postfix) with ESMTP id C26D63A6AB1 for <siprec@ietf.org>; Sat,  5 Mar 2011 12:05:49 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Sat, 5 Mar 2011 15:06:48 -0500
Message-Id: <8192308F-326D-4209-941D-C4F3BCA87E3F@cdt.org>
From: Alissa Cooper <acooper@cdt.org>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA06C2C5096C@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sat, 5 Mar 2011 20:06:43 +0000
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com><4D6EFFD0.7070109@cisco.com><07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com><CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C5086D@MCHP058A.global-ad.net> <CD2DE94B86B69443B53711F606FCAE120862E4B7@SARUMAN.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB97EC@xmb-sjc-234.amer.cisc o.com>  <A444A0F8084434499206E78C106220CA06C2C5096C@MCHP058A.global-ad.net>
X-Mailer: Apple Mail (2.936)
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018onindications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 05 Mar 2011 20:05:52 -0000

On Mar 4, 2011, at 7:39 AM, Elwell, John wrote:
> "REQ-x1 The mechanism MUST NOT prevent the application of tones or  
> announcements during recording or at the start of a CS to support  
> legal or policy requirements for notifying participants that the  
> call is being recorded or may be recorded."

Why does this requirement only apply to cases where notification is  
provided because of legal or policy requirements? What if the entity  
doing the recording just thinks that notification is a Good Thing to  
Do? My suggestion:

"REQ-x1 The mechanism MUST NOT prevent the application of tones or  
announcements during recording or at the start of a CS to support  
notification to participants that the call is being recorded or may be  
recorded."

Alissa

>
> "REQ-x2 The mechanism MUST provide a means of indicating to  
> recording-aware UAs whether recording is taking place, for  
> appropriate rendering at the user interface.
>
> John
>
>
>> -----Original Message-----
>> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
>> Sent: 03 March 2011 20:05
>> To: Dave Smith; Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>> of REQ-018onindications to participants
>>
>> Just to clarify, is the decision therefore that Req. #18 will
>> be updated
>> as proposed by John?
>>
>>>>>>>> I would suggest the following text:
>>>>>>>> "REQ-018 The mechanism MUST provide a means of
>>>> indicating to the
>>>>>>>> participants involved in a CS that their session is being
>>>>> recorded.
>>>>>>>> Although this can be accomplished using existing SIP
>>>>> techniques for
>>>>>>>> playing an in-band tone, announcement or other media to
>>>>>>>> participants, the mechanism is required also to provide an
>>>>>>>> indication to recording-aware UAs for appropriate
>>>>> rendering at the
>>>>>>>> user interface."
>>
>> If I am interpreting this correctly, playing of a tone or an
>> announcement is an option, not a required form of indication, and  
>> some
>> other indication may be communicated from the SRC to a recording  
>> aware
>> UA that results in the UA producing an indication of recording that  
>> is
>> possibly NOT audible, for example. The choice of the actual
>> rendering of
>> this indication by the UA is left entirely to the UA. Is that  
>> correct?
>>
>> Thanks,
>> Charles
>>
>>
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Dave Smith
>>> Sent: Thursday, March 03, 2011 9:38 AM
>>> To: Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
>>> Cc: siprec@ietf.org
>>> Subject: Re: [siprec] Requirements #66 (new): Clarification of
>> REQ-018onindications to participants
>>>
>>> Thanks for the detailed inputs/explanations.  I agree with the
>>> recommendations for using REQ-x1 and -x2.
>>>
>>> Regards,
>>> Dave
>>>
>>> -----Original Message-----
>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>>> Sent: Thursday, March 03, 2011 9:17 AM
>>> To: Leon Portman; Dave Smith; Paul Kyzivat
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>> of REQ-018
>>> onindications to participants
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>> Sent: 03 March 2011 15:24
>>>> To: Elwell, John; Dave Smith; Paul Kyzivat
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>>>> of REQ-018 on indications to participants
>>>>
>>>> I agree with your points. Just generic question, do we really
>>>> need a requirement for mechanism not to prevent something? It
>>>> can be lot of things like encryption, codec negotiation,
>>>> ability to transfer call etc.
>>> [JRE] It is certainly worth questioning whether we need
>> REQ-x1 below.
>> On
>>> the one hand, SIPREC is unlikely to specify anything that would
>> prevent
>>> this existing capability. In fact it would be quite hard
>> for SIPREC to
>>> specify something that would prevent the application of tones of
>>> announcement. Of course, there might be things that could be done at
>>> deployment time to prevent it (e.g., encryption), but that is not
>>> SIPREC's problem. However, I would still be inclined to keep it. In
>>> particular, the Privacy Considerations section has a statement:
>>> "Therefore this document contains requirements for being able to
>> notify
>>> users that a call is being recorded ...". I don't think REQ-x2 alone
>>> would be sufficient to satisfy that, so if we were to
>> remove REQ-x1 we
>>> would have to revisit the Privacy Considerations text, which I would
>> be
>>> very reluctant to do. So I would like to keep REQ-x1 or something
>>> similar.
>>>
>>> John (as individual)
>>>
>>>>
>>>> Leon
>>>>
>>>> -----Original Message-----
>>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>>>> Sent: Thursday, March 03, 2011 11:14 AM
>>>> To: Dave Smith; Leon Portman; Paul Kyzivat
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>>>> of REQ-018 on indications to participants
>>>>
>>>> Concerning #1, I agree we need to be able to accommodate the
>>>> different requirements of different regions, countries,
>>>> business sectors, etc.. Sometimes this might involve playing
>>>> a tone (e.g., a repeated beep) for the duration of recording,
>>>> and sometimes this might involve an announcement at the
>>>> beginning of the session, which will suffice whether or not
>>>> recording actually takes place during the session. Basically,
>>>> since not all users will use siprec-aware UAs, particularly
>>>> PSTN users, the only solution is for the SRC to arrange that
>>>> the appropriate tone or announcement is injected into the
>>>> audio stream when required. If the SRC itself is able to do
>>>> this, we don't need a SIP solution. If the SRC uses a media
>>>> server to do this, existing SIP/SDP mechanisms will cater for
>>>> this. I don't anticipate siprec providing new mechanisms for
>>>> this. It is really just a case of not preventing the use of
>>>> such mechanisms. How about the following text?
>>>>
>>>> "REQ-x1 The mechanism MUST NOT prevent the application of
>>>> tones or announcements during recording or at the start of a
>>>> CS to support legal or policy requirements for notifying
>>>> participants that the call is being recorded or may be recorded."
>>>>
>>>> Concerning #2, I see this more of a courtesy thing, rather
>>>> than a legal thing. Most web-based conference applications
>>>> give a visual indication of whether the conference is being
>>>> recorded, achieved using web technology. Where this is not
>>>> available, it would be useful if siprec-aware UAs in the CS
>>>> could be advised when recording is taking place so that they
>>>> can give an appropriate indication to the user. I can see a
>>>> number of reasons for this:
>>>> - It provides the possibility of alternative modes for
>>>> hearing-impaired users.
>>>> - It gives more precise information in cases where an
>>>> SRC-injected announcement is given only at the start of the call.
>>>> - It provides feedback to users who have requested that
>>>> recording be started / stopped / paused / resumed.
>>>> - It gives an explicit indication to users who might not
>>>> understand the meaning of an injected tone.
>>>> - It is independent of medium type (audio, video, real-time
>>>> text, fax...).
>>>> - Potentially its granularity could be on a per medium basis,
>>>> although I would prefer to leave that as an option for the
>>>> solution, rather than making a requirement.
>>>>
>>>> So how about the following text?
>>>>
>>>> "REQ-x2 The mechanism MUST provide a means of indicating to
>>>> recording-aware UAs whether recording is taking place, for
>>>> appropriate rendering at the user interface.
>>>>
>>>> John (as individual)
>>>>
>>>>>>>> participants involved in a CS that their session is being
>>>>> recorded.
>>>>>>>> Although this can be accomplished using existing SIP
>>>>> techniques for
>>>>>>>> playing an in-band tone, announcement or other media to
>>>>>>>> participants, the mechanism is required also to provide an
>>>>>>>> indication to recording-aware UAs for appropriate
>>>>> rendering at the
>>>>>>>> user interface."
>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org
>>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
>>>>> Sent: 03 March 2011 08:29
>>>>> To: Leon Portman; Paul Kyzivat
>>>>> Cc: siprec@ietf.org
>>>>> Subject: Re: [siprec] Requirements #66 (new): Clarification
>>>>> of REQ-018 on indications to participants
>>>>>
>>>>> I fully agree that an IVR solution (play an announcement) is an
>>>>> acceptable method that is used today to inform a caller.
>>>>> I was introducing this req't (#1 below) in order to improve
>>>> on that.
>>>>>
>>>>> Do we absolutely need #1 - probably not.  Do we
>> absolutely need #2
>> -
>>>>> probably not also.
>>>>>
>>>>> It seems that you are indicating that at least for #1 a solution
>> is
>>>>> difficult to provide and would restrict the SRC solution
>>>>> significantly,
>>>>> so we should not include it.
>>>>> I am wondering if that is also the case for #2.
>>>>>
>>>>> I don't think we need to mention any "optional" solutions in
>>>>> the req't.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Dave
>>>>>
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>> Sent: Wednesday, March 02, 2011 11:32 PM
>>>>> To: Paul Kyzivat; Dave Smith
>>>>> Cc: siprec@ietf.org
>>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>>>> of REQ-018
>>>>> on indications to participants
>>>>>
>>>>> I agree with Paul. In the environment where SRC cannot inject
>>>>> any audio
>>>>> into the CS, best practice is to have IVR or Voice Portal
>>>> to make such
>>>>> announcement.
>>>>>
>>>>> Leon
>>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org
>>>>> [mailto:siprec-bounces@ietf.org] On Behalf
>>>>> Of Paul Kyzivat
>>>>> Sent: Thursday, March 03, 2011 4:41 AM
>>>>> To: Dave Smith
>>>>> Cc: siprec@ietf.org
>>>>> Subject: Re: [siprec] Requirements #66 (new): Clarification
>>>> of REQ-018
>>>>> on indications to participants
>>>>>
>>>>>
>>>>>
>>>>> On 3/2/2011 7:50 PM, Dave Smith wrote:
>>>>>> I think the solution should be able to support these
>>>>> functionalities:
>>>>>>  1.  playing a repeatable tone to CS participants
>>>>>>  2.  indicate to recording-aware UAs that recording is
>> currently
>>>>>> occurring
>>>>>>
>>>>>> Although there may be other things that could be done, I
>>>>> believe that
>>>>>> these functionalities are reasonable and sufficient, and would
>> be
>>>>>> universally accepted, and that both are required in order
>>>>> to be able
>>>>>> to addresss most use cases for indicating to the
>>>>> participants involved
>>>>>
>>>>>> in a CS that their session is being recorded.
>>>>>
>>>>>> I am not sure of what the last paragraph of your response
>>>> is about
>>>>>> exactly.  A solution to this req't needs to be worked out
>>>>> in another
>>>>>> SIPREC Draft; my current thoughts are that since the SRC is
>>>>> handling
>>>>>> and in the path of CS UA media and is already communicating
>>>>> with these
>>>>>
>>>>>> UAs, probably an SRC-based solution could be more easily
>>>>> used to solve
>>>>>
>>>>>> this req't.
>>>>>
>>>>> I'll try to elaborate:
>>>>>
>>>>> I'm not informed of the specific legalities involved, but am of
>> the
>>>>> impression that they vary widely. There are certainly
>>>>> contexts in which
>>>>> no audible indication need be played. (E.g. call centers,
>>>> at least in
>>>>> some places.) In some cases this is dealt with by playing a
>> general
>>>>> disclaimer at the beginning of the call, and/or having a
>> contractual
>>>>> relationship by which this isn't required.
>>>>>
>>>>> In such environments the SRC may not need any way of
>> injecting an
>>>>> audible indication that recording is going on.
>>>>>
>>>>> And there are ways an SRC could get the media for recording
>>>> that don't
>>>>> provide a way to inject these tones. (E.g. a media *relay*
>>>>> may fork the
>>>>> media, but not be able to alter it.)
>>>>>
>>>>> If you combine these things, you can end up with mechanisms for
>>>>> implementing the SRC function that are *incapable* of
>>>> satisfying your
>>>>> proposed requirement, and yet are perfectly suitable for
>>>> the intended
>>>>> recording task. I don't want to rule those out as valid
>>>>> implementations
>>>>> of siprec.
>>>>>
>>>>> I'm fine with having the tone generation as an *option*,
>>>> and one that
>>>>> may be absolutely required in *some* markets. If you have a
>> business
>>>>> that requires this tone generation then you will buy a product
>> that
>>>>> supports it.
>>>>>
>>>>>    Thanks,
>>>>>    Paul
>>>>>
>>>>>> Regards,
>>>>>> Dave
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>> On
>>>>>> Behalf Of Paul Kyzivat
>>>>>> Sent: Wednesday, March 02, 2011 1:43 PM
>>>>>> To: siprec@ietf.org
>>>>>> Subject: Re: [siprec] Requirements #66 (new): Clarification
>>>>> of REQ-018
>>>>>
>>>>>> on indications to participants
>>>>>>
>>>>>> Dave,
>>>>>>
>>>>>> I recognize that there are environments where this audible
>>>>> tone is a
>>>>>> requirement. And also environments where it is not, or that
>>>>> there is
>>>>>> some *other* requirement.
>>>>>>
>>>>>> My question is whether rendering such things is "part of the
>>>>>> mechanism",
>>>>>>
>>>>>> or simply something that some SRCs must be able to do.
>>>>>>
>>>>>> Making this part of the mechanism begs the question of "what
>>>>> mechanism".
>>>>>>
>>>>>> There are mechanisms for capturing the media for recording
>>>>> that do not
>>>>>
>>>>>> have a device in place that can insert something into
>> the media.
>>>>>> Making this a requirement on the mechanism would exclude
>>>>> using those
>>>>>> techniques.
>>>>>>
>>>>>>  Thanks,
>>>>>>  Paul
>>>>>>
>>>>>> On 3/2/2011 2:57 PM, Dave Smith wrote:
>>>>>>> I do have an input to this requirement.
>>>>>>>
>>>>>>> I agree that the system should be able to provide an
>>>> indication to
>>>>>>> recording-aware UAs that recording is currently
>> occurring (for
>>>>>>> appropriate rendering at the user interface).
>>>>>>> I also believe that the system should be able to provide a
>>>>> "tone" to
>>>>>> CS
>>>>>>> participants to indicate that recording is currently
>> occurring
>>>>>>> (specifically, a distinct "beep tone" signal that is repeated
>> at
>>>>>> regular
>>>>>>> intervals during the course of the telephone
>>>> conversation when the
>>>>>>> recording device is in use); note that this is
>> consistent with
>>>>>> existing
>>>>>>> methods from FCC Rules Regarding Telephone Company
>> Recording of
>>>>>>> Interstate or International Wireline Telephone Conversations.
>>>>>>> But I do not see a reason to mention
>> "announcements", or "other
>>>>> media"
>>>>>>> in this requirement.
>>>>>>>
>>>>>>> Therefore, I recommend the following wording for REQ-018:
>>>>>>>
>>>>>>> "REQ-018 The mechanism MUST provide a means of indicating to
>> the
>>>>>>> participants involved in a CS that their session is
>>>> being recorded.
>>>>>> To
>>>>>>> support this the mechanism MUST provide a means of playing a
>>>>>> repeatable
>>>>>>> tone to CS participants, and also the mechanism MUST
>>>>> provide a means
>>>>>> to
>>>>>>> indicate to recording-aware UAs that recording is
>>>>> currently occurring
>>>>>
>>>>>>> (for appropriate rendering at the user interface)."
>>>>>>>
>>>>>>> Regards,
>>>>>>> Dave
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: siprec-bounces@ietf.org
>> [mailto:siprec-bounces@ietf.org]
>> On
>>>>>> Behalf
>>>>>>> Of Elwell, John
>>>>>>> Sent: Wednesday, March 02, 2011 3:41 AM
>>>>>>> To: Leon Portman; siprec issue tracker
>>>>>>> Cc: siprec@ietf.org
>>>>>>> Subject: Re: [siprec] Requirements #66 (new):
>> Clarification of
>>>>>>> REQ-018 on indications to participants
>>>>>>>
>>>>>>> In the interests of getting the requirements document
>>>> finished, I
>>>>>>> will set a short deadline for this remaining issue. If I
>>>> have not
>>>>>>> heard any objections to the proposal below by 2011-03-07 I
>>>>> will ask
>>>>>>> the editor
>>>>>> to
>>>>>>> adopt this new text and publish -07.
>>>>>>>
>>>>>>> John (as chair)
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>>>>> Sent: 28 February 2011 16:17
>>>>>>>> To: Elwell, John; siprec issue tracker
>>>>>>>> Cc: siprec@ietf.org
>>>>>>>> Subject: RE: [siprec] Requirements #66 (new):
>> Clarification of
>>>>>>>> REQ-018 on indications to participants
>>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> Leon
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Elwell, John
>> [mailto:john.elwell@siemens-enterprise.com]
>>>>>>>> Sent: Monday, February 28, 2011 5:35 PM
>>>>>>>> To: Leon Portman; siprec issue tracker
>>>>>>>> Cc: siprec@ietf.org
>>>>>>>> Subject: RE: [siprec] Requirements #66 (new):
>> Clarification of
>>>>>>>> REQ-018 on indications to participants
>>>>>>>>
>>>>>>>> There has been little discussion on this, apart from
>>>> support from
>>>>>>>> Leon. The existing text says:
>>>>>>>> "REQ-018 The mechanism MUST provide a means of indicating to
>> the
>>>>>>>>     participants involved in a CS that their
>> session is being
>>>>>> recorded.
>>>>>>>>
>>>>>>>>     Examples include: inject tones into the CS from the
>>>>> SRC, play a
>>>>>>>>     message at the beginning of a session, a visual
>>>>> indicator on a
>>>>>>>>     display, etc."
>>>>>>>>
>>>>>>>> I would suggest the following text:
>>>>>>>> "REQ-018 The mechanism MUST provide a means of
>>>> indicating to the
>>>>>>>> participants involved in a CS that their session is being
>>>>> recorded.
>>>>>>>> Although this can be accomplished using existing SIP
>>>>> techniques for
>>>>>>>> playing an in-band tone, announcement or other media to
>>>>>>>> participants, the mechanism is required also to provide an
>>>>>>>> indication to recording-aware UAs for appropriate
>>>>> rendering at the
>>>>>>>> user interface."
>>>>>>>>
>>>>>>>> John (as individual)
>>>>>
>>>>
>>>
>>>
>>>
>> --------------------------------------------------------------
>> ----------
>> ------------------------------
>>> -------------
>>> CONFIDENTIALITY NOTICE: This e-mail and any files attached
>> may contain
>> confidential and proprietary
>>> information of Alcatel-Lucent and/or its affiliated entities. Access
>> by the intended recipient only is
>>> authorized. Any liability arising from any party acting, or
>> refraining
>> from acting, on any information
>>> contained in this e-mail is hereby excluded. If you are not the
>> intended recipient, please notify the
>>> sender immediately, destroy the original transmission and its
>> attachments and do not disclose the
>>> contents to any other person, use it for any purpose, or
>> store or copy
>> the information in any medium.
>>> Copyright in this e-mail and any attachments belongs to
>> Alcatel-Lucent
>> and/or its affiliated entities.
>>>
>>> _______________________________________________
>>> 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
>



From partr@cisco.com  Sun Mar  6 10:08:53 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F12953A6828 for <siprec@core3.amsl.com>; Sun,  6 Mar 2011 10:08:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.402
X-Spam-Level: 
X-Spam-Status: No, score=-9.402 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OhpNqBgHo2A9 for <siprec@core3.amsl.com>; Sun,  6 Mar 2011 10:08:49 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 881743A683B for <siprec@ietf.org>; Sun,  6 Mar 2011 10:08:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=54746; q=dns/txt; s=iport; t=1299435002; x=1300644602; h=mime-version:subject:date:message-id:references:from:to: cc; bh=b4VXATfSlSvsvjeCpOR8p/Vzf6xRm/rNv6cQsa82rso=; b=BBJ1/PkYrZsNys/Hh8xvsaGJodyeTfEJDz1yYFQ+gvgFzddFN9KbvRmG p33r3utKcI3sgIf6ZCVXvnVh4OW1QVmcIsqhBYzeKVB/1h7aUIfnDb1v2 uh+2+zz/CqnhsfAN5VAX0ZAQLdJWVBVaV8TLUsn2VXkyTAvZuWAvY9rO2 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUBAIpcc01AaMHG/2dsb2JhbACYJI1kWHSjA5pqgiCDQgSFGopfgxQ
X-IronPort-AV: E=Sophos;i="4.62,272,1297036800";  d="scan'208,217";a="270695206"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-4.cisco.com with ESMTP; 06 Mar 2011 18:10:00 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p26I9qAF011620; Sun, 6 Mar 2011 18:09:52 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 6 Mar 2011 23:39:51 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBDC29.B0077E0F"
Date: Sun, 6 Mar 2011 23:39:51 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A681@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] FW: NewVersionNotificationfor	draft-portman-siprec-protocol-03
Thread-Index: AcvYdoq1VttmMUOCSj+I/EBWiH/OmQAgjaaAADyUJVAAKMzRwAAA9vCQAAC4CSAAAKdlAABkMTyn
References: <059AF07365DC474393A19A3AF187DF7406BAE35F@NAHALD.us.int.genesyslab.com><4D6D3FE5.9000902@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE3EE@NAHALD.us.int.genesyslab.com><4D6D98DC.8080008@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE5C6@NAHALD.us.int.genesyslab.com><E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB987B@xmb-sjc-234.amer.cisco.com><059AF07365DC474393A19A3AF187DF7406C36B5D@NAHALD.us.int.genesyslab.com><E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9ABD@xmb-sjc-234.amer.cisco.com><059AF07365DC474393A19A3AF187DF7406C36B88@NAHALD.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9B09@xmb-sjc-234.amer.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Henry Lum" <Henry.Lum@alcatel-lucent.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 06 Mar 2011 18:09:51.0981 (UTC) FILETIME=[B04D31D0:01CBDC29]
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: NewVersionNotificationfor	draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 06 Mar 2011 18:08:53 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBDC29.B0077E0F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Henry,
=20
I agree with Paul & Charles for INFO vs UPDATE or RE-INVITE without SDP. =
My general comments and doubt are as follows:
=20

1) Fig 2 Step 5 indicates callid. Pls elaborate what is the callid =
represented here?

=20

2) Sec 4.3,  "The metadata snapshot request will be provided as an INFO

   package [RFC6086] and sent as mid-dialog messages within the

   recording session by the SRS." it shall be UPDATE or RE-INVITE =
without SDP with request for complete metadata.

=20

3) Sec 4.3 last para: "however, it is

   envisioned that a link with a URI can be provided in the recording

   session INVITE message so that the SRS can access the session

   metadata via the URI provided that the SRS supports the type of URI."

   Any new mechanism will be introduced in RS to pass this link?

=20

4) Sec 5 last para: During mid-dialog transaction in Recording session =
(dialog) between SRC and SRS, SRC and SRC SHALL support all SIP =
mid-dialog behavior between two UA. IOW, SRS may be sending =
RE-INVITE/UDPATE for media attributes change, session timer or any other =
reason.

=20

5) Update Sec 5.3.1 as per the comment 1 wherein Re-INVITE/UPDATE shall =
be used to request new metadata snapshot

=20

6) As earlier discussed, pls include the possible error code in the =
draft.

=20

Doubt:

1) Fig 3 which may leads to UA A moves out of the conference right?

=20

Please read inline for more comments

=20

Thanks

Partha


________________________________

From: siprec-bounces@ietf.org on behalf of Charles Eckel (eckelcu)
Sent: Fri 3/4/2011 11:45 PM
To: Henry Lum; Paul Kyzivat (pkyzivat)
Cc: siprec@ietf.org
Subject: Re: [siprec] FW: NewVersionNotificationfor =
draft-portman-siprec-protocol-03



Please see inline.

> -----Original Message-----
> From: Henry Lum [mailto:Henry.Lum@alcatel-lucent.com]
> Sent: Friday, March 04, 2011 10:03 AM
> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] FW: New VersionNotificationfor
draft-portman-siprec-protocol-03
>
> Inline.
>
> > -----Original Message-----
> > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > Sent: Friday, March 04, 2011 12:47 PM
> > To: Henry Lum; Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] FW: New VersionNotificationfor draft-portman-
> > siprec-protocol-03
> >
> > Hi Henry,
> >
> > Please see inline.
> >
> > > -----Original Message-----
> > > From: Henry Lum [mailto:Henry.Lum@alcatel-lucent.com]
> > > Sent: Friday, March 04, 2011 9:29 AM
> > > To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat)
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] FW: New VersionNotificationfor
> > draft-portman-siprec-protocol-03
> > >
> > > Please see inline.
> > >
> > > > -----Original Message-----
> > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > Sent: Thursday, March 03, 2011 4:55 PM
> > > > To: Henry Lum; Paul Kyzivat (pkyzivat)
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] FW: New VersionNotificationfor
> draft-portman-
> > > > siprec-protocol-03
> > > >
> > > > I think it is better to stick to using UPDATE and not introduce
a
> > need
> > > > to use INFO. I would also expect that using re-INVITE instead of
> > > > UPDATE,
> > > > though not explicitly recommended, would work as well. What
drives
> > > this
> > > > is the inclusion of the newly defined tags and the actual
> metadata.
> > > >
> > > [[hlum]] Okay - let's hear if there are supporters for INFO before
> > > making a change.
> >
> > Okay.
> >
> > > > Section 5 reads,
> > > >
> > > >    The SRC must be able to accept re-INVITE from SRS with the
> > updated
> > > >    SDP as part of the session timer mechanism.
> > > >
> > > > What is the purpose of stating this?
> > > > I agree the SRC needs to be able
> > > > to
> > > > accept a re-INVITE with updated or non-updated SDP from the SRS.
> It
> > > > also
> > > > needs to be able to receive an UPDATE with updated or
non-updated
> > SDP.
> > > > This appears to me to be independent of using session timer, and
I
> > do
> > > > not believe we are mandating support for session timer either.
> > >
> > > [[hlum]] Perhaps the wording may be a bit too explicit, but the
> > > intention is that a recording session should use session timer
since
> > the
> > > SRS never sends any media to the SRC and the SRC needs a way to
tell
> > > that the SRS is still around. I don't think session timer needs to
> be
> > > mandated but I think it is recommended that we use it.
> >
> > I am not a fan of that. I think session timer is optional. What is
> > mandatory in my opinion is that the SRS sends RTCP messages, and
that
> > lets you know if is there and receiving the media. It also should do
> > something to make sure the RTP port does not get closed by a
> > firewall/NAT, and there are several mechanisms for that. That said,
> > this
> > is not specific to SIPREC, so I do not think we need explicit
> > requirements, but if we are providing recommendations those are the
> one
> > I suggest providing.
>
> [[hlum]] Agreed that this problem is not specific to SIPREC. The SRS
> does not send RTP to the SRC so I don't think it matters when that RTP
> port gets closed, but it makes sense to for SRS to send RTCP messages
to
> the SRC to acknowledge receipt of recorded media. Do we need to
mandate
> this?

RFC 3550 already mandates RTCP. We could reference
draft-marjou-behave-app-rtp-keepalive and RFC 5761, but I do not think
we need to mandate this.

Cheers,
Charles

<Partha> SRS & SRC MUST mid-dialog behavior of RFC 3261 which includes =
codec change, media change, session timer (optional)  </Partha>

> >
> > > >
> > > > In section 6.2, what does the "record" attribute and the defined
> > > > "indication" attribute give us that we do not already have using
> > > > sendonly and inactive, where off/pause maps to inactive and on
> maps
> > to
> > > > sendonly?
> > >
> > > [[hlum]] a=3Dsendrev/sendonly/recvonly describes the =
directionality
of
> > the
> > > actual media stream in the CS. What we want is an indication on
the
> > CS
> > > media streams where recording is actually taking place or not, and
> > that
> > > should not involve changing the directionality of the actual media
> > > stream.
> > > On the recording session media streams, we do use
> a=3Dsendrecv/sendonly
> > to
> > > indicate pause/resume.
> >
> > I see. This is really needed between the UA and the SRC, even if not
> > needed between the SRC and the SRS.
> >
> > > >
> > > > In section 6.3, recording preference, do we really need pause
and
> > > > resume? I am thinking record and norecord may be sufficient.
> > > >
> > > [[hlum]] The current consensus for the new wording of REQ-017
> > includes
> > > pause and resume:
> > >
> > > "REQ-zzz The mechanism MUST support a means for a recording-aware
UA
> > > involved in a CS to request during a session that the recording of
> > the
> > > CS should be started, paused, resumed or stopped, the honoring of
> > such
> > a
> > > request being dependent on policy."
> >
> > Here as well, it may not be needed between the SRC and the SRS, but
> > between a UA and a SRC, is that correct.
> >
> [[hlum]] Yes this mechanism is only for recording-aware UA in the CS.
>
> > Thanks,
> > Charles
> >
> > > > Cheers,
> > > > Charles
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> On
> > > > Behalf Of Henry Lum
> > > > > Sent: Wednesday, March 02, 2011 8:45 AM
> > > > > To: Paul Kyzivat (pkyzivat)
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] FW: New VersionNotificationfor
> > > > draft-portman-siprec-protocol-03
> > > > >
> > > > > I don't feel strongly too about using INFO so I am open to
using
> > > > UPDATE
> > > > > if the group feels that it is okay for SRC/SRS to deal with
the
> > > > > consequences of UPDATE collision.
> > > > >
> > > > > Henry
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > > > > > Sent: Tuesday, March 01, 2011 8:10 PM
> > > > > > To: Henry Lum
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] FW: New Version Notificationfor draft-
> > > > portman-
> > > > > > siprec-protocol-03
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 3/1/2011 2:32 PM, Henry Lum wrote:
> > > > > > > When there is an UPDATE transaction collision, you will
have
> > to
> > > > make
> > > > > > > both SRC and SRS to wait a while before being able to send
> > > UPDATE
> > > > > > again.
> > > > > > > Since SRC is normally the side initiating the SIP dialog,
it
> > is
> > > > the
> > > > > > > owner of the Call-ID and will come second after the SRS
has
> a
> > > > chance
> > > > > > to
> > > > > > > resend the UPDATE. In that case, does the SRC keep the
> > existing
> > > > > > UPDATE
> > > > > > > or send a new snapshot as requested by the SRS? The SRC
also
> > > need
> > > > to
> > > > > > > keep track of metadata changes while waiting for the
timer.
> I
> > > > worry
> > > > > > that
> > > > > > > it will make the solution more complicated than just using
> an
> > > > INFO
> > > > > > for
> > > > > > > snapshot request and minimize the collision problem.
> > > > > >
> > > > > > OK, collision on update is a *possibility*.
> > > > > > I guess the question is whether that justifies implementing
an
> > > > > entirely
> > > > > > different mechanism just for the rare error message.
> > > > > >
> > > > > > I expect that the likelihood of collision is pretty slim,
> given
> > > > that
> > > > > > messages from the SRS to the SRC will be very infrequent,
and
> > if
> > > > the
> > > > > > message comes shortly after a metadata is received from the
> > SRC,
> > > > there
> > > > > > may be little likelihood that the SRC will be sending more
> > > metadata
> > > > so
> > > > > > soon. And even if we don't use UPDATE for this, the SRC,
like
> > any
> > > > UA,
> > > > > > needs to be prepared to cope with a collision of this sort.
> > > > > >
> > > > > > But I don't feel *too* strongly about this.
> > > > > >
> > > > > >     Thanks,
> > > > > >     Paul
> > > > > >
> > > > > > > Regards,
> > > > > > > Henry
> > > > > > >
> > > > > > >> -----Original Message-----
> > > > > > >> From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org]
> > > > On
> > > > > > >> Behalf Of Paul Kyzivat
> > > > > > >> Sent: Tuesday, March 01, 2011 1:50 PM
> > > > > > >> To: siprec@ietf.org
> > > > > > >> Subject: Re: [siprec] FW: New Version Notificationfor
> > > > > draft-portman-
> > > > > > >> siprec-protocol-03
> > > > > > >>
> > > > > > >> Thanks Henry.
> > > > > > >>
> > > > > > >> One comment/question:
> > > > > > >>
> > > > > > >> Is there a reason to use an Info package for Requesting
for
> > > > > metadata
> > > > > > >> snapshot? Since we are already defining c-d recording-
> > session
> > > > and
> > > > > > >> passing bodies in invite/update for it, is there a reason
> > not
> > > to
> > > > > use
> > > > > > >> the
> > > > > > >> same mechanism to send error notifications/snapshop
> > requests?
> > > > > > >>
> > > > > > >> (I'm thinking just using a different content-type for
this,
> > and
> > > > of
> > > > > > >> course sending it from SRS to SRC.)
> > > > > > >>
> > > > > > >> Also, we could consider permitting (not requiring) this
in
> > the
> > > > > > >> responses
> > > > > > >> to the messages containing metadata.
> > > > > > >>
> > > > > > >>  Thanks,
> > > > > > >>  Paul
> > > > > > >>
> > > > > > >>
> > > > > > >> On 3/1/2011 12:13 PM, Henry Lum wrote:
> > > > > > >>> A new version has been submitted to address the
> outstanding
> > > > issues
> > > > > > >> and include extensions for the new wording for REQ-017
and
> > > > REQ-018.
> > > > > > >>>
> > > > > > >>>
> > > https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/
> > > > > > >>>
> > > > > > >>> Regards,
> > > > > > >>> Henry
> > > > > > >>>
> > > > > > >>> -----Original Message-----
> > > > > > >>> From: IETF I-D Submission Tool
> > [mailto:idsubmission@ietf.org]
> > > > > > >>> Sent: Tuesday, March 01, 2011 12:09 PM
> > > > > > >>> To: Henry Lum
> > > > > > >>> Cc: leon.portman@nice.com; alan.b.johnston@gmail.com;
> > > > > > >> andrew.hutton@siemens-enterprise.com
> > > > > > >>> Subject: New Version Notification for
> draft-portman-siprec-
> > > > > > protocol-
> > > > > > >> 03
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> A new version of I-D,
draft-portman-siprec-protocol-03.txt
> > has
> > > > > been
> > > > > > >> successfully submitted by Henry Lum and posted to the
IETF
> > > > > > repository.
> > > > > > >>>
> > > > > > >>> Filename:        draft-portman-siprec-protocol
> > > > > > >>> Revision:        03
> > > > > > >>> Title:           The SIP-based Media Recording Protocol
> > > > (SIPREC)
> > > > > > >>> Creation_date:   2011-03-01
> > > > > > >>> WG ID:           Independent Submission
> > > > > > >>> Number_of_pages: 20
> > > > > > >>>
> > > > > > >>> Abstract:
> > > > > > >>> SIPREC Session Recording Protocol is used for
establishing
> > > > > > recording
> > > > > > >>> session and reporting of the metadata of the
communication
> > > > > session.
> > > > > > >>>
> > > > > > >>> This document specifies the SIPREC Protocol (SIPREC).
> > SIPREC
> > > > is
> > > > > > > used
> > > > > > >>> between Session Recording Client (SRC) and Session
> > Recording
> > > > > Server
> > > > > > >>> (SRS).
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> The IETF Secretariat.
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > >> ----------------------------------------------
> > > > > > >>> CONFIDENTIALITY NOTICE: This e-mail and any files
attached
> > may
> > > > > > >> contain confidential and proprietary information of
> > > > Alcatel-Lucent
> > > > > > >> and/or its affiliated entities. Access by the intended
> > > recipient
> > > > > > only
> > > > > > >> is authorized. Any liability arising from any party
acting,
> > or
> > > > > > >> refraining from acting, on any information contained in
> this
> > > > e-mail
> > > > > > is
> > > > > > >> hereby excluded. If you are not the intended recipient,
> > please
> > > > > > notify
> > > > > > >> the sender immediately, destroy the original transmission
> > and
> > > > its
> > > > > > >> attachments and do not disclose the contents to any other
> > > > person,
> > > > > > use
> > > > > > >> it for any purpose, or store or copy the information in
any
> > > > medium.
> > > > > > >> Copyright in this e-mail and any attachments belongs to
> > > Alcatel-
> > > > > > Lucent
> > > > > > >> and/or its affiliated entities.
> > > > > > >>>
> > > > > > >>> _______________________________________________
> > > > > > >>> 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
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > ----------------------------------------------
> > > > > > > CONFIDENTIALITY NOTICE: This e-mail and any files attached
> > may
> > > > > > contain confidential and proprietary information of
> > Alcatel-Lucent
> > > > > > and/or its affiliated entities. Access by the intended
> > recipient
> > > > only
> > > > > > is authorized. Any liability arising from any party acting,
or
> > > > > > refraining from acting, on any information contained in this
> > > e-mail
> > > > is
> > > > > > hereby excluded. If you are not the intended recipient,
please
> > > > notify
> > > > > > the sender immediately, destroy the original transmission
and
> > its
> > > > > > attachments and do not disclose the contents to any other
> > person,
> > > > use
> > > > > > it for any purpose, or store or copy the information in any
> > > medium.
> > > > > > Copyright in this e-mail and any attachments belongs to
> > > > Alcatel-Lucent
> > > > > > and/or its affiliated entities.
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
-----------------------------------------------------------------------
> > > > -
> > > > ------------------------------
> > > > > -------------
> > > > > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > > > contain
> > > > confidential and proprietary
> > > > > information of Alcatel-Lucent and/or its affiliated entities.
> > Access
> > > > by the intended recipient only is
> > > > > authorized. Any liability arising from any party acting, or
> > > > refraining
> > > > from acting, on any information
> > > > > contained in this e-mail is hereby excluded. If you are not
the
> > > > intended recipient, please notify the
> > > > > sender immediately, destroy the original transmission and its
> > > > attachments and do not disclose the
> > > > > contents to any other person, use it for any purpose, or store
> or
> > > > copy
> > > > the information in any medium.
> > > > > Copyright in this e-mail and any attachments belongs to
Alcatel-
> > > > Lucent
> > > > and/or its affiliated entities.
> > > > >
> > > > > _______________________________________________
> > > > > siprec mailing list
> > > > > siprec@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/siprec
> > >
> > >
> > >
> >
>
-----------------------------------------------------------------------
> > -
> > ------------------------------
> > > -------------
> > > CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> > contain
> > confidential and proprietary
> > > information of Alcatel-Lucent and/or its affiliated entities.
Access
> > by the intended recipient only is
> > > authorized. Any liability arising from any party acting, or
> > refraining
> > from acting, on any information
> > > contained in this e-mail is hereby excluded. If you are not the
> > intended recipient, please notify the
> > > sender immediately, destroy the original transmission and its
> > attachments and do not disclose the
> > > contents to any other person, use it for any purpose, or store or
> > copy
> > the information in any medium.
> > > Copyright in this e-mail and any attachments belongs to Alcatel-
> > Lucent
> > and/or its affiliated entities.
> > >
>
>
>
------------------------------------------------------------------------
------------------------------
> -------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary
> information of Alcatel-Lucent and/or its affiliated entities. Access
by the intended recipient only is
> authorized. Any liability arising from any party acting, or refraining
from acting, on any information
> contained in this e-mail is hereby excluded. If you are not the
intended recipient, please notify the
> sender immediately, destroy the original transmission and its
attachments and do not disclose the
> contents to any other person, use it for any purpose, or store or copy
the information in any medium.
> Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
>
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec



------_=_NextPart_001_01CBDC29.B0077E0F
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: [siprec] FW: NewVersionNotificationfor =
draft-portman-siprec-protocol-03</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText64484>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>Hi =
Henry,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>I agree with Paul &amp; =
Charles for INFO vs UPDATE or RE-INVITE without SDP. My general comments =
and doubt are as follows:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2>1) Fig 2 Step 5 indicates callid. Pls =
elaborate what is the callid represented here?<?xml:namespace prefix =3D =
o ns =3D "urn:schemas-microsoft-com:office:office" =
/><o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><o:p><FONT size=3D2 =
face=3DArial>&nbsp;</FONT></o:p></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2>2) Sec 4.3,<SPAN style=3D"mso-spacerun: =
yes">&nbsp; </SPAN>"The metadata snapshot request will be provided as an =
INFO<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp; </SPAN>package [RFC6086] and sent as mid-dialog =
messages within the<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp; </SPAN>recording session by the SRS." it shall be =
UPDATE or RE-INVITE without SDP with request for complete =
metadata.<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><o:p><FONT size=3D2 =
face=3DArial>&nbsp;</FONT></o:p></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2>3) Sec 4.3 last para: "however, it =
is<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp; </SPAN>envisioned that a link with a URI can be =
provided in the recording<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp; </SPAN>session INVITE message so that the SRS can =
access the session<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp; </SPAN>metadata via the URI provided that the SRS =
supports the type of URI."<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp; </SPAN>Any new mechanism will be introduced in RS to =
pass this link?<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><o:p><FONT size=3D2 =
face=3DArial>&nbsp;</FONT></o:p></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2>4) Sec 5 last para: During mid-dialog =
transaction in Recording session (dialog) between SRC and SRS, SRC and =
SRC SHALL support all SIP mid-dialog behavior between two UA. IOW, SRS =
may be sending RE-INVITE/UDPATE for media attributes change, session =
timer or any other reason.<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><o:p><FONT size=3D2 =
face=3DArial>&nbsp;</FONT></o:p></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2>5) Update Sec 5.3.1 as per the comment 1 =
wherein Re-INVITE/UPDATE shall be used to request new metadata =
snapshot</FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2></FONT></FONT>&nbsp;</P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2>6) As earlier discussed, pls include the =
possible error code in the draft.</FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><o:p><FONT size=3D2 =
face=3DArial>&nbsp;</FONT></o:p></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2>Doubt:<o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2>1) Fig 3 which may leads to UA A moves out =
of the conference right?</FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2></FONT></FONT>&nbsp;</P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT =
face=3DArial><FONT size=3D2>Please read inline for more =
comments</FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT size=3D2 =
face=3DArial></FONT>&nbsp;</P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT size=3D2 =
face=3DArial>Thanks</FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT size=3D2 =
face=3DArial>Partha</FONT></P></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> siprec-bounces@ietf.org on =
behalf of Charles Eckel (eckelcu)<BR><B>Sent:</B> Fri 3/4/2011 11:45 =
PM<BR><B>To:</B> Henry Lum; Paul Kyzivat (pkyzivat)<BR><B>Cc:</B> =
siprec@ietf.org<BR><B>Subject:</B> Re: [siprec] FW: =
NewVersionNotificationfor =
draft-portman-siprec-protocol-03<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Please see inline.<BR><BR>&gt; -----Original =
Message-----<BR>&gt; From: Henry Lum [<A =
href=3D"mailto:Henry.Lum@alcatel-lucent.com">mailto:Henry.Lum@alcatel-luc=
ent.com</A>]<BR>&gt; Sent: Friday, March 04, 2011 10:03 AM<BR>&gt; To: =
Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat)<BR>&gt; Cc: =
siprec@ietf.org<BR>&gt; Subject: RE: [siprec] FW: New =
VersionNotificationfor<BR>draft-portman-siprec-protocol-03<BR>&gt;<BR>&gt=
; Inline.<BR>&gt;<BR>&gt; &gt; -----Original Message-----<BR>&gt; &gt; =
From: Charles Eckel (eckelcu) [<A =
href=3D"mailto:eckelcu@cisco.com">mailto:eckelcu@cisco.com</A>]<BR>&gt; =
&gt; Sent: Friday, March 04, 2011 12:47 PM<BR>&gt; &gt; To: Henry Lum; =
Paul Kyzivat (pkyzivat)<BR>&gt; &gt; Cc: siprec@ietf.org<BR>&gt; &gt; =
Subject: RE: [siprec] FW: New VersionNotificationfor =
draft-portman-<BR>&gt; &gt; siprec-protocol-03<BR>&gt; &gt;<BR>&gt; &gt; =
Hi Henry,<BR>&gt; &gt;<BR>&gt; &gt; Please see inline.<BR>&gt; =
&gt;<BR>&gt; &gt; &gt; -----Original Message-----<BR>&gt; &gt; &gt; =
From: Henry Lum [<A =
href=3D"mailto:Henry.Lum@alcatel-lucent.com">mailto:Henry.Lum@alcatel-luc=
ent.com</A>]<BR>&gt; &gt; &gt; Sent: Friday, March 04, 2011 9:29 =
AM<BR>&gt; &gt; &gt; To: Charles Eckel (eckelcu); Paul Kyzivat =
(pkyzivat)<BR>&gt; &gt; &gt; Cc: siprec@ietf.org<BR>&gt; &gt; &gt; =
Subject: RE: [siprec] FW: New VersionNotificationfor<BR>&gt; &gt; =
draft-portman-siprec-protocol-03<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
Please see inline.<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; =
-----Original Message-----<BR>&gt; &gt; &gt; &gt; From: Charles Eckel =
(eckelcu) [<A =
href=3D"mailto:eckelcu@cisco.com">mailto:eckelcu@cisco.com</A>]<BR>&gt; =
&gt; &gt; &gt; Sent: Thursday, March 03, 2011 4:55 PM<BR>&gt; &gt; &gt; =
&gt; To: Henry Lum; Paul Kyzivat (pkyzivat)<BR>&gt; &gt; &gt; &gt; Cc: =
siprec@ietf.org<BR>&gt; &gt; &gt; &gt; Subject: RE: [siprec] FW: New =
VersionNotificationfor<BR>&gt; draft-portman-<BR>&gt; &gt; &gt; &gt; =
siprec-protocol-03<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; I think =
it is better to stick to using UPDATE and not introduce<BR>a<BR>&gt; =
&gt; need<BR>&gt; &gt; &gt; &gt; to use INFO. I would also expect that =
using re-INVITE instead of<BR>&gt; &gt; &gt; &gt; UPDATE,<BR>&gt; &gt; =
&gt; &gt; though not explicitly recommended, would work as well. =
What<BR>drives<BR>&gt; &gt; &gt; this<BR>&gt; &gt; &gt; &gt; is the =
inclusion of the newly defined tags and the actual<BR>&gt; =
metadata.<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; [[hlum]] Okay - let's =
hear if there are supporters for INFO before<BR>&gt; &gt; &gt; making a =
change.<BR>&gt; &gt;<BR>&gt; &gt; Okay.<BR>&gt; &gt;<BR>&gt; &gt; &gt; =
&gt; Section 5 reads,<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp; The SRC must be able to accept re-INVITE from SRS =
with the<BR>&gt; &gt; updated<BR>&gt; &gt; &gt; &gt;&nbsp;&nbsp;&nbsp; =
SDP as part of the session timer mechanism.<BR>&gt; &gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &gt; What is the purpose of stating this?<BR>&gt; =
&gt; &gt; &gt; I agree the SRC needs to be able<BR>&gt; &gt; &gt; &gt; =
to<BR>&gt; &gt; &gt; &gt; accept a re-INVITE with updated or non-updated =
SDP from the SRS.<BR>&gt; It<BR>&gt; &gt; &gt; &gt; also<BR>&gt; &gt; =
&gt; &gt; needs to be able to receive an UPDATE with updated =
or<BR>non-updated<BR>&gt; &gt; SDP.<BR>&gt; &gt; &gt; &gt; This appears =
to me to be independent of using session timer, and<BR>I<BR>&gt; &gt; =
do<BR>&gt; &gt; &gt; &gt; not believe we are mandating support for =
session timer either.<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; [[hlum]] =
Perhaps the wording may be a bit too explicit, but the<BR>&gt; &gt; &gt; =
intention is that a recording session should use session =
timer<BR>since<BR>&gt; &gt; the<BR>&gt; &gt; &gt; SRS never sends any =
media to the SRC and the SRC needs a way to<BR>tell<BR>&gt; &gt; &gt; =
that the SRS is still around. I don't think session timer needs =
to<BR>&gt; be<BR>&gt; &gt; &gt; mandated but I think it is recommended =
that we use it.<BR>&gt; &gt;<BR>&gt; &gt; I am not a fan of that. I =
think session timer is optional. What is<BR>&gt; &gt; mandatory in my =
opinion is that the SRS sends RTCP messages, and<BR>that<BR>&gt; &gt; =
lets you know if is there and receiving the media. It also should =
do<BR>&gt; &gt; something to make sure the RTP port does not get closed =
by a<BR>&gt; &gt; firewall/NAT, and there are several mechanisms for =
that. That said,<BR>&gt; &gt; this<BR>&gt; &gt; is not specific to =
SIPREC, so I do not think we need explicit<BR>&gt; &gt; requirements, =
but if we are providing recommendations those are the<BR>&gt; =
one<BR>&gt; &gt; I suggest providing.<BR>&gt;<BR>&gt; [[hlum]] Agreed =
that this problem is not specific to SIPREC. The SRS<BR>&gt; does not =
send RTP to the SRC so I don't think it matters when that RTP<BR>&gt; =
port gets closed, but it makes sense to for SRS to send RTCP =
messages<BR>to<BR>&gt; the SRC to acknowledge receipt of recorded media. =
Do we need to<BR>mandate<BR>&gt; this?<BR><BR>RFC 3550 already mandates =
RTCP. We could reference<BR>draft-marjou-behave-app-rtp-keepalive and =
RFC 5761, but I do not think<BR>we need to mandate =
this.<BR><BR>Cheers,<BR>Charles</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; SRS &amp; SRC MUST mid-dialog behavior =
of RFC 3261 which includes codec change, media change, session timer =
(optional)&nbsp; &lt;/Partha&gt;<BR><BR>&gt; &gt;<BR>&gt; &gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &gt; In section 6.2, what does the "record" =
attribute and the defined<BR>&gt; &gt; &gt; &gt; "indication" attribute =
give us that we do not already have using<BR>&gt; &gt; &gt; &gt; =
sendonly and inactive, where off/pause maps to inactive and on<BR>&gt; =
maps<BR>&gt; &gt; to<BR>&gt; &gt; &gt; &gt; sendonly?<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt; [[hlum]] a=3Dsendrev/sendonly/recvonly describes =
the directionality<BR>of<BR>&gt; &gt; the<BR>&gt; &gt; &gt; actual media =
stream in the CS. What we want is an indication on<BR>the<BR>&gt; &gt; =
CS<BR>&gt; &gt; &gt; media streams where recording is actually taking =
place or not, and<BR>&gt; &gt; that<BR>&gt; &gt; &gt; should not involve =
changing the directionality of the actual media<BR>&gt; &gt; &gt; =
stream.<BR>&gt; &gt; &gt; On the recording session media streams, we do =
use<BR>&gt; a=3Dsendrecv/sendonly<BR>&gt; &gt; to<BR>&gt; &gt; &gt; =
indicate pause/resume.<BR>&gt; &gt;<BR>&gt; &gt; I see. This is really =
needed between the UA and the SRC, even if not<BR>&gt; &gt; needed =
between the SRC and the SRS.<BR>&gt; &gt;<BR>&gt; &gt; &gt; &gt;<BR>&gt; =
&gt; &gt; &gt; In section 6.3, recording preference, do we really need =
pause<BR>and<BR>&gt; &gt; &gt; &gt; resume? I am thinking record and =
norecord may be sufficient.<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; =
[[hlum]] The current consensus for the new wording of REQ-017<BR>&gt; =
&gt; includes<BR>&gt; &gt; &gt; pause and resume:<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt; "REQ-zzz The mechanism MUST support a means for a =
recording-aware<BR>UA<BR>&gt; &gt; &gt; involved in a CS to request =
during a session that the recording of<BR>&gt; &gt; the<BR>&gt; &gt; =
&gt; CS should be started, paused, resumed or stopped, the honoring =
of<BR>&gt; &gt; such<BR>&gt; &gt; a<BR>&gt; &gt; &gt; request being =
dependent on policy."<BR>&gt; &gt;<BR>&gt; &gt; Here as well, it may not =
be needed between the SRC and the SRS, but<BR>&gt; &gt; between a UA and =
a SRC, is that correct.<BR>&gt; &gt;<BR>&gt; [[hlum]] Yes this mechanism =
is only for recording-aware UA in the CS.<BR>&gt;<BR>&gt; &gt; =
Thanks,<BR>&gt; &gt; Charles<BR>&gt; &gt;<BR>&gt; &gt; &gt; &gt; =
Cheers,<BR>&gt; &gt; &gt; &gt; Charles<BR>&gt; &gt; &gt; &gt;<BR>&gt; =
&gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt; -----Original =
Message-----<BR>&gt; &gt; &gt; &gt; &gt; From: siprec-bounces@ietf.org =
[<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>]<BR>&gt; On<BR>&gt; &gt; &gt; &gt; Behalf Of Henry Lum<BR>&gt; &gt; =
&gt; &gt; &gt; Sent: Wednesday, March 02, 2011 8:45 AM<BR>&gt; &gt; &gt; =
&gt; &gt; To: Paul Kyzivat (pkyzivat)<BR>&gt; &gt; &gt; &gt; &gt; Cc: =
siprec@ietf.org<BR>&gt; &gt; &gt; &gt; &gt; Subject: Re: [siprec] FW: =
New VersionNotificationfor<BR>&gt; &gt; &gt; &gt; =
draft-portman-siprec-protocol-03<BR>&gt; &gt; &gt; &gt; &gt;<BR>&gt; =
&gt; &gt; &gt; &gt; I don't feel strongly too about using INFO so I am =
open to<BR>using<BR>&gt; &gt; &gt; &gt; UPDATE<BR>&gt; &gt; &gt; &gt; =
&gt; if the group feels that it is okay for SRC/SRS to deal =
with<BR>the<BR>&gt; &gt; &gt; &gt; &gt; consequences of UPDATE =
collision.<BR>&gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt; =
Henry<BR>&gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
-----Original Message-----<BR>&gt; &gt; &gt; &gt; &gt; &gt; From: Paul =
Kyzivat [<A =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</A>]<BR>&gt;=
 &gt; &gt; &gt; &gt; &gt; Sent: Tuesday, March 01, 2011 8:10 PM<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; To: Henry Lum<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
Cc: siprec@ietf.org<BR>&gt; &gt; &gt; &gt; &gt; &gt; Subject: Re: =
[siprec] FW: New Version Notificationfor draft-<BR>&gt; &gt; &gt; &gt; =
portman-<BR>&gt; &gt; &gt; &gt; &gt; &gt; siprec-protocol-03<BR>&gt; =
&gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; =
&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; On 3/1/2011 2:32 =
PM, Henry Lum wrote:<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt; When there is =
an UPDATE transaction collision, you will<BR>have<BR>&gt; &gt; =
to<BR>&gt; &gt; &gt; &gt; make<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt; =
both SRC and SRS to wait a while before being able to send<BR>&gt; &gt; =
&gt; UPDATE<BR>&gt; &gt; &gt; &gt; &gt; &gt; again.<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; &gt; Since SRC is normally the side initiating the SIP =
dialog,<BR>it<BR>&gt; &gt; is<BR>&gt; &gt; &gt; &gt; the<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt; owner of the Call-ID and will come second after =
the SRS<BR>has<BR>&gt; a<BR>&gt; &gt; &gt; &gt; chance<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; to<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt; resend the =
UPDATE. In that case, does the SRC keep the<BR>&gt; &gt; =
existing<BR>&gt; &gt; &gt; &gt; &gt; &gt; UPDATE<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt; or send a new snapshot as requested by the SRS? The =
SRC<BR>also<BR>&gt; &gt; &gt; need<BR>&gt; &gt; &gt; &gt; to<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; &gt; keep track of metadata changes while =
waiting for the<BR>timer.<BR>&gt; I<BR>&gt; &gt; &gt; &gt; worry<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; that<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt; it =
will make the solution more complicated than just using<BR>&gt; =
an<BR>&gt; &gt; &gt; &gt; INFO<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
for<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt; snapshot request and minimize =
the collision problem.<BR>&gt; &gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; OK, collision on update is a *possibility*.<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; I guess the question is whether that justifies =
implementing<BR>an<BR>&gt; &gt; &gt; &gt; &gt; entirely<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; different mechanism just for the rare error =
message.<BR>&gt; &gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt; =
&gt; I expect that the likelihood of collision is pretty slim,<BR>&gt; =
given<BR>&gt; &gt; &gt; &gt; that<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
messages from the SRS to the SRC will be very infrequent,<BR>and<BR>&gt; =
&gt; if<BR>&gt; &gt; &gt; &gt; the<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
message comes shortly after a metadata is received from the<BR>&gt; &gt; =
SRC,<BR>&gt; &gt; &gt; &gt; there<BR>&gt; &gt; &gt; &gt; &gt; &gt; may =
be little likelihood that the SRC will be sending more<BR>&gt; &gt; &gt; =
metadata<BR>&gt; &gt; &gt; &gt; so<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
soon. And even if we don't use UPDATE for this, the SRC,<BR>like<BR>&gt; =
&gt; any<BR>&gt; &gt; &gt; &gt; UA,<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
needs to be prepared to cope with a collision of this sort.<BR>&gt; &gt; =
&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; But I don't feel =
*too* strongly about this.<BR>&gt; &gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &nbsp;&nbsp;&nbsp; Thanks,<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &nbsp;&nbsp;&nbsp; Paul<BR>&gt; &gt; &gt; &gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt; Regards,<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; &gt; Henry<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; &gt;&gt; -----Original Message-----<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; &gt;&gt; From: siprec-bounces@ietf.org<BR>&gt; =
&gt; [<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>]<BR>&gt; &gt; &gt; &gt; On<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; =
Behalf Of Paul Kyzivat<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; Sent: =
Tuesday, March 01, 2011 1:50 PM<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt; To: siprec@ietf.org<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; =
Subject: Re: [siprec] FW: New Version Notificationfor<BR>&gt; &gt; &gt; =
&gt; &gt; draft-portman-<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; =
siprec-protocol-03<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; &gt;&gt; Thanks Henry.<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; One =
comment/question:<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt; Is there a reason to use an Info package =
for Requesting<BR>for<BR>&gt; &gt; &gt; &gt; &gt; metadata<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt; snapshot? Since we are already defining c-d =
recording-<BR>&gt; &gt; session<BR>&gt; &gt; &gt; &gt; and<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt; passing bodies in invite/update for it, is =
there a reason<BR>&gt; &gt; not<BR>&gt; &gt; &gt; to<BR>&gt; &gt; &gt; =
&gt; &gt; use<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; the<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt; same mechanism to send error =
notifications/snapshop<BR>&gt; &gt; requests?<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; (I'm =
thinking just using a different content-type for<BR>this,<BR>&gt; &gt; =
and<BR>&gt; &gt; &gt; &gt; of<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; =
course sending it from SRS to SRC.)<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; Also, we could =
consider permitting (not requiring) this<BR>in<BR>&gt; &gt; the<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; &gt;&gt; responses<BR>&gt; &gt; &gt; &gt; &gt; =
&gt; &gt;&gt; to the messages containing metadata.<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; &gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&nbsp; =
Thanks,<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&nbsp; Paul<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; &gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; On 3/1/2011 12:13 PM, =
Henry Lum wrote:<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; A new =
version has been submitted to address the<BR>&gt; outstanding<BR>&gt; =
&gt; &gt; &gt; issues<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; and =
include extensions for the new wording for REQ-017<BR>and<BR>&gt; &gt; =
&gt; &gt; REQ-018.<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt; <A =
href=3D"https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/">=
https://datatracker.ietf.org/doc/draft-portman-siprec-protocol/</A><BR>&g=
t; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; =
&gt; &gt;&gt;&gt; Regards,<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; =
Henry<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; &gt;&gt;&gt; -----Original Message-----<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; &gt;&gt;&gt; From: IETF I-D Submission Tool<BR>&gt; &gt; =
[<A =
href=3D"mailto:idsubmission@ietf.org">mailto:idsubmission@ietf.org</A>]<B=
R>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; Sent: Tuesday, March 01, =
2011 12:09 PM<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; To: Henry =
Lum<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; Cc: =
leon.portman@nice.com; alan.b.johnston@gmail.com;<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt;&gt; andrew.hutton@siemens-enterprise.com<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt;&gt; Subject: New Version Notification =
for<BR>&gt; draft-portman-siprec-<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
protocol-<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; 03<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; A new version =
of I-D,<BR>draft-portman-siprec-protocol-03.txt<BR>&gt; &gt; has<BR>&gt; =
&gt; &gt; &gt; &gt; been<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; =
successfully submitted by Henry Lum and posted to the<BR>IETF<BR>&gt; =
&gt; &gt; &gt; &gt; &gt; repository.<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; =
Filename:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-portman-siprec-protocol<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt; Revision:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
03<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; Title:&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The SIP-based Media =
Recording Protocol<BR>&gt; &gt; &gt; &gt; (SIPREC)<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; &gt;&gt;&gt; Creation_date:&nbsp;&nbsp; =
2011-03-01<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; WG ID:&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Independent =
Submission<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; =
Number_of_pages: 20<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; =
Abstract:<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; SIPREC Session =
Recording Protocol is used for<BR>establishing<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; recording<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; =
session and reporting of the metadata of the<BR>communication<BR>&gt; =
&gt; &gt; &gt; &gt; session.<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; This document =
specifies the SIPREC Protocol (SIPREC).<BR>&gt; &gt; SIPREC<BR>&gt; &gt; =
&gt; &gt; is<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt; used<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt;&gt; between Session Recording Client (SRC) =
and Session<BR>&gt; &gt; Recording<BR>&gt; &gt; &gt; &gt; &gt; =
Server<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt; (SRS).<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt;&gt; The IETF Secretariat.<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; =
&gt; &gt;<BR>&gt; &gt; &gt;<BR>&gt; =
---------------------------------------------------------------------<BR>=
&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; =
----------------------------------------------<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt;&gt;&gt; CONFIDENTIALITY NOTICE: This e-mail and any =
files<BR>attached<BR>&gt; &gt; may<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt; contain confidential and proprietary information of<BR>&gt; =
&gt; &gt; &gt; Alcatel-Lucent<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; =
and/or its affiliated entities. Access by the intended<BR>&gt; &gt; &gt; =
recipient<BR>&gt; &gt; &gt; &gt; &gt; &gt; only<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt;&gt; is authorized. Any liability arising from any =
party<BR>acting,<BR>&gt; &gt; or<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt; refraining from acting, on any information contained in<BR>&gt; =
this<BR>&gt; &gt; &gt; &gt; e-mail<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
is<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; hereby excluded. If you are =
not the intended recipient,<BR>&gt; &gt; please<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; notify<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; the sender =
immediately, destroy the original transmission<BR>&gt; &gt; and<BR>&gt; =
&gt; &gt; &gt; its<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; attachments =
and do not disclose the contents to any other<BR>&gt; &gt; &gt; &gt; =
person,<BR>&gt; &gt; &gt; &gt; &gt; &gt; use<BR>&gt; &gt; &gt; &gt; &gt; =
&gt; &gt;&gt; it for any purpose, or store or copy the information =
in<BR>any<BR>&gt; &gt; &gt; &gt; medium.<BR>&gt; &gt; &gt; &gt; &gt; =
&gt; &gt;&gt; Copyright in this e-mail and any attachments belongs =
to<BR>&gt; &gt; &gt; Alcatel-<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
Lucent<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; and/or its affiliated =
entities.<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; &gt;&gt;&gt; =
_______________________________________________<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt;&gt;&gt; siprec mailing list<BR>&gt; &gt; &gt; &gt; &gt; =
&gt; &gt;&gt;&gt; siprec@ietf.org<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; =
_______________________________________________<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt;&gt; siprec mailing list<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;&gt; siprec@ietf.org<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;&gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR>&gt; &gt; &gt; &gt; &gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt; =
&gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt;<BR>&gt; =
---------------------------------------------------------------------<BR>=
&gt; &gt; &gt; &gt; &gt; &gt; =
----------------------------------------------<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt; CONFIDENTIALITY NOTICE: This e-mail and any files =
attached<BR>&gt; &gt; may<BR>&gt; &gt; &gt; &gt; &gt; &gt; contain =
confidential and proprietary information of<BR>&gt; &gt; =
Alcatel-Lucent<BR>&gt; &gt; &gt; &gt; &gt; &gt; and/or its affiliated =
entities. Access by the intended<BR>&gt; &gt; recipient<BR>&gt; &gt; =
&gt; &gt; only<BR>&gt; &gt; &gt; &gt; &gt; &gt; is authorized. Any =
liability arising from any party acting,<BR>or<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; refraining from acting, on any information contained in =
this<BR>&gt; &gt; &gt; e-mail<BR>&gt; &gt; &gt; &gt; is<BR>&gt; &gt; =
&gt; &gt; &gt; &gt; hereby excluded. If you are not the intended =
recipient,<BR>please<BR>&gt; &gt; &gt; &gt; notify<BR>&gt; &gt; &gt; =
&gt; &gt; &gt; the sender immediately, destroy the original =
transmission<BR>and<BR>&gt; &gt; its<BR>&gt; &gt; &gt; &gt; &gt; &gt; =
attachments and do not disclose the contents to any other<BR>&gt; &gt; =
person,<BR>&gt; &gt; &gt; &gt; use<BR>&gt; &gt; &gt; &gt; &gt; &gt; it =
for any purpose, or store or copy the information in any<BR>&gt; &gt; =
&gt; medium.<BR>&gt; &gt; &gt; &gt; &gt; &gt; Copyright in this e-mail =
and any attachments belongs to<BR>&gt; &gt; &gt; &gt; =
Alcatel-Lucent<BR>&gt; &gt; &gt; &gt; &gt; &gt; and/or its affiliated =
entities.<BR>&gt; &gt; &gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; =
&gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; =
&gt;<BR>&gt; =
&gt;<BR>&gt;<BR>---------------------------------------------------------=
--------------<BR>&gt; &gt; &gt; &gt; -<BR>&gt; &gt; &gt; &gt; =
------------------------------<BR>&gt; &gt; &gt; &gt; &gt; =
-------------<BR>&gt; &gt; &gt; &gt; &gt; CONFIDENTIALITY NOTICE: This =
e-mail and any files attached may<BR>&gt; &gt; &gt; &gt; contain<BR>&gt; =
&gt; &gt; &gt; confidential and proprietary<BR>&gt; &gt; &gt; &gt; &gt; =
information of Alcatel-Lucent and/or its affiliated entities.<BR>&gt; =
&gt; Access<BR>&gt; &gt; &gt; &gt; by the intended recipient only =
is<BR>&gt; &gt; &gt; &gt; &gt; authorized. Any liability arising from =
any party acting, or<BR>&gt; &gt; &gt; &gt; refraining<BR>&gt; &gt; &gt; =
&gt; from acting, on any information<BR>&gt; &gt; &gt; &gt; &gt; =
contained in this e-mail is hereby excluded. If you are =
not<BR>the<BR>&gt; &gt; &gt; &gt; intended recipient, please notify =
the<BR>&gt; &gt; &gt; &gt; &gt; sender immediately, destroy the original =
transmission and its<BR>&gt; &gt; &gt; &gt; attachments and do not =
disclose the<BR>&gt; &gt; &gt; &gt; &gt; contents to any other person, =
use it for any purpose, or store<BR>&gt; or<BR>&gt; &gt; &gt; &gt; =
copy<BR>&gt; &gt; &gt; &gt; the information in any medium.<BR>&gt; &gt; =
&gt; &gt; &gt; Copyright in this e-mail and any attachments belongs =
to<BR>Alcatel-<BR>&gt; &gt; &gt; &gt; Lucent<BR>&gt; &gt; &gt; &gt; =
and/or its affiliated entities.<BR>&gt; &gt; &gt; &gt; &gt;<BR>&gt; &gt; =
&gt; &gt; &gt; _______________________________________________<BR>&gt; =
&gt; &gt; &gt; &gt; siprec mailing list<BR>&gt; &gt; &gt; &gt; &gt; =
siprec@ietf.org<BR>&gt; &gt; &gt; &gt; &gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR>&gt; &gt; &gt;<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt;<BR>&gt; =
&gt;<BR>&gt;<BR>---------------------------------------------------------=
--------------<BR>&gt; &gt; -<BR>&gt; &gt; =
------------------------------<BR>&gt; &gt; &gt; -------------<BR>&gt; =
&gt; &gt; CONFIDENTIALITY NOTICE: This e-mail and any files attached =
may<BR>&gt; &gt; contain<BR>&gt; &gt; confidential and =
proprietary<BR>&gt; &gt; &gt; information of Alcatel-Lucent and/or its =
affiliated entities.<BR>Access<BR>&gt; &gt; by the intended recipient =
only is<BR>&gt; &gt; &gt; authorized. Any liability arising from any =
party acting, or<BR>&gt; &gt; refraining<BR>&gt; &gt; from acting, on =
any information<BR>&gt; &gt; &gt; contained in this e-mail is hereby =
excluded. If you are not the<BR>&gt; &gt; intended recipient, please =
notify the<BR>&gt; &gt; &gt; sender immediately, destroy the original =
transmission and its<BR>&gt; &gt; attachments and do not disclose =
the<BR>&gt; &gt; &gt; contents to any other person, use it for any =
purpose, or store or<BR>&gt; &gt; copy<BR>&gt; &gt; the information in =
any medium.<BR>&gt; &gt; &gt; Copyright in this e-mail and any =
attachments belongs to Alcatel-<BR>&gt; &gt; Lucent<BR>&gt; &gt; and/or =
its affiliated entities.<BR>&gt; &gt; =
&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>-----------------------------------------=
-------------------------------<BR>------------------------------<BR>&gt;=
 -------------<BR>&gt; CONFIDENTIALITY NOTICE: This e-mail and any files =
attached may contain<BR>confidential and proprietary<BR>&gt; information =
of Alcatel-Lucent and/or its affiliated entities. Access<BR>by the =
intended recipient only is<BR>&gt; authorized. Any liability arising =
from any party acting, or refraining<BR>from acting, on any =
information<BR>&gt; contained in this e-mail is hereby excluded. If you =
are not the<BR>intended recipient, please notify the<BR>&gt; sender =
immediately, destroy the original transmission and its<BR>attachments =
and do not disclose the<BR>&gt; contents to any other person, use it for =
any purpose, or store or copy<BR>the information in any medium.<BR>&gt; =
Copyright in this e-mail and any attachments belongs to =
Alcatel-Lucent<BR>and/or its affiliated =
entities.<BR>&gt;<BR>_______________________________________________<BR>s=
iprec mailing list<BR>siprec@ietf.org<BR><A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR></P></FONT></DIV></BODY></HTML>
------_=_NextPart_001_01CBDC29.B0077E0F--

From partr@cisco.com  Sun Mar  6 23:38:32 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BABC63A6923 for <siprec@core3.amsl.com>; Sun,  6 Mar 2011 23:38:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.78
X-Spam-Level: 
X-Spam-Status: No, score=-9.78 tagged_above=-999 required=5 tests=[AWL=0.219,  BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r-1QeoMmzmLx for <siprec@core3.amsl.com>; Sun,  6 Mar 2011 23:38:31 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 2659C3A68F2 for <siprec@ietf.org>; Sun,  6 Mar 2011 23:38:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=9715; q=dns/txt; s=iport; t=1299483584; x=1300693184; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=Vs8zLQPGI1nUt/V7XauuLEJL/TAA0WPJh0qLK4jIFMU=; b=PH9qTexo5tWBTRWzYCYdP8sBCXFmgIIQH45Tzms1qDqAKCkragMtxsCS d4GLLtoGACO3RAptJJuUeUHZBjWqgSijKg+p+wVwkKdlR5aLTI1ReIXZi Uq2KvHLrSkxsoKnqFbRJ/zaotLEa/iKPuFBxu7N8s+1ac9suLgBSanjdt 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggBAGIadE1AaMHG/2dsb2JhbACYDY48dKJwmw+CfoJkBIUail8
X-IronPort-AV: E=Sophos;i="4.62,276,1297036800"; d="scan'208";a="317551895"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-2.cisco.com with ESMTP; 07 Mar 2011 07:39:43 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p277dejX005683; Mon, 7 Mar 2011 07:39:42 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 7 Mar 2011 13:09:40 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 7 Mar 2011 13:09:42 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904B1DC49@XMB-BGL-411.cisco.com>
In-Reply-To: <4D712B5F.40805@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Synchronous vs Asynchronous Error handling
Thread-Index: Acval6PGBvtWEgOWRy+FwKyElMuFbACAj2lg
References: <A11921905DA1564D9BCF64A6430A62390293A665@XMB-BGL-411.cisco.com><4D67EC69.7080507@cisco.com><059AF07365DC474393A19A3AF187DF7406BADEA6@NAHALD.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2BAA742@MCHP058A.global-ad.net><4D6BBDAE.3020808@cisco.com><059AF07365DC474393A19A3AF187DF7406BAE02F@NAHALD.us.int.genesyslab.com><07465C1D981ABC41A344374066AE1A2C38A81E5A0C@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A623904A63B8A@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB991A@xmb-sjc-234.amer.cisco.com> <4D70423D.7030202@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB9A9F@xmb-sjc-234.amer.cisco.com> <4D712B5F.40805@cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
X-OriginalArrivalTime: 07 Mar 2011 07:39:40.0642 (UTC) FILETIME=[D1667C20:01CBDC9A]
Cc: Leon Portman <Leon.Portman@nice.com>, Henry Lum <Henry.Lum@alcatel-lucent.com>, siprec@ietf.org
Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 07 Mar 2011 07:38:32 -0000

IIRC, asynchronous Error handling of metadata is required to re-sync
between SRS & SRC and SRS has to trigger re-sync. Let us discuss the
exact mechanism as part of draft-portman-siprec-protocol-03 draft
review.

Thanks
Partha

-----Original Message-----
From: Paul Kyzivat (pkyzivat)=20
Sent: Friday, March 04, 2011 11:42 PM
To: Charles Eckel (eckelcu)
Cc: Parthasarathi R (partr); Leon Portman; Henry Lum; Elwell, John;
siprec@ietf.org
Subject: Re: [siprec] Synchronous vs Asynchronous Error handling

yes

On 3/4/2011 12:22 PM, Charles Eckel (eckelcu) wrote:
> Hi Paul,
>
> I think we are both saying the same thing, but let me make sure. In=20
> cases in which processing everything synchronously is not feasible, an

> implementation MUST send an SDP answer synchronously in order to=20
> complete the existing SIP transaction, then complete the processing of

> the metadata asynchronously, and if required, MAY send an offer in=20
> another SIP transaction to address and changes required.
>
> Cheers,
> Charles
>
>> -----Original Message-----
>> From: Paul Kyzivat (pkyzivat)
>> Sent: Thursday, March 03, 2011 5:37 PM
>> To: Charles Eckel (eckelcu)
>> Cc: Parthasarathi R (partr); Leon Portman; Henry Lum; Elwell, John;
> siprec@ietf.org
>> Subject: Re: [siprec] Synchronous vs Asynchronous Error handling
>>
>> Charles,
>>
>> Its my expectation that none of the metadata *need* be processed in=20
>> order to answer an sdp offer. However the sdp will typically be
> required
>> to supplement the metadata processing. So it likely will be necessary
> to
>> queue the xml+sdp for later processing as metadata.
>>
>> One might want to make decisions about how to construct the answer
> (e.g.
>> whether to accept or reject a media stream) based on the xml
metadata.
>> If one is capable of doing all the processing synchronously in order
> to
>> do so, go for it. But nobody should be forced to do that.
>>
>> 	Thanks,
>> 	Paul
>>
>> On 3/3/2011 6:41 PM, Charles Eckel (eckelcu) wrote:
>>> Hi Partha,
>>>
>>> I think we need both. If the error is detected in SDP processing,=20
>>> handling it in the SIP response synchronously makes sense. If the
> error
>>> is detected in the metadata processing, it would ideally be handled
> in
>>> the SIP response synchronously, but it may result in a subsequent=20
>>> request being sent to indicate and/or recover from the error. Errors
> may
>>> also be encountered independent of any SIP request processing, and
> those
>>> will need to be handled asynchronously.
>>> So I think we need both, and how much of the XML to process=20
>>> synchronously is up to the answerer. Ideally we will structure the
> XML
>>> such that it is as clear and efficient as possible to identify the
> XML
>>> that directly impacts the SDP. This will facilitate synchronous=20
>>> responses.
>>>
>>> Cheers,
>>> Charles
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf Of Parthasarathi R (partr)
>>>> Sent: Wednesday, March 02, 2011 5:48 AM
>>>> To: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
>>>> Cc: siprec@ietf.org
>>>> Subject: [siprec] Synchronous vs Asynchronous Error handling
>>>>
>>>> Hi all,
>>>>
>>>> Another issue discussed as part of the below mail thread is whether

>>>> metadata (XML+SDP) error has to be responded synchronously (SIP=20
>>>> Request/[SIP provisional response]/SIP Response) or
> asynchronously(SIP
>>>> Request/SIP Response/SIP Error request/SIP Error response).
>>>>
>>>> Synchronous Error handling:
>>>>   From SRC perspective, synchronous error handling is simple to
>>> implement
>>>> as there is no extra context or state to be maintained about the
>>> earlier
>>>> SIP transactions.
>>>>
>>>> In SRS, SDP Metadata portion *MUST* be processed in synchronously
> to
>>>> meet offer/answer model requirement. Now the question is whether
> XML
>>>> takes so much of a time wherein the error MUST be handled
>>> asynchronous?
>>>> The simple SRS will be able to send provisional response and
> respond
>>>> back final response once the complete XML check is done. My
> reasoning
>>> is
>>>> so because B2BUA normally handles INVITE/RE-INVITE in a way that
> send
>>>> (100 trying) provisional response to the incoming dialog side, send

>>>> INVITE/RE-INVITE to the outgoing dialog side which may take upto 32
>>> sec
>>>> delay to respond and forwards 200 OK to incoming dialog side once
> it
>>> is
>>>> received from outgoing dialog side and it is well working deployed=20
>>>> model. Please let me know in which situation this mechanism has
> issues
>>>> specific to SIPREC&   XML.
>>>>
>>>> Asynchronous Error handling:
>>>> Here as well in SRS, SDP Metadata portion *MUST* be processed in=20
>>>> synchronously to meet offer/answer model requirement.
>>>>
>>>> Two cases exists from SRC perspective.
>>>> 1) In case the sequence number has to be maintained by SRC for=20
>>>> asynchronous error handling, then it *MAY* require SRC to maintain
> the
>>>> earlier transaction which is overkill as SRC will not keep track or

>>>> record its previous state.
>>>>
>>>> 2) In most of the scenario, it is not possible to re-record but it
> is
>>>> only possible to re-sync. In case the motivation of asynchronous
> error
>>>> is to re-sync metadata by SRS to SRC, it is very similar to SRS=20
>>>> requesting for current complete metadata (SDP+XML) from SRC. On=20
>>>> receiving re-sync request, SRC has to trigger the complete metadata

>>>> towards SRS. The sequence number from SRS *MAY* be used for logging

>>>> purpose if required.
>>>>
>>>> Please let me know which one of the above asynchronous behavior is=20
>>>> expected from SRC. Also, instead of asynchronous error message, do
> you
>>>> wish to create re-sync request mechanism from SRS which may be used
>>> for
>>>> error or other purpose as well.
>>>>
>>>> Thanks
>>>> Partha
>>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf
>>>> Of Leon Portman
>>>> Sent: Monday, February 28, 2011 9:48 PM
>>>> To: Henry Lum; Paul Kyzivat (pkyzivat); Elwell, John
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] Metadata XML document error representation=20
>>>> forwhole doc or for portion of doc
>>>>
>>>> +1
>>>>
>>>> Leon
>>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf
>>>> Of Henry Lum
>>>> Sent: Monday, February 28, 2011 6:13 PM
>>>> To: Paul Kyzivat; Elwell, John
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] Metadata XML document error representation
> for
>>>> whole doc or for portion of doc
>>>>
>>>>
>>>>
>>>>>>> We are also thinking of providing the SRS with a mechanism to=20
>>>>>>> request the SRC to ask for the current snapshot
>>>>> so
>>>>>>> that the SRC/SRS can reset the states in the case where SRS is
> in
>>> a
>>>>
>>>>>>> really bad state. By doing so, we may be able to avoid providing
>>>>> nack
>>>>>>> responses and avoid using a chatty protocol.
>>>>>> [JRE] Yes, and the request to resend full metadata could
>>> optionally
>>>>> include some sort of error report that gave rise to the request.
>>> That
>>>>> error report could, for example, include the sequence number of
> the
>>>>> metadata update that was found to be in error.
>>>>>
>>>>> That is sort of what I had in mind about getting the two sides in
>>>> sync.
>>>>> But we will have to think more about exactly what it means.
>>>>> At best I think it will describe the *current* state of things in
>>> this
>>>>
>>>>> RS, without regard to what has happened in the past.
>>>>>
>>>>> Even that may present some technical challenges. But we should
> keep
>>>>> this desire in mind.
>>>>
>>>> [[hlum]] I agree it would be reasonable for the SRC to send the
>>> current
>>>> state as a snapshot and forget what happened previously. The
>>> subsequent
>>>> sequence numbers only refers to the current snapshot rather than
> the
>>>> original one, so in a way we are resetting the sequence number.
>>>>
>>>>
>>>>
>>>
> ----------------------------------------------------------------------
> --
>>>> -------------------------------------------
>>>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may
> contain
>>>> confidential and proprietary information of Alcatel-Lucent and/or
> its
>>>> affiliated entities. Access by the intended recipient only is=20
>>>> authorized. Any liability arising from any party acting, or
> refraining
>>>> from acting, on any information contained in this e-mail is hereby=20
>>>> excluded. If you are not the intended recipient, please notify the=20
>>>> sender immediately, destroy the original transmission and its=20
>>>> attachments and do not disclose the contents to any other person,
> use
>>> it
>>>> for any purpose, or store or copy the information in any medium.
>>>> Copyright in this e-mail and any attachments belongs to
> Alcatel-Lucent
>>>> and/or its affiliated entities.
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>

From Leon.Portman@nice.com  Sun Mar  6 23:40:51 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EEA83A692A for <siprec@core3.amsl.com>; Sun,  6 Mar 2011 23:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gL4r8Kmen5wj for <siprec@core3.amsl.com>; Sun,  6 Mar 2011 23:40:49 -0800 (PST)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 56BB23A6920 for <siprec@ietf.org>; Sun,  6 Mar 2011 23:40:48 -0800 (PST)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Mon, 7 Mar 2011 09:41:59 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: Alissa Cooper <acooper@cdt.org>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Mon, 7 Mar 2011 09:41:58 +0200
Thread-Topic: [siprec] Requirements #66 (new): Clarification of REQ-018onindications to participants
Thread-Index: AcvbcOgWwJIVGoMnS1KN+Z39zqm1QwBKjePg
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A837A5A0@TLVMBX01.nice.com>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com><4D6EFFD0.7070109@cisco.com><07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com><CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C5086D@MCHP058A.global-ad.net> <CD2DE94B86B69443B53711F606FCAE120862E4B7@SARUMAN.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB97EC@xmb-sjc-234.amer.cisc	o.com> <A444A0F8084434499206E78C106220CA06C2C5096C@MCHP058A.global-ad.net> <8192308F-326D-4209-941D-C4F3BCA87E3F@cdt.org>
In-Reply-To: <8192308F-326D-4209-941D-C4F3BCA87E3F@cdt.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Requirements #66 (new): Clarification of	REQ-018onindications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 07 Mar 2011 07:40:51 -0000

+1


Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Alissa Cooper
Sent: Saturday, March 05, 2011 10:07 PM
To: Elwell, John
Cc: siprec@ietf.org
Subject: Re: [siprec] Requirements #66 (new): Clarification of REQ-018onind=
ications to participants

On Mar 4, 2011, at 7:39 AM, Elwell, John wrote:
> "REQ-x1 The mechanism MUST NOT prevent the application of tones or
> announcements during recording or at the start of a CS to support
> legal or policy requirements for notifying participants that the call
> is being recorded or may be recorded."

Why does this requirement only apply to cases where notification is provide=
d because of legal or policy requirements? What if the entity doing the rec=
ording just thinks that notification is a Good Thing to Do? My suggestion:

"REQ-x1 The mechanism MUST NOT prevent the application of tones or announce=
ments during recording or at the start of a CS to support notification to p=
articipants that the call is being recorded or may be recorded."

Alissa

>
> "REQ-x2 The mechanism MUST provide a means of indicating to
> recording-aware UAs whether recording is taking place, for appropriate
> rendering at the user interface.
>
> John
>
>
>> -----Original Message-----
>> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
>> Sent: 03 March 2011 20:05
>> To: Dave Smith; Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
>> REQ-018onindications to participants
>>
>> Just to clarify, is the decision therefore that Req. #18 will be
>> updated as proposed by John?
>>
>>>>>>>> I would suggest the following text:
>>>>>>>> "REQ-018 The mechanism MUST provide a means of
>>>> indicating to the
>>>>>>>> participants involved in a CS that their session is being
>>>>> recorded.
>>>>>>>> Although this can be accomplished using existing SIP
>>>>> techniques for
>>>>>>>> playing an in-band tone, announcement or other media to
>>>>>>>> participants, the mechanism is required also to provide an
>>>>>>>> indication to recording-aware UAs for appropriate
>>>>> rendering at the
>>>>>>>> user interface."
>>
>> If I am interpreting this correctly, playing of a tone or an
>> announcement is an option, not a required form of indication, and
>> some other indication may be communicated from the SRC to a recording
>> aware UA that results in the UA producing an indication of recording
>> that is possibly NOT audible, for example. The choice of the actual
>> rendering of this indication by the UA is left entirely to the UA. Is
>> that correct?
>>
>> Thanks,
>> Charles
>>
>>
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Dave Smith
>>> Sent: Thursday, March 03, 2011 9:38 AM
>>> To: Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
>>> Cc: siprec@ietf.org
>>> Subject: Re: [siprec] Requirements #66 (new): Clarification of
>> REQ-018onindications to participants
>>>
>>> Thanks for the detailed inputs/explanations.  I agree with the
>>> recommendations for using REQ-x1 and -x2.
>>>
>>> Regards,
>>> Dave
>>>
>>> -----Original Message-----
>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>>> Sent: Thursday, March 03, 2011 9:17 AM
>>> To: Leon Portman; Dave Smith; Paul Kyzivat
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>> of REQ-018
>>> onindications to participants
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>> Sent: 03 March 2011 15:24
>>>> To: Elwell, John; Dave Smith; Paul Kyzivat
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
>>>> REQ-018 on indications to participants
>>>>
>>>> I agree with your points. Just generic question, do we really need
>>>> a requirement for mechanism not to prevent something? It can be lot
>>>> of things like encryption, codec negotiation, ability to transfer
>>>> call etc.
>>> [JRE] It is certainly worth questioning whether we need
>> REQ-x1 below.
>> On
>>> the one hand, SIPREC is unlikely to specify anything that would
>> prevent
>>> this existing capability. In fact it would be quite hard
>> for SIPREC to
>>> specify something that would prevent the application of tones of
>>> announcement. Of course, there might be things that could be done at
>>> deployment time to prevent it (e.g., encryption), but that is not
>>> SIPREC's problem. However, I would still be inclined to keep it. In
>>> particular, the Privacy Considerations section has a statement:
>>> "Therefore this document contains requirements for being able to
>> notify
>>> users that a call is being recorded ...". I don't think REQ-x2 alone
>>> would be sufficient to satisfy that, so if we were to
>> remove REQ-x1 we
>>> would have to revisit the Privacy Considerations text, which I would
>> be
>>> very reluctant to do. So I would like to keep REQ-x1 or something
>>> similar.
>>>
>>> John (as individual)
>>>
>>>>
>>>> Leon
>>>>
>>>> -----Original Message-----
>>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>>>> Sent: Thursday, March 03, 2011 11:14 AM
>>>> To: Dave Smith; Leon Portman; Paul Kyzivat
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
>>>> REQ-018 on indications to participants
>>>>
>>>> Concerning #1, I agree we need to be able to accommodate the
>>>> different requirements of different regions, countries, business
>>>> sectors, etc.. Sometimes this might involve playing a tone (e.g., a
>>>> repeated beep) for the duration of recording, and sometimes this
>>>> might involve an announcement at the beginning of the session,
>>>> which will suffice whether or not recording actually takes place
>>>> during the session. Basically, since not all users will use
>>>> siprec-aware UAs, particularly PSTN users, the only solution is for
>>>> the SRC to arrange that the appropriate tone or announcement is
>>>> injected into the audio stream when required. If the SRC itself is
>>>> able to do this, we don't need a SIP solution. If the SRC uses a
>>>> media server to do this, existing SIP/SDP mechanisms will cater for
>>>> this. I don't anticipate siprec providing new mechanisms for this.
>>>> It is really just a case of not preventing the use of such
>>>> mechanisms. How about the following text?
>>>>
>>>> "REQ-x1 The mechanism MUST NOT prevent the application of tones or
>>>> announcements during recording or at the start of a CS to support
>>>> legal or policy requirements for notifying participants that the
>>>> call is being recorded or may be recorded."
>>>>
>>>> Concerning #2, I see this more of a courtesy thing, rather than a
>>>> legal thing. Most web-based conference applications give a visual
>>>> indication of whether the conference is being recorded, achieved
>>>> using web technology. Where this is not available, it would be
>>>> useful if siprec-aware UAs in the CS could be advised when
>>>> recording is taking place so that they can give an appropriate
>>>> indication to the user. I can see a number of reasons for this:
>>>> - It provides the possibility of alternative modes for
>>>> hearing-impaired users.
>>>> - It gives more precise information in cases where an SRC-injected
>>>> announcement is given only at the start of the call.
>>>> - It provides feedback to users who have requested that recording
>>>> be started / stopped / paused / resumed.
>>>> - It gives an explicit indication to users who might not understand
>>>> the meaning of an injected tone.
>>>> - It is independent of medium type (audio, video, real-time text,
>>>> fax...).
>>>> - Potentially its granularity could be on a per medium basis,
>>>> although I would prefer to leave that as an option for the
>>>> solution, rather than making a requirement.
>>>>
>>>> So how about the following text?
>>>>
>>>> "REQ-x2 The mechanism MUST provide a means of indicating to
>>>> recording-aware UAs whether recording is taking place, for
>>>> appropriate rendering at the user interface.
>>>>
>>>> John (as individual)
>>>>
>>>>>>>> participants involved in a CS that their session is being
>>>>> recorded.
>>>>>>>> Although this can be accomplished using existing SIP
>>>>> techniques for
>>>>>>>> playing an in-band tone, announcement or other media to
>>>>>>>> participants, the mechanism is required also to provide an
>>>>>>>> indication to recording-aware UAs for appropriate
>>>>> rendering at the
>>>>>>>> user interface."
>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org
>>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
>>>>> Sent: 03 March 2011 08:29
>>>>> To: Leon Portman; Paul Kyzivat
>>>>> Cc: siprec@ietf.org
>>>>> Subject: Re: [siprec] Requirements #66 (new): Clarification of
>>>>> REQ-018 on indications to participants
>>>>>
>>>>> I fully agree that an IVR solution (play an announcement) is an
>>>>> acceptable method that is used today to inform a caller.
>>>>> I was introducing this req't (#1 below) in order to improve
>>>> on that.
>>>>>
>>>>> Do we absolutely need #1 - probably not.  Do we
>> absolutely need #2
>> -
>>>>> probably not also.
>>>>>
>>>>> It seems that you are indicating that at least for #1 a solution
>> is
>>>>> difficult to provide and would restrict the SRC solution
>>>>> significantly, so we should not include it.
>>>>> I am wondering if that is also the case for #2.
>>>>>
>>>>> I don't think we need to mention any "optional" solutions in the
>>>>> req't.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Dave
>>>>>
>>>>> -----Original Message-----
>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>> Sent: Wednesday, March 02, 2011 11:32 PM
>>>>> To: Paul Kyzivat; Dave Smith
>>>>> Cc: siprec@ietf.org
>>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
>>>> of REQ-018
>>>>> on indications to participants
>>>>>
>>>>> I agree with Paul. In the environment where SRC cannot inject any
>>>>> audio into the CS, best practice is to have IVR or Voice Portal
>>>> to make such
>>>>> announcement.
>>>>>
>>>>> Leon
>>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org
>>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat
>>>>> Sent: Thursday, March 03, 2011 4:41 AM
>>>>> To: Dave Smith
>>>>> Cc: siprec@ietf.org
>>>>> Subject: Re: [siprec] Requirements #66 (new): Clarification
>>>> of REQ-018
>>>>> on indications to participants
>>>>>
>>>>>
>>>>>
>>>>> On 3/2/2011 7:50 PM, Dave Smith wrote:
>>>>>> I think the solution should be able to support these
>>>>> functionalities:
>>>>>>  1.  playing a repeatable tone to CS participants  2.  indicate
>>>>>> to recording-aware UAs that recording is
>> currently
>>>>>> occurring
>>>>>>
>>>>>> Although there may be other things that could be done, I
>>>>> believe that
>>>>>> these functionalities are reasonable and sufficient, and would
>> be
>>>>>> universally accepted, and that both are required in order
>>>>> to be able
>>>>>> to addresss most use cases for indicating to the
>>>>> participants involved
>>>>>
>>>>>> in a CS that their session is being recorded.
>>>>>
>>>>>> I am not sure of what the last paragraph of your response
>>>> is about
>>>>>> exactly.  A solution to this req't needs to be worked out
>>>>> in another
>>>>>> SIPREC Draft; my current thoughts are that since the SRC is
>>>>> handling
>>>>>> and in the path of CS UA media and is already communicating
>>>>> with these
>>>>>
>>>>>> UAs, probably an SRC-based solution could be more easily
>>>>> used to solve
>>>>>
>>>>>> this req't.
>>>>>
>>>>> I'll try to elaborate:
>>>>>
>>>>> I'm not informed of the specific legalities involved, but am of
>> the
>>>>> impression that they vary widely. There are certainly contexts in
>>>>> which no audible indication need be played. (E.g. call centers,
>>>> at least in
>>>>> some places.) In some cases this is dealt with by playing a
>> general
>>>>> disclaimer at the beginning of the call, and/or having a
>> contractual
>>>>> relationship by which this isn't required.
>>>>>
>>>>> In such environments the SRC may not need any way of
>> injecting an
>>>>> audible indication that recording is going on.
>>>>>
>>>>> And there are ways an SRC could get the media for recording
>>>> that don't
>>>>> provide a way to inject these tones. (E.g. a media *relay* may
>>>>> fork the media, but not be able to alter it.)
>>>>>
>>>>> If you combine these things, you can end up with mechanisms for
>>>>> implementing the SRC function that are *incapable* of
>>>> satisfying your
>>>>> proposed requirement, and yet are perfectly suitable for
>>>> the intended
>>>>> recording task. I don't want to rule those out as valid
>>>>> implementations of siprec.
>>>>>
>>>>> I'm fine with having the tone generation as an *option*,
>>>> and one that
>>>>> may be absolutely required in *some* markets. If you have a
>> business
>>>>> that requires this tone generation then you will buy a product
>> that
>>>>> supports it.
>>>>>
>>>>>    Thanks,
>>>>>    Paul
>>>>>
>>>>>> Regards,
>>>>>> Dave
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
>> On
>>>>>> Behalf Of Paul Kyzivat
>>>>>> Sent: Wednesday, March 02, 2011 1:43 PM
>>>>>> To: siprec@ietf.org
>>>>>> Subject: Re: [siprec] Requirements #66 (new): Clarification
>>>>> of REQ-018
>>>>>
>>>>>> on indications to participants
>>>>>>
>>>>>> Dave,
>>>>>>
>>>>>> I recognize that there are environments where this audible
>>>>> tone is a
>>>>>> requirement. And also environments where it is not, or that
>>>>> there is
>>>>>> some *other* requirement.
>>>>>>
>>>>>> My question is whether rendering such things is "part of the
>>>>>> mechanism",
>>>>>>
>>>>>> or simply something that some SRCs must be able to do.
>>>>>>
>>>>>> Making this part of the mechanism begs the question of "what
>>>>> mechanism".
>>>>>>
>>>>>> There are mechanisms for capturing the media for recording
>>>>> that do not
>>>>>
>>>>>> have a device in place that can insert something into
>> the media.
>>>>>> Making this a requirement on the mechanism would exclude
>>>>> using those
>>>>>> techniques.
>>>>>>
>>>>>>  Thanks,
>>>>>>  Paul
>>>>>>
>>>>>> On 3/2/2011 2:57 PM, Dave Smith wrote:
>>>>>>> I do have an input to this requirement.
>>>>>>>
>>>>>>> I agree that the system should be able to provide an
>>>> indication to
>>>>>>> recording-aware UAs that recording is currently
>> occurring (for
>>>>>>> appropriate rendering at the user interface).
>>>>>>> I also believe that the system should be able to provide a
>>>>> "tone" to
>>>>>> CS
>>>>>>> participants to indicate that recording is currently
>> occurring
>>>>>>> (specifically, a distinct "beep tone" signal that is repeated
>> at
>>>>>> regular
>>>>>>> intervals during the course of the telephone
>>>> conversation when the
>>>>>>> recording device is in use); note that this is
>> consistent with
>>>>>> existing
>>>>>>> methods from FCC Rules Regarding Telephone Company
>> Recording of
>>>>>>> Interstate or International Wireline Telephone Conversations.
>>>>>>> But I do not see a reason to mention
>> "announcements", or "other
>>>>> media"
>>>>>>> in this requirement.
>>>>>>>
>>>>>>> Therefore, I recommend the following wording for REQ-018:
>>>>>>>
>>>>>>> "REQ-018 The mechanism MUST provide a means of indicating to
>> the
>>>>>>> participants involved in a CS that their session is
>>>> being recorded.
>>>>>> To
>>>>>>> support this the mechanism MUST provide a means of playing a
>>>>>> repeatable
>>>>>>> tone to CS participants, and also the mechanism MUST
>>>>> provide a means
>>>>>> to
>>>>>>> indicate to recording-aware UAs that recording is
>>>>> currently occurring
>>>>>
>>>>>>> (for appropriate rendering at the user interface)."
>>>>>>>
>>>>>>> Regards,
>>>>>>> Dave
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: siprec-bounces@ietf.org
>> [mailto:siprec-bounces@ietf.org]
>> On
>>>>>> Behalf
>>>>>>> Of Elwell, John
>>>>>>> Sent: Wednesday, March 02, 2011 3:41 AM
>>>>>>> To: Leon Portman; siprec issue tracker
>>>>>>> Cc: siprec@ietf.org
>>>>>>> Subject: Re: [siprec] Requirements #66 (new):
>> Clarification of
>>>>>>> REQ-018 on indications to participants
>>>>>>>
>>>>>>> In the interests of getting the requirements document
>>>> finished, I
>>>>>>> will set a short deadline for this remaining issue. If I
>>>> have not
>>>>>>> heard any objections to the proposal below by 2011-03-07 I
>>>>> will ask
>>>>>>> the editor
>>>>>> to
>>>>>>> adopt this new text and publish -07.
>>>>>>>
>>>>>>> John (as chair)
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>>>>> Sent: 28 February 2011 16:17
>>>>>>>> To: Elwell, John; siprec issue tracker
>>>>>>>> Cc: siprec@ietf.org
>>>>>>>> Subject: RE: [siprec] Requirements #66 (new):
>> Clarification of
>>>>>>>> REQ-018 on indications to participants
>>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> Leon
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Elwell, John
>> [mailto:john.elwell@siemens-enterprise.com]
>>>>>>>> Sent: Monday, February 28, 2011 5:35 PM
>>>>>>>> To: Leon Portman; siprec issue tracker
>>>>>>>> Cc: siprec@ietf.org
>>>>>>>> Subject: RE: [siprec] Requirements #66 (new):
>> Clarification of
>>>>>>>> REQ-018 on indications to participants
>>>>>>>>
>>>>>>>> There has been little discussion on this, apart from
>>>> support from
>>>>>>>> Leon. The existing text says:
>>>>>>>> "REQ-018 The mechanism MUST provide a means of indicating to
>> the
>>>>>>>>     participants involved in a CS that their
>> session is being
>>>>>> recorded.
>>>>>>>>
>>>>>>>>     Examples include: inject tones into the CS from the
>>>>> SRC, play a
>>>>>>>>     message at the beginning of a session, a visual
>>>>> indicator on a
>>>>>>>>     display, etc."
>>>>>>>>
>>>>>>>> I would suggest the following text:
>>>>>>>> "REQ-018 The mechanism MUST provide a means of
>>>> indicating to the
>>>>>>>> participants involved in a CS that their session is being
>>>>> recorded.
>>>>>>>> Although this can be accomplished using existing SIP
>>>>> techniques for
>>>>>>>> playing an in-band tone, announcement or other media to
>>>>>>>> participants, the mechanism is required also to provide an
>>>>>>>> indication to recording-aware UAs for appropriate
>>>>> rendering at the
>>>>>>>> user interface."
>>>>>>>>
>>>>>>>> John (as individual)
>>>>>
>>>>
>>>
>>>
>>>
>> --------------------------------------------------------------
>> ----------
>> ------------------------------
>>> -------------
>>> CONFIDENTIALITY NOTICE: This e-mail and any files attached
>> may contain
>> confidential and proprietary
>>> information of Alcatel-Lucent and/or its affiliated entities. Access
>> by the intended recipient only is
>>> authorized. Any liability arising from any party acting, or
>> refraining
>> from acting, on any information
>>> contained in this e-mail is hereby excluded. If you are not the
>> intended recipient, please notify the
>>> sender immediately, destroy the original transmission and its
>> attachments and do not disclose the
>>> contents to any other person, use it for any purpose, or
>> store or copy
>> the information in any medium.
>>> Copyright in this e-mail and any attachments belongs to
>> Alcatel-Lucent
>> and/or its affiliated entities.
>>>
>>> _______________________________________________
>>> 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

From rmohanr@cisco.com  Mon Mar  7 02:53:40 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C3D93A6944 for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 02:53:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t3bOA9CCNf0B for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 02:53:39 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 1D3A33A67AE for <siprec@ietf.org>; Mon,  7 Mar 2011 02:53:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=2378; q=dns/txt; s=iport; t=1299495292; x=1300704892; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to:cc; bh=EzswjsLkxO04ioc+7mhBysM/kXPqQCEzEHF88YDTLcQ=; b=b9zXKjBD6w+ByAck/NMKGbVLa+hrPWg9X9gOdOUJgc3R4eN1LLfgrXfP MVbd69410U903G+ceS1PF83chzr2pUncO8Mw03399ONZaYSuksR1T7hzq zt9gk28Hsg5O8688Jaq/JDxuBhfXJgsjTwba9tSKtpJVtLaW28rZNC+xV M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlsBABdIdE1AaMHG/2dsb2JhbACEKJNkP40cYXSiL4sMkCOBJ4FXgW52BIUail8
X-IronPort-AV: E=Sophos;i="4.62,276,1297036800"; d="scan'208";a="271372296"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-4.cisco.com with ESMTP; 07 Mar 2011 10:54:48 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p27AsEnx008695 for <siprec@ietf.org>; Mon, 7 Mar 2011 10:54:46 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 7 Mar 2011 16:24:45 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Mon, 7 Mar 2011 16:24:42 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD0595D337@XMB-BGL-417.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Version Notification for draft-ram-siprec-metadata-04 
Thread-Index: AcvctXp6kNwelg6+TGS/IEMp40tvTQAAAwQA
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: <siprec@ietf.org>
X-OriginalArrivalTime: 07 Mar 2011 10:54:45.0333 (UTC) FILETIME=[11F09850:01CBDCB6]
Subject: [siprec] FW: New Version Notification for draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 07 Mar 2011 10:53:40 -0000

SGkgYWxsLA0KDQpXZSBoYXZlIHN1Ym1pdHRlZCB0aGUgdmVyc2lvbiAwNCBvZiAiU0lQIHJlY29y
ZGluZyBtZXRhZGF0YSBtb2RlbCIuIA0KDQpTdW1tYXJ5IG9mIGNoYW5nZXMgbWFkZSBpbiB0aGlz
IHZlcnNpb24gaW5jbHVkZXM6DQoNCkFkZGVkIGEgY291cGxlIG9mIHVzZSBjYXNlcyAoaW5zdGFu
Y2UgZGlhZ3JhbXMpIGZvciBjb25mZXJlbmNlIGNhc2VzLg0KQWRkcmVzc2VkIHRoZSBjb21tZW50
cyByZWNlaXZlZCBvbiB0aGUgcHJldmlvdXMgdmVyc2lvbiBbMDNdDQpBZGRlZCBDUyBJZGVudGlm
aWVyIGF0dHJpYnV0ZSB0byBDUyBibG9jay4gVGhpcyBhdHRyaWJ1dGUgaXMgbmVlZGVkIHRvIHVu
aXF1ZWx5IGlkZW50aWZ5IGEgQ1MuDQpDbG9zZWQgYWxsIHRoZSBvcGVuIGl0ZW1zLg0KDQpQbGVh
c2UgcmV2aWV3IHRoZSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQgYW5kIHByb3ZpZGUgeW91ciBj
b21tZW50czoNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXJhbS1zaXBy
ZWMtbWV0YWRhdGEvDQoNClJlZ2FyZHMsDQpSYW0NCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KRnJvbTogSUVURiBJLUQgU3VibWlzc2lvbiBUb29sIFttYWlsdG86aWRzdWJtaXNzaW9u
QGlldGYub3JnXSANClNlbnQ6IE1vbmRheSwgTWFyY2ggMDcsIDIwMTEgNDoxOSBQTQ0KVG86IFJh
bSBNb2hhbiBSIChybW9oYW5yKQ0KQ2M6IFBhcnRoYXNhcmF0aGkgUiAocGFydHIpOyBQYXVsIEt5
eml2YXQgKHBreXppdmF0KQ0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBk
cmFmdC1yYW0tc2lwcmVjLW1ldGFkYXRhLTA0IA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBk
cmFmdC1yYW0tc2lwcmVjLW1ldGFkYXRhLTA0LnR4dCBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3Vi
bWl0dGVkIGJ5IFJhbSBSIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KRmls
ZW5hbWU6CSBkcmFmdC1yYW0tc2lwcmVjLW1ldGFkYXRhDQpSZXZpc2lvbjoJIDA0DQpUaXRsZToJ
CSBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9jb2wgKFNJUCkgUmVjb3JkaW5nIE1ldGFkYXRhDQpD
cmVhdGlvbl9kYXRlOgkgMjAxMS0wMy0wNw0KV0cgSUQ6CQkgSW5kZXBlbmRlbnQgU3VibWlzc2lv
bg0KTnVtYmVyX29mX3BhZ2VzOiAyMw0KDQpBYnN0cmFjdDoNClNlc3Npb24gcmVjb3JkaW5nIGlz
IGEgY3JpdGljYWwgcmVxdWlyZW1lbnQgaW4gbWFueSBjb21tdW5pY2F0aW9ucw0KZW52aXJvbm1l
bnRzIHN1Y2ggYXMgY2FsbCBjZW50ZXJzIGFuZCBmaW5hbmNpYWwgdHJhZGluZy4gIEluIHNvbWUg
b2YNCnRoZXNlIGVudmlyb25tZW50cywgYWxsIGNhbGxzIG11c3QgYmUgcmVjb3JkZWQgZm9yIHJl
Z3VsYXRvcnksDQpjb21wbGlhbmNlLCBhbmQgY29uc3VtZXIgcHJvdGVjdGlvbiByZWFzb25zLiAg
UmVjb3JkaW5nIG9mIGEgc2Vzc2lvbg0KaXMgdHlwaWNhbGx5IHBlcmZvcm1lZCBieSBzZW5kaW5n
IGEgY29weSBvZiBhIG1lZGlhIHN0cmVhbSB0byBhDQpyZWNvcmRpbmcgZGV2aWNlLiAgVGhpcyBk
b2N1bWVudCBkZXNjcmliZXMgdGhlIG1ldGFkYXRhIG1vZGVsIGFzDQp2aWV3ZWQgYnkgU2Vzc2lv
biBSZWNvcmRpbmcgU2VydmVyKFNSUykuDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0K
VGhlIElFVEYgU2VjcmV0YXJpYXQuDQoNCg0K

From andrew.hutton@siemens-enterprise.com  Mon Mar  7 03:42:38 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B540B3A63CB for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 03:42:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6IP0CYeruQxU for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 03:42:36 -0800 (PST)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id B9D883A6924 for <siprec@ietf.org>; Mon,  7 Mar 2011 03:42:35 -0800 (PST)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3652383; Mon, 7 Mar 2011 12:43:48 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 0A91D23F0278; Mon,  7 Mar 2011 12:43:48 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 7 Mar 2011 12:43:48 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, Alissa Cooper <acooper@cdt.org>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Mon, 7 Mar 2011 12:43:46 +0100
Thread-Topic: [siprec] Requirements #66 (new): Clarification	of REQ-018onindications to participants
Thread-Index: AcvbcOgWwJIVGoMnS1KN+Z39zqm1QwBKjePgAAhanUA=
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B61A8FEC0@MCHP058A.global-ad.net>
References: <075.d9e0afcd7cf3ee35c38905ea3efdd6c9@tools.ietf.org><07465C1D981ABC41A344374066AE1A2C38A78FCD61@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2BAA7CA@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A81E5A0B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C501A0@MCHP058A.global-ad.net><CD2DE94B86B69443B53711F606FCAE120862E12B@SARUMAN.us.int.genesyslab.com><4D6EB9C6.6080505@cisco.com><CD2DE94B86B69443B53711F606FCAE120862E2FE@SARUMAN.us.int.genesyslab.com><4D6EFFD0.7070109@cisco.com><07465C1D981ABC41A344374066AE1A2C38A8379C48@TLVMBX01.nice.com><CD2DE94B86B69443B53711F606FCAE120862E376@SARUMAN.us.int.genesyslab.com><A444A0F8084434499206E78C106220CA06C2C5056B@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A8379EE0@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA06C2C5086D@MCHP058A.global-ad.net> <CD2DE94B86B69443B53711F606FCAE120862E4B7@SARUMAN.us.int.genesyslab.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03AB97EC@xmb-sjc-234.amer.cisc	o.com> <A444A0F8084434499206E78C106220CA06C2C5096C@MCHP058A.global-ad.net> <8192308F-326D-4209-941D-C4F3BCA87E3F@cdt.org> <07465C1D981ABC41A344374066AE1A2C38A837A5A0@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A837A5A0@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Requirements #66 (new): Clarification	of	REQ-018onindications to participants
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 07 Mar 2011 11:42:38 -0000

+1.

I am happy with Alissa's proposal for REQ-x1 and also with the previously p=
roposed REQ-x2.

Regards
Andy


> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Leon Portman
> Sent: 07 March 2011 07:42
> To: Alissa Cooper; Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification
> of REQ-018onindications to participants
>
> +1
>
>
> Leon
>
> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Alissa Cooper
> Sent: Saturday, March 05, 2011 10:07 PM
> To: Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Requirements #66 (new): Clarification
> of REQ-018onindications to participants
>
> On Mar 4, 2011, at 7:39 AM, Elwell, John wrote:
> > "REQ-x1 The mechanism MUST NOT prevent the application of tones or
> > announcements during recording or at the start of a CS to support
> > legal or policy requirements for notifying participants
> that the call
> > is being recorded or may be recorded."
>
> Why does this requirement only apply to cases where
> notification is provided because of legal or policy
> requirements? What if the entity doing the recording just
> thinks that notification is a Good Thing to Do? My suggestion:
>
> "REQ-x1 The mechanism MUST NOT prevent the application of
> tones or announcements during recording or at the start of a
> CS to support notification to participants that the call is
> being recorded or may be recorded."
>
> Alissa
>
> >
> > "REQ-x2 The mechanism MUST provide a means of indicating to
> > recording-aware UAs whether recording is taking place, for
> appropriate
> > rendering at the user interface.
> >
> > John
> >
> >
> >> -----Original Message-----
> >> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> >> Sent: 03 March 2011 20:05
> >> To: Dave Smith; Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
> >> Cc: siprec@ietf.org
> >> Subject: RE: [siprec] Requirements #66 (new): Clarification of
> >> REQ-018onindications to participants
> >>
> >> Just to clarify, is the decision therefore that Req. #18 will be
> >> updated as proposed by John?
> >>
> >>>>>>>> I would suggest the following text:
> >>>>>>>> "REQ-018 The mechanism MUST provide a means of
> >>>> indicating to the
> >>>>>>>> participants involved in a CS that their session is being
> >>>>> recorded.
> >>>>>>>> Although this can be accomplished using existing SIP
> >>>>> techniques for
> >>>>>>>> playing an in-band tone, announcement or other media to
> >>>>>>>> participants, the mechanism is required also to provide an
> >>>>>>>> indication to recording-aware UAs for appropriate
> >>>>> rendering at the
> >>>>>>>> user interface."
> >>
> >> If I am interpreting this correctly, playing of a tone or an
> >> announcement is an option, not a required form of indication, and
> >> some other indication may be communicated from the SRC to
> a recording
> >> aware UA that results in the UA producing an indication of
> recording
> >> that is possibly NOT audible, for example. The choice of the actual
> >> rendering of this indication by the UA is left entirely to
> the UA. Is
> >> that correct?
> >>
> >> Thanks,
> >> Charles
> >>
> >>
> >>> -----Original Message-----
> >>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> >> Behalf Of Dave Smith
> >>> Sent: Thursday, March 03, 2011 9:38 AM
> >>> To: Elwell, John; Leon Portman; Paul Kyzivat (pkyzivat)
> >>> Cc: siprec@ietf.org
> >>> Subject: Re: [siprec] Requirements #66 (new): Clarification of
> >> REQ-018onindications to participants
> >>>
> >>> Thanks for the detailed inputs/explanations.  I agree with the
> >>> recommendations for using REQ-x1 and -x2.
> >>>
> >>> Regards,
> >>> Dave
> >>>
> >>> -----Original Message-----
> >>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> >>> Sent: Thursday, March 03, 2011 9:17 AM
> >>> To: Leon Portman; Dave Smith; Paul Kyzivat
> >>> Cc: siprec@ietf.org
> >>> Subject: RE: [siprec] Requirements #66 (new): Clarification
> >> of REQ-018
> >>> onindications to participants
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> >>>> Sent: 03 March 2011 15:24
> >>>> To: Elwell, John; Dave Smith; Paul Kyzivat
> >>>> Cc: siprec@ietf.org
> >>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
> >>>> REQ-018 on indications to participants
> >>>>
> >>>> I agree with your points. Just generic question, do we
> really need
> >>>> a requirement for mechanism not to prevent something? It
> can be lot
> >>>> of things like encryption, codec negotiation, ability to transfer
> >>>> call etc.
> >>> [JRE] It is certainly worth questioning whether we need
> >> REQ-x1 below.
> >> On
> >>> the one hand, SIPREC is unlikely to specify anything that would
> >> prevent
> >>> this existing capability. In fact it would be quite hard
> >> for SIPREC to
> >>> specify something that would prevent the application of tones of
> >>> announcement. Of course, there might be things that could
> be done at
> >>> deployment time to prevent it (e.g., encryption), but that is not
> >>> SIPREC's problem. However, I would still be inclined to
> keep it. In
> >>> particular, the Privacy Considerations section has a statement:
> >>> "Therefore this document contains requirements for being able to
> >> notify
> >>> users that a call is being recorded ...". I don't think
> REQ-x2 alone
> >>> would be sufficient to satisfy that, so if we were to
> >> remove REQ-x1 we
> >>> would have to revisit the Privacy Considerations text,
> which I would
> >> be
> >>> very reluctant to do. So I would like to keep REQ-x1 or something
> >>> similar.
> >>>
> >>> John (as individual)
> >>>
> >>>>
> >>>> Leon
> >>>>
> >>>> -----Original Message-----
> >>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> >>>> Sent: Thursday, March 03, 2011 11:14 AM
> >>>> To: Dave Smith; Leon Portman; Paul Kyzivat
> >>>> Cc: siprec@ietf.org
> >>>> Subject: RE: [siprec] Requirements #66 (new): Clarification of
> >>>> REQ-018 on indications to participants
> >>>>
> >>>> Concerning #1, I agree we need to be able to accommodate the
> >>>> different requirements of different regions, countries, business
> >>>> sectors, etc.. Sometimes this might involve playing a
> tone (e.g., a
> >>>> repeated beep) for the duration of recording, and sometimes this
> >>>> might involve an announcement at the beginning of the session,
> >>>> which will suffice whether or not recording actually takes place
> >>>> during the session. Basically, since not all users will use
> >>>> siprec-aware UAs, particularly PSTN users, the only
> solution is for
> >>>> the SRC to arrange that the appropriate tone or announcement is
> >>>> injected into the audio stream when required. If the SRC
> itself is
> >>>> able to do this, we don't need a SIP solution. If the SRC uses a
> >>>> media server to do this, existing SIP/SDP mechanisms
> will cater for
> >>>> this. I don't anticipate siprec providing new mechanisms
> for this.
> >>>> It is really just a case of not preventing the use of such
> >>>> mechanisms. How about the following text?
> >>>>
> >>>> "REQ-x1 The mechanism MUST NOT prevent the application
> of tones or
> >>>> announcements during recording or at the start of a CS to support
> >>>> legal or policy requirements for notifying participants that the
> >>>> call is being recorded or may be recorded."
> >>>>
> >>>> Concerning #2, I see this more of a courtesy thing, rather than a
> >>>> legal thing. Most web-based conference applications give a visual
> >>>> indication of whether the conference is being recorded, achieved
> >>>> using web technology. Where this is not available, it would be
> >>>> useful if siprec-aware UAs in the CS could be advised when
> >>>> recording is taking place so that they can give an appropriate
> >>>> indication to the user. I can see a number of reasons for this:
> >>>> - It provides the possibility of alternative modes for
> >>>> hearing-impaired users.
> >>>> - It gives more precise information in cases where an
> SRC-injected
> >>>> announcement is given only at the start of the call.
> >>>> - It provides feedback to users who have requested that recording
> >>>> be started / stopped / paused / resumed.
> >>>> - It gives an explicit indication to users who might not
> understand
> >>>> the meaning of an injected tone.
> >>>> - It is independent of medium type (audio, video, real-time text,
> >>>> fax...).
> >>>> - Potentially its granularity could be on a per medium basis,
> >>>> although I would prefer to leave that as an option for the
> >>>> solution, rather than making a requirement.
> >>>>
> >>>> So how about the following text?
> >>>>
> >>>> "REQ-x2 The mechanism MUST provide a means of indicating to
> >>>> recording-aware UAs whether recording is taking place, for
> >>>> appropriate rendering at the user interface.
> >>>>
> >>>> John (as individual)
> >>>>
> >>>>>>>> participants involved in a CS that their session is being
> >>>>> recorded.
> >>>>>>>> Although this can be accomplished using existing SIP
> >>>>> techniques for
> >>>>>>>> playing an in-band tone, announcement or other media to
> >>>>>>>> participants, the mechanism is required also to provide an
> >>>>>>>> indication to recording-aware UAs for appropriate
> >>>>> rendering at the
> >>>>>>>> user interface."
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: siprec-bounces@ietf.org
> >>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of Dave Smith
> >>>>> Sent: 03 March 2011 08:29
> >>>>> To: Leon Portman; Paul Kyzivat
> >>>>> Cc: siprec@ietf.org
> >>>>> Subject: Re: [siprec] Requirements #66 (new): Clarification of
> >>>>> REQ-018 on indications to participants
> >>>>>
> >>>>> I fully agree that an IVR solution (play an announcement) is an
> >>>>> acceptable method that is used today to inform a caller.
> >>>>> I was introducing this req't (#1 below) in order to improve
> >>>> on that.
> >>>>>
> >>>>> Do we absolutely need #1 - probably not.  Do we
> >> absolutely need #2
> >> -
> >>>>> probably not also.
> >>>>>
> >>>>> It seems that you are indicating that at least for #1 a solution
> >> is
> >>>>> difficult to provide and would restrict the SRC solution
> >>>>> significantly, so we should not include it.
> >>>>> I am wondering if that is also the case for #2.
> >>>>>
> >>>>> I don't think we need to mention any "optional" solutions in the
> >>>>> req't.
> >>>>>
> >>>>>
> >>>>> Regards,
> >>>>> Dave
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> >>>>> Sent: Wednesday, March 02, 2011 11:32 PM
> >>>>> To: Paul Kyzivat; Dave Smith
> >>>>> Cc: siprec@ietf.org
> >>>>> Subject: RE: [siprec] Requirements #66 (new): Clarification
> >>>> of REQ-018
> >>>>> on indications to participants
> >>>>>
> >>>>> I agree with Paul. In the environment where SRC cannot
> inject any
> >>>>> audio into the CS, best practice is to have IVR or Voice Portal
> >>>> to make such
> >>>>> announcement.
> >>>>>
> >>>>> Leon
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: siprec-bounces@ietf.org
> >>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat
> >>>>> Sent: Thursday, March 03, 2011 4:41 AM
> >>>>> To: Dave Smith
> >>>>> Cc: siprec@ietf.org
> >>>>> Subject: Re: [siprec] Requirements #66 (new): Clarification
> >>>> of REQ-018
> >>>>> on indications to participants
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 3/2/2011 7:50 PM, Dave Smith wrote:
> >>>>>> I think the solution should be able to support these
> >>>>> functionalities:
> >>>>>>  1.  playing a repeatable tone to CS participants  2.  indicate
> >>>>>> to recording-aware UAs that recording is
> >> currently
> >>>>>> occurring
> >>>>>>
> >>>>>> Although there may be other things that could be done, I
> >>>>> believe that
> >>>>>> these functionalities are reasonable and sufficient, and would
> >> be
> >>>>>> universally accepted, and that both are required in order
> >>>>> to be able
> >>>>>> to addresss most use cases for indicating to the
> >>>>> participants involved
> >>>>>
> >>>>>> in a CS that their session is being recorded.
> >>>>>
> >>>>>> I am not sure of what the last paragraph of your response
> >>>> is about
> >>>>>> exactly.  A solution to this req't needs to be worked out
> >>>>> in another
> >>>>>> SIPREC Draft; my current thoughts are that since the SRC is
> >>>>> handling
> >>>>>> and in the path of CS UA media and is already communicating
> >>>>> with these
> >>>>>
> >>>>>> UAs, probably an SRC-based solution could be more easily
> >>>>> used to solve
> >>>>>
> >>>>>> this req't.
> >>>>>
> >>>>> I'll try to elaborate:
> >>>>>
> >>>>> I'm not informed of the specific legalities involved, but am of
> >> the
> >>>>> impression that they vary widely. There are certainly
> contexts in
> >>>>> which no audible indication need be played. (E.g. call centers,
> >>>> at least in
> >>>>> some places.) In some cases this is dealt with by playing a
> >> general
> >>>>> disclaimer at the beginning of the call, and/or having a
> >> contractual
> >>>>> relationship by which this isn't required.
> >>>>>
> >>>>> In such environments the SRC may not need any way of
> >> injecting an
> >>>>> audible indication that recording is going on.
> >>>>>
> >>>>> And there are ways an SRC could get the media for recording
> >>>> that don't
> >>>>> provide a way to inject these tones. (E.g. a media *relay* may
> >>>>> fork the media, but not be able to alter it.)
> >>>>>
> >>>>> If you combine these things, you can end up with mechanisms for
> >>>>> implementing the SRC function that are *incapable* of
> >>>> satisfying your
> >>>>> proposed requirement, and yet are perfectly suitable for
> >>>> the intended
> >>>>> recording task. I don't want to rule those out as valid
> >>>>> implementations of siprec.
> >>>>>
> >>>>> I'm fine with having the tone generation as an *option*,
> >>>> and one that
> >>>>> may be absolutely required in *some* markets. If you have a
> >> business
> >>>>> that requires this tone generation then you will buy a product
> >> that
> >>>>> supports it.
> >>>>>
> >>>>>    Thanks,
> >>>>>    Paul
> >>>>>
> >>>>>> Regards,
> >>>>>> Dave
> >>>>>>
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> >> On
> >>>>>> Behalf Of Paul Kyzivat
> >>>>>> Sent: Wednesday, March 02, 2011 1:43 PM
> >>>>>> To: siprec@ietf.org
> >>>>>> Subject: Re: [siprec] Requirements #66 (new): Clarification
> >>>>> of REQ-018
> >>>>>
> >>>>>> on indications to participants
> >>>>>>
> >>>>>> Dave,
> >>>>>>
> >>>>>> I recognize that there are environments where this audible
> >>>>> tone is a
> >>>>>> requirement. And also environments where it is not, or that
> >>>>> there is
> >>>>>> some *other* requirement.
> >>>>>>
> >>>>>> My question is whether rendering such things is "part of the
> >>>>>> mechanism",
> >>>>>>
> >>>>>> or simply something that some SRCs must be able to do.
> >>>>>>
> >>>>>> Making this part of the mechanism begs the question of "what
> >>>>> mechanism".
> >>>>>>
> >>>>>> There are mechanisms for capturing the media for recording
> >>>>> that do not
> >>>>>
> >>>>>> have a device in place that can insert something into
> >> the media.
> >>>>>> Making this a requirement on the mechanism would exclude
> >>>>> using those
> >>>>>> techniques.
> >>>>>>
> >>>>>>  Thanks,
> >>>>>>  Paul
> >>>>>>
> >>>>>> On 3/2/2011 2:57 PM, Dave Smith wrote:
> >>>>>>> I do have an input to this requirement.
> >>>>>>>
> >>>>>>> I agree that the system should be able to provide an
> >>>> indication to
> >>>>>>> recording-aware UAs that recording is currently
> >> occurring (for
> >>>>>>> appropriate rendering at the user interface).
> >>>>>>> I also believe that the system should be able to provide a
> >>>>> "tone" to
> >>>>>> CS
> >>>>>>> participants to indicate that recording is currently
> >> occurring
> >>>>>>> (specifically, a distinct "beep tone" signal that is repeated
> >> at
> >>>>>> regular
> >>>>>>> intervals during the course of the telephone
> >>>> conversation when the
> >>>>>>> recording device is in use); note that this is
> >> consistent with
> >>>>>> existing
> >>>>>>> methods from FCC Rules Regarding Telephone Company
> >> Recording of
> >>>>>>> Interstate or International Wireline Telephone Conversations.
> >>>>>>> But I do not see a reason to mention
> >> "announcements", or "other
> >>>>> media"
> >>>>>>> in this requirement.
> >>>>>>>
> >>>>>>> Therefore, I recommend the following wording for REQ-018:
> >>>>>>>
> >>>>>>> "REQ-018 The mechanism MUST provide a means of indicating to
> >> the
> >>>>>>> participants involved in a CS that their session is
> >>>> being recorded.
> >>>>>> To
> >>>>>>> support this the mechanism MUST provide a means of playing a
> >>>>>> repeatable
> >>>>>>> tone to CS participants, and also the mechanism MUST
> >>>>> provide a means
> >>>>>> to
> >>>>>>> indicate to recording-aware UAs that recording is
> >>>>> currently occurring
> >>>>>
> >>>>>>> (for appropriate rendering at the user interface)."
> >>>>>>>
> >>>>>>> Regards,
> >>>>>>> Dave
> >>>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: siprec-bounces@ietf.org
> >> [mailto:siprec-bounces@ietf.org]
> >> On
> >>>>>> Behalf
> >>>>>>> Of Elwell, John
> >>>>>>> Sent: Wednesday, March 02, 2011 3:41 AM
> >>>>>>> To: Leon Portman; siprec issue tracker
> >>>>>>> Cc: siprec@ietf.org
> >>>>>>> Subject: Re: [siprec] Requirements #66 (new):
> >> Clarification of
> >>>>>>> REQ-018 on indications to participants
> >>>>>>>
> >>>>>>> In the interests of getting the requirements document
> >>>> finished, I
> >>>>>>> will set a short deadline for this remaining issue. If I
> >>>> have not
> >>>>>>> heard any objections to the proposal below by 2011-03-07 I
> >>>>> will ask
> >>>>>>> the editor
> >>>>>> to
> >>>>>>> adopt this new text and publish -07.
> >>>>>>>
> >>>>>>> John (as chair)
> >>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
> >>>>>>>> Sent: 28 February 2011 16:17
> >>>>>>>> To: Elwell, John; siprec issue tracker
> >>>>>>>> Cc: siprec@ietf.org
> >>>>>>>> Subject: RE: [siprec] Requirements #66 (new):
> >> Clarification of
> >>>>>>>> REQ-018 on indications to participants
> >>>>>>>>
> >>>>>>>> +1
> >>>>>>>>
> >>>>>>>> Leon
> >>>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: Elwell, John
> >> [mailto:john.elwell@siemens-enterprise.com]
> >>>>>>>> Sent: Monday, February 28, 2011 5:35 PM
> >>>>>>>> To: Leon Portman; siprec issue tracker
> >>>>>>>> Cc: siprec@ietf.org
> >>>>>>>> Subject: RE: [siprec] Requirements #66 (new):
> >> Clarification of
> >>>>>>>> REQ-018 on indications to participants
> >>>>>>>>
> >>>>>>>> There has been little discussion on this, apart from
> >>>> support from
> >>>>>>>> Leon. The existing text says:
> >>>>>>>> "REQ-018 The mechanism MUST provide a means of indicating to
> >> the
> >>>>>>>>     participants involved in a CS that their
> >> session is being
> >>>>>> recorded.
> >>>>>>>>
> >>>>>>>>     Examples include: inject tones into the CS from the
> >>>>> SRC, play a
> >>>>>>>>     message at the beginning of a session, a visual
> >>>>> indicator on a
> >>>>>>>>     display, etc."
> >>>>>>>>
> >>>>>>>> I would suggest the following text:
> >>>>>>>> "REQ-018 The mechanism MUST provide a means of
> >>>> indicating to the
> >>>>>>>> participants involved in a CS that their session is being
> >>>>> recorded.
> >>>>>>>> Although this can be accomplished using existing SIP
> >>>>> techniques for
> >>>>>>>> playing an in-band tone, announcement or other media to
> >>>>>>>> participants, the mechanism is required also to provide an
> >>>>>>>> indication to recording-aware UAs for appropriate
> >>>>> rendering at the
> >>>>>>>> user interface."
> >>>>>>>>
> >>>>>>>> John (as individual)
> >>>>>
> >>>>
> >>>
> >>>
> >>>
> >> --------------------------------------------------------------
> >> ----------
> >> ------------------------------
> >>> -------------
> >>> CONFIDENTIALITY NOTICE: This e-mail and any files attached
> >> may contain
> >> confidential and proprietary
> >>> information of Alcatel-Lucent and/or its affiliated
> entities. Access
> >> by the intended recipient only is
> >>> authorized. Any liability arising from any party acting, or
> >> refraining
> >> from acting, on any information
> >>> contained in this e-mail is hereby excluded. If you are not the
> >> intended recipient, please notify the
> >>> sender immediately, destroy the original transmission and its
> >> attachments and do not disclose the
> >>> contents to any other person, use it for any purpose, or
> >> store or copy
> >> the information in any medium.
> >>> Copyright in this e-mail and any attachments belongs to
> >> Alcatel-Lucent
> >> and/or its affiliated entities.
> >>>
> >>> _______________________________________________
> >>> 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 mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>

From john.elwell@siemens-enterprise.com  Mon Mar  7 07:03:01 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 878643A69B7 for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 07:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.617
X-Spam-Level: 
X-Spam-Status: No, score=-102.617 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Upykr8XyLCij for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 07:03:00 -0800 (PST)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 6082D3A69B3 for <siprec@ietf.org>; Mon,  7 Mar 2011 07:03:00 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3654057 for siprec@ietf.org; Mon, 7 Mar 2011 16:04:12 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id E69F81EB82AB for <siprec@ietf.org>; Mon,  7 Mar 2011 16:04:12 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 7 Mar 2011 16:04:12 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 7 Mar 2011 16:04:11 +0100
Thread-Topic: Adopt metadata model as WG item? (was RE: I-D Action:draft-ram-siprec-metadata-04.txt)
Thread-Index: Acvct15QEc+wcp2iQZWED2n/Bc8wrwAH9/HQ
Message-ID: <A444A0F8084434499206E78C106220CA086A647BFE@MCHP058A.global-ad.net>
References: <20110307110004.10841.52270.idtracker@localhost>
Keywords: SIPREC
In-Reply-To: <20110307110004.10841.52270.idtracker@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] Adopt metadata model as WG item? (was RE: I-D Action:draft-ram-siprec-metadata-04.txt)
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 07 Mar 2011 15:03:01 -0000

Ram has posted this new version of the metadata model. He and his co-author=
s feel it is ready for consideration for adoption as a basis for our milest=
one "Submit metadata model to IESG as Informational RFC". The draft has bee=
n discussed during recent interim conference calls, as well as in Beijing, =
and the authors have endeavoured to take feedback into account. Adoption by=
 the WG would bring the document under WG control. Minor concerns with the =
document can be dealt with during that phase. The important thing is that p=
eople are comfortable with the general approach before taking this step.

Therefore, if anyone has any objection to adopting -04 as a basis for this =
milestone, please make your views known by 2011-03-14.

John (as chair)

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org=20
> [mailto:i-d-announce-bounces@ietf.org] On Behalf Of=20
> Internet-Drafts@ietf.org
> Sent: 07 March 2011 11:00
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-ram-siprec-metadata-04.txt
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
>=20
> 	Title           : Session Initiation Protocol (SIP)=20
> Recording Metadata
> 	Author(s)       : R. R, et al.
> 	Filename        : draft-ram-siprec-metadata-04.txt
> 	Pages           : 23
> 	Date            : 2011-03-07
>=20
> 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 the metadata model as
> viewed by Session Recording Server(SRS).
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ram-siprec-metadata-04.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> =

From Leon.Portman@nice.com  Mon Mar  7 07:12:20 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D21013A67D4 for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 07:12:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KKqacs9dIENJ for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 07:12:18 -0800 (PST)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id C308E3A67D8 for <siprec@ietf.org>; Mon,  7 Mar 2011 07:12:17 -0800 (PST)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Mon, 7 Mar 2011 17:13:30 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 7 Mar 2011 17:13:29 +0200
Thread-Topic: [siprec] Adopt metadata model as WG item? (was RE: I-D Action:draft-ram-siprec-metadata-04.txt)
Thread-Index: Acvct15QEc+wcp2iQZWED2n/Bc8wrwAH9/HQAAC5tbA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A837A86B@TLVMBX01.nice.com>
References: <20110307110004.10841.52270.idtracker@localhost> <A444A0F8084434499206E78C106220CA086A647BFE@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A647BFE@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Adopt metadata model as WG item? (was RE: I-D Action:draft-ram-siprec-metadata-04.txt)
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 07 Mar 2011 15:12:20 -0000

I think it is ready for the adoption of WG item

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Elwell, John
Sent: Monday, March 07, 2011 5:04 PM
To: siprec@ietf.org
Subject: [siprec] Adopt metadata model as WG item? (was RE: I-D Action:draf=
t-ram-siprec-metadata-04.txt)

Ram has posted this new version of the metadata model. He and his co-author=
s feel it is ready for consideration for adoption as a basis for our milest=
one "Submit metadata model to IESG as Informational RFC". The draft has bee=
n discussed during recent interim conference calls, as well as in Beijing, =
and the authors have endeavoured to take feedback into account. Adoption by=
 the WG would bring the document under WG control. Minor concerns with the =
document can be dealt with during that phase. The important thing is that p=
eople are comfortable with the general approach before taking this step.

Therefore, if anyone has any objection to adopting -04 as a basis for this =
milestone, please make your views known by 2011-03-14.

John (as chair)

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org
> [mailto:i-d-announce-bounces@ietf.org] On Behalf Of=20
> Internet-Drafts@ietf.org
> Sent: 07 March 2011 11:00
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-ram-siprec-metadata-04.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts=20
> directories.
>=20
> 	Title           : Session Initiation Protocol (SIP)=20
> Recording Metadata
> 	Author(s)       : R. R, et al.
> 	Filename        : draft-ram-siprec-metadata-04.txt
> 	Pages           : 23
> 	Date            : 2011-03-07
>=20
> Session recording is a critical requirement in many communications=20
> environments such as call centers and financial trading.  In some of=20
> these environments, all calls must be recorded for regulatory,=20
> compliance, and consumer protection reasons.  Recording of a session=20
> is typically performed by sending a copy of a media stream to a=20
> recording device.  This document describes the metadata model as=20
> viewed by Session Recording Server(SRS).
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ram-siprec-metadata-04.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader=20
> implementation to automatically retrieve the ASCII version of the=20
> Internet-Draft.
>=20
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From andrew.hutton@siemens-enterprise.com  Mon Mar  7 08:40:34 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A87C3A686E for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 08:40:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dqIqyQltfWYy for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 08:40:33 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id D0F293A67F2 for <siprec@ietf.org>; Mon,  7 Mar 2011 08:40:32 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3646953 for siprec@ietf.org; Mon, 7 Mar 2011 17:40:36 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 94A791EB82AE for <siprec@ietf.org>; Mon,  7 Mar 2011 17:40:34 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 7 Mar 2011 17:40:34 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 7 Mar 2011 17:40:33 +0100
Thread-Topic: Metadata Re-Sync
Thread-Index: Acvc5mCv81WpEpG/Qve/SW7pifeJ2A==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B61A90122@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E30B61A90122MCHP058Agloba_"
MIME-Version: 1.0
Subject: [siprec] Metadata Re-Sync
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 07 Mar 2011 16:40:34 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E30B61A90122MCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

I have a couple of questions/observations regarding the issue of a re-sync =
of metadata between the SRC and SRS.

The current draft (draft-portman-siprec-protocol-03) section 6.3.1. talks a=
bout the SRS requesting a metadata snapshot and by snapshot I assume we mea=
n what is in the metadata model at the moment in time that the snapshot is =
created.  I am therefore assuming there is no requirement for the SRC to ho=
ld on to any historical information about for example past participants in =
a CS. Therefore when we talk about a the SRS requesting a re-sync what it i=
s actually asking for is a current snapshot. Do people agree on that ?

Also give that a RS (Recording Session) can relate to many CS's then to mak=
e the re-sync manageable it might be a good idea if the SRS could request a=
 snapshot for a given CS.

It would therefore probably make sense to separate the metadata for differe=
nt CS's even when it is carried in the same RS. So would it be sensible to =
split the metadata for each CS in to different bodies in whatever SIP Reque=
st we agree will carry the metadata.

Regards
Andy


--_000_101C6067BEC68246B0C3F6843BCCC1E30B61A90122MCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"2">
<div>Hi All,</div>
<div>&nbsp;</div>
<div>I have a couple of questions/observations regarding the issue of a re-=
sync of metadata between the SRC and SRS.</div>
<div>&nbsp;</div>
<div>The current draft (draft-portman-siprec-protocol-03) section 6.3.1. ta=
lks about the SRS requesting a metadata snapshot and by snapshot I assume w=
e mean what is in the metadata model at the moment in time that the snapsho=
t is created.&nbsp; I am therefore assuming
there is no requirement for the SRC to hold on to any historical informatio=
n about for example past participants in a CS. Therefore when we talk about=
 a the SRS requesting a re-sync what it is actually asking for is a current=
 snapshot. Do people agree on that
?</div>
<div>&nbsp;</div>
<div>Also give that a RS (Recording Session) can relate to many CS's then t=
o make the re-sync manageable it might be a good idea if the SRS could requ=
est a snapshot for a given CS. </div>
<div>&nbsp;</div>
<div>It would therefore probably make sense to separate the metadata for di=
fferent CS's even when it is carried in the same RS. So would it be sensibl=
e to split the metadata for each CS in to different bodies in whatever SIP =
Request we agree will carry the
metadata.</div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Andy</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_101C6067BEC68246B0C3F6843BCCC1E30B61A90122MCHP058Agloba_--

From pkyzivat@cisco.com  Mon Mar  7 10:04:38 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C36E43A680C for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 10:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.521
X-Spam-Level: 
X-Spam-Status: No, score=-110.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fi6tb2tjATOC for <siprec@core3.amsl.com>; Mon,  7 Mar 2011 10:04:36 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 1CC673A67FF for <siprec@ietf.org>; Mon,  7 Mar 2011 10:04:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=3861; q=dns/txt; s=iport; t=1299521150; x=1300730750; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=soWDTl6nULDphQCXMx3YpUapW1wWx7YIg9//yxr9J0E=; b=erTTK93IHtX242rvtlce7Ls7t1z1vCKcsDlME/t1067ti3FaBWY5OH24 QpccHdmc5ToUzzAetmFuV0O9wvPq4YOYTfd10kOYWmUErdkTGt1kly55I 1xj7jD/0DPZZhFBHY+qfiBRzX8tIszfHVoSI8ii0sEaXBymMZXsVg+lYL o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAN+sdE1AZnwN/2dsb2JhbACmTnSiWpthhWIEhRyHFIND
X-IronPort-AV: E=Sophos;i="4.62,278,1297036800"; d="scan'208";a="222954179"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 07 Mar 2011 18:05:49 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p27I5nWB011786 for <siprec@ietf.org>; Mon, 7 Mar 2011 18:05:49 GMT
Message-ID: <4D751E7D.3060003@cisco.com>
Date: Mon, 07 Mar 2011 13:05:49 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: siprec@ietf.org
References: <101C6067BEC68246B0C3F6843BCCC1E30B61A90122@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E30B61A90122@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Metadata Re-Sync
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 07 Mar 2011 18:04:39 -0000

Andrew,

Its pretty important to get this right, and there are subtleties to it.

IMO we must make the assumption that the SRC retains a minimum of 
historical information. It is shipping data to the SRS so that it *can* 
forget about it. So when there is a need for the SRC to do a "snapshot", 
what that really means is to send what it still knows, possibly 
including "some" stuff that it remembers. There is a likelihood that 
stuff will get lost in this process.

For the mechanisms we are currently discussing, the SRC is assigning IDs 
to things in order that it can refer back to them later. For instance, 
IDs for CSs, CS-groups, media-sessions, participants, etc. We are 
currently expecting these to be dynamically assigned UUIDs.

Hence, if the SRC establishes a CS and a CS-group, each will have an 
associated ID, and the message that says the CS is a member of the 
CS-group will contain both IDs.

Clearly if the SRC wants to retain the option of adding additional CSs 
to a CS-group it will need to remember the ID of the CS-group. It can 
forget this when there is no longer any need to reference it.

If asked to send a snapshot, the SRC will hopefully remember the IDs for 
the CSs that are still active. And it will probably remember the IDs of 
the CS-groups those CSs were assigned to. (I'm not certain if that is 
necessary.)

But it might not retain much metadata info about those things that was 
sent in the past. It might just remember "I have CS-group IDs for these 
CSs". When sending a "snapshot" it might just be sending metadata 
describing current state of active sessions with reference to IDs 
created in the past. If the SRS did not get or properly process the 
metadata that first defined those IDs it might not be able to properly 
process the new snapshot.

An alternative is that when asked for a "snapshot" the SRC might 
intentially forget all the old IDs it had. Instead it could start "from 
scratch" assigning new IDs to everything it currently knows about, and 
sending metadata definitions of those, even if those definitions lack a 
lot of desirable information. The advantage is that there is no reliance 
on anything sent previously, and so corruption issues are minimized.

Obviously this is a bit difficult to discuss in the abstract, since it 
is tied pretty tightly to specific implementation approaches.

Nothing is cast in stone here. So we can discuss pro/cons of different 
approaches.

	Thanks,
	Paul

On 3/7/2011 11:40 AM, Hutton, Andrew wrote:
> Hi All,
> I have a couple of questions/observations regarding the issue of a
> re-sync of metadata between the SRC and SRS.
> The current draft (draft-portman-siprec-protocol-03) section 6.3.1.
> talks about the SRS requesting a metadata snapshot and by snapshot I
> assume we mean what is in the metadata model at the moment in time that
> the snapshot is created. I am therefore assuming there is no requirement
> for the SRC to hold on to any historical information about for example
> past participants in a CS. Therefore when we talk about a the SRS
> requesting a re-sync what it is actually asking for is a current
> snapshot. Do people agree on that ?
> Also give that a RS (Recording Session) can relate to many CS's then to
> make the re-sync manageable it might be a good idea if the SRS could
> request a snapshot for a given CS.
> It would therefore probably make sense to separate the metadata for
> different CS's even when it is carried in the same RS. So would it be
> sensible to split the metadata for each CS in to different bodies in
> whatever SIP Request we agree will carry the metadata.
> Regards
> Andy
>
>
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From Internet-Drafts@ietf.org  Mon Mar  7 21:15:03 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 110FB28C112; Mon,  7 Mar 2011 21:15:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r+H1UTO+Nh8x; Mon,  7 Mar 2011 21:15:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 528713A696F; Mon,  7 Mar 2011 21:15:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110308051502.32383.27444.idtracker@localhost>
Date: Mon, 07 Mar 2011 21:15:02 -0800
Cc: siprec@ietf.org
Subject: [siprec] I-D Action:draft-ietf-siprec-req-07.txt
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 08 Mar 2011 05:15:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP Recording Working Group of the IETF.


	Title           : Requirements for SIP-based Media Recording (SIPREC)
	Author(s)       : K. Rehor, et al.
	Filename        : draft-ietf-siprec-req-07.txt
	Pages           : 16
	Date            : 2011-03-07

Session recording is a critical requirement in many business
communications environments such as call centers and financial
trading floors.  In some of these environments, all calls must be
recorded for regulatory and compliance reasons.  In others, calls may
be recorded for quality control or business analytics.

Recording is typically performed by sending a copy of the session
media to the recording devices.  This document specifies requirements
for extensions to SIP that will manage delivery of RTP media to a
recording device.  This is being referred to as SIP-based Media
Recording.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-siprec-req-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-siprec-req-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-07211343.I-D@ietf.org>


--NextPart--

From partr@cisco.com  Tue Mar  8 06:22:46 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAD693A67B7 for <siprec@core3.amsl.com>; Tue,  8 Mar 2011 06:22:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.842
X-Spam-Level: 
X-Spam-Status: No, score=-9.842 tagged_above=-999 required=5 tests=[AWL=0.157,  BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pAb8HVz-v1dR for <siprec@core3.amsl.com>; Tue,  8 Mar 2011 06:22:44 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id B3AAD3A6874 for <siprec@ietf.org>; Tue,  8 Mar 2011 06:22:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=2752; q=dns/txt; s=iport; t=1299594238; x=1300803838; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=dvCNw+Rb7vjvRrNI+WWPIAb6Mu7PxHpaStqgppCTAco=; b=bK/i7hxNTp9nCvXVpzxTkJCulZ6GUnyA/uMALR10jqI40KGJ2wrCqsQC u+ys7JWTKLRo40R5ioFV4KlHWR/KAdWhffa0eXo8em4oFyG3Wep4uYc8A A/NDfE6tl6fUlBY5xs1kgwaMeyNXzsDywLa/9VU0IvqjnAp6eYLg0FNyk Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEBAM7KdU1AaMHG/2dsb2JhbACYEz+NbnSiU5xDhWMEhRuKZA
X-IronPort-AV: E=Sophos;i="4.62,284,1297036800"; d="scan'208";a="317948208"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-2.cisco.com with ESMTP; 08 Mar 2011 14:23:55 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p28ENV62005314 for <siprec@ietf.org>; Tue, 8 Mar 2011 14:23:54 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 8 Mar 2011 19:53:53 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Mar 2011 19:53:51 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review Request for draft-ram-siprec-metadata-format-01 
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfw
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: <siprec@ietf.org>
X-OriginalArrivalTime: 08 Mar 2011 14:23:53.0288 (UTC) FILETIME=[73845480:01CBDD9C]
Subject: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 08 Mar 2011 14:22:47 -0000

Hi all,

As per the mailing list comments and interim meeting discussion, I
updated -01 draft of draft-ram-siprec-metadata-format and send it for
review. The draft is available at
http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt. The
following update are done as part of -01 draft:

1) URN UUID (RFC 4122) mechanism is used as the unique id mechanism for
relevant XML elements like group, session, stream, participant.=20

2) Partial XML passing in RS is supported by having unique URN UUID for
group, session, stream, participant, recording, extension data which are
directly under recording-metadata container/namespace.=20

3) Include recording-metadata element as a container element instead of
recording element. This helps in avoiding duplicate data of recording
elements during the partial update

4) Updated elements in XML document as per draft-ram-siprec-metadata-04
elements & associations

5) Changed appdata element name as extensiondata

6) Removed container element like sessions, participants, streams from
XML document as  parent reference exists in each element

7) Added Partial Update example & SIP usage XML+SDP example

8) Portion of security considerations section is added.

Could you please review and provide your expert comments on the draft.

Thanks
Partha=20

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
Sent: Tuesday, March 08, 2011 7:31 PM
To: Parthasarathi R (partr)
Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
Subject: New Version Notification for
draft-ram-siprec-metadata-format-01=20


A new version of I-D, draft-ram-siprec-metadata-format-01.txt has been
successfully submitted by Parthasarathi R and posted to the IETF
repository.

Filename:	 draft-ram-siprec-metadata-format
Revision:	 01
Title:		 Session Initiation Protocol (SIP) Recording Metadata
Format
Creation_date:	 2011-03-08
WG ID:		 Independent Submission
Number_of_pages: 20

Abstract:
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.  The requirements for which are described in
[I-D.ietf-siprec-req], the architecture for which is described in
[I-D.ietf-siprec-architecture], and the metadata model viewed by Session
Recording Server is described in [I-D.ram-siprec-metadata].
This document focuses on the Recording metadata format which describes
the communication session.
=20



The IETF Secretariat.



From john.elwell@siemens-enterprise.com  Tue Mar  8 09:37:54 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F12413A693D for <siprec@core3.amsl.com>; Tue,  8 Mar 2011 09:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dbeof4YI6gfZ for <siprec@core3.amsl.com>; Tue,  8 Mar 2011 09:37:53 -0800 (PST)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id D520B3A6936 for <siprec@ietf.org>; Tue,  8 Mar 2011 09:37:52 -0800 (PST)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3668703; Tue, 8 Mar 2011 18:39:05 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 0E96523F0294; Tue,  8 Mar 2011 18:39:05 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 8 Mar 2011 18:39:05 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>, Leon Portman <Leon.Portman@nice.com>, "Ken Rehor (krehor) (krehor@cisco.com)" <krehor@cisco.com>
Date: Tue, 8 Mar 2011 18:39:04 +0100
Thread-Topic: Last chance for changes to siprec-req-07
Thread-Index: Acvdt7euTNDO2n4QSAyVfMXgONVCfQ==
Message-ID: <A444A0F8084434499206E78C106220CA086A648103@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] Last chance for changes to siprec-req-07
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 08 Mar 2011 17:37:54 -0000

The editors have posted req-07. This is your last chance to request changes=
. Deadline 2011-03-13 (to give the editors chance to produce -08 before the=
 deadline the next day).

I noticed the following:
1. IDNITS gave a warning about the disclaimer concerning pre-RFC5378 work i=
n the boiler plate. Since the document (and also its draft-rehor predecesso=
r) is post 2008, is this applicable?
2. IDNITS revealed missing references RFC 4733 and RFC 4103 (I believe both=
 are normative references)
3. IDNITS revealed unused reference RFC 2804.
4. Change "Ral-time" to "Real-time"
5. "REQ-001 The mechanism MUST provide a means for "using the SIP
   protocol for" establishing, maintaining and terminating"
Remove 'the quotes around using the SIP protocol for'
6. "Note: A mixed audio stream is where several Communication Sessions
   are carried in a single Recording Session."
Change to:
"Note: A mixed audio stream is where several related Communication Sessions
   are carried in a single Recording Session."
(i.e., add the word "related".
7. "Requirements for participant notification of recording varies widely
   by jurisdiction."
Change "varies" to "vary".

Would the editors please correct these and ensure the document passes IDNIT=
S. Please ensure -08 is posted by the submission deadline 2011-03-14. By al=
l means wait for other comments, but not at the expense of missing the dead=
line!

Thanks,

John


From rmohanr@cisco.com  Wed Mar  9 05:36:11 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 488A63A683E for <siprec@core3.amsl.com>; Wed,  9 Mar 2011 05:36:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.301, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aC0FkMdjkQU2 for <siprec@core3.amsl.com>; Wed,  9 Mar 2011 05:36:06 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id BB2A93A684D for <siprec@ietf.org>; Wed,  9 Mar 2011 05:36:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=11424; q=dns/txt; s=iport; t=1299677842; x=1300887442; h=mime-version:subject:date:message-id:from:to; bh=ztiTuV//k7arIvs6sN3n3JuqGdKhkJgOdex71mxY5Dw=; b=cJFE9xYadgD5DEwJI3SDS5VU4UvjdACZ+2CHLen7bFaGdmTteHG+Uuld OB0JHPt8tEkvxBTHE/dxzXvMP9NvWphkDH1ehEIZ6MlmgsmeMf/LQgXQV KI161PgUy/Nh0V1IFgWYDpOATakH+9wmUfbb99p7Zvr6fcB9rZuYJDE71 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvYEAMIRd01AaMHGgWdsb2JhbACCT6QeFQEBFiIlpn6cSoVlBIUgimg
X-IronPort-AV: E=Sophos;i="4.62,290,1297036800"; d="scan'208,217";a="78423946"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by ams-iport-1.cisco.com with ESMTP; 09 Mar 2011 13:37:17 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p29DZUCR020602; Wed, 9 Mar 2011 13:37:16 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 9 Mar 2011 19:06:11 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBDE5E.F42EFCEE"
Date: Wed, 9 Mar 2011 19:06:10 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD0595DC37@XMB-BGL-417.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-portman-siprec-protocol-03
Thread-Index: AcveXvN2+0yxcSaqRYuaW9cRuFWTxQ==
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: <siprec@ietf.org>, "Leon Portman" <Leon.Portman@nice.com>
X-OriginalArrivalTime: 09 Mar 2011 13:36:11.0890 (UTC) FILETIME=[F4676520:01CBDE5E]
Subject: [siprec] Comments on draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 09 Mar 2011 13:36:11 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBDE5E.F42EFCEE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Leon et all,

=20

Good work in putting up this draft. Here are some of my general
comments:

=20

The title says "The SIP-based Media Recording Protocol (SIPREC)" where
as abstract says "SIPREC Session Recording Protocol". I think it's
better to have a consistent naming convention. I suggest using "Session
Recording Protocol" which the charter has. The same(Using of SIPREC
protocol and Session Recording Protocol alternatively) is seen at
several places across the document . It would be better to have one
naming convention across the document.

=20

The introduction section says

"In order to allow access to such recordings, information about the
communication session (metadata) is also shared between SRC and SRS."

This sentence is little confusing as it sounds like metadata needs to be
shared between SRC and SRS to allow access to recording. Irrespective of
whether we send metadata or not SRS can still access the data. So I
suggest we reword it as

"The metadata about a CS SHALL be sent from SRC to SRS"

=20

There may not be need to re-define the terms in Section 2 as
ietf-siprec-req already has them. IMO reference to ietf-siprec-req is
sufficient.

=20

I am not sure if scope section is needed, SIPREC requirements document
clearly lists what are the requirements that needs to be addressed.
Anything not mentioned there is outside the scope. Do we need to
explicitly call out the list here ?

=20

Section 4.1, Figure 2

I see that RS invite is sent after CS is connected. I don't think we
need to restrict the call flow to this. There MAY be implementations
where RS may be setup right after SRC receives INVITE even before CS is
connected. Also for persistent recording cases the call flow will be
different.

=20

We will have to see if there is a real need to have the metadata
snapshot request provided as an INFO  package.  I have not seen a strong
use case for that as of now.  IMO ( and raised by others too) it's
better to use UPDATE/RE-INVITE.

=20

Section 5 has this text

"The SRC must be able to accept re-INVITE from SRS with the updated SDP
as part of the session timer mechanism." why do we need this text here ?
Is Session refresh handling different for RS from what is mentioned in
RFC 4028 ? If not I don't see a need to mention here.=20

=20

Section 5.3.1 we need to discuss more on how re-sync between SRS and SRC
can happen. I will give my comments on the mail thread that Andy has
started for this.

Please also add reference to metadata format draft that has XML schema
(draft-ram-siprec-metadata-format-01)

=20

Regards,

Ram

=20


------_=_NextPart_001_01CBDE5E.F42EFCEE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi Leon et =
all,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Good work in putting up this draft. Here are some of =
my general comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The title =
says &quot;The SIP-based Media Recording Protocol (SIPREC)&quot; where =
as abstract says &quot;SIPREC Session Recording Protocol&quot;. I think =
it&#8217;s better to have a consistent naming convention. I suggest =
using &quot;Session Recording Protocol&quot; which the charter has. The =
same(Using of SIPREC protocol and Session Recording Protocol =
alternatively) is seen at several places across the document . It would =
be better to have one naming convention across the =
document.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The introduction section says<o:p></o:p></p><p =
class=3DMsoNormal>&quot;In order to allow access to such recordings, =
information about the communication session (metadata) is also shared =
between SRC and SRS.&quot;<o:p></o:p></p><p class=3DMsoNormal>This =
sentence is little confusing as it sounds like metadata needs to be =
shared between SRC and SRS to allow access to recording. Irrespective of =
whether we send metadata or not SRS can still access the data. So I =
suggest we reword it as<o:p></o:p></p><p class=3DMsoNormal>&quot;The =
metadata about a CS SHALL be sent from SRC to SRS&quot;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>There may =
not be need to re-define the terms in Section 2 as ietf-siprec-req =
already has them. IMO reference to ietf-siprec-req is =
sufficient.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>I am not sure if scope section is needed, SIPREC =
requirements document clearly lists what are the requirements that needs =
to be addressed. Anything not mentioned there is outside the scope. Do =
we need to explicitly call out the list here ?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Section 4.1, =
Figure 2<o:p></o:p></p><p class=3DMsoNormal>I see that RS invite is sent =
after CS is connected. I don&#8217;t think we need to restrict the call =
flow to this. There MAY be implementations where RS may be setup right =
after SRC receives INVITE even before CS is connected. Also for =
persistent recording cases the call flow will be =
different.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>We will have to see if there is a real need to have =
the metadata snapshot request provided as an INFO&nbsp; package. &nbsp;I =
have not seen a strong use case for that as of now.&nbsp; IMO ( and =
raised by others too) it&#8217;s better to use =
UPDATE/RE-INVITE.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Section 5 =
has this text<o:p></o:p></p><p class=3DMsoNormal>&quot;The SRC must be =
able to accept re-INVITE from SRS with the updated SDP as part of the =
session timer mechanism.&quot; why do we need this text here ? Is =
Session refresh handling different for RS from what is mentioned in RFC =
4028 ? If not I don&#8217;t see a need to mention here. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Section 5.3.1 we need to discuss more on how re-sync =
between SRS and SRC can happen. I will give my comments on the mail =
thread that Andy has started for this.<o:p></o:p></p><p =
class=3DMsoNormal> <o:p></o:p></p><p class=3DMsoNormal>Please also add =
reference to metadata format draft that has XML schema =
(draft-ram-siprec-metadata-format-01)<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Regards,<o:p></o:p></p><p =
class=3DMsoNormal>Ram<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------_=_NextPart_001_01CBDE5E.F42EFCEE--

From Leon.Portman@nice.com  Thu Mar 10 05:58:12 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41A633A67A1 for <siprec@core3.amsl.com>; Thu, 10 Mar 2011 05:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=-0.251, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_45=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3mRHkzyu8mUM for <siprec@core3.amsl.com>; Thu, 10 Mar 2011 05:58:06 -0800 (PST)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 4C10A3A6996 for <siprec@ietf.org>; Thu, 10 Mar 2011 05:58:04 -0800 (PST)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Thu, 10 Mar 2011 15:59:21 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 10 Mar 2011 15:59:20 +0200
Thread-Topic: Comments on draft-portman-siprec-protocol-03
Thread-Index: AcveXvN2+0yxcSaqRYuaW9cRuFWTxQAyu52Q
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A83EA6D4@TLVMBX01.nice.com>
References: <35BCE99A477D6A4986FB2216D8CF2CFD0595DC37@XMB-BGL-417.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD0595DC37@XMB-BGL-417.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_07465C1D981ABC41A344374066AE1A2C38A83EA6D4TLVMBX01nicec_"
MIME-Version: 1.0
Subject: Re: [siprec] Comments on draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 10 Mar 2011 13:58:12 -0000

--_000_07465C1D981ABC41A344374066AE1A2C38A83EA6D4TLVMBX01nicec_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Ram Hi

Thank you very much for the comments

Please see below

Leon

From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Ram Mohan R (rmohanr)
Sent: Wednesday, March 09, 2011 3:36 PM
To: siprec@ietf.org; Leon Portman
Subject: [siprec] Comments on draft-portman-siprec-protocol-03

Hi Leon et all,

Good work in putting up this draft. Here are some of my general comments:

The title says "The SIP-based Media Recording Protocol (SIPREC)" where as a=
bstract says "SIPREC Session Recording Protocol". I think it's better to ha=
ve a consistent naming convention. I suggest using "Session Recording Proto=
col" which the charter has. The same(Using of SIPREC protocol and Session R=
ecording Protocol alternatively) is seen at several places across the docum=
ent . It would be better to have one naming convention across the document.

[Leon] yes, good comment. SIPREC was used as a friendly protocol name.

The introduction section says
"In order to allow access to such recordings, information about the communi=
cation session (metadata) is also shared between SRC and SRS."
This sentence is little confusing as it sounds like metadata needs to be sh=
ared between SRC and SRS to allow access to recording. Irrespective of whet=
her we send metadata or not SRS can still access the data. So I suggest we =
reword it as
"The metadata about a CS SHALL be sent from SRC to SRS"
[Leon] Agree

There may not be need to re-define the terms in Section 2 as ietf-siprec-re=
q already has them. IMO reference to ietf-siprec-req is sufficient.
[Leon] We wanted to have the protocol document self-contained for reading a=
nd understating as possible

I am not sure if scope section is needed, SIPREC requirements document clea=
rly lists what are the requirements that needs to be addressed. Anything no=
t mentioned there is outside the scope. Do we need to explicitly call out t=
he list here ?
[Leon] We were just using template from other protocol drafts (like XCON). =
Usually they have scope inside

Section 4.1, Figure 2
I see that RS invite is sent after CS is connected. I don't think we need t=
o restrict the call flow to this. There MAY be implementations where RS may=
 be setup right after SRC receives INVITE even before CS is connected. Also=
 for persistent recording cases the call flow will be different.
[Leon] Agree, it is just an example

We will have to see if there is a real need to have the metadata snapshot r=
equest provided as an INFO  package.  I have not seen a strong use case for=
 that as of now.  IMO ( and raised by others too) it's better to use UPDATE=
/RE-INVITE.
[Leon] Lets discuss it in Prague. It is important point

Section 5 has this text
"The SRC must be able to accept re-INVITE from SRS with the updated SDP as =
part of the session timer mechanism." why do we need this text here ? Is Se=
ssion refresh handling different for RS from what is mentioned in RFC 4028 =
? If not I don't see a need to mention here.
[Leon] We should finalize this as well.

Section 5.3.1 we need to discuss more on how re-sync between SRS and SRC ca=
n happen. I will give my comments on the mail thread that Andy has started =
for this.
[Leon] Ok

Please also add reference to metadata format draft that has XML schema (dra=
ft-ram-siprec-metadata-format-01)
[Leon] We should check if it will not create some circular references

Regards,
Ram


--_000_07465C1D981ABC41A344374066AE1A2C38A83EA6D4TLVMBX01nicec_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Ram Hi<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'color:#1F497D'>Thank you very much for the comments<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p><=
/span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>Please see bel=
ow<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F49=
7D'>Leon<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F=
497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border-top=
:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span=
></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> si=
prec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] <b>On Behalf Of </b>=
Ram Mohan R (rmohanr)<br><b>Sent:</b> Wednesday, March 09, 2011 3:36 PM<br>=
<b>To:</b> siprec@ietf.org; Leon Portman<br><b>Subject:</b> [siprec] Commen=
ts on draft-portman-siprec-protocol-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi Leon et all,=
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorm=
al>Good work in putting up this draft. Here are some of my general comments=
:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal>The title says &quot;The SIP-based Media Recording Protocol (SIPREC)&qu=
ot; where as abstract says &quot;SIPREC Session Recording Protocol&quot;. I=
 think it&#8217;s better to have a consistent naming convention. I suggest =
using &quot;Session Recording Protocol&quot; which the charter has. The sam=
e(Using of SIPREC protocol and Session Recording Protocol alternatively) is=
 seen at several places across the document . It would be better to have on=
e naming convention across the document.<o:p></o:p></p><p class=3DMsoNormal=
><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'color:#1F497D'>[Leon] yes, good comment. SIPREC was use=
d as a friendly protocol name.<o:p></o:p></span></p><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p><p class=3DMsoNormal>The introduction section says<o:p><=
/o:p></p><p class=3DMsoNormal>&quot;In order to allow access to such record=
ings, information about the communication session (metadata) is also shared=
 between SRC and SRS.&quot;<o:p></o:p></p><p class=3DMsoNormal>This sentenc=
e is little confusing as it sounds like metadata needs to be shared between=
 SRC and SRS to allow access to recording. Irrespective of whether we send =
metadata or not SRS can still access the data. So I suggest we reword it as=
<o:p></o:p></p><p class=3DMsoNormal>&quot;The metadata about a CS SHALL be =
sent from SRC to SRS&quot;<o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>[Leon] Agree<o:p></o:p></span></p><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><p class=3DMsoNormal>There may not be need to re-define=
 the terms in Section 2 as ietf-siprec-req already has them. IMO reference =
to ietf-siprec-req is sufficient.<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>[Leon] We wanted to have the protocol document self=
-contained for reading and understating as possible<o:p></o:p></span></p><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I am not sure =
if scope section is needed, SIPREC requirements document clearly lists what=
 are the requirements that needs to be addressed. Anything not mentioned th=
ere is outside the scope. Do we need to explicitly call out the list here ?=
<o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>[Leon] We=
 were just using template from other protocol drafts (like XCON). Usually t=
hey have scope inside<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p><p class=3DMsoNormal>Section 4.1, Figure 2<o:p></o:p></p><p class=
=3DMsoNormal>I see that RS invite is sent after CS is connected. I don&#821=
7;t think we need to restrict the call flow to this. There MAY be implement=
ations where RS may be setup right after SRC receives INVITE even before CS=
 is connected. Also for persistent recording cases the call flow will be di=
fferent.<o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>[=
Leon] Agree, it is just an example<o:p></o:p></span></p><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We will have to see if there is=
 a real need to have the metadata snapshot request provided as an INFO&nbsp=
; package. &nbsp;I have not seen a strong use case for that as of now.&nbsp=
; IMO ( and raised by others too) it&#8217;s better to use UPDATE/RE-INVITE=
.<o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>[Leon] L=
ets discuss it in Prague. It is important point<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Section 5 has this=
 text<o:p></o:p></p><p class=3DMsoNormal>&quot;The SRC must be able to acce=
pt re-INVITE from SRS with the updated SDP as part of the session timer mec=
hanism.&quot; why do we need this text here ? Is Session refresh handling d=
ifferent for RS from what is mentioned in RFC 4028 ? If not I don&#8217;t s=
ee a need to mention here. <o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>[Leon] We should finalize this as well.<o:p></o:p></span=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Section=
 5.3.1 we need to discuss more on how re-sync between SRS and SRC can happe=
n. I will give my comments on the mail thread that Andy has started for thi=
s.<o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>[Leon] =
Ok<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>Please also add reference to metadata format draft that has XM=
L schema (draft-ram-siprec-metadata-format-01)<o:p></o:p></p><p class=3DMso=
Normal><span style=3D'color:#1F497D'>[Leon] We should check if it will not =
create some circular references<o:p></o:p></span></p><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Regards,<o:p></o:p></p><p class=3D=
MsoNormal>Ram<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
></body></html>=

--_000_07465C1D981ABC41A344374066AE1A2C38A83EA6D4TLVMBX01nicec_--

From pkyzivat@cisco.com  Thu Mar 10 06:09:59 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E3D03A69D8 for <siprec@core3.amsl.com>; Thu, 10 Mar 2011 06:09:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08oti1J+qWs6 for <siprec@core3.amsl.com>; Thu, 10 Mar 2011 06:09:58 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 7A23E3A69C8 for <siprec@ietf.org>; Thu, 10 Mar 2011 06:09:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=479; q=dns/txt; s=iport; t=1299766276; x=1300975876; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=4rcRDz1Y2hO9Ha+ZT5DC6yaipyzzCu+4Egvl1+Z4ohs=; b=CT3fDN+cTGE4V9V4mb4JxtgXHEyht5slXvxIaCJgC+/dnS8BOTYtrYjh pipjqm05aYR5fBXG4xDMzODhgMDgwSy0kYvs/Ka6XaoNrKy2Zw48ohcuc WDTuE37nmCdy5CRtmUqL6wzJZefpry9l/dYlv5IBPgQq6G03ZDlAE1NbN E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggHAP5qeE2rRDoH/2dsb2JhbACZFY1td6ROnD2FYgSFJIcfg0o
X-IronPort-AV: E=Sophos;i="4.62,295,1297036800"; d="scan'208";a="343688009"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-5.cisco.com with ESMTP; 10 Mar 2011 14:11:16 +0000
Received: from [10.86.255.13] ([10.86.255.13]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2AEBFDp031376 for <siprec@ietf.org>; Thu, 10 Mar 2011 14:11:16 GMT
Message-ID: <4D78DC03.5070002@cisco.com>
Date: Thu, 10 Mar 2011 09:11:15 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: siprec@ietf.org
References: <35BCE99A477D6A4986FB2216D8CF2CFD0595DC37@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A83EA6D4@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A83EA6D4@TLVMBX01.nice.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Comments on draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 10 Mar 2011 14:09:59 -0000

On 3/10/2011 8:59 AM, Leon Portman wrote:

> Please also add reference to metadata format draft that has XML schema
> (draft-ram-siprec-metadata-format-01)
>
> [Leon] We should check if it will not create some circular references

Circular references are not forbidden.
The consequence is that they must make the transition to RFC 
concurrently. That may be ok. But if things can be arranged to avoid 
circular references it is probably better.

	Thanks,
	Paul

From partr@cisco.com  Thu Mar 10 08:30:31 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DEB443A6A1A for <siprec@core3.amsl.com>; Thu, 10 Mar 2011 08:30:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.515
X-Spam-Level: 
X-Spam-Status: No, score=-9.515 tagged_above=-999 required=5 tests=[AWL=-0.313, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gctuQrK4WG-l for <siprec@core3.amsl.com>; Thu, 10 Mar 2011 08:30:30 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 097543A6B41 for <siprec@ietf.org>; Thu, 10 Mar 2011 08:30:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=5509; q=dns/txt; s=iport; t=1299774708; x=1300984308; h=mime-version:subject:date:message-id:references:from:to; bh=uphr6yqb88KUUEARjHnX5PMwwH8NcBQt9Wlh25oOxVI=; b=fJSXRufTtpJ/V72ITYXt3G1FSlTLREyqgsbN2EZ6Pi1MdOc39ei+yinb AcNO25FK5480kPTl7YARQa/wuiunnJBkfBcnrDWO4zxa1oLzSY/wR+QZt vNp2v29Ezn2W3U4oBpX6huydvKPXU9G2shLbzNRkADbsSfp4aKK3VhZcz 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqoEAFGMeE2Q/khMgWdsb2JhbAClUlcUAQEWJiWkWJxAhWIEhSKKcQ
X-IronPort-AV: E=Sophos;i="4.62,296,1297036800"; d="scan'208,217";a="78630422"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 10 Mar 2011 16:31:47 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2AGVN29015057; Thu, 10 Mar 2011 16:31:47 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 10 Mar 2011 22:01:36 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBDF40.9F9AA6E0"
Date: Thu, 10 Mar 2011 22:01:35 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A690@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Comments on draft-portman-siprec-protocol-03
Thread-Index: AcvfLQ01RnLyWElMTjmQY3HJFTG0aQAESxoA
References: <35BCE99A477D6A4986FB2216D8CF2CFD0595DC37@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A83EA6D4@TLVMBX01.nice.com> <4D78DC03.5070002@cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, <siprec@ietf.org>, <Leon.Portman@nice.com>
X-OriginalArrivalTime: 10 Mar 2011 16:31:36.0198 (UTC) FILETIME=[9FCB1A60:01CBDF40]
Subject: Re: [siprec] Comments on draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 10 Mar 2011 16:30:32 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBDF40.9F9AA6E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Leon,
=20
Adding to Paul's point, currently Sec  8 of =
draft-ram-siprec-metadata-format-01 refers =
draft-portman-siprec-protocol-03, Sec 7 & 8 of =
draft-ram-siprec-metadata-format-01  is written for providing more =
information to understand usage of XML with SIP & SDP and there is no =
normative statements involved related to metadata. when everybody comes =
to have some common understanding, these example shall be removed or =
modified with just XML body in the later stage . So, circular reference =
shall be avoided easily then.
=20
Apart from this, there was a comment not to include SIP stuff in =
draft-ram-siprec-metadata-format-01 and it is mentioned as an one open =
item in Sec 7:

   "Open item: Whether it is allowed to have SIP specific table in this
   draft?"=20
=20
Please let me know your opinion here.=20
=20
Thanks
Partha
________________________________

From: siprec-bounces@ietf.org on behalf of Paul Kyzivat (pkyzivat)
Sent: Thu 3/10/2011 7:41 PM
To: siprec@ietf.org
Subject: Re: [siprec] Comments on draft-portman-siprec-protocol-03





On 3/10/2011 8:59 AM, Leon Portman wrote:

> Please also add reference to metadata format draft that has XML schema
> (draft-ram-siprec-metadata-format-01)
>
> [Leon] We should check if it will not create some circular references

Circular references are not forbidden.
The consequence is that they must make the transition to RFC
concurrently. That may be ok. But if things can be arranged to avoid
circular references it is probably better.

        Thanks,
        Paul
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec



------_=_NextPart_001_01CBDF40.9F9AA6E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: [siprec] Comments on =
draft-portman-siprec-protocol-03</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText84390>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>=0A=
<DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>=0A=
<DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Leon,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Adding to Paul's point, =
currently Sec&nbsp; 8 of draft-ram-siprec-metadata-format-01 refers =
draft-portman-siprec-protocol-03, Sec 7 &amp; 8 of =
draft-ram-siprec-metadata-format-01&nbsp;&nbsp;is written for providing =
more information to understand usage of XML with SIP &amp; SDP and there =
is no normative statements involved related to metadata. when everybody =
comes to have some common understanding, these example shall be removed =
or modified with just XML body in the later stage .&nbsp;So, circular =
reference shall be avoided easily then.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Apart from this,&nbsp;there =
was a&nbsp;comment not to include SIP stuff in =
draft-ram-siprec-metadata-format-01 and it is mentioned as an one open =
item in Sec 7:</FONT></DIV>=0A=
<DIV dir=3Dltr><BR><FONT size=3D2 face=3DArial>&nbsp;&nbsp;&nbsp;<SPAN =
class=3D875042616-10032011>"</SPAN>Open item: Whether it is allowed to =
have SIP specific table in this<BR>&nbsp;&nbsp; draft?<SPAN =
class=3D875042616-10032011>"</SPAN>&nbsp;</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Please let me know your =
opinion here. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 =
face=3DArial>Partha</FONT></DIV></DIV></FONT></FONT>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> siprec-bounces@ietf.org on =
behalf of Paul Kyzivat (pkyzivat)<BR><B>Sent:</B> Thu 3/10/2011 7:41 =
PM<BR><B>To:</B> siprec@ietf.org<BR><B>Subject:</B> Re: [siprec] =
Comments on =
draft-portman-siprec-protocol-03<BR></FONT><BR></DIV></DIV></DIV></DIV>=0A=
<DIV><BR><BR>=0A=
<P><FONT size=3D2>On 3/10/2011 8:59 AM, Leon Portman wrote:<BR><BR>&gt; =
Please also add reference to metadata format draft that has XML =
schema<BR>&gt; (draft-ram-siprec-metadata-format-01)<BR>&gt;<BR>&gt; =
[Leon] We should check if it will not create some circular =
references<BR><BR>Circular references are not forbidden.<BR>The =
consequence is that they must make the transition to =
RFC<BR>concurrently. That may be ok. But if things can be arranged to =
avoid<BR>circular references it is probably =
better.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Thanks,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Paul<BR>_______________________________________________<BR>siprec =
mailing list<BR>siprec@ietf.org<BR><A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01CBDF40.9F9AA6E0--

From john.elwell@siemens-enterprise.com  Thu Mar 10 08:37:19 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F8BC3A69C3 for <siprec@core3.amsl.com>; Thu, 10 Mar 2011 08:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.615
X-Spam-Level: 
X-Spam-Status: No, score=-102.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N916UM7yR8O3 for <siprec@core3.amsl.com>; Thu, 10 Mar 2011 08:37:18 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 00F303A6916 for <siprec@ietf.org>; Thu, 10 Mar 2011 08:37:17 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3689378; Thu, 10 Mar 2011 17:38:21 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 2DBAA1EB82B5; Thu, 10 Mar 2011 17:38:20 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 10 Mar 2011 17:38:20 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 10 Mar 2011 17:38:19 +0100
Thread-Topic: Comments on draft-portman-siprec-protocol-03
Thread-Index: AcveXvN2+0yxcSaqRYuaW9cRuFWTxQAyu52QAAXGysA=
Message-ID: <A444A0F8084434499206E78C106220CA086A89A930@MCHP058A.global-ad.net>
References: <35BCE99A477D6A4986FB2216D8CF2CFD0595DC37@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A83EA6D4@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A83EA6D4@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Comments on draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 10 Mar 2011 16:37:19 -0000

</snip>=20
>=20
> There may not be need to re-define the terms in Section 2 as=20
> ietf-siprec-req already has them. IMO reference to=20
> ietf-siprec-req is sufficient.
>=20
> [Leon] We wanted to have the protocol document self-contained=20
> for reading and understating as possible
[JRE] That is fine while it is an individual draft, but when these drafts a=
re adopted as WG documents, I would want to avoid too much duplication.

> I am not sure if scope section is needed, SIPREC requirements=20
> document clearly lists what are the requirements that needs=20
> to be addressed. Anything not mentioned there is outside the=20
> scope. Do we need to explicitly call out the list here ?
>=20
> [Leon] We were just using template from other protocol drafts=20
> (like XCON). Usually they have scope inside
[JRE] There is no set rule. If it makes sense to have a scope section, rath=
er than putting such statements into the introduction section or relying on=
 a reference to the requirements document, say, then fine. But there certai=
nly is no necessity for a scope section.

John (as chair)

From andrew.hutton@siemens-enterprise.com  Fri Mar 11 06:07:44 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F0A93A6C07 for <siprec@core3.amsl.com>; Fri, 11 Mar 2011 06:07:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFjqjsKoCrJX for <siprec@core3.amsl.com>; Fri, 11 Mar 2011 06:07:43 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 0794F3A6C02 for <siprec@ietf.org>; Fri, 11 Mar 2011 06:07:42 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3702576; Fri, 11 Mar 2011 15:08:53 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id C30091EB82B4; Fri, 11 Mar 2011 15:08:53 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 11 Mar 2011 15:08:54 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Fri, 11 Mar 2011 15:08:51 +0100
Thread-Topic: [siprec] Metadata Re-Sync
Thread-Index: Acvc8lpQxyhCWt3yTti4MV/+Ro9AGgDAjXuA
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B61CEF059@MCHP058A.global-ad.net>
References: <101C6067BEC68246B0C3F6843BCCC1E30B61A90122@MCHP058A.global-ad.net> <4D751E7D.3060003@cisco.com>
In-Reply-To: <4D751E7D.3060003@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Metadata Re-Sync
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Mar 2011 14:07:44 -0000

Hi Paul,

Thanks for sharing your thoughts on this.

I think we are thinking along the same lines I think a snapshot relates to =
the state at the moment in time it is asked for and would not want the SRC =
to have to remember any metadata from the past that is not relevant to the =
current state of the CS or CS's.

So it if fine for the SRC to have to remember the ID's for things like the =
CS Groups as long as these relate to currently active CS groups and not som=
e historical information.=20

I don't think the SRC should have to reset the ID's just because of a SRS a=
sks for a snapshot this might be problematic if for example the SRC was sen=
ding the metadata to multiple SRS.

Regards
Andy
=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: 07 March 2011 18:06
> To: siprec@ietf.org
> Subject: Re: [siprec] Metadata Re-Sync
>=20
> Andrew,
>=20
> Its pretty important to get this right, and there are=20
> subtleties to it.
>=20
> IMO we must make the assumption that the SRC retains a minimum of=20
> historical information. It is shipping data to the SRS so=20
> that it *can*=20
> forget about it. So when there is a need for the SRC to do a=20
> "snapshot",=20
> what that really means is to send what it still knows, possibly=20
> including "some" stuff that it remembers. There is a likelihood that=20
> stuff will get lost in this process.
>=20
> For the mechanisms we are currently discussing, the SRC is=20
> assigning IDs=20
> to things in order that it can refer back to them later. For=20
> instance,=20
> IDs for CSs, CS-groups, media-sessions, participants, etc. We are=20
> currently expecting these to be dynamically assigned UUIDs.
>=20
> Hence, if the SRC establishes a CS and a CS-group, each will have an=20
> associated ID, and the message that says the CS is a member of the=20
> CS-group will contain both IDs.
>=20
> Clearly if the SRC wants to retain the option of adding=20
> additional CSs=20
> to a CS-group it will need to remember the ID of the CS-group. It can=20
> forget this when there is no longer any need to reference it.
>=20
> If asked to send a snapshot, the SRC will hopefully remember=20
> the IDs for=20
> the CSs that are still active. And it will probably remember=20
> the IDs of=20
> the CS-groups those CSs were assigned to. (I'm not certain if that is=20
> necessary.)
>=20
> But it might not retain much metadata info about those things=20
> that was=20
> sent in the past. It might just remember "I have CS-group IDs=20
> for these=20
> CSs". When sending a "snapshot" it might just be sending metadata=20
> describing current state of active sessions with reference to IDs=20
> created in the past. If the SRS did not get or properly process the=20
> metadata that first defined those IDs it might not be able to=20
> properly=20
> process the new snapshot.
>=20
> An alternative is that when asked for a "snapshot" the SRC might=20
> intentially forget all the old IDs it had. Instead it could=20
> start "from=20
> scratch" assigning new IDs to everything it currently knows=20
> about, and=20
> sending metadata definitions of those, even if those=20
> definitions lack a=20
> lot of desirable information. The advantage is that there is=20
> no reliance=20
> on anything sent previously, and so corruption issues are minimized.
>=20
> Obviously this is a bit difficult to discuss in the abstract,=20
> since it=20
> is tied pretty tightly to specific implementation approaches.
>=20
> Nothing is cast in stone here. So we can discuss pro/cons of=20
> different=20
> approaches.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/7/2011 11:40 AM, Hutton, Andrew wrote:
> > Hi All,
> > I have a couple of questions/observations regarding the issue of a
> > re-sync of metadata between the SRC and SRS.
> > The current draft (draft-portman-siprec-protocol-03) section 6.3.1.
> > talks about the SRS requesting a metadata snapshot and by snapshot I
> > assume we mean what is in the metadata model at the moment=20
> in time that
> > the snapshot is created. I am therefore assuming there is=20
> no requirement
> > for the SRC to hold on to any historical information about=20
> for example
> > past participants in a CS. Therefore when we talk about a the SRS
> > requesting a re-sync what it is actually asking for is a current
> > snapshot. Do people agree on that ?
> > Also give that a RS (Recording Session) can relate to many=20
> CS's then to
> > make the re-sync manageable it might be a good idea if the SRS could
> > request a snapshot for a given CS.
> > It would therefore probably make sense to separate the metadata for
> > different CS's even when it is carried in the same RS. So=20
> would it be
> > sensible to split the metadata for each CS in to different bodies in
> > whatever SIP Request we agree will carry the metadata.
> > Regards
> > Andy
> >
> >
> >
> > _______________________________________________
> > 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
> =

From pkyzivat@cisco.com  Fri Mar 11 06:20:50 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A10553A6C28 for <siprec@core3.amsl.com>; Fri, 11 Mar 2011 06:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level: 
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jKoXDo1+JMyZ for <siprec@core3.amsl.com>; Fri, 11 Mar 2011 06:20:48 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 95FE03A6C27 for <siprec@ietf.org>; Fri, 11 Mar 2011 06:20:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=5490; q=dns/txt; s=iport; t=1299853328; x=1301062928; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=o5rAegKN9LiHqEtukVd63Ilh2DQze8SHxmlnbcJaW5U=; b=YKqar8hrjAdu7ZiaZJy+WNFdXGgVsevIc2r9GXdTMKr394yxBqvjnuVN pCZhbWqatQbylLmoiXpvj99sYBRpaH+t4BoZFRNMC3OTXLlk0kdskLINB 1GpWe0oUY4J/GNoo5ZH2fWodyhyG8ObHELxnHHmBV8aRrS+6RpoqlW745 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKW+eU2tJV2d/2dsb2JhbACmMHelQpwxhWIEhSmHJoNK
X-IronPort-AV: E=Sophos;i="4.62,303,1297036800"; d="scan'208";a="224425374"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rtp-iport-1.cisco.com with ESMTP; 11 Mar 2011 14:22:06 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id p2BEM61O002278;  Fri, 11 Mar 2011 14:22:06 GMT
Message-ID: <4D7A300D.9030500@cisco.com>
Date: Fri, 11 Mar 2011 09:22:05 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
References: <101C6067BEC68246B0C3F6843BCCC1E30B61A90122@MCHP058A.global-ad.net> <4D751E7D.3060003@cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61CEF059@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E30B61CEF059@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Metadata Re-Sync
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Mar 2011 14:20:50 -0000

Andy - I agree that it sounds like we are mostly in agreement. The devil 
is in the details. But its better to have some agreement on direction 
before investing further effort in the details.

	Thanks,
	Paul

On 3/11/2011 9:08 AM, Hutton, Andrew wrote:
> Hi Paul,
>
> Thanks for sharing your thoughts on this.
>
> I think we are thinking along the same lines I think a snapshot relates to the state at the moment in time it is asked for and would not want the SRC to have to remember any metadata from the past that is not relevant to the current state of the CS or CS's.
>
> So it if fine for the SRC to have to remember the ID's for things like the CS Groups as long as these relate to currently active CS groups and not some historical information.
>
> I don't think the SRC should have to reset the ID's just because of a SRS asks for a snapshot this might be problematic if for example the SRC was sending the metadata to multiple SRS.
>
> Regards
> Andy
>
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org
>> [mailto:siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat
>> Sent: 07 March 2011 18:06
>> To: siprec@ietf.org
>> Subject: Re: [siprec] Metadata Re-Sync
>>
>> Andrew,
>>
>> Its pretty important to get this right, and there are
>> subtleties to it.
>>
>> IMO we must make the assumption that the SRC retains a minimum of
>> historical information. It is shipping data to the SRS so
>> that it *can*
>> forget about it. So when there is a need for the SRC to do a
>> "snapshot",
>> what that really means is to send what it still knows, possibly
>> including "some" stuff that it remembers. There is a likelihood that
>> stuff will get lost in this process.
>>
>> For the mechanisms we are currently discussing, the SRC is
>> assigning IDs
>> to things in order that it can refer back to them later. For
>> instance,
>> IDs for CSs, CS-groups, media-sessions, participants, etc. We are
>> currently expecting these to be dynamically assigned UUIDs.
>>
>> Hence, if the SRC establishes a CS and a CS-group, each will have an
>> associated ID, and the message that says the CS is a member of the
>> CS-group will contain both IDs.
>>
>> Clearly if the SRC wants to retain the option of adding
>> additional CSs
>> to a CS-group it will need to remember the ID of the CS-group. It can
>> forget this when there is no longer any need to reference it.
>>
>> If asked to send a snapshot, the SRC will hopefully remember
>> the IDs for
>> the CSs that are still active. And it will probably remember
>> the IDs of
>> the CS-groups those CSs were assigned to. (I'm not certain if that is
>> necessary.)
>>
>> But it might not retain much metadata info about those things
>> that was
>> sent in the past. It might just remember "I have CS-group IDs
>> for these
>> CSs". When sending a "snapshot" it might just be sending metadata
>> describing current state of active sessions with reference to IDs
>> created in the past. If the SRS did not get or properly process the
>> metadata that first defined those IDs it might not be able to
>> properly
>> process the new snapshot.
>>
>> An alternative is that when asked for a "snapshot" the SRC might
>> intentially forget all the old IDs it had. Instead it could
>> start "from
>> scratch" assigning new IDs to everything it currently knows
>> about, and
>> sending metadata definitions of those, even if those
>> definitions lack a
>> lot of desirable information. The advantage is that there is
>> no reliance
>> on anything sent previously, and so corruption issues are minimized.
>>
>> Obviously this is a bit difficult to discuss in the abstract,
>> since it
>> is tied pretty tightly to specific implementation approaches.
>>
>> Nothing is cast in stone here. So we can discuss pro/cons of
>> different
>> approaches.
>>
>> 	Thanks,
>> 	Paul
>>
>> On 3/7/2011 11:40 AM, Hutton, Andrew wrote:
>>> Hi All,
>>> I have a couple of questions/observations regarding the issue of a
>>> re-sync of metadata between the SRC and SRS.
>>> The current draft (draft-portman-siprec-protocol-03) section 6.3.1.
>>> talks about the SRS requesting a metadata snapshot and by snapshot I
>>> assume we mean what is in the metadata model at the moment
>> in time that
>>> the snapshot is created. I am therefore assuming there is
>> no requirement
>>> for the SRC to hold on to any historical information about
>> for example
>>> past participants in a CS. Therefore when we talk about a the SRS
>>> requesting a re-sync what it is actually asking for is a current
>>> snapshot. Do people agree on that ?
>>> Also give that a RS (Recording Session) can relate to many
>> CS's then to
>>> make the re-sync manageable it might be a good idea if the SRS could
>>> request a snapshot for a given CS.
>>> It would therefore probably make sense to separate the metadata for
>>> different CS's even when it is carried in the same RS. So
>> would it be
>>> sensible to split the metadata for each CS in to different bodies in
>>> whatever SIP Request we agree will carry the metadata.
>>> Regards
>>> Andy
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>

From john.elwell@siemens-enterprise.com  Fri Mar 11 06:48:15 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 440AA3A69D8 for <siprec@core3.amsl.com>; Fri, 11 Mar 2011 06:48:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.315
X-Spam-Level: 
X-Spam-Status: No, score=-102.315 tagged_above=-999 required=5 tests=[AWL=-0.316, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KzL2CD66vhoF for <siprec@core3.amsl.com>; Fri, 11 Mar 2011 06:48:11 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id A30443A6948 for <siprec@ietf.org>; Fri, 11 Mar 2011 06:48:08 -0800 (PST)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3703584; Fri, 11 Mar 2011 15:49:27 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 9B9B423F02A0; Fri, 11 Mar 2011 15:49:15 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 11 Mar 2011 15:49:15 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Fri, 11 Mar 2011 15:49:14 +0100
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCA=
Message-ID: <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com>
Keywords: SIPREC
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Mar 2011 14:48:15 -0000

Partha,

I read -01 and have the following comments:

1. In section 3:
"The media related details of metadata SHALL be passed across using
   session description protocol (SDP) [RFC4566].  SDP attributes
   describes about different media formats like audio, video."
I wonder whether it is really appropriate to describe SDP attributes as par=
t of the metadata. If I look at the metadata model, I don't see any attribu=
tes of a Media Stream object that could be satisfied using RS SDP. For exam=
ple, the "codec parameters" attribute relates to the CS, not the RS - the t=
wo sessions could use different codecs or different codec parameters. I thi=
nk it would be far simpler to regard all metadata as being sent in XML. Not=
e that the SDP label attribute can still be used as the linkage between a M=
edia Stream object in the metadata and the corresponding RS media stream th=
at captures the CS media stream concerned.

2. We perhaps need to think about mixed RS media streams, i.e., where sever=
al CS media streams have been mixed to produce a single RS media stream. In=
 this case, the several Media Stream objects would all point to the same SD=
P label, I guess. This then brings into question the mode element (type str=
eamMode) - why is this needed? The fact that several Media Stream objects (=
stream elements) point to the same label would imply there has been mixing,=
 so the mode element seems to be redundant.

3. Section 4.2.4:
"Each group MAY have initiator entity attribute which contains SIP/
   SIPS URI to identify the device which acts as Session Recording
   Client (SRC).  The entity attribute SIP/SIPS URI FQDN or IP address
   represents the device and may not have user part."
It is unclear to me why a URI identifying the SRC should be an attribute of=
 a group element. I cannot find a corresponding attribute in the CS Group o=
bject in the metadata model draft.

4. The example (section 5.1) seems rather odd, in that the recording-metada=
ta element appears to comprise a sequence of elements (recording, group, se=
ssion, etc.) alternating with extensiondata elements, i.e., there is an ext=
ensiondata element after each of the other elements. This probably complies=
 with the schema, but what is the meaning of several extensiondata elements=
 all within the same recording-metadata element? Why not just a single exte=
nsiondata element? Is any significance to be drawn from the fact that there=
 is an extensiondata element following the recording element, another follo=
wing the group element, etc.?

5. On the other hand, elements group, session, etc. seem to lack extensiond=
ata elements - would it not be sensible to allow each of these to be extens=
ible?

6. The method of sending partial metadata seems to imply that when a sessio=
n, participant, stream etc. comes to an end, we send partial metadata indic=
ating that the element concerned now has an end time. This seems implicitly=
 to mean that the element ceases to exist - correct? So if the SRS were to =
request a snapshot of complete metadata, it would not receive any elements =
for which a stop time has previously been sent - correct? I don't think I h=
ave an issue with this - I just wanted to confirm my understanding.

John (as individual)


> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 08 March 2011 14:24
> To: siprec@ietf.org
> Subject: [siprec] Review Request for=20
> draft-ram-siprec-metadata-format-01
>=20
> Hi all,
>=20
> As per the mailing list comments and interim meeting discussion, I
> updated -01 draft of draft-ram-siprec-metadata-format and send it for
> review. The draft is available at
> http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt. The
> following update are done as part of -01 draft:
>=20
> 1) URN UUID (RFC 4122) mechanism is used as the unique id=20
> mechanism for
> relevant XML elements like group, session, stream, participant.=20
>=20
> 2) Partial XML passing in RS is supported by having unique=20
> URN UUID for
> group, session, stream, participant, recording, extension=20
> data which are
> directly under recording-metadata container/namespace.=20
>=20
> 3) Include recording-metadata element as a container element=20
> instead of
> recording element. This helps in avoiding duplicate data of recording
> elements during the partial update
>=20
> 4) Updated elements in XML document as per=20
> draft-ram-siprec-metadata-04
> elements & associations
>=20
> 5) Changed appdata element name as extensiondata
>=20
> 6) Removed container element like sessions, participants, streams from
> XML document as  parent reference exists in each element
>=20
> 7) Added Partial Update example & SIP usage XML+SDP example
>=20
> 8) Portion of security considerations section is added.
>=20
> Could you please review and provide your expert comments on the draft.
>=20
> Thanks
> Partha=20
>=20
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
> Sent: Tuesday, March 08, 2011 7:31 PM
> To: Parthasarathi R (partr)
> Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> Subject: New Version Notification for
> draft-ram-siprec-metadata-format-01=20
>=20
>=20
> A new version of I-D, draft-ram-siprec-metadata-format-01.txt has been
> successfully submitted by Parthasarathi R and posted to the IETF
> repository.
>=20
> Filename:	 draft-ram-siprec-metadata-format
> Revision:	 01
> Title:		 Session Initiation Protocol (SIP)=20
> Recording Metadata
> Format
> Creation_date:	 2011-03-08
> WG ID:		 Independent Submission
> Number_of_pages: 20
>=20
> Abstract:
> 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=20
> session is
> typically performed by sending a copy of a media stream to a recording
> device.  The requirements for which are described in
> [I-D.ietf-siprec-req], the architecture for which is described in
> [I-D.ietf-siprec-architecture], and the metadata model viewed=20
> by Session
> Recording Server is described in [I-D.ram-siprec-metadata].
> This document focuses on the Recording metadata format which describes
> the communication session.
> =20
>=20
>=20
>=20
> The IETF Secretariat.
>=20
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From pkyzivat@cisco.com  Fri Mar 11 10:22:05 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79E063A6946 for <siprec@core3.amsl.com>; Fri, 11 Mar 2011 10:22:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.54
X-Spam-Level: 
X-Spam-Status: No, score=-110.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cShbvc4A86yf for <siprec@core3.amsl.com>; Fri, 11 Mar 2011 10:22:02 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id F29EC3A6930 for <siprec@ietf.org>; Fri, 11 Mar 2011 10:22:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=1883; q=dns/txt; s=iport; t=1299867801; x=1301077401; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=d7KNSm4+ZapfzsdqPWJN+W7goU5denI1bya+yf6vOAQ=; b=J2yKmypo4c6ZvJA9VeM1hmp+PZlVqxGM1ygTcBtWugH7dng6aq8WLXNA +8ifddhZq/XWznhySNyVInSJ50Qf8Ufffcwl8+bPsgiVNwUuWVJlnhoV4 3k81SnFlw6kxGt3J0fQqj3bG/0vBf9OY9JIyoT1dfRyZ/ata60iJgs7I4 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtwGABb3eU2tJXHB/2dsb2JhbACZJI0Od6YOnCCFYgSFKYcmg0o
X-IronPort-AV: E=Sophos;i="4.62,304,1297036800"; d="scan'208";a="274869812"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by sj-iport-4.cisco.com with ESMTP; 11 Mar 2011 18:23:21 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id p2BINKm8027778 for <siprec@ietf.org>; Fri, 11 Mar 2011 18:23:21 GMT
Message-ID: <4D7A6898.1060809@cisco.com>
Date: Fri, 11 Mar 2011 13:23:20 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: siprec@ietf.org
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Mar 2011 18:22:05 -0000

On 3/11/2011 9:49 AM, Elwell, John wrote:
> Partha,
>
> I read -01 and have the following comments:
>
> 1. In section 3:
> "The media related details of metadata SHALL be passed across using
>     session description protocol (SDP) [RFC4566].  SDP attributes
>     describes about different media formats like audio, video."
> I wonder whether it is really appropriate to describe SDP attributes as part of the metadata. If I look at the metadata model, I don't see any attributes of a Media Stream object that could be satisfied using RS SDP. For example, the "codec parameters" attribute relates to the CS, not the RS - the two sessions could use different codecs or different codec parameters. I think it would be far simpler to regard all metadata as being sent in XML. Note that the SDP label attribute can still be used as the linkage between a Media Stream object in the metadata and the corresponding RS media stream that captures the CS media stream concerned.

I think I agree with you here.
The label reference in the xml, and the label in the sdp provide a 
linkage between the *meta*data and the *data*. Originally I was thinking 
that there would be some things in the sdp that were metadata, but so 
far that seems not to be true.

> 2. We perhaps need to think about mixed RS media streams, i.e., where several CS media streams have been mixed to produce a single RS media stream. In this case, the several Media Stream objects would all point to the same SDP label, I guess. This then brings into question the mode element (type streamMode) - why is this needed? The fact that several Media Stream objects (stream elements) point to the same label would imply there has been mixing, so the mode element seems to be redundant.

My thinking is that situation is modeled as a single media stream with 
multiple participants.

	Thanks,
	Paul

From partr@cisco.com  Sat Mar 12 09:48:52 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 487E23A6A1C for <siprec@core3.amsl.com>; Sat, 12 Mar 2011 09:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.435
X-Spam-Level: 
X-Spam-Status: No, score=-9.435 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h0BBdPHMMjRS for <siprec@core3.amsl.com>; Sat, 12 Mar 2011 09:48:50 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 0BE103A6A1A for <siprec@ietf.org>; Sat, 12 Mar 2011 09:48:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=7967; q=dns/txt; s=iport; t=1299952211; x=1301161811; h=mime-version:subject:date:message-id:references:from:to; bh=RuUC/u9I2HOcajGWY676A0tVQO+Vc7fDY9yJUDxVJXY=; b=eTuKS2WpK62zadtjA3hjHxYQcfLRtUEDC4PZmFgWjsx0eVZY9xJSLCd2 t5WDbHbkxs6dPwG9YXPdoen/KX4W1cizJKd7u6/oPCNkJ4Ls3FExR+PtE gq1x1TpqdUfuVyDCMAlT7nIVLifWXdeiEmVSFrofQxFqedc30Q6HLlfKx I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtQEAOVAe02Q/khNgWdsb2JhbAClalkUAQEWJiWkLptVhWIEhSmKfQ
X-IronPort-AV: E=Sophos;i="4.62,308,1297036800"; d="scan'208,217";a="78892841"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 12 Mar 2011 17:50:10 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2CHo9eW015906 for <siprec@ietf.org>; Sat, 12 Mar 2011 17:50:09 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 12 Mar 2011 23:20:09 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE0DD.EDB16A28"
Date: Sat, 12 Mar 2011 23:20:09 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A699@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvgGXSFwN7kntbSThSxDvrHQp54ZQAwj423
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <4D7A6898.1060809@cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 12 Mar 2011 17:50:09.0235 (UTC) FILETIME=[EDCEFA30:01CBE0DD]
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 12 Mar 2011 17:48:52 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE0DD.EDB16A28
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John/Paul,
=20
Please read inline.
=20
Thanks
Partha

________________________________

From: siprec-bounces@ietf.org on behalf of Paul Kyzivat (pkyzivat)
Sent: Fri 3/11/2011 11:53 PM
To: siprec@ietf.org
Subject: Re: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01





On 3/11/2011 9:49 AM, Elwell, John wrote:
> Partha,
>
> I read -01 and have the following comments:
>
> 1. In section 3:
> "The media related details of metadata SHALL be passed across using
>     session description protocol (SDP) [RFC4566].  SDP attributes
>     describes about different media formats like audio, video."
> I wonder whether it is really appropriate to describe SDP attributes =
as part of the metadata. If I look at the metadata model, I don't see =
any attributes of a Media Stream object that could be satisfied using RS =
SDP. For example, the "codec parameters" attribute relates to the CS, =
not the RS - the two sessions could use different codecs or different =
codec parameters. I think it would be far simpler to regard all metadata =
as being sent in XML. Note that the SDP label attribute can still be =
used as the linkage between a Media Stream object in the metadata and =
the corresponding RS media stream that captures the CS media stream =
concerned.

I think I agree with you here.
The label reference in the xml, and the label in the sdp provide a
linkage between the *meta*data and the *data*. Originally I was thinking
that there would be some things in the sdp that were metadata, but so
far that seems not to be true.

<Partha> I agree with the linkage part and CS codec parameters =
information in the model.  IMO, some of the information shall be =
retrieved from RS SDP=20

1) Media Type (Audio/Video)

2) In a unmixed stream, grouping of direction attribute in RS helps to =
understand that CS is in hold during the given time. =20

BTW, these information is possible to be passed in stream extension data =
but I thought that reusing the existing SDP framework may be preferred. =
I'm not very sure at this moment whether removing this text is =
appropriate. In case everyone feels that it is *data* and not =
*metadata*, I'll remove this sentence in the next revision. </Partha>

> 2. We perhaps need to think about mixed RS media streams, i.e., where =
several CS media streams have been mixed to produce a single RS media =
stream. In this case, the several Media Stream objects would all point =
to the same SDP label, I guess. This then brings into question the mode =
element (type streamMode) - why is this needed? The fact that several =
Media Stream objects (stream elements) point to the same label would =
imply there has been mixing, so the mode element seems to be redundant.

My thinking is that situation is modeled as a single media stream with
multiple participants.

        Thanks,
        Paul
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec



------_=_NextPart_001_01CBE0DD.EDB16A28
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText97039>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 =
face=3DArial>John/Paul,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Please read =
inline.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> siprec-bounces@ietf.org on =
behalf of Paul Kyzivat (pkyzivat)<BR><B>Sent:</B> Fri 3/11/2011 11:53 =
PM<BR><B>To:</B> siprec@ietf.org<BR><B>Subject:</B> Re: [siprec] Review =
Request for draft-ram-siprec-metadata-format-01<BR></FONT><BR></DIV>=0A=
<DIV><BR><BR>=0A=
<P><FONT size=3D2>On 3/11/2011 9:49 AM, Elwell, John wrote:<BR>&gt; =
Partha,<BR>&gt;<BR>&gt; I read -01 and have the following =
comments:<BR>&gt;<BR>&gt; 1. In section 3:<BR>&gt; "The media related =
details of metadata SHALL be passed across =
using<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; session description protocol (SDP) =
[RFC4566].&nbsp; SDP attributes<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
describes about different media formats like audio, video."<BR>&gt; I =
wonder whether it is really appropriate to describe SDP attributes as =
part of the metadata. </FONT><FONT size=3D2>If I look at the metadata =
model, I don't see any attributes of a Media Stream object that could be =
satisfied using RS SDP. For example, the "codec parameters" attribute =
relates to the CS, not the RS - the two sessions could use different =
codecs or different codec parameters. I think it would be far simpler to =
regard all metadata as being sent in XML. Note that the SDP label =
attribute can still be used as the linkage between a Media Stream object =
in the metadata and the corresponding RS media stream that captures the =
CS media stream concerned.<BR><BR>I think I agree with you here.<BR>The =
label reference in the xml, and the label in the sdp provide =
a<BR>linkage between the *meta*data and the *data*. Originally I was =
thinking<BR>that there would be some things in the sdp that were =
metadata, but so<BR>far that seems not to be true.</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt;&nbsp;I agree with the linkage part and =
CS codec parameters information in the model.&nbsp;</FONT><FONT =
size=3D2>&nbsp;IMO, some of the information shall be retrieved from RS =
SDP </FONT></P>=0A=
<P><FONT size=3D2>1) Media Type (Audio/Video)</FONT></P>=0A=
<P><FONT size=3D2>2)&nbsp;</FONT><FONT size=3D2>In a unmixed stream, =
grouping of direction attribute&nbsp;in RS helps to understand that CS =
is in hold during the given time.&nbsp; </FONT></P>=0A=
<P><FONT size=3D2>BTW, these information is possible to be passed in =
stream extension data but I thought that reusing the existing SDP =
framework may be preferred. I</FONT><FONT size=3D2>'m not very sure at =
this moment whether removing this text is appropriate. In case everyone =
feels that it is *data* and not *metadata*, I'll remove this sentence in =
the next revision. &lt;/Partha&gt;<BR><BR>&gt; 2. We perhaps need to =
think about mixed RS media streams, i.e., where several CS media streams =
have been mixed to produce a single RS media stream. In this case, the =
several Media Stream objects would all point to the same SDP label, I =
guess. This then brings into question the mode element (type streamMode) =
- why is this needed? The fact that several Media Stream objects (stream =
elements) point to the same label would imply there has been mixing, so =
the mode element seems to be redundant.<BR><BR>My thinking is that =
situation is modeled as a single media stream with<BR>multiple =
participants.</FONT><FONT =
size=3D2><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Thanks,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Paul<BR>_______________________________________________<BR>siprec =
mailing list<BR>siprec@ietf.org<BR><A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR></P></FONT></DIV></BODY></HTML>
------_=_NextPart_001_01CBE0DD.EDB16A28--

From partr@cisco.com  Sat Mar 12 10:23:02 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0264F3A6A28 for <siprec@core3.amsl.com>; Sat, 12 Mar 2011 10:23:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.122
X-Spam-Level: 
X-Spam-Status: No, score=-9.122 tagged_above=-999 required=5 tests=[AWL=-0.520, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XhyrX23B31-u for <siprec@core3.amsl.com>; Sat, 12 Mar 2011 10:22:59 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id EFC053A67F9 for <siprec@ietf.org>; Sat, 12 Mar 2011 10:22:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=20218; q=dns/txt; s=iport; t=1299954261; x=1301163861; h=mime-version:subject:date:message-id:references:from:to; bh=Cmku3qqR5TlWkmPJNoD+tna9cXMaNEwJJON0s3xCXGs=; b=BI3WMPMHAC/EWH+YpXlmTuhsHIgLRz1dZqMypY/iANwxHVKaMUhgxu09 64rYit9EVBy1aq7np0ASX00wjwHJy22H2F7SLPLoXKJvGd3ZzwixC4bsa LKakyWC7LAkxKB55SuT/6+ep2QwlopK4QJqyKOxOtUY6J6otjE/2Ke6pF Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBAIZJe02Q/khNgWdsb2JhbACYdox0WRQBARYmJaRhm1KCexsBgksEhSmKfQ
X-IronPort-AV: E=Sophos;i="4.62,308,1297036800"; d="scan'208,217";a="21448129"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 12 Mar 2011 18:24:05 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2CIO1KT020625; Sat, 12 Mar 2011 18:24:03 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 12 Mar 2011 23:54:01 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE0E2.A90E7677"
Date: Sat, 12 Mar 2011 23:54:01 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCAAP1pCbA==
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 12 Mar 2011 18:24:01.0672 (UTC) FILETIME=[A93C4080:01CBE0E2]
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 12 Mar 2011 18:23:02 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE0E2.A90E7677
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John,
=20
Thanks for the detailed comments. Please read inline.
=20
Thanks
Partha

________________________________

From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
Sent: Fri 3/11/2011 8:19 PM
To: Parthasarathi R (partr); siprec@ietf.org
Subject: RE: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01



Partha,

I read -01 and have the following comments:

1. In section 3:
"The media related details of metadata SHALL be passed across using
   session description protocol (SDP) [RFC4566].  SDP attributes
   describes about different media formats like audio, video."
I wonder whether it is really appropriate to describe SDP attributes as =
part of the metadata. If I look at the metadata model, I don't see any =
attributes of a Media Stream object that could be satisfied using RS =
SDP. For example, the "codec parameters" attribute relates to the CS, =
not the RS - the two sessions could use different codecs or different =
codec parameters. I think it would be far simpler to regard all metadata =
as being sent in XML. Note that the SDP label attribute can still be =
used as the linkage between a Media Stream object in the metadata and =
the corresponding RS media stream that captures the CS media stream =
concerned.

2. We perhaps need to think about mixed RS media streams, i.e., where =
several CS media streams have been mixed to produce a single RS media =
stream. In this case, the several Media Stream objects would all point =
to the same SDP label, I guess. This then brings into question the mode =
element (type streamMode) - why is this needed? The fact that several =
Media Stream objects (stream elements) point to the same label would =
imply there has been mixing, so the mode element seems to be redundant.

3. Section 4.2.4:
"Each group MAY have initiator entity attribute which contains SIP/
   SIPS URI to identify the device which acts as Session Recording
   Client (SRC).  The entity attribute SIP/SIPS URI FQDN or IP address
   represents the device and may not have user part."
It is unclear to me why a URI identifying the SRC should be an attribute =
of a group element. I cannot find a corresponding attribute in the CS =
Group object in the metadata model draft.

<Partha> It is a good point. I missed to remove after our last interim =
meeting discussion. I'll remove in the next revision as there is no =
strong request for initiator of the session </Partha>=20

4. The example (section 5.1) seems rather odd, in that the =
recording-metadata element appears to comprise a sequence of elements =
(recording, group, session, etc.) alternating with extensiondata =
elements, i.e., there is an extensiondata element after each of the =
other elements. This probably complies with the schema, but what is the =
meaning of several extensiondata elements all within the same =
recording-metadata element?=20

<Partha> Each extensiondata has its own id and different parent id. =
Parent id shall be of recording, group, session etc., It is possible for =
each extension data to have different extended namespace which is =
specific to its parent.  But it is possible to uniquely identify within =
recording-metadata as it has its own unique id. </Partha>

Why not just a single extensiondata element?=20

<Partha> It may not be preferred because it is tough to arrange =
extension data for a particular stream within the extension data of =
group. The individual extension data also provides flexibility to pass =
the specific extension-data during partial update in case other =
extension data is not modified. </Partha>

Is any significance to be drawn from the fact that there is an =
extensiondata element following the recording element, another following =
the group element, etc.?

<Partha> As mentioned earlier, group mechanism may passed in group =
extensiondata  whereas retention policy of a specific session will be =
passed in session, recording extension data will have common attribute =
like os login shall be passed. It provides more flexibility and it is =
optional element, so it is required to pass whenever applicable only =
</Partha>

5. On the other hand, elements group, session, etc. seem to lack =
extensiondata elements - would it not be sensible to allow each of these =
to be extensible?

<Partha> Parent-id in extension data helps to link group, session to =
specific extension data </partha>

6. The method of sending partial metadata seems to imply that when a =
session, participant, stream etc. comes to an end, we send partial =
metadata indicating that the element concerned now has an end time. This =
seems implicitly to mean that the element ceases to exist - correct? So =
if the SRS were to request a snapshot of complete metadata, it would not =
receive any elements for which a stop time has previously been sent - =
correct?

<Partha> Your understanding is correct, end-time will not passed across =
in case of SRS request for complete metadata as SRC may have lost the =
state</Partha>

 I don't think I have an issue with this - I just wanted to confirm my =
understanding.

John (as individual)


> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 08 March 2011 14:24
> To: siprec@ietf.org
> Subject: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
> Hi all,
>
> As per the mailing list comments and interim meeting discussion, I
> updated -01 draft of draft-ram-siprec-metadata-format and send it for
> review. The draft is available at
> http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt. The
> following update are done as part of -01 draft:
>
> 1) URN UUID (RFC 4122) mechanism is used as the unique id
> mechanism for
> relevant XML elements like group, session, stream, participant.
>
> 2) Partial XML passing in RS is supported by having unique
> URN UUID for
> group, session, stream, participant, recording, extension
> data which are
> directly under recording-metadata container/namespace.
>
> 3) Include recording-metadata element as a container element
> instead of
> recording element. This helps in avoiding duplicate data of recording
> elements during the partial update
>
> 4) Updated elements in XML document as per
> draft-ram-siprec-metadata-04
> elements & associations
>
> 5) Changed appdata element name as extensiondata
>
> 6) Removed container element like sessions, participants, streams from
> XML document as  parent reference exists in each element
>
> 7) Added Partial Update example & SIP usage XML+SDP example
>
> 8) Portion of security considerations section is added.
>
> Could you please review and provide your expert comments on the draft.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: Tuesday, March 08, 2011 7:31 PM
> To: Parthasarathi R (partr)
> Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> Subject: New Version Notification for
> draft-ram-siprec-metadata-format-01
>
>
> A new version of I-D, draft-ram-siprec-metadata-format-01.txt has been
> successfully submitted by Parthasarathi R and posted to the IETF
> repository.
>
> Filename:      draft-ram-siprec-metadata-format
> Revision:      01
> Title:                 Session Initiation Protocol (SIP)
> Recording Metadata
> Format
> Creation_date:         2011-03-08
> WG ID:                 Independent Submission
> Number_of_pages: 20
>
> Abstract:
> 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.  The requirements for which are described in
> [I-D.ietf-siprec-req], the architecture for which is described in
> [I-D.ietf-siprec-architecture], and the metadata model viewed
> by Session
> Recording Server is described in [I-D.ram-siprec-metadata].
> This document focuses on the Recording metadata format which describes
> the communication session.
>=20
>
>
>
> The IETF Secretariat.
>
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>



------_=_NextPart_001_01CBE0E2.A90E7677
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText3363>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 =
face=3DArial>John,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks for the detailed =
comments. Please read inline.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> Elwell, John =
[mailto:john.elwell@siemens-enterprise.com]<BR><B>Sent:</B> Fri =
3/11/2011 8:19 PM<BR><B>To:</B> Parthasarathi R (partr); =
siprec@ietf.org<BR><B>Subject:</B> RE: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Partha,<BR><BR>I read -01 and have the following =
comments:<BR><BR>1. In section 3:<BR>"The media related details of =
metadata SHALL be passed across using<BR>&nbsp;&nbsp; session =
description protocol (SDP) [RFC4566].&nbsp; SDP =
attributes<BR>&nbsp;&nbsp; describes about different media formats like =
audio, video."<BR>I wonder whether it is really appropriate to describe =
SDP attributes as part of the metadata. If I look at the metadata model, =
I don't see any attributes of a Media Stream object that could be =
satisfied using RS SDP. For example, the "codec parameters" attribute =
relates to the CS, not the RS - the two sessions could use different =
codecs or different codec parameters. I think it would be far simpler to =
regard all metadata as being sent in XML. Note that the SDP label =
attribute can still be used as the linkage between a Media Stream object =
in the metadata and the corresponding RS media stream that captures the =
CS media stream concerned.<BR><BR>2. We perhaps need to think about =
mixed RS media streams, i.e., where several CS media streams have been =
mixed to produce a single RS media stream. In this case, the several =
Media Stream objects would all point to the same SDP label, I guess. =
This then brings into question the mode element (type streamMode) - why =
is this needed? The fact that several Media Stream objects (stream =
elements) point to the same label would imply there has been mixing, so =
the mode element seems to be redundant.<BR><BR>3. Section =
4.2.4:<BR>"Each group MAY have initiator entity attribute which contains =
SIP/<BR>&nbsp;&nbsp; SIPS URI to identify the device which acts as =
Session Recording<BR>&nbsp;&nbsp; Client (SRC).&nbsp; The entity =
attribute SIP/SIPS URI FQDN or IP address<BR>&nbsp;&nbsp; represents the =
device and may not have user part."<BR>It is unclear to me why a URI =
identifying the SRC should be an attribute of a group element. I cannot =
find a corresponding attribute in the CS Group object in the metadata =
model draft.</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; It is a good point. I missed =
to&nbsp;remove after our last interim meeting discussion. I'll remove in =
the next revision as&nbsp;there is no strong request for initiator of =
the session &lt;/Partha&gt;</FONT><FONT size=3D2>&nbsp;<BR><BR>4. The =
example (section 5.1) seems rather odd, in that the recording-metadata =
element appears to comprise a sequence of elements (recording, group, =
session, etc.) alternating with extensiondata elements, i.e., there is =
an extensiondata element after each of the other elements. This probably =
complies with the schema, but what is the meaning of several =
extensiondata elements all within the same recording-metadata element? =
</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; Each extensiondata has its own id and =
different parent id. Parent id shall be of recording, group, session =
etc.,&nbsp;It is possible for each extension data to have different =
extended namespace which is specific to its parent. &nbsp;But it is =
possible to uniquely identify within recording-metadata as it has its =
own unique id. &lt;/Partha&gt;</FONT></P>=0A=
<P><FONT size=3D2>Why not just a single extensiondata element? =
</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; It may not be preferred because it is =
tough to arrange extension data for a particular stream within the =
extension data of group. The individual extension data also provides =
flexibility to pass the specific extension-data during partial update in =
case other extension data is not modified. &lt;/Partha&gt;</FONT></P>=0A=
<P><FONT size=3D2>Is any significance to be drawn from the fact that =
there is an extensiondata element following the recording element, =
another following the group element, etc.?</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; As mentioned earlier, group =
mechanism&nbsp;may passed in group extensiondata &nbsp;whereas retention =
policy of a specific session will be passed in session, recording =
extension data will have common attribute like os login shall be passed. =
It provides more flexibility and it is optional element, so it is =
required to pass whenever applicable only&nbsp;&lt;/Partha&gt;<BR><BR>5. =
On the other hand, elements group, session, etc. seem to lack =
extensiondata elements - would it not be sensible to allow each of these =
to be extensible?</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; Parent-id in&nbsp;extension =
data&nbsp;helps to link group, session to specific extension data =
&lt;/partha&gt;<BR><BR>6. The method of sending partial metadata seems =
to imply that when a session, participant, stream etc. comes to an end, =
we send partial metadata indicating that the element concerned now has =
an end time. This seems implicitly to mean that the element ceases to =
exist - correct? So if the SRS were to request a snapshot of complete =
metadata, it would not receive any elements for which a stop time has =
previously been sent - correct?</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; Your understanding is correct, end-time =
will not passed across in case of SRS request for complete metadata as =
SRC may have lost the state&lt;/Partha&gt;</FONT></P>=0A=
<P><FONT size=3D2>&nbsp;I don't think I have an issue with =
thi</FONT><FONT size=3D2>s - I just wanted to confirm my =
understanding.<BR><BR>John (as individual)<BR><BR><BR>&gt; -----Original =
Message-----<BR>&gt; From: siprec-bounces@ietf.org<BR>&gt; [<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>] On Behalf Of Parthasarathi R (partr)<BR>&gt; Sent: 08 March 2011 =
14:24<BR>&gt; To: siprec@ietf.org<BR>&gt; Subject: [siprec] Review =
Request for<BR>&gt; draft-ram-siprec-metadata-format-01<BR>&gt;<BR>&gt; =
Hi all,<BR>&gt;<BR>&gt; As per the mailing list comments and interim =
meeting discussion, I<BR>&gt; updated -01 draft of =
draft-ram-siprec-metadata-format and send it for<BR>&gt; review. The =
draft is available at<BR>&gt; <A =
href=3D"http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt">h=
ttp://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt</A>. =
The<BR>&gt; following update are done as part of -01 =
draft:<BR>&gt;<BR>&gt; 1) URN UUID (RFC 4122) mechanism is used as the =
unique id<BR>&gt; mechanism for<BR>&gt; relevant XML elements like =
group, session, stream, participant.<BR>&gt;<BR>&gt; 2) Partial XML =
passing in RS is supported by having unique<BR>&gt; URN UUID for<BR>&gt; =
group, session, stream, participant, recording, extension<BR>&gt; data =
which are<BR>&gt; directly under recording-metadata =
container/namespace.<BR>&gt;<BR>&gt; 3) Include recording-metadata =
element as a container element<BR>&gt; instead of<BR>&gt; recording =
element. This helps in avoiding duplicate data of recording<BR>&gt; =
elements during the partial update<BR>&gt;<BR>&gt; 4) Updated elements =
in XML document as per<BR>&gt; draft-ram-siprec-metadata-04<BR>&gt; =
elements &amp; associations<BR>&gt;<BR>&gt; 5) Changed appdata element =
name as extensiondata<BR>&gt;<BR>&gt; 6) Removed container element like =
sessions, participants, streams from<BR>&gt; XML document as&nbsp; =
parent reference exists in each element<BR>&gt;<BR>&gt; 7) Added Partial =
Update example &amp; SIP usage XML+SDP example<BR>&gt;<BR>&gt; 8) =
Portion of security considerations section is added.<BR>&gt;<BR>&gt; =
Could you please review and provide your expert comments on the =
draft.<BR>&gt;<BR>&gt; Thanks<BR>&gt; Partha<BR>&gt;<BR>&gt; =
-----Original Message-----<BR>&gt; From: IETF I-D Submission Tool [<A =
href=3D"mailto:idsubmission@ietf.org">mailto:idsubmission@ietf.org</A>]<B=
R>&gt; Sent: Tuesday, March 08, 2011 7:31 PM<BR>&gt; To: Parthasarathi R =
(partr)<BR>&gt; Cc: Ram Mohan R (rmohanr); Paul Kyzivat =
(pkyzivat)<BR>&gt; Subject: New Version Notification for<BR>&gt; =
draft-ram-siprec-metadata-format-01<BR>&gt;<BR>&gt;<BR>&gt; A new =
version of I-D, draft-ram-siprec-metadata-format-01.txt has been<BR>&gt; =
successfully submitted by Parthasarathi R and posted to the IETF<BR>&gt; =
repository.<BR>&gt;<BR>&gt; Filename:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-ram-siprec-metadata-format<BR>&gt; =
Revision:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 01<BR>&gt; =
Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Session Initiation =
Protocol (SIP)<BR>&gt; Recording Metadata<BR>&gt; Format<BR>&gt; =
Creation_date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2011-03-08<BR>&gt; WG ID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Independent =
Submission<BR>&gt; Number_of_pages: 20<BR>&gt;<BR>&gt; Abstract:<BR>&gt; =
Session recording is a critical requirement in many =
communications<BR>&gt; environments such as call centers and financial =
trading.&nbsp; In some of<BR>&gt; these environments, all calls must be =
recorded for regulatory,<BR>&gt; compliance, and consumer protection =
reasons.&nbsp; Recording of a<BR>&gt; session is<BR>&gt; typically =
performed by sending a copy of a media stream to a recording<BR>&gt; =
device.&nbsp; The requirements for which are described in<BR>&gt; =
[I-D.ietf-siprec-req], the architecture for which is described =
in<BR>&gt; [I-D.ietf-siprec-architecture], and the metadata model =
viewed<BR>&gt; by Session<BR>&gt; Recording Server is described in =
[I-D.ram-siprec-metadata].<BR>&gt; This document focuses on the =
Recording metadata format which describes<BR>&gt; the communication =
session.<BR>&gt;&nbsp;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; The IETF =
Secretariat.<BR>&gt;<BR>&gt;<BR>&gt; =
_______________________________________________<BR>&gt; siprec mailing =
list<BR>&gt; siprec@ietf.org<BR>&gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR>&gt;<BR></P></FONT></DIV></BODY></HTML>
------_=_NextPart_001_01CBE0E2.A90E7677--

From pkyzivat@cisco.com  Sat Mar 12 11:52:34 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FB393A6994 for <siprec@core3.amsl.com>; Sat, 12 Mar 2011 11:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ldT+60IdaMRE for <siprec@core3.amsl.com>; Sat, 12 Mar 2011 11:52:27 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id BAB763A690B for <siprec@ietf.org>; Sat, 12 Mar 2011 11:52:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=1097; q=dns/txt; s=iport; t=1299959629; x=1301169229; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=9gOOKwyE6SjsrM6b2wd7jB87ZR0JaIIeGygnGwkNkGY=; b=lmQfga2uO5dOpRuBvnz3g/9PjxDvjyToGUv/lnaAF2axZeK1v2fxNKpL vP5H6gxUM4rSlQIKKTJ8V6DJ3vtUxnAa5SkW4rRK9/gTckXXygu3z/lvB d6XSL2HDm0RuXabuLNKC6edNHZcCUsAU8OgmmksbAC80J/hKvfLpMehhG c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArkGAHNde02tJV2d/2dsb2JhbACZNY0Od6Q/m0WFYgSFK4cng04
X-IronPort-AV: E=Sophos;i="4.62,308,1297036800"; d="scan'208";a="225100924"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rtp-iport-2.cisco.com with ESMTP; 12 Mar 2011 19:53:48 +0000
Received: from [10.86.255.158] ([10.86.255.158]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id p2CJrlBE023391 for <siprec@ietf.org>; Sat, 12 Mar 2011 19:53:47 GMT
Message-ID: <4D7BCF4B.2090205@cisco.com>
Date: Sat, 12 Mar 2011 14:53:47 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: siprec@ietf.org
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com>	<A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 12 Mar 2011 19:52:34 -0000

On 3/12/2011 1:24 PM, Parthasarathi R (partr) wrote:

> 6. The method of sending partial metadata seems to imply that when a
> session, participant, stream etc. comes to an end, we send partial
> metadata indicating that the element concerned now has an end time. This
> seems implicitly to mean that the element ceases to exist - correct? So
> if the SRS were to request a snapshot of complete metadata, it would not
> receive any elements for which a stop time has previously been sent -
> correct?
>
> <Partha> Your understanding is correct, end-time will not passed across
> in case of SRS request for complete metadata as SRC may have lost the
> state</Partha>

The element doesn't cease to exist. None of the elements ever cease to 
exist. They are simply historic. But its likely that the SRC ceases to 
remember it, and hence won't mention it if a snapshot is subsequently 
requested.

However, if it *did* happen to remember it, it *could* subsequently send 
some additional data to associate with it. (But in this case that seems 
unlikely.)

	Thanks,
	Paul

From john.elwell@siemens-enterprise.com  Sun Mar 13 03:39:53 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 400343A6B32 for <siprec@core3.amsl.com>; Sun, 13 Mar 2011 03:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.31
X-Spam-Level: 
X-Spam-Status: No, score=-102.31 tagged_above=-999 required=5 tests=[AWL=-0.311, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sk-Xt2oktUxQ for <siprec@core3.amsl.com>; Sun, 13 Mar 2011 03:39:51 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id C0AC23A6B14 for <siprec@ietf.org>; Sun, 13 Mar 2011 03:39:50 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3721155; Sun, 13 Mar 2011 11:41:10 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id C0ED923F0278; Sun, 13 Mar 2011 11:41:09 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Sun, 13 Mar 2011 11:41:10 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Sun, 13 Mar 2011 11:41:07 +0100
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCAAP1pCbAAiRDpg
Message-ID: <A444A0F8084434499206E78C106220CA086A89AE9E@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 13 Mar 2011 10:39:53 -0000

So let's see if I understand correctly. Element extensionData occurs in rec=
ording-metadata, as part of the sequence that also contains things like ses=
sion, participant, stream. The element has attributes 'id' and 'parent' for=
 linking the extension data to other elements.

Is this correct? I am not sure I understand the reasons for doing it this w=
ay, but it seems it should work.

Some specific comments:

1. The schema shows 'id' and 'session' as the attributes of extensionData -=
 I assume 'session' should be 'parent'.

2. Element extensionData also occurs in element participant for some reason=
, according to the scheme. Is this also an error?

3. In 4.2.2:
"recording-metadata element has recording, group, session, stream
   elements."
Participant seems to be missing (present in the example and in the scheme).

4. The group element is missing from the schema (present in the 4.2.2 and i=
n the example).

John (as individual)
=20

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]=20
> Sent: 12 March 2011 18:24
> To: Elwell, John; siprec@ietf.org
> Subject: RE: [siprec] Review Request for=20
> draft-ram-siprec-metadata-format-01
>=20
> John,
> =20
> Thanks for the detailed comments. Please read inline.
> =20
> Thanks
> Partha
>=20
> ________________________________
>=20
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Fri 3/11/2011 8:19 PM
> To: Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] Review Request for=20
> draft-ram-siprec-metadata-format-01
>=20
>=20
>=20
> Partha,
>=20
> I read -01 and have the following comments:
>=20
> 1. In section 3:
> "The media related details of metadata SHALL be passed across using
>    session description protocol (SDP) [RFC4566].  SDP attributes
>    describes about different media formats like audio, video."
> I wonder whether it is really appropriate to describe SDP=20
> attributes as part of the metadata. If I look at the metadata=20
> model, I don't see any attributes of a Media Stream object=20
> that could be satisfied using RS SDP. For example, the "codec=20
> parameters" attribute relates to the CS, not the RS - the two=20
> sessions could use different codecs or different codec=20
> parameters. I think it would be far simpler to regard all=20
> metadata as being sent in XML. Note that the SDP label=20
> attribute can still be used as the linkage between a Media=20
> Stream object in the metadata and the corresponding RS media=20
> stream that captures the CS media stream concerned.
>=20
> 2. We perhaps need to think about mixed RS media streams,=20
> i.e., where several CS media streams have been mixed to=20
> produce a single RS media stream. In this case, the several=20
> Media Stream objects would all point to the same SDP label, I=20
> guess. This then brings into question the mode element (type=20
> streamMode) - why is this needed? The fact that several Media=20
> Stream objects (stream elements) point to the same label=20
> would imply there has been mixing, so the mode element seems=20
> to be redundant.
>=20
> 3. Section 4.2.4:
> "Each group MAY have initiator entity attribute which contains SIP/
>    SIPS URI to identify the device which acts as Session Recording
>    Client (SRC).  The entity attribute SIP/SIPS URI FQDN or IP address
>    represents the device and may not have user part."
> It is unclear to me why a URI identifying the SRC should be=20
> an attribute of a group element. I cannot find a=20
> corresponding attribute in the CS Group object in the=20
> metadata model draft.
>=20
> <Partha> It is a good point. I missed to remove after our=20
> last interim meeting discussion. I'll remove in the next=20
> revision as there is no strong request for initiator of the=20
> session </Partha>=20
>=20
> 4. The example (section 5.1) seems rather odd, in that the=20
> recording-metadata element appears to comprise a sequence of=20
> elements (recording, group, session, etc.) alternating with=20
> extensiondata elements, i.e., there is an extensiondata=20
> element after each of the other elements. This probably=20
> complies with the schema, but what is the meaning of several=20
> extensiondata elements all within the same recording-metadata=20
> element?=20
>=20
> <Partha> Each extensiondata has its own id and different=20
> parent id. Parent id shall be of recording, group, session=20
> etc., It is possible for each extension data to have=20
> different extended namespace which is specific to its parent.=20
>  But it is possible to uniquely identify within=20
> recording-metadata as it has its own unique id. </Partha>
>=20
> Why not just a single extensiondata element?=20
>=20
> <Partha> It may not be preferred because it is tough to=20
> arrange extension data for a particular stream within the=20
> extension data of group. The individual extension data also=20
> provides flexibility to pass the specific extension-data=20
> during partial update in case other extension data is not=20
> modified. </Partha>
>=20
> Is any significance to be drawn from the fact that there is=20
> an extensiondata element following the recording element,=20
> another following the group element, etc.?
>=20
> <Partha> As mentioned earlier, group mechanism may passed in=20
> group extensiondata  whereas retention policy of a specific=20
> session will be passed in session, recording extension data=20
> will have common attribute like os login shall be passed. It=20
> provides more flexibility and it is optional element, so it=20
> is required to pass whenever applicable only </Partha>
>=20
> 5. On the other hand, elements group, session, etc. seem to=20
> lack extensiondata elements - would it not be sensible to=20
> allow each of these to be extensible?
>=20
> <Partha> Parent-id in extension data helps to link group,=20
> session to specific extension data </partha>
>=20
> 6. The method of sending partial metadata seems to imply that=20
> when a session, participant, stream etc. comes to an end, we=20
> send partial metadata indicating that the element concerned=20
> now has an end time. This seems implicitly to mean that the=20
> element ceases to exist - correct? So if the SRS were to=20
> request a snapshot of complete metadata, it would not receive=20
> any elements for which a stop time has previously been sent - correct?
>=20
> <Partha> Your understanding is correct, end-time will not=20
> passed across in case of SRS request for complete metadata as=20
> SRC may have lost the state</Partha>
>=20
>  I don't think I have an issue with this - I just wanted to=20
> confirm my understanding.
>=20
> John (as individual)
>=20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi=20
> R (partr)
> > Sent: 08 March 2011 14:24
> > To: siprec@ietf.org
> > Subject: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > Hi all,
> >
> > As per the mailing list comments and interim meeting discussion, I
> > updated -01 draft of draft-ram-siprec-metadata-format and=20
> send it for
> > review. The draft is available at
> > http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt. The
> > following update are done as part of -01 draft:
> >
> > 1) URN UUID (RFC 4122) mechanism is used as the unique id
> > mechanism for
> > relevant XML elements like group, session, stream, participant.
> >
> > 2) Partial XML passing in RS is supported by having unique
> > URN UUID for
> > group, session, stream, participant, recording, extension
> > data which are
> > directly under recording-metadata container/namespace.
> >
> > 3) Include recording-metadata element as a container element
> > instead of
> > recording element. This helps in avoiding duplicate data of=20
> recording
> > elements during the partial update
> >
> > 4) Updated elements in XML document as per
> > draft-ram-siprec-metadata-04
> > elements & associations
> >
> > 5) Changed appdata element name as extensiondata
> >
> > 6) Removed container element like sessions, participants,=20
> streams from
> > XML document as  parent reference exists in each element
> >
> > 7) Added Partial Update example & SIP usage XML+SDP example
> >
> > 8) Portion of security considerations section is added.
> >
> > Could you please review and provide your expert comments on=20
> the draft.
> >
> > Thanks
> > Partha
> >
> > -----Original Message-----
> > From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> > Sent: Tuesday, March 08, 2011 7:31 PM
> > To: Parthasarathi R (partr)
> > Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > Subject: New Version Notification for
> > draft-ram-siprec-metadata-format-01
> >
> >
> > A new version of I-D,=20
> draft-ram-siprec-metadata-format-01.txt has been
> > successfully submitted by Parthasarathi R and posted to the IETF
> > repository.
> >
> > Filename:      draft-ram-siprec-metadata-format
> > Revision:      01
> > Title:                 Session Initiation Protocol (SIP)
> > Recording Metadata
> > Format
> > Creation_date:         2011-03-08
> > WG ID:                 Independent Submission
> > Number_of_pages: 20
> >
> > Abstract:
> > 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=20
> a recording
> > device.  The requirements for which are described in
> > [I-D.ietf-siprec-req], the architecture for which is described in
> > [I-D.ietf-siprec-architecture], and the metadata model viewed
> > by Session
> > Recording Server is described in [I-D.ram-siprec-metadata].
> > This document focuses on the Recording metadata format=20
> which describes
> > the communication session.
> >=20
> >
> >
> >
> > The IETF Secretariat.
> >
> >
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >
>=20
>=20
> =

From partr@cisco.com  Sun Mar 13 07:14:06 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F396C3A68F0 for <siprec@core3.amsl.com>; Sun, 13 Mar 2011 07:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.096
X-Spam-Level: 
X-Spam-Status: No, score=-9.096 tagged_above=-999 required=5 tests=[AWL=-0.494, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djmpvUINrizF for <siprec@core3.amsl.com>; Sun, 13 Mar 2011 07:14:03 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 128973A6835 for <siprec@ietf.org>; Sun, 13 Mar 2011 07:14:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=33292; q=dns/txt; s=iport; t=1300025724; x=1301235324; h=mime-version:subject:date:message-id:references:from:to; bh=OOg1EYekIKhQUkB343O+f3DHMgZN3om4qLNNIP/cdBg=; b=WgojlXDdAUBlRxgV2FQu1xz1fcHLQRJRP1TTGqjCGPzK0jmiS3KXRjzF lkRImZkOG8yBe7sH9GgkBRt0VxfXVk2HFzN6D5vTNY3aLPxlamBt9EULj qyDcoIRwwQS1lWg/0zulC0l4YITT9ccxdqWyXfJBesF49kehh8etkfc1z E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUAAMttfE2Q/khLgWdsb2JhbACYcox0WhQBARYmJaN/mmiCexsBgksEhSmKfQ
X-IronPort-AV: E=Sophos;i="4.62,311,1297036800"; d="scan'208,217";a="78941688"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 13 Mar 2011 14:15:23 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2DEFMEx011072; Sun, 13 Mar 2011 14:15:22 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 13 Mar 2011 19:45:21 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE189.1676AC01"
Date: Sun, 13 Mar 2011 19:45:21 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A69B@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCAAP1pCbAAiRDpgAAbozsA=
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AE9E@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 13 Mar 2011 14:15:21.0846 (UTC) FILETIME=[16BD3960:01CBE189]
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 13 Mar 2011 14:14:06 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE189.1676AC01
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John,
=20
Thanks for  further review of the draft and specific comments on XML. =
Please read inline.
=20
Thanks
Partha

________________________________

From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
Sent: Sun 3/13/2011 4:11 PM
To: Parthasarathi R (partr); siprec@ietf.org
Subject: RE: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01



So let's see if I understand correctly. Element extensionData occurs in =
recording-metadata, as part of the sequence that also contains things =
like session, participant, stream. The element has attributes 'id' and =
'parent' for linking the extension data to other elements.

Is this correct?

<Partha> Yeah, it is correct </partha>

 I am not sure I understand the reasons for doing it this way, but it =
seems it should work.

<Partha> Recording metadata is the main container of rs-metadata+xml and =
it is the only one element which MUST be passed in both Complete/Partial =
Metadata XML document. All other metadata block (like stream, session, =
participant, extension data) in the model shall be passed independently =
from SRC and then, SRS will be able to correlate based on the "id". The =
linkage is done so that the hierarchical blocks of metadata model will =
be represented using the "id" relationship in XML document which avoids =
extra namespace during partial XML update. This design logic is applied =
in the following elements:  group, session, stream, participant, =
extensiondata as well. This proposed mechanism allows to update only =
extensiondata alone as well if required. The relationship of element & =
parent element in metadata XML document is as follows:

    Element                           -             parent id name

----------------------------------------------------------------

   group                                -             recording

   session                           -              group

   participant                       -              session

   stream                             -              session

   extensiondata                -              parent

</Partha>
Some specific comments:

1. The schema shows 'id' and 'session' as the attributes of =
extensionData - I assume 'session' should be 'parent'.
2. Element extensionData also occurs in element participant for some =
reason, according to the scheme. Is this also an error?
3. In 4.2.2:
"recording-metadata element has recording, group, session, stream
   elements."
Participant seems to be missing (present in the example and in the =
scheme).

<Partha> Thanks for pointing these error. I'll update the text in the =
next revision </Partha>

4. The group element is missing from the schema (present in the 4.2.2 =
and in the example).

<Partha> Group element is present in Sec 6 of schema.

</xs:complexType>
   <xs:complexType name=3D"group">
       <xs:sequence>
           <xs:element name=3D"initiator" type=3D"xs:anyURI"
            minOccurs=3D"0" maxOccurs=3D"1"/>  =3D=3D=3D=3D> Will be =
removed in the next revision as per below mail discussion=20
         <xs:element name=3D"start-time" type=3D"xs:dateTime"
                minOccurs=3D"0"/>
         <xs:element name=3D"stop-time" type=3D"xs:dateTime"
                minOccurs=3D"0"/>
       </xs:sequence>
       <xs:attribute name=3D"id" type=3D"xs:urnuuid"
            use"required"/>
       <xs:attribute name=3D"recording" type=3D"xs:urnuuid"
            use"required"/>
   </xs:complexType>=20

Please let me know in case any other change has to be done in the group =
element schema=20

</Partha>
John (as individual)

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com =
<mailto:partr@cisco.com> ]
> Sent: 12 March 2011 18:24
> To: Elwell, John; siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
> John,
>=20
> Thanks for the detailed comments. Please read inline.
>=20
> Thanks
> Partha
>
> ________________________________
>
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com =
<mailto:john.elwell@siemens-enterprise.com> ]
> Sent: Fri 3/11/2011 8:19 PM
> To: Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
>
>
> Partha,
>
> I read -01 and have the following comments:
>
> 1. In section 3:
> "The media related details of metadata SHALL be passed across using
>    session description protocol (SDP) [RFC4566].  SDP attributes
>    describes about different media formats like audio, video."
> I wonder whether it is really appropriate to describe SDP
> attributes as part of the metadata. If I look at the metadata
> model, I don't see any attributes of a Media Stream object
> that could be satisfied using RS SDP. For example, the "codec
> parameters" attribute relates to the CS, not the RS - the two
> sessions could use different codecs or different codec
> parameters. I think it would be far simpler to regard all
> metadata as being sent in XML. Note that the SDP label
> attribute can still be used as the linkage between a Media
> Stream object in the metadata and the corresponding RS media
> stream that captures the CS media stream concerned.
>
> 2. We perhaps need to think about mixed RS media streams,
> i.e., where several CS media streams have been mixed to
> produce a single RS media stream. In this case, the several
> Media Stream objects would all point to the same SDP label, I
> guess. This then brings into question the mode element (type
> streamMode) - why is this needed? The fact that several Media
> Stream objects (stream elements) point to the same label
> would imply there has been mixing, so the mode element seems
> to be redundant.
>
> 3. Section 4.2.4:
> "Each group MAY have initiator entity attribute which contains SIP/
>    SIPS URI to identify the device which acts as Session Recording
>    Client (SRC).  The entity attribute SIP/SIPS URI FQDN or IP address
>    represents the device and may not have user part."
> It is unclear to me why a URI identifying the SRC should be
> an attribute of a group element. I cannot find a
> corresponding attribute in the CS Group object in the
> metadata model draft.
>
> <Partha> It is a good point. I missed to remove after our
> last interim meeting discussion. I'll remove in the next
> revision as there is no strong request for initiator of the
> session </Partha>
>
> 4. The example (section 5.1) seems rather odd, in that the
> recording-metadata element appears to comprise a sequence of
> elements (recording, group, session, etc.) alternating with
> extensiondata elements, i.e., there is an extensiondata
> element after each of the other elements. This probably
> complies with the schema, but what is the meaning of several
> extensiondata elements all within the same recording-metadata
> element?
>
> <Partha> Each extensiondata has its own id and different
> parent id. Parent id shall be of recording, group, session
> etc., It is possible for each extension data to have
> different extended namespace which is specific to its parent.
>  But it is possible to uniquely identify within
> recording-metadata as it has its own unique id. </Partha>
>
> Why not just a single extensiondata element?
>
> <Partha> It may not be preferred because it is tough to
> arrange extension data for a particular stream within the
> extension data of group. The individual extension data also
> provides flexibility to pass the specific extension-data
> during partial update in case other extension data is not
> modified. </Partha>
>
> Is any significance to be drawn from the fact that there is
> an extensiondata element following the recording element,
> another following the group element, etc.?
>
> <Partha> As mentioned earlier, group mechanism may passed in
> group extensiondata  whereas retention policy of a specific
> session will be passed in session, recording extension data
> will have common attribute like os login shall be passed. It
> provides more flexibility and it is optional element, so it
> is required to pass whenever applicable only </Partha>
>
> 5. On the other hand, elements group, session, etc. seem to
> lack extensiondata elements - would it not be sensible to
> allow each of these to be extensible?
>
> <Partha> Parent-id in extension data helps to link group,
> session to specific extension data </partha>
>
> 6. The method of sending partial metadata seems to imply that
> when a session, participant, stream etc. comes to an end, we
> send partial metadata indicating that the element concerned
> now has an end time. This seems implicitly to mean that the
> element ceases to exist - correct? So if the SRS were to
> request a snapshot of complete metadata, it would not receive
> any elements for which a stop time has previously been sent - correct?
>
> <Partha> Your understanding is correct, end-time will not
> passed across in case of SRS request for complete metadata as
> SRC may have lost the state</Partha>
>
>  I don't think I have an issue with this - I just wanted to
> confirm my understanding.
>
> John (as individual)
>
>
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org <mailto:siprec-bounces@ietf.org> ] =
On Behalf Of Parthasarathi
> R (partr)
> > Sent: 08 March 2011 14:24
> > To: siprec@ietf.org
> > Subject: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > Hi all,
> >
> > As per the mailing list comments and interim meeting discussion, I
> > updated -01 draft of draft-ram-siprec-metadata-format and
> send it for
> > review. The draft is available at
> > http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt =
<http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt> . The
> > following update are done as part of -01 draft:
> >
> > 1) URN UUID (RFC 4122) mechanism is used as the unique id
> > mechanism for
> > relevant XML elements like group, session, stream, participant.
> >
> > 2) Partial XML passing in RS is supported by having unique
> > URN UUID for
> > group, session, stream, participant, recording, extension
> > data which are
> > directly under recording-metadata container/namespace.
> >
> > 3) Include recording-metadata element as a container element
> > instead of
> > recording element. This helps in avoiding duplicate data of
> recording
> > elements during the partial update
> >
> > 4) Updated elements in XML document as per
> > draft-ram-siprec-metadata-04
> > elements & associations
> >
> > 5) Changed appdata element name as extensiondata
> >
> > 6) Removed container element like sessions, participants,
> streams from
> > XML document as  parent reference exists in each element
> >
> > 7) Added Partial Update example & SIP usage XML+SDP example
> >
> > 8) Portion of security considerations section is added.
> >
> > Could you please review and provide your expert comments on
> the draft.
> >
> > Thanks
> > Partha
> >
> > -----Original Message-----
> > From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org =
<mailto:idsubmission@ietf.org> ]
> > Sent: Tuesday, March 08, 2011 7:31 PM
> > To: Parthasarathi R (partr)
> > Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > Subject: New Version Notification for
> > draft-ram-siprec-metadata-format-01
> >
> >
> > A new version of I-D,
> draft-ram-siprec-metadata-format-01.txt has been
> > successfully submitted by Parthasarathi R and posted to the IETF
> > repository.
> >
> > Filename:      draft-ram-siprec-metadata-format
> > Revision:      01
> > Title:                 Session Initiation Protocol (SIP)
> > Recording Metadata
> > Format
> > Creation_date:         2011-03-08
> > WG ID:                 Independent Submission
> > Number_of_pages: 20
> >
> > Abstract:
> > 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.  The requirements for which are described in
> > [I-D.ietf-siprec-req], the architecture for which is described in
> > [I-D.ietf-siprec-architecture], and the metadata model viewed
> > by Session
> > Recording Server is described in [I-D.ram-siprec-metadata].
> > This document focuses on the Recording metadata format
> which describes
> > the communication session.
> >
> >
> >
> >
> > The IETF Secretariat.
> >
> >
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec =
<https://www.ietf.org/mailman/listinfo/siprec>=20
> >
>
>
>



------_=_NextPart_001_01CBE189.1676AC01
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText39867>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText39867>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 =
face=3DArial>John,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks for&nbsp; further =
review of the draft and specific comments on XML. Please read =
inline.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> Elwell, John =
[mailto:john.elwell@siemens-enterprise.com]<BR><B>Sent:</B> Sun =
3/13/2011 4:11 PM<BR><B>To:</B> Parthasarathi R (partr); =
siprec@ietf.org<BR><B>Subject:</B> RE: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>So let's see if I understand correctly. Element =
extensionData occurs in recording-metadata, as part of the sequence that =
also contains things like session, participant, stream. The element has =
attributes 'id' and 'parent' for linking the extension data to other =
elements.<BR><BR>Is this correct?</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; Yeah, it is =
correct&nbsp;&lt;/partha&gt;</FONT></P>=0A=
<P><FONT size=3D2>&nbsp;I am not sure I understand the reasons for doing =
it this way, but it seems it should work.</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; Recording metadata is the main =
container of rs-metadata+xml&nbsp;and it&nbsp;is the only one element =
which MUST be passed in both Complete/Partial Metadata =
XML&nbsp;document. All other metadata block (like stream, session, =
participant, extension data)&nbsp;in the model shall be passed =
independently from SRC and then, SRS will be able to correlate based on =
the "id". The linkage is done so that =
the&nbsp;hierarchical&nbsp;blocks&nbsp;of&nbsp;metadata&nbsp;model&nbsp;w=
ill be represented&nbsp;using the "id"&nbsp;relationship&nbsp;in XML =
document&nbsp;which avoids extra namespace&nbsp;during partial XML =
update. This design&nbsp;logic&nbsp;is applied in the following =
elements:&nbsp; group, session, stream, participant, extensiondata as =
well. This proposed mechanism allows to update only extensiondata alone =
as well if required.&nbsp;The relationship of element &amp; parent =
element in&nbsp;metadata XML document&nbsp;is as follows:</FONT></P>=0A=
<P><FONT size=3D2>&nbsp;&nbsp;&nbsp; =
Element&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; =
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 parent id name</FONT></P>=0A=
<P><FONT =
size=3D2>----------------------------------------------------------------=
</FONT></P>=0A=
<P><FONT =
size=3D2>&nbsp;&nbsp;&nbsp;group&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; =
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;recording</FONT></P>=0A=
<P><FONT size=3D2>&nbsp;&nbsp; =
session&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; &nbsp;&nbsp;&nbsp; group</FONT></P>=0A=
<P><FONT size=3D2>&nbsp;&nbsp; =
participant&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; session</FONT></P>=0A=
<P><FONT size=3D2>&nbsp;&nbsp; =
stream&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
session</FONT></P>=0A=
<P><FONT size=3D2>&nbsp;&nbsp; =
extensiondata&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
parent</FONT></P>=0A=
<P><FONT size=3D2>&lt;/Partha&gt;<BR>Some specific comments:<BR><BR>1. =
The schema shows 'id' and 'session' as the attributes of extensionData - =
I assume 'session' should be 'parent'.</FONT><FONT size=3D2><BR>2. =
Element extensionData also occurs in element participant for some =
reason, according to the scheme. Is this also an error?</FONT><FONT =
size=3D2><BR>3. In 4.2.2:<BR>"recording-metadata element has recording, =
group, session, stream<BR>&nbsp;&nbsp; elements."<BR>Participant seems =
to be missing (present in the example and in the scheme).</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; Thanks for pointing these error. I'll =
update&nbsp;the text in the next revision &lt;/Partha&gt;<BR><BR>4. The =
group element is missing from the schema (present in the 4.2.2 and in =
the example).</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; Group element is present in&nbsp;Sec 6 =
of&nbsp;schema.</FONT></P>=0A=
<P><FONT size=3D2>&lt;/xs:complexType&gt;<BR>&nbsp;&nbsp; =
&lt;xs:complexType =
name=3D"group"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; &lt;xs:element name=3D"initiator" =
type=3D"xs:anyURI"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; minOccurs=3D"0" maxOccurs=3D"1"/&gt;&nbsp; =
=3D=3D=3D=3D&gt; Will be removed in the next revision&nbsp;as per below =
mail discussion <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element name=3D"start-time" =
type=3D"xs:dateTime"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
minOccurs=3D"0"/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element name=3D"stop-time" =
type=3D"xs:dateTime"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
minOccurs=3D"0"/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;/xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:attribute name=3D"id" =
type=3D"xs:urnuuid"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; =
use"required"/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:attribute name=3D"recording" =
type=3D"xs:urnuuid"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; use"required"/&gt;<BR>&nbsp;&nbsp; =
&lt;/xs:complexType&gt;&nbsp;</FONT></P>=0A=
<P><FONT size=3D2>Please let me know in case any other change has to be =
done in the group element schema </FONT></P>=0A=
<P><FONT size=3D2>&lt;/Partha&gt;<BR>John (as =
individual)<BR></FONT></FONT><FONT size=3D2><BR>&gt; -----Original =
Message-----<BR>&gt; From: Parthasarathi R (partr) [</FONT><A =
href=3D"mailto:partr@cisco.com"><FONT =
size=3D2>mailto:partr@cisco.com</FONT></A><FONT size=3D2>]<BR>&gt; Sent: =
12 March 2011 18:24<BR>&gt; To: Elwell, John; siprec@ietf.org<BR>&gt; =
Subject: RE: [siprec] Review Request for<BR>&gt; =
draft-ram-siprec-metadata-format-01<BR>&gt;<BR>&gt; =
John,<BR>&gt;&nbsp;<BR>&gt; Thanks for the detailed comments. Please =
read inline.<BR>&gt;&nbsp;<BR>&gt; Thanks<BR>&gt; Partha<BR>&gt;<BR>&gt; =
________________________________<BR>&gt;<BR>&gt; From: Elwell, John =
[</FONT><A href=3D"mailto:john.elwell@siemens-enterprise.com"><FONT =
size=3D2>mailto:john.elwell@siemens-enterprise.com</FONT></A><FONT =
size=3D2>]<BR>&gt; Sent: Fri 3/11/2011 8:19 PM<BR>&gt; To: Parthasarathi =
R (partr); siprec@ietf.org<BR>&gt; Subject: RE: [siprec] Review Request =
for<BR>&gt; =
draft-ram-siprec-metadata-format-01<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; =
Partha,<BR>&gt;<BR>&gt; I read -01 and have the following =
comments:<BR>&gt;<BR>&gt; 1. In section 3:<BR>&gt; "The media related =
details of metadata SHALL be passed across =
using<BR>&gt;&nbsp;&nbsp;&nbsp; session description protocol (SDP) =
[RFC4566].&nbsp; SDP attributes<BR>&gt;&nbsp;&nbsp;&nbsp; describes =
about different media formats like audio, video."<BR>&gt; I wonder =
whether it is really appropriate to describe SDP<BR>&gt; attributes as =
part of the metadata. If I look at the metadata<BR>&gt; model, I don't =
see any attributes of a Media Stream object<BR>&gt; that could be =
satisfied using RS SDP. For example, the "codec<BR>&gt; parameters" =
attribute relates to the CS, not the RS - the two<BR>&gt; sessions could =
use different codecs or different codec<BR>&gt; parameters. I think it =
would be far simpler to regard all<BR>&gt; metadata as being sent in =
XML. Note that the SDP label<BR>&gt; attribute can still be used as the =
linkage between a Media<BR>&gt; Stream object in the metadata and the =
corresponding RS media<BR>&gt; stream that captures the CS media stream =
concerned.<BR>&gt;<BR>&gt; 2. We perhaps need to think about mixed RS =
media streams,<BR>&gt; i.e., where several CS media streams have been =
mixed to<BR>&gt; produce a single RS media stream. In this case, the =
several<BR>&gt; Media Stream objects would all point to the same SDP =
label, I<BR>&gt; guess. This then brings into question the mode element =
(type<BR>&gt; streamMode) - why is this needed? The fact that several =
Media<BR>&gt; Stream objects (stream elements) point to the same =
label<BR>&gt; would imply there has been mixing, so the mode element =
seems<BR>&gt; to be redundant.<BR>&gt;<BR>&gt; 3. Section 4.2.4:<BR>&gt; =
"Each group MAY have initiator entity attribute which contains =
SIP/<BR>&gt;&nbsp;&nbsp;&nbsp; SIPS URI to identify the device which =
acts as Session Recording<BR>&gt;&nbsp;&nbsp;&nbsp; Client (SRC).&nbsp; =
The entity attribute SIP/SIPS URI FQDN or IP =
address<BR>&gt;&nbsp;&nbsp;&nbsp; represents the device and may not have =
user part."<BR>&gt; It is unclear to me why a URI identifying the SRC =
should be<BR>&gt; an attribute of a group element. I cannot find =
a<BR>&gt; corresponding attribute in the CS Group object in the<BR>&gt; =
metadata model draft.<BR>&gt;<BR>&gt; &lt;Partha&gt; It is a good point. =
I missed to remove after our<BR>&gt; last interim meeting discussion. =
I'll remove in the next<BR>&gt; revision as there is no strong request =
for initiator of the<BR>&gt; session &lt;/Partha&gt;<BR>&gt;<BR>&gt; 4. =
The example (section 5.1) seems rather odd, in that the<BR>&gt; =
recording-metadata element appears to comprise a sequence of<BR>&gt; =
elements (recording, group, session, etc.) alternating with<BR>&gt; =
extensiondata elements, i.e., there is an extensiondata<BR>&gt; element =
after each of the other elements. This probably<BR>&gt; complies with =
the schema, but what is the meaning of several<BR>&gt; extensiondata =
elements all within the same recording-metadata<BR>&gt; =
element?<BR>&gt;<BR>&gt; &lt;Partha&gt; Each extensiondata has its own =
id and different<BR>&gt; parent id. Parent id shall be of recording, =
group, session<BR>&gt; etc., It is possible for each extension data to =
have<BR>&gt; different extended namespace which is specific to its =
parent.<BR>&gt;&nbsp; But it is possible to uniquely identify =
within<BR>&gt; recording-metadata as it has its own unique id. =
&lt;/Partha&gt;<BR>&gt;<BR>&gt; Why not just a single extensiondata =
element?<BR>&gt;<BR>&gt; &lt;Partha&gt; It may not be preferred because =
it is tough to<BR>&gt; arrange extension data for a particular stream =
within the<BR>&gt; extension data of group. The individual extension =
data also<BR>&gt; provides flexibility to pass the specific =
extension-data<BR>&gt; during partial update in case other extension =
data is not<BR>&gt; modified. &lt;/Partha&gt;<BR>&gt;<BR>&gt; Is any =
significance to be drawn from the fact that there is<BR>&gt; an =
extensiondata element following the recording element,<BR>&gt; another =
following the group element, etc.?<BR>&gt;<BR>&gt; &lt;Partha&gt; As =
mentioned earlier, group mechanism may passed in<BR>&gt; group =
extensiondata&nbsp; whereas retention policy of a specific<BR>&gt; =
session will be passed in session, recording extension data<BR>&gt; will =
have common attribute like os login shall be passed. It<BR>&gt; provides =
more flexibility and it is optional element, so it<BR>&gt; is required =
to pass whenever applicable only &lt;/Partha&gt;<BR>&gt;<BR>&gt; 5. On =
the other hand, elements group, session, etc. seem to<BR>&gt; lack =
extensiondata elements - would it not be sensible to<BR>&gt; allow each =
of these to be extensible?<BR>&gt;<BR>&gt; &lt;Partha&gt; Parent-id in =
extension data helps to link group,<BR>&gt; session to specific =
extension data &lt;/partha&gt;<BR>&gt;<BR>&gt; 6. The method of sending =
partial metadata seems to imply that<BR>&gt; when a session, =
participant, stream etc. comes to an end, we<BR>&gt; send partial =
metadata indicating that the element concerned<BR>&gt; now has an end =
time. This seems implicitly to mean that the<BR>&gt; element ceases to =
exist - correct? So if the SRS were to<BR>&gt; request a snapshot of =
complete metadata, it would not receive<BR>&gt; any elements for which a =
stop time has previously been sent - correct?<BR>&gt;<BR>&gt; =
&lt;Partha&gt; Your understanding is correct, end-time will not<BR>&gt; =
passed across in case of SRS request for complete metadata as<BR>&gt; =
SRC may have lost the state&lt;/Partha&gt;<BR>&gt;<BR>&gt;&nbsp; I don't =
think I have an issue with this - I just wanted to<BR>&gt; confirm my =
understanding.<BR>&gt;<BR>&gt; John (as =
individual)<BR>&gt;<BR>&gt;<BR>&gt; &gt; -----Original =
Message-----<BR>&gt; &gt; From: siprec-bounces@ietf.org<BR>&gt; &gt; =
[</FONT><A href=3D"mailto:siprec-bounces@ietf.org"><FONT =
size=3D2>mailto:siprec-bounces@ietf.org</FONT></A><FONT size=3D2>] On =
Behalf Of Parthasarathi<BR>&gt; R (partr)<BR>&gt; &gt; Sent: 08 March =
2011 14:24<BR>&gt; &gt; To: siprec@ietf.org<BR>&gt; &gt; Subject: =
[siprec] Review Request for<BR>&gt; &gt; =
draft-ram-siprec-metadata-format-01<BR>&gt; &gt;<BR>&gt; &gt; Hi =
all,<BR>&gt; &gt;<BR>&gt; &gt; As per the mailing list comments and =
interim meeting discussion, I<BR>&gt; &gt; updated -01 draft of =
draft-ram-siprec-metadata-format and<BR>&gt; send it for<BR>&gt; &gt; =
review. The draft is available at<BR>&gt; &gt; </FONT><A =
href=3D"http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt"><=
FONT =
size=3D2>http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt</=
FONT></A><FONT size=3D2>. The<BR>&gt; &gt; following update are done as =
part of -01 draft:<BR>&gt; &gt;<BR>&gt; &gt; 1) URN UUID (RFC 4122) =
mechanism is used as the unique id<BR>&gt; &gt; mechanism for<BR>&gt; =
&gt; relevant XML elements like group, session, stream, =
participant.<BR>&gt; &gt;<BR>&gt; &gt; 2) Partial XML passing in RS is =
supported by having unique<BR>&gt; &gt; URN UUID for<BR>&gt; &gt; group, =
session, stream, participant, recording, extension<BR>&gt; &gt; data =
which are<BR>&gt; &gt; directly under recording-metadata =
container/namespace.<BR>&gt; &gt;<BR>&gt; &gt; 3) Include =
recording-metadata element as a container element<BR>&gt; &gt; instead =
of<BR>&gt; &gt; recording element. This helps in avoiding duplicate data =
of<BR>&gt; recording<BR>&gt; &gt; elements during the partial =
update<BR>&gt; &gt;<BR>&gt; &gt; 4) Updated elements in XML document as =
per<BR>&gt; &gt; draft-ram-siprec-metadata-04<BR>&gt; &gt; elements =
&amp; associations<BR>&gt; &gt;<BR>&gt; &gt; 5) Changed appdata element =
name as extensiondata<BR>&gt; &gt;<BR>&gt; &gt; 6) Removed container =
element like sessions, participants,<BR>&gt; streams from<BR>&gt; &gt; =
XML document as&nbsp; parent reference exists in each element<BR>&gt; =
&gt;<BR>&gt; &gt; 7) Added Partial Update example &amp; SIP usage =
XML+SDP example<BR>&gt; &gt;<BR>&gt; &gt; 8) Portion of security =
considerations section is added.<BR>&gt; &gt;<BR>&gt; &gt; Could you =
please review and provide your expert comments on<BR>&gt; the =
draft.<BR>&gt; &gt;<BR>&gt; &gt; Thanks<BR>&gt; &gt; Partha<BR>&gt; =
&gt;<BR>&gt; &gt; -----Original Message-----<BR>&gt; &gt; From: IETF I-D =
Submission Tool [</FONT><A href=3D"mailto:idsubmission@ietf.org"><FONT =
size=3D2>mailto:idsubmission@ietf.org</FONT></A><FONT size=3D2>]<BR>&gt; =
&gt; Sent: Tuesday, March 08, 2011 7:31 PM<BR>&gt; &gt; To: =
Parthasarathi R (partr)<BR>&gt; &gt; Cc: Ram Mohan R (rmohanr); Paul =
Kyzivat (pkyzivat)<BR>&gt; &gt; Subject: New Version Notification =
for<BR>&gt; &gt; draft-ram-siprec-metadata-format-01<BR>&gt; =
&gt;<BR>&gt; &gt;<BR>&gt; &gt; A new version of I-D,<BR>&gt; =
draft-ram-siprec-metadata-format-01.txt has been<BR>&gt; &gt; =
successfully submitted by Parthasarathi R and posted to the IETF<BR>&gt; =
&gt; repository.<BR>&gt; &gt;<BR>&gt; &gt; =
Filename:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-ram-siprec-metadata-format<BR>&gt; &gt; =
Revision:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 01<BR>&gt; &gt; =
Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Session Initiation Protocol (SIP)<BR>&gt; =
&gt; Recording Metadata<BR>&gt; &gt; Format<BR>&gt; &gt; =
Creation_date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2011-03-08<BR>&gt; &gt; WG =
ID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Independent Submission<BR>&gt; &gt; =
Number_of_pages: 20<BR>&gt; &gt;<BR>&gt; &gt; Abstract:<BR>&gt; &gt; =
Session recording is a critical requirement in many =
communications<BR>&gt; &gt; environments such as call centers and =
financial trading.&nbsp; In some of<BR>&gt; &gt; these environments, all =
calls must be recorded for regulatory,<BR>&gt; &gt; compliance, and =
consumer protection reasons.&nbsp; Recording of a<BR>&gt; &gt; session =
is<BR>&gt; &gt; typically performed by sending a copy of a media stream =
to<BR>&gt; a recording<BR>&gt; &gt; device.&nbsp; The requirements for =
which are described in<BR>&gt; &gt; [I-D.ietf-siprec-req], the =
architecture for which is described in<BR>&gt; &gt; =
[I-D.ietf-siprec-architecture], and the metadata model viewed<BR>&gt; =
&gt; by Session<BR>&gt; &gt; Recording Server is described in =
[I-D.ram-siprec-metadata].<BR>&gt; &gt; This document focuses on the =
Recording metadata format<BR>&gt; which describes<BR>&gt; &gt; the =
communication session.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; =
&gt;<BR>&gt; &gt; The IETF Secretariat.<BR>&gt; &gt;<BR>&gt; =
&gt;<BR>&gt; &gt; =
_______________________________________________<BR>&gt; &gt; siprec =
mailing list<BR>&gt; &gt; siprec@ietf.org<BR>&gt; &gt; </FONT><A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec"><FONT =
size=3D2>https://www.ietf.org/mailman/listinfo/siprec</FONT></A><BR><FONT=
 size=3D2>&gt; =
&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR></P></DIV></DIV></DIV></FONT></BODY></HTM=
L>
------_=_NextPart_001_01CBE189.1676AC01--

From trac+siprec@trac.tools.ietf.org  Sun Mar 13 07:30:18 2011
Return-Path: <trac+siprec@trac.tools.ietf.org>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06B423A68F8 for <siprec@core3.amsl.com>; Sun, 13 Mar 2011 07:30:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyRhALyH3idV for <siprec@core3.amsl.com>; Sun, 13 Mar 2011 07:30:17 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 55CDB3A68F0 for <siprec@ietf.org>; Sun, 13 Mar 2011 07:30:17 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.74) (envelope-from <trac+siprec@trac.tools.ietf.org>) id 1PymKW-0003hS-UY; Sun, 13 Mar 2011 07:31:36 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "siprec issue tracker" <trac+siprec@trac.tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: andrew.hutton@siemens-enterprise.com, leonp@nice.com
X-Trac-Project: siprec
Date: Sun, 13 Mar 2011 14:31:36 -0000
X-URL: http://tools.ietf.org/siprec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/siprec/trac/ticket/67
Message-ID: <055.41afc6aa4e9d73c3c70f40ed82b3ef83@trac.tools.ietf.org>
X-Trac-Ticket-ID: 67
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: andrew.hutton@siemens-enterprise.com, leonp@nice.com, siprec@ietf.org
X-SA-Exim-Mail-From: trac+siprec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: siprec@ietf.org
Subject: [siprec]  #67: Metadata Snapshot  via INFO or Update/ReInvite
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 13 Mar 2011 14:30:18 -0000

#67: Metadata Snapshot  via INFO or Update/ReInvite

 Quoting Ram:

 We will have to see if there is a real need to have the metadata snapshot
 request provided as an INFO  package.  I have not seen a strong use case
 for that as of now.  IMO ( and raised by others too) it’s better to use
 UPDATE/RE-INVITE.

-- 
----------------------------+-----------------------------------------------
 Reporter:  leonp@…         |       Owner:  andrew.hutton@…                     
     Type:  defect          |      Status:  new                                 
 Priority:  major           |   Milestone:                                      
Component:  Architecture    |     Version:                                      
 Severity:  -               |    Keywords:                                      
----------------------------+-----------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/siprec/trac/ticket/67>
siprec <http://tools.ietf.org/siprec/>


From trac+siprec@trac.tools.ietf.org  Sun Mar 13 07:31:28 2011
Return-Path: <trac+siprec@trac.tools.ietf.org>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE9DE3A68F8 for <siprec@core3.amsl.com>; Sun, 13 Mar 2011 07:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HQqbuSXy+ASz for <siprec@core3.amsl.com>; Sun, 13 Mar 2011 07:31:27 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 4F0073A68F0 for <siprec@ietf.org>; Sun, 13 Mar 2011 07:31:27 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.74) (envelope-from <trac+siprec@trac.tools.ietf.org>) id 1PymLg-0006uy-TK; Sun, 13 Mar 2011 07:32:48 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "siprec issue tracker" <trac+siprec@trac.tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: andrew.hutton@siemens-enterprise.com, leonp@nice.com
X-Trac-Project: siprec
Date: Sun, 13 Mar 2011 14:32:48 -0000
X-URL: http://tools.ietf.org/siprec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/siprec/trac/ticket/67#comment:1
Message-ID: <064.a551f375c968dd096bdafbe390cf57fe@trac.tools.ietf.org>
References: <055.41afc6aa4e9d73c3c70f40ed82b3ef83@trac.tools.ietf.org>
X-Trac-Ticket-ID: 67
In-Reply-To: <055.41afc6aa4e9d73c3c70f40ed82b3ef83@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: andrew.hutton@siemens-enterprise.com, leonp@nice.com, siprec@ietf.org
X-SA-Exim-Mail-From: trac+siprec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: siprec@ietf.org
Subject: Re: [siprec] #67: Metadata Snapshot  via INFO or Update/ReInvite
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 13 Mar 2011 14:31:28 -0000

#67: Metadata Snapshot  via INFO or Update/ReInvite

Changes (by leonp@…):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 Sorrry, wrong draft

-- 
----------------------------+-----------------------------------------------
 Reporter:  leonp@…         |        Owner:  andrew.hutton@…                     
     Type:  defect          |       Status:  closed                              
 Priority:  major           |    Milestone:                                      
Component:  Architecture    |      Version:                                      
 Severity:  -               |   Resolution:  invalid                             
 Keywords:                  |  
----------------------------+-----------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/siprec/trac/ticket/67#comment:1>
siprec <http://tools.ietf.org/siprec/>


From john.elwell@siemens-enterprise.com  Mon Mar 14 00:37:55 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D77453A69C4 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 00:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.305
X-Spam-Level: 
X-Spam-Status: No, score=-102.305 tagged_above=-999 required=5 tests=[AWL=-0.306, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBCQZJ6EfzTU for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 00:37:53 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 0D96F3A693D for <siprec@ietf.org>; Mon, 14 Mar 2011 00:37:52 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3731292; Mon, 14 Mar 2011 08:39:14 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 65EAC1EB82AB; Mon, 14 Mar 2011 08:39:14 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 14 Mar 2011 08:39:14 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 14 Mar 2011 08:39:12 +0100
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCAAP1pCbAAiRDpgAAbozsAAJbF5EA==
Message-ID: <A444A0F8084434499206E78C106220CA086A89AF11@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AE9E@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69B@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A69B@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 07:37:56 -0000

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 13 March 2011 14:15
> To: Elwell, John; siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
> John,
>
> Thanks for  further review of the draft and specific comments
> on XML. Please read inline.
>
> Thanks
> Partha
>
> ________________________________
>
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Sun 3/13/2011 4:11 PM
> To: Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
>
>
> So let's see if I understand correctly. Element extensionData
> occurs in recording-metadata, as part of the sequence that
> also contains things like session, participant, stream. The
> element has attributes 'id' and 'parent' for linking the
> extension data to other elements.
>
> Is this correct?
>
> <Partha> Yeah, it is correct </partha>
>
>  I am not sure I understand the reasons for doing it this
> way, but it seems it should work.
>
> <Partha> Recording metadata is the main container of
> rs-metadata+xml and it is the only one element which MUST be
> passed in both Complete/Partial Metadata XML document. All
> other metadata block (like stream, session, participant,
> extension data) in the model shall be passed independently
> from SRC and then, SRS will be able to correlate based on the
> "id".
[JRE] I see. So this allows entities other than the SRC to send metadata in=
 this same format to the SRS, and furthermore those entities could send new=
 or revised metadata for an object (group, session etc.) without repeating =
the object itself. I am not sure this is a requirement of the work, but it =
is certainly a property of the chosen solution.

> The linkage is done so that the hierarchical blocks of
> metadata model will be represented using the "id"
> relationship in XML document which avoids extra namespace
> during partial XML update. This design logic is applied in
> the following elements:  group, session, stream, participant,
> extensiondata as well. This proposed mechanism allows to
> update only extensiondata alone as well if required. The
> relationship of element & parent element in metadata XML
> document is as follows:
[JRE] So it has the benefit that the SRS can send new or revised metadata f=
or an object (group, session, etc.) without repeating the object itself. I =
am not sure whether this is a significant benefit - in such circumstances i=
t might save a bit of XML, but it has the cost of transmitting an object's =
identifier every time that object is sent, so I am not convinced there is o=
verall gain.

>
>     Element                           -             parent id name
>
> ----------------------------------------------------------------
>
>    group                                -             recording
>
>    session                           -              group
>
>    participant                       -              session
>
>    stream                             -              session
>
>    extensiondata                -              parent
>
> </Partha>
> Some specific comments:
>
> 1. The schema shows 'id' and 'session' as the attributes of
> extensionData - I assume 'session' should be 'parent'.
> 2. Element extensionData also occurs in element participant
> for some reason, according to the scheme. Is this also an error?
> 3. In 4.2.2:
> "recording-metadata element has recording, group, session, stream
>    elements."
> Participant seems to be missing (present in the example and
> in the scheme).
>
> <Partha> Thanks for pointing these error. I'll update the
> text in the next revision </Partha>
>
> 4. The group element is missing from the schema (present in
> the 4.2.2 and in the example).
>
> <Partha> Group element is present in Sec 6 of schema.
[JRE] Yes, I don't know how I missed it.

John



>
> </xs:complexType>
>    <xs:complexType name=3D"group">
>        <xs:sequence>
>            <xs:element name=3D"initiator" type=3D"xs:anyURI"
>             minOccurs=3D"0" maxOccurs=3D"1"/>  =3D=3D=3D=3D> Will be
> removed in the next revision as per below mail discussion
>          <xs:element name=3D"start-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>        </xs:sequence>
>        <xs:attribute name=3D"id" type=3D"xs:urnuuid"
>             use"required"/>
>        <xs:attribute name=3D"recording" type=3D"xs:urnuuid"
>             use"required"/>
>    </xs:complexType>
>
> Please let me know in case any other change has to be done in
> the group element schema
>
> </Partha>
> John (as individual)
>
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com
> <mailto:partr@cisco.com> ]
> > Sent: 12 March 2011 18:24
> > To: Elwell, John; siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > John,
> >
> > Thanks for the detailed comments. Please read inline.
> >
> > Thanks
> > Partha
> >
> > ________________________________
> >
> > From: Elwell, John
> [mailto:john.elwell@siemens-enterprise.com
> <mailto:john.elwell@siemens-enterprise.com> ]
> > Sent: Fri 3/11/2011 8:19 PM
> > To: Parthasarathi R (partr); siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> >
> >
> > Partha,
> >
> > I read -01 and have the following comments:
> >
> > 1. In section 3:
> > "The media related details of metadata SHALL be passed across using
> >    session description protocol (SDP) [RFC4566].  SDP attributes
> >    describes about different media formats like audio, video."
> > I wonder whether it is really appropriate to describe SDP
> > attributes as part of the metadata. If I look at the metadata
> > model, I don't see any attributes of a Media Stream object
> > that could be satisfied using RS SDP. For example, the "codec
> > parameters" attribute relates to the CS, not the RS - the two
> > sessions could use different codecs or different codec
> > parameters. I think it would be far simpler to regard all
> > metadata as being sent in XML. Note that the SDP label
> > attribute can still be used as the linkage between a Media
> > Stream object in the metadata and the corresponding RS media
> > stream that captures the CS media stream concerned.
> >
> > 2. We perhaps need to think about mixed RS media streams,
> > i.e., where several CS media streams have been mixed to
> > produce a single RS media stream. In this case, the several
> > Media Stream objects would all point to the same SDP label, I
> > guess. This then brings into question the mode element (type
> > streamMode) - why is this needed? The fact that several Media
> > Stream objects (stream elements) point to the same label
> > would imply there has been mixing, so the mode element seems
> > to be redundant.
> >
> > 3. Section 4.2.4:
> > "Each group MAY have initiator entity attribute which contains SIP/
> >    SIPS URI to identify the device which acts as Session Recording
> >    Client (SRC).  The entity attribute SIP/SIPS URI FQDN or
> IP address
> >    represents the device and may not have user part."
> > It is unclear to me why a URI identifying the SRC should be
> > an attribute of a group element. I cannot find a
> > corresponding attribute in the CS Group object in the
> > metadata model draft.
> >
> > <Partha> It is a good point. I missed to remove after our
> > last interim meeting discussion. I'll remove in the next
> > revision as there is no strong request for initiator of the
> > session </Partha>
> >
> > 4. The example (section 5.1) seems rather odd, in that the
> > recording-metadata element appears to comprise a sequence of
> > elements (recording, group, session, etc.) alternating with
> > extensiondata elements, i.e., there is an extensiondata
> > element after each of the other elements. This probably
> > complies with the schema, but what is the meaning of several
> > extensiondata elements all within the same recording-metadata
> > element?
> >
> > <Partha> Each extensiondata has its own id and different
> > parent id. Parent id shall be of recording, group, session
> > etc., It is possible for each extension data to have
> > different extended namespace which is specific to its parent.
> >  But it is possible to uniquely identify within
> > recording-metadata as it has its own unique id. </Partha>
> >
> > Why not just a single extensiondata element?
> >
> > <Partha> It may not be preferred because it is tough to
> > arrange extension data for a particular stream within the
> > extension data of group. The individual extension data also
> > provides flexibility to pass the specific extension-data
> > during partial update in case other extension data is not
> > modified. </Partha>
> >
> > Is any significance to be drawn from the fact that there is
> > an extensiondata element following the recording element,
> > another following the group element, etc.?
> >
> > <Partha> As mentioned earlier, group mechanism may passed in
> > group extensiondata  whereas retention policy of a specific
> > session will be passed in session, recording extension data
> > will have common attribute like os login shall be passed. It
> > provides more flexibility and it is optional element, so it
> > is required to pass whenever applicable only </Partha>
> >
> > 5. On the other hand, elements group, session, etc. seem to
> > lack extensiondata elements - would it not be sensible to
> > allow each of these to be extensible?
> >
> > <Partha> Parent-id in extension data helps to link group,
> > session to specific extension data </partha>
> >
> > 6. The method of sending partial metadata seems to imply that
> > when a session, participant, stream etc. comes to an end, we
> > send partial metadata indicating that the element concerned
> > now has an end time. This seems implicitly to mean that the
> > element ceases to exist - correct? So if the SRS were to
> > request a snapshot of complete metadata, it would not receive
> > any elements for which a stop time has previously been sent
> - correct?
> >
> > <Partha> Your understanding is correct, end-time will not
> > passed across in case of SRS request for complete metadata as
> > SRC may have lost the state</Partha>
> >
> >  I don't think I have an issue with this - I just wanted to
> > confirm my understanding.
> >
> > John (as individual)
> >
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org
> <mailto:siprec-bounces@ietf.org> ] On Behalf Of Parthasarathi
> > R (partr)
> > > Sent: 08 March 2011 14:24
> > > To: siprec@ietf.org
> > > Subject: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > > Hi all,
> > >
> > > As per the mailing list comments and interim meeting discussion, I
> > > updated -01 draft of draft-ram-siprec-metadata-format and
> > send it for
> > > review. The draft is available at
> > >
> http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt
>
> <http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt> . The
> > > following update are done as part of -01 draft:
> > >
> > > 1) URN UUID (RFC 4122) mechanism is used as the unique id
> > > mechanism for
> > > relevant XML elements like group, session, stream, participant.
> > >
> > > 2) Partial XML passing in RS is supported by having unique
> > > URN UUID for
> > > group, session, stream, participant, recording, extension
> > > data which are
> > > directly under recording-metadata container/namespace.
> > >
> > > 3) Include recording-metadata element as a container element
> > > instead of
> > > recording element. This helps in avoiding duplicate data of
> > recording
> > > elements during the partial update
> > >
> > > 4) Updated elements in XML document as per
> > > draft-ram-siprec-metadata-04
> > > elements & associations
> > >
> > > 5) Changed appdata element name as extensiondata
> > >
> > > 6) Removed container element like sessions, participants,
> > streams from
> > > XML document as  parent reference exists in each element
> > >
> > > 7) Added Partial Update example & SIP usage XML+SDP example
> > >
> > > 8) Portion of security considerations section is added.
> > >
> > > Could you please review and provide your expert comments on
> > the draft.
> > >
> > > Thanks
> > > Partha
> > >
> > > -----Original Message-----
> > > From: IETF I-D Submission Tool
> [mailto:idsubmission@ietf.org <mailto:idsubmission@ietf.org> ]
> > > Sent: Tuesday, March 08, 2011 7:31 PM
> > > To: Parthasarathi R (partr)
> > > Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > > Subject: New Version Notification for
> > > draft-ram-siprec-metadata-format-01
> > >
> > >
> > > A new version of I-D,
> > draft-ram-siprec-metadata-format-01.txt has been
> > > successfully submitted by Parthasarathi R and posted to the IETF
> > > repository.
> > >
> > > Filename:      draft-ram-siprec-metadata-format
> > > Revision:      01
> > > Title:                 Session Initiation Protocol (SIP)
> > > Recording Metadata
> > > Format
> > > Creation_date:         2011-03-08
> > > WG ID:                 Independent Submission
> > > Number_of_pages: 20
> > >
> > > Abstract:
> > > 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.  The requirements for which are described in
> > > [I-D.ietf-siprec-req], the architecture for which is described in
> > > [I-D.ietf-siprec-architecture], and the metadata model viewed
> > > by Session
> > > Recording Server is described in [I-D.ram-siprec-metadata].
> > > This document focuses on the Recording metadata format
> > which describes
> > > the communication session.
> > >
> > >
> > >
> > >
> > > The IETF Secretariat.
> > >
> > >
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
> <https://www.ietf.org/mailman/listinfo/siprec>
> > >
> >
> >
> >
>
>
>

From partr@cisco.com  Mon Mar 14 05:32:53 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A372D3A6A68 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 05:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.795
X-Spam-Level: 
X-Spam-Status: No, score=-9.795 tagged_above=-999 required=5 tests=[AWL=0.204,  BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75ILCCY707oD for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 05:32:51 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id B9C553A6853 for <siprec@ietf.org>; Mon, 14 Mar 2011 05:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=17002; q=dns/txt; s=iport; t=1300106054; x=1301315654; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=V6tSnUF6Rt7N7vymFURcF+8Xfdr6Ggk1J2Nr4E5ds74=; b=gbFsxMRXjdXuMBYj0Qne0WJ9hFmPJRZLDZ3EFY8sgLtmpBiDP3ynVHz8 4f6t30GEDnWtINC+qzxi7iIov9AQY/marUYkMMmiMEOEEnrNnstRYjXKS fwhJsTdyiiU4n0uO7cmhw5Kg0B1dMOGgVmmDNTKdVfkAGzbnxx62OmDak I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuEAAJ+nfU2Q/khMgWdsb2JhbACYQI1FFAEBFiYlpAObOIJ7GwGCSwSFKYp9
X-IronPort-AV: E=Sophos;i="4.62,315,1297036800"; d="scan'208";a="21612742"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 14 Mar 2011 12:34:13 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2ECXwfQ025132; Mon, 14 Mar 2011 12:34:13 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Mar 2011 18:04:12 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Mar 2011 18:04:11 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904BE312E@XMB-BGL-411.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A89AF11@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Partial Metadata XML document usage in SIPREC [was RE: [siprec] Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCAAP1pCbAAiRDpgAAbozsAAJbF5EAACzF/Q
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AE9E@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69B@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AF11@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 14 Mar 2011 12:34:12.0589 (UTC) FILETIME=[1F97D9D0:01CBE244]
Cc: Leon Portman <Leon.Portman@nice.com>, Henry Lum <Henry.Lum@alcatel-lucent.com>, "Peter Saint-Andre \(psaintan\)" <psaintan@cisco.com>
Subject: [siprec] Partial Metadata XML document usage in SIPREC [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 12:32:54 -0000

John & all,

I complete agree with you that overhead of id inclusion in each Metadata
block element in case partial metadata XML document has to be supported,
there is no explicit requirement in SIPREC to solve this issue and -00
version metadata format draft addresses for complete snapsnot of XML
every time within single RS session. But I noticed in mailing alias and
last SIPREC interim meeting comment that partial metadata support as an
major open item (elephant) for metadata format draft. I'm including
Leon, Henry, and Paul as they provided comments on partial metadata.=20

I'm convinced for partial metadata XML document support because of the
following reason:=20

1) The usage will be more beneficial for Persistent recording mechanism
2) In Call Center scenarios, Hold & Resume, transfer sort of mid-dialog
service exist during most of the calls. Partial metadata update helps in
these scenarios.
3) Universally Unique id is anyway required for group, session, stream
element in XML which shall be used for partial XML passing as well.

Also, We analyzed multiple partial metadata XML format:

1) Current mechanism of Metadata block level id and single container
2) RFC 5261 - An Extensible Markup Language (XML) Patch Operations
Framework Utilizing XML  Path Language (XPath) Selectors
3) REST architecture for Metadata XML

With above all mechanism, the current partial XML mechanism is the
simplest mechanism which well fit for SIPREC. Including Peter in the
mail thread to find any other simpler or less overhead mechanism exists
in XML.

Please let me know everyone opinion which way to go because this is a
crucial decision point for metadata XML format.

Thanks
Partha

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Monday, March 14, 2011 1:09 PM
To: Parthasarathi R (partr); siprec@ietf.org
Subject: RE: [siprec] Review Request for
draft-ram-siprec-metadata-format-01



> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 13 March 2011 14:15
> To: Elwell, John; siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
> John,
>
> Thanks for  further review of the draft and specific comments on XML.=20
> Please read inline.
>
> Thanks
> Partha
>
> ________________________________
>
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Sun 3/13/2011 4:11 PM
> To: Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
>
>
> So let's see if I understand correctly. Element extensionData occurs=20
> in recording-metadata, as part of the sequence that also contains=20
> things like session, participant, stream. The element has attributes=20
> 'id' and 'parent' for linking the extension data to other elements.
>
> Is this correct?
>
> <Partha> Yeah, it is correct </partha>
>
>  I am not sure I understand the reasons for doing it this way, but it=20
> seems it should work.
>
> <Partha> Recording metadata is the main container of
> rs-metadata+xml and it is the only one element which MUST be
> passed in both Complete/Partial Metadata XML document. All other=20
> metadata block (like stream, session, participant, extension data) in=20
> the model shall be passed independently from SRC and then, SRS will be

> able to correlate based on the "id".
[JRE] I see. So this allows entities other than the SRC to send metadata
in this same format to the SRS, and furthermore those entities could
send new or revised metadata for an object (group, session etc.) without
repeating the object itself. I am not sure this is a requirement of the
work, but it is certainly a property of the chosen solution.

> The linkage is done so that the hierarchical blocks of metadata model=20
> will be represented using the "id"
> relationship in XML document which avoids extra namespace during=20
> partial XML update. This design logic is applied in the following=20
> elements:  group, session, stream, participant, extensiondata as well.

> This proposed mechanism allows to update only extensiondata alone as=20
> well if required. The relationship of element & parent element in=20
> metadata XML document is as follows:
[JRE] So it has the benefit that the SRS can send new or revised
metadata for an object (group, session, etc.) without repeating the
object itself. I am not sure whether this is a significant benefit - in
such circumstances it might save a bit of XML, but it has the cost of
transmitting an object's identifier every time that object is sent, so I
am not convinced there is overall gain.

>
>     Element                           -             parent id name
>
> ----------------------------------------------------------------
>
>    group                                -             recording
>
>    session                           -              group
>
>    participant                       -              session
>
>    stream                             -              session
>
>    extensiondata                -              parent
>
> </Partha>
> Some specific comments:
>
> 1. The schema shows 'id' and 'session' as the attributes of=20
> extensionData - I assume 'session' should be 'parent'.
> 2. Element extensionData also occurs in element participant for some=20
> reason, according to the scheme. Is this also an error?
> 3. In 4.2.2:
> "recording-metadata element has recording, group, session, stream
>    elements."
> Participant seems to be missing (present in the example and in the=20
> scheme).
>
> <Partha> Thanks for pointing these error. I'll update the text in the=20
> next revision </Partha>
>
> 4. The group element is missing from the schema (present in the 4.2.2=20
> and in the example).
>
> <Partha> Group element is present in Sec 6 of schema.
[JRE] Yes, I don't know how I missed it.

John



>
> </xs:complexType>
>    <xs:complexType name=3D"group">
>        <xs:sequence>
>            <xs:element name=3D"initiator" type=3D"xs:anyURI"
>             minOccurs=3D"0" maxOccurs=3D"1"/>  =3D=3D=3D=3D> Will be =
removed in=20
> the next revision as per below mail discussion
>          <xs:element name=3D"start-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>        </xs:sequence>
>        <xs:attribute name=3D"id" type=3D"xs:urnuuid"
>             use"required"/>
>        <xs:attribute name=3D"recording" type=3D"xs:urnuuid"
>             use"required"/>
>    </xs:complexType>
>
> Please let me know in case any other change has to be done in the=20
> group element schema
>
> </Partha>
> John (as individual)
>
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com
> <mailto:partr@cisco.com> ]
> > Sent: 12 March 2011 18:24
> > To: Elwell, John; siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > John,
> >
> > Thanks for the detailed comments. Please read inline.
> >
> > Thanks
> > Partha
> >
> > ________________________________
> >
> > From: Elwell, John
> [mailto:john.elwell@siemens-enterprise.com
> <mailto:john.elwell@siemens-enterprise.com> ]
> > Sent: Fri 3/11/2011 8:19 PM
> > To: Parthasarathi R (partr); siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> >
> >
> > Partha,
> >
> > I read -01 and have the following comments:
> >
> > 1. In section 3:
> > "The media related details of metadata SHALL be passed across using
> >    session description protocol (SDP) [RFC4566].  SDP attributes
> >    describes about different media formats like audio, video."
> > I wonder whether it is really appropriate to describe SDP attributes

> > as part of the metadata. If I look at the metadata model, I don't=20
> > see any attributes of a Media Stream object that could be satisfied=20
> > using RS SDP. For example, the "codec parameters" attribute relates=20
> > to the CS, not the RS - the two sessions could use different codecs=20
> > or different codec parameters. I think it would be far simpler to=20
> > regard all metadata as being sent in XML. Note that the SDP label=20
> > attribute can still be used as the linkage between a Media Stream=20
> > object in the metadata and the corresponding RS media stream that=20
> > captures the CS media stream concerned.
> >
> > 2. We perhaps need to think about mixed RS media streams, i.e.,=20
> > where several CS media streams have been mixed to produce a single=20
> > RS media stream. In this case, the several Media Stream objects=20
> > would all point to the same SDP label, I guess. This then brings=20
> > into question the mode element (type
> > streamMode) - why is this needed? The fact that several Media Stream

> > objects (stream elements) point to the same label would imply there=20
> > has been mixing, so the mode element seems to be redundant.
> >
> > 3. Section 4.2.4:
> > "Each group MAY have initiator entity attribute which contains SIP/
> >    SIPS URI to identify the device which acts as Session Recording
> >    Client (SRC).  The entity attribute SIP/SIPS URI FQDN or
> IP address
> >    represents the device and may not have user part."
> > It is unclear to me why a URI identifying the SRC should be an=20
> > attribute of a group element. I cannot find a corresponding=20
> > attribute in the CS Group object in the metadata model draft.
> >
> > <Partha> It is a good point. I missed to remove after our last=20
> > interim meeting discussion. I'll remove in the next revision as=20
> > there is no strong request for initiator of the session </Partha>
> >
> > 4. The example (section 5.1) seems rather odd, in that the=20
> > recording-metadata element appears to comprise a sequence of=20
> > elements (recording, group, session, etc.) alternating with=20
> > extensiondata elements, i.e., there is an extensiondata element=20
> > after each of the other elements. This probably complies with the=20
> > schema, but what is the meaning of several extensiondata elements=20
> > all within the same recording-metadata element?
> >
> > <Partha> Each extensiondata has its own id and different parent id.=20
> > Parent id shall be of recording, group, session etc., It is possible

> > for each extension data to have different extended namespace which=20
> > is specific to its parent.
> >  But it is possible to uniquely identify within recording-metadata=20
> > as it has its own unique id. </Partha>
> >
> > Why not just a single extensiondata element?
> >
> > <Partha> It may not be preferred because it is tough to arrange=20
> > extension data for a particular stream within the extension data of=20
> > group. The individual extension data also provides flexibility to=20
> > pass the specific extension-data during partial update in case other

> > extension data is not modified. </Partha>
> >
> > Is any significance to be drawn from the fact that there is an=20
> > extensiondata element following the recording element, another=20
> > following the group element, etc.?
> >
> > <Partha> As mentioned earlier, group mechanism may passed in group=20
> > extensiondata  whereas retention policy of a specific session will=20
> > be passed in session, recording extension data will have common=20
> > attribute like os login shall be passed. It provides more=20
> > flexibility and it is optional element, so it is required to pass=20
> > whenever applicable only </Partha>
> >
> > 5. On the other hand, elements group, session, etc. seem to lack=20
> > extensiondata elements - would it not be sensible to allow each of=20
> > these to be extensible?
> >
> > <Partha> Parent-id in extension data helps to link group, session to

> > specific extension data </partha>
> >
> > 6. The method of sending partial metadata seems to imply that when a

> > session, participant, stream etc. comes to an end, we send partial=20
> > metadata indicating that the element concerned now has an end time.=20
> > This seems implicitly to mean that the element ceases to exist -=20
> > correct? So if the SRS were to request a snapshot of complete=20
> > metadata, it would not receive any elements for which a stop time=20
> > has previously been sent
> - correct?
> >
> > <Partha> Your understanding is correct, end-time will not passed=20
> > across in case of SRS request for complete metadata as SRC may have=20
> > lost the state</Partha>
> >
> >  I don't think I have an issue with this - I just wanted to confirm=20
> > my understanding.
> >
> > John (as individual)
> >
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org
> <mailto:siprec-bounces@ietf.org> ] On Behalf Of Parthasarathi
> > R (partr)
> > > Sent: 08 March 2011 14:24
> > > To: siprec@ietf.org
> > > Subject: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > > Hi all,
> > >
> > > As per the mailing list comments and interim meeting discussion, I

> > > updated -01 draft of draft-ram-siprec-metadata-format and
> > send it for
> > > review. The draft is available at
> > >
> http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt
>
> <http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt> . The
> > > following update are done as part of -01 draft:
> > >
> > > 1) URN UUID (RFC 4122) mechanism is used as the unique id=20
> > > mechanism for relevant XML elements like group, session, stream,=20
> > > participant.
> > >
> > > 2) Partial XML passing in RS is supported by having unique URN=20
> > > UUID for group, session, stream, participant, recording, extension

> > > data which are directly under recording-metadata=20
> > > container/namespace.
> > >
> > > 3) Include recording-metadata element as a container element=20
> > > instead of recording element. This helps in avoiding duplicate=20
> > > data of
> > recording
> > > elements during the partial update
> > >
> > > 4) Updated elements in XML document as per
> > > draft-ram-siprec-metadata-04
> > > elements & associations
> > >
> > > 5) Changed appdata element name as extensiondata
> > >
> > > 6) Removed container element like sessions, participants,
> > streams from
> > > XML document as  parent reference exists in each element
> > >
> > > 7) Added Partial Update example & SIP usage XML+SDP example
> > >
> > > 8) Portion of security considerations section is added.
> > >
> > > Could you please review and provide your expert comments on
> > the draft.
> > >
> > > Thanks
> > > Partha
> > >
> > > -----Original Message-----
> > > From: IETF I-D Submission Tool
> [mailto:idsubmission@ietf.org <mailto:idsubmission@ietf.org> ]
> > > Sent: Tuesday, March 08, 2011 7:31 PM
> > > To: Parthasarathi R (partr)
> > > Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > > Subject: New Version Notification for
> > > draft-ram-siprec-metadata-format-01
> > >
> > >
> > > A new version of I-D,
> > draft-ram-siprec-metadata-format-01.txt has been
> > > successfully submitted by Parthasarathi R and posted to the IETF=20
> > > repository.
> > >
> > > Filename:      draft-ram-siprec-metadata-format
> > > Revision:      01
> > > Title:                 Session Initiation Protocol (SIP)
> > > Recording Metadata
> > > Format
> > > Creation_date:         2011-03-08
> > > WG ID:                 Independent Submission
> > > Number_of_pages: 20
> > >
> > > Abstract:
> > > 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,=20
> > > compliance, and consumer protection reasons.  Recording of a=20
> > > session is typically performed by sending a copy of a media stream

> > > to
> > a recording
> > > device.  The requirements for which are described in=20
> > > [I-D.ietf-siprec-req], the architecture for which is described in=20
> > > [I-D.ietf-siprec-architecture], and the metadata model viewed by=20
> > > Session Recording Server is described in=20
> > > [I-D.ram-siprec-metadata].
> > > This document focuses on the Recording metadata format
> > which describes
> > > the communication session.
> > >
> > >
> > >
> > >
> > > The IETF Secretariat.
> > >
> > >
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
> <https://www.ietf.org/mailman/listinfo/siprec>
> > >
> >
> >
> >
>
>
>

From Leon.Portman@nice.com  Mon Mar 14 05:38:39 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F3713A6A62 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 05:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.237
X-Spam-Level: 
X-Spam-Status: No, score=-2.237 tagged_above=-999 required=5 tests=[AWL=-0.238, BAYES_00=-2.599, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZL-hQMK7chJ for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 05:38:37 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 01FBE3A6D08 for <siprec@ietf.org>; Mon, 14 Mar 2011 05:38:37 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.15]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Mon, 14 Mar 2011 14:39:58 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 14 Mar 2011 14:39:58 +0200
Thread-Topic: Partial Metadata XML document usage in SIPREC [was RE: [siprec] Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCAAP1pCbAAiRDpgAAbozsAAJbF5EAACzF/QAAgIcwA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A8BB2FA1@TLVMBX01.nice.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AE9E@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69B@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AF11@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A623904BE312E@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904BE312E@XMB-BGL-411.cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Henry Lum <Henry.Lum@alcatel-lucent.com>, "Peter Saint-Andre \(psaintan\)" <psaintan@cisco.com>
Subject: Re: [siprec] Partial Metadata XML document usage in SIPREC [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 12:38:40 -0000

Sorry, I was not following this thread from the beginning.  I completely ag=
ree with Partha. Support for delta updates of metadata is mandatory from my=
 point of view.

Leon

-----Original Message-----
From: Parthasarathi R (partr) [mailto:partr@cisco.com]
Sent: Monday, March 14, 2011 2:34 PM
To: Elwell, John; siprec@ietf.org
Cc: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Peter Saint-Andre (ps=
aintan)
Subject: Partial Metadata XML document usage in SIPREC [was RE: [siprec] Re=
view Request for draft-ram-siprec-metadata-format-01]

John & all,

I complete agree with you that overhead of id inclusion in each Metadata bl=
ock element in case partial metadata XML document has to be supported, ther=
e is no explicit requirement in SIPREC to solve this issue and -00 version =
metadata format draft addresses for complete snapsnot of XML every time wit=
hin single RS session. But I noticed in mailing alias and last SIPREC inter=
im meeting comment that partial metadata support as an major open item (ele=
phant) for metadata format draft. I'm including Leon, Henry, and Paul as th=
ey provided comments on partial metadata.

I'm convinced for partial metadata XML document support because of the foll=
owing reason:

1) The usage will be more beneficial for Persistent recording mechanism
2) In Call Center scenarios, Hold & Resume, transfer sort of mid-dialog ser=
vice exist during most of the calls. Partial metadata update helps in these=
 scenarios.
3) Universally Unique id is anyway required for group, session, stream elem=
ent in XML which shall be used for partial XML passing as well.

Also, We analyzed multiple partial metadata XML format:

1) Current mechanism of Metadata block level id and single container
2) RFC 5261 - An Extensible Markup Language (XML) Patch Operations Framewor=
k Utilizing XML  Path Language (XPath) Selectors
3) REST architecture for Metadata XML

With above all mechanism, the current partial XML mechanism is the simplest=
 mechanism which well fit for SIPREC. Including Peter in the mail thread to=
 find any other simpler or less overhead mechanism exists in XML.

Please let me know everyone opinion which way to go because this is a cruci=
al decision point for metadata XML format.

Thanks
Partha

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
Sent: Monday, March 14, 2011 1:09 PM
To: Parthasarathi R (partr); siprec@ietf.org
Subject: RE: [siprec] Review Request for
draft-ram-siprec-metadata-format-01



> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 13 March 2011 14:15
> To: Elwell, John; siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
> John,
>
> Thanks for  further review of the draft and specific comments on XML.
> Please read inline.
>
> Thanks
> Partha
>
> ________________________________
>
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Sun 3/13/2011 4:11 PM
> To: Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
>
>
> So let's see if I understand correctly. Element extensionData occurs
> in recording-metadata, as part of the sequence that also contains
> things like session, participant, stream. The element has attributes
> 'id' and 'parent' for linking the extension data to other elements.
>
> Is this correct?
>
> <Partha> Yeah, it is correct </partha>
>
>  I am not sure I understand the reasons for doing it this way, but it
> seems it should work.
>
> <Partha> Recording metadata is the main container of
> rs-metadata+xml and it is the only one element which MUST be
> passed in both Complete/Partial Metadata XML document. All other
> metadata block (like stream, session, participant, extension data) in
> the model shall be passed independently from SRC and then, SRS will be

> able to correlate based on the "id".
[JRE] I see. So this allows entities other than the SRC to send metadata
in this same format to the SRS, and furthermore those entities could
send new or revised metadata for an object (group, session etc.) without
repeating the object itself. I am not sure this is a requirement of the
work, but it is certainly a property of the chosen solution.

> The linkage is done so that the hierarchical blocks of metadata model
> will be represented using the "id"
> relationship in XML document which avoids extra namespace during
> partial XML update. This design logic is applied in the following
> elements:  group, session, stream, participant, extensiondata as well.

> This proposed mechanism allows to update only extensiondata alone as
> well if required. The relationship of element & parent element in
> metadata XML document is as follows:
[JRE] So it has the benefit that the SRS can send new or revised
metadata for an object (group, session, etc.) without repeating the
object itself. I am not sure whether this is a significant benefit - in
such circumstances it might save a bit of XML, but it has the cost of
transmitting an object's identifier every time that object is sent, so I
am not convinced there is overall gain.

>
>     Element                           -             parent id name
>
> ----------------------------------------------------------------
>
>    group                                -             recording
>
>    session                           -              group
>
>    participant                       -              session
>
>    stream                             -              session
>
>    extensiondata                -              parent
>
> </Partha>
> Some specific comments:
>
> 1. The schema shows 'id' and 'session' as the attributes of
> extensionData - I assume 'session' should be 'parent'.
> 2. Element extensionData also occurs in element participant for some
> reason, according to the scheme. Is this also an error?
> 3. In 4.2.2:
> "recording-metadata element has recording, group, session, stream
>    elements."
> Participant seems to be missing (present in the example and in the
> scheme).
>
> <Partha> Thanks for pointing these error. I'll update the text in the
> next revision </Partha>
>
> 4. The group element is missing from the schema (present in the 4.2.2
> and in the example).
>
> <Partha> Group element is present in Sec 6 of schema.
[JRE] Yes, I don't know how I missed it.

John



>
> </xs:complexType>
>    <xs:complexType name=3D"group">
>        <xs:sequence>
>            <xs:element name=3D"initiator" type=3D"xs:anyURI"
>             minOccurs=3D"0" maxOccurs=3D"1"/>  =3D=3D=3D=3D> Will be remo=
ved in
> the next revision as per below mail discussion
>          <xs:element name=3D"start-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>        </xs:sequence>
>        <xs:attribute name=3D"id" type=3D"xs:urnuuid"
>             use"required"/>
>        <xs:attribute name=3D"recording" type=3D"xs:urnuuid"
>             use"required"/>
>    </xs:complexType>
>
> Please let me know in case any other change has to be done in the
> group element schema
>
> </Partha>
> John (as individual)
>
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com
> <mailto:partr@cisco.com> ]
> > Sent: 12 March 2011 18:24
> > To: Elwell, John; siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > John,
> >
> > Thanks for the detailed comments. Please read inline.
> >
> > Thanks
> > Partha
> >
> > ________________________________
> >
> > From: Elwell, John
> [mailto:john.elwell@siemens-enterprise.com
> <mailto:john.elwell@siemens-enterprise.com> ]
> > Sent: Fri 3/11/2011 8:19 PM
> > To: Parthasarathi R (partr); siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> >
> >
> > Partha,
> >
> > I read -01 and have the following comments:
> >
> > 1. In section 3:
> > "The media related details of metadata SHALL be passed across using
> >    session description protocol (SDP) [RFC4566].  SDP attributes
> >    describes about different media formats like audio, video."
> > I wonder whether it is really appropriate to describe SDP attributes

> > as part of the metadata. If I look at the metadata model, I don't
> > see any attributes of a Media Stream object that could be satisfied
> > using RS SDP. For example, the "codec parameters" attribute relates
> > to the CS, not the RS - the two sessions could use different codecs
> > or different codec parameters. I think it would be far simpler to
> > regard all metadata as being sent in XML. Note that the SDP label
> > attribute can still be used as the linkage between a Media Stream
> > object in the metadata and the corresponding RS media stream that
> > captures the CS media stream concerned.
> >
> > 2. We perhaps need to think about mixed RS media streams, i.e.,
> > where several CS media streams have been mixed to produce a single
> > RS media stream. In this case, the several Media Stream objects
> > would all point to the same SDP label, I guess. This then brings
> > into question the mode element (type
> > streamMode) - why is this needed? The fact that several Media Stream

> > objects (stream elements) point to the same label would imply there
> > has been mixing, so the mode element seems to be redundant.
> >
> > 3. Section 4.2.4:
> > "Each group MAY have initiator entity attribute which contains SIP/
> >    SIPS URI to identify the device which acts as Session Recording
> >    Client (SRC).  The entity attribute SIP/SIPS URI FQDN or
> IP address
> >    represents the device and may not have user part."
> > It is unclear to me why a URI identifying the SRC should be an
> > attribute of a group element. I cannot find a corresponding
> > attribute in the CS Group object in the metadata model draft.
> >
> > <Partha> It is a good point. I missed to remove after our last
> > interim meeting discussion. I'll remove in the next revision as
> > there is no strong request for initiator of the session </Partha>
> >
> > 4. The example (section 5.1) seems rather odd, in that the
> > recording-metadata element appears to comprise a sequence of
> > elements (recording, group, session, etc.) alternating with
> > extensiondata elements, i.e., there is an extensiondata element
> > after each of the other elements. This probably complies with the
> > schema, but what is the meaning of several extensiondata elements
> > all within the same recording-metadata element?
> >
> > <Partha> Each extensiondata has its own id and different parent id.
> > Parent id shall be of recording, group, session etc., It is possible

> > for each extension data to have different extended namespace which
> > is specific to its parent.
> >  But it is possible to uniquely identify within recording-metadata
> > as it has its own unique id. </Partha>
> >
> > Why not just a single extensiondata element?
> >
> > <Partha> It may not be preferred because it is tough to arrange
> > extension data for a particular stream within the extension data of
> > group. The individual extension data also provides flexibility to
> > pass the specific extension-data during partial update in case other

> > extension data is not modified. </Partha>
> >
> > Is any significance to be drawn from the fact that there is an
> > extensiondata element following the recording element, another
> > following the group element, etc.?
> >
> > <Partha> As mentioned earlier, group mechanism may passed in group
> > extensiondata  whereas retention policy of a specific session will
> > be passed in session, recording extension data will have common
> > attribute like os login shall be passed. It provides more
> > flexibility and it is optional element, so it is required to pass
> > whenever applicable only </Partha>
> >
> > 5. On the other hand, elements group, session, etc. seem to lack
> > extensiondata elements - would it not be sensible to allow each of
> > these to be extensible?
> >
> > <Partha> Parent-id in extension data helps to link group, session to

> > specific extension data </partha>
> >
> > 6. The method of sending partial metadata seems to imply that when a

> > session, participant, stream etc. comes to an end, we send partial
> > metadata indicating that the element concerned now has an end time.
> > This seems implicitly to mean that the element ceases to exist -
> > correct? So if the SRS were to request a snapshot of complete
> > metadata, it would not receive any elements for which a stop time
> > has previously been sent
> - correct?
> >
> > <Partha> Your understanding is correct, end-time will not passed
> > across in case of SRS request for complete metadata as SRC may have
> > lost the state</Partha>
> >
> >  I don't think I have an issue with this - I just wanted to confirm
> > my understanding.
> >
> > John (as individual)
> >
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org
> <mailto:siprec-bounces@ietf.org> ] On Behalf Of Parthasarathi
> > R (partr)
> > > Sent: 08 March 2011 14:24
> > > To: siprec@ietf.org
> > > Subject: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > > Hi all,
> > >
> > > As per the mailing list comments and interim meeting discussion, I

> > > updated -01 draft of draft-ram-siprec-metadata-format and
> > send it for
> > > review. The draft is available at
> > >
> http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt
>
> <http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt> . The
> > > following update are done as part of -01 draft:
> > >
> > > 1) URN UUID (RFC 4122) mechanism is used as the unique id
> > > mechanism for relevant XML elements like group, session, stream,
> > > participant.
> > >
> > > 2) Partial XML passing in RS is supported by having unique URN
> > > UUID for group, session, stream, participant, recording, extension

> > > data which are directly under recording-metadata
> > > container/namespace.
> > >
> > > 3) Include recording-metadata element as a container element
> > > instead of recording element. This helps in avoiding duplicate
> > > data of
> > recording
> > > elements during the partial update
> > >
> > > 4) Updated elements in XML document as per
> > > draft-ram-siprec-metadata-04
> > > elements & associations
> > >
> > > 5) Changed appdata element name as extensiondata
> > >
> > > 6) Removed container element like sessions, participants,
> > streams from
> > > XML document as  parent reference exists in each element
> > >
> > > 7) Added Partial Update example & SIP usage XML+SDP example
> > >
> > > 8) Portion of security considerations section is added.
> > >
> > > Could you please review and provide your expert comments on
> > the draft.
> > >
> > > Thanks
> > > Partha
> > >
> > > -----Original Message-----
> > > From: IETF I-D Submission Tool
> [mailto:idsubmission@ietf.org <mailto:idsubmission@ietf.org> ]
> > > Sent: Tuesday, March 08, 2011 7:31 PM
> > > To: Parthasarathi R (partr)
> > > Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > > Subject: New Version Notification for
> > > draft-ram-siprec-metadata-format-01
> > >
> > >
> > > A new version of I-D,
> > draft-ram-siprec-metadata-format-01.txt has been
> > > successfully submitted by Parthasarathi R and posted to the IETF
> > > repository.
> > >
> > > Filename:      draft-ram-siprec-metadata-format
> > > Revision:      01
> > > Title:                 Session Initiation Protocol (SIP)
> > > Recording Metadata
> > > Format
> > > Creation_date:         2011-03-08
> > > WG ID:                 Independent Submission
> > > Number_of_pages: 20
> > >
> > > Abstract:
> > > 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.  The requirements for which are described in
> > > [I-D.ietf-siprec-req], the architecture for which is described in
> > > [I-D.ietf-siprec-architecture], and the metadata model viewed by
> > > Session Recording Server is described in
> > > [I-D.ram-siprec-metadata].
> > > This document focuses on the Recording metadata format
> > which describes
> > > the communication session.
> > >
> > >
> > >
> > >
> > > The IETF Secretariat.
> > >
> > >
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
> <https://www.ietf.org/mailman/listinfo/siprec>
> > >
> >
> >
> >
>
>
>

From rmohanr@cisco.com  Mon Mar 14 05:54:40 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 241BE3A6928 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 05:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.149
X-Spam-Level: 
X-Spam-Status: No, score=-10.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9GxxtnkiERt for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 05:54:38 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 5A7CA3A6BFC for <siprec@ietf.org>; Mon, 14 Mar 2011 05:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=19262; q=dns/txt; s=iport; t=1300107361; x=1301316961; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=CHvWYZ4nveI99vAL5EspgNmlm4J7QRrgjDnM1Eaed/c=; b=Tj8RoWVGFY3yFsKOFbE0N+Am8FpNLLsfu5oCW77ITNCFwG9ybG9XzKDS TxXaUNzSluNQTRRspPu9/WTwg/NIsyC8W1CiiVuLKZelQPzQXAKq9yPq0 0+lJuhxmF1xcL1y84h3oK7mGDHU8bbkMjsDYHPpHFca6dUtkj5c8kKBI7 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuEAAHqtfU2Q/khNgWdsb2JhbACYQI1FFAEBFiYlo3GbQYJ7GwGCSwSFKYp9
X-IronPort-AV: E=Sophos;i="4.62,315,1297036800"; d="scan'208";a="21615783"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 14 Mar 2011 12:55:59 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2ECtwIp004390; Mon, 14 Mar 2011 12:55:59 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Mar 2011 18:25:58 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Mar 2011 18:25:54 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD05A7E793@XMB-BGL-417.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A8BB2FA1@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Partial Metadata XML document usage in SIPREC [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCAAP1pCbAAiRDpgAAbozsAAJbF5EAACzF/QAAgIcwAAAHrTQA==
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AE9E@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A69B@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AF11@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A623904BE312E@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A8BB2FA1@TLVMBX01.nice.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 14 Mar 2011 12:55:58.0324 (UTC) FILETIME=[29DF3340:01CBE247]
Cc: Henry Lum <Henry.Lum@alcatel-lucent.com>, "Peter Saint-Andre \(psaintan\)" <psaintan@cisco.com>
Subject: Re: [siprec] Partial Metadata XML document usage in SIPREC [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 12:54:40 -0000

+1.=20
As per my understanding, in the last interim meeting there was a general
agreement from most folks on the need to have partial updates for
metadata.
If we feel there is an overhead with the current proposed mechanism in
draft-ram-siprec-metadata-format-01 we could brainstorm on that to see
if there is any better approach.

Ram

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Leon Portman
> Sent: Monday, March 14, 2011 6:10 PM
> To: Parthasarathi R (partr); Elwell, John; siprec@ietf.org
> Cc: Henry Lum; Peter Saint-Andre (psaintan)
> Subject: Re: [siprec] Partial Metadata XML document usage in SIPREC
> [was RE: Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Sorry, I was not following this thread from the beginning.  I
> completely agree with Partha. Support for delta updates of metadata is
> mandatory from my point of view.
>=20
> Leon
>=20
> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: Monday, March 14, 2011 2:34 PM
> To: Elwell, John; siprec@ietf.org
> Cc: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Peter
Saint-Andre
> (psaintan)
> Subject: Partial Metadata XML document usage in SIPREC [was RE:
> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
>=20
> John & all,
>=20
> I complete agree with you that overhead of id inclusion in each
> Metadata block element in case partial metadata XML document has to be
> supported, there is no explicit requirement in SIPREC to solve this
> issue and -00 version metadata format draft addresses for complete
> snapsnot of XML every time within single RS session. But I noticed in
> mailing alias and last SIPREC interim meeting comment that partial
> metadata support as an major open item (elephant) for metadata format
> draft. I'm including Leon, Henry, and Paul as they provided comments
on
> partial metadata.
>=20
> I'm convinced for partial metadata XML document support because of the
> following reason:
>=20
> 1) The usage will be more beneficial for Persistent recording
mechanism
> 2) In Call Center scenarios, Hold & Resume, transfer sort of
mid-dialog
> service exist during most of the calls. Partial metadata update helps
> in these scenarios.
> 3) Universally Unique id is anyway required for group, session, stream
> element in XML which shall be used for partial XML passing as well.
>=20
> Also, We analyzed multiple partial metadata XML format:
>=20
> 1) Current mechanism of Metadata block level id and single container
> 2) RFC 5261 - An Extensible Markup Language (XML) Patch Operations
> Framework Utilizing XML  Path Language (XPath) Selectors
> 3) REST architecture for Metadata XML
>=20
> With above all mechanism, the current partial XML mechanism is the
> simplest mechanism which well fit for SIPREC. Including Peter in the
> mail thread to find any other simpler or less overhead mechanism
exists
> in XML.
>=20
> Please let me know everyone opinion which way to go because this is a
> crucial decision point for metadata XML format.
>=20
> Thanks
> Partha
>=20
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Monday, March 14, 2011 1:09 PM
> To: Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>=20
>=20
>=20
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > Sent: 13 March 2011 14:15
> > To: Elwell, John; siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > John,
> >
> > Thanks for  further review of the draft and specific comments on
XML.
> > Please read inline.
> >
> > Thanks
> > Partha
> >
> > ________________________________
> >
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Sun 3/13/2011 4:11 PM
> > To: Parthasarathi R (partr); siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> >
> >
> > So let's see if I understand correctly. Element extensionData occurs
> > in recording-metadata, as part of the sequence that also contains
> > things like session, participant, stream. The element has attributes
> > 'id' and 'parent' for linking the extension data to other elements.
> >
> > Is this correct?
> >
> > <Partha> Yeah, it is correct </partha>
> >
> >  I am not sure I understand the reasons for doing it this way, but
it
> > seems it should work.
> >
> > <Partha> Recording metadata is the main container of
> > rs-metadata+xml and it is the only one element which MUST be
> > passed in both Complete/Partial Metadata XML document. All other
> > metadata block (like stream, session, participant, extension data)
in
> > the model shall be passed independently from SRC and then, SRS will
> be
>=20
> > able to correlate based on the "id".
> [JRE] I see. So this allows entities other than the SRC to send
> metadata
> in this same format to the SRS, and furthermore those entities could
> send new or revised metadata for an object (group, session etc.)
> without
> repeating the object itself. I am not sure this is a requirement of
the
> work, but it is certainly a property of the chosen solution.
>=20
> > The linkage is done so that the hierarchical blocks of metadata
model
> > will be represented using the "id"
> > relationship in XML document which avoids extra namespace during
> > partial XML update. This design logic is applied in the following
> > elements:  group, session, stream, participant, extensiondata as
> well.
>=20
> > This proposed mechanism allows to update only extensiondata alone as
> > well if required. The relationship of element & parent element in
> > metadata XML document is as follows:
> [JRE] So it has the benefit that the SRS can send new or revised
> metadata for an object (group, session, etc.) without repeating the
> object itself. I am not sure whether this is a significant benefit -
in
> such circumstances it might save a bit of XML, but it has the cost of
> transmitting an object's identifier every time that object is sent, so
> I
> am not convinced there is overall gain.
>=20
> >
> >     Element                           -             parent id name
> >
> > ----------------------------------------------------------------
> >
> >    group                                -             recording
> >
> >    session                           -              group
> >
> >    participant                       -              session
> >
> >    stream                             -              session
> >
> >    extensiondata                -              parent
> >
> > </Partha>
> > Some specific comments:
> >
> > 1. The schema shows 'id' and 'session' as the attributes of
> > extensionData - I assume 'session' should be 'parent'.
> > 2. Element extensionData also occurs in element participant for some
> > reason, according to the scheme. Is this also an error?
> > 3. In 4.2.2:
> > "recording-metadata element has recording, group, session, stream
> >    elements."
> > Participant seems to be missing (present in the example and in the
> > scheme).
> >
> > <Partha> Thanks for pointing these error. I'll update the text in
the
> > next revision </Partha>
> >
> > 4. The group element is missing from the schema (present in the
4.2.2
> > and in the example).
> >
> > <Partha> Group element is present in Sec 6 of schema.
> [JRE] Yes, I don't know how I missed it.
>=20
> John
>=20
>=20
>=20
> >
> > </xs:complexType>
> >    <xs:complexType name=3D"group">
> >        <xs:sequence>
> >            <xs:element name=3D"initiator" type=3D"xs:anyURI"
> >             minOccurs=3D"0" maxOccurs=3D"1"/>  =3D=3D=3D=3D> Will be =
removed in
> > the next revision as per below mail discussion
> >          <xs:element name=3D"start-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >        </xs:sequence>
> >        <xs:attribute name=3D"id" type=3D"xs:urnuuid"
> >             use"required"/>
> >        <xs:attribute name=3D"recording" type=3D"xs:urnuuid"
> >             use"required"/>
> >    </xs:complexType>
> >
> > Please let me know in case any other change has to be done in the
> > group element schema
> >
> > </Partha>
> > John (as individual)
> >
> > > -----Original Message-----
> > > From: Parthasarathi R (partr) [mailto:partr@cisco.com
> > <mailto:partr@cisco.com> ]
> > > Sent: 12 March 2011 18:24
> > > To: Elwell, John; siprec@ietf.org
> > > Subject: RE: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > > John,
> > >
> > > Thanks for the detailed comments. Please read inline.
> > >
> > > Thanks
> > > Partha
> > >
> > > ________________________________
> > >
> > > From: Elwell, John
> > [mailto:john.elwell@siemens-enterprise.com
> > <mailto:john.elwell@siemens-enterprise.com> ]
> > > Sent: Fri 3/11/2011 8:19 PM
> > > To: Parthasarathi R (partr); siprec@ietf.org
> > > Subject: RE: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > >
> > >
> > > Partha,
> > >
> > > I read -01 and have the following comments:
> > >
> > > 1. In section 3:
> > > "The media related details of metadata SHALL be passed across
using
> > >    session description protocol (SDP) [RFC4566].  SDP attributes
> > >    describes about different media formats like audio, video."
> > > I wonder whether it is really appropriate to describe SDP
> attributes
>=20
> > > as part of the metadata. If I look at the metadata model, I don't
> > > see any attributes of a Media Stream object that could be
satisfied
> > > using RS SDP. For example, the "codec parameters" attribute
relates
> > > to the CS, not the RS - the two sessions could use different
codecs
> > > or different codec parameters. I think it would be far simpler to
> > > regard all metadata as being sent in XML. Note that the SDP label
> > > attribute can still be used as the linkage between a Media Stream
> > > object in the metadata and the corresponding RS media stream that
> > > captures the CS media stream concerned.
> > >
> > > 2. We perhaps need to think about mixed RS media streams, i.e.,
> > > where several CS media streams have been mixed to produce a single
> > > RS media stream. In this case, the several Media Stream objects
> > > would all point to the same SDP label, I guess. This then brings
> > > into question the mode element (type
> > > streamMode) - why is this needed? The fact that several Media
> Stream
>=20
> > > objects (stream elements) point to the same label would imply
there
> > > has been mixing, so the mode element seems to be redundant.
> > >
> > > 3. Section 4.2.4:
> > > "Each group MAY have initiator entity attribute which contains
SIP/
> > >    SIPS URI to identify the device which acts as Session Recording
> > >    Client (SRC).  The entity attribute SIP/SIPS URI FQDN or
> > IP address
> > >    represents the device and may not have user part."
> > > It is unclear to me why a URI identifying the SRC should be an
> > > attribute of a group element. I cannot find a corresponding
> > > attribute in the CS Group object in the metadata model draft.
> > >
> > > <Partha> It is a good point. I missed to remove after our last
> > > interim meeting discussion. I'll remove in the next revision as
> > > there is no strong request for initiator of the session </Partha>
> > >
> > > 4. The example (section 5.1) seems rather odd, in that the
> > > recording-metadata element appears to comprise a sequence of
> > > elements (recording, group, session, etc.) alternating with
> > > extensiondata elements, i.e., there is an extensiondata element
> > > after each of the other elements. This probably complies with the
> > > schema, but what is the meaning of several extensiondata elements
> > > all within the same recording-metadata element?
> > >
> > > <Partha> Each extensiondata has its own id and different parent
id.
> > > Parent id shall be of recording, group, session etc., It is
> possible
>=20
> > > for each extension data to have different extended namespace which
> > > is specific to its parent.
> > >  But it is possible to uniquely identify within recording-metadata
> > > as it has its own unique id. </Partha>
> > >
> > > Why not just a single extensiondata element?
> > >
> > > <Partha> It may not be preferred because it is tough to arrange
> > > extension data for a particular stream within the extension data
of
> > > group. The individual extension data also provides flexibility to
> > > pass the specific extension-data during partial update in case
> other
>=20
> > > extension data is not modified. </Partha>
> > >
> > > Is any significance to be drawn from the fact that there is an
> > > extensiondata element following the recording element, another
> > > following the group element, etc.?
> > >
> > > <Partha> As mentioned earlier, group mechanism may passed in group
> > > extensiondata  whereas retention policy of a specific session will
> > > be passed in session, recording extension data will have common
> > > attribute like os login shall be passed. It provides more
> > > flexibility and it is optional element, so it is required to pass
> > > whenever applicable only </Partha>
> > >
> > > 5. On the other hand, elements group, session, etc. seem to lack
> > > extensiondata elements - would it not be sensible to allow each of
> > > these to be extensible?
> > >
> > > <Partha> Parent-id in extension data helps to link group, session
> to
>=20
> > > specific extension data </partha>
> > >
> > > 6. The method of sending partial metadata seems to imply that when
> a
>=20
> > > session, participant, stream etc. comes to an end, we send partial
> > > metadata indicating that the element concerned now has an end
time.
> > > This seems implicitly to mean that the element ceases to exist -
> > > correct? So if the SRS were to request a snapshot of complete
> > > metadata, it would not receive any elements for which a stop time
> > > has previously been sent
> > - correct?
> > >
> > > <Partha> Your understanding is correct, end-time will not passed
> > > across in case of SRS request for complete metadata as SRC may
have
> > > lost the state</Partha>
> > >
> > >  I don't think I have an issue with this - I just wanted to
confirm
> > > my understanding.
> > >
> > > John (as individual)
> > >
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org
> > <mailto:siprec-bounces@ietf.org> ] On Behalf Of Parthasarathi
> > > R (partr)
> > > > Sent: 08 March 2011 14:24
> > > > To: siprec@ietf.org
> > > > Subject: [siprec] Review Request for
> > > > draft-ram-siprec-metadata-format-01
> > > >
> > > > Hi all,
> > > >
> > > > As per the mailing list comments and interim meeting discussion,
> I
>=20
> > > > updated -01 draft of draft-ram-siprec-metadata-format and
> > > send it for
> > > > review. The draft is available at
> > > >
> > http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt
> >
> > <http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt> .
> The
> > > > following update are done as part of -01 draft:
> > > >
> > > > 1) URN UUID (RFC 4122) mechanism is used as the unique id
> > > > mechanism for relevant XML elements like group, session, stream,
> > > > participant.
> > > >
> > > > 2) Partial XML passing in RS is supported by having unique URN
> > > > UUID for group, session, stream, participant, recording,
> extension
>=20
> > > > data which are directly under recording-metadata
> > > > container/namespace.
> > > >
> > > > 3) Include recording-metadata element as a container element
> > > > instead of recording element. This helps in avoiding duplicate
> > > > data of
> > > recording
> > > > elements during the partial update
> > > >
> > > > 4) Updated elements in XML document as per
> > > > draft-ram-siprec-metadata-04
> > > > elements & associations
> > > >
> > > > 5) Changed appdata element name as extensiondata
> > > >
> > > > 6) Removed container element like sessions, participants,
> > > streams from
> > > > XML document as  parent reference exists in each element
> > > >
> > > > 7) Added Partial Update example & SIP usage XML+SDP example
> > > >
> > > > 8) Portion of security considerations section is added.
> > > >
> > > > Could you please review and provide your expert comments on
> > > the draft.
> > > >
> > > > Thanks
> > > > Partha
> > > >
> > > > -----Original Message-----
> > > > From: IETF I-D Submission Tool
> > [mailto:idsubmission@ietf.org <mailto:idsubmission@ietf.org> ]
> > > > Sent: Tuesday, March 08, 2011 7:31 PM
> > > > To: Parthasarathi R (partr)
> > > > Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > > > Subject: New Version Notification for
> > > > draft-ram-siprec-metadata-format-01
> > > >
> > > >
> > > > A new version of I-D,
> > > draft-ram-siprec-metadata-format-01.txt has been
> > > > successfully submitted by Parthasarathi R and posted to the IETF
> > > > repository.
> > > >
> > > > Filename:      draft-ram-siprec-metadata-format
> > > > Revision:      01
> > > > Title:                 Session Initiation Protocol (SIP)
> > > > Recording Metadata
> > > > Format
> > > > Creation_date:         2011-03-08
> > > > WG ID:                 Independent Submission
> > > > Number_of_pages: 20
> > > >
> > > > Abstract:
> > > > Session recording is a critical requirement in many
> communications
>=20
> > > > 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
>=20
> > > > to
> > > a recording
> > > > device.  The requirements for which are described in
> > > > [I-D.ietf-siprec-req], the architecture for which is described
in
> > > > [I-D.ietf-siprec-architecture], and the metadata model viewed by
> > > > Session Recording Server is described in
> > > > [I-D.ram-siprec-metadata].
> > > > This document focuses on the Recording metadata format
> > > which describes
> > > > the communication session.
> > > >
> > > >
> > > >
> > > >
> > > > The IETF Secretariat.
> > > >
> > > >
> > > > _______________________________________________
> > > > siprec mailing list
> > > > siprec@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/siprec
> > <https://www.ietf.org/mailman/listinfo/siprec>
> > > >
> > >
> > >
> > >
> >
> >
> >
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From pkyzivat@cisco.com  Mon Mar 14 06:09:05 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 643FA3A6D35 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 06:09:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.242
X-Spam-Level: 
X-Spam-Status: No, score=-110.242 tagged_above=-999 required=5 tests=[AWL=-0.243, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id stSDmwKn+j78 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 06:09:03 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 8942F3A6D17 for <siprec@ietf.org>; Mon, 14 Mar 2011 06:09:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=15817; q=dns/txt; s=iport; t=1300108227; x=1301317827; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=fe3aZd32SlLWpk3njgJ7w4Bp1s7lPux/KytPoHd51Xw=; b=UybvQh5xcMKJtQo+1L7YlXDwuXeVfq6oT3oo7ahJRl05VfFJQPReTR8D OTJ/qLP+auB5Z01pIWj4eg2NVJeDI+6fL22NaU8us8fm+pzEvK/cJlysH MxeyCG8pfwunn+pe0lXk7awo1IRavIHCoKn//xrzrIhAVV8pWjnL8S/O6 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvcAAAmxfU2tJXHB/2dsb2JhbACYQI1Fd6N1m0aCexsBgksEjFKDTg
X-IronPort-AV: E=Sophos;i="4.62,315,1297036800"; d="scan'208";a="276088142"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by sj-iport-4.cisco.com with ESMTP; 14 Mar 2011 13:10:26 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id p2EDAQ3J027297 for <siprec@ietf.org>; Mon, 14 Mar 2011 13:10:26 GMT
Message-ID: <4D7E13C1.1040905@cisco.com>
Date: Mon, 14 Mar 2011 09:10:25 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: siprec@ietf.org
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com>	<A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net>	<A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com>	<A444A0F8084434499206E78C106220CA086A89AE9E@MCHP058A.global-ad.net>	<A11921905DA1564D9BCF64A6430A62390293A69B@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AF11@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A89AF11@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 13:09:05 -0000

John,

We have been bouncing around different ways of accomplishing the task, 
and this is where we have gotten to. We may not have it quite right yet. 
Its a matter of factoring the model into objects with a suitable 
granularity wrt the way they are used and change. (Things look a bit 
different when you are concentrating on the encoding as xml than they do 
when viewed as an abstract model.)

Right now we are seeing an early step - coming up with an encoding and 
then seeing how it works out in practice. Then we can "stand back and 
look at it", and decide if we like what we see. So I expect that as we 
refine this there may be quite a bit of "fine tuning" - whether things 
are encoded as optional attributes of one object, or as separate objects.

	Thanks,
	Paul

On 3/14/2011 3:39 AM, Elwell, John wrote:
>
>
>> -----Original Message-----
>> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
>> Sent: 13 March 2011 14:15
>> To: Elwell, John; siprec@ietf.org
>> Subject: RE: [siprec] Review Request for
>> draft-ram-siprec-metadata-format-01
>>
>> John,
>>
>> Thanks for  further review of the draft and specific comments
>> on XML. Please read inline.
>>
>> Thanks
>> Partha
>>
>> ________________________________
>>
>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>> Sent: Sun 3/13/2011 4:11 PM
>> To: Parthasarathi R (partr); siprec@ietf.org
>> Subject: RE: [siprec] Review Request for
>> draft-ram-siprec-metadata-format-01
>>
>>
>>
>> So let's see if I understand correctly. Element extensionData
>> occurs in recording-metadata, as part of the sequence that
>> also contains things like session, participant, stream. The
>> element has attributes 'id' and 'parent' for linking the
>> extension data to other elements.
>>
>> Is this correct?
>>
>> <Partha>  Yeah, it is correct</partha>
>>
>>   I am not sure I understand the reasons for doing it this
>> way, but it seems it should work.
>>
>> <Partha>  Recording metadata is the main container of
>> rs-metadata+xml and it is the only one element which MUST be
>> passed in both Complete/Partial Metadata XML document. All
>> other metadata block (like stream, session, participant,
>> extension data) in the model shall be passed independently
>> from SRC and then, SRS will be able to correlate based on the
>> "id".
> [JRE] I see. So this allows entities other than the SRC to send metadata in this same format to the SRS, and furthermore those entities could send new or revised metadata for an object (group, session etc.) without repeating the object itself. I am not sure this is a requirement of the work, but it is certainly a property of the chosen solution.
>
>> The linkage is done so that the hierarchical blocks of
>> metadata model will be represented using the "id"
>> relationship in XML document which avoids extra namespace
>> during partial XML update. This design logic is applied in
>> the following elements:  group, session, stream, participant,
>> extensiondata as well. This proposed mechanism allows to
>> update only extensiondata alone as well if required. The
>> relationship of element&  parent element in metadata XML
>> document is as follows:
> [JRE] So it has the benefit that the SRS can send new or revised metadata for an object (group, session, etc.) without repeating the object itself. I am not sure whether this is a significant benefit - in such circumstances it might save a bit of XML, but it has the cost of transmitting an object's identifier every time that object is sent, so I am not convinced there is overall gain.
>
>>
>>      Element                           -             parent id name
>>
>> ----------------------------------------------------------------
>>
>>     group                                -             recording
>>
>>     session                           -              group
>>
>>     participant                       -              session
>>
>>     stream                             -              session
>>
>>     extensiondata                -              parent
>>
>> </Partha>
>> Some specific comments:
>>
>> 1. The schema shows 'id' and 'session' as the attributes of
>> extensionData - I assume 'session' should be 'parent'.
>> 2. Element extensionData also occurs in element participant
>> for some reason, according to the scheme. Is this also an error?
>> 3. In 4.2.2:
>> "recording-metadata element has recording, group, session, stream
>>     elements."
>> Participant seems to be missing (present in the example and
>> in the scheme).
>>
>> <Partha>  Thanks for pointing these error. I'll update the
>> text in the next revision</Partha>
>>
>> 4. The group element is missing from the schema (present in
>> the 4.2.2 and in the example).
>>
>> <Partha>  Group element is present in Sec 6 of schema.
> [JRE] Yes, I don't know how I missed it.
>
> John
>
>
>
>>
>> </xs:complexType>
>>     <xs:complexType name="group">
>>         <xs:sequence>
>>             <xs:element name="initiator" type="xs:anyURI"
>>              minOccurs="0" maxOccurs="1"/>   ====>  Will be
>> removed in the next revision as per below mail discussion
>>           <xs:element name="start-time" type="xs:dateTime"
>>                  minOccurs="0"/>
>>           <xs:element name="stop-time" type="xs:dateTime"
>>                  minOccurs="0"/>
>>         </xs:sequence>
>>         <xs:attribute name="id" type="xs:urnuuid"
>>              use"required"/>
>>         <xs:attribute name="recording" type="xs:urnuuid"
>>              use"required"/>
>>     </xs:complexType>
>>
>> Please let me know in case any other change has to be done in
>> the group element schema
>>
>> </Partha>
>> John (as individual)
>>
>>> -----Original Message-----
>>> From: Parthasarathi R (partr) [mailto:partr@cisco.com
>> <mailto:partr@cisco.com>  ]
>>> Sent: 12 March 2011 18:24
>>> To: Elwell, John; siprec@ietf.org
>>> Subject: RE: [siprec] Review Request for
>>> draft-ram-siprec-metadata-format-01
>>>
>>> John,
>>>
>>> Thanks for the detailed comments. Please read inline.
>>>
>>> Thanks
>>> Partha
>>>
>>> ________________________________
>>>
>>> From: Elwell, John
>> [mailto:john.elwell@siemens-enterprise.com
>> <mailto:john.elwell@siemens-enterprise.com>  ]
>>> Sent: Fri 3/11/2011 8:19 PM
>>> To: Parthasarathi R (partr); siprec@ietf.org
>>> Subject: RE: [siprec] Review Request for
>>> draft-ram-siprec-metadata-format-01
>>>
>>>
>>>
>>> Partha,
>>>
>>> I read -01 and have the following comments:
>>>
>>> 1. In section 3:
>>> "The media related details of metadata SHALL be passed across using
>>>     session description protocol (SDP) [RFC4566].  SDP attributes
>>>     describes about different media formats like audio, video."
>>> I wonder whether it is really appropriate to describe SDP
>>> attributes as part of the metadata. If I look at the metadata
>>> model, I don't see any attributes of a Media Stream object
>>> that could be satisfied using RS SDP. For example, the "codec
>>> parameters" attribute relates to the CS, not the RS - the two
>>> sessions could use different codecs or different codec
>>> parameters. I think it would be far simpler to regard all
>>> metadata as being sent in XML. Note that the SDP label
>>> attribute can still be used as the linkage between a Media
>>> Stream object in the metadata and the corresponding RS media
>>> stream that captures the CS media stream concerned.
>>>
>>> 2. We perhaps need to think about mixed RS media streams,
>>> i.e., where several CS media streams have been mixed to
>>> produce a single RS media stream. In this case, the several
>>> Media Stream objects would all point to the same SDP label, I
>>> guess. This then brings into question the mode element (type
>>> streamMode) - why is this needed? The fact that several Media
>>> Stream objects (stream elements) point to the same label
>>> would imply there has been mixing, so the mode element seems
>>> to be redundant.
>>>
>>> 3. Section 4.2.4:
>>> "Each group MAY have initiator entity attribute which contains SIP/
>>>     SIPS URI to identify the device which acts as Session Recording
>>>     Client (SRC).  The entity attribute SIP/SIPS URI FQDN or
>> IP address
>>>     represents the device and may not have user part."
>>> It is unclear to me why a URI identifying the SRC should be
>>> an attribute of a group element. I cannot find a
>>> corresponding attribute in the CS Group object in the
>>> metadata model draft.
>>>
>>> <Partha>  It is a good point. I missed to remove after our
>>> last interim meeting discussion. I'll remove in the next
>>> revision as there is no strong request for initiator of the
>>> session</Partha>
>>>
>>> 4. The example (section 5.1) seems rather odd, in that the
>>> recording-metadata element appears to comprise a sequence of
>>> elements (recording, group, session, etc.) alternating with
>>> extensiondata elements, i.e., there is an extensiondata
>>> element after each of the other elements. This probably
>>> complies with the schema, but what is the meaning of several
>>> extensiondata elements all within the same recording-metadata
>>> element?
>>>
>>> <Partha>  Each extensiondata has its own id and different
>>> parent id. Parent id shall be of recording, group, session
>>> etc., It is possible for each extension data to have
>>> different extended namespace which is specific to its parent.
>>>   But it is possible to uniquely identify within
>>> recording-metadata as it has its own unique id.</Partha>
>>>
>>> Why not just a single extensiondata element?
>>>
>>> <Partha>  It may not be preferred because it is tough to
>>> arrange extension data for a particular stream within the
>>> extension data of group. The individual extension data also
>>> provides flexibility to pass the specific extension-data
>>> during partial update in case other extension data is not
>>> modified.</Partha>
>>>
>>> Is any significance to be drawn from the fact that there is
>>> an extensiondata element following the recording element,
>>> another following the group element, etc.?
>>>
>>> <Partha>  As mentioned earlier, group mechanism may passed in
>>> group extensiondata  whereas retention policy of a specific
>>> session will be passed in session, recording extension data
>>> will have common attribute like os login shall be passed. It
>>> provides more flexibility and it is optional element, so it
>>> is required to pass whenever applicable only</Partha>
>>>
>>> 5. On the other hand, elements group, session, etc. seem to
>>> lack extensiondata elements - would it not be sensible to
>>> allow each of these to be extensible?
>>>
>>> <Partha>  Parent-id in extension data helps to link group,
>>> session to specific extension data</partha>
>>>
>>> 6. The method of sending partial metadata seems to imply that
>>> when a session, participant, stream etc. comes to an end, we
>>> send partial metadata indicating that the element concerned
>>> now has an end time. This seems implicitly to mean that the
>>> element ceases to exist - correct? So if the SRS were to
>>> request a snapshot of complete metadata, it would not receive
>>> any elements for which a stop time has previously been sent
>> - correct?
>>>
>>> <Partha>  Your understanding is correct, end-time will not
>>> passed across in case of SRS request for complete metadata as
>>> SRC may have lost the state</Partha>
>>>
>>>   I don't think I have an issue with this - I just wanted to
>>> confirm my understanding.
>>>
>>> John (as individual)
>>>
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org
>>>> [mailto:siprec-bounces@ietf.org
>> <mailto:siprec-bounces@ietf.org>  ] On Behalf Of Parthasarathi
>>> R (partr)
>>>> Sent: 08 March 2011 14:24
>>>> To: siprec@ietf.org
>>>> Subject: [siprec] Review Request for
>>>> draft-ram-siprec-metadata-format-01
>>>>
>>>> Hi all,
>>>>
>>>> As per the mailing list comments and interim meeting discussion, I
>>>> updated -01 draft of draft-ram-siprec-metadata-format and
>>> send it for
>>>> review. The draft is available at
>>>>
>> http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt
>>
>> <http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt>  . The
>>>> following update are done as part of -01 draft:
>>>>
>>>> 1) URN UUID (RFC 4122) mechanism is used as the unique id
>>>> mechanism for
>>>> relevant XML elements like group, session, stream, participant.
>>>>
>>>> 2) Partial XML passing in RS is supported by having unique
>>>> URN UUID for
>>>> group, session, stream, participant, recording, extension
>>>> data which are
>>>> directly under recording-metadata container/namespace.
>>>>
>>>> 3) Include recording-metadata element as a container element
>>>> instead of
>>>> recording element. This helps in avoiding duplicate data of
>>> recording
>>>> elements during the partial update
>>>>
>>>> 4) Updated elements in XML document as per
>>>> draft-ram-siprec-metadata-04
>>>> elements&  associations
>>>>
>>>> 5) Changed appdata element name as extensiondata
>>>>
>>>> 6) Removed container element like sessions, participants,
>>> streams from
>>>> XML document as  parent reference exists in each element
>>>>
>>>> 7) Added Partial Update example&  SIP usage XML+SDP example
>>>>
>>>> 8) Portion of security considerations section is added.
>>>>
>>>> Could you please review and provide your expert comments on
>>> the draft.
>>>>
>>>> Thanks
>>>> Partha
>>>>
>>>> -----Original Message-----
>>>> From: IETF I-D Submission Tool
>> [mailto:idsubmission@ietf.org<mailto:idsubmission@ietf.org>  ]
>>>> Sent: Tuesday, March 08, 2011 7:31 PM
>>>> To: Parthasarathi R (partr)
>>>> Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
>>>> Subject: New Version Notification for
>>>> draft-ram-siprec-metadata-format-01
>>>>
>>>>
>>>> A new version of I-D,
>>> draft-ram-siprec-metadata-format-01.txt has been
>>>> successfully submitted by Parthasarathi R and posted to the IETF
>>>> repository.
>>>>
>>>> Filename:      draft-ram-siprec-metadata-format
>>>> Revision:      01
>>>> Title:                 Session Initiation Protocol (SIP)
>>>> Recording Metadata
>>>> Format
>>>> Creation_date:         2011-03-08
>>>> WG ID:                 Independent Submission
>>>> Number_of_pages: 20
>>>>
>>>> Abstract:
>>>> 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.  The requirements for which are described in
>>>> [I-D.ietf-siprec-req], the architecture for which is described in
>>>> [I-D.ietf-siprec-architecture], and the metadata model viewed
>>>> by Session
>>>> Recording Server is described in [I-D.ram-siprec-metadata].
>>>> This document focuses on the Recording metadata format
>>> which describes
>>>> the communication session.
>>>>
>>>>
>>>>
>>>>
>>>> The IETF Secretariat.
>>>>
>>>>
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>> <https://www.ietf.org/mailman/listinfo/siprec>
>>>>
>>>
>>>
>>>
>>
>>
>>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>

From john.elwell@siemens-enterprise.com  Mon Mar 14 07:27:48 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B16F3A6D91 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 07:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.301, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J+zV4athQftI for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 07:27:47 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 520AC3A6D76 for <siprec@ietf.org>; Mon, 14 Mar 2011 07:27:46 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3739007; Mon, 14 Mar 2011 15:29:06 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 3021A1EB82B5; Mon, 14 Mar 2011 15:29:06 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 14 Mar 2011 15:29:06 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 14 Mar 2011 15:29:03 +0100
Thread-Topic: Partial Metadata XML document usage in SIPREC [was RE: [siprec] Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCAAP1pCbAAiRDpgAAbozsAAJbF5EAACzF/QAAu//FA=
Message-ID: <A444A0F8084434499206E78C106220CA086A89B223@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AE9E@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69B@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AF11@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A623904BE312E@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904BE312E@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Leon Portman <Leon.Portman@nice.com>, Henry Lum <Henry.Lum@alcatel-lucent.com>, "Peter Saint-Andre \(psaintan\)" <psaintan@cisco.com>
Subject: Re: [siprec] Partial Metadata XML document usage in SIPREC [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 14:27:48 -0000

OK, what I failed to appreciate was that the overhead of the identifier in =
each entity (group, session, etc.) is present independently of whether exte=
nsionData can be updated separately or only as part of the entity concerned=
. So given that we need partial updates, the identifier is needed anyway, r=
egardless of how we treat extensionData. Sorry for the confusion.

John (as individual)


> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 14 March 2011 12:34
> To: Elwell, John; siprec@ietf.org
> Cc: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Peter
> Saint-Andre (psaintan)
> Subject: Partial Metadata XML document usage in SIPREC [was
> RE: [siprec] Review Request for draft-ram-siprec-metadata-format-01]
>
> John & all,
>
> I complete agree with you that overhead of id inclusion in
> each Metadata
> block element in case partial metadata XML document has to be
> supported,
> there is no explicit requirement in SIPREC to solve this issue and -00
> version metadata format draft addresses for complete snapsnot of XML
> every time within single RS session. But I noticed in mailing
> alias and
> last SIPREC interim meeting comment that partial metadata
> support as an
> major open item (elephant) for metadata format draft. I'm including
> Leon, Henry, and Paul as they provided comments on partial metadata.
>
> I'm convinced for partial metadata XML document support because of the
> following reason:
>
> 1) The usage will be more beneficial for Persistent recording
> mechanism
> 2) In Call Center scenarios, Hold & Resume, transfer sort of
> mid-dialog
> service exist during most of the calls. Partial metadata
> update helps in
> these scenarios.
> 3) Universally Unique id is anyway required for group, session, stream
> element in XML which shall be used for partial XML passing as well.
>
> Also, We analyzed multiple partial metadata XML format:
>
> 1) Current mechanism of Metadata block level id and single container
> 2) RFC 5261 - An Extensible Markup Language (XML) Patch Operations
> Framework Utilizing XML  Path Language (XPath) Selectors
> 3) REST architecture for Metadata XML
>
> With above all mechanism, the current partial XML mechanism is the
> simplest mechanism which well fit for SIPREC. Including Peter in the
> mail thread to find any other simpler or less overhead
> mechanism exists
> in XML.
>
> Please let me know everyone opinion which way to go because this is a
> crucial decision point for metadata XML format.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Monday, March 14, 2011 1:09 PM
> To: Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
>
>
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > Sent: 13 March 2011 14:15
> > To: Elwell, John; siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > John,
> >
> > Thanks for  further review of the draft and specific
> comments on XML.
> > Please read inline.
> >
> > Thanks
> > Partha
> >
> > ________________________________
> >
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Sun 3/13/2011 4:11 PM
> > To: Parthasarathi R (partr); siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> >
> >
> > So let's see if I understand correctly. Element
> extensionData occurs
> > in recording-metadata, as part of the sequence that also contains
> > things like session, participant, stream. The element has
> attributes
> > 'id' and 'parent' for linking the extension data to other elements.
> >
> > Is this correct?
> >
> > <Partha> Yeah, it is correct </partha>
> >
> >  I am not sure I understand the reasons for doing it this
> way, but it
> > seems it should work.
> >
> > <Partha> Recording metadata is the main container of
> > rs-metadata+xml and it is the only one element which MUST be
> > passed in both Complete/Partial Metadata XML document. All other
> > metadata block (like stream, session, participant,
> extension data) in
> > the model shall be passed independently from SRC and then,
> SRS will be
>
> > able to correlate based on the "id".
> [JRE] I see. So this allows entities other than the SRC to
> send metadata
> in this same format to the SRS, and furthermore those entities could
> send new or revised metadata for an object (group, session
> etc.) without
> repeating the object itself. I am not sure this is a
> requirement of the
> work, but it is certainly a property of the chosen solution.
>
> > The linkage is done so that the hierarchical blocks of
> metadata model
> > will be represented using the "id"
> > relationship in XML document which avoids extra namespace during
> > partial XML update. This design logic is applied in the following
> > elements:  group, session, stream, participant,
> extensiondata as well.
>
> > This proposed mechanism allows to update only extensiondata
> alone as
> > well if required. The relationship of element & parent element in
> > metadata XML document is as follows:
> [JRE] So it has the benefit that the SRS can send new or revised
> metadata for an object (group, session, etc.) without repeating the
> object itself. I am not sure whether this is a significant
> benefit - in
> such circumstances it might save a bit of XML, but it has the cost of
> transmitting an object's identifier every time that object is
> sent, so I
> am not convinced there is overall gain.
>
> >
> >     Element                           -             parent id name
> >
> > ----------------------------------------------------------------
> >
> >    group                                -             recording
> >
> >    session                           -              group
> >
> >    participant                       -              session
> >
> >    stream                             -              session
> >
> >    extensiondata                -              parent
> >
> > </Partha>
> > Some specific comments:
> >
> > 1. The schema shows 'id' and 'session' as the attributes of
> > extensionData - I assume 'session' should be 'parent'.
> > 2. Element extensionData also occurs in element participant
> for some
> > reason, according to the scheme. Is this also an error?
> > 3. In 4.2.2:
> > "recording-metadata element has recording, group, session, stream
> >    elements."
> > Participant seems to be missing (present in the example and in the
> > scheme).
> >
> > <Partha> Thanks for pointing these error. I'll update the
> text in the
> > next revision </Partha>
> >
> > 4. The group element is missing from the schema (present in
> the 4.2.2
> > and in the example).
> >
> > <Partha> Group element is present in Sec 6 of schema.
> [JRE] Yes, I don't know how I missed it.
>
> John
>
>
>
> >
> > </xs:complexType>
> >    <xs:complexType name=3D"group">
> >        <xs:sequence>
> >            <xs:element name=3D"initiator" type=3D"xs:anyURI"
> >             minOccurs=3D"0" maxOccurs=3D"1"/>  =3D=3D=3D=3D> Will be re=
moved in
> > the next revision as per below mail discussion
> >          <xs:element name=3D"start-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >        </xs:sequence>
> >        <xs:attribute name=3D"id" type=3D"xs:urnuuid"
> >             use"required"/>
> >        <xs:attribute name=3D"recording" type=3D"xs:urnuuid"
> >             use"required"/>
> >    </xs:complexType>
> >
> > Please let me know in case any other change has to be done in the
> > group element schema
> >
> > </Partha>
> > John (as individual)
> >
> > > -----Original Message-----
> > > From: Parthasarathi R (partr) [mailto:partr@cisco.com
> > <mailto:partr@cisco.com> ]
> > > Sent: 12 March 2011 18:24
> > > To: Elwell, John; siprec@ietf.org
> > > Subject: RE: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > > John,
> > >
> > > Thanks for the detailed comments. Please read inline.
> > >
> > > Thanks
> > > Partha
> > >
> > > ________________________________
> > >
> > > From: Elwell, John
> > [mailto:john.elwell@siemens-enterprise.com
> > <mailto:john.elwell@siemens-enterprise.com> ]
> > > Sent: Fri 3/11/2011 8:19 PM
> > > To: Parthasarathi R (partr); siprec@ietf.org
> > > Subject: RE: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > >
> > >
> > > Partha,
> > >
> > > I read -01 and have the following comments:
> > >
> > > 1. In section 3:
> > > "The media related details of metadata SHALL be passed
> across using
> > >    session description protocol (SDP) [RFC4566].  SDP attributes
> > >    describes about different media formats like audio, video."
> > > I wonder whether it is really appropriate to describe SDP
> attributes
>
> > > as part of the metadata. If I look at the metadata model, I don't
> > > see any attributes of a Media Stream object that could be
> satisfied
> > > using RS SDP. For example, the "codec parameters"
> attribute relates
> > > to the CS, not the RS - the two sessions could use
> different codecs
> > > or different codec parameters. I think it would be far simpler to
> > > regard all metadata as being sent in XML. Note that the SDP label
> > > attribute can still be used as the linkage between a Media Stream
> > > object in the metadata and the corresponding RS media stream that
> > > captures the CS media stream concerned.
> > >
> > > 2. We perhaps need to think about mixed RS media streams, i.e.,
> > > where several CS media streams have been mixed to produce
> a single
> > > RS media stream. In this case, the several Media Stream objects
> > > would all point to the same SDP label, I guess. This then brings
> > > into question the mode element (type
> > > streamMode) - why is this needed? The fact that several
> Media Stream
>
> > > objects (stream elements) point to the same label would
> imply there
> > > has been mixing, so the mode element seems to be redundant.
> > >
> > > 3. Section 4.2.4:
> > > "Each group MAY have initiator entity attribute which
> contains SIP/
> > >    SIPS URI to identify the device which acts as Session Recording
> > >    Client (SRC).  The entity attribute SIP/SIPS URI FQDN or
> > IP address
> > >    represents the device and may not have user part."
> > > It is unclear to me why a URI identifying the SRC should be an
> > > attribute of a group element. I cannot find a corresponding
> > > attribute in the CS Group object in the metadata model draft.
> > >
> > > <Partha> It is a good point. I missed to remove after our last
> > > interim meeting discussion. I'll remove in the next revision as
> > > there is no strong request for initiator of the session </Partha>
> > >
> > > 4. The example (section 5.1) seems rather odd, in that the
> > > recording-metadata element appears to comprise a sequence of
> > > elements (recording, group, session, etc.) alternating with
> > > extensiondata elements, i.e., there is an extensiondata element
> > > after each of the other elements. This probably complies with the
> > > schema, but what is the meaning of several extensiondata elements
> > > all within the same recording-metadata element?
> > >
> > > <Partha> Each extensiondata has its own id and different
> parent id.
> > > Parent id shall be of recording, group, session etc., It
> is possible
>
> > > for each extension data to have different extended
> namespace which
> > > is specific to its parent.
> > >  But it is possible to uniquely identify within
> recording-metadata
> > > as it has its own unique id. </Partha>
> > >
> > > Why not just a single extensiondata element?
> > >
> > > <Partha> It may not be preferred because it is tough to arrange
> > > extension data for a particular stream within the
> extension data of
> > > group. The individual extension data also provides flexibility to
> > > pass the specific extension-data during partial update in
> case other
>
> > > extension data is not modified. </Partha>
> > >
> > > Is any significance to be drawn from the fact that there is an
> > > extensiondata element following the recording element, another
> > > following the group element, etc.?
> > >
> > > <Partha> As mentioned earlier, group mechanism may passed
> in group
> > > extensiondata  whereas retention policy of a specific
> session will
> > > be passed in session, recording extension data will have common
> > > attribute like os login shall be passed. It provides more
> > > flexibility and it is optional element, so it is required to pass
> > > whenever applicable only </Partha>
> > >
> > > 5. On the other hand, elements group, session, etc. seem to lack
> > > extensiondata elements - would it not be sensible to
> allow each of
> > > these to be extensible?
> > >
> > > <Partha> Parent-id in extension data helps to link group,
> session to
>
> > > specific extension data </partha>
> > >
> > > 6. The method of sending partial metadata seems to imply
> that when a
>
> > > session, participant, stream etc. comes to an end, we
> send partial
> > > metadata indicating that the element concerned now has an
> end time.
> > > This seems implicitly to mean that the element ceases to exist -
> > > correct? So if the SRS were to request a snapshot of complete
> > > metadata, it would not receive any elements for which a stop time
> > > has previously been sent
> > - correct?
> > >
> > > <Partha> Your understanding is correct, end-time will not passed
> > > across in case of SRS request for complete metadata as
> SRC may have
> > > lost the state</Partha>
> > >
> > >  I don't think I have an issue with this - I just wanted
> to confirm
> > > my understanding.
> > >
> > > John (as individual)
> > >
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org
> > <mailto:siprec-bounces@ietf.org> ] On Behalf Of Parthasarathi
> > > R (partr)
> > > > Sent: 08 March 2011 14:24
> > > > To: siprec@ietf.org
> > > > Subject: [siprec] Review Request for
> > > > draft-ram-siprec-metadata-format-01
> > > >
> > > > Hi all,
> > > >
> > > > As per the mailing list comments and interim meeting
> discussion, I
>
> > > > updated -01 draft of draft-ram-siprec-metadata-format and
> > > send it for
> > > > review. The draft is available at
> > > >
> > http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt
> >
> >
> <http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt> . The
> > > > following update are done as part of -01 draft:
> > > >
> > > > 1) URN UUID (RFC 4122) mechanism is used as the unique id
> > > > mechanism for relevant XML elements like group,
> session, stream,
> > > > participant.
> > > >
> > > > 2) Partial XML passing in RS is supported by having unique URN
> > > > UUID for group, session, stream, participant,
> recording, extension
>
> > > > data which are directly under recording-metadata
> > > > container/namespace.
> > > >
> > > > 3) Include recording-metadata element as a container element
> > > > instead of recording element. This helps in avoiding duplicate
> > > > data of
> > > recording
> > > > elements during the partial update
> > > >
> > > > 4) Updated elements in XML document as per
> > > > draft-ram-siprec-metadata-04
> > > > elements & associations
> > > >
> > > > 5) Changed appdata element name as extensiondata
> > > >
> > > > 6) Removed container element like sessions, participants,
> > > streams from
> > > > XML document as  parent reference exists in each element
> > > >
> > > > 7) Added Partial Update example & SIP usage XML+SDP example
> > > >
> > > > 8) Portion of security considerations section is added.
> > > >
> > > > Could you please review and provide your expert comments on
> > > the draft.
> > > >
> > > > Thanks
> > > > Partha
> > > >
> > > > -----Original Message-----
> > > > From: IETF I-D Submission Tool
> > [mailto:idsubmission@ietf.org <mailto:idsubmission@ietf.org> ]
> > > > Sent: Tuesday, March 08, 2011 7:31 PM
> > > > To: Parthasarathi R (partr)
> > > > Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > > > Subject: New Version Notification for
> > > > draft-ram-siprec-metadata-format-01
> > > >
> > > >
> > > > A new version of I-D,
> > > draft-ram-siprec-metadata-format-01.txt has been
> > > > successfully submitted by Parthasarathi R and posted to
> the IETF
> > > > repository.
> > > >
> > > > Filename:      draft-ram-siprec-metadata-format
> > > > Revision:      01
> > > > Title:                 Session Initiation Protocol (SIP)
> > > > Recording Metadata
> > > > Format
> > > > Creation_date:         2011-03-08
> > > > WG ID:                 Independent Submission
> > > > Number_of_pages: 20
> > > >
> > > > Abstract:
> > > > 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.  The requirements for which are described in
> > > > [I-D.ietf-siprec-req], the architecture for which is
> described in
> > > > [I-D.ietf-siprec-architecture], and the metadata model
> viewed by
> > > > Session Recording Server is described in
> > > > [I-D.ram-siprec-metadata].
> > > > This document focuses on the Recording metadata format
> > > which describes
> > > > the communication session.
> > > >
> > > >
> > > >
> > > >
> > > > The IETF Secretariat.
> > > >
> > > >
> > > > _______________________________________________
> > > > siprec mailing list
> > > > siprec@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/siprec
> > <https://www.ietf.org/mailman/listinfo/siprec>
> > > >
> > >
> > >
> > >
> >
> >
> >
>

From john.elwell@siemens-enterprise.com  Mon Mar 14 08:48:17 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 35BF23A6DEE for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 08:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5ut6wt0HABI for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 08:48:16 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id D2F2C3A6D68 for <siprec@ietf.org>; Mon, 14 Mar 2011 08:48:12 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3734919 for siprec@ietf.org; Mon, 14 Mar 2011 16:49:35 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 707B21EB82B5 for <siprec@ietf.org>; Mon, 14 Mar 2011 16:49:35 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 14 Mar 2011 16:49:35 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 14 Mar 2011 16:49:33 +0100
Thread-Topic: Draft agenda
Thread-Index: AcviX2mieA/3k9OlQa2mJQnrQUlqHA==
Message-ID: <A444A0F8084434499206E78C106220CA086A89B2AF@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] Draft agenda
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 15:48:17 -0000

http://www.ietf.org/proceedings/80/agenda/siprec.htm
I see the main topics for Prague as being the protocol and the metadata for=
mat. I expect we will have adopted the metadata model draft as work item, a=
nd although there are no issues at present, discussion between now and then=
 might identify something for discussion, so I allowed a lesser amount of t=
ime on that. I assume the requirements draft will be out of our hands by th=
en, and I am not aware of anything to be discussed on the architecture draf=
t.

Please let me have any changes.

John

From partr@cisco.com  Mon Mar 14 08:55:07 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7130F3A6929 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 08:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.106
X-Spam-Level: 
X-Spam-Status: No, score=-9.106 tagged_above=-999 required=5 tests=[AWL=-0.504, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7JCEF+6Kuuh for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 08:55:03 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 2D91A3A6B40 for <siprec@ietf.org>; Mon, 14 Mar 2011 08:55:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=48648; q=dns/txt; s=iport; t=1300118184; x=1301327784; h=mime-version:subject:date:message-id:references:from:to: cc; bh=VJw/qqWrEqT2mT3B6TJHT29J93rf4q7Nk9OqWJJP/80=; b=Xsn2V0O+M0Xjq65guHUNASuuVOlKUdx7qKMRmLXIQ7CSpnXIJ5dGrmWL VE/ARV8leFYlfpgFL7CUBBhin3REGFq13x45uuxBMJuWi2tXH10Fix6Fd LaC/kkobZFIxbnZ8XgWXqFlW1yXiUd0DGhPWOe1J3LvvXbm0XHmV3RLP7 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuIAAKrXfU2Q/khNgWdsb2JhbACYRIxzUhQBARYmJaQjnAGCexsBgksEhSmKfQ
X-IronPort-AV: E=Sophos;i="4.62,316,1297036800"; d="scan'208,217";a="21644457"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 14 Mar 2011 15:56:22 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2EFuD0i031546; Mon, 14 Mar 2011 15:56:22 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Mar 2011 21:26:21 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE260.5CFE6817"
Date: Mon, 14 Mar 2011 21:21:48 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A69C@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Partial Metadata XML document usage in SIPREC [was RE: [siprec] Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: AcvdmYMWyu0eMrvoQl+YDbOfNvShlAAABJfwAJHBwCAAP1pCbAAiRDpgAAbozsAAJbF5EAACzF/QAAu//FAAAwJnLQ==
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69A@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AE9E@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A69B@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AF11@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A623904BE312E@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89B223@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 14 Mar 2011 15:56:21.0865 (UTC) FILETIME=[5D347D90:01CBE260]
Cc: Leon Portman <Leon.Portman@nice.com>, Henry Lum <Henry.Lum@alcatel-lucent.com>, "Peter Saint-Andre \(psaintan\)" <psaintan@cisco.com>
Subject: Re: [siprec] Partial Metadata XML document usage in SIPREC [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 15:55:07 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE260.5CFE6817
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John,
=20
Thanks for accepting the partial metadata mechanism in the draft.=20
=20
Thanks
Partha

________________________________

From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
Sent: Mon 3/14/2011 7:59 PM
To: Parthasarathi R (partr); siprec@ietf.org
Cc: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Peter Saint-Andre =
(psaintan)
Subject: RE: Partial Metadata XML document usage in SIPREC [was RE: =
[siprec] Review Request for draft-ram-siprec-metadata-format-01]



OK, what I failed to appreciate was that the overhead of the identifier =
in each entity (group, session, etc.) is present independently of =
whether extensionData can be updated separately or only as part of the =
entity concerned. So given that we need partial updates, the identifier =
is needed anyway, regardless of how we treat extensionData. Sorry for =
the confusion.

John (as individual)


> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 14 March 2011 12:34
> To: Elwell, John; siprec@ietf.org
> Cc: Leon Portman; Henry Lum; Paul Kyzivat (pkyzivat); Peter
> Saint-Andre (psaintan)
> Subject: Partial Metadata XML document usage in SIPREC [was
> RE: [siprec] Review Request for draft-ram-siprec-metadata-format-01]
>
> John & all,
>
> I complete agree with you that overhead of id inclusion in
> each Metadata
> block element in case partial metadata XML document has to be
> supported,
> there is no explicit requirement in SIPREC to solve this issue and -00
> version metadata format draft addresses for complete snapsnot of XML
> every time within single RS session. But I noticed in mailing
> alias and
> last SIPREC interim meeting comment that partial metadata
> support as an
> major open item (elephant) for metadata format draft. I'm including
> Leon, Henry, and Paul as they provided comments on partial metadata.
>
> I'm convinced for partial metadata XML document support because of the
> following reason:
>
> 1) The usage will be more beneficial for Persistent recording
> mechanism
> 2) In Call Center scenarios, Hold & Resume, transfer sort of
> mid-dialog
> service exist during most of the calls. Partial metadata
> update helps in
> these scenarios.
> 3) Universally Unique id is anyway required for group, session, stream
> element in XML which shall be used for partial XML passing as well.
>
> Also, We analyzed multiple partial metadata XML format:
>
> 1) Current mechanism of Metadata block level id and single container
> 2) RFC 5261 - An Extensible Markup Language (XML) Patch Operations
> Framework Utilizing XML  Path Language (XPath) Selectors
> 3) REST architecture for Metadata XML
>
> With above all mechanism, the current partial XML mechanism is the
> simplest mechanism which well fit for SIPREC. Including Peter in the
> mail thread to find any other simpler or less overhead
> mechanism exists
> in XML.
>
> Please let me know everyone opinion which way to go because this is a
> crucial decision point for metadata XML format.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Monday, March 14, 2011 1:09 PM
> To: Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
>
>
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > Sent: 13 March 2011 14:15
> > To: Elwell, John; siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > John,
> >
> > Thanks for  further review of the draft and specific
> comments on XML.
> > Please read inline.
> >
> > Thanks
> > Partha
> >
> > ________________________________
> >
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Sun 3/13/2011 4:11 PM
> > To: Parthasarathi R (partr); siprec@ietf.org
> > Subject: RE: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> >
> >
> > So let's see if I understand correctly. Element
> extensionData occurs
> > in recording-metadata, as part of the sequence that also contains
> > things like session, participant, stream. The element has
> attributes
> > 'id' and 'parent' for linking the extension data to other elements.
> >
> > Is this correct?
> >
> > <Partha> Yeah, it is correct </partha>
> >
> >  I am not sure I understand the reasons for doing it this
> way, but it
> > seems it should work.
> >
> > <Partha> Recording metadata is the main container of
> > rs-metadata+xml and it is the only one element which MUST be
> > passed in both Complete/Partial Metadata XML document. All other
> > metadata block (like stream, session, participant,
> extension data) in
> > the model shall be passed independently from SRC and then,
> SRS will be
>
> > able to correlate based on the "id".
> [JRE] I see. So this allows entities other than the SRC to
> send metadata
> in this same format to the SRS, and furthermore those entities could
> send new or revised metadata for an object (group, session
> etc.) without
> repeating the object itself. I am not sure this is a
> requirement of the
> work, but it is certainly a property of the chosen solution.
>
> > The linkage is done so that the hierarchical blocks of
> metadata model
> > will be represented using the "id"
> > relationship in XML document which avoids extra namespace during
> > partial XML update. This design logic is applied in the following
> > elements:  group, session, stream, participant,
> extensiondata as well.
>
> > This proposed mechanism allows to update only extensiondata
> alone as
> > well if required. The relationship of element & parent element in
> > metadata XML document is as follows:
> [JRE] So it has the benefit that the SRS can send new or revised
> metadata for an object (group, session, etc.) without repeating the
> object itself. I am not sure whether this is a significant
> benefit - in
> such circumstances it might save a bit of XML, but it has the cost of
> transmitting an object's identifier every time that object is
> sent, so I
> am not convinced there is overall gain.
>
> >
> >     Element                           -             parent id name
> >
> > ----------------------------------------------------------------
> >
> >    group                                -             recording
> >
> >    session                           -              group
> >
> >    participant                       -              session
> >
> >    stream                             -              session
> >
> >    extensiondata                -              parent
> >
> > </Partha>
> > Some specific comments:
> >
> > 1. The schema shows 'id' and 'session' as the attributes of
> > extensionData - I assume 'session' should be 'parent'.
> > 2. Element extensionData also occurs in element participant
> for some
> > reason, according to the scheme. Is this also an error?
> > 3. In 4.2.2:
> > "recording-metadata element has recording, group, session, stream
> >    elements."
> > Participant seems to be missing (present in the example and in the
> > scheme).
> >
> > <Partha> Thanks for pointing these error. I'll update the
> text in the
> > next revision </Partha>
> >
> > 4. The group element is missing from the schema (present in
> the 4.2.2
> > and in the example).
> >
> > <Partha> Group element is present in Sec 6 of schema.
> [JRE] Yes, I don't know how I missed it.
>
> John
>
>
>
> >
> > </xs:complexType>
> >    <xs:complexType name=3D"group">
> >        <xs:sequence>
> >            <xs:element name=3D"initiator" type=3D"xs:anyURI"
> >             minOccurs=3D"0" maxOccurs=3D"1"/>  =3D=3D=3D=3D> Will be =
removed in
> > the next revision as per below mail discussion
> >          <xs:element name=3D"start-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >        </xs:sequence>
> >        <xs:attribute name=3D"id" type=3D"xs:urnuuid"
> >             use"required"/>
> >        <xs:attribute name=3D"recording" type=3D"xs:urnuuid"
> >             use"required"/>
> >    </xs:complexType>
> >
> > Please let me know in case any other change has to be done in the
> > group element schema
> >
> > </Partha>
> > John (as individual)
> >
> > > -----Original Message-----
> > > From: Parthasarathi R (partr) [mailto:partr@cisco.com
> > <mailto:partr@cisco.com> ]
> > > Sent: 12 March 2011 18:24
> > > To: Elwell, John; siprec@ietf.org
> > > Subject: RE: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > > John,
> > >
> > > Thanks for the detailed comments. Please read inline.
> > >
> > > Thanks
> > > Partha
> > >
> > > ________________________________
> > >
> > > From: Elwell, John
> > [mailto:john.elwell@siemens-enterprise.com
> > <mailto:john.elwell@siemens-enterprise.com> ]
> > > Sent: Fri 3/11/2011 8:19 PM
> > > To: Parthasarathi R (partr); siprec@ietf.org
> > > Subject: RE: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > >
> > >
> > > Partha,
> > >
> > > I read -01 and have the following comments:
> > >
> > > 1. In section 3:
> > > "The media related details of metadata SHALL be passed
> across using
> > >    session description protocol (SDP) [RFC4566].  SDP attributes
> > >    describes about different media formats like audio, video."
> > > I wonder whether it is really appropriate to describe SDP
> attributes
>
> > > as part of the metadata. If I look at the metadata model, I don't
> > > see any attributes of a Media Stream object that could be
> satisfied
> > > using RS SDP. For example, the "codec parameters"
> attribute relates
> > > to the CS, not the RS - the two sessions could use
> different codecs
> > > or different codec parameters. I think it would be far simpler to
> > > regard all metadata as being sent in XML. Note that the SDP label
> > > attribute can still be used as the linkage between a Media Stream
> > > object in the metadata and the corresponding RS media stream that
> > > captures the CS media stream concerned.
> > >
> > > 2. We perhaps need to think about mixed RS media streams, i.e.,
> > > where several CS media streams have been mixed to produce
> a single
> > > RS media stream. In this case, the several Media Stream objects
> > > would all point to the same SDP label, I guess. This then brings
> > > into question the mode element (type
> > > streamMode) - why is this needed? The fact that several
> Media Stream
>
> > > objects (stream elements) point to the same label would
> imply there
> > > has been mixing, so the mode element seems to be redundant.
> > >
> > > 3. Section 4.2.4:
> > > "Each group MAY have initiator entity attribute which
> contains SIP/
> > >    SIPS URI to identify the device which acts as Session Recording
> > >    Client (SRC).  The entity attribute SIP/SIPS URI FQDN or
> > IP address
> > >    represents the device and may not have user part."
> > > It is unclear to me why a URI identifying the SRC should be an
> > > attribute of a group element. I cannot find a corresponding
> > > attribute in the CS Group object in the metadata model draft.
> > >
> > > <Partha> It is a good point. I missed to remove after our last
> > > interim meeting discussion. I'll remove in the next revision as
> > > there is no strong request for initiator of the session </Partha>
> > >
> > > 4. The example (section 5.1) seems rather odd, in that the
> > > recording-metadata element appears to comprise a sequence of
> > > elements (recording, group, session, etc.) alternating with
> > > extensiondata elements, i.e., there is an extensiondata element
> > > after each of the other elements. This probably complies with the
> > > schema, but what is the meaning of several extensiondata elements
> > > all within the same recording-metadata element?
> > >
> > > <Partha> Each extensiondata has its own id and different
> parent id.
> > > Parent id shall be of recording, group, session etc., It
> is possible
>
> > > for each extension data to have different extended
> namespace which
> > > is specific to its parent.
> > >  But it is possible to uniquely identify within
> recording-metadata
> > > as it has its own unique id. </Partha>
> > >
> > > Why not just a single extensiondata element?
> > >
> > > <Partha> It may not be preferred because it is tough to arrange
> > > extension data for a particular stream within the
> extension data of
> > > group. The individual extension data also provides flexibility to
> > > pass the specific extension-data during partial update in
> case other
>
> > > extension data is not modified. </Partha>
> > >
> > > Is any significance to be drawn from the fact that there is an
> > > extensiondata element following the recording element, another
> > > following the group element, etc.?
> > >
> > > <Partha> As mentioned earlier, group mechanism may passed
> in group
> > > extensiondata  whereas retention policy of a specific
> session will
> > > be passed in session, recording extension data will have common
> > > attribute like os login shall be passed. It provides more
> > > flexibility and it is optional element, so it is required to pass
> > > whenever applicable only </Partha>
> > >
> > > 5. On the other hand, elements group, session, etc. seem to lack
> > > extensiondata elements - would it not be sensible to
> allow each of
> > > these to be extensible?
> > >
> > > <Partha> Parent-id in extension data helps to link group,
> session to
>
> > > specific extension data </partha>
> > >
> > > 6. The method of sending partial metadata seems to imply
> that when a
>
> > > session, participant, stream etc. comes to an end, we
> send partial
> > > metadata indicating that the element concerned now has an
> end time.
> > > This seems implicitly to mean that the element ceases to exist -
> > > correct? So if the SRS were to request a snapshot of complete
> > > metadata, it would not receive any elements for which a stop time
> > > has previously been sent
> > - correct?
> > >
> > > <Partha> Your understanding is correct, end-time will not passed
> > > across in case of SRS request for complete metadata as
> SRC may have
> > > lost the state</Partha>
> > >
> > >  I don't think I have an issue with this - I just wanted
> to confirm
> > > my understanding.
> > >
> > > John (as individual)
> > >
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org
> > <mailto:siprec-bounces@ietf.org> ] On Behalf Of Parthasarathi
> > > R (partr)
> > > > Sent: 08 March 2011 14:24
> > > > To: siprec@ietf.org
> > > > Subject: [siprec] Review Request for
> > > > draft-ram-siprec-metadata-format-01
> > > >
> > > > Hi all,
> > > >
> > > > As per the mailing list comments and interim meeting
> discussion, I
>
> > > > updated -01 draft of draft-ram-siprec-metadata-format and
> > > send it for
> > > > review. The draft is available at
> > > >
> > http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt
> >
> >
> <http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt> . The
> > > > following update are done as part of -01 draft:
> > > >
> > > > 1) URN UUID (RFC 4122) mechanism is used as the unique id
> > > > mechanism for relevant XML elements like group,
> session, stream,
> > > > participant.
> > > >
> > > > 2) Partial XML passing in RS is supported by having unique URN
> > > > UUID for group, session, stream, participant,
> recording, extension
>
> > > > data which are directly under recording-metadata
> > > > container/namespace.
> > > >
> > > > 3) Include recording-metadata element as a container element
> > > > instead of recording element. This helps in avoiding duplicate
> > > > data of
> > > recording
> > > > elements during the partial update
> > > >
> > > > 4) Updated elements in XML document as per
> > > > draft-ram-siprec-metadata-04
> > > > elements & associations
> > > >
> > > > 5) Changed appdata element name as extensiondata
> > > >
> > > > 6) Removed container element like sessions, participants,
> > > streams from
> > > > XML document as  parent reference exists in each element
> > > >
> > > > 7) Added Partial Update example & SIP usage XML+SDP example
> > > >
> > > > 8) Portion of security considerations section is added.
> > > >
> > > > Could you please review and provide your expert comments on
> > > the draft.
> > > >
> > > > Thanks
> > > > Partha
> > > >
> > > > -----Original Message-----
> > > > From: IETF I-D Submission Tool
> > [mailto:idsubmission@ietf.org <mailto:idsubmission@ietf.org> ]
> > > > Sent: Tuesday, March 08, 2011 7:31 PM
> > > > To: Parthasarathi R (partr)
> > > > Cc: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > > > Subject: New Version Notification for
> > > > draft-ram-siprec-metadata-format-01
> > > >
> > > >
> > > > A new version of I-D,
> > > draft-ram-siprec-metadata-format-01.txt has been
> > > > successfully submitted by Parthasarathi R and posted to
> the IETF
> > > > repository.
> > > >
> > > > Filename:      draft-ram-siprec-metadata-format
> > > > Revision:      01
> > > > Title:                 Session Initiation Protocol (SIP)
> > > > Recording Metadata
> > > > Format
> > > > Creation_date:         2011-03-08
> > > > WG ID:                 Independent Submission
> > > > Number_of_pages: 20
> > > >
> > > > Abstract:
> > > > 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.  The requirements for which are described in
> > > > [I-D.ietf-siprec-req], the architecture for which is
> described in
> > > > [I-D.ietf-siprec-architecture], and the metadata model
> viewed by
> > > > Session Recording Server is described in
> > > > [I-D.ram-siprec-metadata].
> > > > This document focuses on the Recording metadata format
> > > which describes
> > > > the communication session.
> > > >
> > > >
> > > >
> > > >
> > > > The IETF Secretariat.
> > > >
> > > >
> > > > _______________________________________________
> > > > siprec mailing list
> > > > siprec@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/siprec
> > <https://www.ietf.org/mailman/listinfo/siprec>
> > > >
> > >
> > >
> > >
> >
> >
> >
>



------_=_NextPart_001_01CBE260.5CFE6817
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: Partial Metadata XML document usage in =
SIPREC [was RE: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01]</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText4018>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 =
face=3DArial>John,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks for accepting the =
partial metadata mechanism in the draft. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT><FONT size=3D2 =
face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> Elwell, John =
[mailto:john.elwell@siemens-enterprise.com]<BR><B>Sent:</B> Mon =
3/14/2011 7:59 PM<BR><B>To:</B> Parthasarathi R (partr); =
siprec@ietf.org<BR><B>Cc:</B> Leon Portman; Henry Lum; Paul Kyzivat =
(pkyzivat); Peter Saint-Andre (psaintan)<BR><B>Subject:</B> RE: Partial =
Metadata XML document usage in SIPREC [was RE: [siprec] Review Request =
for draft-ram-siprec-metadata-format-01]<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>OK, what I failed to appreciate was that the overhead =
of the identifier in each entity (group, session, etc.) is present =
independently of whether extensionData can be updated separately or only =
as part of the entity concerned. So given that we need partial updates, =
the identifier is needed anyway, regardless of how we treat =
extensionData. Sorry for the confusion.<BR><BR>John (as =
individual)<BR><BR><BR>&gt; -----Original Message-----<BR>&gt; From: =
Parthasarathi R (partr) [<A =
href=3D"mailto:partr@cisco.com">mailto:partr@cisco.com</A>]<BR>&gt; =
Sent: 14 March 2011 12:34<BR>&gt; To: Elwell, John; =
siprec@ietf.org<BR>&gt; Cc: Leon Portman; Henry Lum; Paul Kyzivat =
(pkyzivat); Peter<BR>&gt; Saint-Andre (psaintan)<BR>&gt; Subject: =
Partial Metadata XML document usage in SIPREC [was<BR>&gt; RE: [siprec] =
Review Request for draft-ram-siprec-metadata-format-01]<BR>&gt;<BR>&gt; =
John &amp; all,<BR>&gt;<BR>&gt; I complete agree with you that overhead =
of id inclusion in<BR>&gt; each Metadata<BR>&gt; block element in case =
partial metadata XML document has to be<BR>&gt; supported,<BR>&gt; there =
is no explicit requirement in SIPREC to solve this issue and -00<BR>&gt; =
version metadata format draft addresses for complete snapsnot of =
XML<BR>&gt; every time within single RS session. But I noticed in =
mailing<BR>&gt; alias and<BR>&gt; last SIPREC interim meeting comment =
that partial metadata<BR>&gt; support as an<BR>&gt; major open item =
(elephant) for metadata format draft. I'm including<BR>&gt; Leon, Henry, =
and Paul as they provided comments on partial metadata.<BR>&gt;<BR>&gt; =
I'm convinced for partial metadata XML document support because of =
the<BR>&gt; following reason:<BR>&gt;<BR>&gt; 1) The usage will be more =
beneficial for Persistent recording<BR>&gt; mechanism<BR>&gt; 2) In Call =
Center scenarios, Hold &amp; Resume, transfer sort of<BR>&gt; =
mid-dialog<BR>&gt; service exist during most of the calls. Partial =
metadata<BR>&gt; update helps in<BR>&gt; these scenarios.<BR>&gt; 3) =
Universally Unique id is anyway required for group, session, =
stream<BR>&gt; element in XML which shall be used for partial XML =
passing as well.<BR>&gt;<BR>&gt; Also, We analyzed multiple partial =
metadata XML format:<BR>&gt;<BR>&gt; 1) Current mechanism of Metadata =
block level id and single container<BR>&gt; 2) RFC 5261 - An Extensible =
Markup Language (XML) Patch Operations<BR>&gt; Framework Utilizing =
XML&nbsp; Path Language (XPath) Selectors<BR>&gt; 3) REST architecture =
for Metadata XML<BR>&gt;<BR>&gt; With above all mechanism, the current =
partial XML mechanism is the<BR>&gt; simplest mechanism which well fit =
for SIPREC. Including Peter in the<BR>&gt; mail thread to find any other =
simpler or less overhead<BR>&gt; mechanism exists<BR>&gt; in =
XML.<BR>&gt;<BR>&gt; Please let me know everyone opinion which way to go =
because this is a<BR>&gt; crucial decision point for metadata XML =
format.<BR>&gt;<BR>&gt; Thanks<BR>&gt; Partha<BR>&gt;<BR>&gt; =
-----Original Message-----<BR>&gt; From: Elwell, John [<A =
href=3D"mailto:john.elwell@siemens-enterprise.com">mailto:john.elwell@sie=
mens-enterprise.com</A>]<BR>&gt; Sent: Monday, March 14, 2011 1:09 =
PM<BR>&gt; To: Parthasarathi R (partr); siprec@ietf.org<BR>&gt; Subject: =
RE: [siprec] Review Request for<BR>&gt; =
draft-ram-siprec-metadata-format-01<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; &gt; =
-----Original Message-----<BR>&gt; &gt; From: Parthasarathi R (partr) =
[<A href=3D"mailto:partr@cisco.com">mailto:partr@cisco.com</A>]<BR>&gt; =
&gt; Sent: 13 March 2011 14:15<BR>&gt; &gt; To: Elwell, John; =
siprec@ietf.org<BR>&gt; &gt; Subject: RE: [siprec] Review Request =
for<BR>&gt; &gt; draft-ram-siprec-metadata-format-01<BR>&gt; =
&gt;<BR>&gt; &gt; John,<BR>&gt; &gt;<BR>&gt; &gt; Thanks for&nbsp; =
further review of the draft and specific<BR>&gt; comments on =
XML.<BR>&gt; &gt; Please read inline.<BR>&gt; &gt;<BR>&gt; &gt; =
Thanks<BR>&gt; &gt; Partha<BR>&gt; &gt;<BR>&gt; &gt; =
________________________________<BR>&gt; &gt;<BR>&gt; &gt; From: Elwell, =
John [<A =
href=3D"mailto:john.elwell@siemens-enterprise.com">mailto:john.elwell@sie=
mens-enterprise.com</A>]<BR>&gt; &gt; Sent: Sun 3/13/2011 4:11 =
PM<BR>&gt; &gt; To: Parthasarathi R (partr); siprec@ietf.org<BR>&gt; =
&gt; Subject: RE: [siprec] Review Request for<BR>&gt; &gt; =
draft-ram-siprec-metadata-format-01<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; =
&gt;<BR>&gt; &gt; So let's see if I understand correctly. =
Element<BR>&gt; extensionData occurs<BR>&gt; &gt; in recording-metadata, =
as part of the sequence that also contains<BR>&gt; &gt; things like =
session, participant, stream. The element has<BR>&gt; attributes<BR>&gt; =
&gt; 'id' and 'parent' for linking the extension data to other =
elements.<BR>&gt; &gt;<BR>&gt; &gt; Is this correct?<BR>&gt; =
&gt;<BR>&gt; &gt; &lt;Partha&gt; Yeah, it is correct =
&lt;/partha&gt;<BR>&gt; &gt;<BR>&gt; &gt;&nbsp; I am not sure I =
understand the reasons for doing it this<BR>&gt; way, but it<BR>&gt; =
&gt; seems it should work.<BR>&gt; &gt;<BR>&gt; &gt; &lt;Partha&gt; =
Recording metadata is the main container of<BR>&gt; &gt; rs-metadata+xml =
and it is the only one element which MUST be<BR>&gt; &gt; passed in both =
Complete/Partial Metadata XML document. All other<BR>&gt; &gt; metadata =
block (like stream, session, participant,<BR>&gt; extension data) =
in<BR>&gt; &gt; the model shall be passed independently from SRC and =
then,<BR>&gt; SRS will be<BR>&gt;<BR>&gt; &gt; able to correlate based =
on the "id".<BR>&gt; [JRE] I see. So this allows entities other than the =
SRC to<BR>&gt; send metadata<BR>&gt; in this same format to the SRS, and =
furthermore those entities could<BR>&gt; send new or revised metadata =
for an object (group, session<BR>&gt; etc.) without<BR>&gt; repeating =
the object itself. I am not sure this is a<BR>&gt; requirement of =
the<BR>&gt; work, but it is certainly a property of the chosen =
solution.<BR>&gt;<BR>&gt; &gt; The linkage is done so that the =
hierarchical blocks of<BR>&gt; metadata model<BR>&gt; &gt; will be =
represented using the "id"<BR>&gt; &gt; relationship in XML document =
which avoids extra namespace during<BR>&gt; &gt; partial XML update. =
This design logic is applied in the following<BR>&gt; &gt; =
elements:&nbsp; group, session, stream, participant,<BR>&gt; =
extensiondata as well.<BR>&gt;<BR>&gt; &gt; This proposed mechanism =
allows to update only extensiondata<BR>&gt; alone as<BR>&gt; &gt; well =
if required. The relationship of element &amp; parent element in<BR>&gt; =
&gt; metadata XML document is as follows:<BR>&gt; [JRE] So it has the =
benefit that the SRS can send new or revised<BR>&gt; metadata for an =
object (group, session, etc.) without repeating the<BR>&gt; object =
itself. I am not sure whether this is a significant<BR>&gt; benefit - =
in<BR>&gt; such circumstances it might save a bit of XML, but it has the =
cost of<BR>&gt; transmitting an object's identifier every time that =
object is<BR>&gt; sent, so I<BR>&gt; am not convinced there is overall =
gain.<BR>&gt;<BR>&gt; &gt;<BR>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; =
Element&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; =
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 parent id name<BR>&gt; &gt;<BR>&gt; &gt; =
----------------------------------------------------------------<BR>&gt; =
&gt;<BR>&gt; &gt;&nbsp;&nbsp;&nbsp; =
group&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 recording<BR>&gt; &gt;<BR>&gt; &gt;&nbsp;&nbsp;&nbsp; =
session&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; =
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; group<BR>&gt; &gt;<BR>&gt; &gt;&nbsp;&nbsp;&nbsp; =
participant&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; session<BR>&gt; &gt;<BR>&gt; &gt;&nbsp;&nbsp;&nbsp; =
stream&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; session<BR>&gt; &gt;<BR>&gt; &gt;&nbsp;&nbsp;&nbsp; =
extensiondata&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; parent<BR>&gt; &gt;<BR>&gt; &gt; &lt;/Partha&gt;<BR>&gt; &gt; =
Some specific comments:<BR>&gt; &gt;<BR>&gt; &gt; 1. The schema shows =
'id' and 'session' as the attributes of<BR>&gt; &gt; extensionData - I =
assume 'session' should be 'parent'.<BR>&gt; &gt; 2. Element =
extensionData also occurs in element participant<BR>&gt; for =
some<BR>&gt; &gt; reason, according to the scheme. Is this also an =
error?<BR>&gt; &gt; 3. In 4.2.2:<BR>&gt; &gt; "recording-metadata =
element has recording, group, session, stream<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp; elements."<BR>&gt; &gt; Participant seems to be =
missing (present in the example and in the<BR>&gt; &gt; scheme).<BR>&gt; =
&gt;<BR>&gt; &gt; &lt;Partha&gt; Thanks for pointing these error. I'll =
update the<BR>&gt; text in the<BR>&gt; &gt; next revision =
&lt;/Partha&gt;<BR>&gt; &gt;<BR>&gt; &gt; 4. The group element is =
missing from the schema (present in<BR>&gt; the 4.2.2<BR>&gt; &gt; and =
in the example).<BR>&gt; &gt;<BR>&gt; &gt; &lt;Partha&gt; Group element =
is present in Sec 6 of schema.<BR>&gt; [JRE] Yes, I don't know how I =
missed it.<BR>&gt;<BR>&gt; John<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; =
&gt;<BR>&gt; &gt; &lt;/xs:complexType&gt;<BR>&gt; &gt;&nbsp;&nbsp;&nbsp; =
&lt;xs:complexType name=3D"group"&gt;<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:sequence&gt;<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element name=3D"initiator" type=3D"xs:anyURI"<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; minOccurs=3D"0" maxOccurs=3D"1"/&gt;&nbsp; =3D=3D=3D=3D&gt; Will be =
removed in<BR>&gt; &gt; the next revision as per below mail =
discussion<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element name=3D"start-time" type=3D"xs:dateTime"<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs=3D"0"/&gt;<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element name=3D"stop-time" type=3D"xs:dateTime"<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs=3D"0"/&gt;<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;/xs:sequence&gt;<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:attribute =
name=3D"id" type=3D"xs:urnuuid"<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; use"required"/&gt;<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:attribute =
name=3D"recording" type=3D"xs:urnuuid"<BR>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; use"required"/&gt;<BR>&gt; &gt;&nbsp;&nbsp;&nbsp; =
&lt;/xs:complexType&gt;<BR>&gt; &gt;<BR>&gt; &gt; Please let me know in =
case any other change has to be done in the<BR>&gt; &gt; group element =
schema<BR>&gt; &gt;<BR>&gt; &gt; &lt;/Partha&gt;<BR>&gt; &gt; John (as =
individual)<BR>&gt; &gt;<BR>&gt; &gt; &gt; -----Original =
Message-----<BR>&gt; &gt; &gt; From: Parthasarathi R (partr) [<A =
href=3D"mailto:partr@cisco.com">mailto:partr@cisco.com</A><BR>&gt; &gt; =
&lt;<A href=3D"mailto:partr@cisco.com">mailto:partr@cisco.com</A>&gt; =
]<BR>&gt; &gt; &gt; Sent: 12 March 2011 18:24<BR>&gt; &gt; &gt; To: =
Elwell, John; siprec@ietf.org<BR>&gt; &gt; &gt; Subject: RE: [siprec] =
Review Request for<BR>&gt; &gt; &gt; =
draft-ram-siprec-metadata-format-01<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
John,<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; Thanks for the detailed =
comments. Please read inline.<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
Thanks<BR>&gt; &gt; &gt; Partha<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
________________________________<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
From: Elwell, John<BR>&gt; &gt; [<A =
href=3D"mailto:john.elwell@siemens-enterprise.com">mailto:john.elwell@sie=
mens-enterprise.com</A><BR>&gt; &gt; &lt;<A =
href=3D"mailto:john.elwell@siemens-enterprise.com">mailto:john.elwell@sie=
mens-enterprise.com</A>&gt; ]<BR>&gt; &gt; &gt; Sent: Fri 3/11/2011 8:19 =
PM<BR>&gt; &gt; &gt; To: Parthasarathi R (partr); =
siprec@ietf.org<BR>&gt; &gt; &gt; Subject: RE: [siprec] Review Request =
for<BR>&gt; &gt; &gt; draft-ram-siprec-metadata-format-01<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
Partha,<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; I read -01 and have the =
following comments:<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; 1. In section =
3:<BR>&gt; &gt; &gt; "The media related details of metadata SHALL be =
passed<BR>&gt; across using<BR>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; session =
description protocol (SDP) [RFC4566].&nbsp; SDP attributes<BR>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp; describes about different media formats like =
audio, video."<BR>&gt; &gt; &gt; I wonder whether it is really =
appropriate to describe SDP<BR>&gt; attributes<BR>&gt;<BR>&gt; &gt; &gt; =
as part of the metadata. If I look at the metadata model, I =
don't<BR>&gt; &gt; &gt; see any attributes of a Media Stream object that =
could be<BR>&gt; satisfied<BR>&gt; &gt; &gt; using RS SDP. For example, =
the "codec parameters"<BR>&gt; attribute relates<BR>&gt; &gt; &gt; to =
the CS, not the RS - the two sessions could use<BR>&gt; different =
codecs<BR>&gt; &gt; &gt; or different codec parameters. I think it would =
be far simpler to<BR>&gt; &gt; &gt; regard all metadata as being sent in =
XML. Note that the SDP label<BR>&gt; &gt; &gt; attribute can still be =
used as the linkage between a Media Stream<BR>&gt; &gt; &gt; object in =
the metadata and the corresponding RS media stream that<BR>&gt; &gt; =
&gt; captures the CS media stream concerned.<BR>&gt; &gt; &gt;<BR>&gt; =
&gt; &gt; 2. We perhaps need to think about mixed RS media streams, =
i.e.,<BR>&gt; &gt; &gt; where several CS media streams have been mixed =
to produce<BR>&gt; a single<BR>&gt; &gt; &gt; RS media stream. In this =
case, the several Media Stream objects<BR>&gt; &gt; &gt; would all point =
to the same SDP label, I guess. This then brings<BR>&gt; &gt; &gt; into =
question the mode element (type<BR>&gt; &gt; &gt; streamMode) - why is =
this needed? The fact that several<BR>&gt; Media Stream<BR>&gt;<BR>&gt; =
&gt; &gt; objects (stream elements) point to the same label =
would<BR>&gt; imply there<BR>&gt; &gt; &gt; has been mixing, so the mode =
element seems to be redundant.<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; 3. =
Section 4.2.4:<BR>&gt; &gt; &gt; "Each group MAY have initiator entity =
attribute which<BR>&gt; contains SIP/<BR>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp; SIPS URI to identify the device which acts as =
Session Recording<BR>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; Client =
(SRC).&nbsp; The entity attribute SIP/SIPS URI FQDN or<BR>&gt; &gt; IP =
address<BR>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; represents the device and =
may not have user part."<BR>&gt; &gt; &gt; It is unclear to me why a URI =
identifying the SRC should be an<BR>&gt; &gt; &gt; attribute of a group =
element. I cannot find a corresponding<BR>&gt; &gt; &gt; attribute in =
the CS Group object in the metadata model draft.<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &lt;Partha&gt; It is a good point. I missed to =
remove after our last<BR>&gt; &gt; &gt; interim meeting discussion. I'll =
remove in the next revision as<BR>&gt; &gt; &gt; there is no strong =
request for initiator of the session &lt;/Partha&gt;<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt; 4. The example (section 5.1) seems rather odd, in =
that the<BR>&gt; &gt; &gt; recording-metadata element appears to =
comprise a sequence of<BR>&gt; &gt; &gt; elements (recording, group, =
session, etc.) alternating with<BR>&gt; &gt; &gt; extensiondata =
elements, i.e., there is an extensiondata element<BR>&gt; &gt; &gt; =
after each of the other elements. This probably complies with =
the<BR>&gt; &gt; &gt; schema, but what is the meaning of several =
extensiondata elements<BR>&gt; &gt; &gt; all within the same =
recording-metadata element?<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
&lt;Partha&gt; Each extensiondata has its own id and different<BR>&gt; =
parent id.<BR>&gt; &gt; &gt; Parent id shall be of recording, group, =
session etc., It<BR>&gt; is possible<BR>&gt;<BR>&gt; &gt; &gt; for each =
extension data to have different extended<BR>&gt; namespace =
which<BR>&gt; &gt; &gt; is specific to its parent.<BR>&gt; &gt; =
&gt;&nbsp; But it is possible to uniquely identify within<BR>&gt; =
recording-metadata<BR>&gt; &gt; &gt; as it has its own unique id. =
&lt;/Partha&gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; Why not just a =
single extensiondata element?<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
&lt;Partha&gt; It may not be preferred because it is tough to =
arrange<BR>&gt; &gt; &gt; extension data for a particular stream within =
the<BR>&gt; extension data of<BR>&gt; &gt; &gt; group. The individual =
extension data also provides flexibility to<BR>&gt; &gt; &gt; pass the =
specific extension-data during partial update in<BR>&gt; case =
other<BR>&gt;<BR>&gt; &gt; &gt; extension data is not modified. =
&lt;/Partha&gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; Is any significance =
to be drawn from the fact that there is an<BR>&gt; &gt; &gt; =
extensiondata element following the recording element, another<BR>&gt; =
&gt; &gt; following the group element, etc.?<BR>&gt; &gt; &gt;<BR>&gt; =
&gt; &gt; &lt;Partha&gt; As mentioned earlier, group mechanism may =
passed<BR>&gt; in group<BR>&gt; &gt; &gt; extensiondata&nbsp; whereas =
retention policy of a specific<BR>&gt; session will<BR>&gt; &gt; &gt; be =
passed in session, recording extension data will have common<BR>&gt; =
&gt; &gt; attribute like os login shall be passed. It provides =
more<BR>&gt; &gt; &gt; flexibility and it is optional element, so it is =
required to pass<BR>&gt; &gt; &gt; whenever applicable only =
&lt;/Partha&gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; 5. On the other =
hand, elements group, session, etc. seem to lack<BR>&gt; &gt; &gt; =
extensiondata elements - would it not be sensible to<BR>&gt; allow each =
of<BR>&gt; &gt; &gt; these to be extensible?<BR>&gt; &gt; &gt;<BR>&gt; =
&gt; &gt; &lt;Partha&gt; Parent-id in extension data helps to link =
group,<BR>&gt; session to<BR>&gt;<BR>&gt; &gt; &gt; specific extension =
data &lt;/partha&gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; 6. The method =
of sending partial metadata seems to imply<BR>&gt; that when =
a<BR>&gt;<BR>&gt; &gt; &gt; session, participant, stream etc. comes to =
an end, we<BR>&gt; send partial<BR>&gt; &gt; &gt; metadata indicating =
that the element concerned now has an<BR>&gt; end time.<BR>&gt; &gt; =
&gt; This seems implicitly to mean that the element ceases to exist =
-<BR>&gt; &gt; &gt; correct? So if the SRS were to request a snapshot of =
complete<BR>&gt; &gt; &gt; metadata, it would not receive any elements =
for which a stop time<BR>&gt; &gt; &gt; has previously been sent<BR>&gt; =
&gt; - correct?<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; &lt;Partha&gt; Your =
understanding is correct, end-time will not passed<BR>&gt; &gt; &gt; =
across in case of SRS request for complete metadata as<BR>&gt; SRC may =
have<BR>&gt; &gt; &gt; lost the state&lt;/Partha&gt;<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt;&nbsp; I don't think I have an issue with this - I =
just wanted<BR>&gt; to confirm<BR>&gt; &gt; &gt; my =
understanding.<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; John (as =
individual)<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; =
-----Original Message-----<BR>&gt; &gt; &gt; &gt; From: =
siprec-bounces@ietf.org<BR>&gt; &gt; &gt; &gt; [<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
><BR>&gt; &gt; &lt;<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>&gt; ] On Behalf Of Parthasarathi<BR>&gt; &gt; &gt; R (partr)<BR>&gt; =
&gt; &gt; &gt; Sent: 08 March 2011 14:24<BR>&gt; &gt; &gt; &gt; To: =
siprec@ietf.org<BR>&gt; &gt; &gt; &gt; Subject: [siprec] Review Request =
for<BR>&gt; &gt; &gt; &gt; draft-ram-siprec-metadata-format-01<BR>&gt; =
&gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; Hi all,<BR>&gt; &gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &gt; As per the mailing list comments and interim =
meeting<BR>&gt; discussion, I<BR>&gt;<BR>&gt; &gt; &gt; &gt; updated -01 =
draft of draft-ram-siprec-metadata-format and<BR>&gt; &gt; &gt; send it =
for<BR>&gt; &gt; &gt; &gt; review. The draft is available at<BR>&gt; =
&gt; &gt; &gt;<BR>&gt; &gt; <A =
href=3D"http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt">h=
ttp://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt</A><BR>&gt;=
 &gt;<BR>&gt; &gt;<BR>&gt; &lt;<A =
href=3D"http://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt">h=
ttp://www.ietf.org/id/draft-ram-siprec-metadata-format-01.txt</A>&gt; . =
The<BR>&gt; &gt; &gt; &gt; following update are done as part of -01 =
draft:<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; 1) URN UUID (RFC =
4122) mechanism is used as the unique id<BR>&gt; &gt; &gt; &gt; =
mechanism for relevant XML elements like group,<BR>&gt; session, =
stream,<BR>&gt; &gt; &gt; &gt; participant.<BR>&gt; &gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &gt; 2) Partial XML passing in RS is supported by =
having unique URN<BR>&gt; &gt; &gt; &gt; UUID for group, session, =
stream, participant,<BR>&gt; recording, extension<BR>&gt;<BR>&gt; &gt; =
&gt; &gt; data which are directly under recording-metadata<BR>&gt; &gt; =
&gt; &gt; container/namespace.<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; =
&gt; 3) Include recording-metadata element as a container =
element<BR>&gt; &gt; &gt; &gt; instead of recording element. This helps =
in avoiding duplicate<BR>&gt; &gt; &gt; &gt; data of<BR>&gt; &gt; &gt; =
recording<BR>&gt; &gt; &gt; &gt; elements during the partial =
update<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; 4) Updated elements =
in XML document as per<BR>&gt; &gt; &gt; &gt; =
draft-ram-siprec-metadata-04<BR>&gt; &gt; &gt; &gt; elements &amp; =
associations<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; 5) Changed =
appdata element name as extensiondata<BR>&gt; &gt; &gt; &gt;<BR>&gt; =
&gt; &gt; &gt; 6) Removed container element like sessions, =
participants,<BR>&gt; &gt; &gt; streams from<BR>&gt; &gt; &gt; &gt; XML =
document as&nbsp; parent reference exists in each element<BR>&gt; &gt; =
&gt; &gt;<BR>&gt; &gt; &gt; &gt; 7) Added Partial Update example &amp; =
SIP usage XML+SDP example<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; =
8) Portion of security considerations section is added.<BR>&gt; &gt; =
&gt; &gt;<BR>&gt; &gt; &gt; &gt; Could you please review and provide =
your expert comments on<BR>&gt; &gt; &gt; the draft.<BR>&gt; &gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &gt; Thanks<BR>&gt; &gt; &gt; &gt; Partha<BR>&gt; =
&gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; -----Original Message-----<BR>&gt; =
&gt; &gt; &gt; From: IETF I-D Submission Tool<BR>&gt; &gt; [<A =
href=3D"mailto:idsubmission@ietf.org">mailto:idsubmission@ietf.org</A> =
&lt;<A =
href=3D"mailto:idsubmission@ietf.org">mailto:idsubmission@ietf.org</A>&gt=
; ]<BR>&gt; &gt; &gt; &gt; Sent: Tuesday, March 08, 2011 7:31 PM<BR>&gt; =
&gt; &gt; &gt; To: Parthasarathi R (partr)<BR>&gt; &gt; &gt; &gt; Cc: =
Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)<BR>&gt; &gt; &gt; &gt; =
Subject: New Version Notification for<BR>&gt; &gt; &gt; &gt; =
draft-ram-siprec-metadata-format-01<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; =
&gt; &gt;<BR>&gt; &gt; &gt; &gt; A new version of I-D,<BR>&gt; &gt; &gt; =
draft-ram-siprec-metadata-format-01.txt has been<BR>&gt; &gt; &gt; &gt; =
successfully submitted by Parthasarathi R and posted to<BR>&gt; the =
IETF<BR>&gt; &gt; &gt; &gt; repository.<BR>&gt; &gt; &gt; &gt;<BR>&gt; =
&gt; &gt; &gt; Filename:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-ram-siprec-metadata-format<BR>&gt; &gt; &gt; &gt; =
Revision:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 01<BR>&gt; &gt; &gt; &gt; =
Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Session Initiation Protocol (SIP)<BR>&gt; =
&gt; &gt; &gt; Recording Metadata<BR>&gt; &gt; &gt; &gt; Format<BR>&gt; =
&gt; &gt; &gt; =
Creation_date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2011-03-08<BR>&gt; &gt; &gt; &gt; WG =
ID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Independent Submission<BR>&gt; &gt; &gt; &gt; =
Number_of_pages: 20<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; =
Abstract:<BR>&gt; &gt; &gt; &gt; Session recording is a critical =
requirement in many<BR>&gt; communications<BR>&gt;<BR>&gt; &gt; &gt; =
&gt; environments such as call centers and financial trading.<BR>&gt; =
&gt; In some of<BR>&gt; &gt; &gt; &gt; these environments, all calls =
must be recorded for regulatory,<BR>&gt; &gt; &gt; &gt; compliance, and =
consumer protection reasons.&nbsp; Recording of a<BR>&gt; &gt; &gt; &gt; =
session is typically performed by sending a copy of a<BR>&gt; media =
stream<BR>&gt;<BR>&gt; &gt; &gt; &gt; to<BR>&gt; &gt; &gt; a =
recording<BR>&gt; &gt; &gt; &gt; device.&nbsp; The requirements for =
which are described in<BR>&gt; &gt; &gt; &gt; [I-D.ietf-siprec-req], the =
architecture for which is<BR>&gt; described in<BR>&gt; &gt; &gt; &gt; =
[I-D.ietf-siprec-architecture], and the metadata model<BR>&gt; viewed =
by<BR>&gt; &gt; &gt; &gt; Session Recording Server is described =
in<BR>&gt; &gt; &gt; &gt; [I-D.ram-siprec-metadata].<BR>&gt; &gt; &gt; =
&gt; This document focuses on the Recording metadata format<BR>&gt; &gt; =
&gt; which describes<BR>&gt; &gt; &gt; &gt; the communication =
session.<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; =
&gt;<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt; The IETF =
Secretariat.<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; =
&gt; &gt; _______________________________________________<BR>&gt; &gt; =
&gt; &gt; siprec mailing list<BR>&gt; &gt; &gt; &gt; =
siprec@ietf.org<BR>&gt; &gt; &gt; &gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR>&gt; &gt; &lt;<A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A>&gt;<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt;<BR>&gt; =
&gt;<BR>&gt; &gt;<BR>&gt;<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01CBE260.5CFE6817--

From krehor@cisco.com  Mon Mar 14 09:06:46 2011
Return-Path: <krehor@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BF943A6D6A for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 09:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.398
X-Spam-Level: 
X-Spam-Status: No, score=-7.398 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_25=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bjH4xK+3tFax for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 09:06:40 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 22C9F3A6C5C for <siprec@ietf.org>; Mon, 14 Mar 2011 09:06:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=krehor@cisco.com; l=132905; q=dns/txt; s=iport; t=1300118878; x=1301328478; h=mime-version:subject:date:message-id:in-reply-to: references:from:to; bh=K1qod49Vs/C6ExQLSUNYMv3S+w5XE6HU11pLxl2doTU=; b=d3Ca9E1QJtsFxj+u+R3UfzEvdDLyz7jK5zc5/dH1B8esbYPzUff7NCrW Qc0WNWetNYGakgGE7mVg7RYmGpcb4zokZ++kQ+g0VAYdw9WWal61hqVi6 hx1ANQh4gN0Nj+lSFvESewUXbv5ZRbCvz6XD9RJweEU+aaXLJa75jxnA5 U=;
X-Files: draft-ietf-siprec-req-08.txt, draft-ietf-siprec-req-08.xml, SIPREC_req_diff_-07_vs_-08.html : 31537, 30554, 32881
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAAETafU2tJV2Z/2dsb2JhbACYRI1Fd6QhjGSPHIJ7gmcEhSuKe4ku
X-IronPort-AV: E=Sophos;i="4.62,316,1297036800";  d="xml'217?txt'217?html'217,217?scan'217,217,208,217";a="346022261"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by sj-iport-5.cisco.com with ESMTP; 14 Mar 2011 16:07:56 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2EG7qdB016492 for <siprec@ietf.org>; Mon, 14 Mar 2011 16:07:55 GMT
Received: from xmb-sjc-22e.amer.cisco.com ([128.107.191.115]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Mar 2011 09:07:34 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CBE261.ED68E66B"
Date: Mon, 14 Mar 2011 09:07:28 -0700
Message-ID: <7744FE52C78D944587F03773EB45146109AC1FDD@xmb-sjc-22e.amer.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A648103@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last chance for changes to siprec-req-07
Thread-Index: Acvdt7euTNDO2n4QSAyVfMXgONVCfQEqfKvQ
References: <A444A0F8084434499206E78C106220CA086A648103@MCHP058A.global-ad.net>
From: "Ken Rehor (krehor)" <krehor@cisco.com>
To: <siprec@ietf.org>
X-OriginalArrivalTime: 14 Mar 2011 16:07:34.0241 (UTC) FILETIME=[EDF8ED10:01CBE261]
Subject: Re: [siprec] Last chance for changes to siprec-req-07
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 16:06:46 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE261.ED68E66B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks to John, Leon and the team, we posted req-08 today. =20
(.txt, .xml, and diff attached)

Ken


> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Tuesday, March 08, 2011 9:39 AM
> To: siprec@ietf.org; Leon Portman; Ken Rehor (krehor)
> Subject: Last chance for changes to siprec-req-07
>=20
> The editors have posted req-07. This is your last chance to request
changes.
> Deadline 2011-03-13 (to give the editors chance to produce -08 before
the
> deadline the next day).
>=20
> I noticed the following:
> 1. IDNITS gave a warning about the disclaimer concerning pre-RFC5378
work in
> the boiler plate. Since the document (and also its draft-rehor
predecessor)
> is post 2008, is this applicable?
> 2. IDNITS revealed missing references RFC 4733 and RFC 4103 (I believe
both
> are normative references)
> 3. IDNITS revealed unused reference RFC 2804.
> 4. Change "Ral-time" to "Real-time"
> 5. "REQ-001 The mechanism MUST provide a means for "using the SIP
>    protocol for" establishing, maintaining and terminating"
> Remove 'the quotes around using the SIP protocol for'
> 6. "Note: A mixed audio stream is where several Communication Sessions
>    are carried in a single Recording Session."
> Change to:
> "Note: A mixed audio stream is where several related Communication
Sessions
>    are carried in a single Recording Session."
> (i.e., add the word "related".
> 7. "Requirements for participant notification of recording varies
widely
>    by jurisdiction."
> Change "varies" to "vary".
>=20
> Would the editors please correct these and ensure the document passes
IDNITS.
> Please ensure -08 is posted by the submission deadline 2011-03-14. By
all
> means wait for other comments, but not at the expense of missing the
> deadline!
>=20
> Thanks,
>=20
> John


------_=_NextPart_001_01CBE261.ED68E66B
Content-Type: text/plain;
	name="draft-ietf-siprec-req-08.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-siprec-req-08.txt
Content-Disposition: attachment;
	filename="draft-ietf-siprec-req-08.txt"

CgoKRElTUEFUQ0ggICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBLLiBSZWhvciwgRWQuCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgQ2lzY28gU3lzdGVtcwpJbnRlbmRlZCBzdGF0dXM6IEluZm9y
bWF0aW9uYWwgICAgICAgICAgICAgICAgICAgICAgICAgICBMLiBQb3J0bWFuLCBFZC4KRXhwaXJl
czogU2VwdGVtYmVyIDE1LCAyMDExICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTklD
RSBTeXN0ZW1zCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIEEuIEh1dHRvbgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBTaWVtZW5zIEVudGVycHJpc2UgQ29tbXVuaWNhdGlvbnMKICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBSLiBKYWlu
CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBJUEMgU3lzdGVtcwogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgTWFyY2ggMTQsIDIwMTEKCgogICAgICAgICAgUmVxdWlyZW1lbnRz
IGZvciBTSVAtYmFzZWQgTWVkaWEgUmVjb3JkaW5nIChTSVBSRUMpCiAgICAgICAgICAgICAgICAg
ICAgICAgIGRyYWZ0LWlldGYtc2lwcmVjLXJlcS0wOAoKQWJzdHJhY3QKCiAgIFNlc3Npb24gcmVj
b3JkaW5nIGlzIGEgY3JpdGljYWwgcmVxdWlyZW1lbnQgaW4gbWFueSBidXNpbmVzcwogICBjb21t
dW5pY2F0aW9ucyBlbnZpcm9ubWVudHMgc3VjaCBhcyBjYWxsIGNlbnRlcnMgYW5kIGZpbmFuY2lh
bAogICB0cmFkaW5nIGZsb29ycy4gIEluIHNvbWUgb2YgdGhlc2UgZW52aXJvbm1lbnRzLCBhbGwg
Y2FsbHMgbXVzdCBiZQogICByZWNvcmRlZCBmb3IgcmVndWxhdG9yeSBhbmQgY29tcGxpYW5jZSBy
ZWFzb25zLiAgSW4gb3RoZXJzLCBjYWxscyBtYXkKICAgYmUgcmVjb3JkZWQgZm9yIHF1YWxpdHkg
Y29udHJvbCBvciBidXNpbmVzcyBhbmFseXRpY3MuCgogICBSZWNvcmRpbmcgaXMgdHlwaWNhbGx5
IHBlcmZvcm1lZCBieSBzZW5kaW5nIGEgY29weSBvZiB0aGUgc2Vzc2lvbgogICBtZWRpYSB0byB0
aGUgcmVjb3JkaW5nIGRldmljZXMuICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyByZXF1aXJlbWVu
dHMKICAgZm9yIGV4dGVuc2lvbnMgdG8gU0lQIHRoYXQgd2lsbCBtYW5hZ2UgZGVsaXZlcnkgb2Yg
UlRQIG1lZGlhIHRvIGEKICAgcmVjb3JkaW5nIGRldmljZS4gIFRoaXMgaXMgYmVpbmcgcmVmZXJy
ZWQgdG8gYXMgU0lQLWJhc2VkIE1lZGlhCiAgIFJlY29yZGluZy4KClN0YXR1cyBvZiB0aGlzIE1l
bW8KCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgaXMgc3VibWl0dGVkIGluIGZ1bGwgY29uZm9ybWFu
Y2Ugd2l0aCB0aGUKICAgcHJvdmlzaW9ucyBvZiBCQ1AgNzggYW5kIEJDUCA3OS4KCiAgIEludGVy
bmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVy
aW5nCiAgIFRhc2sgRm9yY2UgKElFVEYpLiAgTm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkgYWxz
byBkaXN0cmlidXRlCiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy4gIFRo
ZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtCiAgIERyYWZ0cyBpcyBhdCBodHRwOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1cnJlbnQvLgoKICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBk
cmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9udGhzCiAgIGFuZCBt
YXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMg
YXQgYW55CiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFm
dHMgYXMgcmVmZXJlbmNlCiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFz
ICJ3b3JrIGluIHByb2dyZXNzLiIKCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUg
b24gU2VwdGVtYmVyIDE1LCAyMDExLgoKQ29weXJpZ2h0IE5vdGljZQoKICAgQ29weXJpZ2h0IChj
KSAyMDExIElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMgdGhlCgoKClJl
aG9yLCBldCBhbC4gICAgICAgICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTUsIDIwMTEgICAgICAgICAg
ICAgICBbUGFnZSAxXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICBSZXF1aXJlbWVudHMgZm9y
IFNJUFJFQyAgICAgICAgICAgICAgTWFyY2ggMjAxMQoKCiAgIGRvY3VtZW50IGF1dGhvcnMuICBB
bGwgcmlnaHRzIHJlc2VydmVkLgoKICAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJDUCA3
OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbAogICBQcm92aXNpb25zIFJlbGF0aW5nIHRvIElF
VEYgRG9jdW1lbnRzCiAgIChodHRwOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8pIGlu
IGVmZmVjdCBvbiB0aGUgZGF0ZSBvZgogICBwdWJsaWNhdGlvbiBvZiB0aGlzIGRvY3VtZW50LiAg
UGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHMKICAgY2FyZWZ1bGx5LCBhcyB0aGV5IGRlc2Ny
aWJlIHlvdXIgcmlnaHRzIGFuZCByZXN0cmljdGlvbnMgd2l0aCByZXNwZWN0CiAgIHRvIHRoaXMg
ZG9jdW1lbnQuICBDb2RlIENvbXBvbmVudHMgZXh0cmFjdGVkIGZyb20gdGhpcyBkb2N1bWVudCBt
dXN0CiAgIGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZSB0ZXh0IGFzIGRlc2NyaWJlZCBp
biBTZWN0aW9uIDQuZSBvZgogICB0aGUgVHJ1c3QgTGVnYWwgUHJvdmlzaW9ucyBhbmQgYXJlIHBy
b3ZpZGVkIHdpdGhvdXQgd2FycmFudHkgYXMKICAgZGVzY3JpYmVkIGluIHRoZSBTaW1wbGlmaWVk
IEJTRCBMaWNlbnNlLgoKClRhYmxlIG9mIENvbnRlbnRzCgogICAxLiAgUmVxdWlyZW1lbnRzIG5v
dGF0aW9uICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDMKICAgMi4g
IEludHJvZHVjdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICAzCiAgIDMuICBEZWZpbml0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNAogICA0LiAgVXNlIENhc2VzICAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDYKICAgNS4gIFJlcXVpcmVt
ZW50cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEw
CiAgIDYuICBQcml2YWN5IENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAxMgogICA3LiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTMKICAgOC4gIElBTkEgQ29uc2lkZXJhdGlv
bnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE0CiAgIDkuICBB
Y2tub3dsZWRnZW1lbnRzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAxNAogICAxMC4gTm9ybWF0aXZlIFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gMTQKICAgQXV0aG9ycycgQWRkcmVzc2VzIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE0CgoKCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgpSZWhvciwgZXQgYWwuICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE1LCAyMDEx
ICAgICAgICAgICAgICAgW1BhZ2UgMl0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgUmVxdWly
ZW1lbnRzIGZvciBTSVBSRUMgICAgICAgICAgICAgIE1hcmNoIDIwMTEKCgoxLiAgUmVxdWlyZW1l
bnRzIG5vdGF0aW9uCgogICBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJ
UkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIsCiAgICJTSE9VTEQiLCAiU0hPVUxEIE5PVCIsICJS
RUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0aGlzCiAgIGRvY3VtZW50IGFy
ZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQgaW4gW1JGQzIxMTldIGFuZCBpbmRpY2F0
ZQogICByZXF1aXJlbWVudCBsZXZlbHMgZm9yIGNvbXBsaWFudCBtZWNoYW5pc21zLgoKCjIuICBJ
bnRyb2R1Y3Rpb24KCiAgIFNlc3Npb24gcmVjb3JkaW5nIGlzIGEgY3JpdGljYWwgb3BlcmF0aW9u
YWwgcmVxdWlyZW1lbnQgaW4gbWFueQogICBidXNpbmVzc2VzLCBlc3BlY2lhbGx5IHdoZXJlIHZv
aWNlIGlzIHVzZWQgYXMgYSBtZWRpdW0gZm9yIGNvbW1lcmNlCiAgIGFuZCBjdXN0b21lciBzdXBw
b3J0LiAgQSBwcmltZSBleGFtcGxlIHdoZXJlIHZvaWNlIGlzIHVzZWQgZm9yIHRyYWRlCiAgIGlz
IHRoZSBmaW5hbmNpYWwgaW5kdXN0cnkuICBUaGUgY2FsbCByZWNvcmRpbmcgcmVxdWlyZW1lbnRz
IGluIHRoaXMKICAgaW5kdXN0cnkgYXJlIHF1aXRlIHN0cmluZ2VudC4gIFRoZSByZWNvcmRlZCBj
YWxscyBhcmUgdXNlZCBmb3IKICAgZGlzcHV0ZSByZXNvbHV0aW9uIGFuZCBjb21wbGlhbmNlLiAg
T3RoZXIgYnVzaW5lc3NlcyBzdWNoIGFzIGN1c3RvbWVyCiAgIHN1cHBvcnQgY2FsbCBjZW50ZXJz
IHR5cGljYWxseSBlbXBsb3kgY2FsbCByZWNvcmRpbmcgZm9yIHF1YWxpdHkKICAgY29udHJvbCBv
ciBidXNpbmVzcyBhbmFseXRpY3MsIHdpdGggZGlmZmVyZW50IHJlcXVpcmVtZW50cy4KCiAgIERl
cGVuZGluZyBvbiB0aGUgY291bnRyeSBhbmQgaXRzIHJlZ3VsYXRvcnkgcmVxdWlyZW1lbnRzLCBm
aW5hbmNpYWwKICAgdHJhZGluZyBmbG9vcnMgdHlwaWNhbGx5IG11c3QgcmVjb3JkIGFsbCBjYWxs
cy4gIEluIGNvbnRyYXN0LCBjYWxsCiAgIGNlbnRlcnMgdHlwaWNhbGx5IG9ubHkgcmVjb3JkIGEg
c3Vic2V0IG9mIHRoZSBjYWxscywgYW5kIGNhbGxzIG11c3QKICAgbm90IGZhaWwgcmVnYXJkbGVz
cyBvZiB0aGUgYXZhaWxhYmlsaXR5IG9mIHRoZSByZWNvcmRpbmcgZGV2aWNlLgoKICAgUmVzcGVj
dGluZyB0aGUgcHJpdmFjeSByaWdodHMgYW5kIHdpc2hlcyBvZiB1c2VycyBlbmdhZ2VkIGluIGEg
Y2FsbAogICBpcyBvZiBwYXJhbW91bnQgaW1wb3J0YW5jZS4gIEluIG1hbnkganVyaXNkaWN0aW9u
cyBwYXJ0aWNpcGFudHMgaGF2ZQogICBhIHJpZ2h0IHRvIGtub3cgdGhhdCB0aGUgc2Vzc2lvbiBp
cyBiZWluZyByZWNvcmRlZCBvciBtaWdodCBiZQogICByZWNvcmRlZCwgYW5kIGhhdmUgYSByaWdo
dCB0byBvcHQgb3V0LCBlaXRoZXIgYnkgdGVybWluYXRpbmcgdGhlIGNhbGwKICAgb3IgYnkgZGVt
YW5kaW5nIHRoYXQgdGhlIGNhbGwgbm90IGJlIHJlY29yZGVkLiAgVGhlcmVmb3JlIHRoaXMKICAg
ZG9jdW1lbnQgY29udGFpbnMgcmVxdWlyZW1lbnRzIGZvciBiZWluZyBhYmxlIHRvIG5vdGlmeSB1
c2VycyB0aGF0IGEKICAgY2FsbCBpcyBiZWluZyByZWNvcmRlZCBhbmQgZm9yIHVzZXJzIHRvIGJl
IGFibGUgdG8gcmVxdWVzdCB0aGF0IGEKICAgY2FsbCBub3QgYmUgcmVjb3JkZWQuICBVc2UgY2Fz
ZXMgd2hlcmUgdXNlcnMgcGFydGljaXBhdGluZyBpbiBhIGNhbGwKICAgYXJlIG5vdCBpbmZvcm1l
ZCB0aGF0IHRoZSBjYWxsIGlzIG9yIG1pZ2h0IGJlIHJlY29yZGVkIGFyZSBvdXRzaWRlCiAgIHRo
ZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50LiAgSW4gcGFydGljdWxhciwgbGF3ZnVsIGludGVyY2Vw
dCBpcwogICBvdXRzaWRlIHRoZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50LgoKICAgRnVydGhlcm1v
cmUsIHRoZSBzY2FsZSBhbmQgY29zdCBidXJkZW5zIHZhcnkgd2lkZWx5LCBpbiBhbGwgbWFya2V0
cywKICAgd2hlcmUgdGhlIGRpZmZlcmVudCBuZWVkcyBmb3Igc29sdXRpb24gY2FwYWJpbGl0aWVz
IHN1Y2ggYXMgbWVkaWEKICAgaW5qZWN0aW9uLCB0cmFuc2NvZGluZywgYW5kIHNlY3VyaXR5LXJl
bGF0ZWQgbmVlZHMgZG8gbm90IGNvbmZvcm0KICAgd2VsbCB0byBhIG9uZS1zaXplLWZpdHMtYWxs
IG1vZGVsLiAgSWYgYSBzdGFuZGFyZGl6ZWQgc29sdXRpb24KICAgc3VwcG9ydHMgYWxsIG9mIHRo
ZSByZXF1aXJlbWVudHMgZnJvbSBldmVyeSByZWNvcmRpbmcgbWFya2V0LCBidXQKICAgZG9pbmcg
c28gd291bGQgYmUgZXhwZW5zaXZlIGZvciBtYXJrZXRzIHdpdGggbGVzc2VyIG5lZWRzLCB0aGVu
CiAgIHByb3ByaWV0YXJ5IHNvbHV0aW9ucyBmb3IgdGhvc2UgbWFya2V0cyB3aWxsIGNvbnRpbnVl
IHRvIHByb3BhZ2F0ZS4KICAgQ2FyZSBtdXN0IGJlIHRha2VuLCB0aGVyZWZvcmUsIHRvIG1ha2Ug
YSBzdGFuZGFyZHMtYmFzZWQgc29sdXRpb24KICAgc3VwcG9ydCBvcHRpb25hbGl0eSBhbmQgZmxl
eGliaWxpdHkuCgogICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyByZXF1aXJlbWVudHMgZm9yIHVz
aW5nIFNJUCBbUkZDMzI2MV0gYmV0d2VlbgogICBhIFNlc3Npb24gUmVjb3JkaW5nIENsaWVudCBh
bmQgYSBTZXNzaW9uIFJlY29yZGluZyBTZXJ2ZXIgdG8gY29udHJvbAoKCgpSZWhvciwgZXQgYWwu
ICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE1LCAyMDExICAgICAgICAgICAgICAgW1BhZ2Ug
M10KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgUmVxdWlyZW1lbnRzIGZvciBTSVBSRUMgICAg
ICAgICAgICAgIE1hcmNoIDIwMTEKCgogICB0aGUgcmVjb3JkaW5nIG9mIG1lZGlhIHRoYXQgaGFz
IGJlZW4gdHJhbnNtaXR0ZWQgaW4gdGhlIGNvbnRleHQgb2YgYQogICBDb21tdW5pY2F0aW9uIFNl
c3Npb24uICBBIENvbW11bmljYXRpb24gU2Vzc2lvbiBpcyB0aGUgImNhbGwiIGJldHdlZW4KICAg
cGFydGljaXBhbnRzLiAgVGhlIFNlc3Npb24gUmVjb3JkaW5nIENsaWVudCBpcyB0aGUgc291cmNl
IG9mIHRoZQogICByZWNvcmRlZCBtZWRpYS4gIFRoZSBTZXNzaW9uIFJlY29yZGluZyBTZXJ2ZXIg
aXMgdGhlIHNpbmsgb2YgcmVjb3JkZWQKICAgbWVkaWEuICBJdCBzaG91bGQgYmUgbm90ZWQgdGhh
dCB0aGUgcmVxdWlyZW1lbnRzIGZvciB0aGUgcHJvdG9jb2wKICAgYmV0d2VlbiBhIFNlc3Npb24g
UmVjb3JkaW5nIFNlcnZlciBhbmQgU2Vzc2lvbiBSZWNvcmRpbmcgQ2xpZW50IGhhdmUKICAgdmVy
eSBzaW1pbGFyIHJlcXVpcmVtZW50cyAoc3VjaCBhcyBjb2RlYyBhbmQgdHJhbnNwb3J0IG5lZ290
aWF0aW9uLAogICBlbmNyeXB0aW9uIGtleSBpbnRlcmNoYW5nZSwgZmlyZXdhbGwgdHJhdmVyc2Fs
KSBhcyBjb21wYXJlZCB0bwogICByZWd1bGFyIFNJUCBtZWRpYSBzZXNzaW9ucy4gIFRoZSBjaG9p
Y2Ugb2YgU0lQIGZvciBzZXNzaW9uIHJlY29yZGluZwogICBwcm92aWRlcyByZXVzZSBvZiBhbiBl
eGlzdGluZyBwcm90b2NvbC4KCiAgIFRoZSByZWNvcmRlZCBzZXNzaW9ucyBjYW4gYmUgYW55IFJU
UCBtZWRpYSBzZXNzaW9ucyBpbmNsdWRpbmcgdm9pY2UsCiAgIERUTUYgKGFzIGRlZmluZWQgYnkg
W1JGQzQ3MzNdKSwgdmlkZW8sIGFuZCB0ZXh0IChhcyBkZWZpbmVkIGJ5CiAgIFtSRkM0MTAzXSku
CgogICBBbiBhcmNoaXZlZCBzZXNzaW9uIHJlY29yZGluZyBpcyB0eXBpY2FsbHkgY29tcHJpc2Vk
IG9mIHRoZQogICBDb21tdW5pY2F0aW9uIFNlc3Npb24gbWVkaWEgY29udGVudCBhbmQgdGhlIENv
bW11bmljYXRpb24gU2Vzc2lvbgogICBNZXRhZGF0YS4gIFRoZSBDb21tdW5pY2F0aW9uIFNlc3Np
b24gTWV0YWRhdGEgYWxsb3dzIHJlY29yZGluZwogICBhcmNoaXZlcyB0byBiZSBzZWFyY2hlZCBh
bmQgZmlsdGVyZWQgYXQgYSBsYXRlciB0aW1lIGFuZCBhbGxvd3MgYQogICBzZXNzaW9uIHRvIGJl
IHBsYXllZCBiYWNrIGluIGEgbWVhbmluZ2Z1bCB3YXksIGUuZy4sIHdpdGggY29ycmVjdAogICBz
eW5jaHJvbml6YXRpb24gYmV0d2VlbiB0aGUgbWVkaWEuICBUaGUgQ29tbXVuaWNhdGlvbiBTZXNz
aW9uCiAgIE1ldGFkYXRhIG5lZWRzIHRvIGJlIGNvbnZleWVkIGZyb20gdGhlIFNlc3Npb24gUmVj
b3JkaW5nIENsaWVudCB0bwogICB0aGUgU2Vzc2lvbiBSZWNvcmRpbmcgU2VydmVyLgoKICAgVGhp
cyBkb2N1bWVudCBvbmx5IGNvbnNpZGVycyBhY3RpdmUgcmVjb3JkaW5nLCB3aGVyZSB0aGUgU2Vz
c2lvbgogICBSZWNvcmRpbmcgQ2xpZW50IHB1cnBvc2VmdWxseSBzdHJlYW1zIG1lZGlhIHRvIGEg
U2Vzc2lvbiBSZWNvcmRpbmcKICAgU2VydmVyLiAgUGFzc2l2ZSByZWNvcmRpbmcsIHdoZXJlIGEg
cmVjb3JkaW5nIGRldmljZSBkZXRlY3RzIG1lZGlhCiAgIGRpcmVjdGx5IGZyb20gdGhlIG5ldHdv
cmssIGlzIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQuCgoKMy4gIERlZmluaXRp
b25zCgogICBTZXNzaW9uIFJlY29yZGluZyBTZXJ2ZXIgKFNSUyk6IEEgU2Vzc2lvbiBSZWNvcmRp
bmcgU2VydmVyIChTUlMpIGlzIGEKICAgU0lQIFVzZXIgQWdlbnQgKFVBKSB0aGF0IGlzIGEgc3Bl
Y2lhbGl6ZWQgbWVkaWEgc2VydmVyIG9yIGNvbGxlY3RvcgogICB0aGF0IGFjdHMgYXMgdGhlIHNp
bmsgb2YgdGhlIHJlY29yZGVkIG1lZGlhLiAgQW4gU1JTIGlzIHR5cGljYWxseQogICBpbXBsZW1l
bnRlZCBhcyBhIG11bHRpLXBvcnQgZGV2aWNlIHRoYXQgaXMgY2FwYWJsZSBvZiByZWNlaXZpbmcg
bWVkaWEKICAgZnJvbSBtdWx0aXBsZSBzb3VyY2VzIHNpbXVsdGFuZW91c2x5LiAgQW4gU1JTIGlz
IHRoZSBzaW5rIG9mIHRoZQogICByZWNvcmRlZCBzZXNzaW9uIG1ldGFkYXRhLgoKICAgU2Vzc2lv
biBSZWNvcmRpbmcgQ2xpZW50IChTUkMpOiBBIFNlc3Npb24gUmVjb3JkaW5nIENsaWVudCAoU1JD
KSBpcyBhCiAgIFNJUCBVc2VyIEFnZW50IChVQSkgdGhhdCBhY3RzIGFzIHRoZSBzb3VyY2Ugb2Yg
dGhlIHJlY29yZGVkIG1lZGlhLAogICBzZW5kaW5nIGl0IHRvIHRoZSBTUlMuICBBbiBTUkMgaXMg
YSBsb2dpY2FsIGZ1bmN0aW9uLiAgSXRzCiAgIGNhcGFiaWxpdGllcyBtYXkgYmUgaW1wbGVtZW50
ZWQgYWNyb3NzIG9uZSBvciBtb3JlIHBoeXNpY2FsIGRldmljZXMuCiAgIEluIHByYWN0aWNlLCBh
biBTUkMgY291bGQgYmUgYSBwZXJzb25hbCBkZXZpY2UgKHN1Y2ggYXMgYSBTSVAgcGhvbmUpLAog
ICBhIFNJUCBNZWRpYSBHYXRld2F5IChNRyksIGEgU2Vzc2lvbiBCb3JkZXIgQ29udHJvbGxlciAo
U0JDKSBvciBhIFNJUAogICBNZWRpYSBTZXJ2ZXIgKE1TKSBpbnRlZ3JhdGVkIHdpdGggYW4gQXBw
bGljYXRpb24gU2VydmVyIChBUykuICBUaGlzCiAgIHNwZWNpZmljYXRpb24gZGVmaW5lcyB0aGUg
dGVybSBTUkMgc3VjaCB0aGF0IGFsbCBzdWNoIFNJUCBlbnRpdGllcwogICBjYW4gYmUgZ2VuZXJp
Y2FsbHkgYWRkcmVzc2VkIHVuZGVyIG9uZSBkZWZpbml0aW9uLiAgVGhlIFNSQyBwcm92aWRlcwoK
CgpSZWhvciwgZXQgYWwuICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE1LCAyMDExICAgICAg
ICAgICAgICAgW1BhZ2UgNF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgUmVxdWlyZW1lbnRz
IGZvciBTSVBSRUMgICAgICAgICAgICAgIE1hcmNoIDIwMTEKCgogICBtZXRhZGF0YSB0byB0aGUg
U1JTLgoKICAgQ29tbXVuaWNhdGlvbiBTZXNzaW9uIChDUyk6IEEgc2Vzc2lvbiBjcmVhdGVkIGJl
dHdlZW4gdHdvIG9yIG1vcmUgU0lQCiAgIFVzZXIgQWdlbnRzIChVQXMpIHRoYXQgaXMgdGhlIHN1
YmplY3Qgb2YgcmVjb3JkaW5nLgoKICAgUmVjb3JkaW5nIFNlc3Npb24gKFJTKTogVGhlIFNJUCBz
ZXNzaW9uIGNyZWF0ZWQgYmV0d2VlbiBhbiBTUkMgYW5kCiAgIFNSUyBmb3IgdGhlIHB1cnBvc2Ug
b2YgcmVjb3JkaW5nIGEgQ29tbXVuaWNhdGlvbiBTZXNzaW9uLgoKICAgRmlndXJlIDEgcGljdG9y
aWFsbHkgcmVwcmVzZW50cyB0aGUgcmVsYXRpb25zaGlwIGJldHdlZW4gYSBSZWNvcmRpbmcKICAg
U2Vzc2lvbiBhbmQgQ29tbXVuaWNhdGlvbiBTZXNzaW9uLgoKCgogICAgICstLS0tLS0tLS0tLS0t
KyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tKwogICAg
IHwgICAgICAgICAgICAgfCAgICAgICAgQ29tbXVuaWNhdGlvbiBTZXNzaW9uICAgICAgICAgfCAg
ICAgICAgICAgfAogICAgIHwgICAgIEEgICAgICAgfDwtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0+fCAgICAgQiAgICAgfAogICAgIHwgICAgICAgICAgICAgfCAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgfAogICAgICstLS0tLS0tLS0t
LS0tKyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tKwog
ICAgIC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLgogICAgIC4gICAgICAgICAgICAgICAgICAgICAgICAgICAgIFNlc3Npb24g
ICAgICAgICAgICAgICAgICAgICAgICAgICAgLgogICAgIC4gICAgICAgICAgICAgICAgICAgICAg
ICAgICAgUmVjb3JkaW5nICAgICAgICAgICAgICAgICAgICAgICAgICAgLgogICAgIC4gICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIENsaWVudCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
LgogICAgIC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwK
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IFJlY29yZGluZwogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgU2Vzc2lvbgogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICB2CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tKwogICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgIFNlc3Npb24gIHwKICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIHwgIFJlY29yZGluZyB8CiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICB8ICAgU2VydmVyICAgfAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKy0tLS0t
LS0tLS0tLSsKCgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBGaWd1cmUgMQoKICAg
TWV0YWRhdGE6IEluZm9ybWF0aW9uIHRoYXQgZGVzY3JpYmVzIHJlY29yZGVkIG1lZGlhIGFuZCB0
aGUgQ1MgdG8KICAgd2hpY2ggdGhleSByZWxhdGUuCgogICBQYXVzZSBhbmQgUmVzdW1lIGR1cmlu
ZyBhIENvbW11bmljYXRpb24gU2Vzc2lvbjogUGF1c2U6IFRoZSBhY3Rpb24gb2YKICAgdGVtcG9y
YXJpbHkgZGlzY29udGludWluZyB0aGUgdHJhbnNtaXNzaW9uIGFuZCBjb2xsZWN0aW9uIG9mIFJT
IG1lZGlhCiAgIFJlc3VtZTogVGhlIGFjdGlvbiBvZiByZWNvbW1lbmNpbmcgdGhlIHRyYW5zbWlz
c2lvbiBhbmQgY29sbGVjdGlvbiBvZgogICBSUyBtZWRpYQoKCgoKCgoKUmVob3IsIGV0IGFsLiAg
ICAgICAgICBFeHBpcmVzIFNlcHRlbWJlciAxNSwgMjAxMSAgICAgICAgICAgICAgIFtQYWdlIDVd
CgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgIFJlcXVpcmVtZW50cyBmb3IgU0lQUkVDICAgICAg
ICAgICAgICBNYXJjaCAyMDExCgoKNC4gIFVzZSBDYXNlcwoKICAgVXNlIENhc2UgMTogRnVsbC10
aW1lIFJlY29yZGluZzogT25lIFJlY29yZGluZyBTZXNzaW9uIGZvciBlYWNoCiAgIENvbW11bmlj
YXRpb24gU2Vzc2lvbi4KCiAgIEZvciBleGFtcGxlLCB0aGUgZGlhZ3JhbSBiZWxvdyBzaG93cyB0
aGUgbGlmZWN5Y2xlIG9mIENvbW11bmljYXRpb24KICAgU2Vzc2lvbnMgKENTKSBhbmQgdGhlIHJl
bGF0aW9uc2hpcCB0byB0aGUgUmVjb3JkaW5nIFNlc3Npb25zIChSUykKCiAgIENTICB8LS0tIENT
IDEgLS0tfCAgICAgIHwtLS0gQ1MgMiAtLS18ICAgICB8LS0tIENTIDMgLS0tfAoKICAgUlMgIHwt
LS0gUlMgMSAtLS18ICAgICAgfC0tLSBSUyAyIC0tLXwgICAgIHwtLS0gUlMgMyAtLS18CgogICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBGaWd1cmUgMgoKICAgUmVjb3JkIGV2ZXJ5IENT
IGZvciBzcGVjaWZpYyBleHRlbnNpb24vcGVyc29uLgoKICAgVGhlIG5lZWQgdG8gcmVjb3JkIGFs
bCBjYWxscyBpcyB0eXBpY2FsbHkgZHVlIHRvIGJ1c2luZXNzIHByb2Nlc3MKICAgcHVycG9zZXMg
KHN1Y2ggYXMgdHJhbnNhY3Rpb24gY29uZmlybWF0aW9uIG9yIGRpc3B1dGUgcmVzb2x1dGlvbikg
b3IKICAgdG8gZW5zdXJlIGNvbXBsaWFuY2Ugd2l0aCBnb3Zlcm5tZW50YWwgcmVndWxhdGlvbnMu
ICBBcHBsaWNhdGlvbnMKICAgaW5jbHVkZSBlbnRlcnByaXNlLCBjb250YWN0IGNlbnRlciwgYW5k
IGZpbmFuY2lhbCB0cmFkaW5nIGZsb29ycy4KCiAgIEFsc28gY29tbW9ubHkga25vd24gYXMgVG90
YWwgUmVjb3JkaW5nLgoKICAgVXNlIENhc2UgMjogU2VsZWN0aXZlIFJlY29yZGluZzogU3RhcnQg
YSBSZWNvcmRpbmcgU2Vzc2lvbiB3aGVuIGEKICAgQ29tbXVuaWNhdGlvbiBTZXNzaW9uIHRvIGJl
IHJlY29yZGVkIGlzIGVzdGFibGlzaGVkLgoKICAgSW4gdGhpcyBleGFtcGxlLCBDb21tdW5pY2F0
aW9uIFNlc3Npb25zIDEgYW5kIDMgYXJlIHJlY29yZGVkIGJ1dCBDUyAyCiAgIGlzIG5vdC4KCiAg
IENTICB8LS0tIENTIDEgLS0tfCAgICAgIHwtLS0gQ1MgMiAtLS18ICAgICB8LS0tIENTIDMgLS0t
fAoKICAgUlMgIHwtLS0gUlMgMS0tLS18ICAgICAgICAgICAgICAgICAgICAgICAgIHwtLS0gUlMg
MiAtLS18CgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBGaWd1cmUgMwoKICAgVXNl
IENhc2UgMzogU3RhcnQvU3RvcCBhIFJlY29yZGluZyBTZXNzaW9uIGR1cmluZyBhIENvbW11bmlj
YXRpb24KICAgU2Vzc2lvbi4KCiAgIFRoZSBSZWNvcmRpbmcgU2Vzc2lvbiBzdGFydHMgZHVyaW5n
IGEgQ29tbXVuaWNhdGlvbiBTZXNzaW9uLCBlaXRoZXIKICAgbWFudWFsbHkgdmlhIGEgdXNlci1j
b250cm9sbGVkIG1lY2hhbmlzbSAoZS5nLiBidXR0b24gb24gdXNlcidzCiAgIHBob25lKSBvciBh
dXRvbWF0aWNhbGx5IHZpYSBhbiBhcHBsaWNhdGlvbiAoZS5nLiBhIENvbnRhY3QgQ2VudGVyCiAg
IGN1c3RvbWVyIHNlcnZpY2UgYXBwbGljYXRpb24pIG9yIGJ1c2luZXNzIGV2ZW50LiAgQSBSZWNv
cmRpbmcgU2Vzc2lvbgogICBlaXRoZXIgZW5kcyBkdXJpbmcgdGhlIENvbW11bmljYXRpb24gU2Vz
c2lvbiwgb3Igd2hlbiB0aGUKICAgQ29tbXVuaWNhdGlvbiBTZXNzaW9uIGVuZHMuICBPbmUgb3Ig
bW9yZSBSZWNvcmRpbmcgU2Vzc2lvbnMgbWF5CiAgIHJlY29yZCBlYWNoIENvbW11bmljYXRpb24g
U2Vzc2lvbi4KCgoKCgoKUmVob3IsIGV0IGFsLiAgICAgICAgICBFeHBpcmVzIFNlcHRlbWJlciAx
NSwgMjAxMSAgICAgICAgICAgICAgIFtQYWdlIDZdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAg
IFJlcXVpcmVtZW50cyBmb3IgU0lQUkVDICAgICAgICAgICAgICBNYXJjaCAyMDExCgoKICAgQ1Mg
IHwtLS0tLS0tLS0tLS0tIENvbW11bmljYXRpb24gU2Vzc2lvbiAtLS0tLS0tLS0tLXwKCiAgIFJT
ICAgICAgICAgICB8LS0tLSBSUyAxIC0tLS18ICB8LS0tLSBSUyAyIC0tLS0tfAoKICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgRmlndXJlIDQKCiAgIFVzZSBDYXNlIDQ6IFBlcnNpc3Rl
bnQgUmVjb3JkaW5nOiBBIHNpbmdsZSBSZWNvcmRpbmcgU2Vzc2lvbiBjYXB0dXJlcwogICBvbmUg
b3IgbW9yZSBDb21tdW5pY2F0aW9uIFNlc3Npb25zLgoKCiAgICAgICAgICAgICB8LS0tIENTIDEg
LS0tfCAgICAgIHwtLS0gQ1MgMiAtLS18ICAgICB8LS0tIENTIDMgLS0tfAoKICAgUlMgIHwtLS0t
LS0tLS0tLS0tLS0tLS0tLS0tIFJlY29yZGluZyBTZXNzaW9uIC0tLS0tLS0tLS0tLS0tLS0tLS0t
LXwKCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEZpZ3VyZSA1CgogICBBIFJlY29y
ZGluZyBTZXNzaW9uIHJlY29yZHMgY29udGludW91c2x5IHdpdGhvdXQgaW50ZXJydXB0aW9uLgog
ICBQZXJpb2RzIHdoZW4gdGhlcmUgaXMgbm8gQ1MgaW4gcHJvZ3Jlc3MgbXVzdCBiZSByZXByb2R1
Y2VkIHVwb24KICAgcGxheWJhY2sgKGUuZy4gYnkgcmVjb3JkaW5nIHNpbGVuY2UgZHVyaW5nIHN1
Y2ggcGVyaW9kcyBvciBieSBub3QKICAgcmVjb3JkaW5nIHN1Y2ggcGVyaW9kcyBidXQgbWFya2lu
ZyB0aGVtIGJ5IG1lYW5zIG9mIG1ldGFkYXRhIGZvcgogICB1dGlsaXphdGlvbiBvbiBwbGF5YmFj
aywgZXRjLikuICBBcHBsaWNhdGlvbnMgaW5jbHVkZSBmaW5hbmNpYWwKICAgdHJhZGluZyBkZXNr
cyBhbmQgZW1lcmdlbmN5IChmaXJzdC1yZXNwb25kZXIpIHNlcnZpY2UgYnVyZWF1cy4gIFRoZQog
ICBsZW5ndGggb2YgYSBQZXJzaXN0ZW50IFJlY29yZGluZyBTZXNzaW9uIGlzIGluZGVwZW5kZW50
IGZyb20gdGhlCiAgIGxlbmd0aCBvZiB0aGUgYWN0dWFsIENvbW11bmljYXRpb24gU2Vzc2lvbnMu
ICBQZXJzaXN0ZW50IFJlY29yZGluZwogICBTZXNzaW9ucyBhdm9pZCBpc3N1ZXMgc3VjaCBhcyBt
ZWRpYSBjbGlwcGluZyB0aGF0IGNhbiBvY2N1ciBkdWUgdG8KICAgZGVsYXlzIGluIFJlY29yZGlu
ZyBTZXNzaW9uIGVzdGFibGlzaG1lbnQuCgogICBUaGUgY29ubmVjdGlvbiBhbmQgYXR0cmlidXRl
cyBvZiBtZWRpYSBpbiB0aGUgUmVjb3JkaW5nIFNlc3Npb24gYXJlCiAgIG5vdCBkeW5hbWljYWxs
eSBzaWduYWxlZCBmb3IgZWFjaCBDb21tdW5pY2F0aW9uIFNlc3Npb24gYmVmb3JlIGl0IGNhbgog
ICBiZSByZWNvcmRlZDsgaG93ZXZlciwgY29kZWMgcmUtbmVnb3RpYXRpb24gaXMgcG9zc2libGUu
CgogICBJbiBzb21lIGNhc2VzLCBtb3JlIHRoYW4gb25lIGNvbmN1cnJlbnQgQ29tbXVuaWNhdGlv
biBTZXNzaW9uIChvbiBhCiAgIHNpbmdsZSBlbmQtdXNlciBhcHBhcmF0dXMsIGUuZy4gdHJhZGlu
ZyBmbG9vciB0dXJyZXQpIGlzIG1peGVkIGludG8KICAgb25lIFJlY29yZGluZyBTZXNzaW9uOgoK
ICAgICAgICAgICAgICAgICB8LS0tLS0tLS0gQ1MgMSAtLS0tLS0tfAogICAgICAgICAgICAgICAg
ICAgIHwtLS0tLS0tLSBDUyAyIC0tLS0tLS18CiAgICAgICAgICAgICAgIHwtLS0tLS0tLSBDUyAz
IC0tLS0tLS18CgogICBSUyAgfC0tLS0tLS0tLS0tIFJlY29yZGluZyBTZXNzaW9uIC0tLS0tLS0t
LS0tLS0tfAoKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgRmlndXJlIDYKCiAgIFVz
ZSBDYXNlIDU6IFJlYWwtdGltZSBSZWNvcmRpbmcgQ29udHJvbHMuCgogICBGb3IgYW4gYWN0aXZl
IFJlY29yZGluZyBTZXNzaW9uLCBwcml2YWN5IG9yIHNlY3VyaXR5IHJlYXNvbnMgbWF5CiAgIGRl
bWFuZCBub3QgY2FwdHVyaW5nIGEgc3BlY2lmaWMgcG9ydGlvbiBvZiBhIGNvbnZlcnNhdGlvbi4g
IEFuCiAgIGV4YW1wbGUgaXMgZm9yIFBDSSAocGF5bWVudCBjYXJkIGluZHVzdHJ5KSBjb21wbGlh
bmNlIHdoZXJlIGNyZWRpdAoKCgpSZWhvciwgZXQgYWwuICAgICAgICAgIEV4cGlyZXMgU2VwdGVt
YmVyIDE1LCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgN10KDApJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICAgUmVxdWlyZW1lbnRzIGZvciBTSVBSRUMgICAgICAgICAgICAgIE1hcmNoIDIwMTEKCgog
ICBjYXJkIGluZm8gbXVzdCBiZSBwcm90ZWN0ZWQuICBPbmUgc29sdXRpb24gaXMgdG8gbm90IHJl
Y29yZCBhIGNhbGxlcgogICBzcGVha2luZyB0aGVpciBjcmVkaXQgY2FyZCBpbmZvcm1hdGlvbi4K
CiAgIEFuIGV4YW1wbGUgb2YgYSByZWFsLXRpbWUgY29udHJvbHMgaXMgUGF1c2UvUmVzdW1lLgoK
ICAgVXNlIENhc2UgNjogSVZSIC8gVm9pY2UgUG9ydGFsIFJlY29yZGluZy4KCiAgIFNlbGYtc2Vy
dmljZSBJbnRlcmFjdGl2ZSBWb2ljZSBSZXNwb25zZSBhcHBsaWNhdGlvbnMgbWF5IG5lZWQgdG8g
YmUKICAgcmVjb3JkZWQgZm9yIGFwcGxpY2F0aW9uIHBlcmZvcm1hbmNlIHR1bmluZyBvciB0byBt
ZWV0IGNvbXBsaWFuY2UKICAgcmVxdWlyZW1lbnRzLgoKICAgTWV0YWRhdGEgYWJvdXQgYW4gSVZS
IHNlc3Npb24gcmVjb3JkaW5nIG11c3QgaW5jbHVkZSBzZXNzaW9uCiAgIGluZm9ybWF0aW9uIGFu
ZCBtYXkgaW5jbHVkZSBhcHBsaWNhdGlvbiBjb250ZXh0IGluZm9ybWF0aW9uIChlLmcuCiAgIFZv
aWNlWE1MIHNlc3Npb24gdmFyaWFibGVzLCBkaWFsb2cgbmFtZXMsIGV0Yy4pCgogICBVc2UgQ2Fz
ZSA3OiBFbnRlcnByaXNlIE1vYmlsaXR5IFJlY29yZGluZy4KCiAgIE1hbnkgYWdlbnRzIGFuZCBl
bnRlcnByaXNlIHdvcmtlcnMgd2hvc2UgY2FsbHMgYXJlIHRvIGJlIHJlY29yZGVkIGFyZQogICBu
b3QgbG9jYXRlZCBvbiBjb21wYW55IHByZW1pc2VzLgoKICAgRXhhbXBsZXM6CgogICBvIEhvbWUt
YmFzZWQgYWdlbnRzIG9yIGVudGVycHJpc2Ugd29ya2Vycy4KCiAgIG8gTW9iaWxlIHBob25lcyBv
ZiBrbm93bGVkZ2Ugd29ya2VycyB3aGVuIHRoZXkgY29uZHVjdCB3b3JrIHJlbGF0ZWQKICAgKGFu
ZCBsZWdhbGx5IHJlcXVpcmVkIHJlY29yZGluZykgY2FsbHMuIGUuZy4gaW5zdXJhbmNlIGFnZW50
cywKICAgYnJva2VycywgcGh5c2ljaWFucy4KCiAgIFVzZSBDYXNlIDg6IEdlb2dyYXBoaWNhbGx5
IGRpc3RyaWJ1dGVkIG9yIGNlbnRyYWxpemVkIHJlY29yZGluZy4KCiAgIEVudGVycHJpc2VzIHN1
Y2ggYXMgYmFua3MsIGluc3VyYW5jZSBhZ2VuY2llcywgYW5kIHJldGFpbCBzdG9yZXMgbWF5CiAg
IGhhdmUgbWFueSBsb2NhdGlvbnMsIHBvc3NpYmx5IHVwIHRvIHRob3VzYW5kcyBvZiBzbWFsbCBz
aXRlcy4KICAgRnJlcXVlbnRseSBvbmx5IHBob25lcyBhbmQgbmV0d29yayBpbmZyYXN0cnVjdHVy
ZSBhcmUgaW5zdGFsbGVkIGluCiAgIGJyYW5jaGVzLCB3aXRob3V0IGxvY2FsIHJlY29yZGluZyBz
ZXJ2aWNlcy4gIEluIGNhc2VzIHdoZXJlIGNhbGxzCiAgIGluc2lkZSBvciBiZXR3ZWVuIGJyYW5j
aGVzIG11c3QgYmUgcmVjb3JkZWQsIGEgY2VudHJhbGl6ZWQgcmVjb3JkaW5nCiAgIHN5c3RlbSBp
biBkYXRhIGNlbnRlcnMgdG9nZXRoZXIgd2l0aCB0ZWxlcGhvbnkgaW5mcmFzdHJ1Y3R1cmUgKGUu
Zy4KICAgUEJYKSBtZSBkZXBsb3llZC4KCiAgIFVzZSBDYXNlIDk6IFJlY29yZCBjb21wbGV4IGNh
bGwgc2NlbmFyaW9zLgoKICAgVGhlIGZvbGxvd2luZyBpcyBhbiBleGFtcGxlIG9mIGEgc2NlbmFy
aW8gd2hlcmUgb25lIGNhbGwgdGhhdCBpcwogICByZWNvcmRlZCBtdXN0IGJlIGFzc29jaWF0ZWQg
d2l0aCBhIHJlbGF0ZWQgY2FsbCB0aGF0IGFsc28gbXVzdCBiZQogICByZWNvcmRlZC4KCiAgIG8g
QSBDdXN0b21lciBpcyBpbiBhIGNvbnZlcnNhdGlvbiB3aXRoIGEgQ3VzdG9tZXIgU2VydmljZSBB
Z2VudC4KCiAgIG8gQWdlbnQgcHV0cyBDdXN0b21lciBvbiBob2xkIGluIG9yZGVyIHRvIGNvbnN1
bHQgd2l0aCBhIFN1cGVydmlzb3IuCgoKCgpSZWhvciwgZXQgYWwuICAgICAgICAgIEV4cGlyZXMg
U2VwdGVtYmVyIDE1LCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgOF0KDApJbnRlcm5ldC1EcmFm
dCAgICAgICAgICAgUmVxdWlyZW1lbnRzIGZvciBTSVBSRUMgICAgICAgICAgICAgIE1hcmNoIDIw
MTEKCgogICBvIEFnZW50IGVudGVycyBpbnRvIGEgY29udmVyc2F0aW9uIHdpdGggU3VwZXJ2aXNv
ci4KCiAgIG8gQWdlbnQgZGlzY29ubmVjdHMgZnJvbSBTdXBlcnZpc29yLCB0aGVuIHJlY29ubmVj
dHMgd2l0aCBDdXN0b21lci4KCiAgIG8gVGhlIFN1cGVydmlzb3IgY2FsbCBtdXN0IGJlIGFzc29j
aWF0ZWQgd2l0aCB0aGUgb3JpZ2luYWwgY3VzdG9tZXIKICAgY2FsbC4KCiAgIFVzZSBjYXNlIDEw
OiBIaWdoIGF2YWlsYWJpbGl0eSBhbmQgY29udGludW91cyByZWNvcmRpbmcuCgogICBTcGVjaWZp
YyBkZXBsb3ltZW50IHNjZW5hcmlvcyBwcmVzZW50IGRpZmZlcmVudCByZXF1aXJlbWVudHMgZm9y
CiAgIHN5c3RlbSBhdmFpbGFiaWxpdHksIGVycm9yIGhhbmRsaW5nLCBldGMuIGluY2x1ZGluZzoK
CiAgIG8gQW4gU1JTIG11c3QgYWx3YXlzIGJlIGF2YWlsYWJsZSBhdCBjYWxsIHNldHVwIHRpbWUu
CgogICBvIE5vIGxvc3Mgb2YgbWVkaWEgcmVjb3JkaW5nLCBpbmNsdWRpbmcgZHVyaW5nIGZhaWx1
cmUgb2YgYW4gU1JTLgoKICAgbyBUaGUgQ29tbXVuaWNhdGlvbiBTZXNzaW9uIG11c3QgYmUgdGVy
bWluYXRlZCAob3Igc3VpdGFibGUKICAgbm90aWZpY2F0aW9uIGdpdmVuIHRvIHBhcnRpZXMpIGlu
IHRoZSBldmVudCBvZiBhIHJlY29yZGluZyBmYWlsdXJlLgoKICAgVXNlIENhc2UgMTE6IFJlY29y
ZCBtdWx0aS1jaGFubmVsLCBtdWx0aS1tZWRpYSBzZXNzaW9uLgoKICAgU29tZSBhcHBsaWNhdGlv
bnMgcmVxdWlyZSB0aGUgcmVjb3JkaW5nIG9mIG1vcmUgdGhhbiBvbmUgbWVkaWEKICAgc3RyZWFt
LCBwb3NzaWJseSBvZiBkaWZmZXJlbnQgdHlwZXMuICBNZWRpYSBhcmUgc3luY2hyb25pemVkLCBl
aXRoZXIKICAgYXQgc3RvcmFnZSBvciBhdCBwbGF5YmFjay4KCiAgIFNwZWVjaCBhbmFseXRpY3Mg
dGVjaG5vbG9naWVzIChlLmcuIHdvcmQgc3BvdHRpbmcsIGVtb3Rpb24gZGV0ZWN0aW9uLAogICBz
cGVha2VyIGlkZW50aWZpY2F0aW9uKSBtYXkgcmVxdWlyZSBzcGVha2VyLXNlcGFyYXRlZCByZWNv
cmRpbmdzIGZvcgogICBvcHRpbXVtIHBlcmZvcm1hbmNlLgoKICAgTXVsdGktbW9kYWwgQ29udGFj
dCBDZW50ZXJzIG1heSBpbmNsdWRlIGF1ZGlvLCB2aWRlbywgSU0gb3Igb3RoZXIKICAgaW50ZXJh
Y3Rpb24gbW9kYWxpdGllcy4KCiAgIEluIHRyYWRpbmcgZmxvb3JzIGVudmlyb25tZW50cywgaW4g
b3JkZXIgdG8gbWluaW1pemUgc3RvcmFnZSBhbmQKICAgcmVjb3JkaW5nIHN5c3RlbSByZXNvdXJj
ZXMsIGl0IG1heSBiZSBwcmVmZXJhYmxlIHRvIG1peCBtdWx0aXBsZQogICBjb25jdXJyZW50IGNh
bGxzIChDb21tdW5pY2F0aW9uIFNlc3Npb25zKSBvbiBkaWZmZXJlbnQgaGFuZHNldHMvCiAgIHNw
ZWFrZXJzIG9uIHRoZSBzYW1lIHR1cnJldCBpbnRvIHNpbmdsZSByZWNvcmRpbmcgc2Vzc2lvbi4K
CiAgIFVzZSBDYXNlIDEyOiBSZWFsLXRpbWUgbWVkaWEgcHJvY2Vzc2luZy4KCiAgIEl0IG11c3Qg
YmUgcG9zc2libGUgZm9yIGFuIFNSUyB0byBzdXBwb3J0IHJlYWwtdGltZSBtZWRpYSBwcm9jZXNz
aW5nLAogICBzdWNoIGFzIHNwZWVjaCBhbmFseXRpY3Mgb2YgdHJhZGluZyBmbG9vciBpbnRlcmFj
dGlvbnMuICBSZWFsLXRpbWUKICAgYW5hbHl0aWNzIG1heSBiZSBlbXBsb3llZCBmb3IgYXV0b21h
dGljIGludGVydmVudGlvbiAoc3RvcHBpbmcKICAgaW50ZXJhY3Rpb24gb3IgYWxlcnRpbmcpIGlm
IGZvciBleGFtcGxlLCBhIHRyYWRlciBpcyBub3QgZm9sbG93aW5nCiAgIHJlZ3VsYXRpb25zLgoK
ICAgU3BlYWtlciBzZXBhcmF0aW9uIGlzIHJlcXVpcmVkIGluIG9yZGVyIHRvIHJlbGlhYmx5IGRl
dGVjdCB3aG8gaXMKICAgc2F5aW5nIHNwZWNpZmljIHBocmFzZXMuCgoKCgpSZWhvciwgZXQgYWwu
ICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE1LCAyMDExICAgICAgICAgICAgICAgW1BhZ2Ug
OV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgUmVxdWlyZW1lbnRzIGZvciBTSVBSRUMgICAg
ICAgICAgICAgIE1hcmNoIDIwMTEKCgo1LiAgUmVxdWlyZW1lbnRzCgogICBUaGUgZm9sbG93aW5n
IGFyZSByZXF1aXJlbWVudHMgZm9yIFNJUC1iYXNlZCBNZWRpYSBSZWNvcmRpbmc6CgogICBvIFJF
US0wMDEgVGhlIG1lY2hhbmlzbSBNVVNUIHByb3ZpZGUgYSBtZWFucyBmb3IgdXNpbmcgdGhlIFNJ
UAogICBwcm90b2NvbCBmb3IgZXN0YWJsaXNoaW5nLCBtYWludGFpbmluZyBhbmQgdGVybWluYXRp
bmcgUmVjb3JkaW5nCiAgIFNlc3Npb25zIGJldHdlZW4gYSBTZXNzaW9uIFJlY29yZGluZyBDbGll
bnQgYW5kIGEgU2Vzc2lvbiBSZWNvcmRpbmcKICAgU2VydmVyLgoKICAgbyBSRVEtMDAyIFRoZSBt
ZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5IHRvIHJlY29yZCBhbGwgQ1NzIGluCiAg
IHRoZWlyIGVudGlyZXR5LgoKICAgbyBSRVEtMDAzIFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0
IHRoZSBhYmlsaXR5IHRvIHJlY29yZCBzZWxlY3RlZAogICBDU3MgaW4gdGhlaXIgZW50aXJldHks
IGFjY29yZGluZyB0byBwb2xpY3kuCgogICBvIFJFUS0wMDQgVGhlIG1lY2hhbmlzbSBNVVNUIHN1
cHBvcnQgdGhlIGFiaWxpdHkgdG8gcmVjb3JkIHNlbGVjdGVkCiAgIHBhcnRzIG9mIHNlbGVjdGVk
IENTcy4KCiAgIG8gUkVRLTAwNSBUaGUgbWVjaGFuaXNtIE1VU1Qgc3VwcG9ydCB0aGUgYWJpbGl0
eSB0byByZWNvcmQgYSBDUwogICB3aXRob3V0IGxvc3Mgb2YgbWVkaWEgKGZvciBleGFtcGxlLCBj
bGlwcGluZyBtZWRpYSBhdCB0aGUgYmVnaW5uaW5nCiAgIG9mIHRoZSBDUykgZHVlIHRvIFJTIHJl
Y29yZGluZyBwcmVwYXJhdGlvbiBhbmQgYWxzbywgd2l0aG91dAogICBpbXBhY3RpbmcgdGhlIHF1
YWxpdHkgb3IgdGltaW5nIG9mIHRoZSBDUyAoZm9yIGV4YW1wbGUsIGRlbGF5aW5nIHRoZQogICBz
dGFydCBvZiB0aGUgQ1Mgd2hpbGUgcHJlcGFyYXRpb24gZm9yIHJlY29yZGluZyBzZXNzaW9uKS4g
IFNlZSBVc2UKICAgQ2FzZSA0IGluIFNlY3Rpb24gNCBmb3IgbW9yZSBkZXRhaWxzLgoKICAgbyBS
RVEtMDA2IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSByZWNvcmRpbmcgb2YgSVZSIHNl
c3Npb25zLgoKICAgbyBSRVEtMDA3IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSByZWNv
cmRpbmcgb2YgUlRQIG1lZGlhIHR5cGVzCiAgIHZvaWNlLCBEVE1GIChhcyBkZWZpbmVkIGJ5IFtS
RkM0NzMzXSksIHZpZGVvLCBhbmQgdGV4dCAoYXMgZGVmaW5lZCBieQogICBbUkZDNDEwM10pLgoK
ICAgbyBSRVEtMDA4IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5IGZvciBh
biBTUkMgdG8KICAgZGVsaXZlciBtaXhlZCBhdWRpbyBzdHJlYW1zIGZyb20gbXVsdGlwbGUgQ29t
bXVuaWNhdGlvbiBTZXNzaW9ucyB0bwogICBhbiBTUlMuCgogICBOb3RlOiBBIG1peGVkIGF1ZGlv
IHN0cmVhbSBpcyB3aGVyZSBzZXZlcmFsIHJlbGF0ZWQgQ29tbXVuaWNhdGlvbgogICBTZXNzaW9u
cyBhcmUgY2FycmllZCBpbiBhIHNpbmdsZSBSZWNvcmRpbmcgU2Vzc2lvbi4gIEEgbWl4ZWQgbWVk
aWEKICAgc3RyZWFtIGlzIHR5cGljYWxseSBwcm9kdWNlZCBieSBhIG1peGVyIGZ1bmN0aW9uLiAg
VGhlIFJTIE1BWSBiZQogICBpbmZvcm1lZCBhYm91dCB0aGUgY29tcG9zaXRpb24gb2YgdGhlIG1p
eGVkIHN0cmVhbXMgdGhyb3VnaCBzZXNzaW9uCiAgIG1ldGFkYXRhLgoKICAgbyBSRVEtMDA5OiBU
aGUgbWVjaGFuaXNtIE1VU1Qgc3VwcG9ydCB0aGUgYWJpbGl0eSBmb3IgYW4gU1JDIHRvCiAgIGRl
bGl2ZXIgbWl4ZWQgYXVkaW8gc3RyZWFtcyBmcm9tIGRpZmZlcmVudCBwYXJ0aWVzIG9mIGEgZ2l2
ZW4KICAgQ29tbXVuaWNhdGlvbiBTZXNzaW9uIHRvIGFuIFNSUy4KCiAgIG8gUkVRLTAxMCBUaGUg
bWVjaGFuaXNtIE1VU1Qgc3VwcG9ydCB0aGUgYWJpbGl0eSB0byBkZWxpdmVyIHRvIHRoZQogICBT
UlMgbXVsdGlwbGUgbWVkaWEgc3RyZWFtcyBmb3IgYSBnaXZlbiBDUy4KCgoKClJlaG9yLCBldCBh
bC4gICAgICAgICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTUsIDIwMTEgICAgICAgICAgICAgIFtQYWdl
IDEwXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICBSZXF1aXJlbWVudHMgZm9yIFNJUFJFQyAg
ICAgICAgICAgICAgTWFyY2ggMjAxMQoKCiAgIG8gUkVRLTAxMSBUaGUgbWVjaGFuaXNtIE1VU1Qg
c3VwcG9ydCB0aGUgYWJpbGl0eSB0byBwYXVzZSBhbmQgcmVzdW1lCiAgIHRoZSB0cmFuc21pc3Np
b24gYW5kIGNvbGxlY3Rpb24gb2YgUlMgbWVkaWEuCgogICBvIFJFUS0wMTIgVGhlIG1lY2hhbmlz
bSBNVVNUIHByb3ZpZGUgdGhlIFNSUyB3aXRoIG1ldGFkYXRhIGRlc2NyaWJpbmcKICAgQ1NzIHRo
YXQgYXJlIGJlaW5nIHJlY29yZGVkLCBpbmNsdWRpbmcgdGhlIG1lZGlhIGJlaW5nIHVzZWQgYW5k
IHRoZQogICBpZGVudGl0aWVzIG9mIHBhcnRpZXMgaW52b2x2ZWQuCgogICBvIFJFUS0wMTMgVGhl
IG1lY2hhbmlzbSBNVVNUIHByb3ZpZGUgdGhlIFNSUyB3aXRoIHRoZSBtZWFucyB0bwogICBjb3Jy
ZWxhdGUgUlMgbWVkaWEgd2l0aCBDUyBwYXJ0aWNpcGFudCBtZWRpYS4KCiAgIG8gUkVRLTAxNCBN
ZXRhZGF0YSBmb3JtYXQgbXVzdCBiZSBhZ25vc3RpYyBvZiB0aGUgdHJhbnNwb3J0IHByb3RvY29s
LgoKICAgbyBSRVEtMDE1OiBUaGUgbWVjaGFuaXNtIE1VU1Qgc3VwcG9ydCBhIG1lYW5zIHRvIHN0
b3AgdGhlIHJlY29yZGluZy4KCiAgIG8gUkVRLTAxNjogVGhlIG1lY2hhbmlzbSBNVVNUIHN1cHBv
cnQgYSBtZWFucyBmb3IgYSByZWNvcmRpbmctYXdhcmUKICAgVUEgaW52b2x2ZWQgaW4gYSBDUyB0
byByZXF1ZXN0IGF0IHNlc3Npb24gZXN0YWJsaXNobWVudCB0aW1lIHRoYXQgdGhlCiAgIENTIHNo
b3VsZCBiZSByZWNvcmRlZCBvciBzaG91bGQgbm90IGJlIHJlY29yZGVkLCB0aGUgaG9ub3Jpbmcg
b2Ygc3VjaAogICBhIHJlcXVlc3QgYmVpbmcgZGVwZW5kZW50IG9uIHBvbGljeS4KCiAgIG8gUkVR
LTAxNzogVGhlIG1lY2hhbmlzbSBNVVNUIHN1cHBvcnQgYSBtZWFucyBmb3IgYSByZWNvcmRpbmct
YXdhcmUKICAgVUEgaW52b2x2ZWQgaW4gYSBDUyB0byByZXF1ZXN0IGR1cmluZyBhIHNlc3Npb24g
dGhhdCB0aGUgcmVjb3JkaW5nIG9mCiAgIHRoZSBDUyBzaG91bGQgYmUgc3RhcnRlZCwgcGF1c2Vk
LCByZXN1bWVkIG9yIHN0b3BwZWQsIHRoZSBob25vcmluZyBvZgogICBzdWNoIGEgcmVxdWVzdCBi
ZWluZyBkZXBlbmRlbnQgb24gcG9saWN5LgoKICAgbyBSRVEtMDE4IFRoZSBtZWNoYW5pc20gTVVT
VCBOT1QgcHJldmVudCB0aGUgYXBwbGljYXRpb24gb2YgdG9uZXMgb3IKICAgYW5ub3VuY2VtZW50
cyBkdXJpbmcgcmVjb3JkaW5nIG9yIGF0IHRoZSBzdGFydCBvZiBhIENTIHRvIHN1cHBvcnQKICAg
bm90aWZpY2F0aW9uIHRvIHBhcnRpY2lwYW50cyB0aGF0IHRoZSBjYWxsIGlzIGJlaW5nIHJlY29y
ZGVkIG9yIG1heQogICBiZSByZWNvcmRlZC4KCiAgIG8gUkVRLTAxOSBUaGUgbWVjaGFuaXNtIE1V
U1QgcHJvdmlkZSBhIG1lYW5zIG9mIGluZGljYXRpbmcgdG8KICAgcmVjb3JkaW5nLWF3YXJlIFVB
cyB3aGV0aGVyIHJlY29yZGluZyBpcyB0YWtpbmcgcGxhY2UsIGZvcgogICBhcHByb3ByaWF0ZSBy
ZW5kZXJpbmcgYXQgdGhlIHVzZXIgaW50ZXJmYWNlLgoKICAgbyBSRVEtMDIwIFRoZSBtZWNoYW5p
c20gTVVTVCBwcm92aWRlIGEgd2F5IGZvciBtZXRhZGF0YSB0byBiZQogICBjb252ZXllZCB0byB0
aGUgU1JTIGluY3JlbWVudGFsbHkgZHVyaW5nIHRoZSBDUy4KCiAgIG8gUkVRLTAyMSBUaGUgbWVj
aGFuaXNtIE1VU1QgTk9UIHByZXZlbnQgaGlnaCBhdmFpbGFiaWxpdHkKICAgZGVwbG95bWVudHMu
CgogICBvIFJFUS0wMjIgVGhlIG1lY2hhbmlzbSBNVVNUIHByb3ZpZGUgdGhlIFNSUyB0aGUgc3Rh
cnRpbmcgd2FsbCBjbG9jawogICB0aW1lIGZvciBlYWNoIFJTIG1lZGlhIHN0cmVhbSBjb3JyZXNw
b25kaW5nIHRvIHRoZSBDUyBwYXJ0aWNpcGFudAogICBtZWRpYS4KCiAgIG8gUkVRLTAyMyBUaGUg
bWVjaGFuaXNtIE1VU1QgcHJvdmlkZSB0aGUgU1JTIHRoZSB3YWxsIGNsb2NrIHRpbWUgd2hlbgog
ICB0aGUgUmVjb3JkaW5nIFNlc3Npb24gaXMgcGF1c2VkIGFuZCByZXN1bWVkLgoKICAgbyBSRVEt
MDI0IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IGZ1bmN0aW9uYWxpdHkgc3VjaCB0aGF0IGlm
IHRoZQogICBDUyBpcyBlbmNyeXB0ZWQsIHRoZSBSUyBtYXkgdXNlIHRoZSBzYW1lIG9yIGRpZmZl
cmVudCBlbmNyeXB0aW9uCgoKClJlaG9yLCBldCBhbC4gICAgICAgICAgRXhwaXJlcyBTZXB0ZW1i
ZXIgMTUsIDIwMTEgICAgICAgICAgICAgIFtQYWdlIDExXQoMCkludGVybmV0LURyYWZ0ICAgICAg
ICAgICBSZXF1aXJlbWVudHMgZm9yIFNJUFJFQyAgICAgICAgICAgICAgTWFyY2ggMjAxMQoKCiAg
IGtleXMuCgogICBvIFJFUS0wMjUgVGhlIG1lY2hhbmlzbSBNVVNUIHByb3ZpZGUgbWVhbnMgZm9y
IGFuIFNSUyB0byBhdXRoZW50aWNhdGUKICAgdGhlIFNSQyBvbiBSUyBpbml0aWF0aW9uLgoKICAg
byBSRVEtMDI2IFRoZSBtZWNoYW5pc20gTVVTVCBwcm92aWRlIG1lYW5zIGZvciBhbiBTUkMgdG8g
YXV0aGVudGljYXRlCiAgIHRoZSBTUlMgb24gUlMgaW5pdGlhdGlvbi4KCiAgIG8gUkVRLTAyNyBU
aGUgbWVjaGFuaXNtIE1VU1QgZW5zdXJlIHRoYXQgdGhlIGludGVncml0eSBvZiB0aGUKICAgbWV0
YWRhdGEgc2VudCBmcm9tIFNSQyB0byBTUlMgaXMgYW4gYWNjdXJhdGUgcmVwcmVzZW50YXRpb24g
b2YgdGhlCiAgIG9yaWdpbmFsIENTIG1ldGFkYXRhLgoKICAgbyBSRVEtMDI4IFRoZSBtZWNoYW5p
c20gTVVTVCBlbnN1cmUgdGhhdCB0aGUgaW50ZWdyaXR5IG9mIHRoZSBtZWRpYQogICBzZW50IGZy
b20gU1JDIHRvIFNSUyBpcyBhbiBhY2N1cmF0ZSByZXByZXNlbnRhdGlvbiBvZiB0aGUgb3JpZ2lu
YWwgQ1MKICAgbWVkaWEuCgogICBvIFJFUS0wMjkgVGhlIG1lY2hhbmlzbSBNVVNUIGVuc3VyZSB0
aGUgY29uZmlkZW50aWFsaXR5IG9mIHRoZQogICBNZXRhZGF0YSBzZW50IGZyb20gU1JDIHRvIFNS
Uy4KCiAgIG8gUkVRLTAzMCBUaGUgbWVjaGFuaXNtIE1VU1QgcHJvdmlkZSBhIG1lYW5zIHRvIHN1
cHBvcnQgUlMKICAgY29uZmlkZW50aWFsaXR5LgoKICAgbyBSRVEtMDMxIFRoZSBtZWNoYW5pc20g
TVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5IHRvIGRlbGl2ZXIgdG8gdGhlCiAgIFNSUyBtdWx0aXBs
ZSBtZWRpYSBzdHJlYW1zIG9mIHRoZSBzYW1lIG1lZGlhIHR5cGUgKGUuZy4gYXVkaW8sCiAgIHZp
ZGVvKS4gIEZvciBleGFtcGxlIGluIHRoZSBjYXNlIG9mIGRlbGl2ZXJpbmcgdW5taXhlZCBhdWRp
byBmb3IgZWFjaAogICBwYXJ0aWNpcGFudCBpbiB0aGUgQ1MuCgoKNi4gIFByaXZhY3kgQ29uc2lk
ZXJhdGlvbnMKCiAgIFJlc3BlY3RpbmcgdGhlIHByaXZhY3kgcmlnaHRzIGFuZCB3aXNoZXMgb2Yg
dXNlcnMgZW5nYWdlZCBpbiBhIGNhbGwKICAgaXMgb2YgcGFyYW1vdW50IGltcG9ydGFuY2UuICBJ
biBtYW55IGp1cmlzZGljdGlvbnMgcGFydGljaXBhbnRzIGhhdmUKICAgYSByaWdodCB0byBrbm93
IHRoYXQgdGhlIHNlc3Npb24gaXMgYmVpbmcgcmVjb3JkZWQgb3IgbWlnaHQgYmUKICAgcmVjb3Jk
ZWQsIGFuZCBoYXZlIGEgcmlnaHQgdG8gb3B0IG91dCwgZWl0aGVyIGJ5IHRlcm1pbmF0aW5nIHRo
ZSBjYWxsCiAgIG9yIGJ5IGRlbWFuZGluZyB0aGF0IHRoZSBjYWxsIG5vdCBiZSByZWNvcmRlZC4g
IFRoZXJlZm9yZSB0aGlzCiAgIGRvY3VtZW50IGNvbnRhaW5zIHJlcXVpcmVtZW50cyBmb3IgYmVp
bmcgYWJsZSB0byBub3RpZnkgdXNlcnMgdGhhdCBhCiAgIGNhbGwgaXMgYmVpbmcgcmVjb3JkZWQg
YW5kIGZvciB1c2VycyB0byBiZSBhYmxlIHRvIHJlcXVlc3QgdGhhdCBhCiAgIGNhbGwgbm90IGJl
IHJlY29yZGVkLiAgVXNlIGNhc2VzIHdoZXJlIHVzZXJzIHBhcnRpY2lwYXRpbmcgaW4gYSBjYWxs
CiAgIGFyZSBub3QgaW5mb3JtZWQgdGhhdCB0aGUgY2FsbCBpcyBvciBtaWdodCBiZSByZWNvcmRl
ZCBhcmUgb3V0c2lkZQogICB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudC4gIEluIHBhcnRpY3Vs
YXIsIGxhd2Z1bCBpbnRlcmNlcHQgaXMKICAgb3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1
bWVudC4KCiAgIFJlcXVpcmVtZW50cyBmb3IgcGFydGljaXBhbnQgbm90aWZpY2F0aW9uIG9mIHJl
Y29yZGluZyB2YXJ5IHdpZGVseSBieQogICBqdXJpc2RpY3Rpb24uICBJbiBhIGdpdmVuIGRlcGxv
eW1lbnQsIG5vdCBhbGwgdXNlcnMgd2lsbCBiZQogICBhdXRob3JpemVkIHRvIHN0b3AgdGhlIHJl
Y29yZGluZyBvZiBhIENTIChhbHRob3VnaCBhbnkgdXNlciBjYW4KICAgdGVybWluYXRlIGEgQ1Mp
LiAgVHlwaWNhbGx5IHVzZXJzIHdpdGhpbiB0aGUgZG9tYWluIHRoYXQgaXMgY2FycnlpbmcKICAg
b3V0IHRoZSByZWNvcmRpbmcgd2lsbCBiZSBzdWJqZWN0IHRvIHBvbGljaWVzIG9mIHRoYXQgZG9t
YWluCiAgIGNvbmNlcm5pbmcgd2hldGhlciBDU3MgYXJlIHJlY29yZGVkLiAgRm9yIGV4YW1wbGUs
IGluIGEgY2FsbCBjZW50cmUsCgoKClJlaG9yLCBldCBhbC4gICAgICAgICAgRXhwaXJlcyBTZXB0
ZW1iZXIgMTUsIDIwMTEgICAgICAgICAgICAgIFtQYWdlIDEyXQoMCkludGVybmV0LURyYWZ0ICAg
ICAgICAgICBSZXF1aXJlbWVudHMgZm9yIFNJUFJFQyAgICAgICAgICAgICAgTWFyY2ggMjAxMQoK
CiAgIGFnZW50cyB3aWxsIGJlIHN1YmplY3QgdG8gcG9saWNpZXMgb2YgdGhlIGNhbGwgY2VudHJl
IGFuZCBtYXkgb3IgbWF5CiAgIG5vdCBoYXZlIHRoZSByaWdodCB0byBwcmV2ZW50IHRoZSByZWNv
cmRpbmcgb2YgYSBDUyBvciBwYXJ0IG9mIGEgQ1MuCiAgIFVzZXJzIGNhbGxpbmcgaW50byB0aGUg
Y2FsbCBjZW50cmUsIG9uIHRoZSBvdGhlciBoYW5kLCB3aWxsIHR5cGljYWxseQogICBoYXZlIHRv
IGFzayB0aGUgYWdlbnQgbm90IHRvIHJlY29yZCB0aGUgQ1MuICBJZiB0aGUgYWdlbnQgaXMgdW5h
YmxlCiAgIHRvIHByZXZlbnQgcmVjb3JkaW5nLCBvciBpZiB0aGUgY2FsbGVyIGRvZXMgbm90IHRy
dXN0IHRoZSBhZ2VudCwgdGhlCiAgIG9ubHkgb3B0aW9uIGdlbmVyYWxseSBpcyB0byB0ZXJtaW5h
dGUgdGhlIENTLgoKICAgUHJpdmFjeSBjb25zaWRlcmF0aW9ucyBhbHNvIGV4dGVuZCB0byB3aGF0
IGhhcHBlbnMgdG8gYSByZWNvcmRpbmcKICAgb25jZSBpdCBoYXMgYmVlbiBjcmVhdGVkLiAgVHlw
aWNhbCBpc3N1ZXMgYXJlIHdobyBjYW4gYWNjZXNzIHRoZQogICByZWNvcmRpbmcgKGUuZy4sIHJl
Y2VpdmUgYSBjb3B5IG9mIHRoZSByZWNvcmRpbmcsIHZpZXcgdGhlIG1ldGFkYXRhLAogICBwbGF5
IGJhY2sgdGhlIG1lZGlhLCBldGMuKSwgZm9yIHdoYXQgcHVycG9zZSB0aGUgcmVjb3JkaW5nIGNh
biBiZQogICB1c2VkIChlLmcuLCBmb3Igbm9uLXJlcHVkaWF0aW9uLCBmb3IgdHJhaW5pbmcgcHVy
cG9zZXMsIGZvciBxdWFsaXR5CiAgIGNvbnRyb2wgcHVycG9zZXMsIGV0Yy4pIGFuZCBmb3IgaG93
IGxvbmcgdGhlIHJlY29yZGluZyBpcyB0byBiZQogICByZXRhaW5lZCBiZWZvcmUgZGVsZXRpb24u
ICBUaGVzZSBhcmUgdHlwaWNhbGx5IHBvbGljaWVzIG9mIHRoZSBkb21haW4KICAgdGhhdCBtYWtl
cyB0aGUgcmVjb3JkaW5nLCByYXRoZXIgdGhhbiBwb2xpY2llcyBvZiBpbmRpdmlkdWFsIHVzZXJz
CiAgIGludm9sdmVkIGluIGEgcmVjb3JkZWQgQ1MsIHdoZXRoZXIgdGhvc2UgdXNlcnMgYmUgaW4g
dGhlIHNhbWUgZG9tYWluCiAgIG9yIGluIGEgZGlmZmVyZW50IGRvbWFpbi4gIFRha2luZyB0aGUg
Y2FsbCBjZW50cmUgZXhhbXBsZSBhZ2FpbiwKICAgYWdlbnRzIG1pZ2h0IGJlIG1hZGUgYXdhcmUg
b2YgY2FsbCBjZW50cmUgcG9saWN5IHJlZ2FyZGluZyByZXRlbnRpb24KICAgYW5kIHVzZSBvZiBy
ZWNvcmRpbmdzIGFzIHBhcnQgb2YgdGhlaXIgZW1wbG95bWVudCBjb250cmFjdCwgYW5kCiAgIGNh
bGxlcnMgZnJvbSBvdXRzaWRlIHRoZSBjYWxsIGNlbnRyZSBtaWdodCBiZSBnaXZlbiBzb21lIGlu
Zm9ybWF0aW9uCiAgIGFib3V0IHBvbGljeSB3aGVuIG5vdGlmaWVkIHRoYXQgYSBDUyB3aWxsIGJl
IHJlY29yZGVkIChlLmcuLCB0aHJvdWdoCiAgIGFuIGFubm91bmNlbWVudCB0aGF0IHNheXMgdGhh
dCBjYWxscyBtYXkgYmUgcmVjb3JkZWQgZm9yIHF1YWxpdHkKICAgcHVycG9zZXMpLgoKICAgVGhp
cyBkb2N1bWVudCBkb2VzIG5vdCBzcGVjaWZ5IGFueSByZXF1aXJlbWVudHMgZm9yIGEgdXNlciBl
bmdhZ2VkIGluCiAgIGEgQ1MgdG8gYmUgYWJsZSB0byBkaWN0YXRlIHBvbGljeSBmb3Igd2hhdCBo
YXBwZW5zIHRvIGEgcmVjb3JkaW5nLCBvcgogICBmb3Igc3VjaCBpbmZvcm1hdGlvbiB0byBiZSBj
b252ZXllZCBmcm9tIGFuIFNSQyB0byBhbiBTUlMuICBJdCBpcwogICBhc3N1bWVkIHRoYXQgdGhl
IFNSUyBoYXMgYWNjZXNzIHRvIHBvbGljeSBhcHBsaWNhYmxlIHRvIGl0cwogICBlbnZpcm9ubWVu
dCBhbmQgY2FuIGVuc3VyZSB0aGF0IHJlY29yZGluZ3MgYXJlIHN0b3JlZCBhbmQgdXNlZCBpbgog
ICBhY2NvcmRhbmNlIHdpdGggdGhhdCBwb2xpY3kuCgoKNy4gIFNlY3VyaXR5IENvbnNpZGVyYXRp
b25zCgogICBTZXNzaW9uIHJlY29yZGluZyBoYXMgc3Vic3RhbnRpYWwgc2VjdXJpdHkgaW1wbGlj
YXRpb25zLCBmb3IgdGhlIFNJUAogICBVQSdzIGJlaW5nIHJlY29yZGVkLCB0aGUgU1JDLCBhbmQg
dGhlIFNSUy4KCiAgIEZvciB0aGUgU0lQIFVBJ3MgaW52b2x2ZWQgaW4gdGhlIENvbW11bmljYXRp
b24gU2Vzc2lvbiwgdGhlCiAgIHJlcXVpcmVtZW50cyBpbiB0aGlzIGRyYWZ0IGVuYWJsZSB0aGUg
VUEgdG8gaWRlbnRpZnkgdGhhdCBhCiAgIENvbW11bmljYXRpb24gU2Vzc2lvbiBpcyBiZWluZyBy
ZWNvcmRlZCBhbmQgZm9yIHRoZSBVQSB0byByZXF1ZXN0CiAgIHRoYXQgYSBnaXZlbiBDb21tdW5p
Y2F0aW9uIFNlc3Npb24gaXMgbm90IHN1YmplY3QgdG8gcmVjb3JkaW5nLgoKICAgU2luY2UgaHVt
YW5zIGRvbid0IHR5cGljYWxseSBsb29rIGF0IG9yIGtub3cgYWJvdXQgcHJvdG9jb2wgc2lnbmFs
aW5nCiAgIHN1Y2ggYXMgU0lQLCBhbmQgaW5kZWVkIHRoZSBTSVAgc2Vzc2lvbiBtaWdodCBoYXZl
IG9yaWdpbmF0ZWQgdGhyb3VnaAogICBhIFBTVE4gR2F0ZXdheSB3aXRob3V0IGFueSBhYmlsaXR5
IHRvIHBhc3Mgb24gaW4tc2lnbmFsaW5nCiAgIGluZGljYXRpb25zIG9mIHJlY29yZGluZywgdXNl
cnMgY2FuIGJlIG5vdGlmaWVkIG9mIHJlY29yZGluZyBpbiB0aGUKICAgbWVkaWEgaXRzZWxmIHRo
cm91Z2ggdm9pY2UgYW5ub3VuY2VtZW50cywgYSB2aXN1YWwgaW5kaWNhdG9yIG9uIHRoZQogICBl
bmRwb2ludCwgb3Igb3RoZXIgbWVhbnMuCgoKClJlaG9yLCBldCBhbC4gICAgICAgICAgRXhwaXJl
cyBTZXB0ZW1iZXIgMTUsIDIwMTEgICAgICAgICAgICAgIFtQYWdlIDEzXQoMCkludGVybmV0LURy
YWZ0ICAgICAgICAgICBSZXF1aXJlbWVudHMgZm9yIFNJUFJFQyAgICAgICAgICAgICAgTWFyY2gg
MjAxMQoKCiAgIFdpdGggcmVnYXJkcyB0byBzZWN1cml0eSBpbXBsaWNhdGlvbnMgb2YgdGhlIHBy
b3RvY29sKHMpLCBjbGVhcmx5CiAgIHRoZXJlIGlzIGEgbmVlZCBmb3IgYXV0aGVudGljYXRpb24s
IGF1dGhvcml6YXRpb24sIGVhdmVzZHJvcHBpbmcKICAgcHJvdGVjdGlvbiwgYW5kIG5vbi1yZXB1
ZGlhdGlvbiBmb3IgdGhlIHNvbHV0aW9uLiAgVGhlIFNSQyBuZWVkcyB0bwogICBrbm93IHRoZSBT
UlMgaXQgaXMgY29tbXVuaWNhdGluZyB3aXRoIGlzIGxlZ2l0aW1hdGUsIGFuZCB2aWNlLXZlcnNh
LAogICBldmVuIGlmIHRoZXkgYXJlIGluIGRpZmZlcmVudCBkb21haW5zLiAgQm90aCB0aGUgc2ln
bmFsaW5nIGFuZCBtZWRpYQogICBmb3IgdGhlIFJlY29yZGluZyBTZXNzaW9uIG5lZWQgdGhlIGFi
aWxpdHkgdG8gYmUgYXV0aGVudGljYXRlZCBhbmQKICAgcHJvdGVjdGVkIGZyb20gZWF2ZXNkcm9w
cGluZyBhbmQgbm9uLXJlcHVkaWF0aW9uLiAgUmVxdWlyZW1lbnRzIGFyZQogICBkZXRhaWxlZCBp
biB0aGUgcmVxdWlyZW1lbnRzIHNlY3Rpb24uCgoKOC4gIElBTkEgQ29uc2lkZXJhdGlvbnMKCiAg
IFRoaXMgZG9jdW1lbnQgaGFzIG5vIElBTkEgYWN0aW9ucy4KCgo5LiAgQWNrbm93bGVkZ2VtZW50
cwoKICAgVGhhbmtzIHRvIERhbiBXaW5nLCBBbGFuIEpvaG5zb24sIFZpamF5IEd1cmJhbmksIEN1
bGxlbiBKZW5uaW5ncywKICAgSGFkcmllbCBLYXBsYW4sIEhlbnJ5IEx1bSwgRGF2ZSBTbWl0aCwg
TWFydGluIFBhbG1lciwgQWxpc3NhIENvb3BlciwKICAgRGVlcGFuc2h1IEdhdXRhbSwgUGF1bCBL
eXppdmF0LCBQYXJ0aGFzYXJhdGhpIFIsIGFuZCBSYW0gTW9oYW4gUiBmb3IKICAgdGhlaXIgc2ln
bmlmaWNhbnQgY29udHJpYnV0aW9ucyBhbmQgYXNzaXN0YW5jZSB3aXRoIHRoaXMgZG9jdW1lbnQg
YW5kCiAgIFdvcmtpbmcgR3JvdXAsIGFuZCB0byBhbGwgdGhlIG1lbWJlcnMgb2YgdGhlIERJU1BB
VENIIFdHIGFuZCBTSVBSRUMKICAgV0cgbWFpbGluZyBsaXN0cyBmb3IgcHJvdmlkaW5nIHZhbHVh
YmxlIGlucHV0IHRvIHRoaXMgd29yay4KCgoxMC4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzCgogICBb
UkZDMjExOV0gIEJyYWRuZXIsIFMuLCAiS2V5IHdvcmRzIGZvciB1c2UgaW4gUkZDcyB0byBJbmRp
Y2F0ZQogICAgICAgICAgICAgIFJlcXVpcmVtZW50IExldmVscyIsIEJDUCAxNCwgUkZDIDIxMTks
IE1hcmNoIDE5OTcuCgogICBbUkZDMzI2MV0gIFJvc2VuYmVyZywgSi4sIFNjaHVsenJpbm5lLCBI
LiwgQ2FtYXJpbGxvLCBHLiwgSm9obnN0b24sCiAgICAgICAgICAgICAgQS4sIFBldGVyc29uLCBK
LiwgU3BhcmtzLCBSLiwgSGFuZGxleSwgTS4sIGFuZCBFLgogICAgICAgICAgICAgIFNjaG9vbGVy
LCAiU0lQOiBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9jb2wiLCBSRkMgMzI2MSwKICAgICAgICAg
ICAgICBKdW5lIDIwMDIuCgogICBbUkZDNDEwM10gIEhlbGxzdHJvbSwgRy4gYW5kIFAuIEpvbmVz
LCAiUlRQIFBheWxvYWQgZm9yIFRleHQKICAgICAgICAgICAgICBDb252ZXJzYXRpb24iLCBSRkMg
NDEwMywgSnVuZSAyMDA1LgoKICAgW1JGQzQ3MzNdICBTY2h1bHpyaW5uZSwgSC4gYW5kIFQuIFRh
eWxvciwgIlJUUCBQYXlsb2FkIGZvciBEVE1GCiAgICAgICAgICAgICAgRGlnaXRzLCBUZWxlcGhv
bnkgVG9uZXMsIGFuZCBUZWxlcGhvbnkgU2lnbmFscyIsIFJGQyA0NzMzLAogICAgICAgICAgICAg
IERlY2VtYmVyIDIwMDYuCgoKCgoKCgoKCgpSZWhvciwgZXQgYWwuICAgICAgICAgIEV4cGlyZXMg
U2VwdGVtYmVyIDE1LCAyMDExICAgICAgICAgICAgICBbUGFnZSAxNF0KDApJbnRlcm5ldC1EcmFm
dCAgICAgICAgICAgUmVxdWlyZW1lbnRzIGZvciBTSVBSRUMgICAgICAgICAgICAgIE1hcmNoIDIw
MTEKCgpBdXRob3JzJyBBZGRyZXNzZXMKCiAgIEtlbiBSZWhvciAoZWRpdG9yKQogICBDaXNjbyBT
eXN0ZW1zCiAgIDE3MCBXZXN0IFRhc21hbiBEci4KICAgTWFpbCBTdG9wIFNKQzMwLzIvCiAgIFNh
biBKb3NlLCBDQSAgOTUxMzQKICAgVVNBCgogICBFbWFpbDoga3JlaG9yQGNpc2NvLmNvbQoKCiAg
IExlb24gUG9ydG1hbiAoZWRpdG9yKQogICBOSUNFIFN5c3RlbXMKICAgOCBIYXBuaW5hCiAgIFJh
J2FuYW5hICA0MzAxNwogICBJc3JhZWwKCiAgIEVtYWlsOiBsZW9uLnBvcnRtYW5AbmljZS5jb20K
CgogICBBbmRyZXcgSHV0dG9uCiAgIFNpZW1lbnMgRW50ZXJwcmlzZSBDb21tdW5pY2F0aW9ucwoK
ICAgRW1haWw6IGFuZHJldy5odXR0b25Ac2llbWVucy1lbnRlcnByaXNlLmNvbQogICBVUkk6ICAg
aHR0cDovL3d3dy5zaWVtZW5zLWVudGVycHJpc2UuY29tCgoKICAgUmFqbmlzaCBKYWluCiAgIElQ
QyBTeXN0ZW1zCiAgIDc3NyBDb21tZXJjZSBEcml2ZQogICBGYWlyZmllbGQsIENUICAwNjgyNQog
ICBVU0EKCiAgIEVtYWlsOiByYWpuaXNoLmphaW5AaXBjLmNvbQoKCgoKCgoKCgoKCgoKCgoKUmVo
b3IsIGV0IGFsLiAgICAgICAgICBFeHBpcmVzIFNlcHRlbWJlciAxNSwgMjAxMSAgICAgICAgICAg
ICAgW1BhZ2UgMTVdCgwKCg==

------_=_NextPart_001_01CBE261.ED68E66B
Content-Type: text/xml;
	name="draft-ietf-siprec-req-08.xml"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-siprec-req-08.xml
Content-Disposition: attachment;
	filename="draft-ietf-siprec-req-08.xml"

PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCg0KPCFET0NUWVBFIHJmYyBT
WVNURU0gInJmYzI2MjkuZHRkIiBbDQogICA8IUVOVElUWSByZmMyMTE5IFBVQkxJQyAnJyAnaHR0
cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNlLlJGQy4yMTE5
LnhtbCc+DQogICA8IUVOVElUWSByZmMzMjYxIFNZU1RFTSAiaHR0cDovL3htbC5yZXNvdXJjZS5v
cmcvcHVibGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNlLlJGQy4zMjYxLnhtbCI+DQogICA8IUVOVElU
WSByZmM0MTAzIFNZU1RFTSAiaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4
bWwvcmVmZXJlbmNlLlJGQy40MTAzLnhtbCI+DQogICA8IUVOVElUWSByZmM0NzMzIFNZU1RFTSAi
aHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNlLlJGQy40
NzMzLnhtbCI+DQpdPg0KDQo8cmZjIAljYXRlZ29yeT0iaW5mbyIgDQoJaXByPSJ0cnVzdDIwMDkw
MiIgDQogICAgIAlkb2NOYW1lPSJkcmFmdC1pZXRmLXNpcHJlYy1yZXEtMDgiPg0KDQo8P3htbC1z
dHlsZXNoZWV0IHR5cGU9J3RleHQveHNsJyBocmVmPSdyZmMyNjI5LnhzbHQnID8+DQoNCjw/cmZj
IHRvYz0ieWVzIiA/Pg0KPD9yZmMgc3ltcmVmcz0ieWVzIiA/Pg0KPD9yZmMgc29ydHJlZnM9Inll
cyI/Pg0KPD9yZmMgaXBybm90aWZpZWQ9Im5vIiA/Pg0KPD9yZmMgY29tcGFjdD0ieWVzIiA/Pg0K
PD9yZmMgc3ViY29tcGFjdD0ibm8iID8+DQo8P3JmYyBzdHJpY3Q9Im5vIiA/Pg0KDQogIDxmcm9u
dD4NCiAgICA8dGl0bGUgYWJicmV2PSJSZXF1aXJlbWVudHMgZm9yIFNJUFJFQyI+UmVxdWlyZW1l
bnRzIGZvciBTSVAtYmFzZWQgTWVkaWEgUmVjb3JkaW5nIChTSVBSRUMpPC90aXRsZT4NCiAgICA8
YXV0aG9yIGZ1bGxuYW1lPSJLZW4gUmVob3IiIGluaXRpYWxzPSJLLlIiIHJvbGU9ImVkaXRvciIg
c3VybmFtZT0iUmVob3IiPg0KICAgICAgPG9yZ2FuaXphdGlvbj5DaXNjbyBTeXN0ZW1zPC9vcmdh
bml6YXRpb24+DQogICAgICA8YWRkcmVzcz4NCiAgICAgICAgPHBvc3RhbD4NCiAgICAgICAgICA8
c3RyZWV0PjE3MCBXZXN0IFRhc21hbiBEci48L3N0cmVldD4NCiAgICAgICAgICA8c3RyZWV0Pk1h
aWwgU3RvcCBTSkMzMC8yLzwvc3RyZWV0Pg0KICAgICAgICAgIDxjaXR5PlNhbiBKb3NlPC9jaXR5
Pg0KICAgICAgICAgIDxyZWdpb24+Q0E8L3JlZ2lvbj4NCiAgICAgICAgICA8Y29kZT45NTEzNDwv
Y29kZT4NCiAgICAgICAgICA8Y291bnRyeT5VU0E8L2NvdW50cnk+DQogICAgICAgIDwvcG9zdGFs
Pg0KICAgICAgICA8ZW1haWw+a3JlaG9yQGNpc2NvLmNvbTwvZW1haWw+DQogICAgICA8L2FkZHJl
c3M+DQogICAgPC9hdXRob3I+DQoNCiAgICA8YXV0aG9yIGZ1bGxuYW1lPSJMZW9uIFBvcnRtYW4i
IGluaXRpYWxzPSJMLlAiIHJvbGU9ImVkaXRvciIgc3VybmFtZT0iUG9ydG1hbiI+DQogICAgICA8
b3JnYW5pemF0aW9uPk5JQ0UgU3lzdGVtczwvb3JnYW5pemF0aW9uPg0KICAgICAgPGFkZHJlc3M+
DQogICAgICAgIDxwb3N0YWw+DQogICAgICAgICAgPHN0cmVldD44IEhhcG5pbmE8L3N0cmVldD4N
CiAgICAgICAgICA8Y2l0eT5SYSdhbmFuYTwvY2l0eT4NCiAgICAgICAgICA8Y29kZT40MzAxNzwv
Y29kZT4NCiAgICAgICAgICA8Y291bnRyeT5Jc3JhZWw8L2NvdW50cnk+DQogICAgICAgIDwvcG9z
dGFsPg0KICAgICAgICA8ZW1haWw+bGVvbi5wb3J0bWFuQG5pY2UuY29tPC9lbWFpbD4NCiAgICAg
IDwvYWRkcmVzcz4NCiAgICA8L2F1dGhvcj4NCiAgICANCiAgICA8YXV0aG9yIGZ1bGxuYW1lPSJB
bmRyZXcgSHV0dG9uIiBpbml0aWFscz0iQS4iIHN1cm5hbWU9Ikh1dHRvbiI+DQogICAgCTxvcmdh
bml6YXRpb24+U2llbWVucyBFbnRlcnByaXNlIENvbW11bmljYXRpb25zPC9vcmdhbml6YXRpb24+
DQogICAgCTxhZGRyZXNzPg0KCQk8ZW1haWw+YW5kcmV3Lmh1dHRvbkBzaWVtZW5zLWVudGVycHJp
c2UuY29tPC9lbWFpbD4NCiAgICAJCTx1cmk+aHR0cDovL3d3dy5zaWVtZW5zLWVudGVycHJpc2Uu
Y29tPC91cmk+DQogICAJPC9hZGRyZXNzPg0KICAgIDwvYXV0aG9yPiANCg0KICAgIDxhdXRob3Ig
ZnVsbG5hbWU9IlJham5pc2ggSmFpbiIgaW5pdGlhbHM9IlIuSiIgc3VybmFtZT0iSmFpbiI+DQog
ICAgICA8b3JnYW5pemF0aW9uPklQQyBTeXN0ZW1zPC9vcmdhbml6YXRpb24+DQogICAgICA8YWRk
cmVzcz4NCiAgICAgICAgPHBvc3RhbD4NCiAgICAgICAgICA8c3RyZWV0Pjc3NyBDb21tZXJjZSBE
cml2ZTwvc3RyZWV0Pg0KICAgICAgICAgIDxjaXR5PkZhaXJmaWVsZDwvY2l0eT4NCiAgICAgICAg
ICA8cmVnaW9uPkNUPC9yZWdpb24+DQogICAgICAgICAgPGNvZGU+MDY4MjU8L2NvZGU+DQogICAg
ICAgICAgPGNvdW50cnk+VVNBPC9jb3VudHJ5Pg0KICAgICAgICA8L3Bvc3RhbD4NCiAgICAgICAg
PGVtYWlsPnJham5pc2guamFpbkBpcGMuY29tPC9lbWFpbD4NCiAgICAgIDwvYWRkcmVzcz4NCiAg
ICA8L2F1dGhvcj4NCiAgICANCiAgICANCiAgICA8ZGF0ZSBtb250aD0iTWFyY2giIGRheT0iMTQi
IHllYXI9IjIwMTEiLz4NCiAgICANCiAgICA8d29ya2dyb3VwPkRJU1BBVENIPC93b3JrZ3JvdXA+
DQogICAgPGtleXdvcmQ+SW50ZXJuZXQtRHJhZnQ8L2tleXdvcmQ+DQogICAgDQogICAgPGFic3Ry
YWN0Pg0KCTx0PlNlc3Npb24gcmVjb3JkaW5nIGlzIGEgY3JpdGljYWwgcmVxdWlyZW1lbnQgaW4g
bWFueSBidXNpbmVzcw0KICAgCWNvbW11bmljYXRpb25zIGVudmlyb25tZW50cyBzdWNoIGFzIGNh
bGwgY2VudGVycyBhbmQgZmluYW5jaWFsDQogICAJdHJhZGluZyBmbG9vcnMuICBJbiBzb21lIG9m
IHRoZXNlIGVudmlyb25tZW50cywgYWxsIGNhbGxzIG11c3QgYmUNCglyZWNvcmRlZCBmb3IgcmVn
dWxhdG9yeSBhbmQgY29tcGxpYW5jZSByZWFzb25zLiAgSW4gb3RoZXJzLCBjYWxscyBtYXkNCiAg
IAliZSByZWNvcmRlZCBmb3IgcXVhbGl0eSBjb250cm9sIG9yIGJ1c2luZXNzIGFuYWx5dGljcy48
L3Q+DQoJDQoJPHQ+UmVjb3JkaW5nIGlzIHR5cGljYWxseSBwZXJmb3JtZWQgYnkgc2VuZGluZyBh
IGNvcHkgb2YgdGhlIHNlc3Npb24gbWVkaWEgDQogICAJdG8gdGhlIHJlY29yZGluZyBkZXZpY2Vz
LiAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgcmVxdWlyZW1lbnRzIGZvciANCiAgIAlleHRlbnNp
b25zIHRvIFNJUCB0aGF0IHdpbGwgbWFuYWdlIGRlbGl2ZXJ5IG9mIFJUUCBtZWRpYSB0byBhIHJl
Y29yZGluZyBkZXZpY2UuICANCiAgIAlUaGlzIGlzIGJlaW5nIHJlZmVycmVkIHRvIGFzIFNJUC1i
YXNlZCBNZWRpYSBSZWNvcmRpbmcuPC90Pg0KICAgIDwvYWJzdHJhY3Q+DQogIDwvZnJvbnQ+DQoN
CiAgPG1pZGRsZT4NCiAgICA8c2VjdGlvbiB0aXRsZT0iUmVxdWlyZW1lbnRzIG5vdGF0aW9uIj4N
CiAgICAgIAk8dD5UaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwg
IlNIQUxMIiwgIlNIQUxMIE5PVCIsDQogICAgICAJIlNIT1VMRCIsICJTSE9VTEQgTk9UIiwgIlJF
Q09NTUVOREVEIiwgIk1BWSIsIGFuZCAiT1BUSU9OQUwiIGluIHRoaXMNCiAgICAgIAlkb2N1bWVu
dCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFtSRkMyMTE5XSBhbmQgaW5k
aWNhdGUNCglyZXF1aXJlbWVudCBsZXZlbHMgZm9yIGNvbXBsaWFudCBtZWNoYW5pc21zLjwvdD4N
CiAgICA8L3NlY3Rpb24+DQoNCiAgICA8c2VjdGlvbiB0aXRsZT0iSW50cm9kdWN0aW9uIj4NCiAg
ICAJPHQ+U2Vzc2lvbiByZWNvcmRpbmcgaXMgYSBjcml0aWNhbCBvcGVyYXRpb25hbCByZXF1aXJl
bWVudCBpbiBtYW55DQogICAgCWJ1c2luZXNzZXMsIGVzcGVjaWFsbHkgd2hlcmUgdm9pY2UgaXMg
dXNlZCBhcyBhIG1lZGl1bSBmb3IgY29tbWVyY2UNCiAgICAJYW5kIGN1c3RvbWVyIHN1cHBvcnQu
ICBBIHByaW1lIGV4YW1wbGUgd2hlcmUgdm9pY2UgaXMgdXNlZCBmb3IgdHJhZGUNCiAgICAJaXMg
dGhlIGZpbmFuY2lhbCBpbmR1c3RyeS4gIFRoZSBjYWxsIHJlY29yZGluZyByZXF1aXJlbWVudHMg
aW4gdGhpcw0KICAgIAlpbmR1c3RyeSBhcmUgcXVpdGUgc3RyaW5nZW50LiAgVGhlIHJlY29yZGVk
IGNhbGxzIGFyZSB1c2VkIGZvcg0KICAgIAlkaXNwdXRlIHJlc29sdXRpb24gYW5kIGNvbXBsaWFu
Y2UuICBPdGhlciBidXNpbmVzc2VzIHN1Y2ggYXMgY3VzdG9tZXINCiAgICAJc3VwcG9ydCBjYWxs
IGNlbnRlcnMgdHlwaWNhbGx5IGVtcGxveSBjYWxsIHJlY29yZGluZyBmb3IgcXVhbGl0eQ0KICAg
IAljb250cm9sIG9yIGJ1c2luZXNzIGFuYWx5dGljcywgd2l0aCBkaWZmZXJlbnQgcmVxdWlyZW1l
bnRzLjwvdD4NCiAgICANCiAgICAJPHQ+RGVwZW5kaW5nIG9uIHRoZSBjb3VudHJ5IGFuZCBpdHMg
cmVndWxhdG9yeSByZXF1aXJlbWVudHMsIGZpbmFuY2lhbA0KICAgIAl0cmFkaW5nIGZsb29ycyB0
eXBpY2FsbHkgbXVzdCByZWNvcmQgYWxsIGNhbGxzLiAgSW4gY29udHJhc3QsIGNhbGwgY2VudGVy
cyB0eXBpY2FsbHkgb25seQ0KICAgIAlyZWNvcmQgYSBzdWJzZXQgb2YgdGhlIGNhbGxzLCBhbmQg
Y2FsbHMgbXVzdCBub3QgZmFpbCByZWdhcmRsZXNzIG9mDQogICAgCXRoZSBhdmFpbGFiaWxpdHkg
b2YgdGhlIHJlY29yZGluZyBkZXZpY2UuPC90Pg0KICAgIAkNCiAgICAJPHQ+UmVzcGVjdGluZyB0
aGUgcHJpdmFjeSByaWdodHMgYW5kIHdpc2hlcyBvZiB1c2VycyBlbmdhZ2VkIGluIGEgY2FsbA0K
ICAgIAlpcyBvZiBwYXJhbW91bnQgaW1wb3J0YW5jZS4gSW4gbWFueSBqdXJpc2RpY3Rpb25zIHBh
cnRpY2lwYW50cyBoYXZlIGEgcmlnaHQgdG8gDQogICAgICAgIGtub3cgdGhhdCB0aGUgc2Vzc2lv
biBpcyBiZWluZyByZWNvcmRlZCBvciBtaWdodCBiZSByZWNvcmRlZCwgYW5kIGhhdmUgYSANCiAg
ICAgICAgcmlnaHQgdG8gb3B0IG91dCwgZWl0aGVyIGJ5IHRlcm1pbmF0aW5nIHRoZSBjYWxsIG9y
IGJ5IGRlbWFuZGluZyB0aGF0IHRoZSANCiAgICAgICAgY2FsbCBub3QgYmUgcmVjb3JkZWQuIFRo
ZXJlZm9yZSB0aGlzIGRvY3VtZW50IGNvbnRhaW5zIHJlcXVpcmVtZW50cyBmb3IgYmVpbmcgDQog
ICAgICAgYWJsZSB0byBub3RpZnkgdXNlcnMgdGhhdCBhIGNhbGwgaXMgYmVpbmcgcmVjb3JkZWQg
YW5kIGZvciB1c2VycyB0byBiZSBhYmxlIA0KICAgICAgIHRvIHJlcXVlc3QgdGhhdCBhIGNhbGwg
bm90IGJlIHJlY29yZGVkLg0KICAgICAgIA0KICAgICAgIFVzZSBjYXNlcyB3aGVyZSB1c2VycyBw
YXJ0aWNpcGF0aW5nIGluIGEgY2FsbCBhcmUgbm90IGluZm9ybWVkIHRoYXQgdGhlIA0KICAgICAg
IGNhbGwgaXMgb3IgbWlnaHQgYmUgcmVjb3JkZWQgYXJlIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRo
aXMgZG9jdW1lbnQuIA0KICAgICAgIEluIHBhcnRpY3VsYXIsIGxhd2Z1bCBpbnRlcmNlcHQgaXMg
b3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudC4NCiAgICAJPC90Pg0KICAgIAkNCgk8
dD5GdXJ0aGVybW9yZSwgdGhlIHNjYWxlIGFuZCBjb3N0IGJ1cmRlbnMgdmFyeSB3aWRlbHksIGlu
IGFsbCBtYXJrZXRzLA0KICAgCXdoZXJlIHRoZSBkaWZmZXJlbnQgbmVlZHMgZm9yIHNvbHV0aW9u
IGNhcGFiaWxpdGllcyBzdWNoIGFzIG1lZGlhDQogICAJaW5qZWN0aW9uLCB0cmFuc2NvZGluZywg
YW5kIHNlY3VyaXR5LXJlbGF0ZWQgbmVlZHMgZG8gbm90IGNvbmZvcm0NCiAgIAl3ZWxsIHRvIGEg
b25lLXNpemUtZml0cy1hbGwgbW9kZWwuICBJZiBhIHN0YW5kYXJkaXplZCBzb2x1dGlvbg0KICAg
CXN1cHBvcnRzIGFsbCBvZiB0aGUgcmVxdWlyZW1lbnRzIGZyb20gZXZlcnkgcmVjb3JkaW5nIG1h
cmtldCwgYnV0DQogICAJZG9pbmcgc28gd291bGQgYmUgZXhwZW5zaXZlIGZvciBtYXJrZXRzIHdp
dGggbGVzc2VyIG5lZWRzLCB0aGVuDQogICAJcHJvcHJpZXRhcnkgc29sdXRpb25zIGZvciB0aG9z
ZSBtYXJrZXRzIHdpbGwgY29udGludWUgdG8gcHJvcGFnYXRlLg0KICAgCUNhcmUgbXVzdCBiZSB0
YWtlbiwgdGhlcmVmb3JlLCB0byBtYWtlIGEgc3RhbmRhcmRzLWJhc2VkIHNvbHV0aW9uDQogICAJ
c3VwcG9ydCBvcHRpb25hbGl0eSBhbmQgZmxleGliaWxpdHkuPC90Pg0KICAgCQ0KICAgCTx0PlRo
aXMgZG9jdW1lbnQgc3BlY2lmaWVzIHJlcXVpcmVtZW50cyBmb3IgdXNpbmcgU0lQIDx4cmVmIHRh
cmdldD0iUkZDMzI2MSIvPiBiZXR3ZWVuIGEgDQogICAJU2Vzc2lvbiBSZWNvcmRpbmcgQ2xpZW50
IGFuZCBhIFNlc3Npb24gUmVjb3JkaW5nIFNlcnZlciB0byBjb250cm9sIHRoZSANCiAgIAlyZWNv
cmRpbmcgb2YgbWVkaWEgdGhhdCBoYXMgYmVlbiB0cmFuc21pdHRlZCBpbiB0aGUgY29udGV4dCBv
ZiBhIENvbW11bmljYXRpb24gU2Vzc2lvbi4NCiAgIAkNCiAgCUEgQ29tbXVuaWNhdGlvbiBTZXNz
aW9uIGlzIHRoZSAiY2FsbCIgYmV0d2VlbiBwYXJ0aWNpcGFudHMuIA0KICAJVGhlIFNlc3Npb24g
UmVjb3JkaW5nIENsaWVudCBpcyB0aGUgc291cmNlIG9mIHRoZSByZWNvcmRlZCBtZWRpYS4gVGhl
IFNlc3Npb24gUmVjb3JkaW5nIFNlcnZlciBpcyB0aGUgc2luayBvZg0KICAgCXJlY29yZGVkIG1l
ZGlhLiBJdCBzaG91bGQgYmUgbm90ZWQgdGhhdCB0aGUgcmVxdWlyZW1lbnRzIGZvciB0aGUgcHJv
dG9jb2wgYmV0d2VlbiBhDQogICAJU2Vzc2lvbiBSZWNvcmRpbmcgU2VydmVyIGFuZCBTZXNzaW9u
IFJlY29yZGluZyBDbGllbnQgaGF2ZSB2ZXJ5IHNpbWlsYXIgcmVxdWlyZW1lbnRzDQogICAJKHN1
Y2ggYXMgY29kZWMgYW5kIHRyYW5zcG9ydCBuZWdvdGlhdGlvbiwgZW5jcnlwdGlvbiBrZXkgaW50
ZXJjaGFuZ2UsDQogICAJZmlyZXdhbGwgdHJhdmVyc2FsKSBhcyBjb21wYXJlZCB0byByZWd1bGFy
IFNJUCBtZWRpYSBzZXNzaW9ucy4gIFRoZQ0KICAgCWNob2ljZSBvZiBTSVAgZm9yIHNlc3Npb24g
cmVjb3JkaW5nIHByb3ZpZGVzIHJldXNlIG9mIGFuIGV4aXN0aW5nDQogICAJcHJvdG9jb2wuICA8
L3Q+DQogICAJDQogICAJPHQ+VGhlIHJlY29yZGVkIHNlc3Npb25zIGNhbiBiZSBhbnkgUlRQIG1l
ZGlhIHNlc3Npb25zIA0KICAgCWluY2x1ZGluZyB2b2ljZSwgRFRNRiAoYXMgZGVmaW5lZCBieSBb
UkZDNDczM10pLCB2aWRlbywgYW5kIHRleHQgKGFzIGRlZmluZWQgYnkgW1JGQzQxMDNdKS48L3Q+
DQogICAJDQogICAJPHQ+QW4gYXJjaGl2ZWQgc2Vzc2lvbiByZWNvcmRpbmcgaXMgdHlwaWNhbGx5
IGNvbXByaXNlZCBvZiB0aGUgQ29tbXVuaWNhdGlvbiBTZXNzaW9uIG1lZGlhIGNvbnRlbnQgYW5k
IA0KICAgCXRoZSBDb21tdW5pY2F0aW9uIFNlc3Npb24gTWV0YWRhdGEuICBUaGUgQ29tbXVuaWNh
dGlvbiBTZXNzaW9uIE1ldGFkYXRhIGFsbG93cyByZWNvcmRpbmcgYXJjaGl2ZXMgdG8gYmUgc2Vh
cmNoZWQgYW5kDQogICAJZmlsdGVyZWQgYXQgYSBsYXRlciB0aW1lIGFuZCBhbGxvd3MgYSBzZXNz
aW9uIHRvIGJlIHBsYXllZCBiYWNrIGluIGEgbWVhbmluZ2Z1bCB3YXksIA0KICAgCWUuZy4sIHdp
dGggY29ycmVjdCBzeW5jaHJvbml6YXRpb24gYmV0d2VlbiB0aGUgbWVkaWEuIA0KICAgCQ0KICAg
CVRoZSBDb21tdW5pY2F0aW9uIFNlc3Npb24gTWV0YWRhdGEgbmVlZHMgdG8gYmUgY29udmV5ZWQg
ZnJvbSB0aGUgU2Vzc2lvbiBSZWNvcmRpbmcgQ2xpZW50IA0KICAgCXRvIHRoZSBTZXNzaW9uIFJl
Y29yZGluZyBTZXJ2ZXIuPC90Pg0KICAgCQ0KICAgCTx0PlRoaXMgZG9jdW1lbnQgb25seSBjb25z
aWRlcnMgYWN0aXZlIHJlY29yZGluZywgd2hlcmUgdGhlIFNlc3Npb24gUmVjb3JkaW5nDQogICAJ
Q2xpZW50IHB1cnBvc2VmdWxseSBzdHJlYW1zIG1lZGlhIHRvIGEgU2Vzc2lvbiBSZWNvcmRpbmcg
U2VydmVyLiAgUGFzc2l2ZQ0KICAgCXJlY29yZGluZywgd2hlcmUgYSByZWNvcmRpbmcgZGV2aWNl
IGRldGVjdHMgbWVkaWEgZGlyZWN0bHkgZnJvbSB0aGUNCgluZXR3b3JrLCBpcyBvdXRzaWRlIHRo
ZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50LjwvdD4NCiAgICA8L3NlY3Rpb24+DQoNCiAgICA8c2Vj
dGlvbiB0aXRsZT0iRGVmaW5pdGlvbnMiPg0KCTx0PlNlc3Npb24gUmVjb3JkaW5nIFNlcnZlciAo
U1JTKTogQSBTZXNzaW9uIFJlY29yZGluZyBTZXJ2ZXIgKFNSUykgaXMgYSBTSVAgVXNlciBBZ2Vu
dCAoVUEpIHRoYXQgaXMgYSANCglzcGVjaWFsaXplZCBtZWRpYSBzZXJ2ZXIgb3IgY29sbGVjdG9y
IHRoYXQgYWN0cyBhcyB0aGUgc2luayBvZiB0aGUgcmVjb3JkZWQgbWVkaWEuICANCglBbiBTUlMg
aXMgdHlwaWNhbGx5IGltcGxlbWVudGVkIGFzIGEgbXVsdGktcG9ydCBkZXZpY2UgdGhhdCBpcyBj
YXBhYmxlDQoJb2YgcmVjZWl2aW5nIG1lZGlhIGZyb20gbXVsdGlwbGUgc291cmNlcyBzaW11bHRh
bmVvdXNseS4gIA0KCUFuIFNSUyBpcyB0aGUgc2luayBvZiB0aGUgcmVjb3JkZWQgc2Vzc2lvbiBt
ZXRhZGF0YS4gIA0KCTwvdD4NCgkNCgk8dD5TZXNzaW9uIFJlY29yZGluZyBDbGllbnQgKFNSQyk6
IEEgU2Vzc2lvbiBSZWNvcmRpbmcgQ2xpZW50IChTUkMpIGlzIGEgU0lQIFVzZXIgQWdlbnQNCgko
VUEpIHRoYXQgYWN0cyBhcyB0aGUgc291cmNlIG9mIHRoZSByZWNvcmRlZCBtZWRpYSwgc2VuZGlu
ZyBpdCB0byB0aGUgU1JTLiAgQW4gU1JDIGlzIGEgbG9naWNhbA0KCWZ1bmN0aW9uLiAgSXRzIGNh
cGFiaWxpdGllcyBtYXkgYmUgaW1wbGVtZW50ZWQgYWNyb3NzIG9uZSBvciBtb3JlDQoJcGh5c2lj
YWwgZGV2aWNlcy4gIEluIHByYWN0aWNlLCBhbiBTUkMgY291bGQgYmUgYSBwZXJzb25hbCBkZXZp
Y2UNCgkoc3VjaCBhcyBhIFNJUCBwaG9uZSksIGEgU0lQIE1lZGlhIEdhdGV3YXkgKE1HKSwgYSBT
ZXNzaW9uIEJvcmRlcg0KCUNvbnRyb2xsZXIgKFNCQykgb3IgYSBTSVAgTWVkaWEgU2VydmVyIChN
UykgaW50ZWdyYXRlZCB3aXRoIGFuDQoJQXBwbGljYXRpb24gU2VydmVyIChBUykuICBUaGlzIHNw
ZWNpZmljYXRpb24gZGVmaW5lcyB0aGUgdGVybSBTUkMgc3VjaA0KCXRoYXQgYWxsIHN1Y2ggU0lQ
IGVudGl0aWVzIGNhbiBiZSBnZW5lcmljYWxseSBhZGRyZXNzZWQgdW5kZXIgb25lDQoJZGVmaW5p
dGlvbi4gIFRoZSBTUkMgcHJvdmlkZXMgbWV0YWRhdGEgdG8gdGhlIFNSUy48L3Q+DQoJDQoJPHQ+
Q29tbXVuaWNhdGlvbiBTZXNzaW9uIChDUyk6IEEgc2Vzc2lvbiBjcmVhdGVkIGJldHdlZW4gdHdv
IG9yIG1vcmUgU0lQIFVzZXIgQWdlbnRzIChVQXMpIA0KCXRoYXQgaXMgdGhlIHN1YmplY3Qgb2Yg
cmVjb3JkaW5nLjwvdD4NCgkNCgk8dD5SZWNvcmRpbmcgU2Vzc2lvbiAoUlMpOiBUaGUgU0lQIHNl
c3Npb24gY3JlYXRlZCBiZXR3ZWVuIGFuIFNSQyBhbmQgU1JTIGZvciB0aGUNCiAgIAlwdXJwb3Nl
IG9mIHJlY29yZGluZyBhIENvbW11bmljYXRpb24gU2Vzc2lvbi48L3Q+DQoNCg0KCTx0PkZpZ3Vy
ZSAxIHBpY3RvcmlhbGx5IHJlcHJlc2VudHMgdGhlIHJlbGF0aW9uc2hpcCBiZXR3ZWVuIGEgUmVj
b3JkaW5nIFNlc3Npb24gYW5kIENvbW11bmljYXRpb24gU2Vzc2lvbi48L3Q+DQoJDQoJPGZpZ3Vy
ZSBhbmNob3I9InJlY29yZGluZ19zZXNzaW9uIj4NCgkgIAk8cHJlYW1ibGU+PC9wcmVhbWJsZT4N
CgkgIAk8YXJ0d29yaz48IVtDREFUQVsNCg0KICArLS0tLS0tLS0tLS0tLSsgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICstLS0tLS0tLS0tLSsNCiAgfCAgICAgICAgICAgICB8
ICAgICAgICBDb21tdW5pY2F0aW9uIFNlc3Npb24gICAgICAgICB8ICAgICAgICAgICB8DQogIHwg
ICAgIEEgICAgICAgfDwtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0+fCAgICAg
QiAgICAgfA0KICB8ICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIHwgICAgICAgICAgIHwNCiAgKy0tLS0tLS0tLS0tLS0rICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0rDQogIC4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLg0KICAuICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICBTZXNzaW9uICAgICAgICAgICAgICAgICAgICAgICAgICAg
IC4NCiAgLiAgICAgICAgICAgICAgICAgICAgICAgICAgICBSZWNvcmRpbmcgICAgICAgICAgICAg
ICAgICAgICAgICAgICAuDQogIC4gICAgICAgICAgICAgICAgICAgICAgICAgICAgIENsaWVudCAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgLg0KICAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4NCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICB8IFJlY29yZGluZw0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IFNlc3Np
b24NCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICB2DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgKy0tLS0t
LS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgU2Vzc2lvbiAgfA0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIHwgIFJlY29yZGluZyB8DQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgfCAgIFNlcnZlciAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAr
LS0tLS0tLS0tLS0tKw0KDQogIAkgIAldXT48L2FydHdvcms+DQoJICAJPHBvc3RhbWJsZT48L3Bv
c3RhbWJsZT4NCgk8L2ZpZ3VyZT4NCg0KDQoJPHQ+TWV0YWRhdGE6ICBJbmZvcm1hdGlvbiB0aGF0
IGRlc2NyaWJlcyByZWNvcmRlZCBtZWRpYSBhbmQgdGhlIENTIHRvIHdoaWNoIHRoZXkgcmVsYXRl
LjwvdD4NCgkNCgk8dD5QYXVzZSBhbmQgUmVzdW1lIGR1cmluZyBhIENvbW11bmljYXRpb24gU2Vz
c2lvbjoNCiAgIAlQYXVzZTogVGhlIGFjdGlvbiBvZiB0ZW1wb3JhcmlseSBkaXNjb250aW51aW5n
IHRoZSB0cmFuc21pc3Npb24gYW5kIGNvbGxlY3Rpb24gb2YgUlMgbWVkaWENCglSZXN1bWU6IFRo
ZSBhY3Rpb24gb2YgcmVjb21tZW5jaW5nIHRoZSB0cmFuc21pc3Npb24gYW5kIGNvbGxlY3Rpb24g
b2YgUlMgbWVkaWENCgk8L3Q+DQogICANCiAgICA8L3NlY3Rpb24+DQogICAgDQoNCiAgICA8c2Vj
dGlvbiB0aXRsZT0iVXNlIENhc2VzIj4NCgk8dD5Vc2UgQ2FzZSAxOiBGdWxsLXRpbWUgUmVjb3Jk
aW5nOiAgT25lIFJlY29yZGluZyBTZXNzaW9uIGZvciBlYWNoIENvbW11bmljYXRpb24gU2Vzc2lv
bi48L3Q+CSAgICAgIA0KCQ0KICAgICAgICA8ZmlndXJlIGFuY2hvcj0iZnVsbF90aW1lIj4NCgkg
ICAgCTxwcmVhbWJsZT5Gb3IgZXhhbXBsZSwgdGhlIGRpYWdyYW0gYmVsb3cgc2hvd3MgdGhlIGxp
ZmVjeWNsZSBvZiBDb21tdW5pY2F0aW9uIFNlc3Npb25zIChDUykgDQoJCWFuZCB0aGUgcmVsYXRp
b25zaGlwIHRvIHRoZSBSZWNvcmRpbmcgU2Vzc2lvbnMgKFJTKTwvcHJlYW1ibGU+DQogICAgICAJ
CTxhcnR3b3JrPjwhW0NEQVRBWw0KQ1MgIHwtLS0gQ1MgMSAtLS18ICAgICAgfC0tLSBDUyAyIC0t
LXwgICAgIHwtLS0gQ1MgMyAtLS18DQoNClJTICB8LS0tIFJTIDEgLS0tfCAgICAgIHwtLS0gUlMg
MiAtLS18ICAgICB8LS0tIFJTIDMgLS0tfA0KCSAgICAgIAldXT48L2FydHdvcms+DQoJICAgICAg
CTxwb3N0YW1ibGU+PC9wb3N0YW1ibGU+DQogICAgCTwvZmlndXJlPg0KICAgIAkNCiAgICAJPHQ+
UmVjb3JkIGV2ZXJ5IENTIGZvciBzcGVjaWZpYyBleHRlbnNpb24vcGVyc29uLjwvdD4NCiAgICAJ
DQogICAgCTx0PlRoZSBuZWVkIHRvIHJlY29yZCBhbGwgY2FsbHMgaXMgdHlwaWNhbGx5IGR1ZSB0
byBidXNpbmVzcyBwcm9jZXNzIHB1cnBvc2VzIA0KICAgIAkoc3VjaCBhcyB0cmFuc2FjdGlvbiBj
b25maXJtYXRpb24gb3IgZGlzcHV0ZSByZXNvbHV0aW9uKSANCiAgICAJb3IgdG8gZW5zdXJlIGNv
bXBsaWFuY2Ugd2l0aCBnb3Zlcm5tZW50YWwgcmVndWxhdGlvbnMuICANCiAgICAJQXBwbGljYXRp
b25zIGluY2x1ZGUgZW50ZXJwcmlzZSwgY29udGFjdCBjZW50ZXIsIGFuZCBmaW5hbmNpYWwgdHJh
ZGluZyBmbG9vcnMuPC90Pg0KICAgIAkNCiAgICAJPHQ+QWxzbyBjb21tb25seSBrbm93biBhcyBU
b3RhbCBSZWNvcmRpbmcuPC90Pg0KICAgIAkNCiAgICAJPHQ+VXNlIENhc2UgMjogU2VsZWN0aXZl
IFJlY29yZGluZzogU3RhcnQgYSBSZWNvcmRpbmcgU2Vzc2lvbiB3aGVuIGEgDQogICAgCUNvbW11
bmljYXRpb24gU2Vzc2lvbiB0byBiZSByZWNvcmRlZCBpcyBlc3RhYmxpc2hlZC48L3Q+DQogICAg
CQ0KICAgICAgICA8ZmlndXJlIGFuY2hvcj0ic2VsZWN0aXZlIj4NCgkgICAgCTxwcmVhbWJsZT5J
biB0aGlzIGV4YW1wbGUsIENvbW11bmljYXRpb24gU2Vzc2lvbnMgMSBhbmQgMyBhcmUgcmVjb3Jk
ZWQgYnV0IENTIDIgaXMgbm90LjwvcHJlYW1ibGU+DQogICAgICAJCTxhcnR3b3JrPjwhW0NEQVRB
Ww0KQ1MgIHwtLS0gQ1MgMSAtLS18ICAgICAgfC0tLSBDUyAyIC0tLXwgICAgIHwtLS0gQ1MgMyAt
LS18DQoNClJTICB8LS0tIFJTIDEtLS0tfCAgICAgICAgICAgICAgICAgICAgICAgICB8LS0tIFJT
IDIgLS0tfA0KCSAgICAgIAldXT48L2FydHdvcms+DQoJICAgICAgCTxwb3N0YW1ibGU+PC9wb3N0
YW1ibGU+DQogICAgCTwvZmlndXJlPg0KICAgIAkNCiAgICAJPHQ+VXNlIENhc2UgMzogIFN0YXJ0
L1N0b3AgYSBSZWNvcmRpbmcgU2Vzc2lvbiBkdXJpbmcgYSBDb21tdW5pY2F0aW9uIFNlc3Npb24u
PC90Pg0KICAgIAkNCiAgICAJPHQ+VGhlIFJlY29yZGluZyBTZXNzaW9uIHN0YXJ0cyBkdXJpbmcg
YSBDb21tdW5pY2F0aW9uIFNlc3Npb24sIGVpdGhlciBtYW51YWxseSB2aWEgYSB1c2VyLWNvbnRy
b2xsZWQgbWVjaGFuaXNtIA0KICAgIAkoZS5nLiBidXR0b24gb24gdXNlciZyc3F1bztzIHBob25l
KSBvciBhdXRvbWF0aWNhbGx5IHZpYSBhbiBhcHBsaWNhdGlvbiAoZS5nLiBhIENvbnRhY3QgQ2Vu
dGVyIGN1c3RvbWVyIHNlcnZpY2UgYXBwbGljYXRpb24pIA0KICAgIAlvciBidXNpbmVzcyBldmVu
dC4gDQogICAgCUEgUmVjb3JkaW5nIFNlc3Npb24gZWl0aGVyIGVuZHMgZHVyaW5nIHRoZSBDb21t
dW5pY2F0aW9uIFNlc3Npb24sIG9yIHdoZW4gdGhlIENvbW11bmljYXRpb24gU2Vzc2lvbiBlbmRz
LiANCiAgICAJT25lIG9yIG1vcmUgUmVjb3JkaW5nIFNlc3Npb25zIG1heSByZWNvcmQgZWFjaCBD
b21tdW5pY2F0aW9uIFNlc3Npb24uPC90Pg0KICAgIAkNCiAgICAJPGZpZ3VyZSBhbmNob3I9ImR5
bmFtaWMiPg0KCQk8cHJlYW1ibGU+PC9wcmVhbWJsZT4NCgkgICAgICAJPGFydHdvcms+PCFbQ0RB
VEFbDQpDUyAgfC0tLS0tLS0tLS0tLS0gQ29tbXVuaWNhdGlvbiBTZXNzaW9uIC0tLS0tLS0tLS0t
fA0KDQpSUyAgICAgICAgICAgfC0tLS0gUlMgMSAtLS0tfCAgfC0tLS0gUlMgMiAtLS0tLXwNCgkJ
XV0+PC9hcnR3b3JrPg0KCQk8cG9zdGFtYmxlPjwvcG9zdGFtYmxlPg0KICAgIAk8L2ZpZ3VyZT4N
CiAgICAJDQogICAJDQogICAJPHQ+VXNlIENhc2UgNDogUGVyc2lzdGVudCBSZWNvcmRpbmc6IEEg
c2luZ2xlIFJlY29yZGluZyBTZXNzaW9uIGNhcHR1cmVzIG9uZSBvciBtb3JlIENvbW11bmljYXRp
b24gU2Vzc2lvbnMuICAgCQ0KICAgCTwvdD4NCiAgIAkNCiAgIAk8ZmlndXJlIGFuY2hvcj0icGVy
c2lzdGVudCI+DQoJCTxwcmVhbWJsZT48L3ByZWFtYmxlPg0KCQk8YXJ0d29yaz48IVtDREFUQVsN
CgkgIHwtLS0gQ1MgMSAtLS18ICAgICAgfC0tLSBDUyAyIC0tLXwgICAgIHwtLS0gQ1MgMyAtLS18
DQoNClJTICB8LS0tLS0tLS0tLS0tLS0tLS0tLS0tLSBSZWNvcmRpbmcgU2Vzc2lvbiAtLS0tLS0t
LS0tLS0tLS0tLS0tLS18DQoJCV1dPjwvYXJ0d29yaz4NCgkJPHBvc3RhbWJsZT48L3Bvc3RhbWJs
ZT4NCiAgICAJPC9maWd1cmU+DQogICAJDQoJPHQ+QSBSZWNvcmRpbmcgU2Vzc2lvbiByZWNvcmRz
IGNvbnRpbnVvdXNseSB3aXRob3V0IGludGVycnVwdGlvbi4gUGVyaW9kcw0KCXdoZW4gdGhlcmUg
aXMgbm8gQ1MgaW4gcHJvZ3Jlc3MgbXVzdCBiZSByZXByb2R1Y2VkIHVwb24gcGxheWJhY2sgKGUu
Zy4gYnkNCglyZWNvcmRpbmcgc2lsZW5jZSBkdXJpbmcgc3VjaCBwZXJpb2RzIG9yIGJ5IG5vdCBy
ZWNvcmRpbmcgc3VjaCBwZXJpb2RzIGJ1dA0KCW1hcmtpbmcgdGhlbSBieSBtZWFucyBvZiBtZXRh
ZGF0YSBmb3IgdXRpbGl6YXRpb24gb24gcGxheWJhY2ssIGV0Yy4pLg0KDQoJDQoJQXBwbGljYXRp
b25zIGluY2x1ZGUgZmluYW5jaWFsIHRyYWRpbmcgZGVza3MgYW5kIGVtZXJnZW5jeSAoZmlyc3Qt
cmVzcG9uZGVyKSBzZXJ2aWNlDQoJYnVyZWF1cy4gVGhlIGxlbmd0aCBvZiBhIFBlcnNpc3RlbnQg
UmVjb3JkaW5nIFNlc3Npb24gaXMNCglpbmRlcGVuZGVudCBmcm9tIHRoZSBsZW5ndGggb2YgdGhl
IGFjdHVhbCBDb21tdW5pY2F0aW9uIFNlc3Npb25zLg0KCVBlcnNpc3RlbnQgUmVjb3JkaW5nIFNl
c3Npb25zIGF2b2lkIGlzc3VlcyBzdWNoIGFzIG1lZGlhIGNsaXBwaW5nDQoJdGhhdCBjYW4gb2Nj
dXIgZHVlIHRvIGRlbGF5cyBpbiBSZWNvcmRpbmcgU2Vzc2lvbiBlc3RhYmxpc2htZW50LjwvdD4N
CgkNCgk8dD5UaGUgY29ubmVjdGlvbiBhbmQgYXR0cmlidXRlcyBvZiBtZWRpYSBpbiB0aGUgUmVj
b3JkaW5nDQogICAJU2Vzc2lvbiBhcmUgbm90IGR5bmFtaWNhbGx5IHNpZ25hbGVkIGZvciBlYWNo
IENvbW11bmljYXRpb24gU2Vzc2lvbiBiZWZvcmUNCiAgIAlpdCBjYW4gYmUgcmVjb3JkZWQ7IGhv
d2V2ZXIsIGNvZGVjIHJlLW5lZ290aWF0aW9uIGlzIHBvc3NpYmxlLjwvdD4NCiAgIAkNCiAgIAk8
ZmlndXJlIGFuY2hvcj0ibWl4aW5nIj4NCgkJPHByZWFtYmxlPkluIHNvbWUgY2FzZXMsIG1vcmUg
dGhhbiBvbmUgY29uY3VycmVudCBDb21tdW5pY2F0aW9uIFNlc3Npb24gDQoJCShvbiBhIHNpbmds
ZSBlbmQtdXNlciBhcHBhcmF0dXMsIGUuZy4gdHJhZGluZyBmbG9vciB0dXJyZXQpIA0KCQlpcyBt
aXhlZCBpbnRvIG9uZSBSZWNvcmRpbmcgU2Vzc2lvbjo8L3ByZWFtYmxlPg0KCQk8YXJ0d29yaz48
IVtDREFUQVsNCiAgICAgICAgICAgICAgfC0tLS0tLS0tIENTIDEgLS0tLS0tLXwgIA0KCSAgICAg
ICAgIHwtLS0tLS0tLSBDUyAyIC0tLS0tLS18ICANCgkgICAgfC0tLS0tLS0tIENTIDMgLS0tLS0t
LXwgIA0KDQpSUyAgfC0tLS0tLS0tLS0tIFJlY29yZGluZyBTZXNzaW9uIC0tLS0tLS0tLS0tLS0t
fA0KCQldXT48L2FydHdvcms+DQoJCTxwb3N0YW1ibGU+PC9wb3N0YW1ibGU+DQogICAgCTwvZmln
dXJlPg0KDQogICAJPHQ+VXNlIENhc2UgNTogUmVhbC10aW1lIFJlY29yZGluZyBDb250cm9scy48
L3Q+DQogICAJDQogICAJPHQ+Rm9yIGFuIGFjdGl2ZSBSZWNvcmRpbmcgU2Vzc2lvbiwgcHJpdmFj
eSBvciBzZWN1cml0eSByZWFzb25zIG1heQ0KICAgCWRlbWFuZCBub3QgY2FwdHVyaW5nIGEgc3Bl
Y2lmaWMgcG9ydGlvbiBvZiBhIGNvbnZlcnNhdGlvbi4gIA0KICAgCQ0KICAgCUFuIGV4YW1wbGUg
aXMgZm9yIFBDSSAocGF5bWVudCBjYXJkIGluZHVzdHJ5KSBjb21wbGlhbmNlIHdoZXJlIGNyZWRp
dA0KCWNhcmQgaW5mbyBtdXN0IGJlIHByb3RlY3RlZC4gIE9uZSBzb2x1dGlvbiBpcyB0byBub3Qg
cmVjb3JkIGEgY2FsbGVyDQogICAJc3BlYWtpbmcgdGhlaXIgY3JlZGl0IGNhcmQgaW5mb3JtYXRp
b24uPC90Pg0KICAgCQ0KICAgCTx0PkFuIGV4YW1wbGUgb2YgYSByZWFsLXRpbWUgY29udHJvbHMg
aXMgUGF1c2UvUmVzdW1lLjwvdD4NCiAgIAkNCiAgIAk8dD5Vc2UgQ2FzZSA2OiBJVlIgLyBWb2lj
ZSBQb3J0YWwgUmVjb3JkaW5nLjwvdD4NCiAgIAkNCiAgIAk8dD4gICBTZWxmLXNlcnZpY2UgSW50
ZXJhY3RpdmUgVm9pY2UgUmVzcG9uc2UgYXBwbGljYXRpb25zDQogICAJbWF5IG5lZWQgdG8gYmUg
cmVjb3JkZWQgZm9yIGFwcGxpY2F0aW9uIHBlcmZvcm1hbmNlIHR1bmluZyBvciB0byBtZWV0DQog
ICAJY29tcGxpYW5jZSByZXF1aXJlbWVudHMuPC90Pg0KICAgCQ0KICAgCTx0Pk1ldGFkYXRhIGFi
b3V0IGFuIElWUiBzZXNzaW9uIHJlY29yZGluZyBtdXN0IGluY2x1ZGUgc2Vzc2lvbiBpbmZvcm1h
dGlvbiANCiAgIAlhbmQgbWF5IGluY2x1ZGUgYXBwbGljYXRpb24gY29udGV4dCBpbmZvcm1hdGlv
biAoZS5nLiBWb2ljZVhNTCBzZXNzaW9uIHZhcmlhYmxlcywgZGlhbG9nIG5hbWVzLCBldGMuKTwv
dD4NCiAgIAkNCiAgIAk8dD5Vc2UgQ2FzZSA3OiBFbnRlcnByaXNlIE1vYmlsaXR5IFJlY29yZGlu
Zy48L3Q+DQogICAJDQogICAJPHQ+TWFueSBhZ2VudHMgYW5kIGVudGVycHJpc2Ugd29ya2VycyB3
aG9zZSBjYWxscyBhcmUgdG8gYmUgcmVjb3JkZWQgYXJlIG5vdCBsb2NhdGVkIG9uIGNvbXBhbnkg
cHJlbWlzZXMuPC90Pg0KICAgCQ0KICAgCTx0PkV4YW1wbGVzOjwvdD4NCiAgIAkNCiAgIAk8dD5v
IEhvbWUtYmFzZWQgYWdlbnRzIG9yIGVudGVycHJpc2Ugd29ya2Vycy48L3Q+DQogICAJDQogICAJ
PHQ+byBNb2JpbGUgcGhvbmVzIG9mIGtub3dsZWRnZSB3b3JrZXJzIHdoZW4gdGhleSBjb25kdWN0
IHdvcmsgcmVsYXRlZA0KICAgCShhbmQgbGVnYWxseSByZXF1aXJlZCByZWNvcmRpbmcpIGNhbGxz
LiBlLmcuIGluc3VyYW5jZSBhZ2VudHMsDQogICAJYnJva2VycywgcGh5c2ljaWFucy48L3Q+DQog
ICAJDQogICAJPHQ+VXNlIENhc2UgODogR2VvZ3JhcGhpY2FsbHkgZGlzdHJpYnV0ZWQgb3IgY2Vu
dHJhbGl6ZWQgcmVjb3JkaW5nLjwvdD4NCiAgIAkNCiAJDQogICAgCTx0PkVudGVycHJpc2VzIHN1
Y2ggYXMgYmFua3MsIGluc3VyYW5jZSBhZ2VuY2llcywgYW5kIHJldGFpbCBzdG9yZXMgbWF5IGhh
dmUgbWFueSBsb2NhdGlvbnMsIA0KICAgIAlwb3NzaWJseSB1cCB0byB0aG91c2FuZHMgb2Ygc21h
bGwgc2l0ZXMuIEZyZXF1ZW50bHkgb25seSBwaG9uZXMgYW5kIG5ldHdvcmsgaW5mcmFzdHJ1Y3R1
cmUgYXJlDQogICAgCWluc3RhbGxlZCBpbiBicmFuY2hlcywgd2l0aG91dCBsb2NhbCByZWNvcmRp
bmcgc2VydmljZXMuIEluIGNhc2VzIHdoZXJlICBjYWxscyBpbnNpZGUgb3IgYmV0d2VlbiANCiAg
ICAJYnJhbmNoZXMgbXVzdCBiZSByZWNvcmRlZCwgYSBjZW50cmFsaXplZCByZWNvcmRpbmcgc3lz
dGVtIGluIGRhdGEgY2VudGVycyB0b2dldGhlciB3aXRoDQogICAJdGVsZXBob255IGluZnJhc3Ry
dWN0dXJlIChlLmcuIFBCWCkgbWUgZGVwbG95ZWQuPC90Pg0KDQogICAJDQogICAJPHQ+VXNlIENh
c2UgOTogUmVjb3JkIGNvbXBsZXggY2FsbCBzY2VuYXJpb3MuPC90Pg0KICAgCQ0KICAgCTx0PlRo
ZSBmb2xsb3dpbmcgaXMgYW4gZXhhbXBsZSBvZiBhIHNjZW5hcmlvIHdoZXJlIG9uZSBjYWxsIHRo
YXQgaXMgcmVjb3JkZWQgDQogICAJbXVzdCBiZSBhc3NvY2lhdGVkIHdpdGggYSByZWxhdGVkIGNh
bGwgdGhhdCBhbHNvIG11c3QgYmUgcmVjb3JkZWQuPC90Pg0KICAgCQ0KICAgCTx0Pm8gQSBDdXN0
b21lciBpcyBpbiBhIGNvbnZlcnNhdGlvbiB3aXRoIGEgQ3VzdG9tZXIgU2VydmljZSBBZ2VudC48
L3Q+DQogICAJDQogICAJPHQ+byBBZ2VudCBwdXRzIEN1c3RvbWVyIG9uIGhvbGQgaW4gb3JkZXIg
dG8gY29uc3VsdCB3aXRoIGEgU3VwZXJ2aXNvci48L3Q+DQogICAJDQogICAJPHQ+byBBZ2VudCBl
bnRlcnMgaW50byBhIGNvbnZlcnNhdGlvbiB3aXRoIFN1cGVydmlzb3IuPC90Pg0KICAgCQ0KICAg
CTx0Pm8gQWdlbnQgZGlzY29ubmVjdHMgZnJvbSBTdXBlcnZpc29yLCB0aGVuIHJlY29ubmVjdHMg
d2l0aCBDdXN0b21lci48L3Q+DQogICAJDQogICAJPHQ+byBUaGUgU3VwZXJ2aXNvciBjYWxsIG11
c3QgYmUgYXNzb2NpYXRlZCB3aXRoIHRoZSBvcmlnaW5hbCBjdXN0b21lciBjYWxsLjwvdD4NCiAg
IA0KICAgCQ0KICAgCTx0PlVzZSBjYXNlIDEwOiBIaWdoIGF2YWlsYWJpbGl0eSBhbmQgY29udGlu
dW91cyByZWNvcmRpbmcuPC90Pg0KICAgCQ0KICAgCTx0PlNwZWNpZmljIGRlcGxveW1lbnQgc2Nl
bmFyaW9zIHByZXNlbnQgZGlmZmVyZW50IHJlcXVpcmVtZW50cyBmb3Igc3lzdGVtIGF2YWlsYWJp
bGl0eSwgDQogICAJZXJyb3IgaGFuZGxpbmcsIGV0Yy4gaW5jbHVkaW5nOjwvdD4NCg0KCTx0Pm8g
QW4gU1JTIG11c3QgYWx3YXlzIGJlIGF2YWlsYWJsZSBhdCBjYWxsIHNldHVwIHRpbWUuPC90Pg0K
DQogICAJPHQ+byBObyBsb3NzIG9mIG1lZGlhIHJlY29yZGluZywgaW5jbHVkaW5nIGR1cmluZyBm
YWlsdXJlIG9mIGFuIFNSUy48L3Q+DQogICAJDQogICAJPHQ+byBUaGUgQ29tbXVuaWNhdGlvbiBT
ZXNzaW9uIG11c3QgYmUgdGVybWluYXRlZCAob3Igc3VpdGFibGUgDQogICAJbm90aWZpY2F0aW9u
IGdpdmVuIHRvIHBhcnRpZXMpIGluIHRoZSBldmVudCBvZiBhIHJlY29yZGluZyBmYWlsdXJlLjwv
dD4NCiAgIAkNCiAgDQogICAJDQogICAJPHQ+VXNlIENhc2UgMTE6IFJlY29yZCBtdWx0aS1jaGFu
bmVsLCBtdWx0aS1tZWRpYSBzZXNzaW9uLjwvdD4NCgkNCgk8dD5Tb21lIGFwcGxpY2F0aW9ucyBy
ZXF1aXJlIHRoZSByZWNvcmRpbmcgb2YgbW9yZSB0aGFuIG9uZSBtZWRpYQ0KCXN0cmVhbSwgcG9z
c2libHkgb2YgZGlmZmVyZW50IHR5cGVzLiAgTWVkaWEgYXJlIHN5bmNocm9uaXplZCwgZWl0aGVy
DQoJYXQgc3RvcmFnZSBvciBhdCBwbGF5YmFjay48L3Q+DQoJDQoJPHQ+U3BlZWNoIGFuYWx5dGlj
cyB0ZWNobm9sb2dpZXMgKGUuZy4gd29yZCBzcG90dGluZywgZW1vdGlvbiBkZXRlY3Rpb24sDQoJ
c3BlYWtlciBpZGVudGlmaWNhdGlvbikgbWF5IHJlcXVpcmUgc3BlYWtlci1zZXBhcmF0ZWQgcmVj
b3JkaW5ncyBmb3INCglvcHRpbXVtIHBlcmZvcm1hbmNlLjwvdD4NCgkNCgk8dD5NdWx0aS1tb2Rh
bCBDb250YWN0IENlbnRlcnMgbWF5IGluY2x1ZGUgYXVkaW8sIHZpZGVvLCBJTSBvciBvdGhlcg0K
CWludGVyYWN0aW9uIG1vZGFsaXRpZXMuPC90Pg0KCQ0KCTx0PkluIHRyYWRpbmcgZmxvb3JzIGVu
dmlyb25tZW50cywgaW4gb3JkZXIgdG8gbWluaW1pemUgc3RvcmFnZSBhbmQgcmVjb3JkaW5nIHN5
c3RlbSByZXNvdXJjZXMsIA0KCWl0IG1heSBiZSBwcmVmZXJhYmxlIHRvIG1peCBtdWx0aXBsZSBj
b25jdXJyZW50IGNhbGxzIChDb21tdW5pY2F0aW9uIFNlc3Npb25zKSANCglvbiBkaWZmZXJlbnQg
aGFuZHNldHMvc3BlYWtlcnMgb24gdGhlIHNhbWUgdHVycmV0IGludG8gc2luZ2xlIHJlY29yZGlu
ZyBzZXNzaW9uLjwvdD4NCgkNCgk8dD5Vc2UgQ2FzZSAxMjogUmVhbC10aW1lIG1lZGlhIHByb2Nl
c3NpbmcuPC90Pg0KCQ0KCTx0Pkl0IG11c3QgYmUgcG9zc2libGUgZm9yIGFuIFNSUyB0byBzdXBw
b3J0IHJlYWwtdGltZSBtZWRpYSBwcm9jZXNzaW5nLCBzdWNoIGFzIHNwZWVjaCBhbmFseXRpY3MN
CglvZiB0cmFkaW5nIGZsb29yIGludGVyYWN0aW9ucy4gUmVhbC10aW1lIGFuYWx5dGljcyBtYXkg
YmUgZW1wbG95ZWQgZm9yIGF1dG9tYXRpYyBpbnRlcnZlbnRpb24gDQoJKHN0b3BwaW5nIGludGVy
YWN0aW9uIG9yIGFsZXJ0aW5nKSBpZiBmb3IgZXhhbXBsZSwgYSB0cmFkZXIgaXMgbm90IGZvbGxv
d2luZyByZWd1bGF0aW9ucy48L3Q+DQoJDQoJPHQ+U3BlYWtlciBzZXBhcmF0aW9uIGlzIHJlcXVp
cmVkIGluIG9yZGVyIHRvIHJlbGlhYmx5IGRldGVjdCB3aG8gaXMgc2F5aW5nIHNwZWNpZmljIHBo
cmFzZXMuPC90Pg0KICAgIDwvc2VjdGlvbj4gICAgDQoNCiAgICA8c2VjdGlvbiB0aXRsZT0iUmVx
dWlyZW1lbnRzIj4NCiAgICAJPHQ+VGhlIGZvbGxvd2luZyBhcmUgcmVxdWlyZW1lbnRzIGZvciBT
SVAtYmFzZWQgTWVkaWEgUmVjb3JkaW5nOjwvdD4NCiAgICAJDQogICAgCQ0KCTx0Pm8gUkVRLTAw
MSBUaGUgbWVjaGFuaXNtIE1VU1QgcHJvdmlkZSBhIG1lYW5zIGZvciB1c2luZyB0aGUgU0lQIHBy
b3RvY29sIGZvciBlc3RhYmxpc2hpbmcsIA0KCW1haW50YWluaW5nIGFuZCB0ZXJtaW5hdGluZyBS
ZWNvcmRpbmcgU2Vzc2lvbnMgYmV0d2VlbiBhIFNlc3Npb24gUmVjb3JkaW5nIENsaWVudCBhbmQg
YSANCglTZXNzaW9uIFJlY29yZGluZyBTZXJ2ZXIuPC90Pg0KICAgIA0KICAgICAgIAk8dD5vIFJF
US0wMDIgVGhlIG1lY2hhbmlzbSBNVVNUIHN1cHBvcnQgdGhlIGFiaWxpdHkgdG8gcmVjb3JkIGFs
bCBDU3MgaW4gdGhlaXIgZW50aXJldHkuPC90Pg0KICAgIA0KICAgICAgCTx0Pm8gUkVRLTAwMyBU
aGUgbWVjaGFuaXNtIE1VU1Qgc3VwcG9ydCB0aGUgYWJpbGl0eSB0byByZWNvcmQgc2VsZWN0ZWQg
Q1NzIGluIHRoZWlyIGVudGlyZXR5LCBhY2NvcmRpbmcgdG8gcG9saWN5LjwvdD4NCiAgICANCiAg
ICAgICAJPHQ+byBSRVEtMDA0IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5
IHRvIHJlY29yZCBzZWxlY3RlZCBwYXJ0cyBvZiBzZWxlY3RlZCBDU3MuPC90Pg0KICAgIA0KICAg
ICAgIAk8dD5vIFJFUS0wMDUgVGhlIG1lY2hhbmlzbSBNVVNUIHN1cHBvcnQgdGhlIGFiaWxpdHkg
dG8gcmVjb3JkIGEgQ1Mgd2l0aG91dCBsb3NzIG9mIG1lZGlhIA0KICAgICAgIAkoZm9yIGV4YW1w
bGUsIGNsaXBwaW5nIG1lZGlhIGF0IHRoZSBiZWdpbm5pbmcgb2YgdGhlIENTKSBkdWUgdG8gUlMg
cmVjb3JkaW5nIHByZXBhcmF0aW9uIGFuZCBhbHNvLCANCiAgICAgICAJd2l0aG91dCBpbXBhY3Rp
bmcgdGhlIHF1YWxpdHkgb3IgdGltaW5nIG9mIHRoZSBDUyAoZm9yIGV4YW1wbGUsIGRlbGF5aW5n
IHRoZSBzdGFydCBvZiB0aGUgQ1Mgd2hpbGUgDQogICAgICAgCXByZXBhcmF0aW9uIGZvciByZWNv
cmRpbmcgc2Vzc2lvbikuIFNlZSBVc2UgQ2FzZSA0IGluIFNlY3Rpb24gNCBmb3IgbW9yZSBkZXRh
aWxzLjwvdD4NCiAgICANCiAgICANCiAgICAgICAJPHQ+byBSRVEtMDA2IFRoZSBtZWNoYW5pc20g
TVVTVCBzdXBwb3J0IHRoZSByZWNvcmRpbmcgb2YgSVZSIHNlc3Npb25zLjwvdD4NCiAgICAgICAJ
DQoNCiAgIAk8dD5vIFJFUS0wMDcgVGhlIG1lY2hhbmlzbSBNVVNUIHN1cHBvcnQgdGhlIHJlY29y
ZGluZyBvZiBSVFAgbWVkaWEgdHlwZXMgdm9pY2UsIA0KICAgCURUTUYgKGFzIGRlZmluZWQgYnkg
W1JGQzQ3MzNdKSwgdmlkZW8sIGFuZCB0ZXh0IChhcyBkZWZpbmVkIGJ5IFtSRkM0MTAzXSkuPC90
Pg0KICAgCQ0KIA0KCTx0Pm8gUkVRLTAwOCBUaGUgbWVjaGFuaXNtIE1VU1Qgc3VwcG9ydCB0aGUg
YWJpbGl0eSBmb3IgYW4gU1JDIHRvIGRlbGl2ZXIgbWl4ZWQgYXVkaW8NCglzdHJlYW1zIGZyb20g
bXVsdGlwbGUgQ29tbXVuaWNhdGlvbiBTZXNzaW9ucyB0byBhbiBTUlMuPC90Pg0KDQoJPHQ+Tm90
ZTogQSBtaXhlZCBhdWRpbyBzdHJlYW0gaXMgd2hlcmUgc2V2ZXJhbCByZWxhdGVkIENvbW11bmlj
YXRpb24gU2Vzc2lvbnMNCglhcmUgY2FycmllZCBpbiBhIHNpbmdsZSBSZWNvcmRpbmcgU2Vzc2lv
bi4gIEEgbWl4ZWQgbWVkaWEgc3RyZWFtIGlzDQoJdHlwaWNhbGx5IHByb2R1Y2VkIGJ5IGEgbWl4
ZXIgZnVuY3Rpb24uIA0KCVRoZSBSUyBNQVkgYmUgaW5mb3JtZWQgYWJvdXQgdGhlIGNvbXBvc2l0
aW9uIG9mIHRoZSBtaXhlZCBzdHJlYW1zIHRocm91Z2ggc2Vzc2lvbiBtZXRhZGF0YS48L3Q+DQoN
Cgk8dD5vIFJFUS0wMDk6IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5IGZv
ciBhbiBTUkMgdG8gZGVsaXZlciANCm1peGVkIGF1ZGlvIHN0cmVhbXMgZnJvbSBkaWZmZXJlbnQg
cGFydGllcyBvZiBhIGdpdmVuIENvbW11bmljYXRpb24gU2Vzc2lvbiB0byBhbiBTUlMuPC90Pg0K
DQoNCiAgICAgICAJPHQ+byBSRVEtMDEwIFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSBh
YmlsaXR5IHRvIGRlbGl2ZXIgdG8gdGhlIFNSUyBtdWx0aXBsZSBtZWRpYSBzdHJlYW1zIGZvciBh
IGdpdmVuIENTLjwvdD4NCiAgICANCiAgICAgICAJPHQ+byBSRVEtMDExIFRoZSBtZWNoYW5pc20g
TVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5IHRvIHBhdXNlIGFuZCByZXN1bWUgdGhlIA0KICAgICAg
IAl0cmFuc21pc3Npb24gYW5kIGNvbGxlY3Rpb24gb2YgUlMgbWVkaWEuPC90Pg0KICAgIA0KIAk8
dD5vIFJFUS0wMTIgVGhlIG1lY2hhbmlzbSBNVVNUIHByb3ZpZGUgdGhlIFNSUyB3aXRoIG1ldGFk
YXRhIGRlc2NyaWJpbmcgQ1NzIA0KIAl0aGF0IGFyZSBiZWluZyByZWNvcmRlZCwgaW5jbHVkaW5n
IHRoZSBtZWRpYSBiZWluZyB1c2VkIGFuZCB0aGUgaWRlbnRpdGllcyBvZiANCiAJcGFydGllcyBp
bnZvbHZlZC48L3Q+DQoNCgk8dD5vIFJFUS0wMTMgVGhlIG1lY2hhbmlzbSBNVVNUIHByb3ZpZGUg
dGhlIFNSUyB3aXRoIHRoZSBtZWFucyB0byBjb3JyZWxhdGUgDQoJUlMgbWVkaWEgd2l0aCBDUyBw
YXJ0aWNpcGFudCBtZWRpYS48L3Q+DQoNCiAgICANCgk8dD5vIFJFUS0wMTQgTWV0YWRhdGEgZm9y
bWF0IG11c3QgYmUgYWdub3N0aWMgb2YgdGhlIHRyYW5zcG9ydCBwcm90b2NvbC48L3Q+DQogICAg
DQoNCgk8dD5vIFJFUS0wMTU6IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IGEgbWVhbnMgdG8g
c3RvcCB0aGUgcmVjb3JkaW5nLjwvdD4NCg0KICAgICAgIAk8dD5vIFJFUS0wMTY6IFRoZSBtZWNo
YW5pc20gTVVTVCBzdXBwb3J0IGEgbWVhbnMgZm9yIGEgcmVjb3JkaW5nLWF3YXJlIFVBIGludm9s
dmVkIA0KICAgICAgIAlpbiBhIENTIHRvIHJlcXVlc3QgYXQgc2Vzc2lvbiBlc3RhYmxpc2htZW50
IHRpbWUgdGhhdCB0aGUgQ1MgIHNob3VsZCBiZSByZWNvcmRlZCANCiAgICAgICAJb3Igc2hvdWxk
IG5vdCBiZSByZWNvcmRlZCwgdGhlIGhvbm9yaW5nIG9mIHN1Y2ggYSByZXF1ZXN0IGJlaW5nIGRl
cGVuZGVudCBvbiBwb2xpY3kuPC90Pg0KDQoNCiAgICAgICAJPHQ+byBSRVEtMDE3OiBUaGUgbWVj
aGFuaXNtIE1VU1Qgc3VwcG9ydCBhIG1lYW5zIGZvciBhIHJlY29yZGluZy1hd2FyZSBVQSBpbnZv
bHZlZCANCiAgICAgICAJaW4gYSBDUyB0byByZXF1ZXN0IGR1cmluZyBhIHNlc3Npb24gdGhhdCB0
aGUgcmVjb3JkaW5nIG9mIHRoZSBDUyAgc2hvdWxkIGJlIHN0YXJ0ZWQsIA0KICAgICAgIAlwYXVz
ZWQsIHJlc3VtZWQgb3Igc3RvcHBlZCwgdGhlIGhvbm9yaW5nIG9mIHN1Y2ggYSByZXF1ZXN0IGJl
aW5nIGRlcGVuZGVudCBvbiBwb2xpY3kuPC90Pg0KDQoNCgk8dD5vIFJFUS0wMTggVGhlIG1lY2hh
bmlzbSBNVVNUIE5PVCBwcmV2ZW50IHRoZSBhcHBsaWNhdGlvbiBvZiB0b25lcyBvciBhbm5vdW5j
ZW1lbnRzIGR1cmluZyANCglyZWNvcmRpbmcgb3IgYXQgdGhlIHN0YXJ0IG9mIGEgQ1MgdG8gc3Vw
cG9ydCBub3RpZmljYXRpb24gdG8gcGFydGljaXBhbnRzIHRoYXQgdGhlIGNhbGwgaXMgDQoJYmVp
bmcgcmVjb3JkZWQgb3IgbWF5IGJlIHJlY29yZGVkLjwvdD4NCg0KCQ0KCTx0Pm8gUkVRLTAxOSBU
aGUgbWVjaGFuaXNtIE1VU1QgcHJvdmlkZSBhIG1lYW5zIG9mIGluZGljYXRpbmcgdG8gcmVjb3Jk
aW5nLWF3YXJlIFVBcyB3aGV0aGVyIA0KCXJlY29yZGluZyBpcyB0YWtpbmcgcGxhY2UsIGZvciBh
cHByb3ByaWF0ZSByZW5kZXJpbmcgYXQgdGhlIHVzZXIgaW50ZXJmYWNlLjwvdD4NCg0KDQoJPHQ+
byBSRVEtMDIwIFRoZSAgbWVjaGFuaXNtIE1VU1QgcHJvdmlkZSBhIHdheSBmb3IgbWV0YWRhdGEg
dG8gYmUgY29udmV5ZWQgdG8gdGhlIFNSUyBpbmNyZW1lbnRhbGx5IGR1cmluZyB0aGUgQ1MuPC90
Pg0KDQoNCgk8dD5vIFJFUS0wMjEgVGhlIG1lY2hhbmlzbSBNVVNUIE5PVCBwcmV2ZW50IGhpZ2gg
YXZhaWxhYmlsaXR5IGRlcGxveW1lbnRzLjwvdD4NCg0KDQoJPHQ+byBSRVEtMDIyIFRoZSBtZWNo
YW5pc20gTVVTVCBwcm92aWRlIHRoZSBTUlMgdGhlIHN0YXJ0aW5nIHdhbGwgY2xvY2sgdGltZSBm
b3IgDQoJZWFjaCBSUyBtZWRpYSBzdHJlYW0gY29ycmVzcG9uZGluZyB0byB0aGUgQ1MgcGFydGlj
aXBhbnQgbWVkaWEuPC90Pg0KDQoJPHQ+byBSRVEtMDIzIFRoZSBtZWNoYW5pc20gTVVTVCBwcm92
aWRlIHRoZSBTUlMgdGhlIHdhbGwgY2xvY2sgdGltZSB3aGVuIHRoZSANCglSZWNvcmRpbmcgU2Vz
c2lvbiBpcyBwYXVzZWQgYW5kIHJlc3VtZWQuPC90Pg0KDQogICAgICAJPHQ+byBSRVEtMDI0IFRo
ZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IGZ1bmN0aW9uYWxpdHkgc3VjaCB0aGF0IGlmIHRoZSBD
UyBpcyBlbmNyeXB0ZWQsIA0KICAgICAgCXRoZSBSUyBtYXkgdXNlIHRoZSBzYW1lIG9yIGRpZmZl
cmVudCBlbmNyeXB0aW9uIGtleXMuPC90Pg0KDQoJPHQ+byBSRVEtMDI1IFRoZSBtZWNoYW5pc20g
TVVTVCBwcm92aWRlIG1lYW5zIGZvciBhbiBTUlMgdG8gYXV0aGVudGljYXRlIHRoZSBTUkMgb24g
UlMgaW5pdGlhdGlvbi48L3Q+DQoNCgkNCgk8dD5vIFJFUS0wMjYgVGhlIG1lY2hhbmlzbSBNVVNU
IHByb3ZpZGUgbWVhbnMgZm9yIGFuIFNSQyB0byBhdXRoZW50aWNhdGUgdGhlIFNSUyBvbiBSUyBp
bml0aWF0aW9uLjwvdD4NCg0KDQoJPHQ+byBSRVEtMDI3IFRoZSBtZWNoYW5pc20gTVVTVCBlbnN1
cmUgdGhhdCB0aGUgaW50ZWdyaXR5IG9mIHRoZSBtZXRhZGF0YSBzZW50IGZyb20gU1JDIHRvIFNS
UyBpcyBhbiBhY2N1cmF0ZSByZXByZXNlbnRhdGlvbiBvZiB0aGUgb3JpZ2luYWwgQ1MgbWV0YWRh
dGEuPC90Pg0KCQ0KCTx0Pm8gUkVRLTAyOCBUaGUgbWVjaGFuaXNtIE1VU1QgZW5zdXJlIHRoYXQg
dGhlIGludGVncml0eSBvZiB0aGUgbWVkaWEgc2VudCBmcm9tIFNSQyB0byBTUlMgaXMgYW4gYWNj
dXJhdGUgcmVwcmVzZW50YXRpb24gb2YgdGhlIG9yaWdpbmFsIENTIG1lZGlhLjwvdD4NCgkNCgkN
Cgk8dD5vIFJFUS0wMjkgVGhlIG1lY2hhbmlzbSBNVVNUIGVuc3VyZSB0aGUgY29uZmlkZW50aWFs
aXR5IG9mIHRoZSBNZXRhZGF0YSBzZW50IGZyb20gU1JDIHRvIFNSUy48L3Q+DQoJDQoJPHQ+byBS
RVEtMDMwIFRoZSBtZWNoYW5pc20gTVVTVCBwcm92aWRlIGEgbWVhbnMgdG8gc3VwcG9ydCBSUyBj
b25maWRlbnRpYWxpdHkuPC90Pg0KDQoJPHQ+byBSRVEtMDMxIFRoZSBtZWNoYW5pc20gTVVTVCBz
dXBwb3J0IHRoZSBhYmlsaXR5IHRvIGRlbGl2ZXIgdG8gdGhlIFNSUyBtdWx0aXBsZSBtZWRpYSBz
dHJlYW1zIA0KCW9mIHRoZSBzYW1lIG1lZGlhIHR5cGUgKGUuZy4gYXVkaW8sIHZpZGVvKS4gRm9y
IGV4YW1wbGUgaW4gdGhlIGNhc2Ugb2YgZGVsaXZlcmluZyB1bm1peGVkIGF1ZGlvIGZvciANCgll
YWNoIHBhcnRpY2lwYW50IGluIHRoZSBDUy48L3Q+DQoNCjwvc2VjdGlvbj4NCg0KDQogICAgPHNl
Y3Rpb24gdGl0bGU9IlByaXZhY3kgQ29uc2lkZXJhdGlvbnMiPg0KICAgICAgIDx0PlJlc3BlY3Rp
bmcgdGhlIHByaXZhY3kgcmlnaHRzIGFuZCB3aXNoZXMgb2YgdXNlcnMgZW5nYWdlZCBpbiBhIGNh
bGwNCiAgICAJaXMgb2YgcGFyYW1vdW50IGltcG9ydGFuY2UuIEluIG1hbnkganVyaXNkaWN0aW9u
cyBwYXJ0aWNpcGFudHMgaGF2ZSBhIHJpZ2h0IHRvIA0KICAgICAgICBrbm93IHRoYXQgdGhlIHNl
c3Npb24gaXMgYmVpbmcgcmVjb3JkZWQgb3IgbWlnaHQgYmUgcmVjb3JkZWQsIGFuZCBoYXZlIGEg
DQogICAgICAgIHJpZ2h0IHRvIG9wdCBvdXQsIGVpdGhlciBieSB0ZXJtaW5hdGluZyB0aGUgY2Fs
bCBvciBieSBkZW1hbmRpbmcgdGhhdCB0aGUgDQogICAgICAgIGNhbGwgbm90IGJlIHJlY29yZGVk
LiBUaGVyZWZvcmUgdGhpcyBkb2N1bWVudCBjb250YWlucyByZXF1aXJlbWVudHMgZm9yIGJlaW5n
IA0KICAgICAgIGFibGUgdG8gbm90aWZ5IHVzZXJzIHRoYXQgYSBjYWxsIGlzIGJlaW5nIHJlY29y
ZGVkIGFuZCBmb3IgdXNlcnMgdG8gYmUgYWJsZSANCiAgICAgICB0byByZXF1ZXN0IHRoYXQgYSBj
YWxsIG5vdCBiZSByZWNvcmRlZC4NCiAgICAgICANCiAgICAgICBVc2UgY2FzZXMgd2hlcmUgdXNl
cnMgcGFydGljaXBhdGluZyBpbiBhIGNhbGwgYXJlIG5vdCBpbmZvcm1lZCB0aGF0IHRoZSANCiAg
ICAgICBjYWxsIGlzIG9yIG1pZ2h0IGJlIHJlY29yZGVkIGFyZSBvdXRzaWRlIHRoZSBzY29wZSBv
ZiB0aGlzIGRvY3VtZW50LiANCiAgICAgICBJbiBwYXJ0aWN1bGFyLCBsYXdmdWwgaW50ZXJjZXB0
IGlzIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQuPC90Pg0KICAgICAgIA0KICAg
ICAgIA0KICAgICAgIA0KICAgICAgIDx0Pg0KICAgICAgIFJlcXVpcmVtZW50cyBmb3IgcGFydGlj
aXBhbnQgbm90aWZpY2F0aW9uIG9mIHJlY29yZGluZyANCiAgICAgICB2YXJ5IHdpZGVseSBieSBq
dXJpc2RpY3Rpb24uIEluIGEgZ2l2ZW4gZGVwbG95bWVudCwgbm90IGFsbCB1c2VycyB3aWxsIGJl
IA0KICAgICAgIGF1dGhvcml6ZWQgdG8gc3RvcCB0aGUgcmVjb3JkaW5nIA0KCW9mIGEgQ1MgKGFs
dGhvdWdoIGFueSB1c2VyIGNhbiB0ZXJtaW5hdGUgYSBDUykuIFR5cGljYWxseSB1c2VycyB3aXRo
aW4gdGhlIA0KCWRvbWFpbiB0aGF0IGlzIGNhcnJ5aW5nIG91dCB0aGUgcmVjb3JkaW5nIHdpbGwg
YmUgc3ViamVjdCB0byBwb2xpY2llcyBvZiANCgl0aGF0IGRvbWFpbiBjb25jZXJuaW5nIHdoZXRo
ZXIgQ1NzIGFyZSByZWNvcmRlZC4gRm9yIGV4YW1wbGUsIGluIGEgY2FsbCBjZW50cmUsIA0KCWFn
ZW50cyB3aWxsIGJlIHN1YmplY3QgdG8gcG9saWNpZXMgb2YgdGhlIGNhbGwgY2VudHJlIGFuZCBt
YXkgb3IgbWF5IG5vdCBoYXZlIA0KCXRoZSByaWdodCB0byBwcmV2ZW50IHRoZSByZWNvcmRpbmcg
b2YgYSBDUyBvciBwYXJ0IG9mIGEgQ1MuIFVzZXJzIGNhbGxpbmcgaW50byANCgl0aGUgY2FsbCBj
ZW50cmUsIG9uIHRoZSBvdGhlciBoYW5kLCB3aWxsIHR5cGljYWxseSBoYXZlIHRvIGFzayB0aGUg
YWdlbnQgbm90IA0KCXRvIHJlY29yZCB0aGUgQ1MuIElmIHRoZSBhZ2VudCBpcyB1bmFibGUgdG8g
cHJldmVudCByZWNvcmRpbmcsIG9yIGlmIHRoZSBjYWxsZXIgDQoJZG9lcyBub3QgdHJ1c3QgdGhl
IGFnZW50LCB0aGUgb25seSBvcHRpb24gZ2VuZXJhbGx5IGlzIHRvIHRlcm1pbmF0ZSB0aGUgQ1Mu
PC90Pg0KDQoJPHQ+UHJpdmFjeSBjb25zaWRlcmF0aW9ucyBhbHNvIGV4dGVuZCB0byB3aGF0IGhh
cHBlbnMgdG8gYSByZWNvcmRpbmcgb25jZSBpdCANCgloYXMgYmVlbiBjcmVhdGVkLiBUeXBpY2Fs
IGlzc3VlcyBhcmUgd2hvIGNhbiBhY2Nlc3MgdGhlIHJlY29yZGluZyAoZS5nLiwgDQoJcmVjZWl2
ZSBhIGNvcHkgb2YgdGhlIHJlY29yZGluZywgdmlldyB0aGUgbWV0YWRhdGEsIHBsYXkgYmFjayB0
aGUgbWVkaWEsIGV0Yy4pLCANCglmb3Igd2hhdCBwdXJwb3NlIHRoZSByZWNvcmRpbmcgY2FuIGJl
IHVzZWQgKGUuZy4sIGZvciBub24tcmVwdWRpYXRpb24sIGZvciANCgl0cmFpbmluZyBwdXJwb3Nl
cywgZm9yIHF1YWxpdHkgY29udHJvbCBwdXJwb3NlcywgZXRjLikgYW5kIGZvciBob3cgbG9uZyB0
aGUgDQoJcmVjb3JkaW5nIGlzIHRvIGJlIHJldGFpbmVkIGJlZm9yZSBkZWxldGlvbi4gVGhlc2Ug
YXJlIHR5cGljYWxseSBwb2xpY2llcyBvZiANCgl0aGUgZG9tYWluIHRoYXQgbWFrZXMgdGhlIHJl
Y29yZGluZywgcmF0aGVyIHRoYW4gcG9saWNpZXMgb2YgaW5kaXZpZHVhbCB1c2VycyANCglpbnZv
bHZlZCBpbiBhIHJlY29yZGVkIENTLCB3aGV0aGVyIHRob3NlIHVzZXJzIGJlIGluIHRoZSBzYW1l
IGRvbWFpbiBvciBpbiBhIA0KCWRpZmZlcmVudCBkb21haW4uIFRha2luZyB0aGUgY2FsbCBjZW50
cmUgZXhhbXBsZSBhZ2FpbiwgYWdlbnRzIG1pZ2h0IGJlIG1hZGUgDQoJYXdhcmUgb2YgY2FsbCBj
ZW50cmUgcG9saWN5IHJlZ2FyZGluZyByZXRlbnRpb24gYW5kIHVzZSBvZiByZWNvcmRpbmdzIGFz
IHBhcnQgDQoJb2YgdGhlaXIgZW1wbG95bWVudCBjb250cmFjdCwgYW5kIGNhbGxlcnMgZnJvbSBv
dXRzaWRlIHRoZSBjYWxsIGNlbnRyZSBtaWdodCANCgliZSBnaXZlbiBzb21lIGluZm9ybWF0aW9u
IGFib3V0IHBvbGljeSB3aGVuIG5vdGlmaWVkIHRoYXQgYSBDUyB3aWxsIGJlIHJlY29yZGVkIA0K
CShlLmcuLCB0aHJvdWdoIGFuIGFubm91bmNlbWVudCB0aGF0IHNheXMgdGhhdCBjYWxscyBtYXkg
YmUgcmVjb3JkZWQgIGZvciBxdWFsaXR5IHB1cnBvc2VzKS48L3Q+DQoJDQoJPHQ+VGhpcyBkb2N1
bWVudCBkb2VzIG5vdCBzcGVjaWZ5IGFueSByZXF1aXJlbWVudHMgZm9yIGEgdXNlciBlbmdhZ2Vk
IGluDQoJYSBDUyB0byBiZSBhYmxlIHRvIGRpY3RhdGUgcG9saWN5IGZvciB3aGF0IGhhcHBlbnMg
dG8gYSByZWNvcmRpbmcsIG9yDQoJZm9yIHN1Y2ggaW5mb3JtYXRpb24gdG8gYmUgY29udmV5ZWQg
ZnJvbSBhbiBTUkMgdG8gYW4gU1JTLiBJdCBpcw0KCWFzc3VtZWQgdGhhdCB0aGUgU1JTIGhhcyBh
Y2Nlc3MgdG8gcG9saWN5IGFwcGxpY2FibGUgdG8gaXRzDQoJZW52aXJvbm1lbnQgYW5kIGNhbiBl
bnN1cmUgdGhhdCByZWNvcmRpbmdzIGFyZSBzdG9yZWQgYW5kIHVzZWQgaW4NCglhY2NvcmRhbmNl
IHdpdGggdGhhdCBwb2xpY3kuDQoJPC90Pg0KICAgIDwvc2VjdGlvbj4NCg0KICAgIA0KICAgIDxz
ZWN0aW9uIHRpdGxlPSJTZWN1cml0eSBDb25zaWRlcmF0aW9ucyI+DQogICAgICAgPHQ+U2Vzc2lv
biByZWNvcmRpbmcgaGFzIHN1YnN0YW50aWFsIHNlY3VyaXR5IGltcGxpY2F0aW9ucywgZm9yIHRo
ZQ0KICAgICAgIFNJUCBVQSdzIGJlaW5nIHJlY29yZGVkLCB0aGUgU1JDLCBhbmQgdGhlIFNSUy48
L3Q+DQogICAgICAgICAgIA0KICAgICAgIDx0PkZvciB0aGUgU0lQIFVBJ3MgaW52b2x2ZWQgaW4g
dGhlIENvbW11bmljYXRpb24gU2Vzc2lvbiwgdGhlIHJlcXVpcmVtZW50cw0KICAgICAgIGluIHRo
aXMgZHJhZnQgZW5hYmxlIHRoZSBVQSB0byBpZGVudGlmeSB0aGF0IGEgQ29tbXVuaWNhdGlvbiBT
ZXNzaW9uIGlzIGJlaW5nDQogICAgICAgcmVjb3JkZWQgYW5kIGZvciB0aGUgVUEgdG8gcmVxdWVz
dCB0aGF0IGEgZ2l2ZW4gQ29tbXVuaWNhdGlvbiBTZXNzaW9uIGlzIG5vdA0KICAgICAgIHN1Ympl
Y3QgdG8gcmVjb3JkaW5nLjwvdD4NCiAgICANCiAgICAgICA8dD5TaW5jZSBodW1hbnMgZG9uJ3Qg
dHlwaWNhbGx5IGxvb2sgYXQgb3Iga25vdyBhYm91dCBwcm90b2NvbCBzaWduYWxpbmcNCiAgICAg
ICBzdWNoIGFzIFNJUCwgYW5kIGluZGVlZCB0aGUgU0lQIHNlc3Npb24gbWlnaHQgaGF2ZSBvcmln
aW5hdGVkIHRocm91Z2gNCiAgICAgICBhIFBTVE4gR2F0ZXdheSB3aXRob3V0IGFueSBhYmlsaXR5
IHRvIHBhc3Mgb24gaW4tc2lnbmFsaW5nDQogICAgICAgaW5kaWNhdGlvbnMgb2YgcmVjb3JkaW5n
LCB1c2VycyBjYW4gYmUgbm90aWZpZWQgb2YgcmVjb3JkaW5nIGluIHRoZQ0KICAgICAgIG1lZGlh
IGl0c2VsZiB0aHJvdWdoIHZvaWNlIGFubm91bmNlbWVudHMsIGEgdmlzdWFsIGluZGljYXRvciBv
bg0KICAgICAgIHRoZSBlbmRwb2ludCwgb3Igb3RoZXIgbWVhbnMuPC90Pg0KICAgIA0KICAgICAg
IDx0PldpdGggcmVnYXJkcyB0byBzZWN1cml0eSBpbXBsaWNhdGlvbnMgb2YgdGhlIHByb3RvY29s
KHMpLCBjbGVhcmx5DQogICAgICAgdGhlcmUgaXMgYSBuZWVkIGZvciBhdXRoZW50aWNhdGlvbiwg
YXV0aG9yaXphdGlvbiwgZWF2ZXNkcm9wcGluZw0KICAgICAgIHByb3RlY3Rpb24sIGFuZCBub24t
cmVwdWRpYXRpb24gZm9yIHRoZSBzb2x1dGlvbi4gIFRoZSBTUkMgbmVlZHMgdG8NCiAgICAgICBr
bm93IHRoZSBTUlMgaXQgaXMgY29tbXVuaWNhdGluZyB3aXRoIGlzIGxlZ2l0aW1hdGUsIGFuZCB2
aWNlLXZlcnNhLA0KICAgICAgIGV2ZW4gaWYgdGhleSBhcmUgaW4gZGlmZmVyZW50IGRvbWFpbnMu
ICBCb3RoIHRoZSBzaWduYWxpbmcgYW5kIG1lZGlhDQogICAgICAgZm9yIHRoZSBSZWNvcmRpbmcg
U2Vzc2lvbiBuZWVkIHRoZSBhYmlsaXR5IHRvIGJlIGF1dGhlbnRpY2F0ZWQgYW5kIHByb3RlY3Rl
ZCBmcm9tDQogICAgICAgZWF2ZXNkcm9wcGluZyBhbmQgbm9uLXJlcHVkaWF0aW9uLiAgUmVxdWly
ZW1lbnRzIGFyZQ0KICAgICAgIGRldGFpbGVkIGluIHRoZSByZXF1aXJlbWVudHMgc2VjdGlvbi48
L3Q+DQogICAgPC9zZWN0aW9uPg0KDQogICAgPHNlY3Rpb24gdGl0bGU9IklBTkEgQ29uc2lkZXJh
dGlvbnMiPg0KICAgICAgPHQ+VGhpcyBkb2N1bWVudCBoYXMgbm8gSUFOQSBhY3Rpb25zLjwvdD4N
CiAgICA8L3NlY3Rpb24+DQoNCiAgICA8c2VjdGlvbiB0aXRsZT0iQWNrbm93bGVkZ2VtZW50cyI+
DQogICAgICA8dD5UaGFua3MgdG8gRGFuIFdpbmcsIEFsYW4gSm9obnNvbiwgVmlqYXkgR3VyYmFu
aSwgDQogICAgICBDdWxsZW4gSmVubmluZ3MsIEhhZHJpZWwgS2FwbGFuLCBIZW5yeSBMdW0sIERh
dmUgU21pdGgsIE1hcnRpbiBQYWxtZXIsIEFsaXNzYSBDb29wZXIsIA0KICAgICAgRGVlcGFuc2h1
IEdhdXRhbSwgUGF1bCBLeXppdmF0LCBQYXJ0aGFzYXJhdGhpIFIsIGFuZCBSYW0gTW9oYW4gUg0K
ICAgICAgZm9yIHRoZWlyIHNpZ25pZmljYW50IGNvbnRyaWJ1dGlvbnMgYW5kIGFzc2lzdGFuY2Ug
d2l0aCB0aGlzIGRvY3VtZW50IGFuZCBXb3JraW5nIEdyb3VwLCANCiAgICAgIGFuZCB0byBhbGwg
dGhlIG1lbWJlcnMgb2YgdGhlIERJU1BBVENIIFdHIGFuZCBTSVBSRUMgV0cgbWFpbGluZyBsaXN0
cyBmb3IgDQogICAgICBwcm92aWRpbmcgdmFsdWFibGUgaW5wdXQgdG8gdGhpcyB3b3JrLjwvdD4N
CiAgICA8L3NlY3Rpb24+DQoNCiAgICANCiAgPC9taWRkbGU+DQogIA0KICAgIDxiYWNrPg0KICAg
ICAgICA8cmVmZXJlbmNlcyB0aXRsZT0nTm9ybWF0aXZlIFJlZmVyZW5jZXMnPg0KICAgICAgICAg
ICAmcmZjMjExOTsNCiAgICAgICAgICAgJnJmYzMyNjE7DQoJCSAgICZyZmM0MTAzOw0KCSAgICAg
ICAmcmZjNDczMzsNCiAgICAgICAgPC9yZWZlcmVuY2VzPg0KICAgIDwvYmFjaz4NCg0KPC9yZmM+
DQo=

------_=_NextPart_001_01CBE261.ED68E66B
Content-Type: text/html;
	name="SIPREC_req_diff_-07_vs_-08.html"
Content-Transfer-Encoding: base64
Content-Description: SIPREC_req_diff_-07_vs_-08.html
Content-Disposition: attachment;
	filename="SIPREC_req_diff_-07_vs_-08.html"

PGh0bWw+PGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJjb250ZW50LXR5cGUiIGNvbnRlbnQ9InRl
eHQvaHRtbDsgY2hhcnNldD1JU08tODg1OS0xIj4NCjx0aXRsZT53ZGlmZiBkcmFmdC1pZXRmLXNp
cHJlYy1yZXEtMDcudHh0IGRyYWZ0LWlldGYtc2lwcmVjLXJlcS0wOC50eHQ8L3RpdGxlPjwvaGVh
ZD48Ym9keT4NCjxwcmU+DQpESVNQQVRDSCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIEsuIFJlaG9yLCBFZC4NCkludGVybmV0LURyYWZ0ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgQ2lzY28gU3lzdGVtcw0KSW50ZW5k
ZWQgc3RhdHVzOiBJbmZvcm1hdGlvbmFsICAgICAgICAgICAgICAgICAgICAgICAgICAgTC4gUG9y
dG1hbiwgRWQuDQpFeHBpcmVzOiBTZXB0ZW1iZXIgPHN0cmlrZT48Zm9udCBjb2xvcj0icmVkIj44
LDwvZm9udD48L3N0cmlrZT4gPHN0cm9uZz48Zm9udCBjb2xvcj0iZ3JlZW4iPjE1LDwvZm9udD48
L3N0cm9uZz4gMjAxMSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIE5JQ0UgU3lzdGVt
cw0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgQS4gSHV0dG9uDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICBTaWVtZW5zIEVudGVycHJpc2UgQ29tbXVuaWNhdGlvbnMNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUi4gSmFpbg0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IElQQyBTeXN0ZW1zDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgTWFyY2ggPHN0cmlrZT48Zm9udCBjb2xvcj0icmVkIj4wNyw8L2ZvbnQ+
PC9zdHJpa2U+IDxzdHJvbmc+PGZvbnQgY29sb3I9ImdyZWVuIj4xNCw8L2ZvbnQ+PC9zdHJvbmc+
IDIwMTENCg0KICAgICAgICAgIFJlcXVpcmVtZW50cyBmb3IgU0lQLWJhc2VkIE1lZGlhIFJlY29y
ZGluZyAoU0lQUkVDKQ0KICAgICAgICAgICAgICAgICAgICAgICAgPHN0cmlrZT48Zm9udCBjb2xv
cj0icmVkIj5kcmFmdC1pZXRmLXNpcHJlYy1yZXEtMDc8L2ZvbnQ+PC9zdHJpa2U+DQogICAgICAg
ICAgICAgICAgICAgICAgICA8c3Ryb25nPjxmb250IGNvbG9yPSJncmVlbiI+ZHJhZnQtaWV0Zi1z
aXByZWMtcmVxLTA4PC9mb250Pjwvc3Ryb25nPg0KDQpBYnN0cmFjdA0KDQogICBTZXNzaW9uIHJl
Y29yZGluZyBpcyBhIGNyaXRpY2FsIHJlcXVpcmVtZW50IGluIG1hbnkgYnVzaW5lc3MNCiAgIGNv
bW11bmljYXRpb25zIGVudmlyb25tZW50cyBzdWNoIGFzIGNhbGwgY2VudGVycyBhbmQgZmluYW5j
aWFsDQogICB0cmFkaW5nIGZsb29ycy4gIEluIHNvbWUgb2YgdGhlc2UgZW52aXJvbm1lbnRzLCBh
bGwgY2FsbHMgbXVzdCBiZQ0KICAgcmVjb3JkZWQgZm9yIHJlZ3VsYXRvcnkgYW5kIGNvbXBsaWFu
Y2UgcmVhc29ucy4gIEluIG90aGVycywgY2FsbHMgbWF5DQogICBiZSByZWNvcmRlZCBmb3IgcXVh
bGl0eSBjb250cm9sIG9yIGJ1c2luZXNzIGFuYWx5dGljcy4NCg0KICAgUmVjb3JkaW5nIGlzIHR5
cGljYWxseSBwZXJmb3JtZWQgYnkgc2VuZGluZyBhIGNvcHkgb2YgdGhlIHNlc3Npb24NCiAgIG1l
ZGlhIHRvIHRoZSByZWNvcmRpbmcgZGV2aWNlcy4gIFRoaXMgZG9jdW1lbnQgc3BlY2lmaWVzIHJl
cXVpcmVtZW50cw0KICAgZm9yIGV4dGVuc2lvbnMgdG8gU0lQIHRoYXQgd2lsbCBtYW5hZ2UgZGVs
aXZlcnkgb2YgUlRQIG1lZGlhIHRvIGENCiAgIHJlY29yZGluZyBkZXZpY2UuICBUaGlzIGlzIGJl
aW5nIHJlZmVycmVkIHRvIGFzIFNJUC1iYXNlZCBNZWRpYQ0KICAgUmVjb3JkaW5nLg0KDQpTdGF0
dXMgb2YgdGhpcyBNZW1vDQoNCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgaXMgc3VibWl0dGVkIGlu
IGZ1bGwgY29uZm9ybWFuY2Ugd2l0aCB0aGUNCiAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFuZCBC
Q1AgNzkuDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhl
IEludGVybmV0IEVuZ2luZWVyaW5nDQogICBUYXNrIEZvcmNlIChJRVRGKS4gIE5vdGUgdGhhdCBv
dGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZQ0KICAgd29ya2luZyBkb2N1bWVudHMgYXMg
SW50ZXJuZXQtRHJhZnRzLiAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC0NCiAgIERyYWZ0
cyBpcyBhdCBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1cnJlbnQvLg0KDQog
ICBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVt
IG9mIHNpeCBtb250aHMNCiAgIGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29s
ZXRlZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55DQogICB0aW1lLiAgSXQgaXMgaW5hcHByb3By
aWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZQ0KICAgbWF0ZXJpYWwgb3Ig
dG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4gYXMgIndvcmsgaW4gcHJvZ3Jlc3MuIg0KDQogICBUaGlz
IEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIFNlcHRlbWJlciA8c3RyaWtlPjxmb250IGNv
bG9yPSJyZWQiPjgsPC9mb250Pjwvc3RyaWtlPiA8c3Ryb25nPjxmb250IGNvbG9yPSJncmVlbiI+
MTUsPC9mb250Pjwvc3Ryb25nPiAyMDExLg0KDQpDb3B5cmlnaHQgTm90aWNlDQoNCiAgIENvcHly
aWdodCAoYykgMjAxMSBJRVRGIFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVudGlmaWVkIGFzIHRo
ZQ0KICAgZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQuDQoNCiAgIFRoaXMg
ZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWwN
CiAgIFByb3Zpc2lvbnMgUmVsYXRpbmcgdG8gSUVURiBEb2N1bWVudHMNCiAgIChodHRwOi8vdHJ1
c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8pIGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZg0KICAg
cHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2UgZG9jdW1l
bnRzDQogICBjYXJlZnVsbHksIGFzIHRoZXkgZGVzY3JpYmUgeW91ciByaWdodHMgYW5kIHJlc3Ry
aWN0aW9ucyB3aXRoIHJlc3BlY3QNCiAgIHRvIHRoaXMgZG9jdW1lbnQuICBDb2RlIENvbXBvbmVu
dHMgZXh0cmFjdGVkIGZyb20gdGhpcyBkb2N1bWVudCBtdXN0DQogICBpbmNsdWRlIFNpbXBsaWZp
ZWQgQlNEIExpY2Vuc2UgdGV4dCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA0LmUgb2YNCiAgIHRo
ZSBUcnVzdCBMZWdhbCBQcm92aXNpb25zIGFuZCBhcmUgcHJvdmlkZWQgd2l0aG91dCB3YXJyYW50
eSBhcw0KICAgZGVzY3JpYmVkIGluIHRoZSBTaW1wbGlmaWVkIEJTRCBMaWNlbnNlLg0KDQogICA8
c3RyaWtlPjxmb250IGNvbG9yPSJyZWQiPlRoaXMgZG9jdW1lbnQgbWF5IGNvbnRhaW4gbWF0ZXJp
YWwgZnJvbSBJRVRGIERvY3VtZW50cyBvciBJRVRGDQogICBDb250cmlidXRpb25zIHB1Ymxpc2hl
ZCBvciBtYWRlIHB1YmxpY2x5IGF2YWlsYWJsZSBiZWZvcmUgTm92ZW1iZXINCiAgIDEwLCAyMDA4
LiAgVGhlIHBlcnNvbihzKSBjb250cm9sbGluZyB0aGUgY29weXJpZ2h0IGluIHNvbWUgb2YgdGhp
cw0KICAgbWF0ZXJpYWwgbWF5IG5vdCBoYXZlIGdyYW50ZWQgdGhlIElFVEYgVHJ1c3QgdGhlIHJp
Z2h0IHRvIGFsbG93DQogICBtb2RpZmljYXRpb25zIG9mIHN1Y2ggbWF0ZXJpYWwgb3V0c2lkZSB0
aGUgSUVURiBTdGFuZGFyZHMgUHJvY2Vzcy4NCiAgIFdpdGhvdXQgb2J0YWluaW5nIGFuIGFkZXF1
YXRlIGxpY2Vuc2UgZnJvbSB0aGUgcGVyc29uKHMpIGNvbnRyb2xsaW5nDQogICB0aGUgY29weXJp
Z2h0IGluIHN1Y2ggbWF0ZXJpYWxzLCB0aGlzIGRvY3VtZW50IG1heSBub3QgYmUgbW9kaWZpZWQN
CiAgIG91dHNpZGUgdGhlIElFVEYgU3RhbmRhcmRzIFByb2Nlc3MsIGFuZCBkZXJpdmF0aXZlIHdv
cmtzIG9mIGl0IG1heQ0KICAgbm90IGJlIGNyZWF0ZWQgb3V0c2lkZSB0aGUgSUVURiBTdGFuZGFy
ZHMgUHJvY2VzcywgZXhjZXB0IHRvIGZvcm1hdA0KICAgaXQgZm9yIHB1YmxpY2F0aW9uIGFzIGFu
IFJGQyBvciB0byB0cmFuc2xhdGUgaXQgaW50byBsYW5ndWFnZXMgb3RoZXINCiAgIHRoYW4gRW5n
bGlzaC48L2ZvbnQ+PC9zdHJpa2U+DQoNClRhYmxlIG9mIENvbnRlbnRzDQoNCiAgIDEuICBSZXF1
aXJlbWVudHMgbm90YXRpb24gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgPHN0cmlrZT48Zm9udCBjb2xvcj0icmVkIj40PC9mb250Pjwvc3RyaWtlPiAgPHN0cm9uZz48
Zm9udCBjb2xvcj0iZ3JlZW4iPjM8L2ZvbnQ+PC9zdHJvbmc+DQogICAyLiAgSW50cm9kdWN0aW9u
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzdHJp
a2U+PGZvbnQgY29sb3I9InJlZCI+NDwvZm9udD48L3N0cmlrZT4gIDxzdHJvbmc+PGZvbnQgY29s
b3I9ImdyZWVuIj4zPC9mb250Pjwvc3Ryb25nPg0KICAgMy4gIERlZmluaXRpb25zICAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3RyaWtlPjxmb250
IGNvbG9yPSJyZWQiPjU8L2ZvbnQ+PC9zdHJpa2U+ICA8c3Ryb25nPjxmb250IGNvbG9yPSJncmVl
biI+NDwvZm9udD48L3N0cm9uZz4NCiAgIDQuICBVc2UgQ2FzZXMgIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHN0cmlrZT48Zm9udCBjb2xvcj0i
cmVkIj43PC9mb250Pjwvc3RyaWtlPiAgPHN0cm9uZz48Zm9udCBjb2xvcj0iZ3JlZW4iPjY8L2Zv
bnQ+PC9zdHJvbmc+DQogICA1LiAgUmVxdWlyZW1lbnRzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gPHN0cmlrZT48Zm9udCBjb2xvcj0icmVkIj4xMTwv
Zm9udD48L3N0cmlrZT4gPHN0cm9uZz48Zm9udCBjb2xvcj0iZ3JlZW4iPjEwPC9mb250Pjwvc3Ry
b25nPg0KICAgNi4gIFByaXZhY3kgQ29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIDxzdHJpa2U+PGZvbnQgY29sb3I9InJlZCI+MTM8L2ZvbnQ+PC9z
dHJpa2U+IDxzdHJvbmc+PGZvbnQgY29sb3I9ImdyZWVuIj4xMjwvZm9udD48L3N0cm9uZz4NCiAg
IDcuICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiA8c3RyaWtlPjxmb250IGNvbG9yPSJyZWQiPjE0PC9mb250Pjwvc3RyaWtlPiA8
c3Ryb25nPjxmb250IGNvbG9yPSJncmVlbiI+MTM8L2ZvbnQ+PC9zdHJvbmc+DQogICA4LiAgSUFO
QSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gPHN0cmlrZT48Zm9udCBjb2xvcj0icmVkIj4xNTwvZm9udD48L3N0cmlrZT4gPHN0cm9uZz48
Zm9udCBjb2xvcj0iZ3JlZW4iPjE0PC9mb250Pjwvc3Ryb25nPg0KICAgOS4gIEFja25vd2xlZGdl
bWVudHMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDxzdHJp
a2U+PGZvbnQgY29sb3I9InJlZCI+MTU8L2ZvbnQ+PC9zdHJpa2U+IDxzdHJvbmc+PGZvbnQgY29s
b3I9ImdyZWVuIj4xNDwvZm9udD48L3N0cm9uZz4NCiAgIDEwLiBOb3JtYXRpdmUgUmVmZXJlbmNl
cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA8c3RyaWtlPjxmb250
IGNvbG9yPSJyZWQiPjE1PC9mb250Pjwvc3RyaWtlPiA8c3Ryb25nPjxmb250IGNvbG9yPSJncmVl
biI+MTQ8L2ZvbnQ+PC9zdHJvbmc+DQogICBBdXRob3JzJyBBZGRyZXNzZXMgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gPHN0cmlrZT48Zm9udCBjb2xvcj0i
cmVkIj4xNTwvZm9udD48L3N0cmlrZT4gPHN0cm9uZz48Zm9udCBjb2xvcj0iZ3JlZW4iPjE0PC9m
b250Pjwvc3Ryb25nPg0KDQoxLiAgUmVxdWlyZW1lbnRzIG5vdGF0aW9uDQoNCiAgIFRoZSBrZXkg
d29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9U
IiwNCiAgICJTSE9VTEQiLCAiU0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQg
Ik9QVElPTkFMIiBpbiB0aGlzDQogICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMg
ZGVzY3JpYmVkIGluIFtSRkMyMTE5XSBhbmQgaW5kaWNhdGUNCiAgIHJlcXVpcmVtZW50IGxldmVs
cyBmb3IgY29tcGxpYW50IG1lY2hhbmlzbXMuDQoNCjIuICBJbnRyb2R1Y3Rpb24NCg0KICAgU2Vz
c2lvbiByZWNvcmRpbmcgaXMgYSBjcml0aWNhbCBvcGVyYXRpb25hbCByZXF1aXJlbWVudCBpbiBt
YW55DQogICBidXNpbmVzc2VzLCBlc3BlY2lhbGx5IHdoZXJlIHZvaWNlIGlzIHVzZWQgYXMgYSBt
ZWRpdW0gZm9yIGNvbW1lcmNlDQogICBhbmQgY3VzdG9tZXIgc3VwcG9ydC4gIEEgcHJpbWUgZXhh
bXBsZSB3aGVyZSB2b2ljZSBpcyB1c2VkIGZvciB0cmFkZQ0KICAgaXMgdGhlIGZpbmFuY2lhbCBp
bmR1c3RyeS4gIFRoZSBjYWxsIHJlY29yZGluZyByZXF1aXJlbWVudHMgaW4gdGhpcw0KICAgaW5k
dXN0cnkgYXJlIHF1aXRlIHN0cmluZ2VudC4gIFRoZSByZWNvcmRlZCBjYWxscyBhcmUgdXNlZCBm
b3INCiAgIGRpc3B1dGUgcmVzb2x1dGlvbiBhbmQgY29tcGxpYW5jZS4gIE90aGVyIGJ1c2luZXNz
ZXMgc3VjaCBhcyBjdXN0b21lcg0KICAgc3VwcG9ydCBjYWxsIGNlbnRlcnMgdHlwaWNhbGx5IGVt
cGxveSBjYWxsIHJlY29yZGluZyBmb3IgcXVhbGl0eQ0KICAgY29udHJvbCBvciBidXNpbmVzcyBh
bmFseXRpY3MsIHdpdGggZGlmZmVyZW50IHJlcXVpcmVtZW50cy4NCg0KICAgRGVwZW5kaW5nIG9u
IHRoZSBjb3VudHJ5IGFuZCBpdHMgcmVndWxhdG9yeSByZXF1aXJlbWVudHMsIGZpbmFuY2lhbA0K
ICAgdHJhZGluZyBmbG9vcnMgdHlwaWNhbGx5IG11c3QgcmVjb3JkIGFsbCBjYWxscy4gIEluIGNv
bnRyYXN0LCBjYWxsDQogICBjZW50ZXJzIHR5cGljYWxseSBvbmx5IHJlY29yZCBhIHN1YnNldCBv
ZiB0aGUgY2FsbHMsIGFuZCBjYWxscyBtdXN0DQogICBub3QgZmFpbCByZWdhcmRsZXNzIG9mIHRo
ZSBhdmFpbGFiaWxpdHkgb2YgdGhlIHJlY29yZGluZyBkZXZpY2UuDQoNCiAgIFJlc3BlY3Rpbmcg
dGhlIHByaXZhY3kgcmlnaHRzIGFuZCB3aXNoZXMgb2YgdXNlcnMgZW5nYWdlZCBpbiBhIGNhbGwN
CiAgIGlzIG9mIHBhcmFtb3VudCBpbXBvcnRhbmNlLiAgSW4gbWFueSBqdXJpc2RpY3Rpb25zIHBh
cnRpY2lwYW50cyBoYXZlDQogICBhIHJpZ2h0IHRvIGtub3cgdGhhdCB0aGUgc2Vzc2lvbiBpcyBi
ZWluZyByZWNvcmRlZCBvciBtaWdodCBiZQ0KICAgcmVjb3JkZWQsIGFuZCBoYXZlIGEgcmlnaHQg
dG8gb3B0IG91dCwgZWl0aGVyIGJ5IHRlcm1pbmF0aW5nIHRoZSBjYWxsDQogICBvciBieSBkZW1h
bmRpbmcgdGhhdCB0aGUgY2FsbCBub3QgYmUgcmVjb3JkZWQuICBUaGVyZWZvcmUgdGhpcw0KICAg
ZG9jdW1lbnQgY29udGFpbnMgcmVxdWlyZW1lbnRzIGZvciBiZWluZyBhYmxlIHRvIG5vdGlmeSB1
c2VycyB0aGF0IGENCiAgIGNhbGwgaXMgYmVpbmcgcmVjb3JkZWQgYW5kIGZvciB1c2VycyB0byBi
ZSBhYmxlIHRvIHJlcXVlc3QgdGhhdCBhDQogICBjYWxsIG5vdCBiZSByZWNvcmRlZC4gIFVzZSBj
YXNlcyB3aGVyZSB1c2VycyBwYXJ0aWNpcGF0aW5nIGluIGEgY2FsbA0KICAgYXJlIG5vdCBpbmZv
cm1lZCB0aGF0IHRoZSBjYWxsIGlzIG9yIG1pZ2h0IGJlIHJlY29yZGVkIGFyZSBvdXRzaWRlDQog
ICB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudC4gIEluIHBhcnRpY3VsYXIsIGxhd2Z1bCBpbnRl
cmNlcHQgaXMNCiAgIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQuDQoNCiAgIEZ1
cnRoZXJtb3JlLCB0aGUgc2NhbGUgYW5kIGNvc3QgYnVyZGVucyB2YXJ5IHdpZGVseSwgaW4gYWxs
IG1hcmtldHMsDQogICB3aGVyZSB0aGUgZGlmZmVyZW50IG5lZWRzIGZvciBzb2x1dGlvbiBjYXBh
YmlsaXRpZXMgc3VjaCBhcyBtZWRpYQ0KICAgaW5qZWN0aW9uLCB0cmFuc2NvZGluZywgYW5kIHNl
Y3VyaXR5LXJlbGF0ZWQgbmVlZHMgZG8gbm90IGNvbmZvcm0NCiAgIHdlbGwgdG8gYSBvbmUtc2l6
ZS1maXRzLWFsbCBtb2RlbC4gIElmIGEgc3RhbmRhcmRpemVkIHNvbHV0aW9uDQogICBzdXBwb3J0
cyBhbGwgb2YgdGhlIHJlcXVpcmVtZW50cyBmcm9tIGV2ZXJ5IHJlY29yZGluZyBtYXJrZXQsIGJ1
dA0KICAgZG9pbmcgc28gd291bGQgYmUgZXhwZW5zaXZlIGZvciBtYXJrZXRzIHdpdGggbGVzc2Vy
IG5lZWRzLCB0aGVuDQogICBwcm9wcmlldGFyeSBzb2x1dGlvbnMgZm9yIHRob3NlIG1hcmtldHMg
d2lsbCBjb250aW51ZSB0byBwcm9wYWdhdGUuDQogICBDYXJlIG11c3QgYmUgdGFrZW4sIHRoZXJl
Zm9yZSwgdG8gbWFrZSBhIHN0YW5kYXJkcy1iYXNlZCBzb2x1dGlvbg0KICAgc3VwcG9ydCBvcHRp
b25hbGl0eSBhbmQgZmxleGliaWxpdHkuDQoNCiAgIFRoaXMgZG9jdW1lbnQgc3BlY2lmaWVzIHJl
cXVpcmVtZW50cyBmb3IgdXNpbmcgU0lQIFtSRkMzMjYxXSBiZXR3ZWVuDQogICBhIFNlc3Npb24g
UmVjb3JkaW5nIENsaWVudCBhbmQgYSBTZXNzaW9uIFJlY29yZGluZyBTZXJ2ZXIgdG8gY29udHJv
bA0KICAgdGhlIHJlY29yZGluZyBvZiBtZWRpYSB0aGF0IGhhcyBiZWVuIHRyYW5zbWl0dGVkIGlu
IHRoZSBjb250ZXh0IG9mIGENCiAgIENvbW11bmljYXRpb24gU2Vzc2lvbi4gIEEgQ29tbXVuaWNh
dGlvbiBTZXNzaW9uIGlzIHRoZSAiY2FsbCIgYmV0d2Vlbg0KICAgcGFydGljaXBhbnRzLiAgVGhl
IFNlc3Npb24gUmVjb3JkaW5nIENsaWVudCBpcyB0aGUgc291cmNlIG9mIHRoZQ0KICAgcmVjb3Jk
ZWQgbWVkaWEuICBUaGUgU2Vzc2lvbiBSZWNvcmRpbmcgU2VydmVyIGlzIHRoZSBzaW5rIG9mIHJl
Y29yZGVkDQogICBtZWRpYS4gIEl0IHNob3VsZCBiZSBub3RlZCB0aGF0IHRoZSByZXF1aXJlbWVu
dHMgZm9yIHRoZSBwcm90b2NvbA0KICAgYmV0d2VlbiBhIFNlc3Npb24gUmVjb3JkaW5nIFNlcnZl
ciBhbmQgU2Vzc2lvbiBSZWNvcmRpbmcgQ2xpZW50IGhhdmUNCiAgIHZlcnkgc2ltaWxhciByZXF1
aXJlbWVudHMgKHN1Y2ggYXMgY29kZWMgYW5kIHRyYW5zcG9ydCBuZWdvdGlhdGlvbiwNCiAgIGVu
Y3J5cHRpb24ga2V5IGludGVyY2hhbmdlLCBmaXJld2FsbCB0cmF2ZXJzYWwpIGFzIGNvbXBhcmVk
IHRvDQogICByZWd1bGFyIFNJUCBtZWRpYSBzZXNzaW9ucy4gIFRoZSBjaG9pY2Ugb2YgU0lQIGZv
ciBzZXNzaW9uIHJlY29yZGluZw0KICAgcHJvdmlkZXMgcmV1c2Ugb2YgYW4gZXhpc3RpbmcgcHJv
dG9jb2wuDQoNCiAgIFRoZSByZWNvcmRlZCBzZXNzaW9ucyBjYW4gYmUgYW55IFJUUCBtZWRpYSBz
ZXNzaW9ucyBpbmNsdWRpbmcgdm9pY2UsDQogICBEVE1GIChhcyBkZWZpbmVkIGJ5IFtSRkM0NzMz
XSksIHZpZGVvLCBhbmQgdGV4dCAoYXMgZGVmaW5lZCBieQ0KICAgW1JGQzQxMDNdKS4NCg0KICAg
QW4gYXJjaGl2ZWQgc2Vzc2lvbiByZWNvcmRpbmcgaXMgdHlwaWNhbGx5IGNvbXByaXNlZCBvZiB0
aGUNCiAgIENvbW11bmljYXRpb24gU2Vzc2lvbiBtZWRpYSBjb250ZW50IGFuZCB0aGUgQ29tbXVu
aWNhdGlvbiBTZXNzaW9uDQogICBNZXRhZGF0YS4gIFRoZSBDb21tdW5pY2F0aW9uIFNlc3Npb24g
TWV0YWRhdGEgYWxsb3dzIHJlY29yZGluZw0KICAgYXJjaGl2ZXMgdG8gYmUgc2VhcmNoZWQgYW5k
IGZpbHRlcmVkIGF0IGEgbGF0ZXIgdGltZSBhbmQgYWxsb3dzIGENCiAgIHNlc3Npb24gdG8gYmUg
cGxheWVkIGJhY2sgaW4gYSBtZWFuaW5nZnVsIHdheSwgZS5nLiwgd2l0aCBjb3JyZWN0DQogICBz
eW5jaHJvbml6YXRpb24gYmV0d2VlbiB0aGUgbWVkaWEuICBUaGUgQ29tbXVuaWNhdGlvbiBTZXNz
aW9uDQogICBNZXRhZGF0YSBuZWVkcyB0byBiZSBjb252ZXllZCBmcm9tIHRoZSBTZXNzaW9uIFJl
Y29yZGluZyBDbGllbnQgdG8NCiAgIHRoZSBTZXNzaW9uIFJlY29yZGluZyBTZXJ2ZXIuDQoNCiAg
IFRoaXMgZG9jdW1lbnQgb25seSBjb25zaWRlcnMgYWN0aXZlIHJlY29yZGluZywgd2hlcmUgdGhl
IFNlc3Npb24NCiAgIFJlY29yZGluZyBDbGllbnQgcHVycG9zZWZ1bGx5IHN0cmVhbXMgbWVkaWEg
dG8gYSBTZXNzaW9uIFJlY29yZGluZw0KICAgU2VydmVyLiAgUGFzc2l2ZSByZWNvcmRpbmcsIHdo
ZXJlIGEgcmVjb3JkaW5nIGRldmljZSBkZXRlY3RzIG1lZGlhDQogICBkaXJlY3RseSBmcm9tIHRo
ZSBuZXR3b3JrLCBpcyBvdXRzaWRlIHRoZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50Lg0KDQozLiAg
RGVmaW5pdGlvbnMNCg0KICAgU2Vzc2lvbiBSZWNvcmRpbmcgU2VydmVyIChTUlMpOiBBIFNlc3Np
b24gUmVjb3JkaW5nIFNlcnZlciAoU1JTKSBpcyBhDQogICBTSVAgVXNlciBBZ2VudCAoVUEpIHRo
YXQgaXMgYSBzcGVjaWFsaXplZCBtZWRpYSBzZXJ2ZXIgb3IgY29sbGVjdG9yDQogICB0aGF0IGFj
dHMgYXMgdGhlIHNpbmsgb2YgdGhlIHJlY29yZGVkIG1lZGlhLiAgQW4gU1JTIGlzIHR5cGljYWxs
eQ0KICAgaW1wbGVtZW50ZWQgYXMgYSBtdWx0aS1wb3J0IGRldmljZSB0aGF0IGlzIGNhcGFibGUg
b2YgcmVjZWl2aW5nIG1lZGlhDQogICBmcm9tIG11bHRpcGxlIHNvdXJjZXMgc2ltdWx0YW5lb3Vz
bHkuICBBbiBTUlMgaXMgdGhlIHNpbmsgb2YgdGhlDQogICByZWNvcmRlZCBzZXNzaW9uIG1ldGFk
YXRhLg0KDQogICBTZXNzaW9uIFJlY29yZGluZyBDbGllbnQgKFNSQyk6IEEgU2Vzc2lvbiBSZWNv
cmRpbmcgQ2xpZW50IChTUkMpIGlzIGENCiAgIFNJUCBVc2VyIEFnZW50IChVQSkgdGhhdCBhY3Rz
IGFzIHRoZSBzb3VyY2Ugb2YgdGhlIHJlY29yZGVkIG1lZGlhLA0KICAgc2VuZGluZyBpdCB0byB0
aGUgU1JTLiAgQW4gU1JDIGlzIGEgbG9naWNhbCBmdW5jdGlvbi4gIEl0cw0KICAgY2FwYWJpbGl0
aWVzIG1heSBiZSBpbXBsZW1lbnRlZCBhY3Jvc3Mgb25lIG9yIG1vcmUgcGh5c2ljYWwgZGV2aWNl
cy4NCiAgIEluIHByYWN0aWNlLCBhbiBTUkMgY291bGQgYmUgYSBwZXJzb25hbCBkZXZpY2UgKHN1
Y2ggYXMgYSBTSVAgcGhvbmUpLA0KICAgYSBTSVAgTWVkaWEgR2F0ZXdheSAoTUcpLCBhIFNlc3Np
b24gQm9yZGVyIENvbnRyb2xsZXIgKFNCQykgb3IgYSBTSVANCiAgIE1lZGlhIFNlcnZlciAoTVMp
IGludGVncmF0ZWQgd2l0aCBhbiBBcHBsaWNhdGlvbiBTZXJ2ZXIgKEFTKS4gIFRoaXMNCiAgIHNw
ZWNpZmljYXRpb24gZGVmaW5lcyB0aGUgdGVybSBTUkMgc3VjaCB0aGF0IGFsbCBzdWNoIFNJUCBl
bnRpdGllcw0KICAgY2FuIGJlIGdlbmVyaWNhbGx5IGFkZHJlc3NlZCB1bmRlciBvbmUgZGVmaW5p
dGlvbi4gIFRoZSBTUkMgcHJvdmlkZXMNCiAgIG1ldGFkYXRhIHRvIHRoZSBTUlMuDQoNCiAgIENv
bW11bmljYXRpb24gU2Vzc2lvbiAoQ1MpOiBBIHNlc3Npb24gY3JlYXRlZCBiZXR3ZWVuIHR3byBv
ciBtb3JlIFNJUA0KICAgVXNlciBBZ2VudHMgKFVBcykgdGhhdCBpcyB0aGUgc3ViamVjdCBvZiBy
ZWNvcmRpbmcuDQoNCiAgIFJlY29yZGluZyBTZXNzaW9uIChSUyk6IFRoZSBTSVAgc2Vzc2lvbiBj
cmVhdGVkIGJldHdlZW4gYW4gU1JDIGFuZA0KICAgU1JTIGZvciB0aGUgcHVycG9zZSBvZiByZWNv
cmRpbmcgYSBDb21tdW5pY2F0aW9uIFNlc3Npb24uDQoNCiAgIEZpZ3VyZSAxIHBpY3RvcmlhbGx5
IHJlcHJlc2VudHMgdGhlIHJlbGF0aW9uc2hpcCBiZXR3ZWVuIGEgUmVjb3JkaW5nDQogICBTZXNz
aW9uIGFuZCBDb21tdW5pY2F0aW9uIFNlc3Npb24uDQoNCiAgICAgKy0tLS0tLS0tLS0tLS0rICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0rDQogICAgIHwg
ICAgICAgICAgICAgfCAgICAgICAgQ29tbXVuaWNhdGlvbiBTZXNzaW9uICAgICAgICAgfCAgICAg
ICAgICAgfA0KICAgICB8ICAgICBBICAgICAgIHwmbHQ7LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tJmd0O3wgICAgIEIgICAgIHwNCiAgICAgfCAgICAgICAgICAgICB8ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICB8DQogICAgICstLS0t
LS0tLS0tLS0tKyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0t
LS0tKw0KICAgICAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4NCiAgICAgLiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
U2Vzc2lvbiAgICAgICAgICAgICAgICAgICAgICAgICAgICAuDQogICAgIC4gICAgICAgICAgICAg
ICAgICAgICAgICAgICAgUmVjb3JkaW5nICAgICAgICAgICAgICAgICAgICAgICAgICAgLg0KICAg
ICAuICAgICAgICAgICAgICAgICAgICAgICAgICAgICBDbGllbnQgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIC4NCiAgICAgLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uDQogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBSZWNv
cmRpbmcNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBTZXNzaW9uDQog
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgdg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICst
LS0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgIFNlc3Npb24g
IHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICBSZWNvcmRpbmcgfA0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIHwgICBTZXJ2ZXIgICB8DQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLSsNCg0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgRmlndXJlIDENCg0KICAgTWV0YWRhdGE6IEluZm9ybWF0aW9uIHRoYXQgZGVzY3Jp
YmVzIHJlY29yZGVkIG1lZGlhIGFuZCB0aGUgQ1MgdG8NCiAgIHdoaWNoIHRoZXkgcmVsYXRlLg0K
DQogICBQYXVzZSBhbmQgUmVzdW1lIGR1cmluZyBhIENvbW11bmljYXRpb24gU2Vzc2lvbjogUGF1
c2U6IFRoZSBhY3Rpb24gb2YNCiAgIHRlbXBvcmFyaWx5IGRpc2NvbnRpbnVpbmcgdGhlIHRyYW5z
bWlzc2lvbiBhbmQgY29sbGVjdGlvbiBvZiBSUyBtZWRpYQ0KICAgUmVzdW1lOiBUaGUgYWN0aW9u
IG9mIHJlY29tbWVuY2luZyB0aGUgdHJhbnNtaXNzaW9uIGFuZCBjb2xsZWN0aW9uIG9mDQogICBS
UyBtZWRpYQ0KDQo0LiAgVXNlIENhc2VzDQoNCiAgIFVzZSBDYXNlIDE6IEZ1bGwtdGltZSBSZWNv
cmRpbmc6IE9uZSBSZWNvcmRpbmcgU2Vzc2lvbiBmb3IgZWFjaA0KICAgQ29tbXVuaWNhdGlvbiBT
ZXNzaW9uLg0KDQogICBGb3IgZXhhbXBsZSwgdGhlIGRpYWdyYW0gYmVsb3cgc2hvd3MgdGhlIGxp
ZmVjeWNsZSBvZiBDb21tdW5pY2F0aW9uDQogICBTZXNzaW9ucyAoQ1MpIGFuZCB0aGUgcmVsYXRp
b25zaGlwIHRvIHRoZSBSZWNvcmRpbmcgU2Vzc2lvbnMgKFJTKQ0KDQogICBDUyAgfC0tLSBDUyAx
IC0tLXwgICAgICB8LS0tIENTIDIgLS0tfCAgICAgfC0tLSBDUyAzIC0tLXwNCg0KICAgUlMgIHwt
LS0gUlMgMSAtLS18ICAgICAgfC0tLSBSUyAyIC0tLXwgICAgIHwtLS0gUlMgMyAtLS18DQoNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEZpZ3VyZSAyDQoNCiAgIFJlY29yZCBldmVy
eSBDUyBmb3Igc3BlY2lmaWMgZXh0ZW5zaW9uL3BlcnNvbi4NCg0KICAgVGhlIG5lZWQgdG8gcmVj
b3JkIGFsbCBjYWxscyBpcyB0eXBpY2FsbHkgZHVlIHRvIGJ1c2luZXNzIHByb2Nlc3MNCiAgIHB1
cnBvc2VzIChzdWNoIGFzIHRyYW5zYWN0aW9uIGNvbmZpcm1hdGlvbiBvciBkaXNwdXRlIHJlc29s
dXRpb24pIG9yDQogICB0byBlbnN1cmUgY29tcGxpYW5jZSB3aXRoIGdvdmVybm1lbnRhbCByZWd1
bGF0aW9ucy4gIEFwcGxpY2F0aW9ucw0KICAgaW5jbHVkZSBlbnRlcnByaXNlLCBjb250YWN0IGNl
bnRlciwgYW5kIGZpbmFuY2lhbCB0cmFkaW5nIGZsb29ycy4NCg0KICAgQWxzbyBjb21tb25seSBr
bm93biBhcyBUb3RhbCBSZWNvcmRpbmcuDQoNCiAgIFVzZSBDYXNlIDI6IFNlbGVjdGl2ZSBSZWNv
cmRpbmc6IFN0YXJ0IGEgUmVjb3JkaW5nIFNlc3Npb24gd2hlbiBhDQogICBDb21tdW5pY2F0aW9u
IFNlc3Npb24gdG8gYmUgcmVjb3JkZWQgaXMgZXN0YWJsaXNoZWQuDQoNCiAgIEluIHRoaXMgZXhh
bXBsZSwgQ29tbXVuaWNhdGlvbiBTZXNzaW9ucyAxIGFuZCAzIGFyZSByZWNvcmRlZCBidXQgQ1Mg
Mg0KICAgaXMgbm90Lg0KDQogICBDUyAgfC0tLSBDUyAxIC0tLXwgICAgICB8LS0tIENTIDIgLS0t
fCAgICAgfC0tLSBDUyAzIC0tLXwNCg0KICAgUlMgIHwtLS0gUlMgMS0tLS18ICAgICAgICAgICAg
ICAgICAgICAgICAgIHwtLS0gUlMgMiAtLS18DQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIEZpZ3VyZSAzDQoNCiAgIFVzZSBDYXNlIDM6IFN0YXJ0L1N0b3AgYSBSZWNvcmRpbmcg
U2Vzc2lvbiBkdXJpbmcgYSBDb21tdW5pY2F0aW9uDQogICBTZXNzaW9uLg0KDQogICBUaGUgUmVj
b3JkaW5nIFNlc3Npb24gc3RhcnRzIGR1cmluZyBhIENvbW11bmljYXRpb24gU2Vzc2lvbiwgZWl0
aGVyDQogICBtYW51YWxseSB2aWEgYSB1c2VyLWNvbnRyb2xsZWQgbWVjaGFuaXNtIChlLmcuIGJ1
dHRvbiBvbiB1c2VyJ3MNCiAgIHBob25lKSBvciBhdXRvbWF0aWNhbGx5IHZpYSBhbiBhcHBsaWNh
dGlvbiAoZS5nLiBhIENvbnRhY3QgQ2VudGVyDQogICBjdXN0b21lciBzZXJ2aWNlIGFwcGxpY2F0
aW9uKSBvciBidXNpbmVzcyBldmVudC4gIEEgUmVjb3JkaW5nIFNlc3Npb24NCiAgIGVpdGhlciBl
bmRzIGR1cmluZyB0aGUgQ29tbXVuaWNhdGlvbiBTZXNzaW9uLCBvciB3aGVuIHRoZQ0KICAgQ29t
bXVuaWNhdGlvbiBTZXNzaW9uIGVuZHMuICBPbmUgb3IgbW9yZSBSZWNvcmRpbmcgU2Vzc2lvbnMg
bWF5DQogICByZWNvcmQgZWFjaCBDb21tdW5pY2F0aW9uIFNlc3Npb24uDQoNCiAgIENTICB8LS0t
LS0tLS0tLS0tLSBDb21tdW5pY2F0aW9uIFNlc3Npb24gLS0tLS0tLS0tLS18DQoNCiAgIFJTICAg
ICAgICAgICB8LS0tLSBSUyAxIC0tLS18ICB8LS0tLSBSUyAyIC0tLS0tfA0KDQogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICBGaWd1cmUgNA0KDQogICBVc2UgQ2FzZSA0OiBQZXJzaXN0
ZW50IFJlY29yZGluZzogQSBzaW5nbGUgUmVjb3JkaW5nIFNlc3Npb24gY2FwdHVyZXMNCiAgIG9u
ZSBvciBtb3JlIENvbW11bmljYXRpb24gU2Vzc2lvbnMuDQoNCiAgICAgICAgICAgICB8LS0tIENT
IDEgLS0tfCAgICAgIHwtLS0gQ1MgMiAtLS18ICAgICB8LS0tIENTIDMgLS0tfA0KDQogICBSUyAg
fC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gUmVjb3JkaW5nIFNlc3Npb24gLS0tLS0tLS0tLS0tLS0t
LS0tLS0tfA0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBGaWd1cmUgNQ0KDQog
ICBBIFJlY29yZGluZyBTZXNzaW9uIHJlY29yZHMgY29udGludW91c2x5IHdpdGhvdXQgaW50ZXJy
dXB0aW9uLg0KICAgUGVyaW9kcyB3aGVuIHRoZXJlIGlzIG5vIENTIGluIHByb2dyZXNzIG11c3Qg
YmUgcmVwcm9kdWNlZCB1cG9uDQogICBwbGF5YmFjayAoZS5nLiBieSByZWNvcmRpbmcgc2lsZW5j
ZSBkdXJpbmcgc3VjaCBwZXJpb2RzIG9yIGJ5IG5vdA0KICAgcmVjb3JkaW5nIHN1Y2ggcGVyaW9k
cyBidXQgbWFya2luZyB0aGVtIGJ5IG1lYW5zIG9mIG1ldGFkYXRhIGZvcg0KICAgdXRpbGl6YXRp
b24gb24gcGxheWJhY2ssIGV0Yy4pLiAgQXBwbGljYXRpb25zIGluY2x1ZGUgZmluYW5jaWFsDQog
ICB0cmFkaW5nIGRlc2tzIGFuZCBlbWVyZ2VuY3kgKGZpcnN0LXJlc3BvbmRlcikgc2VydmljZSBi
dXJlYXVzLiAgVGhlDQogICBsZW5ndGggb2YgYSBQZXJzaXN0ZW50IFJlY29yZGluZyBTZXNzaW9u
IGlzIGluZGVwZW5kZW50IGZyb20gdGhlDQogICBsZW5ndGggb2YgdGhlIGFjdHVhbCBDb21tdW5p
Y2F0aW9uIFNlc3Npb25zLiAgUGVyc2lzdGVudCBSZWNvcmRpbmcNCiAgIFNlc3Npb25zIGF2b2lk
IGlzc3VlcyBzdWNoIGFzIG1lZGlhIGNsaXBwaW5nIHRoYXQgY2FuIG9jY3VyIGR1ZSB0bw0KICAg
ZGVsYXlzIGluIFJlY29yZGluZyBTZXNzaW9uIGVzdGFibGlzaG1lbnQuDQoNCiAgIFRoZSBjb25u
ZWN0aW9uIGFuZCBhdHRyaWJ1dGVzIG9mIG1lZGlhIGluIHRoZSBSZWNvcmRpbmcgU2Vzc2lvbiBh
cmUNCiAgIG5vdCBkeW5hbWljYWxseSBzaWduYWxlZCBmb3IgZWFjaCBDb21tdW5pY2F0aW9uIFNl
c3Npb24gYmVmb3JlIGl0IGNhbg0KICAgYmUgcmVjb3JkZWQ7IGhvd2V2ZXIsIGNvZGVjIHJlLW5l
Z290aWF0aW9uIGlzIHBvc3NpYmxlLg0KDQogICBJbiBzb21lIGNhc2VzLCBtb3JlIHRoYW4gb25l
IGNvbmN1cnJlbnQgQ29tbXVuaWNhdGlvbiBTZXNzaW9uIChvbiBhDQogICBzaW5nbGUgZW5kLXVz
ZXIgYXBwYXJhdHVzLCBlLmcuIHRyYWRpbmcgZmxvb3IgdHVycmV0KSBpcyBtaXhlZCBpbnRvDQog
ICBvbmUgUmVjb3JkaW5nIFNlc3Npb246DQoNCiAgICAgICAgICAgICAgICAgfC0tLS0tLS0tIENT
IDEgLS0tLS0tLXwNCiAgICAgICAgICAgICAgICAgICAgfC0tLS0tLS0tIENTIDIgLS0tLS0tLXwN
CiAgICAgICAgICAgICAgIHwtLS0tLS0tLSBDUyAzIC0tLS0tLS18DQoNCiAgIFJTICB8LS0tLS0t
LS0tLS0gUmVjb3JkaW5nIFNlc3Npb24gLS0tLS0tLS0tLS0tLS18DQoNCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIEZpZ3VyZSA2DQoNCiAgIFVzZSBDYXNlIDU6IFJlYWwtdGltZSBS
ZWNvcmRpbmcgQ29udHJvbHMuDQoNCiAgIEZvciBhbiBhY3RpdmUgUmVjb3JkaW5nIFNlc3Npb24s
IHByaXZhY3kgb3Igc2VjdXJpdHkgcmVhc29ucyBtYXkNCiAgIGRlbWFuZCBub3QgY2FwdHVyaW5n
IGEgc3BlY2lmaWMgcG9ydGlvbiBvZiBhIGNvbnZlcnNhdGlvbi4gIEFuDQogICBleGFtcGxlIGlz
IGZvciBQQ0kgKHBheW1lbnQgY2FyZCBpbmR1c3RyeSkgY29tcGxpYW5jZSB3aGVyZSBjcmVkaXQN
CiAgIGNhcmQgaW5mbyBtdXN0IGJlIHByb3RlY3RlZC4gIE9uZSBzb2x1dGlvbiBpcyB0byBub3Qg
cmVjb3JkIGEgY2FsbGVyDQogICBzcGVha2luZyB0aGVpciBjcmVkaXQgY2FyZCBpbmZvcm1hdGlv
bi4NCg0KICAgQW4gZXhhbXBsZSBvZiBhIHJlYWwtdGltZSBjb250cm9scyBpcyBQYXVzZS9SZXN1
bWUuDQoNCiAgIFVzZSBDYXNlIDY6IElWUiAvIFZvaWNlIFBvcnRhbCBSZWNvcmRpbmcuDQoNCiAg
IFNlbGYtc2VydmljZSBJbnRlcmFjdGl2ZSBWb2ljZSBSZXNwb25zZSBhcHBsaWNhdGlvbnMgbWF5
IG5lZWQgdG8gYmUNCiAgIHJlY29yZGVkIGZvciBhcHBsaWNhdGlvbiBwZXJmb3JtYW5jZSB0dW5p
bmcgb3IgdG8gbWVldCBjb21wbGlhbmNlDQogICByZXF1aXJlbWVudHMuDQoNCiAgIE1ldGFkYXRh
IGFib3V0IGFuIElWUiBzZXNzaW9uIHJlY29yZGluZyBtdXN0IGluY2x1ZGUgc2Vzc2lvbg0KICAg
aW5mb3JtYXRpb24gYW5kIG1heSBpbmNsdWRlIGFwcGxpY2F0aW9uIGNvbnRleHQgaW5mb3JtYXRp
b24gKGUuZy4NCiAgIFZvaWNlWE1MIHNlc3Npb24gdmFyaWFibGVzLCBkaWFsb2cgbmFtZXMsIGV0
Yy4pDQoNCiAgIFVzZSBDYXNlIDc6IEVudGVycHJpc2UgTW9iaWxpdHkgUmVjb3JkaW5nLg0KDQog
ICBNYW55IGFnZW50cyBhbmQgZW50ZXJwcmlzZSB3b3JrZXJzIHdob3NlIGNhbGxzIGFyZSB0byBi
ZSByZWNvcmRlZCBhcmUNCiAgIG5vdCBsb2NhdGVkIG9uIGNvbXBhbnkgcHJlbWlzZXMuDQoNCiAg
IEV4YW1wbGVzOg0KDQogICBvIEhvbWUtYmFzZWQgYWdlbnRzIG9yIGVudGVycHJpc2Ugd29ya2Vy
cy4NCg0KICAgbyBNb2JpbGUgcGhvbmVzIG9mIGtub3dsZWRnZSB3b3JrZXJzIHdoZW4gdGhleSBj
b25kdWN0IHdvcmsgcmVsYXRlZA0KICAgKGFuZCBsZWdhbGx5IHJlcXVpcmVkIHJlY29yZGluZykg
Y2FsbHMuIGUuZy4gaW5zdXJhbmNlIGFnZW50cywNCiAgIGJyb2tlcnMsIHBoeXNpY2lhbnMuDQoN
CiAgIFVzZSBDYXNlIDg6IEdlb2dyYXBoaWNhbGx5IGRpc3RyaWJ1dGVkIG9yIGNlbnRyYWxpemVk
IHJlY29yZGluZy4NCg0KICAgRW50ZXJwcmlzZXMgc3VjaCBhcyBiYW5rcywgaW5zdXJhbmNlIGFn
ZW5jaWVzLCBhbmQgcmV0YWlsIHN0b3JlcyBtYXkNCiAgIGhhdmUgbWFueSBsb2NhdGlvbnMsIHBv
c3NpYmx5IHVwIHRvIHRob3VzYW5kcyBvZiBzbWFsbCBzaXRlcy4NCiAgIEZyZXF1ZW50bHkgb25s
eSBwaG9uZXMgYW5kIG5ldHdvcmsgaW5mcmFzdHJ1Y3R1cmUgYXJlIGluc3RhbGxlZCBpbg0KICAg
YnJhbmNoZXMsIHdpdGhvdXQgbG9jYWwgcmVjb3JkaW5nIHNlcnZpY2VzLiAgSW4gY2FzZXMgd2hl
cmUgY2FsbHMNCiAgIGluc2lkZSBvciBiZXR3ZWVuIGJyYW5jaGVzIG11c3QgYmUgcmVjb3JkZWQs
IGEgY2VudHJhbGl6ZWQgcmVjb3JkaW5nDQogICBzeXN0ZW0gaW4gZGF0YSBjZW50ZXJzIHRvZ2V0
aGVyIHdpdGggdGVsZXBob255IGluZnJhc3RydWN0dXJlIChlLmcuDQogICBQQlgpIG1lIGRlcGxv
eWVkLg0KDQogICBVc2UgQ2FzZSA5OiBSZWNvcmQgY29tcGxleCBjYWxsIHNjZW5hcmlvcy4NCg0K
ICAgVGhlIGZvbGxvd2luZyBpcyBhbiBleGFtcGxlIG9mIGEgc2NlbmFyaW8gd2hlcmUgb25lIGNh
bGwgdGhhdCBpcw0KICAgcmVjb3JkZWQgbXVzdCBiZSBhc3NvY2lhdGVkIHdpdGggYSByZWxhdGVk
IGNhbGwgdGhhdCBhbHNvIG11c3QgYmUNCiAgIHJlY29yZGVkLg0KDQogICBvIEEgQ3VzdG9tZXIg
aXMgaW4gYSBjb252ZXJzYXRpb24gd2l0aCBhIEN1c3RvbWVyIFNlcnZpY2UgQWdlbnQuDQoNCiAg
IG8gQWdlbnQgcHV0cyBDdXN0b21lciBvbiBob2xkIGluIG9yZGVyIHRvIGNvbnN1bHQgd2l0aCBh
IFN1cGVydmlzb3IuDQoNCiAgIG8gQWdlbnQgZW50ZXJzIGludG8gYSBjb252ZXJzYXRpb24gd2l0
aCBTdXBlcnZpc29yLg0KDQogICBvIEFnZW50IGRpc2Nvbm5lY3RzIGZyb20gU3VwZXJ2aXNvciwg
dGhlbiByZWNvbm5lY3RzIHdpdGggQ3VzdG9tZXIuDQoNCiAgIG8gVGhlIFN1cGVydmlzb3IgY2Fs
bCBtdXN0IGJlIGFzc29jaWF0ZWQgd2l0aCB0aGUgb3JpZ2luYWwgY3VzdG9tZXINCiAgIGNhbGwu
DQoNCiAgIFVzZSBjYXNlIDEwOiBIaWdoIGF2YWlsYWJpbGl0eSBhbmQgY29udGludW91cyByZWNv
cmRpbmcuDQoNCiAgIFNwZWNpZmljIGRlcGxveW1lbnQgc2NlbmFyaW9zIHByZXNlbnQgZGlmZmVy
ZW50IHJlcXVpcmVtZW50cyBmb3INCiAgIHN5c3RlbSBhdmFpbGFiaWxpdHksIGVycm9yIGhhbmRs
aW5nLCBldGMuIGluY2x1ZGluZzoNCg0KICAgbyBBbiBTUlMgbXVzdCBhbHdheXMgYmUgYXZhaWxh
YmxlIGF0IGNhbGwgc2V0dXAgdGltZS4NCg0KICAgbyBObyBsb3NzIG9mIG1lZGlhIHJlY29yZGlu
ZywgaW5jbHVkaW5nIGR1cmluZyBmYWlsdXJlIG9mIGFuIFNSUy4NCg0KICAgbyBUaGUgQ29tbXVu
aWNhdGlvbiBTZXNzaW9uIG11c3QgYmUgdGVybWluYXRlZCAob3Igc3VpdGFibGUNCiAgIG5vdGlm
aWNhdGlvbiBnaXZlbiB0byBwYXJ0aWVzKSBpbiB0aGUgZXZlbnQgb2YgYSByZWNvcmRpbmcgZmFp
bHVyZS4NCg0KICAgVXNlIENhc2UgMTE6IFJlY29yZCBtdWx0aS1jaGFubmVsLCBtdWx0aS1tZWRp
YSBzZXNzaW9uLg0KDQogICBTb21lIGFwcGxpY2F0aW9ucyByZXF1aXJlIHRoZSByZWNvcmRpbmcg
b2YgbW9yZSB0aGFuIG9uZSBtZWRpYQ0KICAgc3RyZWFtLCBwb3NzaWJseSBvZiBkaWZmZXJlbnQg
dHlwZXMuICBNZWRpYSBhcmUgc3luY2hyb25pemVkLCBlaXRoZXINCiAgIGF0IHN0b3JhZ2Ugb3Ig
YXQgcGxheWJhY2suDQoNCiAgIFNwZWVjaCBhbmFseXRpY3MgdGVjaG5vbG9naWVzIChlLmcuIHdv
cmQgc3BvdHRpbmcsIGVtb3Rpb24gZGV0ZWN0aW9uLA0KICAgc3BlYWtlciBpZGVudGlmaWNhdGlv
bikgbWF5IHJlcXVpcmUgc3BlYWtlci1zZXBhcmF0ZWQgcmVjb3JkaW5ncyBmb3INCiAgIG9wdGlt
dW0gcGVyZm9ybWFuY2UuDQoNCiAgIE11bHRpLW1vZGFsIENvbnRhY3QgQ2VudGVycyBtYXkgaW5j
bHVkZSBhdWRpbywgdmlkZW8sIElNIG9yIG90aGVyDQogICBpbnRlcmFjdGlvbiBtb2RhbGl0aWVz
Lg0KDQogICBJbiB0cmFkaW5nIGZsb29ycyBlbnZpcm9ubWVudHMsIGluIG9yZGVyIHRvIG1pbmlt
aXplIHN0b3JhZ2UgYW5kDQogICByZWNvcmRpbmcgc3lzdGVtIHJlc291cmNlcywgaXQgbWF5IGJl
IHByZWZlcmFibGUgdG8gbWl4IG11bHRpcGxlDQogICBjb25jdXJyZW50IGNhbGxzIChDb21tdW5p
Y2F0aW9uIFNlc3Npb25zKSBvbiBkaWZmZXJlbnQgaGFuZHNldHMvDQogICBzcGVha2VycyBvbiB0
aGUgc2FtZSB0dXJyZXQgaW50byBzaW5nbGUgcmVjb3JkaW5nIHNlc3Npb24uDQoNCiAgIFVzZSBD
YXNlIDEyOiBSZWFsLXRpbWUgbWVkaWEgcHJvY2Vzc2luZy4NCg0KICAgSXQgbXVzdCBiZSBwb3Nz
aWJsZSBmb3IgYW4gU1JTIHRvIHN1cHBvcnQgcmVhbC10aW1lIG1lZGlhIHByb2Nlc3NpbmcsDQog
ICBzdWNoIGFzIHNwZWVjaCBhbmFseXRpY3Mgb2YgdHJhZGluZyBmbG9vciBpbnRlcmFjdGlvbnMu
ICA8c3RyaWtlPjxmb250IGNvbG9yPSJyZWQiPlJhbC10aW1lPC9mb250Pjwvc3RyaWtlPiAgPHN0
cm9uZz48Zm9udCBjb2xvcj0iZ3JlZW4iPlJlYWwtdGltZTwvZm9udD48L3N0cm9uZz4NCiAgIGFu
YWx5dGljcyBtYXkgYmUgZW1wbG95ZWQgZm9yIGF1dG9tYXRpYyBpbnRlcnZlbnRpb24gKHN0b3Bw
aW5nDQogICBpbnRlcmFjdGlvbiBvciBhbGVydGluZykgaWYgZm9yIGV4YW1wbGUsIGEgdHJhZGVy
IGlzIG5vdCBmb2xsb3dpbmcNCiAgIHJlZ3VsYXRpb25zLg0KDQogICBTcGVha2VyIHNlcGFyYXRp
b24gaXMgcmVxdWlyZWQgaW4gb3JkZXIgdG8gcmVsaWFibHkgZGV0ZWN0IHdobyBpcw0KICAgc2F5
aW5nIHNwZWNpZmljIHBocmFzZXMuDQoNCjUuICBSZXF1aXJlbWVudHMNCg0KICAgVGhlIGZvbGxv
d2luZyBhcmUgcmVxdWlyZW1lbnRzIGZvciBTSVAtYmFzZWQgTWVkaWEgUmVjb3JkaW5nOg0KDQog
ICBvIFJFUS0wMDEgVGhlIG1lY2hhbmlzbSBNVVNUIHByb3ZpZGUgYSBtZWFucyBmb3IgPHN0cmlr
ZT48Zm9udCBjb2xvcj0icmVkIj4idXNpbmc8L2ZvbnQ+PC9zdHJpa2U+IDxzdHJvbmc+PGZvbnQg
Y29sb3I9ImdyZWVuIj51c2luZzwvZm9udD48L3N0cm9uZz4gdGhlIFNJUA0KICAgcHJvdG9jb2wg
PHN0cmlrZT48Zm9udCBjb2xvcj0icmVkIj5mb3IiPC9mb250Pjwvc3RyaWtlPiA8c3Ryb25nPjxm
b250IGNvbG9yPSJncmVlbiI+Zm9yPC9mb250Pjwvc3Ryb25nPiBlc3RhYmxpc2hpbmcsIG1haW50
YWluaW5nIGFuZCB0ZXJtaW5hdGluZyBSZWNvcmRpbmcNCiAgIFNlc3Npb25zIGJldHdlZW4gYSBT
ZXNzaW9uIFJlY29yZGluZyBDbGllbnQgYW5kIGEgU2Vzc2lvbiBSZWNvcmRpbmcNCiAgIFNlcnZl
ci4NCg0KICAgbyBSRVEtMDAyIFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5
IHRvIHJlY29yZCBhbGwgQ1NzIGluDQogICB0aGVpciBlbnRpcmV0eS4NCg0KICAgbyBSRVEtMDAz
IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5IHRvIHJlY29yZCBzZWxlY3Rl
ZA0KICAgQ1NzIGluIHRoZWlyIGVudGlyZXR5LCBhY2NvcmRpbmcgdG8gcG9saWN5Lg0KDQogICBv
IFJFUS0wMDQgVGhlIG1lY2hhbmlzbSBNVVNUIHN1cHBvcnQgdGhlIGFiaWxpdHkgdG8gcmVjb3Jk
IHNlbGVjdGVkDQogICBwYXJ0cyBvZiBzZWxlY3RlZCBDU3MuDQoNCiAgIG8gUkVRLTAwNSBUaGUg
bWVjaGFuaXNtIE1VU1Qgc3VwcG9ydCB0aGUgYWJpbGl0eSB0byByZWNvcmQgYSBDUw0KICAgd2l0
aG91dCBsb3NzIG9mIG1lZGlhIChmb3IgZXhhbXBsZSwgY2xpcHBpbmcgbWVkaWEgYXQgdGhlIGJl
Z2lubmluZw0KICAgb2YgdGhlIENTKSBkdWUgdG8gUlMgcmVjb3JkaW5nIHByZXBhcmF0aW9uIGFu
ZCBhbHNvLCB3aXRob3V0DQogICBpbXBhY3RpbmcgdGhlIHF1YWxpdHkgb3IgdGltaW5nIG9mIHRo
ZSBDUyAoZm9yIGV4YW1wbGUsIGRlbGF5aW5nIHRoZQ0KICAgc3RhcnQgb2YgdGhlIENTIHdoaWxl
IHByZXBhcmF0aW9uIGZvciByZWNvcmRpbmcgc2Vzc2lvbikuICBTZWUgVXNlDQogICBDYXNlIDQg
aW4gU2VjdGlvbiA0IGZvciBtb3JlIGRldGFpbHMuDQoNCiAgIG8gUkVRLTAwNiBUaGUgbWVjaGFu
aXNtIE1VU1Qgc3VwcG9ydCB0aGUgcmVjb3JkaW5nIG9mIElWUiBzZXNzaW9ucy4NCg0KICAgbyBS
RVEtMDA3IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRoZSByZWNvcmRpbmcgb2YgUlRQIG1l
ZGlhIHR5cGVzDQogICB2b2ljZSwgRFRNRiAoYXMgZGVmaW5lZCBieSBbUkZDNDczM10pLCB2aWRl
bywgYW5kIHRleHQgKGFzIGRlZmluZWQgYnkNCiAgIFtSRkM0MTAzXSkuDQoNCiAgIG8gUkVRLTAw
OCBUaGUgbWVjaGFuaXNtIE1VU1Qgc3VwcG9ydCB0aGUgYWJpbGl0eSBmb3IgYW4gU1JDIHRvDQog
ICBkZWxpdmVyIG1peGVkIGF1ZGlvIHN0cmVhbXMgZnJvbSBtdWx0aXBsZSBDb21tdW5pY2F0aW9u
IFNlc3Npb25zIHRvDQogICBhbiBTUlMuDQoNCiAgIE5vdGU6IEEgbWl4ZWQgYXVkaW8gc3RyZWFt
IGlzIHdoZXJlIHNldmVyYWwgPHN0cm9uZz48Zm9udCBjb2xvcj0iZ3JlZW4iPnJlbGF0ZWQ8L2Zv
bnQ+PC9zdHJvbmc+IENvbW11bmljYXRpb24NCiAgIFNlc3Npb25zIGFyZSBjYXJyaWVkIGluIGEg
c2luZ2xlIFJlY29yZGluZyBTZXNzaW9uLiAgQSBtaXhlZCBtZWRpYQ0KICAgc3RyZWFtIGlzIHR5
cGljYWxseSBwcm9kdWNlZCBieSBhIG1peGVyIGZ1bmN0aW9uLiAgVGhlIFJTIE1BWSBiZQ0KICAg
aW5mb3JtZWQgYWJvdXQgdGhlIGNvbXBvc2l0aW9uIG9mIHRoZSBtaXhlZCBzdHJlYW1zIHRocm91
Z2ggc2Vzc2lvbg0KICAgbWV0YWRhdGEuDQoNCiAgIG8gUkVRLTAwOTogVGhlIG1lY2hhbmlzbSBN
VVNUIHN1cHBvcnQgdGhlIGFiaWxpdHkgZm9yIGFuIFNSQyB0bw0KICAgZGVsaXZlciBtaXhlZCBh
dWRpbyBzdHJlYW1zIGZyb20gZGlmZmVyZW50IHBhcnRpZXMgb2YgYSBnaXZlbg0KICAgQ29tbXVu
aWNhdGlvbiBTZXNzaW9uIHRvIGFuIFNSUy4NCg0KICAgbyBSRVEtMDEwIFRoZSBtZWNoYW5pc20g
TVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5IHRvIGRlbGl2ZXIgdG8gdGhlDQogICBTUlMgbXVsdGlw
bGUgbWVkaWEgc3RyZWFtcyBmb3IgYSBnaXZlbiBDUy4NCg0KICAgbyBSRVEtMDExIFRoZSBtZWNo
YW5pc20gTVVTVCBzdXBwb3J0IHRoZSBhYmlsaXR5IHRvIHBhdXNlIGFuZCByZXN1bWUNCiAgIHRo
ZSB0cmFuc21pc3Npb24gYW5kIGNvbGxlY3Rpb24gb2YgUlMgbWVkaWEuDQoNCiAgIG8gUkVRLTAx
MiBUaGUgbWVjaGFuaXNtIE1VU1QgcHJvdmlkZSB0aGUgU1JTIHdpdGggbWV0YWRhdGEgZGVzY3Jp
YmluZw0KICAgQ1NzIHRoYXQgYXJlIGJlaW5nIHJlY29yZGVkLCBpbmNsdWRpbmcgdGhlIG1lZGlh
IGJlaW5nIHVzZWQgYW5kIHRoZQ0KICAgaWRlbnRpdGllcyBvZiBwYXJ0aWVzIGludm9sdmVkLg0K
DQogICBvIFJFUS0wMTMgVGhlIG1lY2hhbmlzbSBNVVNUIHByb3ZpZGUgdGhlIFNSUyB3aXRoIHRo
ZSBtZWFucyB0bw0KICAgY29ycmVsYXRlIFJTIG1lZGlhIHdpdGggQ1MgcGFydGljaXBhbnQgbWVk
aWEuDQoNCiAgIG8gUkVRLTAxNCBNZXRhZGF0YSBmb3JtYXQgbXVzdCBiZSBhZ25vc3RpYyBvZiB0
aGUgdHJhbnNwb3J0IHByb3RvY29sLg0KDQogICBvIFJFUS0wMTU6IFRoZSBtZWNoYW5pc20gTVVT
VCBzdXBwb3J0IGEgbWVhbnMgdG8gc3RvcCB0aGUgcmVjb3JkaW5nLg0KDQogICBvIFJFUS0wMTY6
IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IGEgbWVhbnMgZm9yIGEgcmVjb3JkaW5nLWF3YXJl
DQogICBVQSBpbnZvbHZlZCBpbiBhIENTIHRvIHJlcXVlc3QgYXQgc2Vzc2lvbiBlc3RhYmxpc2ht
ZW50IHRpbWUgdGhhdCB0aGUNCiAgIENTIHNob3VsZCBiZSByZWNvcmRlZCBvciBzaG91bGQgbm90
IGJlIHJlY29yZGVkLCB0aGUgaG9ub3Jpbmcgb2Ygc3VjaA0KICAgYSByZXF1ZXN0IGJlaW5nIGRl
cGVuZGVudCBvbiBwb2xpY3kuDQoNCiAgIG8gUkVRLTAxNzogVGhlIG1lY2hhbmlzbSBNVVNUIHN1
cHBvcnQgYSBtZWFucyBmb3IgYSByZWNvcmRpbmctYXdhcmUNCiAgIFVBIGludm9sdmVkIGluIGEg
Q1MgdG8gcmVxdWVzdCBkdXJpbmcgYSBzZXNzaW9uIHRoYXQgdGhlIHJlY29yZGluZyBvZg0KICAg
dGhlIENTIHNob3VsZCBiZSBzdGFydGVkLCBwYXVzZWQsIHJlc3VtZWQgb3Igc3RvcHBlZCwgdGhl
IGhvbm9yaW5nIG9mDQogICBzdWNoIGEgcmVxdWVzdCBiZWluZyBkZXBlbmRlbnQgb24gcG9saWN5
Lg0KDQogICBvIFJFUS0wMTggVGhlIG1lY2hhbmlzbSBNVVNUIE5PVCBwcmV2ZW50IHRoZSBhcHBs
aWNhdGlvbiBvZiB0b25lcyBvcg0KICAgYW5ub3VuY2VtZW50cyBkdXJpbmcgcmVjb3JkaW5nIG9y
IGF0IHRoZSBzdGFydCBvZiBhIENTIHRvIHN1cHBvcnQNCiAgIG5vdGlmaWNhdGlvbiB0byBwYXJ0
aWNpcGFudHMgdGhhdCB0aGUgY2FsbCBpcyBiZWluZyByZWNvcmRlZCBvciBtYXkNCiAgIGJlIHJl
Y29yZGVkLg0KDQogICBvIFJFUS0wMTkgVGhlIG1lY2hhbmlzbSBNVVNUIHByb3ZpZGUgYSBtZWFu
cyBvZiBpbmRpY2F0aW5nIHRvDQogICByZWNvcmRpbmctYXdhcmUgVUFzIHdoZXRoZXIgcmVjb3Jk
aW5nIGlzIHRha2luZyBwbGFjZSwgZm9yDQogICBhcHByb3ByaWF0ZSByZW5kZXJpbmcgYXQgdGhl
IHVzZXIgaW50ZXJmYWNlLg0KDQogICBvIFJFUS0wMjAgVGhlIG1lY2hhbmlzbSBNVVNUIHByb3Zp
ZGUgYSB3YXkgZm9yIG1ldGFkYXRhIHRvIGJlDQogICBjb252ZXllZCB0byB0aGUgU1JTIGluY3Jl
bWVudGFsbHkgZHVyaW5nIHRoZSBDUy4NCg0KICAgbyBSRVEtMDIxIFRoZSBtZWNoYW5pc20gTVVT
VCBOT1QgcHJldmVudCBoaWdoIGF2YWlsYWJpbGl0eQ0KICAgZGVwbG95bWVudHMuDQoNCiAgIG8g
UkVRLTAyMiBUaGUgbWVjaGFuaXNtIE1VU1QgcHJvdmlkZSB0aGUgU1JTIHRoZSBzdGFydGluZyB3
YWxsIGNsb2NrDQogICB0aW1lIGZvciBlYWNoIFJTIG1lZGlhIHN0cmVhbSBjb3JyZXNwb25kaW5n
IHRvIHRoZSBDUyBwYXJ0aWNpcGFudA0KICAgbWVkaWEuDQoNCiAgIG8gUkVRLTAyMyBUaGUgbWVj
aGFuaXNtIE1VU1QgcHJvdmlkZSB0aGUgU1JTIHRoZSB3YWxsIGNsb2NrIHRpbWUgd2hlbg0KICAg
dGhlIFJlY29yZGluZyBTZXNzaW9uIGlzIHBhdXNlZCBhbmQgcmVzdW1lZC4NCg0KICAgbyBSRVEt
MDI0IFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IGZ1bmN0aW9uYWxpdHkgc3VjaCB0aGF0IGlm
IHRoZQ0KICAgQ1MgaXMgZW5jcnlwdGVkLCB0aGUgUlMgbWF5IHVzZSB0aGUgc2FtZSBvciBkaWZm
ZXJlbnQgZW5jcnlwdGlvbg0KICAga2V5cy4NCg0KICAgbyBSRVEtMDI1IFRoZSBtZWNoYW5pc20g
TVVTVCBwcm92aWRlIG1lYW5zIGZvciBhbiBTUlMgdG8gYXV0aGVudGljYXRlDQogICB0aGUgU1JD
IG9uIFJTIGluaXRpYXRpb24uDQoNCiAgIG8gUkVRLTAyNiBUaGUgbWVjaGFuaXNtIE1VU1QgcHJv
dmlkZSBtZWFucyBmb3IgYW4gU1JDIHRvIGF1dGhlbnRpY2F0ZQ0KICAgdGhlIFNSUyBvbiBSUyBp
bml0aWF0aW9uLg0KDQogICBvIFJFUS0wMjcgVGhlIG1lY2hhbmlzbSBNVVNUIGVuc3VyZSB0aGF0
IHRoZSBpbnRlZ3JpdHkgb2YgdGhlDQogICBtZXRhZGF0YSBzZW50IGZyb20gU1JDIHRvIFNSUyBp
cyBhbiBhY2N1cmF0ZSByZXByZXNlbnRhdGlvbiBvZiB0aGUNCiAgIG9yaWdpbmFsIENTIG1ldGFk
YXRhLg0KDQogICBvIFJFUS0wMjggVGhlIG1lY2hhbmlzbSBNVVNUIGVuc3VyZSB0aGF0IHRoZSBp
bnRlZ3JpdHkgb2YgdGhlIG1lZGlhDQogICBzZW50IGZyb20gU1JDIHRvIFNSUyBpcyBhbiBhY2N1
cmF0ZSByZXByZXNlbnRhdGlvbiBvZiB0aGUgb3JpZ2luYWwgQ1MNCiAgIG1lZGlhLg0KDQogICBv
IFJFUS0wMjkgVGhlIG1lY2hhbmlzbSBNVVNUIGVuc3VyZSB0aGUgY29uZmlkZW50aWFsaXR5IG9m
IHRoZQ0KICAgTWV0YWRhdGEgc2VudCBmcm9tIFNSQyB0byBTUlMuDQoNCiAgIG8gUkVRLTAzMCBU
aGUgbWVjaGFuaXNtIE1VU1QgcHJvdmlkZSBhIG1lYW5zIHRvIHN1cHBvcnQgUlMNCiAgIGNvbmZp
ZGVudGlhbGl0eS4NCg0KICAgbyBSRVEtMDMxIFRoZSBtZWNoYW5pc20gTVVTVCBzdXBwb3J0IHRo
ZSBhYmlsaXR5IHRvIGRlbGl2ZXIgdG8gdGhlDQogICBTUlMgbXVsdGlwbGUgbWVkaWEgc3RyZWFt
cyBvZiB0aGUgc2FtZSBtZWRpYSB0eXBlIChlLmcuIGF1ZGlvLA0KICAgdmlkZW8pLiAgRm9yIGV4
YW1wbGUgaW4gdGhlIGNhc2Ugb2YgZGVsaXZlcmluZyB1bm1peGVkIGF1ZGlvIGZvciBlYWNoDQog
ICBwYXJ0aWNpcGFudCBpbiB0aGUgQ1MuDQoNCjYuICBQcml2YWN5IENvbnNpZGVyYXRpb25zDQoN
CiAgIFJlc3BlY3RpbmcgdGhlIHByaXZhY3kgcmlnaHRzIGFuZCB3aXNoZXMgb2YgdXNlcnMgZW5n
YWdlZCBpbiBhIGNhbGwNCiAgIGlzIG9mIHBhcmFtb3VudCBpbXBvcnRhbmNlLiAgSW4gbWFueSBq
dXJpc2RpY3Rpb25zIHBhcnRpY2lwYW50cyBoYXZlDQogICBhIHJpZ2h0IHRvIGtub3cgdGhhdCB0
aGUgc2Vzc2lvbiBpcyBiZWluZyByZWNvcmRlZCBvciBtaWdodCBiZQ0KICAgcmVjb3JkZWQsIGFu
ZCBoYXZlIGEgcmlnaHQgdG8gb3B0IG91dCwgZWl0aGVyIGJ5IHRlcm1pbmF0aW5nIHRoZSBjYWxs
DQogICBvciBieSBkZW1hbmRpbmcgdGhhdCB0aGUgY2FsbCBub3QgYmUgcmVjb3JkZWQuICBUaGVy
ZWZvcmUgdGhpcw0KICAgZG9jdW1lbnQgY29udGFpbnMgcmVxdWlyZW1lbnRzIGZvciBiZWluZyBh
YmxlIHRvIG5vdGlmeSB1c2VycyB0aGF0IGENCiAgIGNhbGwgaXMgYmVpbmcgcmVjb3JkZWQgYW5k
IGZvciB1c2VycyB0byBiZSBhYmxlIHRvIHJlcXVlc3QgdGhhdCBhDQogICBjYWxsIG5vdCBiZSBy
ZWNvcmRlZC4gIFVzZSBjYXNlcyB3aGVyZSB1c2VycyBwYXJ0aWNpcGF0aW5nIGluIGEgY2FsbA0K
ICAgYXJlIG5vdCBpbmZvcm1lZCB0aGF0IHRoZSBjYWxsIGlzIG9yIG1pZ2h0IGJlIHJlY29yZGVk
IGFyZSBvdXRzaWRlDQogICB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudC4gIEluIHBhcnRpY3Vs
YXIsIGxhd2Z1bCBpbnRlcmNlcHQgaXMNCiAgIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9j
dW1lbnQuDQoNCiAgIFJlcXVpcmVtZW50cyBmb3IgcGFydGljaXBhbnQgbm90aWZpY2F0aW9uIG9m
IHJlY29yZGluZyA8c3RyaWtlPjxmb250IGNvbG9yPSJyZWQiPnZhcmllczwvZm9udD48L3N0cmlr
ZT4gPHN0cm9uZz48Zm9udCBjb2xvcj0iZ3JlZW4iPnZhcnk8L2ZvbnQ+PC9zdHJvbmc+IHdpZGVs
eSBieQ0KICAganVyaXNkaWN0aW9uLiAgSW4gYSBnaXZlbiBkZXBsb3ltZW50LCBub3QgYWxsIHVz
ZXJzIHdpbGwgYmUNCiAgIGF1dGhvcml6ZWQgdG8gc3RvcCB0aGUgcmVjb3JkaW5nIG9mIGEgQ1Mg
KGFsdGhvdWdoIGFueSB1c2VyIGNhbg0KICAgdGVybWluYXRlIGEgQ1MpLiAgVHlwaWNhbGx5IHVz
ZXJzIHdpdGhpbiB0aGUgZG9tYWluIHRoYXQgaXMgY2FycnlpbmcNCiAgIG91dCB0aGUgcmVjb3Jk
aW5nIHdpbGwgYmUgc3ViamVjdCB0byBwb2xpY2llcyBvZiB0aGF0IGRvbWFpbg0KICAgY29uY2Vy
bmluZyB3aGV0aGVyIENTcyBhcmUgcmVjb3JkZWQuICBGb3IgZXhhbXBsZSwgaW4gYSBjYWxsIGNl
bnRyZSwNCiAgIGFnZW50cyB3aWxsIGJlIHN1YmplY3QgdG8gcG9saWNpZXMgb2YgdGhlIGNhbGwg
Y2VudHJlIGFuZCBtYXkgb3IgbWF5DQogICBub3QgaGF2ZSB0aGUgcmlnaHQgdG8gcHJldmVudCB0
aGUgcmVjb3JkaW5nIG9mIGEgQ1Mgb3IgcGFydCBvZiBhIENTLg0KICAgVXNlcnMgY2FsbGluZyBp
bnRvIHRoZSBjYWxsIGNlbnRyZSwgb24gdGhlIG90aGVyIGhhbmQsIHdpbGwgdHlwaWNhbGx5DQog
ICBoYXZlIHRvIGFzayB0aGUgYWdlbnQgbm90IHRvIHJlY29yZCB0aGUgQ1MuICBJZiB0aGUgYWdl
bnQgaXMgdW5hYmxlDQogICB0byBwcmV2ZW50IHJlY29yZGluZywgb3IgaWYgdGhlIGNhbGxlciBk
b2VzIG5vdCB0cnVzdCB0aGUgYWdlbnQsIHRoZQ0KICAgb25seSBvcHRpb24gZ2VuZXJhbGx5IGlz
IHRvIHRlcm1pbmF0ZSB0aGUgQ1MuDQoNCiAgIFByaXZhY3kgY29uc2lkZXJhdGlvbnMgYWxzbyBl
eHRlbmQgdG8gd2hhdCBoYXBwZW5zIHRvIGEgcmVjb3JkaW5nDQogICBvbmNlIGl0IGhhcyBiZWVu
IGNyZWF0ZWQuICBUeXBpY2FsIGlzc3VlcyBhcmUgd2hvIGNhbiBhY2Nlc3MgdGhlDQogICByZWNv
cmRpbmcgKGUuZy4sIHJlY2VpdmUgYSBjb3B5IG9mIHRoZSByZWNvcmRpbmcsIHZpZXcgdGhlIG1l
dGFkYXRhLA0KICAgcGxheSBiYWNrIHRoZSBtZWRpYSwgZXRjLiksIGZvciB3aGF0IHB1cnBvc2Ug
dGhlIHJlY29yZGluZyBjYW4gYmUNCiAgIHVzZWQgKGUuZy4sIGZvciBub24tcmVwdWRpYXRpb24s
IGZvciB0cmFpbmluZyBwdXJwb3NlcywgZm9yIHF1YWxpdHkNCiAgIGNvbnRyb2wgcHVycG9zZXMs
IGV0Yy4pIGFuZCBmb3IgaG93IGxvbmcgdGhlIHJlY29yZGluZyBpcyB0byBiZQ0KICAgcmV0YWlu
ZWQgYmVmb3JlIGRlbGV0aW9uLiAgVGhlc2UgYXJlIHR5cGljYWxseSBwb2xpY2llcyBvZiB0aGUg
ZG9tYWluDQogICB0aGF0IG1ha2VzIHRoZSByZWNvcmRpbmcsIHJhdGhlciB0aGFuIHBvbGljaWVz
IG9mIGluZGl2aWR1YWwgdXNlcnMNCiAgIGludm9sdmVkIGluIGEgcmVjb3JkZWQgQ1MsIHdoZXRo
ZXIgdGhvc2UgdXNlcnMgYmUgaW4gdGhlIHNhbWUgZG9tYWluDQogICBvciBpbiBhIGRpZmZlcmVu
dCBkb21haW4uICBUYWtpbmcgdGhlIGNhbGwgY2VudHJlIGV4YW1wbGUgYWdhaW4sDQogICBhZ2Vu
dHMgbWlnaHQgYmUgbWFkZSBhd2FyZSBvZiBjYWxsIGNlbnRyZSBwb2xpY3kgcmVnYXJkaW5nIHJl
dGVudGlvbg0KICAgYW5kIHVzZSBvZiByZWNvcmRpbmdzIGFzIHBhcnQgb2YgdGhlaXIgZW1wbG95
bWVudCBjb250cmFjdCwgYW5kDQogICBjYWxsZXJzIGZyb20gb3V0c2lkZSB0aGUgY2FsbCBjZW50
cmUgbWlnaHQgYmUgZ2l2ZW4gc29tZSBpbmZvcm1hdGlvbg0KICAgYWJvdXQgcG9saWN5IHdoZW4g
bm90aWZpZWQgdGhhdCBhIENTIHdpbGwgYmUgcmVjb3JkZWQgKGUuZy4sIHRocm91Z2gNCiAgIGFu
IGFubm91bmNlbWVudCB0aGF0IHNheXMgdGhhdCBjYWxscyBtYXkgYmUgcmVjb3JkZWQgZm9yIHF1
YWxpdHkNCiAgIHB1cnBvc2VzKS4NCg0KICAgVGhpcyBkb2N1bWVudCBkb2VzIG5vdCBzcGVjaWZ5
IGFueSByZXF1aXJlbWVudHMgZm9yIGEgdXNlciBlbmdhZ2VkIGluDQogICBhIENTIHRvIGJlIGFi
bGUgdG8gZGljdGF0ZSBwb2xpY3kgZm9yIHdoYXQgaGFwcGVucyB0byBhIHJlY29yZGluZywgb3IN
CiAgIGZvciBzdWNoIGluZm9ybWF0aW9uIHRvIGJlIGNvbnZleWVkIGZyb20gYW4gU1JDIHRvIGFu
IFNSUy4gIEl0IGlzDQogICBhc3N1bWVkIHRoYXQgdGhlIFNSUyBoYXMgYWNjZXNzIHRvIHBvbGlj
eSBhcHBsaWNhYmxlIHRvIGl0cw0KICAgZW52aXJvbm1lbnQgYW5kIGNhbiBlbnN1cmUgdGhhdCBy
ZWNvcmRpbmdzIGFyZSBzdG9yZWQgYW5kIHVzZWQgaW4NCiAgIGFjY29yZGFuY2Ugd2l0aCB0aGF0
IHBvbGljeS4NCg0KNy4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zDQoNCiAgIFNlc3Npb24gcmVj
b3JkaW5nIGhhcyBzdWJzdGFudGlhbCBzZWN1cml0eSBpbXBsaWNhdGlvbnMsIGZvciB0aGUgU0lQ
DQogICBVQSdzIGJlaW5nIHJlY29yZGVkLCB0aGUgU1JDLCBhbmQgdGhlIFNSUy4NCg0KICAgRm9y
IHRoZSBTSVAgVUEncyBpbnZvbHZlZCBpbiB0aGUgQ29tbXVuaWNhdGlvbiBTZXNzaW9uLCB0aGUN
CiAgIHJlcXVpcmVtZW50cyBpbiB0aGlzIGRyYWZ0IGVuYWJsZSB0aGUgVUEgdG8gaWRlbnRpZnkg
dGhhdCBhDQogICBDb21tdW5pY2F0aW9uIFNlc3Npb24gaXMgYmVpbmcgcmVjb3JkZWQgYW5kIGZv
ciB0aGUgVUEgdG8gcmVxdWVzdA0KICAgdGhhdCBhIGdpdmVuIENvbW11bmljYXRpb24gU2Vzc2lv
biBpcyBub3Qgc3ViamVjdCB0byByZWNvcmRpbmcuDQoNCiAgIFNpbmNlIGh1bWFucyBkb24ndCB0
eXBpY2FsbHkgbG9vayBhdCBvciBrbm93IGFib3V0IHByb3RvY29sIHNpZ25hbGluZw0KICAgc3Vj
aCBhcyBTSVAsIGFuZCBpbmRlZWQgdGhlIFNJUCBzZXNzaW9uIG1pZ2h0IGhhdmUgb3JpZ2luYXRl
ZCB0aHJvdWdoDQogICBhIFBTVE4gR2F0ZXdheSB3aXRob3V0IGFueSBhYmlsaXR5IHRvIHBhc3Mg
b24gaW4tc2lnbmFsaW5nDQogICBpbmRpY2F0aW9ucyBvZiByZWNvcmRpbmcsIHVzZXJzIGNhbiBi
ZSBub3RpZmllZCBvZiByZWNvcmRpbmcgaW4gdGhlDQogICBtZWRpYSBpdHNlbGYgdGhyb3VnaCB2
b2ljZSBhbm5vdW5jZW1lbnRzLCBhIHZpc3VhbCBpbmRpY2F0b3Igb24gdGhlDQogICBlbmRwb2lu
dCwgb3Igb3RoZXIgbWVhbnMuDQoNCiAgIFdpdGggcmVnYXJkcyB0byBzZWN1cml0eSBpbXBsaWNh
dGlvbnMgb2YgdGhlIHByb3RvY29sKHMpLCBjbGVhcmx5DQogICB0aGVyZSBpcyBhIG5lZWQgZm9y
IGF1dGhlbnRpY2F0aW9uLCBhdXRob3JpemF0aW9uLCBlYXZlc2Ryb3BwaW5nDQogICBwcm90ZWN0
aW9uLCBhbmQgbm9uLXJlcHVkaWF0aW9uIGZvciB0aGUgc29sdXRpb24uICBUaGUgU1JDIG5lZWRz
IHRvDQogICBrbm93IHRoZSBTUlMgaXQgaXMgY29tbXVuaWNhdGluZyB3aXRoIGlzIGxlZ2l0aW1h
dGUsIGFuZCB2aWNlLXZlcnNhLA0KICAgZXZlbiBpZiB0aGV5IGFyZSBpbiBkaWZmZXJlbnQgZG9t
YWlucy4gIEJvdGggdGhlIHNpZ25hbGluZyBhbmQgbWVkaWENCiAgIGZvciB0aGUgUmVjb3JkaW5n
IFNlc3Npb24gbmVlZCB0aGUgYWJpbGl0eSB0byBiZSBhdXRoZW50aWNhdGVkIGFuZA0KICAgcHJv
dGVjdGVkIGZyb20gZWF2ZXNkcm9wcGluZyBhbmQgbm9uLXJlcHVkaWF0aW9uLiAgUmVxdWlyZW1l
bnRzIGFyZQ0KICAgZGV0YWlsZWQgaW4gdGhlIHJlcXVpcmVtZW50cyBzZWN0aW9uLg0KDQo4LiAg
SUFOQSBDb25zaWRlcmF0aW9ucw0KDQogICBUaGlzIGRvY3VtZW50IGhhcyBubyBJQU5BIGFjdGlv
bnMuDQoNCjkuICBBY2tub3dsZWRnZW1lbnRzDQoNCiAgIFRoYW5rcyB0byBEYW4gV2luZywgQWxh
biBKb2huc29uLCBWaWpheSBHdXJiYW5pLCBDdWxsZW4gSmVubmluZ3MsDQogICBIYWRyaWVsIEth
cGxhbiwgSGVucnkgTHVtLCBEYXZlIFNtaXRoLCBNYXJ0aW4gUGFsbWVyLCBBbGlzc2EgQ29vcGVy
LA0KICAgRGVlcGFuc2h1IEdhdXRhbSwgUGF1bCBLeXppdmF0LCBQYXJ0aGFzYXJhdGhpIFIsIGFu
ZCBSYW0gTW9oYW4gUiBmb3INCiAgIHRoZWlyIHNpZ25pZmljYW50IGNvbnRyaWJ1dGlvbnMgYW5k
IGFzc2lzdGFuY2Ugd2l0aCB0aGlzIGRvY3VtZW50IGFuZA0KICAgV29ya2luZyBHcm91cCwgYW5k
IHRvIGFsbCB0aGUgbWVtYmVycyBvZiB0aGUgRElTUEFUQ0ggV0cgYW5kIFNJUFJFQw0KICAgV0cg
bWFpbGluZyBsaXN0cyBmb3IgcHJvdmlkaW5nIHZhbHVhYmxlIGlucHV0IHRvIHRoaXMgd29yay4N
Cg0KMTAuICBOb3JtYXRpdmUgUmVmZXJlbmNlcw0KDQogICBbUkZDMjExOV0gIEJyYWRuZXIsIFMu
LCAiS2V5IHdvcmRzIGZvciB1c2UgaW4gUkZDcyB0byBJbmRpY2F0ZQ0KICAgICAgICAgICAgICBS
ZXF1aXJlbWVudCBMZXZlbHMiLCBCQ1AgMTQsIFJGQyAyMTE5LCBNYXJjaCAxOTk3Lg0KDQogICA8
c3RyaWtlPjxmb250IGNvbG9yPSJyZWQiPltSRkMyODA0XSAgSUFCIGFuZCBJRVNHLCAiSUVURiBQ
b2xpY3kgb24gV2lyZXRhcHBpbmciLCBSRkMgMjgwNCwNCiAgICAgICAgICAgICAgTWF5IDIwMDAu
PC9mb250Pjwvc3RyaWtlPg0KDQogICBbUkZDMzI2MV0gIFJvc2VuYmVyZywgSi4sIFNjaHVsenJp
bm5lLCBILiwgQ2FtYXJpbGxvLCBHLiwgSm9obnN0b24sDQogICAgICAgICAgICAgIEEuLCBQZXRl
cnNvbiwgSi4sIFNwYXJrcywgUi4sIEhhbmRsZXksIE0uLCBhbmQgRS4NCiAgICAgICAgICAgICAg
U2Nob29sZXIsICJTSVA6IFNlc3Npb24gSW5pdGlhdGlvbiBQcm90b2NvbCIsIFJGQyAzMjYxLA0K
ICAgICAgICAgICAgICBKdW5lIDIwMDIuDQoNCiAgIDxzdHJvbmc+PGZvbnQgY29sb3I9ImdyZWVu
Ij5bUkZDNDEwM10gIEhlbGxzdHJvbSwgRy4gYW5kIFAuIEpvbmVzLCAiUlRQIFBheWxvYWQgZm9y
IFRleHQNCiAgICAgICAgICAgICAgQ29udmVyc2F0aW9uIiwgUkZDIDQxMDMsIEp1bmUgMjAwNS4N
Cg0KICAgW1JGQzQ3MzNdICBTY2h1bHpyaW5uZSwgSC4gYW5kIFQuIFRheWxvciwgIlJUUCBQYXls
b2FkIGZvciBEVE1GDQogICAgICAgICAgICAgIERpZ2l0cywgVGVsZXBob255IFRvbmVzLCBhbmQg
VGVsZXBob255IFNpZ25hbHMiLCBSRkMgNDczMywNCiAgICAgICAgICAgICAgRGVjZW1iZXIgMjAw
Ni48L2ZvbnQ+PC9zdHJvbmc+DQoNCkF1dGhvcnMnIEFkZHJlc3Nlcw0KDQogICBLZW4gUmVob3Ig
KGVkaXRvcikNCiAgIENpc2NvIFN5c3RlbXMNCiAgIDE3MCBXZXN0IFRhc21hbiBEci4NCiAgIE1h
aWwgU3RvcCBTSkMzMC8yLw0KICAgU2FuIEpvc2UsIENBICA5NTEzNA0KICAgVVNBDQoNCiAgIEVt
YWlsOiBrcmVob3JAY2lzY28uY29tDQoNCiAgIExlb24gUG9ydG1hbiAoZWRpdG9yKQ0KICAgTklD
RSBTeXN0ZW1zDQogICA4IEhhcG5pbmENCiAgIFJhJ2FuYW5hICA0MzAxNw0KICAgSXNyYWVsDQoN
CiAgIEVtYWlsOiBsZW9uLnBvcnRtYW5AbmljZS5jb20NCg0KICAgQW5kcmV3IEh1dHRvbg0KICAg
U2llbWVucyBFbnRlcnByaXNlIENvbW11bmljYXRpb25zDQoNCiAgIEVtYWlsOiBhbmRyZXcuaHV0
dG9uQHNpZW1lbnMtZW50ZXJwcmlzZS5jb20NCiAgIFVSSTogICBodHRwOi8vd3d3LnNpZW1lbnMt
ZW50ZXJwcmlzZS5jb20NCg0KICAgUmFqbmlzaCBKYWluDQogICBJUEMgU3lzdGVtcw0KICAgNzc3
IENvbW1lcmNlIERyaXZlDQogICBGYWlyZmllbGQsIENUICAwNjgyNQ0KICAgVVNBDQoNCiAgIEVt
YWlsOiByYWpuaXNoLmphaW5AaXBjLmNvbQ0KPC9wcmU+DQo8L2JvZHk+PC9odG1sPg==

------_=_NextPart_001_01CBE261.ED68E66B--

From Internet-Drafts@ietf.org  Mon Mar 14 09:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D90FF3A6D6A; Mon, 14 Mar 2011 09:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mYN5C8RUPisn; Mon, 14 Mar 2011 09:15:01 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 704DF3A6D41; Mon, 14 Mar 2011 09:15:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314161501.21193.6297.idtracker@localhost>
Date: Mon, 14 Mar 2011 09:15:01 -0700
Cc: siprec@ietf.org
Subject: [siprec] I-D Action:draft-ietf-siprec-req-08.txt
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 16:15:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP Recording Working Group of the IETF.


	Title           : Requirements for SIP-based Media Recording (SIPREC)
	Author(s)       : K. Rehor, et al.
	Filename        : draft-ietf-siprec-req-08.txt
	Pages           : 15
	Date            : 2011-03-14

Session recording is a critical requirement in many business
communications environments such as call centers and financial
trading floors.  In some of these environments, all calls must be
recorded for regulatory and compliance reasons.  In others, calls may
be recorded for quality control or business analytics.

Recording is typically performed by sending a copy of the session
media to the recording devices.  This document specifies requirements
for extensions to SIP that will manage delivery of RTP media to a
recording device.  This is being referred to as SIP-based Media
Recording.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-siprec-req-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-siprec-req-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-14090019.I-D@ietf.org>


--NextPart--

From partr@cisco.com  Mon Mar 14 10:05:22 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 417CA3A6E57 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 10:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.235
X-Spam-Level: 
X-Spam-Status: No, score=-8.235 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZtpjeKllMx8E for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 10:05:20 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id AA0A13A6E39 for <siprec@ietf.org>; Mon, 14 Mar 2011 10:05:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=5766; q=dns/txt; s=iport; t=1300122404; x=1301332004; h=mime-version:subject:date:message-id:references:from:to; bh=x5ccrstuz4M3n1PXnb6H+6TSznqhyoMqS9n41RM55ag=; b=cw6BfFk23BdI1jKkVdfEGh+AY2+qhESl5kyOPR/Gn/Iu5e/C7PLCXb06 g6OtRQrv0ZkfSpbszVgMX34h4t8Ve4YPBSz0YwkE6USRaHr+HpnLvVbzC 0uFC8HsD+8fl29/HhnhA6AIzPBMDQVjqVvolVF7XyHjlBCFSZGywDpohf s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqsEAF/nfU2Q/khNgWdsb2JhbAClN1IUAQEWJiWkJZwQhWIEhSmKfQ
X-IronPort-AV: E=Sophos;i="4.62,316,1297036800"; d="scan'208,217";a="79117771"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 14 Mar 2011 17:06:41 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2EH6dnf023693; Mon, 14 Mar 2011 17:06:41 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Mar 2011 22:36:39 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE26A.2F030A2B"
Date: Mon, 14 Mar 2011 22:34:32 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1I
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 14 Mar 2011 17:06:39.0745 (UTC) FILETIME=[2F41E710:01CBE26A]
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 17:05:22 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE26A.2F030A2B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

SIPREC Architecture-01 draft looks good in the high level. Some of the =
minor comments are as follows:
=20
Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be preferred =
to indicate that SRC also has AS & MS clubbed together. IMO, this =
provide more clarity while reading.
=20
Sec 4.1.5 Figure shall be added to indicate a scenarion whererin focus =
acts as SRC.
=20
Sec 4.2 Para 2 example does not go inline with REQ-024 of -07 =
Requirement draft. The example shall change from "client must decrypt" =
to "client may decrypt". =20
=20
Sec 4.2.1 Fourth bullet text may be preferred to change as "Indicate =
support for the recording metadata"
=20
Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or "sendonly as =
it is indicated as SRS and SRC in the beginning of the line.
=20
Sec 4.3.1 1st bullet shall be changed from "Dialog identifier" to =
"Communication Session Identifier"
=20
Sec 4.3.1 whether 3rd bullet is required?=20
=20
General comment: it is preferred to change to "should, must" to "SHOULD, =
MUST" as per RFC 2119=20
=20
Sec 4.3.2 1st bullet has to be removed as it is not required any more.
=20
Sec 4.3.2 3rd bullet has to be changed to indicate XML package instead =
of Event package
=20
Sec 4.3.2 last bullet: is it required to pass metadata using non-sip =
mechanism?

Thanks
Partha

________________________________

From: siprec-bounces@ietf.org on behalf of Elwell, John
Sent: Wed 3/2/2011 10:25 PM
To: siprec@ietf.org
Subject: [siprec] Progressing the architecture document



draft-ietf-siprec-architecture has not moved forward much in recent =
months, waiting for progress on solutions to help confirm the =
architecture. Now would be an excellent time for people to raise any =
issues that can perhaps be addressed by the editor before the cut-off =
(2011-03-14) or discussed in Prague.

John

_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec



------_=_NextPart_001_01CBE26A.2F030A2B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>[siprec] Progressing the architecture =
document</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText81337>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>SIPREC =
Architecture-01&nbsp;draft looks good in the high level. Some of the =
minor comments are as follows:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.1.4 Fig 3 indicates about SRS having AS &amp; MS, =
it may be preferred to indicate that SRC also has AS &amp; MS clubbed =
together. IMO, this provide more clarity while reading.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.1.5 Figure shall be added to indicate a scenarion =
whererin focus acts as SRC.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.2 Para 2 example does not go inline with REQ-024 of =
-07 Requirement draft. The example shall change from "client must =
decrypt" to "client may decrypt".&nbsp; </DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.2.1 Fourth bullet text may be preferred to change =
as "Indicate support for the recording metadata"</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" =
or "sendonly as it is indicated as SRS and SRC in the beginning of the =
line.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.3.1 1st bullet shall be changed from "Dialog =
identifier" to "Communication Session Identifier"</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.3.1 whether 3rd bullet is required? </DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>General comment: it is preferred to change to "should, =
must" to "SHOULD, MUST" as per RFC 2119 </DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.3.2 1st bullet has to be removed as it is not =
required any more.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.3.2 3rd bullet has to be changed to indicate XML =
package instead of Event package</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Sec 4.3.2 last bullet: is it required to pass metadata =
using non-sip mechanism?<BR></DIV>=0A=
<DIV dir=3Dltr>Thanks</DIV>=0A=
<DIV dir=3Dltr>Partha</DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> siprec-bounces@ietf.org on =
behalf of Elwell, John<BR><B>Sent:</B> Wed 3/2/2011 10:25 =
PM<BR><B>To:</B> siprec@ietf.org<BR><B>Subject:</B> [siprec] Progressing =
the architecture document<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>draft-ietf-siprec-architecture has not moved forward =
much in recent months, waiting for progress on solutions to help confirm =
the architecture. Now would be an excellent time for people to raise any =
issues that can perhaps be addressed by the editor before the cut-off =
(2011-03-14) or discussed in =
Prague.<BR><BR>John<BR><BR>______________________________________________=
_<BR>siprec mailing list<BR>siprec@ietf.org<BR><A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01CBE26A.2F030A2B--

From rmohanr@cisco.com  Mon Mar 14 10:08:17 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AABC3A6D40 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 10:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.314
X-Spam-Level: 
X-Spam-Status: No, score=-10.314 tagged_above=-999 required=5 tests=[AWL=0.285, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UwHr501b1bNL for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 10:08:16 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id B3A613A6D1D for <siprec@ietf.org>; Mon, 14 Mar 2011 10:08:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=2316; q=dns/txt; s=iport; t=1300122579; x=1301332179; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=inCgqBEJ+Yy2+qvDBCA+HoAreKNjQ4fDXauu3aFnQhk=; b=OhgjP1lSx9w06Z9GszNOFV96dCgvbq7PR842DxOwnaKhZxDi0HwzVKSi dxYDz7FL7EnsPQ0lrCkYC+tD/AGQdDZDxcxNmJtbuRBtAZjfRqG6KyX80 DYAswAvtfsjrlnZLXZMf5M/4/iqNXWcZ5L9iVcV8b8vOmVk7jD24/Q6xU U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuIAAEjpfU2Q/khLgWdsb2JhbACYRI1FFAEBFiYlpBacFYViBIUpin0
X-IronPort-AV: E=Sophos;i="4.62,316,1297036800"; d="scan'208";a="21654344"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 14 Mar 2011 17:09:25 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2EH9PsU001142 for <siprec@ietf.org>; Mon, 14 Mar 2011 17:09:25 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Mar 2011 22:39:25 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Mar 2011 22:39:23 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD05A7E856@XMB-BGL-417.cisco.com>
In-Reply-To: <7744FE52C78D944587F03773EB45146109AC1FDD@xmb-sjc-22e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Last chance for changes to siprec-req-07
Thread-Index: Acvdt7euTNDO2n4QSAyVfMXgONVCfQEqfKvQAAI0XGA=
References: <A444A0F8084434499206E78C106220CA086A648103@MCHP058A.global-ad.net> <7744FE52C78D944587F03773EB45146109AC1FDD@xmb-sjc-22e.amer.cisco.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Ken Rehor (krehor)" <krehor@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 14 Mar 2011 17:09:25.0017 (UTC) FILETIME=[91C46890:01CBE26A]
Subject: Re: [siprec] Last chance for changes to siprec-req-07
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 17:08:17 -0000

The revised document looks pretty clean and good to go.

Ram

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Ken Rehor (krehor)
> Sent: Monday, March 14, 2011 9:37 PM
> To: siprec@ietf.org
> Subject: Re: [siprec] Last chance for changes to siprec-req-07
>=20
> Thanks to John, Leon and the team, we posted req-08 today.
> (.txt, .xml, and diff attached)
>=20
> Ken
>=20
>=20
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Tuesday, March 08, 2011 9:39 AM
> > To: siprec@ietf.org; Leon Portman; Ken Rehor (krehor)
> > Subject: Last chance for changes to siprec-req-07
> >
> > The editors have posted req-07. This is your last chance to request
> changes.
> > Deadline 2011-03-13 (to give the editors chance to produce -08
before
> the
> > deadline the next day).
> >
> > I noticed the following:
> > 1. IDNITS gave a warning about the disclaimer concerning pre-RFC5378
> work in
> > the boiler plate. Since the document (and also its draft-rehor
> predecessor)
> > is post 2008, is this applicable?
> > 2. IDNITS revealed missing references RFC 4733 and RFC 4103 (I
> believe
> both
> > are normative references)
> > 3. IDNITS revealed unused reference RFC 2804.
> > 4. Change "Ral-time" to "Real-time"
> > 5. "REQ-001 The mechanism MUST provide a means for "using the SIP
> >    protocol for" establishing, maintaining and terminating"
> > Remove 'the quotes around using the SIP protocol for'
> > 6. "Note: A mixed audio stream is where several Communication
> Sessions
> >    are carried in a single Recording Session."
> > Change to:
> > "Note: A mixed audio stream is where several related Communication
> Sessions
> >    are carried in a single Recording Session."
> > (i.e., add the word "related".
> > 7. "Requirements for participant notification of recording varies
> widely
> >    by jurisdiction."
> > Change "varies" to "vary".
> >
> > Would the editors please correct these and ensure the document
passes
> IDNITS.
> > Please ensure -08 is posted by the submission deadline 2011-03-14.
By
> all
> > means wait for other comments, but not at the expense of missing the
> > deadline!
> >
> > Thanks,
> >
> > John


From john.elwell@siemens-enterprise.com  Mon Mar 14 10:52:47 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E71F3A6DBE for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 10:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2EnR9u18BbmU for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 10:52:42 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id D71533A6A31 for <siprec@ietf.org>; Mon, 14 Mar 2011 10:52:41 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3742880; Mon, 14 Mar 2011 18:54:04 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id C8B0B1EB82AE; Mon, 14 Mar 2011 18:54:04 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 14 Mar 2011 18:54:04 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>
Date: Mon, 14 Mar 2011 18:54:03 +0100
Thread-Topic: Submission of draft-ietf-siprec-req-08 to IESG
Thread-Index: AcvecGUPbZBrMSmERDukGXT0Y/e3Ng==
Message-ID: <A444A0F8084434499206E78C106220CA086A89B338@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "'Brian.Rosen@neustar.biz' \(Brian.Rosen@neustar.biz\)" <Brian.Rosen@neustar.biz>, "siprec@ietf.org" <siprec@ietf.org>
Subject: [siprec] Submission of draft-ietf-siprec-req-08 to IESG
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 17:52:50 -0000

Gonzalo,

I am submitting siprec-req-08 to the IESG. Here is the write-up:


  (1.a) Who is the Document Shepherd for this document? Has the
        Document Shepherd personally reviewed this version of the=20
        document and, in particular, does he or she believe this=20
        version is ready for forwarding to the IESG for publication?
I am the Document Shepherd, I have personally reviewed this version and I b=
elieve it is ready for forwarding to the IESG.

  (1.b) Has the document had adequate review both from key WG members=20
        and from key non-WG members? Does the Document Shepherd have=20
        any concerns about the depth or breadth of the reviews that=20
        have been performed?
The document has had extensive review from during its development, involvin=
g most/all active members of WG and discussion of open issues during meetin=
gs and interims.

  (1.c) Does the Document Shepherd have concerns that the document=20
        needs more review from a particular or broader perspective,=20
        e.g., security, operational complexity, someone familiar with=20
        AAA, internationalization or XML?
No concerns. In particular, we engaged the services of a privacy expert to =
review requirements relating to privacy.

  (1.d) Does the Document Shepherd have any specific concerns or=20
        issues with this document that the Responsible Area Director
        and/or the IESG should be aware of? For example, perhaps he=20
        or she is uncomfortable with certain parts of the document, or=20
        has concerns whether there really is a need for it. In any=20
        event, if the WG has discussed those issues and has indicated=20
        that it still wishes to advance the document, detail those=20
        concerns here. Has an IPR disclosure related to this document=20
        been filed? If so, please include a reference to the=20
        disclosure and summarize the WG discussion and conclusion on=20
        this issue.
No concerns or issues. No IPR disclosures.

  (1.e) How solid is the WG consensus behind this document? Does it=20
        represent the strong concurrence of a few individuals, with=20
        others being silent, or does the WG as a whole understand and=20
        agree with it?
There is strong consensus, and furthermore the WG is using these requiremen=
ts to guide its work on solution.

  (1.f) Has anyone threatened an appeal or otherwise indicated extreme=20
        discontent? If so, please summarise the areas of conflict in=20
        separate email messages to the Responsible Area Director. (It=20
        should be in a separate email because this questionnaire is=20
        entered into the ID Tracker.)
No

  (1.g) Has the Document Shepherd personally verified that the=20
        document satisfies all ID nits? (See the Internet-Drafts Checklist=
=20
        and http://tools.ietf.org/tools/idnits/). Boilerplate checks are=20
        not enough; this check needs to be thorough. Has the document=20
        met all formal review criteria it needs to, such as the MIB=20
        Doctor, media type and URI type reviews?
The document passes IDNITS. Other reviews such as MIB Doctor are not applic=
able.

  (1.h) Has the document split its references into normative and=20
        informative? Are there normative references to documents that=20
        are not ready for advancement or are otherwise in an unclear=20
        state? If such normative references exist, what is the=20
        strategy for their completion? Are there normative references=20
        that are downward references, as described in [RFC3967]? If=20
        so, list these downward references to support the Area=20
        Director in the Last Call procedure for them [RFC3967].
There are only normative references - no informative. All normative referen=
ces are published RFCs and there are no downward references.

  (1.i) Has the Document Shepherd verified that the document IANA=20
        consideration section exists and is consistent with the body=20
        of the document? If the document specifies protocol=20
        extensions, are reservations requested in appropriate IANA=20
        registries? Are the IANA registries clearly identified? If=20
        the document creates a new registry, does it define the=20
        proposed initial contents of the registry and an allocation=20
        procedure for future registrations? Does it suggest a=20
        reasonable name for the new registry? See [RFC5226]. If the=20
        document describes an Expert Review process has Shepherd=20
        conferred with the Responsible Area Director so that the IESG=20
        can appoint the needed Expert during the IESG Evaluation?
IANA section exists - there are no IANA actions.

  (1.j) Has the Document Shepherd verified that sections of the=20
        document that are written in a formal language, such as XML=20
        code, BNF rules, MIB definitions, etc., validate correctly in=20
        an automated checker?
Not applicable.

  (1.k) The IESG approval announcement includes a Document=20
        Announcement Write-Up. Please provide such a Document=20
        Announcement Write-Up? Recent examples can be found in the
        "Action" announcements for approved documents. The approval=20
        announcement contains the following sections:
     Technical Summary=20
        Relevant content can frequently be found in the abstract=20
        and/or introduction of the document. If not, this may be=20
        an indication that there are deficiencies in the abstract=20
        or introduction.
This document summarizes the requirements for a SIP-based mechanism for con=
trolling a session (media) recorder, taking into account any special securi=
ty or privacy considerations as well as the distinction between the session=
 that is being recorded and the session established for the purpose of reco=
rding.

     Working Group Summary=20
        Was there anything in WG process that is worth noting? For=20
        example, was there controversy about particular points or=20
        were there decisions where the consensus was particularly=20
        rough?
There were no particularly controversial issues, although significant time =
was spent working on requirements relating to privacy and notifications.
=20
     Document Quality=20
        Are there existing implementations of the protocol? Have a=20
        significant number of vendors indicated their plan to=20
        implement the specification? Are there any reviewers that=20
        merit special mention as having done a thorough review,=20
        e.g., one that resulted in important changes or a=20
        conclusion that the document had no substantive issues? If=20
        there was a MIB Doctor, Media Type or other expert review,=20
        what was its course (briefly)? In the case of a Media Type=20
        review, on what date was the request posted?=20
The document has been reviewed by participants within the IETF SIPREC WG, i=
ncluding representatives from traditional SIP vendors as well as from sessi=
on recording vendors.

John
=20

From rmohanr@cisco.com  Mon Mar 14 11:01:35 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9687B3A6E46 for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 11:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.055
X-Spam-Level: 
X-Spam-Status: No, score=-10.055 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-Ll4Nir9HXZ for <siprec@core3.amsl.com>; Mon, 14 Mar 2011 11:01:34 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 5797A3A6E3F for <siprec@ietf.org>; Mon, 14 Mar 2011 11:01:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=2190; q=dns/txt; s=iport; t=1300125778; x=1301335378; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=L7dC32FAuFr1zio9pqkNqkT9xfaGfR9iymSJL1Z+dz4=; b=exR51+HlduRO+8hqr7K3fUKL5ktsFWLhrhFNdWmnOJffx0yeGo4NeK4Q i+cJRnbqjTNign0MzGrFuKi+tYR+C3AFNIQ0iRETIwDKubLFDD1wduBq7 zW4qFjRsdXDviRmQ1LIhrg3yA9FzdwdLimh6msIYov8VBv3I6Ii2mOggJ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuIAAPf0fU2Q/khLgWdsb2JhbACYRI1GFAEBFiYlpBmcGoViBIUpin0
X-IronPort-AV: E=Sophos;i="4.62,317,1297036800"; d="scan'208";a="21660120"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 14 Mar 2011 18:02:57 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2EI2ut8016102; Mon, 14 Mar 2011 18:02:57 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Mar 2011 23:32:56 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Mar 2011 23:32:53 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD05A7E88B@XMB-BGL-417.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJcITDA
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>, "Leon Portman" <Leon.Portman@nice.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Ken Rehor (krehor)" <krehor@cisco.com>
X-OriginalArrivalTime: 14 Mar 2011 18:02:56.0265 (UTC) FILETIME=[0BD1F790:01CBE272]
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Mar 2011 18:01:35 -0000

Here are some of my comments on draft-ietf-siprec-architecture.=20

Section 2(Definitions)- The definitions of SRS, SRC, RS, CS is different
in Requirement (ver 08) and Architecture drafts. Please update the
Architecture draft to reflect the same as Requirement or better remove
from architecture as we already have reference to Requirement doc here.
Only additional definitions not present in Requirement but used in
Architecture draft can be included here.

Section 2(Definitions)- The definition of Recording aware UA needs to be
edited as it does not seem to meet REQ-16, 17 and 19

Section 2(Definitions)- Requirement draft already has a definition for
Metadata. Do we need this MRM(Media recording Metadata) ?

Section 4.1.5 - If possible please add a figure here showing the
architecture where SRC is Focus.

Section 4.2 - Paragraph 2 needs to be edited to make it sync with REQ-24
of requirement draft

Section 4.2.4 - There is a typo on the 5th line "recoding server".

Section 4.3.1 - Do we need this section with all the points now ? Since
we have separate draft(s), would it be better to just have a few lines
and then reference this draft. Note, I am not sure if its right to
reference a draft (for the reason Leon mentioned on Circular references)

Section 4.4 - First line here may need change as we have concluded on
other means of notifying recording (like visual indications e.t.c)


Regards,
Ram

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Elwell, John
> Sent: Wednesday, March 02, 2011 10:26 PM
> To: siprec@ietf.org
> Subject: [siprec] Progressing the architecture document
>=20
> draft-ietf-siprec-architecture has not moved forward much in recent
> months, waiting for progress on solutions to help confirm the
> architecture. Now would be an excellent time for people to raise any
> issues that can perhaps be addressed by the editor before the cut-off
> (2011-03-14) or discussed in Prague.
>=20
> John
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From Leon.Portman@nice.com  Tue Mar 15 00:16:44 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54DBD3A6C1F for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 00:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[AWL=-1.080, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PHy1aW84DJ+N for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 00:16:41 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 8CD753A6C1E for <siprec@ietf.org>; Tue, 15 Mar 2011 00:16:38 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.15]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Tue, 15 Mar 2011 09:18:01 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Tue, 15 Mar 2011 09:18:00 +0200
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IAB3KkqA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A8BB32F6@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: multipart/alternative; boundary="_000_07465C1D981ABC41A344374066AE1A2C38A8BB32F6TLVMBX01nicec_"
MIME-Version: 1.0
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 07:16:44 -0000

--_000_07465C1D981ABC41A344374066AE1A2C38A8BB32F6TLVMBX01nicec_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Partha Hi

Thank you very much for the comments. I will start working on the revised v=
ersion

Leon

From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Parthasarathi R (partr)
Sent: Monday, March 14, 2011 7:05 PM
To: Elwell, John; siprec@ietf.org
Subject: Re: [siprec] Progressing the architecture document

SIPREC Architecture-01 draft looks good in the high level. Some of the mino=
r comments are as follows:

Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be preferred to =
indicate that SRC also has AS & MS clubbed together. IMO, this provide more=
 clarity while reading.

Sec 4.1.5 Figure shall be added to indicate a scenarion whererin focus acts=
 as SRC.

Sec 4.2 Para 2 example does not go inline with REQ-024 of -07 Requirement d=
raft. The example shall change from "client must decrypt" to "client may de=
crypt".

Sec 4.2.1 Fourth bullet text may be preferred to change as "Indicate suppor=
t for the recording metadata"

Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or "sendonly as it =
is indicated as SRS and SRC in the beginning of the line.

Sec 4.3.1 1st bullet shall be changed from "Dialog identifier" to "Communic=
ation Session Identifier"

Sec 4.3.1 whether 3rd bullet is required?

General comment: it is preferred to change to "should, must" to "SHOULD, MU=
ST" as per RFC 2119

Sec 4.3.2 1st bullet has to be removed as it is not required any more.

Sec 4.3.2 3rd bullet has to be changed to indicate XML package instead of E=
vent package

Sec 4.3.2 last bullet: is it required to pass metadata using non-sip mechan=
ism?
Thanks
Partha

________________________________
From: siprec-bounces@ietf.org on behalf of Elwell, John
Sent: Wed 3/2/2011 10:25 PM
To: siprec@ietf.org
Subject: [siprec] Progressing the architecture document

draft-ietf-siprec-architecture has not moved forward much in recent months,=
 waiting for progress on solutions to help confirm the architecture. Now wo=
uld be an excellent time for people to raise any issues that can perhaps be=
 addressed by the editor before the cut-off (2011-03-14) or discussed in Pr=
ague.

John

_______________________________________________
siprec mailing list
siprec@ietf.org<mailto:siprec@ietf.org>
https://www.ietf.org/mailman/listinfo/siprec

--_000_07465C1D981ABC41A344374066AE1A2C38A8BB32F6TLVMBX01nicec_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#def=
ault#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><title>[siprec] Progressing the architecture document</=
title><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Partha Hi=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif";color:#1F497D'>Thank you very much for the comments. I will=
 start working on the revised version<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";col=
or:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Leon<o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p>=
<div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt=
 0cm 0cm 0cm'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-=
family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0=
pt;font-family:"Tahoma","sans-serif"'> siprec-bounces@ietf.org [mailto:sipr=
ec-bounces@ietf.org] <b>On Behalf Of </b>Parthasarathi R (partr)<br><b>Sent=
:</b> Monday, March 14, 2011 7:05 PM<br><b>To:</b> Elwell, John; siprec@iet=
f.org<br><b>Subject:</b> Re: [siprec] Progressing the architecture document=
<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
><div id=3DidOWAReplyText81337><div><p class=3DMsoNormal><span style=3D'fon=
t-size:10.0pt;font-family:"Arial","sans-serif";color:black'>SIPREC Architec=
ture-01&nbsp;draft looks good in the high level. Some of the minor comments=
 are as follows:</span><o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp=
;<o:p></o:p></p></div><div><p class=3DMsoNormal>Sec 4.1.4 Fig 3 indicates a=
bout SRS having AS &amp; MS, it may be preferred to indicate that SRC also =
has AS &amp; MS clubbed together. IMO, this provide more clarity while read=
ing.<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p></d=
iv><div><p class=3DMsoNormal>Sec 4.1.5 Figure shall be added to indicate a =
scenarion whererin focus acts as SRC.<o:p></o:p></p></div><div><p class=3DM=
soNormal>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal>Sec 4.2 Para =
2 example does not go inline with REQ-024 of -07 Requirement draft. The exa=
mple shall change from &quot;client must decrypt&quot; to &quot;client may =
decrypt&quot;.&nbsp; <o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;<=
o:p></o:p></p></div><div><p class=3DMsoNormal>Sec 4.2.1 Fourth bullet text =
may be preferred to change as &quot;Indicate support for the recording meta=
data&quot;<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;<o:p></o:p><=
/p></div><div><p class=3DMsoNormal>Sec 4.2.3 change &quot;sendonly&quot; or=
 &quot;recvonly&quot; to &quot;recvonly&quot; or &quot;sendonly as it is in=
dicated as SRS and SRC in the beginning of the line.<o:p></o:p></p></div><d=
iv><p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNorma=
l>Sec 4.3.1 1st bullet shall be changed from &quot;Dialog identifier&quot; =
to &quot;Communication Session Identifier&quot;<o:p></o:p></p></div><div><p=
 class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal>Sec=
 4.3.1 whether 3rd bullet is required? <o:p></o:p></p></div><div><p class=
=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal>General c=
omment: it is preferred to change to &quot;should, must&quot; to &quot;SHOU=
LD, MUST&quot; as per RFC 2119 <o:p></o:p></p></div><div><p class=3DMsoNorm=
al>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal>Sec 4.3.2 1st bulle=
t has to be removed as it is not required any more.<o:p></o:p></p></div><di=
v><p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal=
>Sec 4.3.2 3rd bullet has to be changed to indicate XML package instead of =
Event package<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;<o:p></o:=
p></p></div><div><p class=3DMsoNormal>Sec 4.3.2 last bullet: is it required=
 to pass metadata using non-sip mechanism?<o:p></o:p></p></div><div><p clas=
s=3DMsoNormal>Thanks<o:p></o:p></p></div><div><p class=3DMsoNormal>Partha<o=
:p></o:p></p></div></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><di=
v class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><hr size=3D2=
 width=3D"100%" align=3Dcenter></div><p class=3DMsoNormal style=3D'margin-b=
ottom:12.0pt'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans=
-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif"'> siprec-bounces@ietf.org on behalf of Elwell, John<br><b>S=
ent:</b> Wed 3/2/2011 10:25 PM<br><b>To:</b> siprec@ietf.org<br><b>Subject:=
</b> [siprec] Progressing the architecture document</span><o:p></o:p></p></=
div><div><p><span style=3D'font-size:10.0pt'>draft-ietf-siprec-architecture=
 has not moved forward much in recent months, waiting for progress on solut=
ions to help confirm the architecture. Now would be an excellent time for p=
eople to raise any issues that can perhaps be addressed by the editor befor=
e the cut-off (2011-03-14) or discussed in Prague.<br><br>John<br><br>_____=
__________________________________________<br>siprec mailing list<br><a hre=
f=3D"mailto:siprec@ietf.org">siprec@ietf.org</a><br><a href=3D"https://www.=
ietf.org/mailman/listinfo/siprec">https://www.ietf.org/mailman/listinfo/sip=
rec</a></span><o:p></o:p></p></div></div></body></html>=

--_000_07465C1D981ABC41A344374066AE1A2C38A8BB32F6TLVMBX01nicec_--

From Leon.Portman@nice.com  Tue Mar 15 00:18:18 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 864303A6C05 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 00:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRbQ0iJ8utp8 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 00:18:17 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 5E3443A6982 for <siprec@ietf.org>; Tue, 15 Mar 2011 00:18:17 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.15]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Tue, 15 Mar 2011 09:19:41 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "siprec@ietf.org" <siprec@ietf.org>,  "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Ken Rehor (krehor)" <krehor@cisco.com>
Date: Tue, 15 Mar 2011 09:19:40 +0200
Thread-Topic: [siprec] Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJcITDAAB2BvIA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A8BB32FB@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <35BCE99A477D6A4986FB2216D8CF2CFD05A7E88B@XMB-BGL-417.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD05A7E88B@XMB-BGL-417.cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 07:18:18 -0000

Ram=20

Thanks. We will publish update version

Leon

-----Original Message-----
From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]=20
Sent: Monday, March 14, 2011 8:03 PM
To: Elwell, John; siprec@ietf.org; Leon Portman; Hutton, Andrew; Ken Rehor =
(krehor)
Subject: RE: [siprec] Progressing the architecture document

Here are some of my comments on draft-ietf-siprec-architecture.=20

Section 2(Definitions)- The definitions of SRS, SRC, RS, CS is different in=
 Requirement (ver 08) and Architecture drafts. Please update the Architectu=
re draft to reflect the same as Requirement or better remove from architect=
ure as we already have reference to Requirement doc here.
Only additional definitions not present in Requirement but used in Architec=
ture draft can be included here.

Section 2(Definitions)- The definition of Recording aware UA needs to be ed=
ited as it does not seem to meet REQ-16, 17 and 19

Section 2(Definitions)- Requirement draft already has a definition for Meta=
data. Do we need this MRM(Media recording Metadata) ?

Section 4.1.5 - If possible please add a figure here showing the architectu=
re where SRC is Focus.

Section 4.2 - Paragraph 2 needs to be edited to make it sync with REQ-24 of=
 requirement draft

Section 4.2.4 - There is a typo on the 5th line "recoding server".

Section 4.3.1 - Do we need this section with all the points now ? Since we =
have separate draft(s), would it be better to just have a few lines and the=
n reference this draft. Note, I am not sure if its right to reference a dra=
ft (for the reason Leon mentioned on Circular references)

Section 4.4 - First line here may need change as we have concluded on other=
 means of notifying recording (like visual indications e.t.c)


Regards,
Ram

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> Behalf Of Elwell, John
> Sent: Wednesday, March 02, 2011 10:26 PM
> To: siprec@ietf.org
> Subject: [siprec] Progressing the architecture document
>=20
> draft-ietf-siprec-architecture has not moved forward much in recent=20
> months, waiting for progress on solutions to help confirm the=20
> architecture. Now would be an excellent time for people to raise any=20
> issues that can perhaps be addressed by the editor before the cut-off
> (2011-03-14) or discussed in Prague.
>=20
> John
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From john.elwell@siemens-enterprise.com  Tue Mar 15 01:36:54 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5E873A6C66 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 01:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 446URuy33Cit for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 01:36:53 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 749DD3A6C4E for <siprec@ietf.org>; Tue, 15 Mar 2011 01:36:53 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3733195 for siprec@ietf.org; Tue, 15 Mar 2011 09:37:57 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 60ADB1EB82AB for <siprec@ietf.org>; Tue, 15 Mar 2011 09:37:57 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Tue, 15 Mar 2011 09:37:57 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Tue, 15 Mar 2011 09:37:56 +0100
Thread-Topic: Adopt metadata model as WG item? (was RE: I-D Action:draft-ram-siprec-metadata-04.txt)
Thread-Index: Acvct15QEc+wcp2iQZWED2n/Bc8wrwAH9/HQAYUTm5A=
Message-ID: <A444A0F8084434499206E78C106220CA086A89B49C@MCHP058A.global-ad.net>
References: <20110307110004.10841.52270.idtracker@localhost> 
Keywords: SIPREC
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Adopt metadata model as WG item? (was RE: I-D Action:draft-ram-siprec-metadata-04.txt)
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 08:36:54 -0000

I heard no objection to adopting this draft in fulfilment of our milestone,=
 so I would like to ask Ram to act as editor for draft-ietf-siprec-metadata=
. It would be good to have an -00 as soon as submission opens again on 28th=
. It would be even better if we could get some discussion going on issues t=
hat need fixing in this document - we have some agenda time in Prague earma=
rked for this topic, if any significant issues arise.

John

> -----Original Message-----
> From: Elwell, John=20
> Sent: 07 March 2011 15:04
> To: siprec@ietf.org
> Subject: Adopt metadata model as WG item? (was RE: I-D=20
> Action:draft-ram-siprec-metadata-04.txt)
>=20
> Ram has posted this new version of the metadata model. He and=20
> his co-authors feel it is ready for consideration for=20
> adoption as a basis for our milestone "Submit metadata model=20
> to IESG as Informational RFC". The draft has been discussed=20
> during recent interim conference calls, as well as in=20
> Beijing, and the authors have endeavoured to take feedback=20
> into account. Adoption by the WG would bring the document=20
> under WG control. Minor concerns with the document can be=20
> dealt with during that phase. The important thing is that=20
> people are comfortable with the general approach before=20
> taking this step.
>=20
> Therefore, if anyone has any objection to adopting -04 as a=20
> basis for this milestone, please make your views known by 2011-03-14.
>=20
> John (as chair)
>=20
> > -----Original Message-----
> > From: i-d-announce-bounces@ietf.org=20
> > [mailto:i-d-announce-bounces@ietf.org] On Behalf Of=20
> > Internet-Drafts@ietf.org
> > Sent: 07 March 2011 11:00
> > To: i-d-announce@ietf.org
> > Subject: I-D Action:draft-ram-siprec-metadata-04.txt
> >=20
> > A New Internet-Draft is available from the on-line=20
> > Internet-Drafts directories.
> >=20
> > 	Title           : Session Initiation Protocol (SIP)=20
> > Recording Metadata
> > 	Author(s)       : R. R, et al.
> > 	Filename        : draft-ram-siprec-metadata-04.txt
> > 	Pages           : 23
> > 	Date            : 2011-03-07
> >=20
> > 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 the metadata model as
> > viewed by Session Recording Server(SRS).
> >=20
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ram-siprec-metadata-04.txt
> >=20
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >=20
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> > =

From john.elwell@siemens-enterprise.com  Tue Mar 15 04:40:45 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E7C33A6C78 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 04:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tN3Z9FSRuuWI for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 04:40:44 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id D134A3A6CB3 for <siprec@ietf.org>; Tue, 15 Mar 2011 04:40:43 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3735972; Tue, 15 Mar 2011 12:22:20 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 50E5A23F0290; Tue, 15 Mar 2011 12:22:15 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 15 Mar 2011 12:22:15 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Tue, 15 Mar 2011 12:22:13 +0100
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvgGWwDUZbHh0GvS1mlnsUp9RGXlAC6Fudg
Message-ID: <A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <4D7A6898.1060809@cisco.com>
In-Reply-To: <4D7A6898.1060809@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 11:40:45 -0000

=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: 11 March 2011 18:23
> To: siprec@ietf.org
> Subject: Re: [siprec] Review Request for=20
> draft-ram-siprec-metadata-format-01
>=20
>=20
>=20
> On 3/11/2011 9:49 AM, Elwell, John wrote:
> > Partha,
> >
> > I read -01 and have the following comments:
> >
> > 1. In section 3:
> > "The media related details of metadata SHALL be passed across using
> >     session description protocol (SDP) [RFC4566].  SDP attributes
> >     describes about different media formats like audio, video."
> > I wonder whether it is really appropriate to describe SDP=20
> attributes as part of the metadata. If I look at the metadata=20
> model, I don't see any attributes of a Media Stream object=20
> that could be satisfied using RS SDP. For example, the "codec=20
> parameters" attribute relates to the CS, not the RS - the two=20
> sessions could use different codecs or different codec=20
> parameters. I think it would be far simpler to regard all=20
> metadata as being sent in XML. Note that the SDP label=20
> attribute can still be used as the linkage between a Media=20
> Stream object in the metadata and the corresponding RS media=20
> stream that captures the CS media stream concerned.
>=20
> I think I agree with you here.
> The label reference in the xml, and the label in the sdp provide a=20
> linkage between the *meta*data and the *data*. Originally I=20
> was thinking=20
> that there would be some things in the sdp that were metadata, but so=20
> far that seems not to be true.
>=20
> > 2. We perhaps need to think about mixed RS media streams,=20
> i.e., where several CS media streams have been mixed to=20
> produce a single RS media stream. In this case, the several=20
> Media Stream objects would all point to the same SDP label, I=20
> guess. This then brings into question the mode element (type=20
> streamMode) - why is this needed? The fact that several Media=20
> Stream objects (stream elements) point to the same label=20
> would imply there has been mixing, so the mode element seems=20
> to be redundant.
>=20
> My thinking is that situation is modeled as a single media=20
> stream with=20
> multiple participants.
[JRE] I was confused by section 4.5 of the metadata model draft. It does in=
deed seem to say that it represents an RS media stream:
"A Media Stream block shall have properties of media as seen by SRC and sen=
t to SRS."
And hence your interpretation above would seem reasonable. On the other han=
d, in 4.5.2 it says:
"A Media Stream SHALL be associated with Participant and CS."
This misled me. Also in 4.5.1:
"Codec params - represents codec parameters of the CS media"
This also seemed to imply the Media Stream object relates to a CS media str=
eam.
Perhaps some clarification is needed in the Metadata draft.
Anyway, assuming we go with your interpretation, I suppose what we end up w=
ith is that if streams are mixed (whether this be at an MCU, say, or just p=
art of the SRC in order to send the streams to the SRS), the net result wil=
l be modelling as a single stream in the metadata. Is this a common underst=
anding?

John (as individual)

>=20
> 	Thanks,
> 	Paul
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From john.elwell@siemens-enterprise.com  Tue Mar 15 04:41:37 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1335C3A6D4F for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 04:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tdcmTo+NITP5 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 04:41:36 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id CE9B33A6D58 for <siprec@ietf.org>; Tue, 15 Mar 2011 04:41:35 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3736035; Tue, 15 Mar 2011 12:30:18 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 6F8AB1EB82C2; Tue, 15 Mar 2011 12:27:39 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Tue, 15 Mar 2011 12:27:39 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Tue, 15 Mar 2011 12:27:38 +0100
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvgGXSFwN7kntbSThSxDvrHQp54ZQAwj423AInpzKA=
Message-ID: <A444A0F8084434499206E78C106220CA086A89B57F@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <4D7A6898.1060809@cisco.com> <A11921905DA1564D9BCF64A6430A62390293A699@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A699@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 11:41:37 -0000

=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 12 March 2011 17:50
> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
> Subject: Re: [siprec] Review Request for=20
> draft-ram-siprec-metadata-format-01
>=20
> John/Paul,
> =20
> Please read inline.
> =20
> Thanks
> Partha
>=20
> ________________________________
>=20
> From: siprec-bounces@ietf.org on behalf of Paul Kyzivat (pkyzivat)
> Sent: Fri 3/11/2011 11:53 PM
> To: siprec@ietf.org
> Subject: Re: [siprec] Review Request for=20
> draft-ram-siprec-metadata-format-01
>=20
>=20
>=20
>=20
>=20
> On 3/11/2011 9:49 AM, Elwell, John wrote:
> > Partha,
> >
> > I read -01 and have the following comments:
> >
> > 1. In section 3:
> > "The media related details of metadata SHALL be passed across using
> >     session description protocol (SDP) [RFC4566].  SDP attributes
> >     describes about different media formats like audio, video."
> > I wonder whether it is really appropriate to describe SDP=20
> attributes as part of the metadata. If I look at the metadata=20
> model, I don't see any attributes of a Media Stream object=20
> that could be satisfied using RS SDP. For example, the "codec=20
> parameters" attribute relates to the CS, not the RS - the two=20
> sessions could use different codecs or different codec=20
> parameters. I think it would be far simpler to regard all=20
> metadata as being sent in XML. Note that the SDP label=20
> attribute can still be used as the linkage between a Media=20
> Stream object in the metadata and the corresponding RS media=20
> stream that captures the CS media stream concerned.
>=20
> I think I agree with you here.
> The label reference in the xml, and the label in the sdp provide a
> linkage between the *meta*data and the *data*. Originally I=20
> was thinking
> that there would be some things in the sdp that were metadata, but so
> far that seems not to be true.
>=20
> <Partha> I agree with the linkage part and CS codec=20
> parameters information in the model.  IMO, some of the=20
> information shall be retrieved from RS SDP=20
>=20
> 1) Media Type (Audio/Video)
[JRE] Yes, I agree this needs to form part of the metadata, which unfortuna=
tely breaks my proposed simplification (unless we duplicate the information=
 in the XML metadata).

>=20
> 2) In a unmixed stream, grouping of direction attribute in RS=20
> helps to understand that CS is in hold during the given time. =20
[JRE] I don't understand this. In the RS, I would only ever expect to see s=
endonly (from SSRC to SRS) or inactive. Inactive means recording is paused,=
 sendonly means recording is in progress. It says nothing about the held st=
ate of the CS, which would still need to be captured in XML metadata.

John (as individual)



>=20
> BTW, these information is possible to be passed in stream=20
> extension data but I thought that reusing the existing SDP=20
> framework may be preferred. I'm not very sure at this moment=20
> whether removing this text is appropriate. In case everyone=20
> feels that it is *data* and not *metadata*, I'll remove this=20
> sentence in the next revision. </Partha>
>=20
> > 2. We perhaps need to think about mixed RS media streams,=20
> i.e., where several CS media streams have been mixed to=20
> produce a single RS media stream. In this case, the several=20
> Media Stream objects would all point to the same SDP label, I=20
> guess. This then brings into question the mode element (type=20
> streamMode) - why is this needed? The fact that several Media=20
> Stream objects (stream elements) point to the same label=20
> would imply there has been mixing, so the mode element seems=20
> to be redundant.
>=20
> My thinking is that situation is modeled as a single media stream with
> multiple participants.
>=20
>         Thanks,
>         Paul
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20
>=20
> =

From partr@cisco.com  Tue Mar 15 04:49:24 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 578633A6CAA for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 04:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.055
X-Spam-Level: 
X-Spam-Status: No, score=-10.055 tagged_above=-999 required=5 tests=[AWL=0.544, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H7MldcvNoJ7p for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 04:49:20 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 60BB83A6C96 for <siprec@ietf.org>; Tue, 15 Mar 2011 04:49:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=4974; q=dns/txt; s=iport; t=1300189844; x=1301399444; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=W/HVWrsm9iUdq1M2nsQwrn0SR6u0hWsgToS9LIfqWgY=; b=QUEtWLU51rc3Hhgo71o3d8UNYfr/4fvVkQKi8JRmBnDZ4qVciELUl3Mm IOB3PSsPTBPu4GU4KQjaAhB/nxMJv4XCORg2kZhLxhUIbwsmxHTT3sZrp SrMNTzQ5oY+Ww5ZsPNZPvFto4UlZKSgSqA2kmQAayEYCIXtaXJMqV/lRY g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYAAL7vfk2Q/khLgWdsb2JhbACYSo1FFAEBFiYlpWidBoViBIUuiwQ
X-IronPort-AV: E=Sophos;i="4.62,322,1297036800"; d="scan'208";a="21772081"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 15 Mar 2011 11:50:43 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2FBog4c022003; Tue, 15 Mar 2011 11:50:43 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Mar 2011 17:20:42 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Mar 2011 17:20:41 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904BE3583@XMB-BGL-411.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A89B57F@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvgGXSFwN7kntbSThSxDvrHQp54ZQAwj423AInpzKAAAL9wQA==
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com> <A11921905DA1564D9BCF64A6430A62390293A699@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89B57F@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 15 Mar 2011 11:50:42.0265 (UTC) FILETIME=[3621C490:01CBE307]
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 11:49:24 -0000

John,

Please read inline.

Thanks
Partha=20

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Tuesday, March 15, 2011 4:58 PM
To: Parthasarathi R (partr); Paul Kyzivat (pkyzivat); siprec@ietf.org
Subject: RE: [siprec] Review Request for
draft-ram-siprec-metadata-format-01

=20

> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 12 March 2011 17:50
> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
> Subject: Re: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>=20
> John/Paul,
> =20
> Please read inline.
> =20
> Thanks
> Partha
>=20
> ________________________________
>=20
> From: siprec-bounces@ietf.org on behalf of Paul Kyzivat (pkyzivat)
> Sent: Fri 3/11/2011 11:53 PM
> To: siprec@ietf.org
> Subject: Re: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>=20
>=20
>=20
>=20
>=20
> On 3/11/2011 9:49 AM, Elwell, John wrote:
> > Partha,
> >
> > I read -01 and have the following comments:
> >
> > 1. In section 3:
> > "The media related details of metadata SHALL be passed across using
> >     session description protocol (SDP) [RFC4566].  SDP attributes
> >     describes about different media formats like audio, video."
> > I wonder whether it is really appropriate to describe SDP
> attributes as part of the metadata. If I look at the metadata model, I

> don't see any attributes of a Media Stream object that could be=20
> satisfied using RS SDP. For example, the "codec parameters" attribute=20
> relates to the CS, not the RS - the two sessions could use different=20
> codecs or different codec parameters. I think it would be far simpler=20
> to regard all metadata as being sent in XML. Note that the SDP label=20
> attribute can still be used as the linkage between a Media Stream=20
> object in the metadata and the corresponding RS media stream that=20
> captures the CS media stream concerned.
>=20
> I think I agree with you here.
> The label reference in the xml, and the label in the sdp provide a=20
> linkage between the *meta*data and the *data*. Originally I was=20
> thinking that there would be some things in the sdp that were=20
> metadata, but so far that seems not to be true.
>=20
> <Partha> I agree with the linkage part and CS codec parameters=20
> information in the model.  IMO, some of the information shall be=20
> retrieved from RS SDP
>=20
> 1) Media Type (Audio/Video)
[JRE] Yes, I agree this needs to form part of the metadata, which
unfortunately breaks my proposed simplification (unless we duplicate the
information in the XML metadata).

>=20
> 2) In a unmixed stream, grouping of direction attribute in RS helps to

> understand that CS is in hold during the given time.
[JRE] I don't understand this. In the RS, I would only ever expect to
see sendonly (from SSRC to SRS) or inactive. Inactive means recording is
paused, sendonly means recording is in progress. It says nothing about
the held state of the CS, which would still need to be captured in XML
metadata.

<partha> I agree by looking at the single m-line, it will only evident
whether the recording is paused or not. In case of unmixed audio stream,
there are two m-lines, each m-line is associated with one participant
and SRS shall interpret the information from 2 m-line as follows:

1) Two m-lines have "sendonly" then the recording is in progress
2) Two m-lines have "inactive" then the recording is paused or call hold
3) One m-line have "sendonly", other m-line have "inactive" indicates
the service like music on hold.
</partha>

John (as individual)



>=20
> BTW, these information is possible to be passed in stream extension=20
> data but I thought that reusing the existing SDP framework may be=20
> preferred. I'm not very sure at this moment whether removing this text

> is appropriate. In case everyone feels that it is *data* and not=20
> *metadata*, I'll remove this sentence in the next revision. </Partha>
>=20
> > 2. We perhaps need to think about mixed RS media streams,
> i.e., where several CS media streams have been mixed to produce a=20
> single RS media stream. In this case, the several Media Stream objects

> would all point to the same SDP label, I guess. This then brings into=20
> question the mode element (type
> streamMode) - why is this needed? The fact that several Media Stream=20
> objects (stream elements) point to the same label would imply there=20
> has been mixing, so the mode element seems to be redundant.
>=20
> My thinking is that situation is modeled as a single media stream with

> multiple participants.
>=20
>         Thanks,
>         Paul
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20
>=20
>=20

From pkyzivat@cisco.com  Tue Mar 15 06:01:18 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 075B13A6D10 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 06:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level: 
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SwwO9Bs8YMty for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 06:01:15 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 784D63A6BC3 for <siprec@ietf.org>; Tue, 15 Mar 2011 06:01:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=2361; q=dns/txt; s=iport; t=1300194160; x=1301403760; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=5YaTOHPSfxBCdJBnrtHVPGQ/6aWU/F9vBEcdG7wOu5o=; b=immZ7YhQiisxi05Thawwti9SXLHUxHUzYj2zik9a6r3qeWLE7AqljmKa 9TjUSv/OuoW9T0iG6getbxtZrn822ajZTFAwMtjE873FC9WCocmtupM/N 5JYFnU4lKKMhrHC2QPyXeIjfO0/zNM2M9j0LF7b8apsg7OvB661ebwGu7 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJ4Af02tJV2a/2dsb2JhbACmD3elOZ0BhWIEjF2DTw
X-IronPort-AV: E=Sophos;i="4.62,322,1297036800"; d="scan'208";a="225752157"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rtp-iport-2.cisco.com with ESMTP; 15 Mar 2011 13:02:40 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2FD2dqK030832;  Tue, 15 Mar 2011 13:02:39 GMT
Message-ID: <4D7F636F.5060105@cisco.com>
Date: Tue, 15 Mar 2011 09:02:39 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com>	<A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <4D7A6898.1060809@cisco.com> <A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 13:01:18 -0000

On 3/15/2011 7:22 AM, Elwell, John wrote:

>>> 2. We perhaps need to think about mixed RS media streams,
>> i.e., where several CS media streams have been mixed to
>> produce a single RS media stream. In this case, the several
>> Media Stream objects would all point to the same SDP label, I
>> guess. This then brings into question the mode element (type
>> streamMode) - why is this needed? The fact that several Media
>> Stream objects (stream elements) point to the same label
>> would imply there has been mixing, so the mode element seems
>> to be redundant.
>>
>> My thinking is that situation is modeled as a single media
>> stream with
>> multiple participants.
> [JRE] I was confused by section 4.5 of the metadata model draft. It does indeed seem to say that it represents an RS media stream:
> "A Media Stream block shall have properties of media as seen by SRC and sent to SRS."
> And hence your interpretation above would seem reasonable. On the other hand, in 4.5.2 it says:
> "A Media Stream SHALL be associated with Participant and CS."
> This misled me. Also in 4.5.1:
> "Codec params - represents codec parameters of the CS media"
> This also seemed to imply the Media Stream object relates to a CS media stream.
> Perhaps some clarification is needed in the Metadata draft.
> Anyway, assuming we go with your interpretation, I suppose what we end up with is that if streams are mixed (whether this be at an MCU, say, or just part of the SRC in order to send the streams to the SRS), the net result will be modelling as a single stream in the metadata. Is this a common understanding?

You may have a point here - that things are somewhat ambiguous.

If we have two distinct media streams in the CS, and they are mixed 
together by the SRC before sending to the SRS, then they could be 
treated different ways:

- The SRC could report this as a single media stream with multiple 
participants. But then it would have to report its metadata as if it 
were a single stream from a mixer.

- The SRC could report it as multiple media streams from a metadata 
perspective, but map them all onto the same RS media stream. (This is a 
possibility I had never considered/recognized.)

Is there a desire to support both? If so, the metamodel and mechanism 
will probably need some tweaking.

	Thanks,
	Paul

From john.elwell@siemens-enterprise.com  Tue Mar 15 06:56:00 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 833113A6D16 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 06:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00o1hm-OxLH6 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 06:55:59 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 2E5463A6D27 for <siprec@ietf.org>; Tue, 15 Mar 2011 06:55:58 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3739254; Tue, 15 Mar 2011 14:56:17 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 9FE8223F0278; Tue, 15 Mar 2011 14:56:17 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Tue, 15 Mar 2011 14:56:17 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Date: Tue, 15 Mar 2011 14:56:17 +0100
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvjEUSsHcJ38+GcQ7elOYlEMOVDqwAByJ8w
Message-ID: <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net> <4D7A6898.1060809@cisco.com> <A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net> <4D7F636F.5060105@cisco.com>
In-Reply-To: <4D7F636F.5060105@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 13:56:00 -0000

=20

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
> Sent: 15 March 2011 13:03
> To: Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Review Request for=20
> draft-ram-siprec-metadata-format-01
>=20
> On 3/15/2011 7:22 AM, Elwell, John wrote:
>=20
> >>> 2. We perhaps need to think about mixed RS media streams,
> >> i.e., where several CS media streams have been mixed to
> >> produce a single RS media stream. In this case, the several
> >> Media Stream objects would all point to the same SDP label, I
> >> guess. This then brings into question the mode element (type
> >> streamMode) - why is this needed? The fact that several Media
> >> Stream objects (stream elements) point to the same label
> >> would imply there has been mixing, so the mode element seems
> >> to be redundant.
> >>
> >> My thinking is that situation is modeled as a single media
> >> stream with
> >> multiple participants.
> > [JRE] I was confused by section 4.5 of the metadata model=20
> draft. It does indeed seem to say that it represents an RS=20
> media stream:
> > "A Media Stream block shall have properties of media as=20
> seen by SRC and sent to SRS."
> > And hence your interpretation above would seem reasonable.=20
> On the other hand, in 4.5.2 it says:
> > "A Media Stream SHALL be associated with Participant and CS."
> > This misled me. Also in 4.5.1:
> > "Codec params - represents codec parameters of the CS media"
> > This also seemed to imply the Media Stream object relates=20
> to a CS media stream.
> > Perhaps some clarification is needed in the Metadata draft.
> > Anyway, assuming we go with your interpretation, I suppose=20
> what we end up with is that if streams are mixed (whether=20
> this be at an MCU, say, or just part of the SRC in order to=20
> send the streams to the SRS), the net result will be=20
> modelling as a single stream in the metadata. Is this a=20
> common understanding?
>=20
> You may have a point here - that things are somewhat ambiguous.
>=20
> If we have two distinct media streams in the CS, and they are mixed=20
> together by the SRC before sending to the SRS, then they could be=20
> treated different ways:
>=20
> - The SRC could report this as a single media stream with multiple=20
> participants. But then it would have to report its metadata as if it=20
> were a single stream from a mixer.
>=20
> - The SRC could report it as multiple media streams from a metadata=20
> perspective, but map them all onto the same RS media stream.=20
> (This is a=20
> possibility I had never considered/recognized.)
>=20
> Is there a desire to support both? If so, the metamodel and mechanism=20
> will probably need some tweaking.
[JRE] Consider:
"REQ-009: The mechanism MUST support the ability for an SRC to
   deliver mixed audio streams from different parties of a given
   Communication Session to an SRS."
One particular case I believe this covers is the simple 2-party call, where=
 there are two media streams, one from A to B and the other from B to A. Th=
e SRC could mix the two together into a single stream to the SRS. Certainly=
 useful for bandwidth constrained environments, but not so friendly towards=
 speech analytics.

John (as individual)


>=20
> 	Thanks,
> 	Paul
> =

From andrew.hutton@siemens-enterprise.com  Tue Mar 15 08:59:04 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F96D3A6D76 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 08:59:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id psbeNdI3wCgt for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 08:59:03 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id F08063A6D81 for <siprec@ietf.org>; Tue, 15 Mar 2011 08:59:02 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3757958; Tue, 15 Mar 2011 17:00:26 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 7B3B11EB82B4; Tue, 15 Mar 2011 17:00:26 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Tue, 15 Mar 2011 17:00:26 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>
Date: Tue, 15 Mar 2011 17:00:25 +0100
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWA=
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 15:59:04 -0000

Hi Partha,

Thanks for your comments.

See below.

Regards
Andy
=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 14 March 2011 17:05
> To: Elwell, John; siprec@ietf.org
> Subject: Re: [siprec] Progressing the architecture document
>=20
> SIPREC Architecture-01 draft looks good in the high level.=20
> Some of the minor comments are as follows:
> =20
> Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be=20
> preferred to indicate that SRC also has AS & MS clubbed=20
> together. IMO, this provide more clarity while reading.

[AndyH] The related text does state that the SRC could also be decomposed i=
n this way and Fig 3. is just one example. I think the figure showing the S=
RS better illustrates the relation to mediactrl with regard to recording so=
 I prefer the current diagram. Why do you think the showing the SRC in this=
 way would add clarity? I could of course include both but not sure this is=
 really necessary.

> =20
> Sec 4.1.5 Figure shall be added to indicate a scenarion=20
> whererin focus acts as SRC.

[AndyH] I will look at creating a diagram.

> =20
> Sec 4.2 Para 2 example does not go inline with REQ-024 of -07=20
> Requirement draft. The example shall change from "client must=20
> decrypt" to "client may decrypt". =20

[AndyH] I think I have to remove the whole sentence as the example is no lo=
nger valid.

> =20
> Sec 4.2.1 Fourth bullet text may be preferred to change as=20
> "Indicate support for the recording metadata"

[AndyH] Have we decided whether we have any indication from the SRC that it=
 supports metadata? I did not think so therefore this is an open issue but =
probably not relevant to the architecture draft. I probably should remove t=
he mechanism related stuff and at some point reference the protocol draft. =
Do you agree?

> =20
> Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or=20
> "sendonly as it is indicated as SRS and SRC in the beginning=20
> of the line.

[AndyH] Done.

> =20
> Sec 4.3.1 1st bullet shall be changed from "Dialog=20
> identifier" to "Communication Session Identifier"

[AndyH] Note sure about this the current text states "Dialog identifiers fo=
r the Communication Session" which seems correct to me. This will probably =
get removed anyway and replaced to a reference to the metadata model when i=
t is adopted.

> =20
> Sec 4.3.1 whether 3rd bullet is required?=20
> =20

[AndyH]I assume it is as for example I assume it would be necessary to reco=
rd early-media and update the SRS when the dialog changes to the confirmed =
or terminated state. Does not seem to be in the metadata draft though. In t=
he end I will either remove these bullets or align with the metadata draft.


> General comment: it is preferred to change to "should, must"=20
> to "SHOULD, MUST" as per RFC 2119=20

[AndyH]I think I need to remove all RFC 2119 wording as it is not appropria=
te to the architecture draft. I will remove all such wording and the refere=
nce to RFC 2119. Is that ok ?

> =20
> Sec 4.3.2 1st bullet has to be removed as it is not required any more.
> =20
[AndyH]OK are there really no information in SIP Headers that could be stor=
ed as metadata?

> Sec 4.3.2 3rd bullet has to be changed to indicate XML=20
> package instead of Event package

[AndyH] Noted. I will need to review this once we have adopted the protocol=
 draft and make sure it is aligned.

> =20
> Sec 4.3.2 last bullet: is it required to pass metadata using=20
> non-sip mechanism?
>=20
[AndyH] I will remove this statement if that is ok with everyone.


> Thanks
> Partha
>=20
> ________________________________
>=20
> From: siprec-bounces@ietf.org on behalf of Elwell, John
> Sent: Wed 3/2/2011 10:25 PM
> To: siprec@ietf.org
> Subject: [siprec] Progressing the architecture document
>=20
>=20
>=20
> draft-ietf-siprec-architecture has not moved forward much in=20
> recent months, waiting for progress on solutions to help=20
> confirm the architecture. Now would be an excellent time for=20
> people to raise any issues that can perhaps be addressed by=20
> the editor before the cut-off (2011-03-14) or discussed in Prague.
>=20
> John
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20
>=20
> =

From partr@cisco.com  Tue Mar 15 17:08:49 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 471AF3A6BA1 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 17:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.225
X-Spam-Level: 
X-Spam-Status: No, score=-8.225 tagged_above=-999 required=5 tests=[AWL=-1.323, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MBRTT0pCj5a1 for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 17:08:47 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 1B3553A6A4E for <siprec@ietf.org>; Tue, 15 Mar 2011 17:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=14506; q=dns/txt; s=iport; t=1300234212; x=1301443812; h=mime-version:subject:date:message-id:references:from:to: cc; bh=I7YBSEu3ePZMGFBxtK3eBiqlokGP9Ge2mtH6o08+MCk=; b=kb830SupVNgq2BMzFcrgexBd+QBxbqESyatxZO2WB/7/0cAPNxUamM89 eiN1HVGmizMWWnrxISgowIwhpbfL6UoJUgsgh0fAHpRozKQRDDGoXie+v SbkLT1sGLLT+m2C7Lba1wvJknuvbYb+Tk2DQvfjxOjuosBRf5qmfhe9iJ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlMEADmdf02Q/khNgWdsb2JhbAClOFUUAQEWJiWkUZxnhWIEhS6LBA
X-IronPort-AV: E=Sophos;i="4.63,191,1299456000"; d="scan'208,217";a="21860284"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 16 Mar 2011 00:10:10 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2G0A9LF005997; Wed, 16 Mar 2011 00:10:10 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Mar 2011 05:40:09 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE36E.82D57B16"
Date: Wed, 16 Mar 2011 05:40:09 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAw==
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 16 Mar 2011 00:10:09.0789 (UTC) FILETIME=[833CAAD0:01CBE36E]
Cc: siprec@ietf.org
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 00:08:49 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE36E.82D57B16
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Andy,
=20
Please read inline.=20
=20
Thanks
Partha

________________________________

From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
Sent: Tue 3/15/2011 9:30 PM
To: Parthasarathi R (partr)
Cc: Elwell, John; siprec@ietf.org
Subject: RE: Progressing the architecture document



Hi Partha,

Thanks for your comments.

See below.

Regards
Andy


> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 14 March 2011 17:05
> To: Elwell, John; siprec@ietf.org
> Subject: Re: [siprec] Progressing the architecture document
>
> SIPREC Architecture-01 draft looks good in the high level.
> Some of the minor comments are as follows:
>=20
> Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be
> preferred to indicate that SRC also has AS & MS clubbed
> together. IMO, this provide more clarity while reading.

[AndyH] The related text does state that the SRC could also be =
decomposed in this way and Fig 3. is just one example. I think the =
figure showing the SRS better illustrates the relation to mediactrl with =
regard to recording so I prefer the current diagram. Why do you think =
the showing the SRC in this way would add clarity? I could of course =
include both but not sure this is really necessary.

<Partha> I know of the call center deployment wherein SRC decomposed as =
AS and MS. So, I thought that it may help others to understand the =
arhcitecture from that perspective. </Partha>=20

>=20
> Sec 4.1.5 Figure shall be added to indicate a scenarion
> whererin focus acts as SRC.

[AndyH] I will look at creating a diagram.

>=20
> Sec 4.2 Para 2 example does not go inline with REQ-024 of -07
> Requirement draft. The example shall change from "client must
> decrypt" to "client may decrypt".=20

[AndyH] I think I have to remove the whole sentence as the example is no =
longer valid.

>=20
> Sec 4.2.1 Fourth bullet text may be preferred to change as
> "Indicate support for the recording metadata"

[AndyH] Have we decided whether we have any indication from the SRC that =
it supports metadata? I did not think so therefore this is an open issue =
but probably not relevant to the architecture draft. I probably should =
remove the mechanism related stuff and at some point reference the =
protocol draft. Do you agree?

<Partha> Agreed </Partha>

>=20
> Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or
> "sendonly as it is indicated as SRS and SRC in the beginning
> of the line.

[AndyH] Done.

>=20
> Sec 4.3.1 1st bullet shall be changed from "Dialog
> identifier" to "Communication Session Identifier"

[AndyH] Note sure about this the current text states "Dialog identifiers =
for the Communication Session" which seems correct to me. This will =
probably get removed anyway and replaced to a reference to the metadata =
model when it is adopted.

>=20
> Sec 4.3.1 whether 3rd bullet is required?
>=20

[AndyH]I assume it is as for example I assume it would be necessary to =
record early-media and update the SRS when the dialog changes to the =
confirmed or terminated state. Does not seem to be in the metadata draft =
though. In the end I will either remove these bullets or align with the =
metadata draft.
<Partha> It is a good point. Dialog state shall be added as one of the =
optional attribute in CS metadata block with default value as =
mid-dialog. This helps to differentiate between early dialog (ringback) =
vs mid-dialog (normal conversation) in recording. In case of no =
objection for this attribute in metadata model, we will add it. We will =
work out metadata format once the consensus occurs for metadata model. =
In case required, we will span separate mail thread to close this issue =
</Partha>

> General comment: it is preferred to change to "should, must"
> to "SHOULD, MUST" as per RFC 2119

[AndyH]I think I need to remove all RFC 2119 wording as it is not =
appropriate to the architecture draft. I will remove all such wording =
and the reference to RFC 2119. Is that ok ?

<Partha> It is fine </Partha>

>=20
> Sec 4.3.2 1st bullet has to be removed as it is not required any more.
>=20
[AndyH]OK are there really no information in SIP Headers that could be =
stored as metadata?

<partha> AFAIK, there is no metadata information is passed in RS session =
SIP header, SIP header have information about SRC & SRS only and few =
information is possible to be retrieved from SDP which is under =
discussion in another mail thread with John. In case you foresee any =
specific SIP header to act as metadata, Please let me know. <Partha> =20

> Sec 4.3.2 3rd bullet has to be changed to indicate XML
> package instead of Event package

[AndyH] Noted. I will need to review this once we have adopted the =
protocol draft and make sure it is aligned.

>=20
> Sec 4.3.2 last bullet: is it required to pass metadata using
> non-sip mechanism?
>
[AndyH] I will remove this statement if that is ok with everyone.

<Partha> In case you foresee this requirement, Please start separate =
mail thread as there are lot of implication in metadata format draft. =
The current metadata format draft is designed for SIP and not for other =
protocols </Partha>


> Thanks
> Partha
>
> ________________________________
>
> From: siprec-bounces@ietf.org on behalf of Elwell, John
> Sent: Wed 3/2/2011 10:25 PM
> To: siprec@ietf.org
> Subject: [siprec] Progressing the architecture document
>
>
>
> draft-ietf-siprec-architecture has not moved forward much in
> recent months, waiting for progress on solutions to help
> confirm the architecture. Now would be an excellent time for
> people to raise any issues that can perhaps be addressed by
> the editor before the cut-off (2011-03-14) or discussed in Prague.
>
> John
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>
>
>



------_=_NextPart_001_01CBE36E.82D57B16
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: Progressing the architecture =
document</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText89739>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>Hi =
Andy,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Please read inline. =
</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> Hutton, Andrew =
[mailto:andrew.hutton@siemens-enterprise.com]<BR><B>Sent:</B> Tue =
3/15/2011 9:30 PM<BR><B>To:</B> Parthasarathi R (partr)<BR><B>Cc:</B> =
Elwell, John; siprec@ietf.org<BR><B>Subject:</B> RE: Progressing the =
architecture document<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi Partha,<BR><BR>Thanks for your comments.<BR><BR>See =
below.<BR><BR>Regards<BR>Andy<BR><BR><BR>&gt; -----Original =
Message-----<BR>&gt; From: siprec-bounces@ietf.org<BR>&gt; [<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>] On Behalf Of Parthasarathi R (partr)<BR>&gt; Sent: 14 March 2011 =
17:05<BR>&gt; To: Elwell, John; siprec@ietf.org<BR>&gt; Subject: Re: =
[siprec] Progressing the architecture document<BR>&gt;<BR>&gt; SIPREC =
Architecture-01 draft looks good in the high level.<BR>&gt; Some of the =
minor comments are as follows:<BR>&gt;&nbsp;<BR>&gt; Sec 4.1.4 Fig 3 =
indicates about SRS having AS &amp; MS, it may be<BR>&gt; preferred to =
indicate that SRC also has AS &amp; MS clubbed<BR>&gt; together. IMO, =
this provide more clarity while reading.<BR><BR>[AndyH] The related text =
does state that the SRC could also be decomposed in this way and Fig 3. =
is just one example. I think the figure showing the SRS better =
illustrates the relation to mediactrl with regard to recording so I =
prefer the current diagram. Why do you think the showing the SRC in this =
way would add clarity? I could of course include both but not sure this =
is really necessary.</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt;&nbsp;I know of the call center =
deployment wherein&nbsp;SRC decomposed as AS and MS.&nbsp;So, I thought =
that it may help others to understand the arhcitecture from that =
perspective. &lt;/Partha&gt;&nbsp;<BR><BR>&gt;&nbsp;<BR>&gt; Sec 4.1.5 =
Figure shall be added to indicate a scenarion<BR>&gt; whererin focus =
acts as SRC.<BR><BR>[AndyH] I will look at creating a =
diagram.<BR><BR>&gt;&nbsp;<BR>&gt; Sec 4.2 Para 2 example does not go =
inline with REQ-024 of -07<BR>&gt; Requirement draft. The example shall =
change from "client must<BR>&gt; decrypt" to "client may =
decrypt".&nbsp;<BR><BR>[AndyH] I think I have to remove the whole =
sentence as the example is no longer valid.<BR><BR>&gt;&nbsp;<BR>&gt; =
Sec 4.2.1 Fourth bullet text may be preferred to change as<BR>&gt; =
"Indicate support for the recording metadata"<BR><BR>[AndyH] Have we =
decided whether we have any indication from the SRC that it supports =
metadata? I did not think so therefore this is an open issue but =
probably not relevant to the architecture draft. I probably should =
remove the mechanism related stuff and at some point reference the =
protocol draft. Do you agree?</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; Agreed =
&lt;/Partha&gt;<BR><BR>&gt;&nbsp;<BR>&gt; Sec 4.2.3 change "sendonly" or =
"recvonly" to "recvonly" or<BR>&gt; "sendonly as it is indicated as SRS =
and SRC in the beginning<BR>&gt; of the line.<BR><BR>[AndyH] =
Done.<BR><BR>&gt;&nbsp;<BR>&gt; Sec 4.3.1 1st bullet shall be changed =
from "Dialog<BR>&gt; identifier" to "Communication Session =
Identifier"<BR><BR>[AndyH] Note sure about this the current text states =
"Dialog identifiers for the Communication Session" which seems correct =
to me. This will probably get removed anyway and replaced to a reference =
to the metadata model when it is adopted.<BR><BR>&gt;&nbsp;<BR>&gt; Sec =
4.3.1 whether 3rd bullet is required?<BR>&gt;&nbsp;<BR><BR>[AndyH]I =
assume it is as for example I assume it would be necessary to record =
early-media and update the SRS when the dialog changes to the confirmed =
or terminated state. Does not seem to be in the metadata draft though. =
In the end I will either remove these bullets or align with the metadata =
draft.<BR>&lt;Partha&gt; It is a good point. Dialog state shall be added =
as one of the&nbsp;optional&nbsp;attribute in CS metadata block with =
default value as mid-dialog. This helps to differentiate between early =
dialog (ringback) vs mid-dialog (normal conversation) in recording. In =
case of no objection for this attribute in metadata model, we will add =
it. We will work out metadata format once the consensus occurs for =
metadata model. In case required, we will span separate mail thread to =
close this issue &lt;/Partha&gt;<BR><BR>&gt; General comment: it is =
preferred to change to "should, must"<BR>&gt; to "SHOULD, MUST" as per =
RFC 2119<BR><BR>[AndyH]I think I need to remove all RFC 2119 wording as =
it is not appropriate to the architecture draft. I will remove all such =
wording and the reference to RFC 2119. Is that ok ?</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; It is fine =
&lt;/Partha&gt;<BR><BR>&gt;&nbsp;<BR>&gt; Sec 4.3.2 1st bullet has to be =
removed as it is not required any more.<BR>&gt;&nbsp;<BR>[AndyH]OK are =
there really no information in SIP Headers that could be stored as =
metadata?</FONT></P>=0A=
<P><FONT size=3D2>&lt;partha&gt; AFAIK, there is no =
metadata&nbsp;information&nbsp;is passed&nbsp;in RS session SIP =
header,&nbsp;SIP header have information about SRC &amp; SRS only and =
few information is possible to be retrieved from SDP which is under =
discussion in another mail thread with John. In case you foresee any =
specific SIP&nbsp;header to act as metadata, Please let me know. =
&lt;Partha&gt;&nbsp;&nbsp;<BR><BR>&gt; Sec 4.3.2 3rd bullet has to be =
changed to indicate XML<BR>&gt; package instead of Event =
package<BR><BR>[AndyH] Noted. I will need to review this once we have =
adopted the protocol draft and make sure it is =
aligned.<BR><BR>&gt;&nbsp;<BR>&gt; Sec 4.3.2 last bullet: is it required =
to pass metadata using<BR>&gt; non-sip mechanism?<BR>&gt;<BR>[AndyH] I =
will remove this statement if that is ok with everyone.</FONT></P>=0A=
<P><FONT size=3D2>&lt;Partha&gt; In case you foresee this requirement, =
Please start separate mail thread as there are lot of implication in =
metadata format draft. The current metadata format draft is designed for =
SIP and not for other protocols &lt;/Partha&gt;<BR><BR><BR>&gt; =
Thanks<BR>&gt; Partha<BR>&gt;<BR>&gt; =
________________________________<BR>&gt;<BR>&gt; From: =
siprec-bounces@ietf.org on behalf of Elwell, John<BR>&gt; Sent: Wed =
3/2/2011 10:25 PM<BR>&gt; To: siprec@ietf.org<BR>&gt; Subject: [siprec] =
Progressing the architecture document<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; =
draft-ietf-siprec-architecture has not moved forward much in<BR>&gt; =
recent months, waiting for progress on solutions to help<BR>&gt; confirm =
the architecture. Now would be an excellent time for<BR>&gt; people to =
raise any issues that can perhaps be addressed by<BR>&gt; the editor =
before the cut-off (2011-03-14) or discussed in Prague.<BR>&gt;<BR>&gt; =
John<BR>&gt;<BR>&gt; =
_______________________________________________<BR>&gt; siprec mailing =
list<BR>&gt; siprec@ietf.org<BR>&gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR>&gt;<BR>&gt;<BR>&gt;<BR></P></FONT></DIV=
></BODY></HTML>
------_=_NextPart_001_01CBE36E.82D57B16--

From partr@cisco.com  Tue Mar 15 18:23:28 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50C003A69DA for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 18:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.331
X-Spam-Level: 
X-Spam-Status: No, score=-9.331 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TnzTvbqv5elP for <siprec@core3.amsl.com>; Tue, 15 Mar 2011 18:23:26 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id D88583A69C3 for <siprec@ietf.org>; Tue, 15 Mar 2011 18:23:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=13263; q=dns/txt; s=iport; t=1300238692; x=1301448292; h=mime-version:subject:date:message-id:references:from:to: cc; bh=mvTZRlhBp9zSGbDJw1sCqlfbtRwiEQx6+3Vx4WAaSmg=; b=AnKNU7VjcD4ud5ajwcLeLzRMtocuKZCwa9ZAJCdRIiMCHLSpM7UC+6V/ xI1TDV+8EHHbo9eETlewt5XcBeHNh3EihP/Otz7BHbBhD2XI00CXvpri1 7JbILG7dsqKuOYBdNAlddQhSRP04MhwWEjL2OOtZjuK2Y7jZMn9lWRzHf U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlMEAA+uf02Q/khMgWdsb2JhbAClOlUUAQEWJiWkSpxngnuCZwSFLosE
X-IronPort-AV: E=Sophos;i="4.63,191,1299456000"; d="scan'208,217";a="79350684"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 16 Mar 2011 01:24:50 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2G1OnLs025273; Wed, 16 Mar 2011 01:24:50 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Mar 2011 06:54:49 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE378.F1115785"
Date: Wed, 16 Mar 2011 06:54:49 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CS Codec Parameter in stream XML element [was RE: [siprec] Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: AcvjEUSsHcJ38+GcQ7elOYlEMOVDqwAByJ8wABcEx28=
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com> <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 16 Mar 2011 01:24:49.0478 (UTC) FILETIME=[F156F660:01CBE378]
Cc: siprec@ietf.org
Subject: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 01:23:28 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE378.F1115785
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John,
=20
Please read inline.
=20
Thanks
Partha

________________________________

From: siprec-bounces@ietf.org on behalf of Elwell, John
Sent: Tue 3/15/2011 7:26 PM
To: Paul Kyzivat (pkyzivat)
Cc: siprec@ietf.org
Subject: Re: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01





> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: 15 March 2011 13:03
> To: Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
> On 3/15/2011 7:22 AM, Elwell, John wrote:
>
> >>> 2. We perhaps need to think about mixed RS media streams,
> >> i.e., where several CS media streams have been mixed to
> >> produce a single RS media stream. In this case, the several
> >> Media Stream objects would all point to the same SDP label, I
> >> guess. This then brings into question the mode element (type
> >> streamMode) - why is this needed? The fact that several Media
> >> Stream objects (stream elements) point to the same label
> >> would imply there has been mixing, so the mode element seems
> >> to be redundant.
> >>
> >> My thinking is that situation is modeled as a single media
> >> stream with
> >> multiple participants.
> > [JRE] I was confused by section 4.5 of the metadata model
> draft. It does indeed seem to say that it represents an RS
> media stream:
> > "A Media Stream block shall have properties of media as
> seen by SRC and sent to SRS."

<Partha> Metadata model support this mechanism.  </Partha>
> > And hence your interpretation above would seem reasonable.
> On the other hand, in 4.5.2 it says:
> > "A Media Stream SHALL be associated with Participant and CS."
> > This misled me. Also in 4.5.1:
> > "Codec params - represents codec parameters of the CS media"
> > This also seemed to imply the Media Stream object relates
> to a CS media stream.

<Partha> It is the assumption done during metadata format that RS SDP =
may be used as Codec params for stream. Please note that format draft =
does not have codec param in stream metadata element. But the assumption =
does not seems to be working for all scenarios. So we need to find the =
way to represent CS Media stream in metadata format.

Even before going into approach, I'm interested in knowing whether it is =
required for SRS to understand the exact codec or SDP parameter used in =
CS? RS may be transcoded/transrated and lost the actual media =
information when it reaches SRS but the question is whether it is =
required to maintain the metadata in SRS even though media (RTP) is =
changed to new format ?=20

In case we decide to pass CS codec parameter to SRS. Two approaches =
exist to solve this issue:

1) Tunnel complete each participant SDP inside stream element using some =
new optional XML element. This approach is straightforward and scale for =
any CS as we are sending the complete set. The overhead will be =
increased in SRS to parse and store appropriately.

2) Identify the list of codec parameters *MUST*  be passed from SRC to =
SRS and create the new XML element for them. This is simple to implement =
as only portion of the SDP is passed across but *may* have scalability =
issue.

I prefer 1st approach because it covers all scenarios. I'm interested in =
hearing from you which way to go.

</partha>


> > Perhaps some clarification is needed in the Metadata draft.
> > Anyway, assuming we go with your interpretation, I suppose
> what we end up with is that if streams are mixed (whether
> this be at an MCU, say, or just part of the SRC in order to
> send the streams to the SRS), the net result will be
> modelling as a single stream in the metadata. Is this a
> common understanding?
>
> You may have a point here - that things are somewhat ambiguous.
>
> If we have two distinct media streams in the CS, and they are mixed
> together by the SRC before sending to the SRS, then they could be
> treated different ways:
>
> - The SRC could report this as a single media stream with multiple
> participants. But then it would have to report its metadata as if it
> were a single stream from a mixer.
>
> - The SRC could report it as multiple media streams from a metadata
> perspective, but map them all onto the same RS media stream.
> (This is a
> possibility I had never considered/recognized.)
>
> Is there a desire to support both? If so, the metamodel and mechanism
> will probably need some tweaking.
[JRE] Consider:
"REQ-009: The mechanism MUST support the ability for an SRC to
   deliver mixed audio streams from different parties of a given
   Communication Session to an SRS."
One particular case I believe this covers is the simple 2-party call, =
where there are two media streams, one from A to B and the other from B =
to A. The SRC could mix the two together into a single stream to the =
SRS. Certainly useful for bandwidth constrained environments, but not so =
friendly towards speech analytics.

John (as individual)


>
>       Thanks,
>       Paul
>
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec



------_=_NextPart_001_01CBE378.F1115785
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText98512>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 =
face=3DArial>John,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Please read =
inline.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> siprec-bounces@ietf.org on =
behalf of Elwell, John<BR><B>Sent:</B> Tue 3/15/2011 7:26 =
PM<BR><B>To:</B> Paul Kyzivat (pkyzivat)<BR><B>Cc:</B> =
siprec@ietf.org<BR><B>Subject:</B> Re: [siprec] Review Request for =
draft-ram-siprec-metadata-format-01<BR></FONT><BR></DIV>=0A=
<DIV><BR><FONT size=3D2>=0A=
<P><BR><BR>&gt; -----Original Message-----<BR>&gt; From: Paul Kyzivat =
[<A =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</A>]<BR>&gt;=
 Sent: 15 March 2011 13:03<BR>&gt; To: Elwell, John<BR>&gt; Cc: =
siprec@ietf.org<BR>&gt; Subject: Re: [siprec] Review Request for<BR>&gt; =
draft-ram-siprec-metadata-format-01<BR>&gt;<BR>&gt; On 3/15/2011 7:22 =
AM, Elwell, John wrote:<BR>&gt;<BR>&gt; &gt;&gt;&gt; 2. We perhaps need =
to think about mixed RS media streams,<BR>&gt; &gt;&gt; i.e., where =
several CS media streams have been mixed to<BR>&gt; &gt;&gt; produce a =
single RS media stream. In this case, the several<BR>&gt; &gt;&gt; Media =
Stream objects would all point to the same SDP label, I<BR>&gt; &gt;&gt; =
guess. This then brings into question the mode element (type<BR>&gt; =
&gt;&gt; streamMode) - why is this needed? The fact that several =
Media<BR>&gt; &gt;&gt; Stream objects (stream elements) point to the =
same label<BR>&gt; &gt;&gt; would imply there has been mixing, so the =
mode element seems<BR>&gt; &gt;&gt; to be redundant.<BR>&gt; =
&gt;&gt;<BR>&gt; &gt;&gt; My thinking is that situation is modeled as a =
single media<BR>&gt; &gt;&gt; stream with<BR>&gt; &gt;&gt; multiple =
participants.<BR>&gt; &gt; [JRE] I was confused by section 4.5 of the =
metadata model<BR>&gt; draft. It does indeed seem to say that it =
represents an RS<BR>&gt; media stream:<BR>&gt; &gt; "A Media Stream =
block shall have properties of media as<BR>&gt; seen by SRC and sent to =
SRS."</P>=0A=
<P>&lt;Partha&gt; Metadata model support this =
mechanism.&nbsp;&nbsp;&lt;/Partha&gt;<BR>&gt; &gt; And hence your =
interpretation above would seem reasonable.<BR>&gt; On the other hand, =
in 4.5.2 it says:<BR>&gt; &gt; "A Media Stream SHALL be associated with =
Participant and CS."<BR>&gt; &gt; This misled me. Also in 4.5.1:<BR>&gt; =
&gt; "Codec params - represents codec parameters of the CS =
media"<BR>&gt; &gt; This also seemed to imply the Media Stream object =
relates<BR>&gt; to a CS media stream.</P>=0A=
<DIV>=0A=
<P><FONT size=3D2 face=3DArial>&lt;Partha&gt; It is the assumption done =
during metadata format that RS SDP may be used as Codec params for =
stream. Please note that format draft does not have codec param in =
stream metadata element.&nbsp;But&nbsp;the assumption does not seems to =
be&nbsp;working for all scenarios. So we need to find the way to =
represent CS Media stream in metadata format.</FONT></P>=0A=
<P><FONT size=3D2 face=3DArial>Even before going into approach, I'm =
interested in knowing whether it is required for SRS to understand the =
exact codec or SDP parameter used in CS? RS may be transcoded/transrated =
and lost the actual<SPAN class=3D316001201-16032011> =
media</SPAN>&nbsp;information when it reaches SRS but the question is =
whether it is required to maintain the metadata in SRS even though media =
(RTP) is changed to new format ? </FONT></P>=0A=
<P><FONT size=3D2 face=3DArial>In case we decide to&nbsp;<SPAN =
class=3D316001201-16032011>pass</SPAN> CS&nbsp;<SPAN =
class=3D316001201-16032011>codec</SPAN> parameter<SPAN =
class=3D316001201-16032011> to SRS</SPAN>.&nbsp;<SPAN =
class=3D316001201-16032011>Two</SPAN> approaches exist to solve this =
issue:</FONT></P>=0A=
<P><FONT size=3D2 face=3DArial>1) Tunnel complete each participant SDP =
inside stream element using some new optional XML element. This approach =
is straightforward and scale for any CS as we are sending the complete =
set. The overhead will be increased in SRS to parse and store =
appropriately.</FONT></P>=0A=
<P><FONT size=3D2 face=3DArial>2) Identify the list of codec =
parameters&nbsp;*MUST*&nbsp; be passed from SRC to SRS and create the =
new XML element for them. This is simple to implement as only portion of =
the SDP is passed across but *may* have scalability issue.</FONT></P>=0A=
<P><FONT size=3D2 face=3DArial>I prefer 1st approach because it covers =
all scenarios. I'm interested in hearing&nbsp;<SPAN =
class=3D316001201-16032011>from you </SPAN>which way to go.</FONT></P>=0A=
<P><FONT size=3D2 face=3DArial>&lt;/partha&gt;<BR></FONT></P></DIV>=0A=
<P>&gt; &gt; Perhaps some clarification is needed in the Metadata =
draft.<BR>&gt; &gt; Anyway, assuming we go with your interpretation, I =
suppose<BR>&gt; what we end up with is that if streams are mixed =
(whether<BR>&gt; this be at an MCU, say, or just part of the SRC in =
order to<BR>&gt; send the streams to the SRS), the net result will =
be<BR>&gt; modelling as a single stream in the metadata. Is this =
a<BR>&gt; common understanding?<BR>&gt;<BR>&gt; You may have a point =
here - that things are somewhat ambiguous.<BR>&gt;<BR>&gt; If we have =
two distinct media streams in the CS, and they are mixed<BR>&gt; =
together by the SRC before sending to the SRS, then they could =
be<BR>&gt; treated different ways:<BR>&gt;<BR>&gt; - The SRC could =
report this as a single media stream with multiple<BR>&gt; participants. =
But then it would have to report its metadata as if it<BR>&gt; were a =
single stream from a mixer.<BR>&gt;<BR>&gt; - The SRC could report it as =
multiple media streams from a metadata<BR>&gt; perspective, but map them =
all onto the same RS media stream.<BR>&gt; (This is a<BR>&gt; =
possibility I had never considered/recognized.)<BR>&gt;<BR>&gt; Is there =
a desire to support both? If so, the metamodel and mechanism<BR>&gt; =
will probably need some tweaking.<BR>[JRE] Consider:<BR>"REQ-009: The =
mechanism MUST support the ability for an SRC to<BR>&nbsp;&nbsp; deliver =
mixed audio streams from different parties of a given<BR>&nbsp;&nbsp; =
Communication Session to an SRS."<BR>One particular case I believe this =
covers is the simple 2-party call, where there are two media streams, =
one from A to B and the other from B to A. The SRC could mix the two =
together into a single stream to the SRS. Certainly useful for bandwidth =
constrained environments, but not so friendly towards speech =
analytics.<BR><BR>John (as individual)<BR><BR><BR>&gt;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Paul<BR>&gt;<BR>_______________________________________________<BR>siprec=
 mailing list<BR>siprec@ietf.org<BR><A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR></P></FONT></DIV></BODY></HTML>
------_=_NextPart_001_01CBE378.F1115785--

From john.elwell@siemens-enterprise.com  Wed Mar 16 00:32:48 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6FE83A6822 for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 00:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ej1sCBbYtsvW for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 00:32:47 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 8750D3A6820 for <siprec@ietf.org>; Wed, 16 Mar 2011 00:32:47 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3757437; Wed, 16 Mar 2011 08:34:12 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 263081EB82AB; Wed, 16 Mar 2011 08:34:12 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 16 Mar 2011 08:34:12 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
Date: Wed, 16 Mar 2011 08:34:10 +0100
Thread-Topic: CS Codec Parameter in stream XML element [was RE: [siprec] Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: AcvjEUSsHcJ38+GcQ7elOYlEMOVDqwAByJ8wABcEx28ADWDC4A==
Message-ID: <A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com> <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 07:32:49 -0000

=20

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]=20
> Sent: 16 March 2011 01:25
> To: Elwell, John; Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: CS Codec Parameter in stream XML element [was RE:=20
> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
>=20
<snip/>
> <Partha> It is the assumption done during metadata format=20
> that RS SDP may be used as Codec params for stream. Please=20
> note that format draft does not have codec param in stream=20
> metadata element. But the assumption does not seems to be=20
> working for all scenarios. So we need to find the way to=20
> represent CS Media stream in metadata format.
>=20
> Even before going into approach, I'm interested in knowing=20
> whether it is required for SRS to understand the exact codec=20
> or SDP parameter used in CS? RS may be transcoded/transrated=20
> and lost the actual media information when it reaches SRS but=20
> the question is whether it is required to maintain the=20
> metadata in SRS even though media (RTP) is changed to new format ?=20
>=20
> In case we decide to pass CS codec parameter to SRS. Two=20
> approaches exist to solve this issue:
>=20
> 1) Tunnel complete each participant SDP inside stream element=20
> using some new optional XML element. This approach is=20
> straightforward and scale for any CS as we are sending the=20
> complete set. The overhead will be increased in SRS to parse=20
> and store appropriately.
>=20
> 2) Identify the list of codec parameters *MUST*  be passed=20
> from SRC to SRS and create the new XML element for them. This=20
> is simple to implement as only portion of the SDP is passed=20
> across but *may* have scalability issue.
>=20
> I prefer 1st approach because it covers all scenarios. I'm=20
> interested in hearing from you which way to go.
>=20
> </partha>
[JRE] I was basing my earlier comment on the fact that the metadata model s=
eems to indicate that the Media Stream object has CS codec parameters as an=
 attribute. This is indeed questionable. I seem to remember somebody wantin=
g this at some stage in the past. From my point of view, I don't think this=
 information is needed by the SRS - it is historic information, nothing to =
do with the media actually sent to the SRS, and of no use to the SRS, in my=
 opinion.

If people do think there is a reason for providing this information to the =
SRS, I don't think I would favour approach 1) above. The SDP could potentia=
lly contain all sorts of information other than codecs (codecs are only a s=
mall part, and the SDP will contain information like IP addresses, ports, s=
ecurity keys!!!, transport, non-recorded media descriptions (e.g., MSRP cha=
nnel, BFCP channel), format parameters, SDP capability negotiation attribut=
es, etc..

Moreover, the offerer and answerer might have agreed several codecs in the =
SDP, so you need to look at RTP to see which codec is actually used. This c=
an change on the fly.

Finally, although the SRS's SIP/SDP stack will surely have and SDP parser, =
the XML metadata is intended for passing to an application. Requiring that =
application to contain an SDP parser is, I think, unreasonable.

So I have doubts as to whether it is really feasible to provide CS codec in=
formation in metadata to the SRS in a meaningful way, whether this be using=
 approach 1) or approach 2), but I particularly dislike approach 1).

John (as individual)=

From partr@cisco.com  Wed Mar 16 02:18:38 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C3733A6822 for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 02:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.026
X-Spam-Level: 
X-Spam-Status: No, score=-10.026 tagged_above=-999 required=5 tests=[AWL=0.573, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VneDls5Hyr+x for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 02:18:37 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 5A8F73A68C8 for <siprec@ietf.org>; Wed, 16 Mar 2011 02:18:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=4840; q=dns/txt; s=iport; t=1300267203; x=1301476803; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=NLnhBfXiCc6Knx/SnON0uo+PWjBp+/HH5+/GDzLTYxo=; b=K0/Hrc2i0dgOsCnChpd/W+BXJx3ENUXMdM8SWZNodO+ywhUYQ8Ya+kCd eoQ6YLSxm8bulE5Kht9SyiTOsaXh3Ri15CynUhT/FuAFOd2olLn71+2Hz fD/it2jvF9tft+O7BefoEXbBRC5JdukDC1iQ/ZKwnKUD5pX1wvcRvGRHt k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvkAAGIdgE2Q/khMgWdsb2JhbACYUI03FAEBFiYlpEqcUYJ7gmcEhS2LBA
X-IronPort-AV: E=Sophos;i="4.63,193,1299456000"; d="scan'208";a="79406271"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 16 Mar 2011 09:20:02 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2G9JCKS019937; Wed, 16 Mar 2011 09:20:01 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Mar 2011 14:49:44 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 16 Mar 2011 14:49:41 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904BE38E7@XMB-BGL-411.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CS Codec Parameter in stream XML element [was RE: [siprec] Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: AcvjEUSsHcJ38+GcQ7elOYlEMOVDqwAByJ8wABcEx28ADWDC4AACcQyQ
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com> <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>
X-OriginalArrivalTime: 16 Mar 2011 09:19:44.0110 (UTC) FILETIME=[4976C0E0:01CBE3BB]
Cc: siprec@ietf.org
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 09:18:38 -0000

Hi John,

Please read inline.

Including Leon in this mail thread as he provided the comment in the
same area.

Thanks
Partha=20

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Wednesday, March 16, 2011 1:04 PM
To: Parthasarathi R (partr); Paul Kyzivat (pkyzivat)
Cc: siprec@ietf.org
Subject: RE: CS Codec Parameter in stream XML element [was RE: [siprec]
Review Request for draft-ram-siprec-metadata-format-01]

=20

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 16 March 2011 01:25
> To: Elwell, John; Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: CS Codec Parameter in stream XML element [was RE:=20
> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
>=20
<snip/>
> <Partha> It is the assumption done during metadata format that RS SDP=20
> may be used as Codec params for stream. Please note that format draft=20
> does not have codec param in stream metadata element. But the=20
> assumption does not seems to be working for all scenarios. So we need=20
> to find the way to represent CS Media stream in metadata format.
>=20
> Even before going into approach, I'm interested in knowing whether it=20
> is required for SRS to understand the exact codec or SDP parameter=20
> used in CS? RS may be transcoded/transrated and lost the actual media=20
> information when it reaches SRS but the question is whether it is=20
> required to maintain the metadata in SRS even though media (RTP) is=20
> changed to new format ?
>=20
> In case we decide to pass CS codec parameter to SRS. Two approaches=20
> exist to solve this issue:
>=20
> 1) Tunnel complete each participant SDP inside stream element using=20
> some new optional XML element. This approach is straightforward and=20
> scale for any CS as we are sending the complete set. The overhead will

> be increased in SRS to parse and store appropriately.
>=20
> 2) Identify the list of codec parameters *MUST*  be passed from SRC to

> SRS and create the new XML element for them. This is simple to=20
> implement as only portion of the SDP is passed across but *may* have=20
> scalability issue.
>=20
> I prefer 1st approach because it covers all scenarios. I'm interested=20
> in hearing from you which way to go.
>=20
> </partha>
[JRE] I was basing my earlier comment on the fact that the metadata
model seems to indicate that the Media Stream object has CS codec
parameters as an attribute. This is indeed questionable. I seem to
remember somebody wanting this at some stage in the past. From my point
of view, I don't think this information is needed by the SRS - it is
historic information, nothing to do with the media actually sent to the
SRS, and of no use to the SRS, in my opinion.

<Partha> I'm of the same opinion as yours as I really didn't get the
exact requirement to keep CS metadata only and not CS original
data(media). Some of my guessed requirements are

1) CS with High Density (HD) video/audio but recording with Low
density(LD) video/audio codec for saving the bandwidth/storage. During
retrieval, somebody may be interested in knowing whether the original
communication is HD or LD

2) SRS may not support the codec which CS is using but during retrieval
process, it may required for weird reason to understand the original CS
codec. This may extended for packetization time of the codec. (Simple
Transcoding & transrating scenario).=20

Let us get more clarity/reason for passing information before proceeding
to the approach. IMO, this parameter shall be removed in case there is
no strong requirement to pass across </Partha>

If people do think there is a reason for providing this information to
the SRS, I don't think I would favour approach 1) above. The SDP could
potentially contain all sorts of information other than codecs (codecs
are only a small part, and the SDP will contain information like IP
addresses, ports, security keys!!!, transport, non-recorded media
descriptions (e.g., MSRP channel, BFCP channel), format parameters, SDP
capability negotiation attributes, etc..

Moreover, the offerer and answerer might have agreed several codecs in
the SDP, so you need to look at RTP to see which codec is actually used.
This can change on the fly.

Finally, although the SRS's SIP/SDP stack will surely have and SDP
parser, the XML metadata is intended for passing to an application.
Requiring that application to contain an SDP parser is, I think,
unreasonable.

So I have doubts as to whether it is really feasible to provide CS codec
information in metadata to the SRS in a meaningful way, whether this be
using approach 1) or approach 2), but I particularly dislike approach
1).

John (as individual)

From pkyzivat@cisco.com  Wed Mar 16 06:31:43 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25DF43A6954 for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 06:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqm0fwLMXCH5 for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 06:31:41 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 581933A6995 for <siprec@ietf.org>; Wed, 16 Mar 2011 06:31:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=3785; q=dns/txt; s=iport; t=1300282388; x=1301491988; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=bWGDTgkViid/ZNBneH8KNuhHMe9poaKel/yjLSgU7Qo=; b=Ct2I3+masUWYGfVANj38lCh1NCdKlJlojJXmYQmlhmonZnNq/gPNuoOE g+aS9Ww081SJ7chZfCj0uWnom7R7ebxWDYm40KboLnWG7wqCZeWcm0s8d lntD2d6C6TOtga7ldpE3+8vDTZNu+CVBiuko91lp1CU6n4XFWYFKW2PtZ A=;
X-IronPort-AV: E=Sophos;i="4.63,194,1299456000"; d="scan'208";a="21956435"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 16 Mar 2011 13:33:07 +0000
Received: from [10.86.242.29] (che-vpn-cluster-2-29.cisco.com [10.86.242.29]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2GDX6Mx001514; Wed, 16 Mar 2011 13:33:06 GMT
Message-ID: <4D80BC11.206@cisco.com>
Date: Wed, 16 Mar 2011 09:33:05 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com> <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 13:31:43 -0000

I believe the codec parameters on the MS have been there since my first 
cut at the metadata model. Putting them there was just speculation on my 
part, and doesn't imply any actual need known to me.

If nobody feels they are necessary, then by all means remove them.

	Thanks,
	Paul

On 3/16/2011 3:34 AM, Elwell, John wrote:
>
>
>> -----Original Message-----
>> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
>> Sent: 16 March 2011 01:25
>> To: Elwell, John; Paul Kyzivat (pkyzivat)
>> Cc: siprec@ietf.org
>> Subject: CS Codec Parameter in stream XML element [was RE:
>> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
>>
> <snip/>
>> <Partha>  It is the assumption done during metadata format
>> that RS SDP may be used as Codec params for stream. Please
>> note that format draft does not have codec param in stream
>> metadata element. But the assumption does not seems to be
>> working for all scenarios. So we need to find the way to
>> represent CS Media stream in metadata format.
>>
>> Even before going into approach, I'm interested in knowing
>> whether it is required for SRS to understand the exact codec
>> or SDP parameter used in CS? RS may be transcoded/transrated
>> and lost the actual media information when it reaches SRS but
>> the question is whether it is required to maintain the
>> metadata in SRS even though media (RTP) is changed to new format ?
>>
>> In case we decide to pass CS codec parameter to SRS. Two
>> approaches exist to solve this issue:
>>
>> 1) Tunnel complete each participant SDP inside stream element
>> using some new optional XML element. This approach is
>> straightforward and scale for any CS as we are sending the
>> complete set. The overhead will be increased in SRS to parse
>> and store appropriately.
>>
>> 2) Identify the list of codec parameters *MUST*  be passed
>> from SRC to SRS and create the new XML element for them. This
>> is simple to implement as only portion of the SDP is passed
>> across but *may* have scalability issue.
>>
>> I prefer 1st approach because it covers all scenarios. I'm
>> interested in hearing from you which way to go.
>>
>> </partha>
> [JRE] I was basing my earlier comment on the fact that the metadata model seems to indicate that the Media Stream object has CS codec parameters as an attribute. This is indeed questionable. I seem to remember somebody wanting this at some stage in the past. From my point of view, I don't think this information is needed by the SRS - it is historic information, nothing to do with the media actually sent to the SRS, and of no use to the SRS, in my opinion.
>
> If people do think there is a reason for providing this information to the SRS, I don't think I would favour approach 1) above. The SDP could potentially contain all sorts of information other than codecs (codecs are only a small part, and the SDP will contain information like IP addresses, ports, security keys!!!, transport, non-recorded media descriptions (e.g., MSRP channel, BFCP channel), format parameters, SDP capability negotiation attributes, etc..
>
> Moreover, the offerer and answerer might have agreed several codecs in the SDP, so you need to look at RTP to see which codec is actually used. This can change on the fly.
>
> Finally, although the SRS's SIP/SDP stack will surely have and SDP parser, the XML metadata is intended for passing to an application. Requiring that application to contain an SDP parser is, I think, unreasonable.
>
> So I have doubts as to whether it is really feasible to provide CS codec information in metadata to the SRS in a meaningful way, whether this be using approach 1) or approach 2), but I particularly dislike approach 1).
>
> John (as individual)

From Leon.Portman@nice.com  Wed Mar 16 08:44:15 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E5933A69BE for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 08:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrtpvYR-kAOV for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 08:44:14 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 6E9E83A6937 for <siprec@ietf.org>; Wed, 16 Mar 2011 08:44:13 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Wed, 16 Mar 2011 17:45:36 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Wed, 16 Mar 2011 17:45:35 +0200
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXg
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com> <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net> <4D80BC11.206@cisco.com>
In-Reply-To: <4D80BC11.206@cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 15:44:15 -0000

I agree with points below that passing actual CS SDP to SRS is a not good i=
dea from security and layers separation point of view.
Today's SRS implementations(at least that I know about) do not keep origina=
l codec information in the database for later retrieval. I am trying to thi=
nk about use cases why SRS can be interested in one, and except troubleshoo=
ting it is not very relevant.=20
The main assumption is that SRC inspected CS SDP and extracted all relevant=
 information like ip addresses, media line labels and infos and reported it=
 to SRS via metadata.

The main reason as I see if we want to be able to report CS SDP via metadat=
a is for the case where SRS wants to sniff RS RTP packets directly and not =
by forking from SRC but it is out of scope.

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Paul Kyzivat
Sent: Wednesday, March 16, 2011 3:33 PM
To: Elwell, John
Cc: siprec@ietf.org
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Rev=
iew Request for draft-ram-siprec-metadata-format-01]

I believe the codec parameters on the MS have been there since my first cut=
 at the metadata model. Putting them there was just speculation on my part,=
 and doesn't imply any actual need known to me.

If nobody feels they are necessary, then by all means remove them.

	Thanks,
	Paul

On 3/16/2011 3:34 AM, Elwell, John wrote:
>
>
>> -----Original Message-----
>> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
>> Sent: 16 March 2011 01:25
>> To: Elwell, John; Paul Kyzivat (pkyzivat)
>> Cc: siprec@ietf.org
>> Subject: CS Codec Parameter in stream XML element [was RE:
>> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
>>
> <snip/>
>> <Partha>  It is the assumption done during metadata format that RS=20
>> SDP may be used as Codec params for stream. Please note that format=20
>> draft does not have codec param in stream metadata element. But the=20
>> assumption does not seems to be working for all scenarios. So we need=20
>> to find the way to represent CS Media stream in metadata format.
>>
>> Even before going into approach, I'm interested in knowing whether it=20
>> is required for SRS to understand the exact codec or SDP parameter=20
>> used in CS? RS may be transcoded/transrated and lost the actual media=20
>> information when it reaches SRS but the question is whether it is=20
>> required to maintain the metadata in SRS even though media (RTP) is=20
>> changed to new format ?
>>
>> In case we decide to pass CS codec parameter to SRS. Two approaches=20
>> exist to solve this issue:
>>
>> 1) Tunnel complete each participant SDP inside stream element using=20
>> some new optional XML element. This approach is straightforward and=20
>> scale for any CS as we are sending the complete set. The overhead=20
>> will be increased in SRS to parse and store appropriately.
>>
>> 2) Identify the list of codec parameters *MUST*  be passed from SRC=20
>> to SRS and create the new XML element for them. This is simple to=20
>> implement as only portion of the SDP is passed across but *may* have=20
>> scalability issue.
>>
>> I prefer 1st approach because it covers all scenarios. I'm interested=20
>> in hearing from you which way to go.
>>
>> </partha>
> [JRE] I was basing my earlier comment on the fact that the metadata model=
 seems to indicate that the Media Stream object has CS codec parameters as =
an attribute. This is indeed questionable. I seem to remember somebody want=
ing this at some stage in the past. From my point of view, I don't think th=
is information is needed by the SRS - it is historic information, nothing t=
o do with the media actually sent to the SRS, and of no use to the SRS, in =
my opinion.
>
> If people do think there is a reason for providing this information to th=
e SRS, I don't think I would favour approach 1) above. The SDP could potent=
ially contain all sorts of information other than codecs (codecs are only a=
 small part, and the SDP will contain information like IP addresses, ports,=
 security keys!!!, transport, non-recorded media descriptions (e.g., MSRP c=
hannel, BFCP channel), format parameters, SDP capability negotiation attrib=
utes, etc..
>
> Moreover, the offerer and answerer might have agreed several codecs in th=
e SDP, so you need to look at RTP to see which codec is actually used. This=
 can change on the fly.
>
> Finally, although the SRS's SIP/SDP stack will surely have and SDP parser=
, the XML metadata is intended for passing to an application. Requiring tha=
t application to contain an SDP parser is, I think, unreasonable.
>
> So I have doubts as to whether it is really feasible to provide CS codec =
information in metadata to the SRS in a meaningful way, whether this be usi=
ng approach 1) or approach 2), but I particularly dislike approach 1).
>
> John (as individual)
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From andrew.hutton@siemens-enterprise.com  Wed Mar 16 08:45:45 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CC243A69CD for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 08:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[AWL=-0.012, BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z0jdNX7Q9ijF for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 08:45:44 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id B2CFF3A6937 for <siprec@ietf.org>; Wed, 16 Mar 2011 08:45:43 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3758115; Wed, 16 Mar 2011 16:47:07 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 3CEFB23F02A4; Wed, 16 Mar 2011 16:47:07 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 16 Mar 2011 16:47:07 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "siprec@ietf.org" <siprec@ietf.org>, Leon Portman <Leon.Portman@nice.com>, "Ken Rehor (krehor)" <krehor@cisco.com>
Date: Wed, 16 Mar 2011 16:47:05 +0100
Thread-Topic: [siprec] Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJcITDAADGr5XA=
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B61E2F594@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <35BCE99A477D6A4986FB2216D8CF2CFD05A7E88B@XMB-BGL-417.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD05A7E88B@XMB-BGL-417.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 15:45:45 -0000

Hi Ram,

Thanks for your comments.

See responses below.

Regards
Andy
=20

> -----Original Message-----
> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]=20
> Sent: 14 March 2011 18:03
> To: Elwell, John; siprec@ietf.org; Leon Portman; Hutton,=20
> Andrew; Ken Rehor (krehor)
> Subject: RE: [siprec] Progressing the architecture document
>=20
> Here are some of my comments on draft-ietf-siprec-architecture.=20
>=20
> Section 2(Definitions)- The definitions of SRS, SRC, RS, CS=20
> is different
> in Requirement (ver 08) and Architecture drafts. Please update the
> Architecture draft to reflect the same as Requirement or better remove
> from architecture as we already have reference to Requirement=20
> doc here.
> Only additional definitions not present in Requirement but used in
> Architecture draft can be included here.
>=20
[AndyH] I would find it strange to not have the definitions of the architec=
tural components in the architecture draft. If everyone agrees I will just =
make sure they are alligned.


> Section 2(Definitions)- The definition of Recording aware UA=20
> needs to be
> edited as it does not seem to meet REQ-16, 17 and 19

[AndyH] Would the following be ok?

"Recording aware UA: A SIP User Agent that is aware of SIP extensions assoc=
iated with the Communication Session. Such extensions may be used to notify=
 the SIP UA that a session is being recorded or to all the SIP UA to expres=
s preferences as to whether a recording should be started, paused, resumed =
or stopped."

>=20
> Section 2(Definitions)- Requirement draft already has a definition for
> Metadata. Do we need this MRM(Media recording Metadata) ?

[AndyH] Personally I would like to keep it and I prefer to call it "Media R=
ecording Metadata" as this is more explicit rather than just calling it "me=
tadata".

>=20
> Section 4.1.5 - If possible please add a figure here showing the
> architecture where SRC is Focus.

[AndyH] OK will try to do this in next update.

>=20
> Section 4.2 - Paragraph 2 needs to be edited to make it sync=20
> with REQ-24
> of requirement draft
>=20

[AndyH] OK will do.

> Section 4.2.4 - There is a typo on the 5th line "recoding server".

[AndyH] Thanks

>=20
> Section 4.3.1 - Do we need this section with all the points=20
> now ? Since
> we have separate draft(s), would it be better to just have a few lines
> and then reference this draft. Note, I am not sure if its right to
> reference a draft (for the reason Leon mentioned on Circular=20
> references)
>=20

[AndyH] Once the working group had adopted the metadata drafts I will refer=
ence those and remove the text.

> Section 4.4 - First line here may need change as we have concluded on
> other means of notifying recording (like visual indications e.t.c)
>=20
[AndyH] I will make some changes to this section I think all we need to do =
in the arch draft is explain that it is the SRC that is responsible for gen=
erating the notifications.


>=20


> Regards,
> Ram
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Elwell, John
> > Sent: Wednesday, March 02, 2011 10:26 PM
> > To: siprec@ietf.org
> > Subject: [siprec] Progressing the architecture document
> >=20
> > draft-ietf-siprec-architecture has not moved forward much in recent
> > months, waiting for progress on solutions to help confirm the
> > architecture. Now would be an excellent time for people to raise any
> > issues that can perhaps be addressed by the editor before=20
> the cut-off
> > (2011-03-14) or discussed in Prague.
> >=20
> > John
> >=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> =

From Leon.Portman@nice.com  Wed Mar 16 08:53:18 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72AA23A69AD for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 08:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.322
X-Spam-Level: 
X-Spam-Status: No, score=-1.322 tagged_above=-999 required=5 tests=[AWL=-1.023, BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KT94-dpsnHZe for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 08:53:17 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id D0A4F3A6977 for <siprec@ietf.org>; Wed, 16 Mar 2011 08:53:16 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Wed, 16 Mar 2011 17:54:42 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>
Date: Wed, 16 Mar 2011 17:54:41 +0200
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAPOyYwA==
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A94915D0@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 15:53:18 -0000

Partha and Andy Hi

I want to address the point regarding indication if SRC supports metadata. =
I think we need to assume that all SRC supports metadata reporting otherwis=
e SRS will not know what it is actually recording. It is very hard for me t=
o find configuration where SRC will implement SIPREC but not will be able t=
o populate metadata XML.
At least on basic level.

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Hutton, Andrew
Sent: Tuesday, March 15, 2011 6:00 PM
To: Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: Re: [siprec] Progressing the architecture document

Hi Partha,

Thanks for your comments.

See below.

Regards
Andy
=20

> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 14 March 2011 17:05
> To: Elwell, John; siprec@ietf.org
> Subject: Re: [siprec] Progressing the architecture document
>=20
> SIPREC Architecture-01 draft looks good in the high level.=20
> Some of the minor comments are as follows:
> =20
> Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be=20
> preferred to indicate that SRC also has AS & MS clubbed together. IMO,=20
> this provide more clarity while reading.

[AndyH] The related text does state that the SRC could also be decomposed i=
n this way and Fig 3. is just one example. I think the figure showing the S=
RS better illustrates the relation to mediactrl with regard to recording so=
 I prefer the current diagram. Why do you think the showing the SRC in this=
 way would add clarity? I could of course include both but not sure this is=
 really necessary.

> =20
> Sec 4.1.5 Figure shall be added to indicate a scenarion whererin focus=20
> acts as SRC.

[AndyH] I will look at creating a diagram.

> =20
> Sec 4.2 Para 2 example does not go inline with REQ-024 of -07=20
> Requirement draft. The example shall change from "client must decrypt"=20
> to "client may decrypt".

[AndyH] I think I have to remove the whole sentence as the example is no lo=
nger valid.

> =20
> Sec 4.2.1 Fourth bullet text may be preferred to change as "Indicate=20
> support for the recording metadata"

[AndyH] Have we decided whether we have any indication from the SRC that it=
 supports metadata? I did not think so therefore this is an open issue but =
probably not relevant to the architecture draft. I probably should remove t=
he mechanism related stuff and at some point reference the protocol draft. =
Do you agree?

> =20
> Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or "sendonly=20
> as it is indicated as SRS and SRC in the beginning of the line.

[AndyH] Done.

> =20
> Sec 4.3.1 1st bullet shall be changed from "Dialog identifier" to=20
> "Communication Session Identifier"

[AndyH] Note sure about this the current text states "Dialog identifiers fo=
r the Communication Session" which seems correct to me. This will probably =
get removed anyway and replaced to a reference to the metadata model when i=
t is adopted.

> =20
> Sec 4.3.1 whether 3rd bullet is required?=20
> =20

[AndyH]I assume it is as for example I assume it would be necessary to reco=
rd early-media and update the SRS when the dialog changes to the confirmed =
or terminated state. Does not seem to be in the metadata draft though. In t=
he end I will either remove these bullets or align with the metadata draft.


> General comment: it is preferred to change to "should, must"=20
> to "SHOULD, MUST" as per RFC 2119

[AndyH]I think I need to remove all RFC 2119 wording as it is not appropria=
te to the architecture draft. I will remove all such wording and the refere=
nce to RFC 2119. Is that ok ?

> =20
> Sec 4.3.2 1st bullet has to be removed as it is not required any more.
> =20
[AndyH]OK are there really no information in SIP Headers that could be stor=
ed as metadata?

> Sec 4.3.2 3rd bullet has to be changed to indicate XML package instead=20
> of Event package

[AndyH] Noted. I will need to review this once we have adopted the protocol=
 draft and make sure it is aligned.

> =20
> Sec 4.3.2 last bullet: is it required to pass metadata using non-sip=20
> mechanism?
>=20
[AndyH] I will remove this statement if that is ok with everyone.


> Thanks
> Partha
>=20
> ________________________________
>=20
> From: siprec-bounces@ietf.org on behalf of Elwell, John
> Sent: Wed 3/2/2011 10:25 PM
> To: siprec@ietf.org
> Subject: [siprec] Progressing the architecture document
>=20
>=20
>=20
> draft-ietf-siprec-architecture has not moved forward much in recent=20
> months, waiting for progress on solutions to help confirm the=20
> architecture. Now would be an excellent time for people to raise any=20
> issues that can perhaps be addressed by the editor before the cut-off=20
> (2011-03-14) or discussed in Prague.
>=20
> John
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20
>=20
>=20
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From andrew.hutton@siemens-enterprise.com  Wed Mar 16 09:03:23 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47E9A3A69BC for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 09:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.159
X-Spam-Level: 
X-Spam-Status: No, score=-1.159 tagged_above=-999 required=5 tests=[AWL=-0.860, BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ED+XtHuq3GjU for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 09:03:22 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id E7F963A6977 for <siprec@ietf.org>; Wed, 16 Mar 2011 09:03:21 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3758456; Wed, 16 Mar 2011 17:04:43 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 895BC1EB82AE; Wed, 16 Mar 2011 17:04:43 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 16 Mar 2011 17:04:43 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, "Parthasarathi R (partr)" <partr@cisco.com>
Date: Wed, 16 Mar 2011 17:04:42 +0100
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAPOyYwAAAOzzQ
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5B4@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A94915D0@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A94915D0@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 16:03:23 -0000

Hi Leon,

At the most basic level an SRS may I assume not need any metadata. For exam=
ple it could be that simply the date and time of the recording is all that =
is needed for metadata and we don't need XML for that.

The question is whether the SRS needs to be given an explicit indication fr=
om the SRC that no metadata will be generated and that probably depends on =
the mechanism for delivering it. =20

Regards
Andy



=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 16 March 2011 15:55
> To: Hutton, Andrew; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Progressing the architecture document
>=20
> Partha and Andy Hi
>=20
> I want to address the point regarding indication if SRC=20
> supports metadata. I think we need to assume that all SRC=20
> supports metadata reporting otherwise SRS will not know what=20
> it is actually recording. It is very hard for me to find=20
> configuration where SRC will implement SIPREC but not will be=20
> able to populate metadata XML.
> At least on basic level.
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton, Andrew
> Sent: Tuesday, March 15, 2011 6:00 PM
> To: Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Progressing the architecture document
>=20
> Hi Partha,
>=20
> Thanks for your comments.
>=20
> See below.
>=20
> Regards
> Andy
> =20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi=20
> R (partr)
> > Sent: 14 March 2011 17:05
> > To: Elwell, John; siprec@ietf.org
> > Subject: Re: [siprec] Progressing the architecture document
> >=20
> > SIPREC Architecture-01 draft looks good in the high level.=20
> > Some of the minor comments are as follows:
> > =20
> > Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be=20
> > preferred to indicate that SRC also has AS & MS clubbed=20
> together. IMO,=20
> > this provide more clarity while reading.
>=20
> [AndyH] The related text does state that the SRC could also=20
> be decomposed in this way and Fig 3. is just one example. I=20
> think the figure showing the SRS better illustrates the=20
> relation to mediactrl with regard to recording so I prefer=20
> the current diagram. Why do you think the showing the SRC in=20
> this way would add clarity? I could of course include both=20
> but not sure this is really necessary.
>=20
> > =20
> > Sec 4.1.5 Figure shall be added to indicate a scenarion=20
> whererin focus=20
> > acts as SRC.
>=20
> [AndyH] I will look at creating a diagram.
>=20
> > =20
> > Sec 4.2 Para 2 example does not go inline with REQ-024 of -07=20
> > Requirement draft. The example shall change from "client=20
> must decrypt"=20
> > to "client may decrypt".
>=20
> [AndyH] I think I have to remove the whole sentence as the=20
> example is no longer valid.
>=20
> > =20
> > Sec 4.2.1 Fourth bullet text may be preferred to change as=20
> "Indicate=20
> > support for the recording metadata"
>=20
> [AndyH] Have we decided whether we have any indication from=20
> the SRC that it supports metadata? I did not think so=20
> therefore this is an open issue but probably not relevant to=20
> the architecture draft. I probably should remove the=20
> mechanism related stuff and at some point reference the=20
> protocol draft. Do you agree?
>=20
> > =20
> > Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or=20
> "sendonly=20
> > as it is indicated as SRS and SRC in the beginning of the line.
>=20
> [AndyH] Done.
>=20
> > =20
> > Sec 4.3.1 1st bullet shall be changed from "Dialog identifier" to=20
> > "Communication Session Identifier"
>=20
> [AndyH] Note sure about this the current text states "Dialog=20
> identifiers for the Communication Session" which seems=20
> correct to me. This will probably get removed anyway and=20
> replaced to a reference to the metadata model when it is adopted.
>=20
> > =20
> > Sec 4.3.1 whether 3rd bullet is required?=20
> > =20
>=20
> [AndyH]I assume it is as for example I assume it would be=20
> necessary to record early-media and update the SRS when the=20
> dialog changes to the confirmed or terminated state. Does not=20
> seem to be in the metadata draft though. In the end I will=20
> either remove these bullets or align with the metadata draft.
>=20
>=20
> > General comment: it is preferred to change to "should, must"=20
> > to "SHOULD, MUST" as per RFC 2119
>=20
> [AndyH]I think I need to remove all RFC 2119 wording as it is=20
> not appropriate to the architecture draft. I will remove all=20
> such wording and the reference to RFC 2119. Is that ok ?
>=20
> > =20
> > Sec 4.3.2 1st bullet has to be removed as it is not=20
> required any more.
> > =20
> [AndyH]OK are there really no information in SIP Headers that=20
> could be stored as metadata?
>=20
> > Sec 4.3.2 3rd bullet has to be changed to indicate XML=20
> package instead=20
> > of Event package
>=20
> [AndyH] Noted. I will need to review this once we have=20
> adopted the protocol draft and make sure it is aligned.
>=20
> > =20
> > Sec 4.3.2 last bullet: is it required to pass metadata=20
> using non-sip=20
> > mechanism?
> >=20
> [AndyH] I will remove this statement if that is ok with everyone.
>=20
>=20
> > Thanks
> > Partha
> >=20
> > ________________________________
> >=20
> > From: siprec-bounces@ietf.org on behalf of Elwell, John
> > Sent: Wed 3/2/2011 10:25 PM
> > To: siprec@ietf.org
> > Subject: [siprec] Progressing the architecture document
> >=20
> >=20
> >=20
> > draft-ietf-siprec-architecture has not moved forward much in recent=20
> > months, waiting for progress on solutions to help confirm the=20
> > architecture. Now would be an excellent time for people to=20
> raise any=20
> > issues that can perhaps be addressed by the editor before=20
> the cut-off=20
> > (2011-03-14) or discussed in Prague.
> >=20
> > John
> >=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >=20
> >=20
> >=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From Leon.Portman@nice.com  Wed Mar 16 09:06:45 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 008073A69BE for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 09:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[AWL=-0.978, BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAHr9W9qlqII for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 09:06:44 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 51D723A69BC for <siprec@ietf.org>; Wed, 16 Mar 2011 09:06:43 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Wed, 16 Mar 2011 18:08:08 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>
Date: Wed, 16 Mar 2011 18:08:07 +0200
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAPOyYwAAAOzzQAAA8kkA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A94915D9@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A94915D0@TLVMBX01.nice.com> <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5B4@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5B4@MCHP058A.global-ad.net>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 16:06:45 -0000

Andy Hi

Actually participants of the CS are basic info as well and I think that XML=
 is required for it.

Leon

-----Original Message-----
From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]=20
Sent: Wednesday, March 16, 2011 6:05 PM
To: Leon Portman; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Progressing the architecture document

Hi Leon,

At the most basic level an SRS may I assume not need any metadata. For exam=
ple it could be that simply the date and time of the recording is all that =
is needed for metadata and we don't need XML for that.

The question is whether the SRS needs to be given an explicit indication fr=
om the SRC that no metadata will be generated and that probably depends on =
the mechanism for delivering it. =20

Regards
Andy



=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 16 March 2011 15:55
> To: Hutton, Andrew; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Progressing the architecture document
>=20
> Partha and Andy Hi
>=20
> I want to address the point regarding indication if SRC supports=20
> metadata. I think we need to assume that all SRC supports metadata=20
> reporting otherwise SRS will not know what it is actually recording.=20
> It is very hard for me to find configuration where SRC will implement=20
> SIPREC but not will be able to populate metadata XML.
> At least on basic level.
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton, Andrew
> Sent: Tuesday, March 15, 2011 6:00 PM
> To: Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Progressing the architecture document
>=20
> Hi Partha,
>=20
> Thanks for your comments.
>=20
> See below.
>=20
> Regards
> Andy
> =20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
> R (partr)
> > Sent: 14 March 2011 17:05
> > To: Elwell, John; siprec@ietf.org
> > Subject: Re: [siprec] Progressing the architecture document
> >=20
> > SIPREC Architecture-01 draft looks good in the high level.=20
> > Some of the minor comments are as follows:
> > =20
> > Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be=20
> > preferred to indicate that SRC also has AS & MS clubbed
> together. IMO,
> > this provide more clarity while reading.
>=20
> [AndyH] The related text does state that the SRC could also be=20
> decomposed in this way and Fig 3. is just one example. I think the=20
> figure showing the SRS better illustrates the relation to mediactrl=20
> with regard to recording so I prefer the current diagram. Why do you=20
> think the showing the SRC in this way would add clarity? I could of=20
> course include both but not sure this is really necessary.
>=20
> > =20
> > Sec 4.1.5 Figure shall be added to indicate a scenarion
> whererin focus
> > acts as SRC.
>=20
> [AndyH] I will look at creating a diagram.
>=20
> > =20
> > Sec 4.2 Para 2 example does not go inline with REQ-024 of -07=20
> > Requirement draft. The example shall change from "client
> must decrypt"=20
> > to "client may decrypt".
>=20
> [AndyH] I think I have to remove the whole sentence as the example is=20
> no longer valid.
>=20
> > =20
> > Sec 4.2.1 Fourth bullet text may be preferred to change as
> "Indicate
> > support for the recording metadata"
>=20
> [AndyH] Have we decided whether we have any indication from the SRC=20
> that it supports metadata? I did not think so therefore this is an=20
> open issue but probably not relevant to the architecture draft. I=20
> probably should remove the mechanism related stuff and at some point=20
> reference the protocol draft. Do you agree?
>=20
> > =20
> > Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or
> "sendonly
> > as it is indicated as SRS and SRC in the beginning of the line.
>=20
> [AndyH] Done.
>=20
> > =20
> > Sec 4.3.1 1st bullet shall be changed from "Dialog identifier" to=20
> > "Communication Session Identifier"
>=20
> [AndyH] Note sure about this the current text states "Dialog=20
> identifiers for the Communication Session" which seems correct to me.=20
> This will probably get removed anyway and replaced to a reference to=20
> the metadata model when it is adopted.
>=20
> > =20
> > Sec 4.3.1 whether 3rd bullet is required?=20
> > =20
>=20
> [AndyH]I assume it is as for example I assume it would be necessary to=20
> record early-media and update the SRS when the dialog changes to the=20
> confirmed or terminated state. Does not seem to be in the metadata=20
> draft though. In the end I will either remove these bullets or align=20
> with the metadata draft.
>=20
>=20
> > General comment: it is preferred to change to "should, must"=20
> > to "SHOULD, MUST" as per RFC 2119
>=20
> [AndyH]I think I need to remove all RFC 2119 wording as it is not=20
> appropriate to the architecture draft. I will remove all such wording=20
> and the reference to RFC 2119. Is that ok ?
>=20
> > =20
> > Sec 4.3.2 1st bullet has to be removed as it is not
> required any more.
> > =20
> [AndyH]OK are there really no information in SIP Headers that could be=20
> stored as metadata?
>=20
> > Sec 4.3.2 3rd bullet has to be changed to indicate XML
> package instead
> > of Event package
>=20
> [AndyH] Noted. I will need to review this once we have adopted the=20
> protocol draft and make sure it is aligned.
>=20
> > =20
> > Sec 4.3.2 last bullet: is it required to pass metadata
> using non-sip
> > mechanism?
> >=20
> [AndyH] I will remove this statement if that is ok with everyone.
>=20
>=20
> > Thanks
> > Partha
> >=20
> > ________________________________
> >=20
> > From: siprec-bounces@ietf.org on behalf of Elwell, John
> > Sent: Wed 3/2/2011 10:25 PM
> > To: siprec@ietf.org
> > Subject: [siprec] Progressing the architecture document
> >=20
> >=20
> >=20
> > draft-ietf-siprec-architecture has not moved forward much in recent=20
> > months, waiting for progress on solutions to help confirm the=20
> > architecture. Now would be an excellent time for people to
> raise any
> > issues that can perhaps be addressed by the editor before
> the cut-off
> > (2011-03-14) or discussed in Prague.
> >=20
> > John
> >=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >=20
> >=20
> >=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20

From andrew.hutton@siemens-enterprise.com  Wed Mar 16 09:33:34 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C01543A69BF for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 09:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.016
X-Spam-Level: 
X-Spam-Status: No, score=-1.016 tagged_above=-999 required=5 tests=[AWL=-0.717, BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JYOXFWGHhi5H for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 09:33:33 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 2F0053A69AE for <siprec@ietf.org>; Wed, 16 Mar 2011 09:33:32 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3775022; Wed, 16 Mar 2011 17:34:56 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id BE6001EB82AB; Wed, 16 Mar 2011 17:34:56 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 16 Mar 2011 17:34:56 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, "Parthasarathi R (partr)" <partr@cisco.com>
Date: Wed, 16 Mar 2011 17:34:55 +0100
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAPOyYwAAAOzzQAAA8kkAAAL8h8A==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5F0@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A94915D0@TLVMBX01.nice.com> <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5B4@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A94915D9@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A94915D9@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 16:33:34 -0000

Hi,

In my book that is not so basic.

I don't think we should mandate that the SRC provides metadata within an XM=
L body. I don't see any reason for mandating that even if we think that all=
 SRC's will do so. There is always going to be some implementation for whic=
h this is not necessary.

The question then is does it help the SRS to know whether the SRC is capabl=
e of sending metadata if for example it asked for a snapshot. I tend to thi=
nk this would be helpful but it is not a big issue for me.

It might also be helpful if the SRS could tell the SRC that it is not inter=
ested in metadata for a given recording session. This might prevent lots of=
 bandwidth being used sending metadata just for the SRS to ignore it.

Just my honest thoughts I look forward to some discussion over a beer in Pr=
ague.

Regards
Andy

=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 16 March 2011 16:08
> To: Hutton, Andrew; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Progressing the architecture document
>=20
> Andy Hi
>=20
> Actually participants of the CS are basic info as well and I=20
> think that XML is required for it.
>=20
> Leon
>=20
> -----Original Message-----
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]=20
> Sent: Wednesday, March 16, 2011 6:05 PM
> To: Leon Portman; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Progressing the architecture document
>=20
> Hi Leon,
>=20
> At the most basic level an SRS may I assume not need any=20
> metadata. For example it could be that simply the date and=20
> time of the recording is all that is needed for metadata and=20
> we don't need XML for that.
>=20
> The question is whether the SRS needs to be given an explicit=20
> indication from the SRC that no metadata will be generated=20
> and that probably depends on the mechanism for delivering it. =20
>=20
> Regards
> Andy
>=20
>=20
>=20
> =20
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 16 March 2011 15:55
> > To: Hutton, Andrew; Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: RE: Progressing the architecture document
> >=20
> > Partha and Andy Hi
> >=20
> > I want to address the point regarding indication if SRC supports=20
> > metadata. I think we need to assume that all SRC supports metadata=20
> > reporting otherwise SRS will not know what it is actually=20
> recording.=20
> > It is very hard for me to find configuration where SRC will=20
> implement=20
> > SIPREC but not will be able to populate metadata XML.
> > At least on basic level.
> >=20
> > Leon
> >=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton, Andrew
> > Sent: Tuesday, March 15, 2011 6:00 PM
> > To: Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Progressing the architecture document
> >=20
> > Hi Partha,
> >=20
> > Thanks for your comments.
> >=20
> > See below.
> >=20
> > Regards
> > Andy
> > =20
> >=20
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
> > R (partr)
> > > Sent: 14 March 2011 17:05
> > > To: Elwell, John; siprec@ietf.org
> > > Subject: Re: [siprec] Progressing the architecture document
> > >=20
> > > SIPREC Architecture-01 draft looks good in the high level.=20
> > > Some of the minor comments are as follows:
> > > =20
> > > Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be=20
> > > preferred to indicate that SRC also has AS & MS clubbed
> > together. IMO,
> > > this provide more clarity while reading.
> >=20
> > [AndyH] The related text does state that the SRC could also be=20
> > decomposed in this way and Fig 3. is just one example. I think the=20
> > figure showing the SRS better illustrates the relation to mediactrl=20
> > with regard to recording so I prefer the current diagram.=20
> Why do you=20
> > think the showing the SRC in this way would add clarity? I could of=20
> > course include both but not sure this is really necessary.
> >=20
> > > =20
> > > Sec 4.1.5 Figure shall be added to indicate a scenarion
> > whererin focus
> > > acts as SRC.
> >=20
> > [AndyH] I will look at creating a diagram.
> >=20
> > > =20
> > > Sec 4.2 Para 2 example does not go inline with REQ-024 of -07=20
> > > Requirement draft. The example shall change from "client
> > must decrypt"=20
> > > to "client may decrypt".
> >=20
> > [AndyH] I think I have to remove the whole sentence as the=20
> example is=20
> > no longer valid.
> >=20
> > > =20
> > > Sec 4.2.1 Fourth bullet text may be preferred to change as
> > "Indicate
> > > support for the recording metadata"
> >=20
> > [AndyH] Have we decided whether we have any indication from the SRC=20
> > that it supports metadata? I did not think so therefore this is an=20
> > open issue but probably not relevant to the architecture draft. I=20
> > probably should remove the mechanism related stuff and at=20
> some point=20
> > reference the protocol draft. Do you agree?
> >=20
> > > =20
> > > Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or
> > "sendonly
> > > as it is indicated as SRS and SRC in the beginning of the line.
> >=20
> > [AndyH] Done.
> >=20
> > > =20
> > > Sec 4.3.1 1st bullet shall be changed from "Dialog identifier" to=20
> > > "Communication Session Identifier"
> >=20
> > [AndyH] Note sure about this the current text states "Dialog=20
> > identifiers for the Communication Session" which seems=20
> correct to me.=20
> > This will probably get removed anyway and replaced to a=20
> reference to=20
> > the metadata model when it is adopted.
> >=20
> > > =20
> > > Sec 4.3.1 whether 3rd bullet is required?=20
> > > =20
> >=20
> > [AndyH]I assume it is as for example I assume it would be=20
> necessary to=20
> > record early-media and update the SRS when the dialog=20
> changes to the=20
> > confirmed or terminated state. Does not seem to be in the metadata=20
> > draft though. In the end I will either remove these bullets=20
> or align=20
> > with the metadata draft.
> >=20
> >=20
> > > General comment: it is preferred to change to "should, must"=20
> > > to "SHOULD, MUST" as per RFC 2119
> >=20
> > [AndyH]I think I need to remove all RFC 2119 wording as it is not=20
> > appropriate to the architecture draft. I will remove all=20
> such wording=20
> > and the reference to RFC 2119. Is that ok ?
> >=20
> > > =20
> > > Sec 4.3.2 1st bullet has to be removed as it is not
> > required any more.
> > > =20
> > [AndyH]OK are there really no information in SIP Headers=20
> that could be=20
> > stored as metadata?
> >=20
> > > Sec 4.3.2 3rd bullet has to be changed to indicate XML
> > package instead
> > > of Event package
> >=20
> > [AndyH] Noted. I will need to review this once we have adopted the=20
> > protocol draft and make sure it is aligned.
> >=20
> > > =20
> > > Sec 4.3.2 last bullet: is it required to pass metadata
> > using non-sip
> > > mechanism?
> > >=20
> > [AndyH] I will remove this statement if that is ok with everyone.
> >=20
> >=20
> > > Thanks
> > > Partha
> > >=20
> > > ________________________________
> > >=20
> > > From: siprec-bounces@ietf.org on behalf of Elwell, John
> > > Sent: Wed 3/2/2011 10:25 PM
> > > To: siprec@ietf.org
> > > Subject: [siprec] Progressing the architecture document
> > >=20
> > >=20
> > >=20
> > > draft-ietf-siprec-architecture has not moved forward much=20
> in recent=20
> > > months, waiting for progress on solutions to help confirm the=20
> > > architecture. Now would be an excellent time for people to
> > raise any
> > > issues that can perhaps be addressed by the editor before
> > the cut-off
> > > (2011-03-14) or discussed in Prague.
> > >=20
> > > John
> > >=20
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
> > >=20
> > >=20
> > >=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >=20
> =

From Leon.Portman@nice.com  Wed Mar 16 09:38:47 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BAB13A69DF for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 09:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.237
X-Spam-Level: 
X-Spam-Status: No, score=-1.237 tagged_above=-999 required=5 tests=[AWL=-0.938, BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QEBC3a+WBOe for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 09:38:46 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 8A81C3A69E1 for <siprec@ietf.org>; Wed, 16 Mar 2011 09:38:45 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Wed, 16 Mar 2011 18:40:09 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>
Date: Wed, 16 Mar 2011 18:40:08 +0200
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAPOyYwAAAOzzQAAA8kkAAAL8h8AAAdXvA
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A94915F3@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A94915D0@TLVMBX01.nice.com> <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5B4@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A94915D9@TLVMBX01.nice.com> <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5F0@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5F0@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 16:38:47 -0000

+1 for beer

-----Original Message-----
From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]=20
Sent: Wednesday, March 16, 2011 6:35 PM
To: Leon Portman; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Progressing the architecture document

Hi,

In my book that is not so basic.

I don't think we should mandate that the SRC provides metadata within an XM=
L body. I don't see any reason for mandating that even if we think that all=
 SRC's will do so. There is always going to be some implementation for whic=
h this is not necessary.

The question then is does it help the SRS to know whether the SRC is capabl=
e of sending metadata if for example it asked for a snapshot. I tend to thi=
nk this would be helpful but it is not a big issue for me.

It might also be helpful if the SRS could tell the SRC that it is not inter=
ested in metadata for a given recording session. This might prevent lots of=
 bandwidth being used sending metadata just for the SRS to ignore it.

Just my honest thoughts I look forward to some discussion over a beer in Pr=
ague.

Regards
Andy

=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 16 March 2011 16:08
> To: Hutton, Andrew; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Progressing the architecture document
>=20
> Andy Hi
>=20
> Actually participants of the CS are basic info as well and I think=20
> that XML is required for it.
>=20
> Leon
>=20
> -----Original Message-----
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> Sent: Wednesday, March 16, 2011 6:05 PM
> To: Leon Portman; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Progressing the architecture document
>=20
> Hi Leon,
>=20
> At the most basic level an SRS may I assume not need any metadata. For=20
> example it could be that simply the date and time of the recording is=20
> all that is needed for metadata and we don't need XML for that.
>=20
> The question is whether the SRS needs to be given an explicit=20
> indication from the SRC that no metadata will be generated and that=20
> probably depends on the mechanism for delivering it.
>=20
> Regards
> Andy
>=20
>=20
>=20
> =20
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 16 March 2011 15:55
> > To: Hutton, Andrew; Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: RE: Progressing the architecture document
> >=20
> > Partha and Andy Hi
> >=20
> > I want to address the point regarding indication if SRC supports=20
> > metadata. I think we need to assume that all SRC supports metadata=20
> > reporting otherwise SRS will not know what it is actually
> recording.=20
> > It is very hard for me to find configuration where SRC will
> implement
> > SIPREC but not will be able to populate metadata XML.
> > At least on basic level.
> >=20
> > Leon
> >=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton, Andrew
> > Sent: Tuesday, March 15, 2011 6:00 PM
> > To: Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Progressing the architecture document
> >=20
> > Hi Partha,
> >=20
> > Thanks for your comments.
> >=20
> > See below.
> >=20
> > Regards
> > Andy
> > =20
> >=20
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
> > R (partr)
> > > Sent: 14 March 2011 17:05
> > > To: Elwell, John; siprec@ietf.org
> > > Subject: Re: [siprec] Progressing the architecture document
> > >=20
> > > SIPREC Architecture-01 draft looks good in the high level.=20
> > > Some of the minor comments are as follows:
> > > =20
> > > Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be=20
> > > preferred to indicate that SRC also has AS & MS clubbed
> > together. IMO,
> > > this provide more clarity while reading.
> >=20
> > [AndyH] The related text does state that the SRC could also be=20
> > decomposed in this way and Fig 3. is just one example. I think the=20
> > figure showing the SRS better illustrates the relation to mediactrl=20
> > with regard to recording so I prefer the current diagram.
> Why do you
> > think the showing the SRC in this way would add clarity? I could of=20
> > course include both but not sure this is really necessary.
> >=20
> > > =20
> > > Sec 4.1.5 Figure shall be added to indicate a scenarion
> > whererin focus
> > > acts as SRC.
> >=20
> > [AndyH] I will look at creating a diagram.
> >=20
> > > =20
> > > Sec 4.2 Para 2 example does not go inline with REQ-024 of -07=20
> > > Requirement draft. The example shall change from "client
> > must decrypt"=20
> > > to "client may decrypt".
> >=20
> > [AndyH] I think I have to remove the whole sentence as the
> example is
> > no longer valid.
> >=20
> > > =20
> > > Sec 4.2.1 Fourth bullet text may be preferred to change as
> > "Indicate
> > > support for the recording metadata"
> >=20
> > [AndyH] Have we decided whether we have any indication from the SRC=20
> > that it supports metadata? I did not think so therefore this is an=20
> > open issue but probably not relevant to the architecture draft. I=20
> > probably should remove the mechanism related stuff and at
> some point
> > reference the protocol draft. Do you agree?
> >=20
> > > =20
> > > Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or
> > "sendonly
> > > as it is indicated as SRS and SRC in the beginning of the line.
> >=20
> > [AndyH] Done.
> >=20
> > > =20
> > > Sec 4.3.1 1st bullet shall be changed from "Dialog identifier" to=20
> > > "Communication Session Identifier"
> >=20
> > [AndyH] Note sure about this the current text states "Dialog=20
> > identifiers for the Communication Session" which seems
> correct to me.=20
> > This will probably get removed anyway and replaced to a
> reference to
> > the metadata model when it is adopted.
> >=20
> > > =20
> > > Sec 4.3.1 whether 3rd bullet is required?=20
> > > =20
> >=20
> > [AndyH]I assume it is as for example I assume it would be
> necessary to
> > record early-media and update the SRS when the dialog
> changes to the
> > confirmed or terminated state. Does not seem to be in the metadata=20
> > draft though. In the end I will either remove these bullets
> or align
> > with the metadata draft.
> >=20
> >=20
> > > General comment: it is preferred to change to "should, must"=20
> > > to "SHOULD, MUST" as per RFC 2119
> >=20
> > [AndyH]I think I need to remove all RFC 2119 wording as it is not=20
> > appropriate to the architecture draft. I will remove all
> such wording
> > and the reference to RFC 2119. Is that ok ?
> >=20
> > > =20
> > > Sec 4.3.2 1st bullet has to be removed as it is not
> > required any more.
> > > =20
> > [AndyH]OK are there really no information in SIP Headers
> that could be
> > stored as metadata?
> >=20
> > > Sec 4.3.2 3rd bullet has to be changed to indicate XML
> > package instead
> > > of Event package
> >=20
> > [AndyH] Noted. I will need to review this once we have adopted the=20
> > protocol draft and make sure it is aligned.
> >=20
> > > =20
> > > Sec 4.3.2 last bullet: is it required to pass metadata
> > using non-sip
> > > mechanism?
> > >=20
> > [AndyH] I will remove this statement if that is ok with everyone.
> >=20
> >=20
> > > Thanks
> > > Partha
> > >=20
> > > ________________________________
> > >=20
> > > From: siprec-bounces@ietf.org on behalf of Elwell, John
> > > Sent: Wed 3/2/2011 10:25 PM
> > > To: siprec@ietf.org
> > > Subject: [siprec] Progressing the architecture document
> > >=20
> > >=20
> > >=20
> > > draft-ietf-siprec-architecture has not moved forward much
> in recent
> > > months, waiting for progress on solutions to help confirm the=20
> > > architecture. Now would be an excellent time for people to
> > raise any
> > > issues that can perhaps be addressed by the editor before
> > the cut-off
> > > (2011-03-14) or discussed in Prague.
> > >=20
> > > John
> > >=20
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
> > >=20
> > >=20
> > >=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >=20
>=20

From john.elwell@siemens-enterprise.com  Wed Mar 16 10:27:08 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3869D3A69E1 for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 10:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aL69syLoTtB4 for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 10:27:07 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id BBB3D3A69D9 for <siprec@ietf.org>; Wed, 16 Mar 2011 10:27:06 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3759890; Wed, 16 Mar 2011 18:28:32 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 51E091EB82B4; Wed, 16 Mar 2011 18:28:32 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Wed, 16 Mar 2011 18:28:32 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Wed, 16 Mar 2011 18:28:31 +0100
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgAAO42HA=
Message-ID: <A444A0F8084434499206E78C106220CA086A964829@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com> <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net> <4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 17:27:08 -0000

Leon,

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 16 March 2011 15:46
> To: Paul Kyzivat; Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML=20
> element [was RE: Review Request for=20
> draft-ram-siprec-metadata-format-01]
>=20
> I agree with points below that passing actual CS SDP to SRS=20
> is a not good idea from security and layers separation point of view.
> Today's SRS implementations(at least that I know about) do=20
> not keep original codec information in the database for later=20
> retrieval. I am trying to think about use cases why SRS can=20
> be interested in one, and except troubleshooting it is not=20
> very relevant.=20
> The main assumption is that SRC inspected CS SDP and=20
> extracted all relevant information like ip addresses, media=20
> line labels and infos and reported it to SRS via metadata.
[JRE] Why would the SRS need to know anything about CS IP addresses?

>=20
> The main reason as I see if we want to be able to report CS=20
> SDP via metadata is for the case where SRS wants to sniff RS=20
> RTP packets directly and not by forking from SRC but it is=20
> out of scope.
[JRE] So I assume you agree that there is no need for metadata to include C=
S codecs (or, for that matter CS IP addresses, ports, etc.).

John (as individual)

>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: Wednesday, March 16, 2011 3:33 PM
> To: Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] CS Codec Parameter in stream XML=20
> element [was RE: Review Request for=20
> draft-ram-siprec-metadata-format-01]
>=20
> I believe the codec parameters on the MS have been there=20
> since my first cut at the metadata model. Putting them there=20
> was just speculation on my part, and doesn't imply any actual=20
> need known to me.
>=20
> If nobody feels they are necessary, then by all means remove them.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/16/2011 3:34 AM, Elwell, John wrote:
> >
> >
> >> -----Original Message-----
> >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> >> Sent: 16 March 2011 01:25
> >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> >> Cc: siprec@ietf.org
> >> Subject: CS Codec Parameter in stream XML element [was RE:
> >> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
> >>
> > <snip/>
> >> <Partha>  It is the assumption done during metadata format that RS=20
> >> SDP may be used as Codec params for stream. Please note=20
> that format=20
> >> draft does not have codec param in stream metadata=20
> element. But the=20
> >> assumption does not seems to be working for all scenarios.=20
> So we need=20
> >> to find the way to represent CS Media stream in metadata format.
> >>
> >> Even before going into approach, I'm interested in knowing=20
> whether it=20
> >> is required for SRS to understand the exact codec or SDP parameter=20
> >> used in CS? RS may be transcoded/transrated and lost the=20
> actual media=20
> >> information when it reaches SRS but the question is whether it is=20
> >> required to maintain the metadata in SRS even though media=20
> (RTP) is=20
> >> changed to new format ?
> >>
> >> In case we decide to pass CS codec parameter to SRS. Two=20
> approaches=20
> >> exist to solve this issue:
> >>
> >> 1) Tunnel complete each participant SDP inside stream=20
> element using=20
> >> some new optional XML element. This approach is=20
> straightforward and=20
> >> scale for any CS as we are sending the complete set. The overhead=20
> >> will be increased in SRS to parse and store appropriately.
> >>
> >> 2) Identify the list of codec parameters *MUST*  be passed=20
> from SRC=20
> >> to SRS and create the new XML element for them. This is simple to=20
> >> implement as only portion of the SDP is passed across but=20
> *may* have=20
> >> scalability issue.
> >>
> >> I prefer 1st approach because it covers all scenarios. I'm=20
> interested=20
> >> in hearing from you which way to go.
> >>
> >> </partha>
> > [JRE] I was basing my earlier comment on the fact that the=20
> metadata model seems to indicate that the Media Stream object=20
> has CS codec parameters as an attribute. This is indeed=20
> questionable. I seem to remember somebody wanting this at=20
> some stage in the past. From my point of view, I don't think=20
> this information is needed by the SRS - it is historic=20
> information, nothing to do with the media actually sent to=20
> the SRS, and of no use to the SRS, in my opinion.
> >
> > If people do think there is a reason for providing this=20
> information to the SRS, I don't think I would favour approach=20
> 1) above. The SDP could potentially contain all sorts of=20
> information other than codecs (codecs are only a small part,=20
> and the SDP will contain information like IP addresses,=20
> ports, security keys!!!, transport, non-recorded media=20
> descriptions (e.g., MSRP channel, BFCP channel), format=20
> parameters, SDP capability negotiation attributes, etc..
> >
> > Moreover, the offerer and answerer might have agreed=20
> several codecs in the SDP, so you need to look at RTP to see=20
> which codec is actually used. This can change on the fly.
> >
> > Finally, although the SRS's SIP/SDP stack will surely have=20
> and SDP parser, the XML metadata is intended for passing to=20
> an application. Requiring that application to contain an SDP=20
> parser is, I think, unreasonable.
> >
> > So I have doubts as to whether it is really feasible to=20
> provide CS codec information in metadata to the SRS in a=20
> meaningful way, whether this be using approach 1) or approach=20
> 2), but I particularly dislike approach 1).
> >
> > John (as individual)
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From partr@cisco.com  Wed Mar 16 14:39:46 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C2423A6A64 for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 14:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.204
X-Spam-Level: 
X-Spam-Status: No, score=-8.204 tagged_above=-999 required=5 tests=[AWL=-1.302, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YP+ETdooIwgt for <siprec@core3.amsl.com>; Wed, 16 Mar 2011 14:39:43 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 45E143A6A59 for <siprec@ietf.org>; Wed, 16 Mar 2011 14:39:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=22355; q=dns/txt; s=iport; t=1300311669; x=1301521269; h=mime-version:subject:date:message-id:references:from:to: cc; bh=YHGfPkc5VJUFC62X1jhZhMLfmdToWphgZwYc+ZBTX+4=; b=Hb+aqe1KaiwWhDnvzJj13bnyWSkCUc3nHxIR0NAHiKRFOmkze1UCUtSH wNw0ekybi527Y7BjPf+yC8qdHVBrM4OC2vjC8+yzNEjT8id1rxAATdq0j UOAVAfoYK6zokc7GykgORbFiJrCxYNA2O2qKF8SXFWbhhreDqk/4X0Fce w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0BAJHLgE2Q/khLgWdsb2JhbACYWIxiUxQBARYmJaYtnFOFYwSFLYsE
X-IronPort-AV: E=Sophos;i="4.63,195,1299456000"; d="scan'208,217";a="22013201"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 16 Mar 2011 21:41:08 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2GLf7Zu028690; Wed, 16 Mar 2011 21:41:07 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Mar 2011 03:11:06 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE422.DA54599D"
Date: Thu, 17 Mar 2011 03:11:05 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A6AC@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Progressing the architecture document
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAPOyYwAAAOzzQAAA8kkAAAL8h8AAAdXvAAAoUKCg=
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A94915D0@TLVMBX01.nice.com> <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5B4@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A94915D9@TLVMBX01.nice.com> <101C6067BEC68246B0C3F6843BCCC1E30B61E2F5F0@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A94915F3@TLVMBX01.nice.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 16 Mar 2011 21:41:06.0676 (UTC) FILETIME=[DB23AB40:01CBE422]
Cc: siprec@ietf.org
Subject: Re: [siprec] Progressing the architecture document
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 21:39:46 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE422.DA54599D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Andy/Leon,
=20
I'm also interested in Beer discussion at Prague :-) Let us plan for it
=20
I understand Andy requirement to pass metadata in the need basis and not =
mandatory to pass always. IMO, it is reasonable requirement. I guess =
that option tag like "rs-metadata" between SRC and SRS may serve the =
purpose. In case rs-metadata is not received from SRS, SRC should not =
send metadata. Please let me know your opinion here.
=20
Thanks
Partha

________________________________

From: Leon Portman [mailto:Leon.Portman@nice.com]
Sent: Wed 3/16/2011 10:10 PM
To: Hutton, Andrew; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Progressing the architecture document



+1 for beer

-----Original Message-----
From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
Sent: Wednesday, March 16, 2011 6:35 PM
To: Leon Portman; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Progressing the architecture document

Hi,

In my book that is not so basic.

I don't think we should mandate that the SRC provides metadata within an =
XML body. I don't see any reason for mandating that even if we think =
that all SRC's will do so. There is always going to be some =
implementation for which this is not necessary.

The question then is does it help the SRS to know whether the SRC is =
capable of sending metadata if for example it asked for a snapshot. I =
tend to think this would be helpful but it is not a big issue for me.

It might also be helpful if the SRS could tell the SRC that it is not =
interested in metadata for a given recording session. This might prevent =
lots of bandwidth being used sending metadata just for the SRS to ignore =
it.

Just my honest thoughts I look forward to some discussion over a beer in =
Prague.

Regards
Andy



> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 16 March 2011 16:08
> To: Hutton, Andrew; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Progressing the architecture document
>
> Andy Hi
>
> Actually participants of the CS are basic info as well and I think
> that XML is required for it.
>
> Leon
>
> -----Original Message-----
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> Sent: Wednesday, March 16, 2011 6:05 PM
> To: Leon Portman; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Progressing the architecture document
>
> Hi Leon,
>
> At the most basic level an SRS may I assume not need any metadata. For
> example it could be that simply the date and time of the recording is
> all that is needed for metadata and we don't need XML for that.
>
> The question is whether the SRS needs to be given an explicit
> indication from the SRC that no metadata will be generated and that
> probably depends on the mechanism for delivering it.
>
> Regards
> Andy
>
>
>
>=20
>
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 16 March 2011 15:55
> > To: Hutton, Andrew; Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: RE: Progressing the architecture document
> >
> > Partha and Andy Hi
> >
> > I want to address the point regarding indication if SRC supports
> > metadata. I think we need to assume that all SRC supports metadata
> > reporting otherwise SRS will not know what it is actually
> recording.
> > It is very hard for me to find configuration where SRC will
> implement
> > SIPREC but not will be able to populate metadata XML.
> > At least on basic level.
> >
> > Leon
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton, Andrew
> > Sent: Tuesday, March 15, 2011 6:00 PM
> > To: Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Progressing the architecture document
> >
> > Hi Partha,
> >
> > Thanks for your comments.
> >
> > See below.
> >
> > Regards
> > Andy
> >=20
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
> > R (partr)
> > > Sent: 14 March 2011 17:05
> > > To: Elwell, John; siprec@ietf.org
> > > Subject: Re: [siprec] Progressing the architecture document
> > >
> > > SIPREC Architecture-01 draft looks good in the high level.
> > > Some of the minor comments are as follows:
> > >=20
> > > Sec 4.1.4 Fig 3 indicates about SRS having AS & MS, it may be
> > > preferred to indicate that SRC also has AS & MS clubbed
> > together. IMO,
> > > this provide more clarity while reading.
> >
> > [AndyH] The related text does state that the SRC could also be
> > decomposed in this way and Fig 3. is just one example. I think the
> > figure showing the SRS better illustrates the relation to mediactrl
> > with regard to recording so I prefer the current diagram.
> Why do you
> > think the showing the SRC in this way would add clarity? I could of
> > course include both but not sure this is really necessary.
> >
> > >=20
> > > Sec 4.1.5 Figure shall be added to indicate a scenarion
> > whererin focus
> > > acts as SRC.
> >
> > [AndyH] I will look at creating a diagram.
> >
> > >=20
> > > Sec 4.2 Para 2 example does not go inline with REQ-024 of -07
> > > Requirement draft. The example shall change from "client
> > must decrypt"
> > > to "client may decrypt".
> >
> > [AndyH] I think I have to remove the whole sentence as the
> example is
> > no longer valid.
> >
> > >=20
> > > Sec 4.2.1 Fourth bullet text may be preferred to change as
> > "Indicate
> > > support for the recording metadata"
> >
> > [AndyH] Have we decided whether we have any indication from the SRC
> > that it supports metadata? I did not think so therefore this is an
> > open issue but probably not relevant to the architecture draft. I
> > probably should remove the mechanism related stuff and at
> some point
> > reference the protocol draft. Do you agree?
> >
> > >=20
> > > Sec 4.2.3 change "sendonly" or "recvonly" to "recvonly" or
> > "sendonly
> > > as it is indicated as SRS and SRC in the beginning of the line.
> >
> > [AndyH] Done.
> >
> > >=20
> > > Sec 4.3.1 1st bullet shall be changed from "Dialog identifier" to
> > > "Communication Session Identifier"
> >
> > [AndyH] Note sure about this the current text states "Dialog
> > identifiers for the Communication Session" which seems
> correct to me.
> > This will probably get removed anyway and replaced to a
> reference to
> > the metadata model when it is adopted.
> >
> > >=20
> > > Sec 4.3.1 whether 3rd bullet is required?
> > >=20
> >
> > [AndyH]I assume it is as for example I assume it would be
> necessary to
> > record early-media and update the SRS when the dialog
> changes to the
> > confirmed or terminated state. Does not seem to be in the metadata
> > draft though. In the end I will either remove these bullets
> or align
> > with the metadata draft.
> >
> >
> > > General comment: it is preferred to change to "should, must"
> > > to "SHOULD, MUST" as per RFC 2119
> >
> > [AndyH]I think I need to remove all RFC 2119 wording as it is not
> > appropriate to the architecture draft. I will remove all
> such wording
> > and the reference to RFC 2119. Is that ok ?
> >
> > >=20
> > > Sec 4.3.2 1st bullet has to be removed as it is not
> > required any more.
> > >=20
> > [AndyH]OK are there really no information in SIP Headers
> that could be
> > stored as metadata?
> >
> > > Sec 4.3.2 3rd bullet has to be changed to indicate XML
> > package instead
> > > of Event package
> >
> > [AndyH] Noted. I will need to review this once we have adopted the
> > protocol draft and make sure it is aligned.
> >
> > >=20
> > > Sec 4.3.2 last bullet: is it required to pass metadata
> > using non-sip
> > > mechanism?
> > >
> > [AndyH] I will remove this statement if that is ok with everyone.
> >
> >
> > > Thanks
> > > Partha
> > >
> > > ________________________________
> > >
> > > From: siprec-bounces@ietf.org on behalf of Elwell, John
> > > Sent: Wed 3/2/2011 10:25 PM
> > > To: siprec@ietf.org
> > > Subject: [siprec] Progressing the architecture document
> > >
> > >
> > >
> > > draft-ietf-siprec-architecture has not moved forward much
> in recent
> > > months, waiting for progress on solutions to help confirm the
> > > architecture. Now would be an excellent time for people to
> > raise any
> > > issues that can perhaps be addressed by the editor before
> > the cut-off
> > > (2011-03-14) or discussed in Prague.
> > >
> > > John
> > >
> > > _______________________________________________
> > > 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
> >
>



------_=_NextPart_001_01CBE422.DA54599D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: Progressing the architecture =
document</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText40375>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 =
face=3DArial>Andy/Leon,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>I'm also interested =
in&nbsp;Beer discussion at Prague&nbsp;:-) Let us plan for =
it</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>I understand Andy requirement =
to pass metadata in the need basis and not mandatory to pass always. =
IMO, it is reasonable requirement.&nbsp;I guess that option tag like =
"rs-metadata" between SRC and SRS may serve the purpose. In case =
rs-metadata&nbsp;is not&nbsp;received from SRS, SRC should not send =
metadata. Please let me know your opinion here.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> Leon Portman =
[mailto:Leon.Portman@nice.com]<BR><B>Sent:</B> Wed 3/16/2011 10:10 =
PM<BR><B>To:</B> Hutton, Andrew; Parthasarathi R (partr)<BR><B>Cc:</B> =
siprec@ietf.org<BR><B>Subject:</B> RE: Progressing the architecture =
document<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>+1 for beer<BR><BR>-----Original Message-----<BR>From: =
Hutton, Andrew [<A =
href=3D"mailto:andrew.hutton@siemens-enterprise.com">mailto:andrew.hutton=
@siemens-enterprise.com</A>]<BR>Sent: Wednesday, March 16, 2011 6:35 =
PM<BR>To: Leon Portman; Parthasarathi R (partr)<BR>Cc: =
siprec@ietf.org<BR>Subject: RE: Progressing the architecture =
document<BR><BR>Hi,<BR><BR>In my book that is not so basic.<BR><BR>I =
don't think we should mandate that the SRC provides metadata within an =
XML body. I don't see any reason for mandating that even if we think =
that all SRC's will do so. There is always going to be some =
implementation for which this is not necessary.<BR><BR>The question then =
is does it help the SRS to know whether the SRC is capable of sending =
metadata if for example it asked for a snapshot. I tend to think this =
would be helpful but it is not a big issue for me.<BR><BR>It might also =
be helpful if the SRS could tell the SRC that it is not interested in =
metadata for a given recording session. This might prevent lots of =
bandwidth being used sending metadata just for the SRS to ignore =
it.<BR><BR>Just my honest thoughts I look forward to some discussion =
over a beer in Prague.<BR><BR>Regards<BR>Andy<BR><BR><BR><BR>&gt; =
-----Original Message-----<BR>&gt; From: Leon Portman [<A =
href=3D"mailto:Leon.Portman@nice.com">mailto:Leon.Portman@nice.com</A>]<B=
R>&gt; Sent: 16 March 2011 16:08<BR>&gt; To: Hutton, Andrew; =
Parthasarathi R (partr)<BR>&gt; Cc: siprec@ietf.org<BR>&gt; Subject: RE: =
Progressing the architecture document<BR>&gt;<BR>&gt; Andy =
Hi<BR>&gt;<BR>&gt; Actually participants of the CS are basic info as =
well and I think<BR>&gt; that XML is required for it.<BR>&gt;<BR>&gt; =
Leon<BR>&gt;<BR>&gt; -----Original Message-----<BR>&gt; From: Hutton, =
Andrew [<A =
href=3D"mailto:andrew.hutton@siemens-enterprise.com">mailto:andrew.hutton=
@siemens-enterprise.com</A>]<BR>&gt; Sent: Wednesday, March 16, 2011 =
6:05 PM<BR>&gt; To: Leon Portman; Parthasarathi R (partr)<BR>&gt; Cc: =
siprec@ietf.org<BR>&gt; Subject: RE: Progressing the architecture =
document<BR>&gt;<BR>&gt; Hi Leon,<BR>&gt;<BR>&gt; At the most basic =
level an SRS may I assume not need any metadata. For<BR>&gt; example it =
could be that simply the date and time of the recording is<BR>&gt; all =
that is needed for metadata and we don't need XML for =
that.<BR>&gt;<BR>&gt; The question is whether the SRS needs to be given =
an explicit<BR>&gt; indication from the SRC that no metadata will be =
generated and that<BR>&gt; probably depends on the mechanism for =
delivering it.<BR>&gt;<BR>&gt; Regards<BR>&gt; =
Andy<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;<BR>&gt;<BR>&gt; &gt; =
-----Original Message-----<BR>&gt; &gt; From: Leon Portman [<A =
href=3D"mailto:Leon.Portman@nice.com">mailto:Leon.Portman@nice.com</A>]<B=
R>&gt; &gt; Sent: 16 March 2011 15:55<BR>&gt; &gt; To: Hutton, Andrew; =
Parthasarathi R (partr)<BR>&gt; &gt; Cc: siprec@ietf.org<BR>&gt; &gt; =
Subject: RE: Progressing the architecture document<BR>&gt; &gt;<BR>&gt; =
&gt; Partha and Andy Hi<BR>&gt; &gt;<BR>&gt; &gt; I want to address the =
point regarding indication if SRC supports<BR>&gt; &gt; metadata. I =
think we need to assume that all SRC supports metadata<BR>&gt; &gt; =
reporting otherwise SRS will not know what it is actually<BR>&gt; =
recording.<BR>&gt; &gt; It is very hard for me to find configuration =
where SRC will<BR>&gt; implement<BR>&gt; &gt; SIPREC but not will be =
able to populate metadata XML.<BR>&gt; &gt; At least on basic =
level.<BR>&gt; &gt;<BR>&gt; &gt; Leon<BR>&gt; &gt;<BR>&gt; &gt; =
-----Original Message-----<BR>&gt; &gt; From: =
siprec-bounces@ietf.org<BR>&gt; &gt; [<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>] On Behalf Of Hutton, Andrew<BR>&gt; &gt; Sent: Tuesday, March 15, =
2011 6:00 PM<BR>&gt; &gt; To: Parthasarathi R (partr)<BR>&gt; &gt; Cc: =
siprec@ietf.org<BR>&gt; &gt; Subject: Re: [siprec] Progressing the =
architecture document<BR>&gt; &gt;<BR>&gt; &gt; Hi Partha,<BR>&gt; =
&gt;<BR>&gt; &gt; Thanks for your comments.<BR>&gt; &gt;<BR>&gt; &gt; =
See below.<BR>&gt; &gt;<BR>&gt; &gt; Regards<BR>&gt; &gt; Andy<BR>&gt; =
&gt;&nbsp;<BR>&gt; &gt;<BR>&gt; &gt; &gt; -----Original =
Message-----<BR>&gt; &gt; &gt; From: siprec-bounces@ietf.org<BR>&gt; =
&gt; &gt; [<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>] On Behalf Of Parthasarathi<BR>&gt; &gt; R (partr)<BR>&gt; &gt; &gt; =
Sent: 14 March 2011 17:05<BR>&gt; &gt; &gt; To: Elwell, John; =
siprec@ietf.org<BR>&gt; &gt; &gt; Subject: Re: [siprec] Progressing the =
architecture document<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; SIPREC =
Architecture-01 draft looks good in the high level.<BR>&gt; &gt; &gt; =
Some of the minor comments are as follows:<BR>&gt; &gt; =
&gt;&nbsp;<BR>&gt; &gt; &gt; Sec 4.1.4 Fig 3 indicates about SRS having =
AS &amp; MS, it may be<BR>&gt; &gt; &gt; preferred to indicate that SRC =
also has AS &amp; MS clubbed<BR>&gt; &gt; together. IMO,<BR>&gt; &gt; =
&gt; this provide more clarity while reading.<BR>&gt; &gt;<BR>&gt; &gt; =
[AndyH] The related text does state that the SRC could also be<BR>&gt; =
&gt; decomposed in this way and Fig 3. is just one example. I think =
the<BR>&gt; &gt; figure showing the SRS better illustrates the relation =
to mediactrl<BR>&gt; &gt; with regard to recording so I prefer the =
current diagram.<BR>&gt; Why do you<BR>&gt; &gt; think the showing the =
SRC in this way would add clarity? I could of<BR>&gt; &gt; course =
include both but not sure this is really necessary.<BR>&gt; &gt;<BR>&gt; =
&gt; &gt;&nbsp;<BR>&gt; &gt; &gt; Sec 4.1.5 Figure shall be added to =
indicate a scenarion<BR>&gt; &gt; whererin focus<BR>&gt; &gt; &gt; acts =
as SRC.<BR>&gt; &gt;<BR>&gt; &gt; [AndyH] I will look at creating a =
diagram.<BR>&gt; &gt;<BR>&gt; &gt; &gt;&nbsp;<BR>&gt; &gt; &gt; Sec 4.2 =
Para 2 example does not go inline with REQ-024 of -07<BR>&gt; &gt; &gt; =
Requirement draft. The example shall change from "client<BR>&gt; &gt; =
must decrypt"<BR>&gt; &gt; &gt; to "client may decrypt".<BR>&gt; =
&gt;<BR>&gt; &gt; [AndyH] I think I have to remove the whole sentence as =
the<BR>&gt; example is<BR>&gt; &gt; no longer valid.<BR>&gt; =
&gt;<BR>&gt; &gt; &gt;&nbsp;<BR>&gt; &gt; &gt; Sec 4.2.1 Fourth bullet =
text may be preferred to change as<BR>&gt; &gt; "Indicate<BR>&gt; &gt; =
&gt; support for the recording metadata"<BR>&gt; &gt;<BR>&gt; &gt; =
[AndyH] Have we decided whether we have any indication from the =
SRC<BR>&gt; &gt; that it supports metadata? I did not think so therefore =
this is an<BR>&gt; &gt; open issue but probably not relevant to the =
architecture draft. I<BR>&gt; &gt; probably should remove the mechanism =
related stuff and at<BR>&gt; some point<BR>&gt; &gt; reference the =
protocol draft. Do you agree?<BR>&gt; &gt;<BR>&gt; &gt; =
&gt;&nbsp;<BR>&gt; &gt; &gt; Sec 4.2.3 change "sendonly" or "recvonly" =
to "recvonly" or<BR>&gt; &gt; "sendonly<BR>&gt; &gt; &gt; as it is =
indicated as SRS and SRC in the beginning of the line.<BR>&gt; =
&gt;<BR>&gt; &gt; [AndyH] Done.<BR>&gt; &gt;<BR>&gt; &gt; =
&gt;&nbsp;<BR>&gt; &gt; &gt; Sec 4.3.1 1st bullet shall be changed from =
"Dialog identifier" to<BR>&gt; &gt; &gt; "Communication Session =
Identifier"<BR>&gt; &gt;<BR>&gt; &gt; [AndyH] Note sure about this the =
current text states "Dialog<BR>&gt; &gt; identifiers for the =
Communication Session" which seems<BR>&gt; correct to me.<BR>&gt; &gt; =
This will probably get removed anyway and replaced to a<BR>&gt; =
reference to<BR>&gt; &gt; the metadata model when it is adopted.<BR>&gt; =
&gt;<BR>&gt; &gt; &gt;&nbsp;<BR>&gt; &gt; &gt; Sec 4.3.1 whether 3rd =
bullet is required?<BR>&gt; &gt; &gt;&nbsp;<BR>&gt; &gt;<BR>&gt; &gt; =
[AndyH]I assume it is as for example I assume it would be<BR>&gt; =
necessary to<BR>&gt; &gt; record early-media and update the SRS when the =
dialog<BR>&gt; changes to the<BR>&gt; &gt; confirmed or terminated =
state. Does not seem to be in the metadata<BR>&gt; &gt; draft though. In =
the end I will either remove these bullets<BR>&gt; or align<BR>&gt; &gt; =
with the metadata draft.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; &gt; =
General comment: it is preferred to change to "should, must"<BR>&gt; =
&gt; &gt; to "SHOULD, MUST" as per RFC 2119<BR>&gt; &gt;<BR>&gt; &gt; =
[AndyH]I think I need to remove all RFC 2119 wording as it is =
not<BR>&gt; &gt; appropriate to the architecture draft. I will remove =
all<BR>&gt; such wording<BR>&gt; &gt; and the reference to RFC 2119. Is =
that ok ?<BR>&gt; &gt;<BR>&gt; &gt; &gt;&nbsp;<BR>&gt; &gt; &gt; Sec =
4.3.2 1st bullet has to be removed as it is not<BR>&gt; &gt; required =
any more.<BR>&gt; &gt; &gt;&nbsp;<BR>&gt; &gt; [AndyH]OK are there =
really no information in SIP Headers<BR>&gt; that could be<BR>&gt; &gt; =
stored as metadata?<BR>&gt; &gt;<BR>&gt; &gt; &gt; Sec 4.3.2 3rd bullet =
has to be changed to indicate XML<BR>&gt; &gt; package instead<BR>&gt; =
&gt; &gt; of Event package<BR>&gt; &gt;<BR>&gt; &gt; [AndyH] Noted. I =
will need to review this once we have adopted the<BR>&gt; &gt; protocol =
draft and make sure it is aligned.<BR>&gt; &gt;<BR>&gt; &gt; =
&gt;&nbsp;<BR>&gt; &gt; &gt; Sec 4.3.2 last bullet: is it required to =
pass metadata<BR>&gt; &gt; using non-sip<BR>&gt; &gt; &gt; =
mechanism?<BR>&gt; &gt; &gt;<BR>&gt; &gt; [AndyH] I will remove this =
statement if that is ok with everyone.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; =
&gt; &gt; Thanks<BR>&gt; &gt; &gt; Partha<BR>&gt; &gt; &gt;<BR>&gt; &gt; =
&gt; ________________________________<BR>&gt; &gt; &gt;<BR>&gt; &gt; =
&gt; From: siprec-bounces@ietf.org on behalf of Elwell, John<BR>&gt; =
&gt; &gt; Sent: Wed 3/2/2011 10:25 PM<BR>&gt; &gt; &gt; To: =
siprec@ietf.org<BR>&gt; &gt; &gt; Subject: [siprec] Progressing the =
architecture document<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt; draft-ietf-siprec-architecture has not moved =
forward much<BR>&gt; in recent<BR>&gt; &gt; &gt; months, waiting for =
progress on solutions to help confirm the<BR>&gt; &gt; &gt; =
architecture. Now would be an excellent time for people to<BR>&gt; &gt; =
raise any<BR>&gt; &gt; &gt; issues that can perhaps be addressed by the =
editor before<BR>&gt; &gt; the cut-off<BR>&gt; &gt; &gt; (2011-03-14) or =
discussed in Prague.<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; John<BR>&gt; =
&gt; &gt;<BR>&gt; &gt; &gt; =
_______________________________________________<BR>&gt; &gt; &gt; siprec =
mailing list<BR>&gt; &gt; &gt; siprec@ietf.org<BR>&gt; &gt; &gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR>&gt; &gt; &gt;<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; =
_______________________________________________<BR>&gt; &gt; siprec =
mailing list<BR>&gt; &gt; siprec@ietf.org<BR>&gt; &gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.or=
g/mailman/listinfo/siprec</A><BR>&gt; =
&gt;<BR>&gt;<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01CBE422.DA54599D--

From rmohanr@cisco.com  Thu Mar 17 00:05:02 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36F1C3A6800 for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.348
X-Spam-Level: 
X-Spam-Status: No, score=-10.348 tagged_above=-999 required=5 tests=[AWL=0.251, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6tkMWKR+Wvmn for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:05:00 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 26D983A67AE for <siprec@ietf.org>; Thu, 17 Mar 2011 00:05:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=6586; q=dns/txt; s=iport; t=1300345588; x=1301555188; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=95NItPlD04GYKxTcuwy+38eegswKwHnu8Hp+tJXcJyU=; b=f4Sz0wT635KmAhXKasLgvfvf8jO5xelNVDo0XYtM7kEIVWL+a5C56Oa8 J68y/dH61G+X8I1GP2YcljYXdd9aulsawui6VfGpASW4zYGzGZaEy/bJK o6mY8kYpxMe7JbKUg1qpOYJzCERblIio2srnSgxLUUIyIl+VBNbju2R6X I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0BAPVPgU2Q/khLgWdsb2JhbACYHI0yFAEBFiYlpxicNYJ7gmgEhS2LBA
X-IronPort-AV: E=Sophos;i="4.63,198,1299456000"; d="scan'208";a="22057893"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 17 Mar 2011 07:06:26 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2H76Jk0022285; Thu, 17 Mar 2011 07:06:26 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Mar 2011 12:36:25 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Mar 2011 12:36:21 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6A=
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 17 Mar 2011 07:06:25.0989 (UTC) FILETIME=[D4A01750:01CBE471]
Cc: siprec@ietf.org
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 07:05:02 -0000

Hi Leon / All,

See inline for my comments

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Leon Portman
> Sent: Wednesday, March 16, 2011 9:16 PM
> To: Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> I agree with points below that passing actual CS SDP to SRS is a not
> good idea from security and layers separation point of view.
> Today's SRS implementations(at least that I know about) do not keep
> original codec information in the database for later retrieval. I am
> trying to think about use cases why SRS can be interested in one, and
> except troubleshooting it is not very relevant.
>=20
> The main assumption is that SRC inspected CS SDP and extracted all
> relevant information like ip addresses, media line labels and infos
and
> reported it to SRS via metadata.

Are you still suggesting here that we pass across some of the parameters
of CS SDP that you mentioned above to SRS via metadata ? Are there any
applications at SRS which may require this information ?

I vaguely remember during IETF 79 presentation that some folks (mainly
from video perspective) were asking for part of information related to
CS SDP to be passed in metadata. But not too sure about the use cases
for the same.=20
I would request people on the mailer list to speak up if there are any
use cases.


IMO if there is only some specific SRS applications that need this, it's
better to pass it as extension data rather than having it as attribute
of MS block in the metadata.


Regards,
Ram

>=20
> The main reason as I see if we want to be able to report CS SDP via
> metadata is for the case where SRS wants to sniff RS RTP packets
> directly and not by forking from SRC but it is out of scope.
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
> Sent: Wednesday, March 16, 2011 3:33 PM
> To: Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> I believe the codec parameters on the MS have been there since my
first
> cut at the metadata model. Putting them there was just speculation on
> my part, and doesn't imply any actual need known to me.
>=20
> If nobody feels they are necessary, then by all means remove them.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/16/2011 3:34 AM, Elwell, John wrote:
> >
> >
> >> -----Original Message-----
> >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> >> Sent: 16 March 2011 01:25
> >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> >> Cc: siprec@ietf.org
> >> Subject: CS Codec Parameter in stream XML element [was RE:
> >> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
> >>
> > <snip/>
> >> <Partha>  It is the assumption done during metadata format that RS
> >> SDP may be used as Codec params for stream. Please note that format
> >> draft does not have codec param in stream metadata element. But the
> >> assumption does not seems to be working for all scenarios. So we
> need
> >> to find the way to represent CS Media stream in metadata format.
> >>
> >> Even before going into approach, I'm interested in knowing whether
> it
> >> is required for SRS to understand the exact codec or SDP parameter
> >> used in CS? RS may be transcoded/transrated and lost the actual
> media
> >> information when it reaches SRS but the question is whether it is
> >> required to maintain the metadata in SRS even though media (RTP) is
> >> changed to new format ?
> >>
> >> In case we decide to pass CS codec parameter to SRS. Two approaches
> >> exist to solve this issue:
> >>
> >> 1) Tunnel complete each participant SDP inside stream element using
> >> some new optional XML element. This approach is straightforward and
> >> scale for any CS as we are sending the complete set. The overhead
> >> will be increased in SRS to parse and store appropriately.
> >>
> >> 2) Identify the list of codec parameters *MUST*  be passed from SRC
> >> to SRS and create the new XML element for them. This is simple to
> >> implement as only portion of the SDP is passed across but *may*
have
> >> scalability issue.
> >>
> >> I prefer 1st approach because it covers all scenarios. I'm
> interested
> >> in hearing from you which way to go.
> >>
> >> </partha>
> > [JRE] I was basing my earlier comment on the fact that the metadata
> model seems to indicate that the Media Stream object has CS codec
> parameters as an attribute. This is indeed questionable. I seem to
> remember somebody wanting this at some stage in the past. From my
point
> of view, I don't think this information is needed by the SRS - it is
> historic information, nothing to do with the media actually sent to
the
> SRS, and of no use to the SRS, in my opinion.
> >
> > If people do think there is a reason for providing this information
> to the SRS, I don't think I would favour approach 1) above. The SDP
> could potentially contain all sorts of information other than codecs
> (codecs are only a small part, and the SDP will contain information
> like IP addresses, ports, security keys!!!, transport, non-recorded
> media descriptions (e.g., MSRP channel, BFCP channel), format
> parameters, SDP capability negotiation attributes, etc..
> >
> > Moreover, the offerer and answerer might have agreed several codecs
> in the SDP, so you need to look at RTP to see which codec is actually
> used. This can change on the fly.
> >
> > Finally, although the SRS's SIP/SDP stack will surely have and SDP
> parser, the XML metadata is intended for passing to an application.
> Requiring that application to contain an SDP parser is, I think,
> unreasonable.
> >
> > So I have doubts as to whether it is really feasible to provide CS
> codec information in metadata to the SRS in a meaningful way, whether
> this be using approach 1) or approach 2), but I particularly dislike
> approach 1).
> >
> > John (as individual)
> _______________________________________________
> 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

From Leon.Portman@nice.com  Thu Mar 17 00:11:07 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D98FD3A67FC for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fU7AtHooBcMg for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:11:06 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id BDADE3A67F7 for <siprec@ietf.org>; Thu, 17 Mar 2011 00:11:05 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Thu, 17 Mar 2011 09:12:32 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Thu, 17 Mar 2011 09:12:31 +0200
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UA==
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 07:11:08 -0000

Hi

I agree that if SRS need something from SDP it will be better to pass it vi=
a metadata extensions. I did some additional checks and currently there is =
no such requirement from SRS point of view.
Regarding video, there was requirement to report video session even if it i=
s not recorded.  And if it is recorded then all relevant information will b=
e reported via RS SDP such as positions, sizes etc.

Leon

-----Original Message-----
From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]=20
Sent: Thursday, March 17, 2011 9:06 AM
To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
Cc: siprec@ietf.org
Subject: RE: [siprec] CS Codec Parameter in stream XML element [was RE: Rev=
iew Request for draft-ram-siprec-metadata-format-01]

Hi Leon / All,

See inline for my comments

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> Behalf Of Leon Portman
> Sent: Wednesday, March 16, 2011 9:16 PM
> To: Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> I agree with points below that passing actual CS SDP to SRS is a not=20
> good idea from security and layers separation point of view.
> Today's SRS implementations(at least that I know about) do not keep=20
> original codec information in the database for later retrieval. I am=20
> trying to think about use cases why SRS can be interested in one, and=20
> except troubleshooting it is not very relevant.
>=20
> The main assumption is that SRC inspected CS SDP and extracted all=20
> relevant information like ip addresses, media line labels and infos
and
> reported it to SRS via metadata.

Are you still suggesting here that we pass across some of the parameters of=
 CS SDP that you mentioned above to SRS via metadata ? Are there any applic=
ations at SRS which may require this information ?

I vaguely remember during IETF 79 presentation that some folks (mainly from=
 video perspective) were asking for part of information related to CS SDP t=
o be passed in metadata. But not too sure about the use cases for the same.=
=20
I would request people on the mailer list to speak up if there are any use =
cases.


IMO if there is only some specific SRS applications that need this, it's be=
tter to pass it as extension data rather than having it as attribute of MS =
block in the metadata.


Regards,
Ram

>=20
> The main reason as I see if we want to be able to report CS SDP via=20
> metadata is for the case where SRS wants to sniff RS RTP packets=20
> directly and not by forking from SRC but it is out of scope.
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> Behalf Of Paul Kyzivat
> Sent: Wednesday, March 16, 2011 3:33 PM
> To: Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> I believe the codec parameters on the MS have been there since my
first
> cut at the metadata model. Putting them there was just speculation on=20
> my part, and doesn't imply any actual need known to me.
>=20
> If nobody feels they are necessary, then by all means remove them.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/16/2011 3:34 AM, Elwell, John wrote:
> >
> >
> >> -----Original Message-----
> >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> >> Sent: 16 March 2011 01:25
> >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> >> Cc: siprec@ietf.org
> >> Subject: CS Codec Parameter in stream XML element [was RE:
> >> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
> >>
> > <snip/>
> >> <Partha>  It is the assumption done during metadata format that RS=20
> >> SDP may be used as Codec params for stream. Please note that format=20
> >> draft does not have codec param in stream metadata element. But the=20
> >> assumption does not seems to be working for all scenarios. So we
> need
> >> to find the way to represent CS Media stream in metadata format.
> >>
> >> Even before going into approach, I'm interested in knowing whether
> it
> >> is required for SRS to understand the exact codec or SDP parameter=20
> >> used in CS? RS may be transcoded/transrated and lost the actual
> media
> >> information when it reaches SRS but the question is whether it is=20
> >> required to maintain the metadata in SRS even though media (RTP) is=20
> >> changed to new format ?
> >>
> >> In case we decide to pass CS codec parameter to SRS. Two approaches=20
> >> exist to solve this issue:
> >>
> >> 1) Tunnel complete each participant SDP inside stream element using=20
> >> some new optional XML element. This approach is straightforward and=20
> >> scale for any CS as we are sending the complete set. The overhead=20
> >> will be increased in SRS to parse and store appropriately.
> >>
> >> 2) Identify the list of codec parameters *MUST*  be passed from SRC=20
> >> to SRS and create the new XML element for them. This is simple to=20
> >> implement as only portion of the SDP is passed across but *may*
have
> >> scalability issue.
> >>
> >> I prefer 1st approach because it covers all scenarios. I'm
> interested
> >> in hearing from you which way to go.
> >>
> >> </partha>
> > [JRE] I was basing my earlier comment on the fact that the metadata
> model seems to indicate that the Media Stream object has CS codec=20
> parameters as an attribute. This is indeed questionable. I seem to=20
> remember somebody wanting this at some stage in the past. From my
point
> of view, I don't think this information is needed by the SRS - it is=20
> historic information, nothing to do with the media actually sent to
the
> SRS, and of no use to the SRS, in my opinion.
> >
> > If people do think there is a reason for providing this information
> to the SRS, I don't think I would favour approach 1) above. The SDP=20
> could potentially contain all sorts of information other than codecs=20
> (codecs are only a small part, and the SDP will contain information=20
> like IP addresses, ports, security keys!!!, transport, non-recorded=20
> media descriptions (e.g., MSRP channel, BFCP channel), format=20
> parameters, SDP capability negotiation attributes, etc..
> >
> > Moreover, the offerer and answerer might have agreed several codecs
> in the SDP, so you need to look at RTP to see which codec is actually=20
> used. This can change on the fly.
> >
> > Finally, although the SRS's SIP/SDP stack will surely have and SDP
> parser, the XML metadata is intended for passing to an application.
> Requiring that application to contain an SDP parser is, I think,=20
> unreasonable.
> >
> > So I have doubts as to whether it is really feasible to provide CS
> codec information in metadata to the SRS in a meaningful way, whether=20
> this be using approach 1) or approach 2), but I particularly dislike=20
> approach 1).
> >
> > John (as individual)
> _______________________________________________
> 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

From Leon.Portman@nice.com  Thu Mar 17 00:11:26 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 113723A6A4D for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 tagged_above=-999 required=5 tests=[AWL=0.240,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w5TaEpLT2uQ2 for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:11:24 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id A7D973A67F7 for <siprec@ietf.org>; Thu, 17 Mar 2011 00:11:23 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Thu, 17 Mar 2011 09:12:49 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Thu, 17 Mar 2011 09:12:48 +0200
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgAAO42HAAHNs3wA==
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A9491701@TLVMBX01.nice.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com> <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net> <4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA086A964829@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A964829@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 07:11:26 -0000

Yes, I think we don't need it

Leon

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Wednesday, March 16, 2011 7:29 PM
To: Leon Portman; Paul Kyzivat
Cc: siprec@ietf.org
Subject: RE: [siprec] CS Codec Parameter in stream XML element [was RE: Rev=
iew Request for draft-ram-siprec-metadata-format-01]

Leon,

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 16 March 2011 15:46
> To: Paul Kyzivat; Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was=20
> RE: Review Request for draft-ram-siprec-metadata-format-01]
>=20
> I agree with points below that passing actual CS SDP to SRS is a not=20
> good idea from security and layers separation point of view.
> Today's SRS implementations(at least that I know about) do not keep=20
> original codec information in the database for later retrieval. I am=20
> trying to think about use cases why SRS can be interested in one, and=20
> except troubleshooting it is not very relevant.
> The main assumption is that SRC inspected CS SDP and extracted all=20
> relevant information like ip addresses, media line labels and infos=20
> and reported it to SRS via metadata.
[JRE] Why would the SRS need to know anything about CS IP addresses?

>=20
> The main reason as I see if we want to be able to report CS SDP via=20
> metadata is for the case where SRS wants to sniff RS RTP packets=20
> directly and not by forking from SRC but it is out of scope.
[JRE] So I assume you agree that there is no need for metadata to include C=
S codecs (or, for that matter CS IP addresses, ports, etc.).

John (as individual)

>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: Wednesday, March 16, 2011 3:33 PM
> To: Elwell, John
> Cc: siprec@ietf.org
> Subject: Re: [siprec] CS Codec Parameter in stream XML element [was=20
> RE: Review Request for draft-ram-siprec-metadata-format-01]
>=20
> I believe the codec parameters on the MS have been there since my=20
> first cut at the metadata model. Putting them there was just=20
> speculation on my part, and doesn't imply any actual need known to me.
>=20
> If nobody feels they are necessary, then by all means remove them.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/16/2011 3:34 AM, Elwell, John wrote:
> >
> >
> >> -----Original Message-----
> >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> >> Sent: 16 March 2011 01:25
> >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> >> Cc: siprec@ietf.org
> >> Subject: CS Codec Parameter in stream XML element [was RE:
> >> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
> >>
> > <snip/>
> >> <Partha>  It is the assumption done during metadata format that RS=20
> >> SDP may be used as Codec params for stream. Please note
> that format
> >> draft does not have codec param in stream metadata
> element. But the
> >> assumption does not seems to be working for all scenarios.=20
> So we need
> >> to find the way to represent CS Media stream in metadata format.
> >>
> >> Even before going into approach, I'm interested in knowing
> whether it
> >> is required for SRS to understand the exact codec or SDP parameter=20
> >> used in CS? RS may be transcoded/transrated and lost the
> actual media
> >> information when it reaches SRS but the question is whether it is=20
> >> required to maintain the metadata in SRS even though media
> (RTP) is
> >> changed to new format ?
> >>
> >> In case we decide to pass CS codec parameter to SRS. Two
> approaches
> >> exist to solve this issue:
> >>
> >> 1) Tunnel complete each participant SDP inside stream
> element using
> >> some new optional XML element. This approach is
> straightforward and
> >> scale for any CS as we are sending the complete set. The overhead=20
> >> will be increased in SRS to parse and store appropriately.
> >>
> >> 2) Identify the list of codec parameters *MUST*  be passed
> from SRC
> >> to SRS and create the new XML element for them. This is simple to=20
> >> implement as only portion of the SDP is passed across but
> *may* have
> >> scalability issue.
> >>
> >> I prefer 1st approach because it covers all scenarios. I'm
> interested
> >> in hearing from you which way to go.
> >>
> >> </partha>
> > [JRE] I was basing my earlier comment on the fact that the
> metadata model seems to indicate that the Media Stream object has CS=20
> codec parameters as an attribute. This is indeed questionable. I seem=20
> to remember somebody wanting this at some stage in the past. From my=20
> point of view, I don't think this information is needed by the SRS -=20
> it is historic information, nothing to do with the media actually sent=20
> to the SRS, and of no use to the SRS, in my opinion.
> >
> > If people do think there is a reason for providing this
> information to the SRS, I don't think I would favour approach
> 1) above. The SDP could potentially contain all sorts of information=20
> other than codecs (codecs are only a small part, and the SDP will=20
> contain information like IP addresses, ports, security keys!!!,=20
> transport, non-recorded media descriptions (e.g., MSRP channel, BFCP=20
> channel), format parameters, SDP capability negotiation attributes,=20
> etc..
> >
> > Moreover, the offerer and answerer might have agreed
> several codecs in the SDP, so you need to look at RTP to see which=20
> codec is actually used. This can change on the fly.
> >
> > Finally, although the SRS's SIP/SDP stack will surely have
> and SDP parser, the XML metadata is intended for passing to an=20
> application. Requiring that application to contain an SDP parser is, I=20
> think, unreasonable.
> >
> > So I have doubts as to whether it is really feasible to
> provide CS codec information in metadata to the SRS in a meaningful=20
> way, whether this be using approach 1) or approach 2), but I=20
> particularly dislike approach 1).
> >
> > John (as individual)
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20

From rmohanr@cisco.com  Thu Mar 17 00:24:27 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EC6D3A680C for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.375
X-Spam-Level: 
X-Spam-Status: No, score=-10.375 tagged_above=-999 required=5 tests=[AWL=0.224, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SEVv2sq+QGgj for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:24:25 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 9C6303A67DB for <siprec@ietf.org>; Thu, 17 Mar 2011 00:24:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=8662; q=dns/txt; s=iport; t=1300346753; x=1301556353; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=BrKV8ZEMiGNgk896WUZxWWn/xQuAwN5CYGGclNKJFyg=; b=GvI08LBRPuRgeFgExvPPSHykooNPsC24mEnW1ydvrjZ+l9M9vk+Zf+7f JoiPyszXvdgWj0xi854lGW7conToMJG6qK8x4hD+QJSHqkb24zF0o7+ch eTI3nAAkFxeCxyj8XwcfeSCSIk8yp2ddJQjC/oIcJqNts4wrgWwNNQ2G2 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjABALNTgU2tJV2d/2dsb2JhbACYHI0yd6cznDOCe4JoBIUtiwQ
X-IronPort-AV: E=Sophos;i="4.63,198,1299456000"; d="scan'208";a="276943345"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by sj-iport-4.cisco.com with ESMTP; 17 Mar 2011 07:25:52 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id p2H7PiPg029160; Thu, 17 Mar 2011 07:25:51 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Mar 2011 12:55:48 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Mar 2011 12:55:44 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQ
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 17 Mar 2011 07:25:48.0582 (UTC) FILETIME=[8995B460:01CBE474]
Cc: siprec@ietf.org
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 07:24:27 -0000

Inline=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Thursday, March 17, 2011 12:43 PM
> To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Hi
>=20
> I agree that if SRS need something from SDP it will be better to pass
> it via metadata extensions. I did some additional checks and currently
> there is no such requirement from SRS point of view.
> Regarding video, there was requirement to report video session even if
> it is not recorded.  And if it is recorded then all relevant
> information will be reported via RS SDP such as positions, sizes etc.

For cases where Video is not recorded, there are two possibilities:
1) Video is offered by SRC in RS SDP to SRS but SRS choose to reject
video. In this case SRC can still continue to send updates via RS SDP to
SRS.=20

2) SRC may not have capability to record video and may not offer video
to SRS in RS SDP.  In this case also we can send a offer (m=3D0) from =
SRC
to SRS having video information.

 My question here is - what information do we see a need to report ? Is
it just the information that video is part of CS or more than that ?

Ram

>=20
> Leon
>=20
> -----Original Message-----
> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> Sent: Thursday, March 17, 2011 9:06 AM
> To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Hi Leon / All,
>=20
> See inline for my comments
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Leon Portman
> > Sent: Wednesday, March 16, 2011 9:16 PM
> > To: Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > I agree with points below that passing actual CS SDP to SRS is a not
> > good idea from security and layers separation point of view.
> > Today's SRS implementations(at least that I know about) do not keep
> > original codec information in the database for later retrieval. I am
> > trying to think about use cases why SRS can be interested in one,
and
> > except troubleshooting it is not very relevant.
> >
> > The main assumption is that SRC inspected CS SDP and extracted all
> > relevant information like ip addresses, media line labels and infos
> and
> > reported it to SRS via metadata.
>=20
> Are you still suggesting here that we pass across some of the
> parameters of CS SDP that you mentioned above to SRS via metadata ?
Are
> there any applications at SRS which may require this information ?
>=20
> I vaguely remember during IETF 79 presentation that some folks (mainly
> from video perspective) were asking for part of information related to
> CS SDP to be passed in metadata. But not too sure about the use cases
> for the same.
> I would request people on the mailer list to speak up if there are any
> use cases.
>=20
>=20
> IMO if there is only some specific SRS applications that need this,
> it's better to pass it as extension data rather than having it as
> attribute of MS block in the metadata.
>=20
>=20
> Regards,
> Ram
>=20
> >
> > The main reason as I see if we want to be able to report CS SDP via
> > metadata is for the case where SRS wants to sniff RS RTP packets
> > directly and not by forking from SRC but it is out of scope.
> >
> > Leon
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Paul Kyzivat
> > Sent: Wednesday, March 16, 2011 3:33 PM
> > To: Elwell, John
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > I believe the codec parameters on the MS have been there since my
> first
> > cut at the metadata model. Putting them there was just speculation
on
> > my part, and doesn't imply any actual need known to me.
> >
> > If nobody feels they are necessary, then by all means remove them.
> >
> > 	Thanks,
> > 	Paul
> >
> > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > >
> > >
> > >> -----Original Message-----
> > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > >> Sent: 16 March 2011 01:25
> > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > >> Cc: siprec@ietf.org
> > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > >> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
> > >>
> > > <snip/>
> > >> <Partha>  It is the assumption done during metadata format that
RS
> > >> SDP may be used as Codec params for stream. Please note that
> format
> > >> draft does not have codec param in stream metadata element. But
> the
> > >> assumption does not seems to be working for all scenarios. So we
> > need
> > >> to find the way to represent CS Media stream in metadata format.
> > >>
> > >> Even before going into approach, I'm interested in knowing
whether
> > it
> > >> is required for SRS to understand the exact codec or SDP
parameter
> > >> used in CS? RS may be transcoded/transrated and lost the actual
> > media
> > >> information when it reaches SRS but the question is whether it is
> > >> required to maintain the metadata in SRS even though media (RTP)
> is
> > >> changed to new format ?
> > >>
> > >> In case we decide to pass CS codec parameter to SRS. Two
> approaches
> > >> exist to solve this issue:
> > >>
> > >> 1) Tunnel complete each participant SDP inside stream element
> using
> > >> some new optional XML element. This approach is straightforward
> and
> > >> scale for any CS as we are sending the complete set. The overhead
> > >> will be increased in SRS to parse and store appropriately.
> > >>
> > >> 2) Identify the list of codec parameters *MUST*  be passed from
> SRC
> > >> to SRS and create the new XML element for them. This is simple to
> > >> implement as only portion of the SDP is passed across but *may*
> have
> > >> scalability issue.
> > >>
> > >> I prefer 1st approach because it covers all scenarios. I'm
> > interested
> > >> in hearing from you which way to go.
> > >>
> > >> </partha>
> > > [JRE] I was basing my earlier comment on the fact that the
metadata
> > model seems to indicate that the Media Stream object has CS codec
> > parameters as an attribute. This is indeed questionable. I seem to
> > remember somebody wanting this at some stage in the past. From my
> point
> > of view, I don't think this information is needed by the SRS - it is
> > historic information, nothing to do with the media actually sent to
> the
> > SRS, and of no use to the SRS, in my opinion.
> > >
> > > If people do think there is a reason for providing this
information
> > to the SRS, I don't think I would favour approach 1) above. The SDP
> > could potentially contain all sorts of information other than codecs
> > (codecs are only a small part, and the SDP will contain information
> > like IP addresses, ports, security keys!!!, transport, non-recorded
> > media descriptions (e.g., MSRP channel, BFCP channel), format
> > parameters, SDP capability negotiation attributes, etc..
> > >
> > > Moreover, the offerer and answerer might have agreed several
codecs
> > in the SDP, so you need to look at RTP to see which codec is
actually
> > used. This can change on the fly.
> > >
> > > Finally, although the SRS's SIP/SDP stack will surely have and SDP
> > parser, the XML metadata is intended for passing to an application.
> > Requiring that application to contain an SDP parser is, I think,
> > unreasonable.
> > >
> > > So I have doubts as to whether it is really feasible to provide CS
> > codec information in metadata to the SRS in a meaningful way,
whether
> > this be using approach 1) or approach 2), but I particularly dislike
> > approach 1).
> > >
> > > John (as individual)
> > _______________________________________________
> > 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

From Leon.Portman@nice.com  Thu Mar 17 00:34:59 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B83C93A680C for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:34:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[AWL=0.231,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zv9avhU-+87W for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:34:58 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id BC5703A69F9 for <siprec@ietf.org>; Thu, 17 Mar 2011 00:34:57 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Thu, 17 Mar 2011 09:36:24 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Thu, 17 Mar 2011 09:36:23 +0200
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 07:34:59 -0000

Regarding information, most basic one is when video started and ended.

What about the configuration where SRC knows about video (because it is ins=
ide CS SIP session) but is not able to fork video. Is it still should offer=
 video m-line?

Leon

-----Original Message-----
From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]=20
Sent: Thursday, March 17, 2011 9:26 AM
To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
Cc: siprec@ietf.org
Subject: RE: [siprec] CS Codec Parameter in stream XML element [was RE: Rev=
iew Request for draft-ram-siprec-metadata-format-01]

Inline=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Thursday, March 17, 2011 12:43 PM
> To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Hi
>=20
> I agree that if SRS need something from SDP it will be better to pass=20
> it via metadata extensions. I did some additional checks and currently=20
> there is no such requirement from SRS point of view.
> Regarding video, there was requirement to report video session even if=20
> it is not recorded.  And if it is recorded then all relevant=20
> information will be reported via RS SDP such as positions, sizes etc.

For cases where Video is not recorded, there are two possibilities:
1) Video is offered by SRC in RS SDP to SRS but SRS choose to reject video.=
 In this case SRC can still continue to send updates via RS SDP to SRS.=20

2) SRC may not have capability to record video and may not offer video to S=
RS in RS SDP.  In this case also we can send a offer (m=3D0) from SRC to SR=
S having video information.

 My question here is - what information do we see a need to report ? Is it =
just the information that video is part of CS or more than that ?

Ram

>=20
> Leon
>=20
> -----Original Message-----
> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> Sent: Thursday, March 17, 2011 9:06 AM
> To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Hi Leon / All,
>=20
> See inline for my comments
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > Behalf Of Leon Portman
> > Sent: Wednesday, March 16, 2011 9:16 PM
> > To: Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > I agree with points below that passing actual CS SDP to SRS is a not=20
> > good idea from security and layers separation point of view.
> > Today's SRS implementations(at least that I know about) do not keep=20
> > original codec information in the database for later retrieval. I am=20
> > trying to think about use cases why SRS can be interested in one,
and
> > except troubleshooting it is not very relevant.
> >
> > The main assumption is that SRC inspected CS SDP and extracted all=20
> > relevant information like ip addresses, media line labels and infos
> and
> > reported it to SRS via metadata.
>=20
> Are you still suggesting here that we pass across some of the=20
> parameters of CS SDP that you mentioned above to SRS via metadata ?
Are
> there any applications at SRS which may require this information ?
>=20
> I vaguely remember during IETF 79 presentation that some folks (mainly=20
> from video perspective) were asking for part of information related to=20
> CS SDP to be passed in metadata. But not too sure about the use cases=20
> for the same.
> I would request people on the mailer list to speak up if there are any=20
> use cases.
>=20
>=20
> IMO if there is only some specific SRS applications that need this,=20
> it's better to pass it as extension data rather than having it as=20
> attribute of MS block in the metadata.
>=20
>=20
> Regards,
> Ram
>=20
> >
> > The main reason as I see if we want to be able to report CS SDP via=20
> > metadata is for the case where SRS wants to sniff RS RTP packets=20
> > directly and not by forking from SRC but it is out of scope.
> >
> > Leon
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > Behalf Of Paul Kyzivat
> > Sent: Wednesday, March 16, 2011 3:33 PM
> > To: Elwell, John
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > I believe the codec parameters on the MS have been there since my
> first
> > cut at the metadata model. Putting them there was just speculation
on
> > my part, and doesn't imply any actual need known to me.
> >
> > If nobody feels they are necessary, then by all means remove them.
> >
> > 	Thanks,
> > 	Paul
> >
> > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > >
> > >
> > >> -----Original Message-----
> > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > >> Sent: 16 March 2011 01:25
> > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > >> Cc: siprec@ietf.org
> > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > >> [siprec] Review Request for draft-ram-siprec-metadata-format-01]
> > >>
> > > <snip/>
> > >> <Partha>  It is the assumption done during metadata format that
RS
> > >> SDP may be used as Codec params for stream. Please note that
> format
> > >> draft does not have codec param in stream metadata element. But
> the
> > >> assumption does not seems to be working for all scenarios. So we
> > need
> > >> to find the way to represent CS Media stream in metadata format.
> > >>
> > >> Even before going into approach, I'm interested in knowing
whether
> > it
> > >> is required for SRS to understand the exact codec or SDP
parameter
> > >> used in CS? RS may be transcoded/transrated and lost the actual
> > media
> > >> information when it reaches SRS but the question is whether it is=20
> > >> required to maintain the metadata in SRS even though media (RTP)
> is
> > >> changed to new format ?
> > >>
> > >> In case we decide to pass CS codec parameter to SRS. Two
> approaches
> > >> exist to solve this issue:
> > >>
> > >> 1) Tunnel complete each participant SDP inside stream element
> using
> > >> some new optional XML element. This approach is straightforward
> and
> > >> scale for any CS as we are sending the complete set. The overhead=20
> > >> will be increased in SRS to parse and store appropriately.
> > >>
> > >> 2) Identify the list of codec parameters *MUST*  be passed from
> SRC
> > >> to SRS and create the new XML element for them. This is simple to=20
> > >> implement as only portion of the SDP is passed across but *may*
> have
> > >> scalability issue.
> > >>
> > >> I prefer 1st approach because it covers all scenarios. I'm
> > interested
> > >> in hearing from you which way to go.
> > >>
> > >> </partha>
> > > [JRE] I was basing my earlier comment on the fact that the
metadata
> > model seems to indicate that the Media Stream object has CS codec=20
> > parameters as an attribute. This is indeed questionable. I seem to=20
> > remember somebody wanting this at some stage in the past. From my
> point
> > of view, I don't think this information is needed by the SRS - it is=20
> > historic information, nothing to do with the media actually sent to
> the
> > SRS, and of no use to the SRS, in my opinion.
> > >
> > > If people do think there is a reason for providing this
information
> > to the SRS, I don't think I would favour approach 1) above. The SDP=20
> > could potentially contain all sorts of information other than codecs=20
> > (codecs are only a small part, and the SDP will contain information=20
> > like IP addresses, ports, security keys!!!, transport, non-recorded=20
> > media descriptions (e.g., MSRP channel, BFCP channel), format=20
> > parameters, SDP capability negotiation attributes, etc..
> > >
> > > Moreover, the offerer and answerer might have agreed several
codecs
> > in the SDP, so you need to look at RTP to see which codec is
actually
> > used. This can change on the fly.
> > >
> > > Finally, although the SRS's SIP/SDP stack will surely have and SDP
> > parser, the XML metadata is intended for passing to an application.
> > Requiring that application to contain an SDP parser is, I think,=20
> > unreasonable.
> > >
> > > So I have doubts as to whether it is really feasible to provide CS
> > codec information in metadata to the SRS in a meaningful way,
whether
> > this be using approach 1) or approach 2), but I particularly dislike=20
> > approach 1).
> > >
> > > John (as individual)
> > _______________________________________________
> > 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

From rmohanr@cisco.com  Thu Mar 17 00:39:08 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 376B33A680C for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.398
X-Spam-Level: 
X-Spam-Status: No, score=-10.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwu72KAbjaMY for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:39:06 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id C223D3A680B for <siprec@ietf.org>; Thu, 17 Mar 2011 00:39:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=10371; q=dns/txt; s=iport; t=1300347633; x=1301557233; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=P0r8WtCrA3DS4NnKNKq2pQK8aUn2NDlQNl2SZnG+TcU=; b=Gewm/e0GXGXfnzHgcnEjY7uhrP3wx4HWHx0mfa9URwRoz5e/HN819eDJ 1iimhSAqtUCSwCEPxnUMD7xVLQT7fP0ZE3SC0XqSdWa7uvGInFPhDdniD Z0Wyb1yXGhWjTFIivTqMWLdzUaXFLNj0KKEMcRb1kh38MVCGNyNcc2Jn2 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0BAHNXgU2Q/khLgWdsb2JhbACYHI0yFAEBFiYlp0ScKoJ7gmgEhS2LBA
X-IronPort-AV: E=Sophos;i="4.63,198,1299456000"; d="scan'208";a="79570977"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 17 Mar 2011 07:40:32 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2H7eV0U001615; Thu, 17 Mar 2011 07:40:32 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Mar 2011 13:10:31 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Mar 2011 13:10:27 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD05B8B577@XMB-BGL-417.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAAAB/NQA==
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 17 Mar 2011 07:40:31.0382 (UTC) FILETIME=[97C64B60:01CBE476]
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 07:39:08 -0000

Inline

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Thursday, March 17, 2011 1:06 PM
> To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Regarding information, most basic one is when video started and ended.
>=20
> What about the configuration where SRC knows about video (because it
is
> inside CS SIP session) but is not able to fork video. Is it still
> should offer video m-line?

As I mentioned in  point 2 below I think SRC can still offer a
m-line(for video in RS SDP) with m=3D0 and have video information.=20
Do you see any issues with this approach ?

The other option could be to carry in metadata.
Ram

>=20
> Leon
>=20
> -----Original Message-----
> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> Sent: Thursday, March 17, 2011 9:26 AM
> To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Inline
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Thursday, March 17, 2011 12:43 PM
> > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Hi
> >
> > I agree that if SRS need something from SDP it will be better to
pass
> > it via metadata extensions. I did some additional checks and
> currently
> > there is no such requirement from SRS point of view.
> > Regarding video, there was requirement to report video session even
> if
> > it is not recorded.  And if it is recorded then all relevant
> > information will be reported via RS SDP such as positions, sizes
etc.
>=20
> For cases where Video is not recorded, there are two possibilities:
> 1) Video is offered by SRC in RS SDP to SRS but SRS choose to reject
> video. In this case SRC can still continue to send updates via RS SDP
> to SRS.
>=20
> 2) SRC may not have capability to record video and may not offer video
> to SRS in RS SDP.  In this case also we can send a offer (m=3D0) from
SRC
> to SRS having video information.
>=20
>  My question here is - what information do we see a need to report ?
Is
> it just the information that video is part of CS or more than that ?
>=20
> Ram
>=20
> >
> > Leon
> >
> > -----Original Message-----
> > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > Sent: Thursday, March 17, 2011 9:06 AM
> > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Hi Leon / All,
> >
> > See inline for my comments
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Leon Portman
> > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] CS Codec Parameter in stream XML element
[was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > I agree with points below that passing actual CS SDP to SRS is a
> not
> > > good idea from security and layers separation point of view.
> > > Today's SRS implementations(at least that I know about) do not
keep
> > > original codec information in the database for later retrieval. I
> am
> > > trying to think about use cases why SRS can be interested in one,
> and
> > > except troubleshooting it is not very relevant.
> > >
> > > The main assumption is that SRC inspected CS SDP and extracted all
> > > relevant information like ip addresses, media line labels and
infos
> > and
> > > reported it to SRS via metadata.
> >
> > Are you still suggesting here that we pass across some of the
> > parameters of CS SDP that you mentioned above to SRS via metadata ?
> Are
> > there any applications at SRS which may require this information ?
> >
> > I vaguely remember during IETF 79 presentation that some folks
> (mainly
> > from video perspective) were asking for part of information related
> to
> > CS SDP to be passed in metadata. But not too sure about the use
cases
> > for the same.
> > I would request people on the mailer list to speak up if there are
> any
> > use cases.
> >
> >
> > IMO if there is only some specific SRS applications that need this,
> > it's better to pass it as extension data rather than having it as
> > attribute of MS block in the metadata.
> >
> >
> > Regards,
> > Ram
> >
> > >
> > > The main reason as I see if we want to be able to report CS SDP
via
> > > metadata is for the case where SRS wants to sniff RS RTP packets
> > > directly and not by forking from SRC but it is out of scope.
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Paul Kyzivat
> > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > To: Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] CS Codec Parameter in stream XML element
[was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > I believe the codec parameters on the MS have been there since my
> > first
> > > cut at the metadata model. Putting them there was just speculation
> on
> > > my part, and doesn't imply any actual need known to me.
> > >
> > > If nobody feels they are necessary, then by all means remove them.
> > >
> > > 	Thanks,
> > > 	Paul
> > >
> > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > >> Sent: 16 March 2011 01:25
> > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > >> Cc: siprec@ietf.org
> > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > >> [siprec] Review Request for
draft-ram-siprec-metadata-format-01]
> > > >>
> > > > <snip/>
> > > >> <Partha>  It is the assumption done during metadata format that
> RS
> > > >> SDP may be used as Codec params for stream. Please note that
> > format
> > > >> draft does not have codec param in stream metadata element. But
> > the
> > > >> assumption does not seems to be working for all scenarios. So
we
> > > need
> > > >> to find the way to represent CS Media stream in metadata
format.
> > > >>
> > > >> Even before going into approach, I'm interested in knowing
> whether
> > > it
> > > >> is required for SRS to understand the exact codec or SDP
> parameter
> > > >> used in CS? RS may be transcoded/transrated and lost the actual
> > > media
> > > >> information when it reaches SRS but the question is whether it
> is
> > > >> required to maintain the metadata in SRS even though media
(RTP)
> > is
> > > >> changed to new format ?
> > > >>
> > > >> In case we decide to pass CS codec parameter to SRS. Two
> > approaches
> > > >> exist to solve this issue:
> > > >>
> > > >> 1) Tunnel complete each participant SDP inside stream element
> > using
> > > >> some new optional XML element. This approach is straightforward
> > and
> > > >> scale for any CS as we are sending the complete set. The
> overhead
> > > >> will be increased in SRS to parse and store appropriately.
> > > >>
> > > >> 2) Identify the list of codec parameters *MUST*  be passed from
> > SRC
> > > >> to SRS and create the new XML element for them. This is simple
> to
> > > >> implement as only portion of the SDP is passed across but *may*
> > have
> > > >> scalability issue.
> > > >>
> > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > interested
> > > >> in hearing from you which way to go.
> > > >>
> > > >> </partha>
> > > > [JRE] I was basing my earlier comment on the fact that the
> metadata
> > > model seems to indicate that the Media Stream object has CS codec
> > > parameters as an attribute. This is indeed questionable. I seem to
> > > remember somebody wanting this at some stage in the past. From my
> > point
> > > of view, I don't think this information is needed by the SRS - it
> is
> > > historic information, nothing to do with the media actually sent
to
> > the
> > > SRS, and of no use to the SRS, in my opinion.
> > > >
> > > > If people do think there is a reason for providing this
> information
> > > to the SRS, I don't think I would favour approach 1) above. The
SDP
> > > could potentially contain all sorts of information other than
> codecs
> > > (codecs are only a small part, and the SDP will contain
information
> > > like IP addresses, ports, security keys!!!, transport,
non-recorded
> > > media descriptions (e.g., MSRP channel, BFCP channel), format
> > > parameters, SDP capability negotiation attributes, etc..
> > > >
> > > > Moreover, the offerer and answerer might have agreed several
> codecs
> > > in the SDP, so you need to look at RTP to see which codec is
> actually
> > > used. This can change on the fly.
> > > >
> > > > Finally, although the SRS's SIP/SDP stack will surely have and
> SDP
> > > parser, the XML metadata is intended for passing to an
application.
> > > Requiring that application to contain an SDP parser is, I think,
> > > unreasonable.
> > > >
> > > > So I have doubts as to whether it is really feasible to provide
> CS
> > > codec information in metadata to the SRS in a meaningful way,
> whether
> > > this be using approach 1) or approach 2), but I particularly
> dislike
> > > approach 1).
> > > >
> > > > John (as individual)
> > > _______________________________________________
> > > 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

From Leon.Portman@nice.com  Thu Mar 17 00:43:45 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C515D3A680B for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.376
X-Spam-Level: 
X-Spam-Status: No, score=-2.376 tagged_above=-999 required=5 tests=[AWL=0.223,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T3JOGymD1ogN for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 00:43:44 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id C1F633A6407 for <siprec@ietf.org>; Thu, 17 Mar 2011 00:43:43 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Thu, 17 Mar 2011 09:45:10 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>,  "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 17 Mar 2011 09:45:09 +0200
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAAAB/NQAAAHNeQ
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A9491741@TLVMBX01.nice.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B577@XMB-BGL-417.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD05B8B577@XMB-BGL-417.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 07:43:45 -0000

Sorry, I missed the m=3D0 part.

The question is then what if as in mixed voice session, where SRC need to d=
escribe in metadata what is actually mixed in RS voice media line, we will =
have something similar for video, where multiple video streams are mixed to=
gether (like grid for example)?
So we still will have metadata describing these sessions, correct?


Leon

-----Original Message-----
From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]=20
Sent: Thursday, March 17, 2011 9:40 AM
To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John; siprec@ietf.org
Subject: RE: [siprec] CS Codec Parameter in stream XML element [was RE: Rev=
iew Request for draft-ram-siprec-metadata-format-01]

Inline

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Thursday, March 17, 2011 1:06 PM
> To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Regarding information, most basic one is when video started and ended.
>=20
> What about the configuration where SRC knows about video (because it
is
> inside CS SIP session) but is not able to fork video. Is it still=20
> should offer video m-line?

As I mentioned in  point 2 below I think SRC can still offer a m-line(for v=
ideo in RS SDP) with m=3D0 and have video information.=20
Do you see any issues with this approach ?

The other option could be to carry in metadata.
Ram

>=20
> Leon
>=20
> -----Original Message-----
> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> Sent: Thursday, March 17, 2011 9:26 AM
> To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Inline
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Thursday, March 17, 2011 12:43 PM
> > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Hi
> >
> > I agree that if SRS need something from SDP it will be better to
pass
> > it via metadata extensions. I did some additional checks and
> currently
> > there is no such requirement from SRS point of view.
> > Regarding video, there was requirement to report video session even
> if
> > it is not recorded.  And if it is recorded then all relevant=20
> > information will be reported via RS SDP such as positions, sizes
etc.
>=20
> For cases where Video is not recorded, there are two possibilities:
> 1) Video is offered by SRC in RS SDP to SRS but SRS choose to reject=20
> video. In this case SRC can still continue to send updates via RS SDP=20
> to SRS.
>=20
> 2) SRC may not have capability to record video and may not offer video=20
> to SRS in RS SDP.  In this case also we can send a offer (m=3D0) from
SRC
> to SRS having video information.
>=20
>  My question here is - what information do we see a need to report ?
Is
> it just the information that video is part of CS or more than that ?
>=20
> Ram
>=20
> >
> > Leon
> >
> > -----Original Message-----
> > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > Sent: Thursday, March 17, 2011 9:06 AM
> > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Hi Leon / All,
> >
> > See inline for my comments
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > > Behalf Of Leon Portman
> > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] CS Codec Parameter in stream XML element
[was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > I agree with points below that passing actual CS SDP to SRS is a
> not
> > > good idea from security and layers separation point of view.
> > > Today's SRS implementations(at least that I know about) do not
keep
> > > original codec information in the database for later retrieval. I
> am
> > > trying to think about use cases why SRS can be interested in one,
> and
> > > except troubleshooting it is not very relevant.
> > >
> > > The main assumption is that SRC inspected CS SDP and extracted all=20
> > > relevant information like ip addresses, media line labels and
infos
> > and
> > > reported it to SRS via metadata.
> >
> > Are you still suggesting here that we pass across some of the=20
> > parameters of CS SDP that you mentioned above to SRS via metadata ?
> Are
> > there any applications at SRS which may require this information ?
> >
> > I vaguely remember during IETF 79 presentation that some folks
> (mainly
> > from video perspective) were asking for part of information related
> to
> > CS SDP to be passed in metadata. But not too sure about the use
cases
> > for the same.
> > I would request people on the mailer list to speak up if there are
> any
> > use cases.
> >
> >
> > IMO if there is only some specific SRS applications that need this,=20
> > it's better to pass it as extension data rather than having it as=20
> > attribute of MS block in the metadata.
> >
> >
> > Regards,
> > Ram
> >
> > >
> > > The main reason as I see if we want to be able to report CS SDP
via
> > > metadata is for the case where SRS wants to sniff RS RTP packets=20
> > > directly and not by forking from SRC but it is out of scope.
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > > Behalf Of Paul Kyzivat
> > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > To: Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] CS Codec Parameter in stream XML element
[was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > I believe the codec parameters on the MS have been there since my
> > first
> > > cut at the metadata model. Putting them there was just speculation
> on
> > > my part, and doesn't imply any actual need known to me.
> > >
> > > If nobody feels they are necessary, then by all means remove them.
> > >
> > > 	Thanks,
> > > 	Paul
> > >
> > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > >> Sent: 16 March 2011 01:25
> > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > >> Cc: siprec@ietf.org
> > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > >> [siprec] Review Request for
draft-ram-siprec-metadata-format-01]
> > > >>
> > > > <snip/>
> > > >> <Partha>  It is the assumption done during metadata format that
> RS
> > > >> SDP may be used as Codec params for stream. Please note that
> > format
> > > >> draft does not have codec param in stream metadata element. But
> > the
> > > >> assumption does not seems to be working for all scenarios. So
we
> > > need
> > > >> to find the way to represent CS Media stream in metadata
format.
> > > >>
> > > >> Even before going into approach, I'm interested in knowing
> whether
> > > it
> > > >> is required for SRS to understand the exact codec or SDP
> parameter
> > > >> used in CS? RS may be transcoded/transrated and lost the actual
> > > media
> > > >> information when it reaches SRS but the question is whether it
> is
> > > >> required to maintain the metadata in SRS even though media
(RTP)
> > is
> > > >> changed to new format ?
> > > >>
> > > >> In case we decide to pass CS codec parameter to SRS. Two
> > approaches
> > > >> exist to solve this issue:
> > > >>
> > > >> 1) Tunnel complete each participant SDP inside stream element
> > using
> > > >> some new optional XML element. This approach is straightforward
> > and
> > > >> scale for any CS as we are sending the complete set. The
> overhead
> > > >> will be increased in SRS to parse and store appropriately.
> > > >>
> > > >> 2) Identify the list of codec parameters *MUST*  be passed from
> > SRC
> > > >> to SRS and create the new XML element for them. This is simple
> to
> > > >> implement as only portion of the SDP is passed across but *may*
> > have
> > > >> scalability issue.
> > > >>
> > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > interested
> > > >> in hearing from you which way to go.
> > > >>
> > > >> </partha>
> > > > [JRE] I was basing my earlier comment on the fact that the
> metadata
> > > model seems to indicate that the Media Stream object has CS codec=20
> > > parameters as an attribute. This is indeed questionable. I seem to=20
> > > remember somebody wanting this at some stage in the past. From my
> > point
> > > of view, I don't think this information is needed by the SRS - it
> is
> > > historic information, nothing to do with the media actually sent
to
> > the
> > > SRS, and of no use to the SRS, in my opinion.
> > > >
> > > > If people do think there is a reason for providing this
> information
> > > to the SRS, I don't think I would favour approach 1) above. The
SDP
> > > could potentially contain all sorts of information other than
> codecs
> > > (codecs are only a small part, and the SDP will contain
information
> > > like IP addresses, ports, security keys!!!, transport,
non-recorded
> > > media descriptions (e.g., MSRP channel, BFCP channel), format=20
> > > parameters, SDP capability negotiation attributes, etc..
> > > >
> > > > Moreover, the offerer and answerer might have agreed several
> codecs
> > > in the SDP, so you need to look at RTP to see which codec is
> actually
> > > used. This can change on the fly.
> > > >
> > > > Finally, although the SRS's SIP/SDP stack will surely have and
> SDP
> > > parser, the XML metadata is intended for passing to an
application.
> > > Requiring that application to contain an SDP parser is, I think,=20
> > > unreasonable.
> > > >
> > > > So I have doubts as to whether it is really feasible to provide
> CS
> > > codec information in metadata to the SRS in a meaningful way,
> whether
> > > this be using approach 1) or approach 2), but I particularly
> dislike
> > > approach 1).
> > > >
> > > > John (as individual)
> > > _______________________________________________
> > > 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

From rmohanr@cisco.com  Thu Mar 17 01:37:20 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8BA23A6806 for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 01:37:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.116
X-Spam-Level: 
X-Spam-Status: No, score=-10.116 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9g2WJPRKvXYy for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 01:37:19 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 684BA3A67F4 for <siprec@ietf.org>; Thu, 17 Mar 2011 01:37:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=12389; q=dns/txt; s=iport; t=1300351126; x=1301560726; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=gAjB2MP/xrkCxv/pn8Qj3noqpB5ACEdI4BRnZdf54mw=; b=mDOtGnNc9WGgsaMlRFoI6stXZIo0iQxdrXdN/5qViTdK9PJExKzeuUAx L217WKtDh4qiK5Uw81d9ksg/fjMLzhX0/7+50f0UHLPOYQepqXYG05xJ7 zA9OUncyD2flZ42m2vpbc/99Cf0uqJmNlFTjCh9q3WzD0W+O6FfCuLTnq Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0BAIJlgU2Q/khMgWdsb2JhbACYHI0wFAEBFiYlp32cIoJ7gmgEhS2LBA
X-IronPort-AV: E=Sophos;i="4.63,198,1299456000"; d="scan'208";a="79580391"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 17 Mar 2011 08:38:45 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2H8ciYI023921; Thu, 17 Mar 2011 08:38:44 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Mar 2011 14:08:43 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Mar 2011 14:08:40 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD05B8B5B0@XMB-BGL-417.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A9491741@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAAAB/NQAAAHNeQAAHzvOA=
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B577@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491741@TLVMBX01.nice.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 17 Mar 2011 08:38:43.0936 (UTC) FILETIME=[B97FBE00:01CBE47E]
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 08:37:20 -0000

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Thursday, March 17, 2011 1:15 PM
> To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John;
> siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Sorry, I missed the m=3D0 part.
>=20
> The question is then what if as in mixed voice session, where SRC need
> to describe in metadata what is actually mixed in RS voice media line,
> we will have something similar for video, where multiple video streams
> are mixed together (like grid for example)?
> So we still will have metadata describing these sessions, correct?

Yes Leon. The metadata will have information about participants and will
also point to the video m-line of RS SDP (through label attribute). We
will add use cases for this (audio+video in CS and only audio recorded
in RS) in the next revision of the format document.

Ram

>=20
>=20
> Leon
>=20
> -----Original Message-----
> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> Sent: Thursday, March 17, 2011 9:40 AM
> To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John;
> siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Inline
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Thursday, March 17, 2011 1:06 PM
> > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Regarding information, most basic one is when video started and
> ended.
> >
> > What about the configuration where SRC knows about video (because it
> is
> > inside CS SIP session) but is not able to fork video. Is it still
> > should offer video m-line?
>=20
> As I mentioned in  point 2 below I think SRC can still offer a m-
> line(for video in RS SDP) with m=3D0 and have video information.
> Do you see any issues with this approach ?
>=20
> The other option could be to carry in metadata.
> Ram
>=20
> >
> > Leon
> >
> > -----Original Message-----
> > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > Sent: Thursday, March 17, 2011 9:26 AM
> > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Inline
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: Thursday, March 17, 2011 12:43 PM
> > > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML element
[was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Hi
> > >
> > > I agree that if SRS need something from SDP it will be better to
> pass
> > > it via metadata extensions. I did some additional checks and
> > currently
> > > there is no such requirement from SRS point of view.
> > > Regarding video, there was requirement to report video session
even
> > if
> > > it is not recorded.  And if it is recorded then all relevant
> > > information will be reported via RS SDP such as positions, sizes
> etc.
> >
> > For cases where Video is not recorded, there are two possibilities:
> > 1) Video is offered by SRC in RS SDP to SRS but SRS choose to reject
> > video. In this case SRC can still continue to send updates via RS
SDP
> > to SRS.
> >
> > 2) SRC may not have capability to record video and may not offer
> video
> > to SRS in RS SDP.  In this case also we can send a offer (m=3D0) =
from
> SRC
> > to SRS having video information.
> >
> >  My question here is - what information do we see a need to report ?
> Is
> > it just the information that video is part of CS or more than that ?
> >
> > Ram
> >
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > > Sent: Thursday, March 17, 2011 9:06 AM
> > > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML element
[was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Hi Leon / All,
> > >
> > > See inline for my comments
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
On
> > > > Behalf Of Leon Portman
> > > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] CS Codec Parameter in stream XML element
> [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > I agree with points below that passing actual CS SDP to SRS is a
> > not
> > > > good idea from security and layers separation point of view.
> > > > Today's SRS implementations(at least that I know about) do not
> keep
> > > > original codec information in the database for later retrieval.
I
> > am
> > > > trying to think about use cases why SRS can be interested in
one,
> > and
> > > > except troubleshooting it is not very relevant.
> > > >
> > > > The main assumption is that SRC inspected CS SDP and extracted
> all
> > > > relevant information like ip addresses, media line labels and
> infos
> > > and
> > > > reported it to SRS via metadata.
> > >
> > > Are you still suggesting here that we pass across some of the
> > > parameters of CS SDP that you mentioned above to SRS via metadata
?
> > Are
> > > there any applications at SRS which may require this information ?
> > >
> > > I vaguely remember during IETF 79 presentation that some folks
> > (mainly
> > > from video perspective) were asking for part of information
related
> > to
> > > CS SDP to be passed in metadata. But not too sure about the use
> cases
> > > for the same.
> > > I would request people on the mailer list to speak up if there are
> > any
> > > use cases.
> > >
> > >
> > > IMO if there is only some specific SRS applications that need
this,
> > > it's better to pass it as extension data rather than having it as
> > > attribute of MS block in the metadata.
> > >
> > >
> > > Regards,
> > > Ram
> > >
> > > >
> > > > The main reason as I see if we want to be able to report CS SDP
> via
> > > > metadata is for the case where SRS wants to sniff RS RTP packets
> > > > directly and not by forking from SRC but it is out of scope.
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
On
> > > > Behalf Of Paul Kyzivat
> > > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > > To: Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] CS Codec Parameter in stream XML element
> [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > I believe the codec parameters on the MS have been there since
my
> > > first
> > > > cut at the metadata model. Putting them there was just
> speculation
> > on
> > > > my part, and doesn't imply any actual need known to me.
> > > >
> > > > If nobody feels they are necessary, then by all means remove
> them.
> > > >
> > > > 	Thanks,
> > > > 	Paul
> > > >
> > > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > > >> Sent: 16 March 2011 01:25
> > > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > > >> Cc: siprec@ietf.org
> > > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > > >> [siprec] Review Request for
> draft-ram-siprec-metadata-format-01]
> > > > >>
> > > > > <snip/>
> > > > >> <Partha>  It is the assumption done during metadata format
> that
> > RS
> > > > >> SDP may be used as Codec params for stream. Please note that
> > > format
> > > > >> draft does not have codec param in stream metadata element.
> But
> > > the
> > > > >> assumption does not seems to be working for all scenarios. So
> we
> > > > need
> > > > >> to find the way to represent CS Media stream in metadata
> format.
> > > > >>
> > > > >> Even before going into approach, I'm interested in knowing
> > whether
> > > > it
> > > > >> is required for SRS to understand the exact codec or SDP
> > parameter
> > > > >> used in CS? RS may be transcoded/transrated and lost the
> actual
> > > > media
> > > > >> information when it reaches SRS but the question is whether
it
> > is
> > > > >> required to maintain the metadata in SRS even though media
> (RTP)
> > > is
> > > > >> changed to new format ?
> > > > >>
> > > > >> In case we decide to pass CS codec parameter to SRS. Two
> > > approaches
> > > > >> exist to solve this issue:
> > > > >>
> > > > >> 1) Tunnel complete each participant SDP inside stream element
> > > using
> > > > >> some new optional XML element. This approach is
> straightforward
> > > and
> > > > >> scale for any CS as we are sending the complete set. The
> > overhead
> > > > >> will be increased in SRS to parse and store appropriately.
> > > > >>
> > > > >> 2) Identify the list of codec parameters *MUST*  be passed
> from
> > > SRC
> > > > >> to SRS and create the new XML element for them. This is
simple
> > to
> > > > >> implement as only portion of the SDP is passed across but
> *may*
> > > have
> > > > >> scalability issue.
> > > > >>
> > > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > > interested
> > > > >> in hearing from you which way to go.
> > > > >>
> > > > >> </partha>
> > > > > [JRE] I was basing my earlier comment on the fact that the
> > metadata
> > > > model seems to indicate that the Media Stream object has CS
codec
> > > > parameters as an attribute. This is indeed questionable. I seem
> to
> > > > remember somebody wanting this at some stage in the past. From
my
> > > point
> > > > of view, I don't think this information is needed by the SRS -
it
> > is
> > > > historic information, nothing to do with the media actually sent
> to
> > > the
> > > > SRS, and of no use to the SRS, in my opinion.
> > > > >
> > > > > If people do think there is a reason for providing this
> > information
> > > > to the SRS, I don't think I would favour approach 1) above. The
> SDP
> > > > could potentially contain all sorts of information other than
> > codecs
> > > > (codecs are only a small part, and the SDP will contain
> information
> > > > like IP addresses, ports, security keys!!!, transport,
> non-recorded
> > > > media descriptions (e.g., MSRP channel, BFCP channel), format
> > > > parameters, SDP capability negotiation attributes, etc..
> > > > >
> > > > > Moreover, the offerer and answerer might have agreed several
> > codecs
> > > > in the SDP, so you need to look at RTP to see which codec is
> > actually
> > > > used. This can change on the fly.
> > > > >
> > > > > Finally, although the SRS's SIP/SDP stack will surely have and
> > SDP
> > > > parser, the XML metadata is intended for passing to an
> application.
> > > > Requiring that application to contain an SDP parser is, I think,
> > > > unreasonable.
> > > > >
> > > > > So I have doubts as to whether it is really feasible to
provide
> > CS
> > > > codec information in metadata to the SRS in a meaningful way,
> > whether
> > > > this be using approach 1) or approach 2), but I particularly
> > dislike
> > > > approach 1).
> > > > >
> > > > > John (as individual)
> > > > _______________________________________________
> > > > 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

From john.elwell@siemens-enterprise.com  Thu Mar 17 03:12:29 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D5BF3A6869 for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 03:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BgZ+uZPlQjYd for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 03:12:27 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 230E43A6839 for <siprec@ietf.org>; Thu, 17 Mar 2011 03:12:26 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3777709; Thu, 17 Mar 2011 11:13:41 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id D181523F0290; Thu, 17 Mar 2011 11:13:41 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 17 Mar 2011 11:13:41 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
Date: Thu, 17 Mar 2011 11:13:40 +0100
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAABTHCIA==
Message-ID: <A444A0F8084434499206E78C106220CA086A9649F5@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 10:12:29 -0000

I think in these sort of situations it would be better to report the non-re=
corded video stream in XML metadata. If the SRC uses an m-line with port=3D=
0 to indicate start of an unrecordable video stream, I don't see how the SR=
C can report the end of that unrecordable video stream in SDP. XML seems a =
better option.

Let me make a proposal. For each Media Stream in XML, attributes should ind=
icate:
- The type of medium (audio, video,...).
- The content type of the medium (c.f., RFC 4796) if applicable, e.g., slid=
es, speaker...
- The SDP label for that medium (absent if the SRC does not offer it for re=
cording).

Yes, I know the first two items would be duplication of SDP (in cases where=
 the medium is offered for recording), but these two items would be particu=
larly useful in cases where the medium is not offered for recording and the=
refore not in the SDP.

John (as individual)

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 17 March 2011 07:36
> To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML=20
> element [was RE: Review Request for=20
> draft-ram-siprec-metadata-format-01]
>=20
> Regarding information, most basic one is when video started and ended.
>=20
> What about the configuration where SRC knows about video=20
> (because it is inside CS SIP session) but is not able to fork=20
> video. Is it still should offer video m-line?
>=20
> Leon
>=20
> -----Original Message-----
> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]=20
> Sent: Thursday, March 17, 2011 9:26 AM
> To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML=20
> element [was RE: Review Request for=20
> draft-ram-siprec-metadata-format-01]
>=20
> Inline=20
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Thursday, March 17, 2011 12:43 PM
> > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >=20
> > Hi
> >=20
> > I agree that if SRS need something from SDP it will be=20
> better to pass=20
> > it via metadata extensions. I did some additional checks=20
> and currently=20
> > there is no such requirement from SRS point of view.
> > Regarding video, there was requirement to report video=20
> session even if=20
> > it is not recorded.  And if it is recorded then all relevant=20
> > information will be reported via RS SDP such as positions,=20
> sizes etc.
>=20
> For cases where Video is not recorded, there are two possibilities:
> 1) Video is offered by SRC in RS SDP to SRS but SRS choose to=20
> reject video. In this case SRC can still continue to send=20
> updates via RS SDP to SRS.=20
>=20
> 2) SRC may not have capability to record video and may not=20
> offer video to SRS in RS SDP.  In this case also we can send=20
> a offer (m=3D0) from SRC to SRS having video information.
>=20
>  My question here is - what information do we see a need to=20
> report ? Is it just the information that video is part of CS=20
> or more than that ?
>=20
> Ram
>=20
> >=20
> > Leon
> >=20
> > -----Original Message-----
> > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > Sent: Thursday, March 17, 2011 9:06 AM
> > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >=20
> > Hi Leon / All,
> >=20
> > See inline for my comments
> >=20
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > > Behalf Of Leon Portman
> > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] CS Codec Parameter in stream XML=20
> element [was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > I agree with points below that passing actual CS SDP to=20
> SRS is a not=20
> > > good idea from security and layers separation point of view.
> > > Today's SRS implementations(at least that I know about)=20
> do not keep=20
> > > original codec information in the database for later=20
> retrieval. I am=20
> > > trying to think about use cases why SRS can be interested in one,
> and
> > > except troubleshooting it is not very relevant.
> > >
> > > The main assumption is that SRC inspected CS SDP and=20
> extracted all=20
> > > relevant information like ip addresses, media line labels=20
> and infos
> > and
> > > reported it to SRS via metadata.
> >=20
> > Are you still suggesting here that we pass across some of the=20
> > parameters of CS SDP that you mentioned above to SRS via metadata ?
> Are
> > there any applications at SRS which may require this information ?
> >=20
> > I vaguely remember during IETF 79 presentation that some=20
> folks (mainly=20
> > from video perspective) were asking for part of information=20
> related to=20
> > CS SDP to be passed in metadata. But not too sure about the=20
> use cases=20
> > for the same.
> > I would request people on the mailer list to speak up if=20
> there are any=20
> > use cases.
> >=20
> >=20
> > IMO if there is only some specific SRS applications that need this,=20
> > it's better to pass it as extension data rather than having it as=20
> > attribute of MS block in the metadata.
> >=20
> >=20
> > Regards,
> > Ram
> >=20
> > >
> > > The main reason as I see if we want to be able to report=20
> CS SDP via=20
> > > metadata is for the case where SRS wants to sniff RS RTP packets=20
> > > directly and not by forking from SRC but it is out of scope.
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > > Behalf Of Paul Kyzivat
> > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > To: Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] CS Codec Parameter in stream XML=20
> element [was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > I believe the codec parameters on the MS have been there since my
> > first
> > > cut at the metadata model. Putting them there was just speculation
> on
> > > my part, and doesn't imply any actual need known to me.
> > >
> > > If nobody feels they are necessary, then by all means remove them.
> > >
> > > 	Thanks,
> > > 	Paul
> > >
> > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > >> Sent: 16 March 2011 01:25
> > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > >> Cc: siprec@ietf.org
> > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > >> [siprec] Review Request for=20
> draft-ram-siprec-metadata-format-01]
> > > >>
> > > > <snip/>
> > > >> <Partha>  It is the assumption done during metadata format that
> RS
> > > >> SDP may be used as Codec params for stream. Please note that
> > format
> > > >> draft does not have codec param in stream metadata element. But
> > the
> > > >> assumption does not seems to be working for all=20
> scenarios. So we
> > > need
> > > >> to find the way to represent CS Media stream in=20
> metadata format.
> > > >>
> > > >> Even before going into approach, I'm interested in knowing
> whether
> > > it
> > > >> is required for SRS to understand the exact codec or SDP
> parameter
> > > >> used in CS? RS may be transcoded/transrated and lost the actual
> > > media
> > > >> information when it reaches SRS but the question is=20
> whether it is=20
> > > >> required to maintain the metadata in SRS even though=20
> media (RTP)
> > is
> > > >> changed to new format ?
> > > >>
> > > >> In case we decide to pass CS codec parameter to SRS. Two
> > approaches
> > > >> exist to solve this issue:
> > > >>
> > > >> 1) Tunnel complete each participant SDP inside stream element
> > using
> > > >> some new optional XML element. This approach is straightforward
> > and
> > > >> scale for any CS as we are sending the complete set.=20
> The overhead=20
> > > >> will be increased in SRS to parse and store appropriately.
> > > >>
> > > >> 2) Identify the list of codec parameters *MUST*  be passed from
> > SRC
> > > >> to SRS and create the new XML element for them. This=20
> is simple to=20
> > > >> implement as only portion of the SDP is passed across but *may*
> > have
> > > >> scalability issue.
> > > >>
> > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > interested
> > > >> in hearing from you which way to go.
> > > >>
> > > >> </partha>
> > > > [JRE] I was basing my earlier comment on the fact that the
> metadata
> > > model seems to indicate that the Media Stream object has CS codec=20
> > > parameters as an attribute. This is indeed questionable.=20
> I seem to=20
> > > remember somebody wanting this at some stage in the past. From my
> > point
> > > of view, I don't think this information is needed by the=20
> SRS - it is=20
> > > historic information, nothing to do with the media=20
> actually sent to
> > the
> > > SRS, and of no use to the SRS, in my opinion.
> > > >
> > > > If people do think there is a reason for providing this
> information
> > > to the SRS, I don't think I would favour approach 1)=20
> above. The SDP=20
> > > could potentially contain all sorts of information other=20
> than codecs=20
> > > (codecs are only a small part, and the SDP will contain=20
> information=20
> > > like IP addresses, ports, security keys!!!, transport,=20
> non-recorded=20
> > > media descriptions (e.g., MSRP channel, BFCP channel), format=20
> > > parameters, SDP capability negotiation attributes, etc..
> > > >
> > > > Moreover, the offerer and answerer might have agreed several
> codecs
> > > in the SDP, so you need to look at RTP to see which codec is
> actually
> > > used. This can change on the fly.
> > > >
> > > > Finally, although the SRS's SIP/SDP stack will surely=20
> have and SDP
> > > parser, the XML metadata is intended for passing to an=20
> application.
> > > Requiring that application to contain an SDP parser is, I think,=20
> > > unreasonable.
> > > >
> > > > So I have doubts as to whether it is really feasible to=20
> provide CS
> > > codec information in metadata to the SRS in a meaningful way,
> whether
> > > this be using approach 1) or approach 2), but I=20
> particularly dislike=20
> > > approach 1).
> > > >
> > > > John (as individual)
> > > _______________________________________________
> > > 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
> =

From partr@cisco.com  Thu Mar 17 04:11:28 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 906343A68ED for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 04:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.004
X-Spam-Level: 
X-Spam-Status: No, score=-10.004 tagged_above=-999 required=5 tests=[AWL=0.595, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rSGODd8aZWMm for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 04:11:26 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id CD1703A6914 for <siprec@ietf.org>; Thu, 17 Mar 2011 04:11:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=13026; q=dns/txt; s=iport; t=1300360374; x=1301569974; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=8dEUud1eJjelo8dA6K1hde2ph3XPOPDuU/FOTLLDgaM=; b=HeCKK3zTkM2sR3VJ75SAVDkj1THr4Q/mLaAA8Ncq/Teugw6OoXcze21b DAOvekZQATLK5OvBcOxgHHL/2uadKqHgsHWZ0w/j2JiruurQaqRhrFjhe Cr6AhmPKxzjSOTeMBLTziweEURns3fy53Nihe/I9Ly3eD+8kzB+BGM0CQ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0BANeJgU2Q/khMgWdsb2JhbACYHY0wFAEBFiYlp3+cKYJ7gmgEhS2LBA
X-IronPort-AV: E=Sophos;i="4.63,198,1299456000"; d="scan'208";a="79609370"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 17 Mar 2011 11:12:52 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2HBCp4L016021; Thu, 17 Mar 2011 11:12:52 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Mar 2011 16:42:51 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Mar 2011 16:42:50 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904CAEFE1@XMB-BGL-411.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A9649F5@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAABTHCIAAA3ufg
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com><07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA086A9649F5@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Leon Portman" <Leon.Portman@nice.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 17 Mar 2011 11:12:51.0744 (UTC) FILETIME=[419F4200:01CBE494]
Cc: siprec@ietf.org
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 11:11:28 -0000

John,

I agree that your proposal will work. I'm trying to find few other
alternatives without duplication of data between SDP and XML.

Approach 1: start-time and stop-time are optional XML element in stream.
In the mentioned scenario, let stream element contains only label
element and no start & stop time elements which indicates that stream is
never activated within the given session.=20

XML format for start-time & stop-time:
         <xs:element name=3D"start-time" type=3D"xs:dateTime"
                minOccurs=3D"0"/>
         <xs:element name=3D"stop-time" type=3D"xs:dateTime"
                minOccurs=3D"0"/>=20

Approach 2: Add both start-time and stop-time in the same stream which
indicates that stream is not started.

I prefer approach 1 which will solve the issue without duplication of
metadata in XML. Please let me know your opinion here.

Leon,

Please read inline.

Thanks
Partha

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Elwell, John
Sent: Thursday, March 17, 2011 3:44 PM
To: Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
Cc: siprec@ietf.org
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE:
Review Request for draft-ram-siprec-metadata-format-01]

I think in these sort of situations it would be better to report the
non-recorded video stream in XML metadata. If the SRC uses an m-line
with port=3D0 to indicate start of an unrecordable video stream, I don't
see how the SRC can report the end of that unrecordable video stream in
SDP. XML seems a better option.

Let me make a proposal. For each Media Stream in XML, attributes should
indicate:
- The type of medium (audio, video,...).
- The content type of the medium (c.f., RFC 4796) if applicable, e.g.,
slides, speaker...
- The SDP label for that medium (absent if the SRC does not offer it for
recording).

Yes, I know the first two items would be duplication of SDP (in cases
where the medium is offered for recording), but these two items would be
particularly useful in cases where the medium is not offered for
recording and therefore not in the SDP.

John (as individual)

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 17 March 2011 07:36
> To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was=20
> RE: Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Regarding information, most basic one is when video started and ended.

<Partha> In the mentioned scenario, video is never started. Hope
Approach 1 serve your purpose </Partha>
>=20
> What about the configuration where SRC knows about video (because it=20
> is inside CS SIP session) but is not able to fork video. Is it still=20
> should offer video m-line?
>=20
<Partha> It is upto SRC to decide whether to indicate the m-line in RS
or not. The decision may be based on the SRC level support for video
recording, policy in the SRC to record video or not. IMO, it is
implementation specific and SIPREC solution SHOULD be flexible for all
kinds of SRC </partha>

> Leon
>=20
> -----Original Message-----
> From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> Sent: Thursday, March 17, 2011 9:26 AM
> To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was=20
> RE: Review Request for draft-ram-siprec-metadata-format-01]
>=20
> Inline
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Thursday, March 17, 2011 12:43 PM
> > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >=20
> > Hi
> >=20
> > I agree that if SRS need something from SDP it will be
> better to pass
> > it via metadata extensions. I did some additional checks
> and currently
> > there is no such requirement from SRS point of view.
> > Regarding video, there was requirement to report video
> session even if
> > it is not recorded.  And if it is recorded then all relevant=20
> > information will be reported via RS SDP such as positions,
> sizes etc.
>=20
> For cases where Video is not recorded, there are two possibilities:
> 1) Video is offered by SRC in RS SDP to SRS but SRS choose to reject=20
> video. In this case SRC can still continue to send updates via RS SDP=20
> to SRS.
>=20
> 2) SRC may not have capability to record video and may not offer video

> to SRS in RS SDP.  In this case also we can send a offer (m=3D0) from=20
> SRC to SRS having video information.
>=20
>  My question here is - what information do we see a need to report ?=20
> Is it just the information that video is part of CS or more than that=20
> ?
>=20
> Ram
>=20
> >=20
> > Leon
> >=20
> > -----Original Message-----
> > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > Sent: Thursday, March 17, 2011 9:06 AM
> > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >=20
> > Hi Leon / All,
> >=20
> > See inline for my comments
> >=20
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > > Behalf Of Leon Portman
> > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> element [was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > I agree with points below that passing actual CS SDP to
> SRS is a not
> > > good idea from security and layers separation point of view.
> > > Today's SRS implementations(at least that I know about)
> do not keep
> > > original codec information in the database for later
> retrieval. I am
> > > trying to think about use cases why SRS can be interested in one,
> and
> > > except troubleshooting it is not very relevant.
> > >
> > > The main assumption is that SRC inspected CS SDP and
> extracted all
> > > relevant information like ip addresses, media line labels
> and infos
> > and
> > > reported it to SRS via metadata.
> >=20
> > Are you still suggesting here that we pass across some of the=20
> > parameters of CS SDP that you mentioned above to SRS via metadata ?
> Are
> > there any applications at SRS which may require this information ?
> >=20
> > I vaguely remember during IETF 79 presentation that some
> folks (mainly
> > from video perspective) were asking for part of information
> related to
> > CS SDP to be passed in metadata. But not too sure about the
> use cases
> > for the same.
> > I would request people on the mailer list to speak up if
> there are any
> > use cases.
> >=20
> >=20
> > IMO if there is only some specific SRS applications that need this,=20
> > it's better to pass it as extension data rather than having it as=20
> > attribute of MS block in the metadata.
> >=20
> >=20
> > Regards,
> > Ram
> >=20
> > >
> > > The main reason as I see if we want to be able to report
> CS SDP via
> > > metadata is for the case where SRS wants to sniff RS RTP packets=20
> > > directly and not by forking from SRC but it is out of scope.
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> > > Behalf Of Paul Kyzivat
> > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > To: Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> element [was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > I believe the codec parameters on the MS have been there since my
> > first
> > > cut at the metadata model. Putting them there was just speculation
> on
> > > my part, and doesn't imply any actual need known to me.
> > >
> > > If nobody feels they are necessary, then by all means remove them.
> > >
> > > 	Thanks,
> > > 	Paul
> > >
> > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > >> Sent: 16 March 2011 01:25
> > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > >> Cc: siprec@ietf.org
> > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > >> [siprec] Review Request for
> draft-ram-siprec-metadata-format-01]
> > > >>
> > > > <snip/>
> > > >> <Partha>  It is the assumption done during metadata format that
> RS
> > > >> SDP may be used as Codec params for stream. Please note that
> > format
> > > >> draft does not have codec param in stream metadata element. But
> > the
> > > >> assumption does not seems to be working for all
> scenarios. So we
> > > need
> > > >> to find the way to represent CS Media stream in
> metadata format.
> > > >>
> > > >> Even before going into approach, I'm interested in knowing
> whether
> > > it
> > > >> is required for SRS to understand the exact codec or SDP
> parameter
> > > >> used in CS? RS may be transcoded/transrated and lost the actual
> > > media
> > > >> information when it reaches SRS but the question is
> whether it is
> > > >> required to maintain the metadata in SRS even though
> media (RTP)
> > is
> > > >> changed to new format ?
> > > >>
> > > >> In case we decide to pass CS codec parameter to SRS. Two
> > approaches
> > > >> exist to solve this issue:
> > > >>
> > > >> 1) Tunnel complete each participant SDP inside stream element
> > using
> > > >> some new optional XML element. This approach is straightforward
> > and
> > > >> scale for any CS as we are sending the complete set.=20
> The overhead
> > > >> will be increased in SRS to parse and store appropriately.
> > > >>
> > > >> 2) Identify the list of codec parameters *MUST*  be passed from
> > SRC
> > > >> to SRS and create the new XML element for them. This
> is simple to
> > > >> implement as only portion of the SDP is passed across but *may*
> > have
> > > >> scalability issue.
> > > >>
> > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > interested
> > > >> in hearing from you which way to go.
> > > >>
> > > >> </partha>
> > > > [JRE] I was basing my earlier comment on the fact that the
> metadata
> > > model seems to indicate that the Media Stream object has CS codec=20
> > > parameters as an attribute. This is indeed questionable.
> I seem to
> > > remember somebody wanting this at some stage in the past. From my
> > point
> > > of view, I don't think this information is needed by the
> SRS - it is
> > > historic information, nothing to do with the media
> actually sent to
> > the
> > > SRS, and of no use to the SRS, in my opinion.
> > > >
> > > > If people do think there is a reason for providing this
> information
> > > to the SRS, I don't think I would favour approach 1)
> above. The SDP
> > > could potentially contain all sorts of information other
> than codecs
> > > (codecs are only a small part, and the SDP will contain
> information
> > > like IP addresses, ports, security keys!!!, transport,
> non-recorded
> > > media descriptions (e.g., MSRP channel, BFCP channel), format=20
> > > parameters, SDP capability negotiation attributes, etc..
> > > >
> > > > Moreover, the offerer and answerer might have agreed several
> codecs
> > > in the SDP, so you need to look at RTP to see which codec is
> actually
> > > used. This can change on the fly.
> > > >
> > > > Finally, although the SRS's SIP/SDP stack will surely
> have and SDP
> > > parser, the XML metadata is intended for passing to an
> application.
> > > Requiring that application to contain an SDP parser is, I think,=20
> > > unreasonable.
> > > >
> > > > So I have doubts as to whether it is really feasible to
> provide CS
> > > codec information in metadata to the SRS in a meaningful way,
> whether
> > > this be using approach 1) or approach 2), but I
> particularly dislike
> > > approach 1).
> > > >
> > > > John (as individual)
> > > _______________________________________________
> > > 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
>=20
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From john.elwell@siemens-enterprise.com  Thu Mar 17 04:36:35 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFBBE3A692F for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 04:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uXNk1RQn0X+x for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 04:36:34 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 718803A6834 for <siprec@ietf.org>; Thu, 17 Mar 2011 04:36:33 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3777538; Thu, 17 Mar 2011 12:37:59 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 6D1481EB82AE; Thu, 17 Mar 2011 12:37:59 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 17 Mar 2011 12:37:59 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, Leon Portman <Leon.Portman@nice.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
Date: Thu, 17 Mar 2011 12:37:58 +0100
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAABTHCIAAA3ufgAAH1vbA=
Message-ID: <A444A0F8084434499206E78C106220CA086A964A62@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com><07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA086A9649F5@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A623904CAEFE1@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904CAEFE1@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 11:36:36 -0000

Partha,

Approach 1 is fine, as far as representation of start/stop times is concern=
ed.

So if I understand correctly the unrecordable / unrecorded stream appears i=
n both XML metadata and SDP, with XML containing the start/stop times and S=
DP containing the media type/content. So an SDP media description would exi=
st for:
- recorded streams;
- streams offered by the SRC for recording but rejected by the SRS;
- streams not offered by the SRC (unrecordable streams).

The first one is fine and the second one we can't really avoid. I am rather=
 uncomfortable about the third one, where there is an SDP media description=
 describing a stream that does not exist in the RS. It clutters the SDP unn=
ecessarily and I feel it is worthwhile having some minimal duplication (in =
XML and SDP) for recorded streams to avoid this addition to SDP for unrecor=
dable streams.

I also feel that media type and content description are logically part of t=
he metadata and should appear in XML, because this is information the appli=
cation needs. SDP, on the other hand, is something the media engine needs i=
n order to receive media correctly and pass the received media in some form=
 up to the application for storage.

John (as individual)

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 17 March 2011 11:13
> To: Elwell, John; Leon Portman; Ram Mohan R (rmohanr); Paul
> Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was RE: Review Request for
> draft-ram-siprec-metadata-format-01]
>
> John,
>
> I agree that your proposal will work. I'm trying to find few other
> alternatives without duplication of data between SDP and XML.
>
> Approach 1: start-time and stop-time are optional XML element
> in stream.
> In the mentioned scenario, let stream element contains only label
> element and no start & stop time elements which indicates
> that stream is
> never activated within the given session.
>
> XML format for start-time & stop-time:
>          <xs:element name=3D"start-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>
> Approach 2: Add both start-time and stop-time in the same stream which
> indicates that stream is not started.
>
> I prefer approach 1 which will solve the issue without duplication of
> metadata in XML. Please let me know your opinion here.
>
> Leon,
>
> Please read inline.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf
> Of Elwell, John
> Sent: Thursday, March 17, 2011 3:44 PM
> To: Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] CS Codec Parameter in stream XML
> element [was RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>
> I think in these sort of situations it would be better to report the
> non-recorded video stream in XML metadata. If the SRC uses an m-line
> with port=3D0 to indicate start of an unrecordable video stream, I don't
> see how the SRC can report the end of that unrecordable video
> stream in
> SDP. XML seems a better option.
>
> Let me make a proposal. For each Media Stream in XML,
> attributes should
> indicate:
> - The type of medium (audio, video,...).
> - The content type of the medium (c.f., RFC 4796) if applicable, e.g.,
> slides, speaker...
> - The SDP label for that medium (absent if the SRC does not
> offer it for
> recording).
>
> Yes, I know the first two items would be duplication of SDP (in cases
> where the medium is offered for recording), but these two
> items would be
> particularly useful in cases where the medium is not offered for
> recording and therefore not in the SDP.
>
> John (as individual)
>
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 17 March 2011 07:36
> > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> > RE: Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Regarding information, most basic one is when video started
> and ended.
>
> <Partha> In the mentioned scenario, video is never started. Hope
> Approach 1 serve your purpose </Partha>
> >
> > What about the configuration where SRC knows about video
> (because it
> > is inside CS SIP session) but is not able to fork video. Is
> it still
> > should offer video m-line?
> >
> <Partha> It is upto SRC to decide whether to indicate the m-line in RS
> or not. The decision may be based on the SRC level support for video
> recording, policy in the SRC to record video or not. IMO, it is
> implementation specific and SIPREC solution SHOULD be flexible for all
> kinds of SRC </partha>
>
> > Leon
> >
> > -----Original Message-----
> > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > Sent: Thursday, March 17, 2011 9:26 AM
> > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> > RE: Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Inline
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: Thursday, March 17, 2011 12:43 PM
> > > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Hi
> > >
> > > I agree that if SRS need something from SDP it will be
> > better to pass
> > > it via metadata extensions. I did some additional checks
> > and currently
> > > there is no such requirement from SRS point of view.
> > > Regarding video, there was requirement to report video
> > session even if
> > > it is not recorded.  And if it is recorded then all relevant
> > > information will be reported via RS SDP such as positions,
> > sizes etc.
> >
> > For cases where Video is not recorded, there are two possibilities:
> > 1) Video is offered by SRC in RS SDP to SRS but SRS choose
> to reject
> > video. In this case SRC can still continue to send updates
> via RS SDP
> > to SRS.
> >
> > 2) SRC may not have capability to record video and may not
> offer video
>
> > to SRS in RS SDP.  In this case also we can send a offer (m=3D0) from
> > SRC to SRS having video information.
> >
> >  My question here is - what information do we see a need to
> report ?
> > Is it just the information that video is part of CS or more
> than that
> > ?
> >
> > Ram
> >
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > > Sent: Thursday, March 17, 2011 9:06 AM
> > > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Hi Leon / All,
> > >
> > > See inline for my comments
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On
> > > > Behalf Of Leon Portman
> > > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > I agree with points below that passing actual CS SDP to
> > SRS is a not
> > > > good idea from security and layers separation point of view.
> > > > Today's SRS implementations(at least that I know about)
> > do not keep
> > > > original codec information in the database for later
> > retrieval. I am
> > > > trying to think about use cases why SRS can be
> interested in one,
> > and
> > > > except troubleshooting it is not very relevant.
> > > >
> > > > The main assumption is that SRC inspected CS SDP and
> > extracted all
> > > > relevant information like ip addresses, media line labels
> > and infos
> > > and
> > > > reported it to SRS via metadata.
> > >
> > > Are you still suggesting here that we pass across some of the
> > > parameters of CS SDP that you mentioned above to SRS via
> metadata ?
> > Are
> > > there any applications at SRS which may require this information ?
> > >
> > > I vaguely remember during IETF 79 presentation that some
> > folks (mainly
> > > from video perspective) were asking for part of information
> > related to
> > > CS SDP to be passed in metadata. But not too sure about the
> > use cases
> > > for the same.
> > > I would request people on the mailer list to speak up if
> > there are any
> > > use cases.
> > >
> > >
> > > IMO if there is only some specific SRS applications that
> need this,
> > > it's better to pass it as extension data rather than having it as
> > > attribute of MS block in the metadata.
> > >
> > >
> > > Regards,
> > > Ram
> > >
> > > >
> > > > The main reason as I see if we want to be able to report
> > CS SDP via
> > > > metadata is for the case where SRS wants to sniff RS
> RTP packets
> > > > directly and not by forking from SRC but it is out of scope.
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On
> > > > Behalf Of Paul Kyzivat
> > > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > > To: Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > I believe the codec parameters on the MS have been
> there since my
> > > first
> > > > cut at the metadata model. Putting them there was just
> speculation
> > on
> > > > my part, and doesn't imply any actual need known to me.
> > > >
> > > > If nobody feels they are necessary, then by all means
> remove them.
> > > >
> > > >         Thanks,
> > > >         Paul
> > > >
> > > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > > >> Sent: 16 March 2011 01:25
> > > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > > >> Cc: siprec@ietf.org
> > > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > > >> [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01]
> > > > >>
> > > > > <snip/>
> > > > >> <Partha>  It is the assumption done during metadata
> format that
> > RS
> > > > >> SDP may be used as Codec params for stream. Please note that
> > > format
> > > > >> draft does not have codec param in stream metadata
> element. But
> > > the
> > > > >> assumption does not seems to be working for all
> > scenarios. So we
> > > > need
> > > > >> to find the way to represent CS Media stream in
> > metadata format.
> > > > >>
> > > > >> Even before going into approach, I'm interested in knowing
> > whether
> > > > it
> > > > >> is required for SRS to understand the exact codec or SDP
> > parameter
> > > > >> used in CS? RS may be transcoded/transrated and lost
> the actual
> > > > media
> > > > >> information when it reaches SRS but the question is
> > whether it is
> > > > >> required to maintain the metadata in SRS even though
> > media (RTP)
> > > is
> > > > >> changed to new format ?
> > > > >>
> > > > >> In case we decide to pass CS codec parameter to SRS. Two
> > > approaches
> > > > >> exist to solve this issue:
> > > > >>
> > > > >> 1) Tunnel complete each participant SDP inside stream element
> > > using
> > > > >> some new optional XML element. This approach is
> straightforward
> > > and
> > > > >> scale for any CS as we are sending the complete set.
> > The overhead
> > > > >> will be increased in SRS to parse and store appropriately.
> > > > >>
> > > > >> 2) Identify the list of codec parameters *MUST*  be
> passed from
> > > SRC
> > > > >> to SRS and create the new XML element for them. This
> > is simple to
> > > > >> implement as only portion of the SDP is passed
> across but *may*
> > > have
> > > > >> scalability issue.
> > > > >>
> > > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > > interested
> > > > >> in hearing from you which way to go.
> > > > >>
> > > > >> </partha>
> > > > > [JRE] I was basing my earlier comment on the fact that the
> > metadata
> > > > model seems to indicate that the Media Stream object
> has CS codec
> > > > parameters as an attribute. This is indeed questionable.
> > I seem to
> > > > remember somebody wanting this at some stage in the
> past. From my
> > > point
> > > > of view, I don't think this information is needed by the
> > SRS - it is
> > > > historic information, nothing to do with the media
> > actually sent to
> > > the
> > > > SRS, and of no use to the SRS, in my opinion.
> > > > >
> > > > > If people do think there is a reason for providing this
> > information
> > > > to the SRS, I don't think I would favour approach 1)
> > above. The SDP
> > > > could potentially contain all sorts of information other
> > than codecs
> > > > (codecs are only a small part, and the SDP will contain
> > information
> > > > like IP addresses, ports, security keys!!!, transport,
> > non-recorded
> > > > media descriptions (e.g., MSRP channel, BFCP channel), format
> > > > parameters, SDP capability negotiation attributes, etc..
> > > > >
> > > > > Moreover, the offerer and answerer might have agreed several
> > codecs
> > > > in the SDP, so you need to look at RTP to see which codec is
> > actually
> > > > used. This can change on the fly.
> > > > >
> > > > > Finally, although the SRS's SIP/SDP stack will surely
> > have and SDP
> > > > parser, the XML metadata is intended for passing to an
> > application.
> > > > Requiring that application to contain an SDP parser is,
> I think,
> > > > unreasonable.
> > > > >
> > > > > So I have doubts as to whether it is really feasible to
> > provide CS
> > > > codec information in metadata to the SRS in a meaningful way,
> > whether
> > > > this be using approach 1) or approach 2), but I
> > particularly dislike
> > > > approach 1).
> > > > >
> > > > > John (as individual)
> > > > _______________________________________________
> > > > 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
>

From partr@cisco.com  Thu Mar 17 05:28:50 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B82B23A687A for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 05:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.869
X-Spam-Level: 
X-Spam-Status: No, score=-8.869 tagged_above=-999 required=5 tests=[AWL=-0.570, BAYES_00=-2.599, MANGLED_FORM=2.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eN1GWojOJ4B4 for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 05:28:47 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id C9E7F3A6875 for <siprec@ietf.org>; Thu, 17 Mar 2011 05:28:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=17821; q=dns/txt; s=iport; t=1300365015; x=1301574615; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=M4+6o1ySmHZM5Ptq1XmrzdOR6TMWEKFF8i1Tr1WMTKA=; b=FL5vriQ9PVNyWUclsAuvw7gAxcg7lLc9qyl17Db6Mzc/Eiy8k7c83vFw +MoM7XGw3GK3bFt5u6Q7wTo/UGeunZlivf66IV2V+dU4SuGtitHDSuY7P 6BFn9Wz9tSbx5lFuwDQWVelQEIb3rM+K3/hVZQasNRiwVNllOyPHZuh/R k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0BAHWbgU2Q/khNgWdsb2JhbACYHY0xFAEBCwsmJagjnC+Ce4JoBIUtiwQ
X-IronPort-AV: E=Sophos;i="4.63,199,1299456000"; d="scan'208";a="79621814"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 17 Mar 2011 12:30:13 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2HCUCTl009939; Thu, 17 Mar 2011 12:30:13 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Mar 2011 18:00:13 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Mar 2011 18:00:11 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904CAF00E@XMB-BGL-411.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A964A62@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAABTHCIAAA3ufgAAH1vbAAAJh80A==
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com><07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA086A9649F5@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A623904CAEFE1@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964A62@MCHP058A.g lobal-ad .net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Leon Portman" <Leon.Portman@nice.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 17 Mar 2011 12:30:13.0095 (UTC) FILETIME=[10153770:01CBE49F]
Cc: siprec@ietf.org
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 12:28:50 -0000

John,

Please read inline.

Thanks
Partha=20

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Thursday, March 17, 2011 5:08 PM
To: Parthasarathi R (partr); Leon Portman; Ram Mohan R (rmohanr); Paul
Kyzivat (pkyzivat)
Cc: siprec@ietf.org
Subject: RE: [siprec] CS Codec Parameter in stream XML element [was RE:
Review Request for draft-ram-siprec-metadata-format-01]

Partha,

Approach 1 is fine, as far as representation of start/stop times is
concerned.

So if I understand correctly the unrecordable / unrecorded stream
appears in both XML metadata and SDP, with XML containing the start/stop
times and SDP containing the media type/content. So an SDP media
description would exist for:
- recorded streams;
- streams offered by the SRC for recording but rejected by the SRS;
- streams not offered by the SRC (unrecordable streams).

The first one is fine and the second one we can't really avoid. I am
rather uncomfortable about the third one, where there is an SDP media
description describing a stream that does not exist in the RS. It
clutters the SDP unnecessarily and I feel it is worthwhile having some
minimal duplication (in XML and SDP) for recorded streams to avoid this
addition to SDP for unrecordable streams.

<Partha> I know of real audio end points (IP phones) which starts with
"m" line having port 0 during the dialog creation stage and then add the
appropriate port in the mid-dialog. Leon may be talking about one such
video phone. AFAIK, "m" line having port 0 in the offer is not violating
any of the RFC. So, those endpoint which creates CS with "m" line having
port 0 during dialog creation shall map its RS dialog creation SDP with
port 0 for "m" line  as well.=20

It is upto SRS to record/store those metadata or not. Please let me know
in case I'm missing something. </Partha>

I also feel that media type and content description are logically part
of the metadata and should appear in XML, because this is information
the application needs.=20

<Partha> IMO, the minimum required codec parameters for metadata in XML
will easily grow till little bit less than complete SDP. For example, it
is not required to pass crypto key or some other parameters. Some of the
possible to be passed across are:

1)Direction attribute - To find the original direction attribute of CS
(I explained the way to retrieve from RS SDP)

2)Codec - Finding CS codec in Transcoding scenario

3)ptime - Finding CS packetization time in Transrating scenario

4)content -  To find the exact content description attribute

5)media type -  Exact media type of CS.

6)fmtp - This attribute plays vital role in video endpoints CS

7)bandwidth - To find the exact bandwidth used in Video scenario. Some
QOS parameter may be used.

There should be a way to extend in case new attribute has to be added in
XML which may fall under extensiondata itself. It was the reason that I
proposed to pass SDP within XML earlier in codec parameter has to be
passed in XML. As Leon mentioned, it is possible to pass the whole SDP
through XML using content element of XML which will be seen as SIPREC
extensiondata in CS.

In case you foresee that this parameter has to be discussed in detail to
find the selective SDP attribute passing between SRC and SRS, I'll add
in the open item for metadata format draft, Let us discuss in IETF-80
meeting.=20
</partha>

SDP, on the other hand, is something the media engine needs in order to
receive media correctly and pass the received media in some form up to
the application for storage.

John (as individual)

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 17 March 2011 11:13
> To: Elwell, John; Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat=20
> (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was=20
> RE: Review Request for draft-ram-siprec-metadata-format-01]
>
> John,
>
> I agree that your proposal will work. I'm trying to find few other=20
> alternatives without duplication of data between SDP and XML.
>
> Approach 1: start-time and stop-time are optional XML element in=20
> stream.
> In the mentioned scenario, let stream element contains only label=20
> element and no start & stop time elements which indicates that stream=20
> is never activated within the given session.
>
> XML format for start-time & stop-time:
>          <xs:element name=3D"start-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
>                 minOccurs=3D"0"/>
>
> Approach 2: Add both start-time and stop-time in the same stream which

> indicates that stream is not started.
>
> I prefer approach 1 which will solve the issue without duplication of=20
> metadata in XML. Please let me know your opinion here.
>
> Leon,
>
> Please read inline.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> Sent: Thursday, March 17, 2011 3:44 PM
> To: Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] CS Codec Parameter in stream XML element [was=20
> RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>
> I think in these sort of situations it would be better to report the=20
> non-recorded video stream in XML metadata. If the SRC uses an m-line=20
> with port=3D0 to indicate start of an unrecordable video stream, I =
don't

> see how the SRC can report the end of that unrecordable video stream=20
> in SDP. XML seems a better option.
>
> Let me make a proposal. For each Media Stream in XML, attributes=20
> should
> indicate:
> - The type of medium (audio, video,...).
> - The content type of the medium (c.f., RFC 4796) if applicable, e.g.,

> slides, speaker...
> - The SDP label for that medium (absent if the SRC does not offer it=20
> for recording).
>
> Yes, I know the first two items would be duplication of SDP (in cases=20
> where the medium is offered for recording), but these two items would=20
> be particularly useful in cases where the medium is not offered for=20
> recording and therefore not in the SDP.
>
> John (as individual)
>
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 17 March 2011 07:36
> > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> > RE: Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Regarding information, most basic one is when video started
> and ended.
>
> <Partha> In the mentioned scenario, video is never started. Hope=20
> Approach 1 serve your purpose </Partha>
> >
> > What about the configuration where SRC knows about video
> (because it
> > is inside CS SIP session) but is not able to fork video. Is
> it still
> > should offer video m-line?
> >
> <Partha> It is upto SRC to decide whether to indicate the m-line in RS

> or not. The decision may be based on the SRC level support for video=20
> recording, policy in the SRC to record video or not. IMO, it is=20
> implementation specific and SIPREC solution SHOULD be flexible for all

> kinds of SRC </partha>
>
> > Leon
> >
> > -----Original Message-----
> > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > Sent: Thursday, March 17, 2011 9:26 AM
> > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> > RE: Review Request for draft-ram-siprec-metadata-format-01]
> >
> > Inline
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: Thursday, March 17, 2011 12:43 PM
> > > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Hi
> > >
> > > I agree that if SRS need something from SDP it will be
> > better to pass
> > > it via metadata extensions. I did some additional checks
> > and currently
> > > there is no such requirement from SRS point of view.
> > > Regarding video, there was requirement to report video
> > session even if
> > > it is not recorded.  And if it is recorded then all relevant=20
> > > information will be reported via RS SDP such as positions,
> > sizes etc.
> >
> > For cases where Video is not recorded, there are two possibilities:
> > 1) Video is offered by SRC in RS SDP to SRS but SRS choose
> to reject
> > video. In this case SRC can still continue to send updates
> via RS SDP
> > to SRS.
> >
> > 2) SRC may not have capability to record video and may not
> offer video
>
> > to SRS in RS SDP.  In this case also we can send a offer (m=3D0) =
from=20
> > SRC to SRS having video information.
> >
> >  My question here is - what information do we see a need to
> report ?
> > Is it just the information that video is part of CS or more
> than that
> > ?
> >
> > Ram
> >
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > > Sent: Thursday, March 17, 2011 9:06 AM
> > > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > RE:
> > > Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Hi Leon / All,
> > >
> > > See inline for my comments
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On
> > > > Behalf Of Leon Portman
> > > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > I agree with points below that passing actual CS SDP to
> > SRS is a not
> > > > good idea from security and layers separation point of view.
> > > > Today's SRS implementations(at least that I know about)
> > do not keep
> > > > original codec information in the database for later
> > retrieval. I am
> > > > trying to think about use cases why SRS can be
> interested in one,
> > and
> > > > except troubleshooting it is not very relevant.
> > > >
> > > > The main assumption is that SRC inspected CS SDP and
> > extracted all
> > > > relevant information like ip addresses, media line labels
> > and infos
> > > and
> > > > reported it to SRS via metadata.
> > >
> > > Are you still suggesting here that we pass across some of the=20
> > > parameters of CS SDP that you mentioned above to SRS via
> metadata ?
> > Are
> > > there any applications at SRS which may require this information ?
> > >
> > > I vaguely remember during IETF 79 presentation that some
> > folks (mainly
> > > from video perspective) were asking for part of information
> > related to
> > > CS SDP to be passed in metadata. But not too sure about the
> > use cases
> > > for the same.
> > > I would request people on the mailer list to speak up if
> > there are any
> > > use cases.
> > >
> > >
> > > IMO if there is only some specific SRS applications that
> need this,
> > > it's better to pass it as extension data rather than having it as=20
> > > attribute of MS block in the metadata.
> > >
> > >
> > > Regards,
> > > Ram
> > >
> > > >
> > > > The main reason as I see if we want to be able to report
> > CS SDP via
> > > > metadata is for the case where SRS wants to sniff RS
> RTP packets
> > > > directly and not by forking from SRC but it is out of scope.
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On
> > > > Behalf Of Paul Kyzivat
> > > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > > To: Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > I believe the codec parameters on the MS have been
> there since my
> > > first
> > > > cut at the metadata model. Putting them there was just
> speculation
> > on
> > > > my part, and doesn't imply any actual need known to me.
> > > >
> > > > If nobody feels they are necessary, then by all means
> remove them.
> > > >
> > > >         Thanks,
> > > >         Paul
> > > >
> > > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > > >> Sent: 16 March 2011 01:25
> > > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > > >> Cc: siprec@ietf.org
> > > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > > >> [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01]
> > > > >>
> > > > > <snip/>
> > > > >> <Partha>  It is the assumption done during metadata
> format that
> > RS
> > > > >> SDP may be used as Codec params for stream. Please note that
> > > format
> > > > >> draft does not have codec param in stream metadata
> element. But
> > > the
> > > > >> assumption does not seems to be working for all
> > scenarios. So we
> > > > need
> > > > >> to find the way to represent CS Media stream in
> > metadata format.
> > > > >>
> > > > >> Even before going into approach, I'm interested in knowing
> > whether
> > > > it
> > > > >> is required for SRS to understand the exact codec or SDP
> > parameter
> > > > >> used in CS? RS may be transcoded/transrated and lost
> the actual
> > > > media
> > > > >> information when it reaches SRS but the question is
> > whether it is
> > > > >> required to maintain the metadata in SRS even though
> > media (RTP)
> > > is
> > > > >> changed to new format ?
> > > > >>
> > > > >> In case we decide to pass CS codec parameter to SRS. Two
> > > approaches
> > > > >> exist to solve this issue:
> > > > >>
> > > > >> 1) Tunnel complete each participant SDP inside stream element
> > > using
> > > > >> some new optional XML element. This approach is
> straightforward
> > > and
> > > > >> scale for any CS as we are sending the complete set.
> > The overhead
> > > > >> will be increased in SRS to parse and store appropriately.
> > > > >>
> > > > >> 2) Identify the list of codec parameters *MUST*  be
> passed from
> > > SRC
> > > > >> to SRS and create the new XML element for them. This
> > is simple to
> > > > >> implement as only portion of the SDP is passed
> across but *may*
> > > have
> > > > >> scalability issue.
> > > > >>
> > > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > > interested
> > > > >> in hearing from you which way to go.
> > > > >>
> > > > >> </partha>
> > > > > [JRE] I was basing my earlier comment on the fact that the
> > metadata
> > > > model seems to indicate that the Media Stream object
> has CS codec
> > > > parameters as an attribute. This is indeed questionable.
> > I seem to
> > > > remember somebody wanting this at some stage in the
> past. From my
> > > point
> > > > of view, I don't think this information is needed by the
> > SRS - it is
> > > > historic information, nothing to do with the media
> > actually sent to
> > > the
> > > > SRS, and of no use to the SRS, in my opinion.
> > > > >
> > > > > If people do think there is a reason for providing this
> > information
> > > > to the SRS, I don't think I would favour approach 1)
> > above. The SDP
> > > > could potentially contain all sorts of information other
> > than codecs
> > > > (codecs are only a small part, and the SDP will contain
> > information
> > > > like IP addresses, ports, security keys!!!, transport,
> > non-recorded
> > > > media descriptions (e.g., MSRP channel, BFCP channel), format=20
> > > > parameters, SDP capability negotiation attributes, etc..
> > > > >
> > > > > Moreover, the offerer and answerer might have agreed several
> > codecs
> > > > in the SDP, so you need to look at RTP to see which codec is
> > actually
> > > > used. This can change on the fly.
> > > > >
> > > > > Finally, although the SRS's SIP/SDP stack will surely
> > have and SDP
> > > > parser, the XML metadata is intended for passing to an
> > application.
> > > > Requiring that application to contain an SDP parser is,
> I think,
> > > > unreasonable.
> > > > >
> > > > > So I have doubts as to whether it is really feasible to
> > provide CS
> > > > codec information in metadata to the SRS in a meaningful way,
> > whether
> > > > this be using approach 1) or approach 2), but I
> > particularly dislike
> > > > approach 1).
> > > > >
> > > > > John (as individual)
> > > > _______________________________________________
> > > > 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
>

From john.elwell@siemens-enterprise.com  Thu Mar 17 07:01:20 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C4F73A699C for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 07:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.446
X-Spam-Level: 
X-Spam-Status: No, score=-101.446 tagged_above=-999 required=5 tests=[AWL=-1.147, BAYES_00=-2.599, MANGLED_FORM=2.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qkhxn5H-W8r4 for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 07:01:18 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 0CE433A695B for <siprec@ietf.org>; Thu, 17 Mar 2011 07:01:17 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3788189; Thu, 17 Mar 2011 15:02:44 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id BE69423F0278; Thu, 17 Mar 2011 15:02:44 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 17 Mar 2011 15:02:45 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, Leon Portman <Leon.Portman@nice.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
Date: Thu, 17 Mar 2011 15:02:43 +0100
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAABTHCIAAA3ufgAAH1vbAAAJh80AAD7Kzg
Message-ID: <A444A0F8084434499206E78C106220CA086A964B5D@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com><07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA086A9649F5@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A623904CAEFE1@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964A62@MCHP058A.g lobal-ad	.net> <A11921905DA1564D9BCF64A6430A623904CAF00E@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904CAF00E@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 14:01:20 -0000

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 17 March 2011 12:30
> To: Elwell, John; Leon Portman; Ram Mohan R (rmohanr); Paul
> Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was RE: Review Request for
> draft-ram-siprec-metadata-format-01]
>
> John,
>
> Please read inline.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 17, 2011 5:08 PM
> To: Parthasarathi R (partr); Leon Portman; Ram Mohan R (rmohanr); Paul
> Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>
> Partha,
>
> Approach 1 is fine, as far as representation of start/stop times is
> concerned.
>
> So if I understand correctly the unrecordable / unrecorded stream
> appears in both XML metadata and SDP, with XML containing the
> start/stop
> times and SDP containing the media type/content. So an SDP media
> description would exist for:
> - recorded streams;
> - streams offered by the SRC for recording but rejected by the SRS;
> - streams not offered by the SRC (unrecordable streams).
>
> The first one is fine and the second one we can't really avoid. I am
> rather uncomfortable about the third one, where there is an SDP media
> description describing a stream that does not exist in the RS. It
> clutters the SDP unnecessarily and I feel it is worthwhile having some
> minimal duplication (in XML and SDP) for recorded streams to
> avoid this
> addition to SDP for unrecordable streams.
>
> <Partha> I know of real audio end points (IP phones) which starts with
> "m" line having port 0 during the dialog creation stage and
> then add the
> appropriate port in the mid-dialog. Leon may be talking about one such
> video phone. AFAIK, "m" line having port 0 in the offer is
> not violating
> any of the RFC. So, those endpoint which creates CS with "m"
> line having
> port 0 during dialog creation shall map its RS dialog
> creation SDP with
> port 0 for "m" line  as well.
>
> It is upto SRS to record/store those metadata or not. Please
> let me know
> in case I'm missing something. </Partha>
[JRE] I agree it is valid SDP - I am just uncomfortable with the SRC offeri=
ng something that it doesn't even intend to use in the future. Normally a p=
ort 0 m-line in the initial offer implies a medium that might be turned on =
later, but I may be wrong.

>
> I also feel that media type and content description are logically part
> of the metadata and should appear in XML, because this is information
> the application needs.
>
> <Partha> IMO, the minimum required codec parameters for
> metadata in XML
> will easily grow till little bit less than complete SDP. For
> example, it
> is not required to pass crypto key or some other parameters.
> Some of the
> possible to be passed across are:
>
> 1)Direction attribute - To find the original direction attribute of CS
> (I explained the way to retrieve from RS SDP)
>
> 2)Codec - Finding CS codec in Transcoding scenario
[JRE] I don't see why this is relevant - I don't think we have a requiremen=
t. Also, even if CS codec information is made available to the SRS, this is=
 only the CS codec as seen by the SRC, and perhaps other codecs were used u=
pstream that are not visible to the SRC. For example, Remote party A transm=
its audio using G.723 to a mixer, and party B transmits audio using G.711 t=
o the mixer. The mixer then transmits audio using OPUS super-wideband to pa=
rty C, and the SRC is located at C's UA (or on the path between the mixer a=
nd C's UA). The SRC uses G.722, say, to send audio to the SRS and reports t=
hat the CS used OPUS super-wideband. What can the SRS learn from this? The =
audio quality will be constrained by the worst link, i.e., G.723 when A is =
talking.

>
> 3)ptime - Finding CS packetization time in Transrating scenario
[JRE] I don't think CS ptime is relevant. Also pTime doesn't give actual pa=
cketization time, which can vary during the session..

>
> 4)content -  To find the exact content description attribute
>
> 5)media type -  Exact media type of CS.
>
> 6)fmtp - This attribute plays vital role in video endpoints CS
[JRE] Again I don't see the relevance of particular formats used on the CS.=
 By the time media reaches the SRS, it has been reformatted in accordance w=
ith fmtp parameters for the RS (and in some cases mixed with other streams =
at the SRC before sending to the SRS) so I really don't see how knowledge o=
f the fmtp parameters used on the CS can help the SRC (with analysing the m=
edia, say).

>
> 7)bandwidth - To find the exact bandwidth used in Video scenario. Some
> QOS parameter may be used.
[JRE] Again I don't see the relevance.

>
> There should be a way to extend in case new attribute has to
> be added in
> XML which may fall under extensiondata itself. It was the
> reason that I
> proposed to pass SDP within XML earlier in codec parameter has to be
> passed in XML. As Leon mentioned, it is possible to pass the whole SDP
> through XML using content element of XML which will be seen as SIPREC
> extensiondata in CS.
[JRE] I agree with extensibility, and if there are future requirements to s=
end any of this information in XML, we could do that. But I fail to see any=
 motivation for defining these now. Also, as explained before, I am uncomfo=
rtable about encapsulating CS SDP within XML metadata.

John (as individual)


>
> In case you foresee that this parameter has to be discussed
> in detail to
> find the selective SDP attribute passing between SRC and SRS, I'll add
> in the open item for metadata format draft, Let us discuss in IETF-80
> meeting.
> </partha>
>
> SDP, on the other hand, is something the media engine needs
> in order to
> receive media correctly and pass the received media in some form up to
> the application for storage.
>
> John (as individual)
>
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > Sent: 17 March 2011 11:13
> > To: Elwell, John; Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat
> > (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> > RE: Review Request for draft-ram-siprec-metadata-format-01]
> >
> > John,
> >
> > I agree that your proposal will work. I'm trying to find few other
> > alternatives without duplication of data between SDP and XML.
> >
> > Approach 1: start-time and stop-time are optional XML element in
> > stream.
> > In the mentioned scenario, let stream element contains only label
> > element and no start & stop time elements which indicates
> that stream
> > is never activated within the given session.
> >
> > XML format for start-time & stop-time:
> >          <xs:element name=3D"start-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >
> > Approach 2: Add both start-time and stop-time in the same
> stream which
>
> > indicates that stream is not started.
> >
> > I prefer approach 1 which will solve the issue without
> duplication of
> > metadata in XML. Please let me know your opinion here.
> >
> > Leon,
> >
> > Please read inline.
> >
> > Thanks
> > Partha
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> > Sent: Thursday, March 17, 2011 3:44 PM
> > To: Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
> > RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > I think in these sort of situations it would be better to
> report the
> > non-recorded video stream in XML metadata. If the SRC uses
> an m-line
> > with port=3D0 to indicate start of an unrecordable video
> stream, I don't
>
> > see how the SRC can report the end of that unrecordable
> video stream
> > in SDP. XML seems a better option.
> >
> > Let me make a proposal. For each Media Stream in XML, attributes
> > should
> > indicate:
> > - The type of medium (audio, video,...).
> > - The content type of the medium (c.f., RFC 4796) if
> applicable, e.g.,
>
> > slides, speaker...
> > - The SDP label for that medium (absent if the SRC does not
> offer it
> > for recording).
> >
> > Yes, I know the first two items would be duplication of SDP
> (in cases
> > where the medium is offered for recording), but these two
> items would
> > be particularly useful in cases where the medium is not offered for
> > recording and therefore not in the SDP.
> >
> > John (as individual)
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 17 March 2011 07:36
> > > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > > RE: Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Regarding information, most basic one is when video started
> > and ended.
> >
> > <Partha> In the mentioned scenario, video is never started. Hope
> > Approach 1 serve your purpose </Partha>
> > >
> > > What about the configuration where SRC knows about video
> > (because it
> > > is inside CS SIP session) but is not able to fork video. Is
> > it still
> > > should offer video m-line?
> > >
> > <Partha> It is upto SRC to decide whether to indicate the
> m-line in RS
>
> > or not. The decision may be based on the SRC level support
> for video
> > recording, policy in the SRC to record video or not. IMO, it is
> > implementation specific and SIPREC solution SHOULD be
> flexible for all
>
> > kinds of SRC </partha>
> >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > > Sent: Thursday, March 17, 2011 9:26 AM
> > > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > > RE: Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Inline
> > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: Thursday, March 17, 2011 12:43 PM
> > > > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > Hi
> > > >
> > > > I agree that if SRS need something from SDP it will be
> > > better to pass
> > > > it via metadata extensions. I did some additional checks
> > > and currently
> > > > there is no such requirement from SRS point of view.
> > > > Regarding video, there was requirement to report video
> > > session even if
> > > > it is not recorded.  And if it is recorded then all relevant
> > > > information will be reported via RS SDP such as positions,
> > > sizes etc.
> > >
> > > For cases where Video is not recorded, there are two
> possibilities:
> > > 1) Video is offered by SRC in RS SDP to SRS but SRS choose
> > to reject
> > > video. In this case SRC can still continue to send updates
> > via RS SDP
> > > to SRS.
> > >
> > > 2) SRC may not have capability to record video and may not
> > offer video
> >
> > > to SRS in RS SDP.  In this case also we can send a offer
> (m=3D0) from
> > > SRC to SRS having video information.
> > >
> > >  My question here is - what information do we see a need to
> > report ?
> > > Is it just the information that video is part of CS or more
> > than that
> > > ?
> > >
> > > Ram
> > >
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > > > Sent: Thursday, March 17, 2011 9:06 AM
> > > > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > Hi Leon / All,
> > > >
> > > > See inline for my comments
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On
> > > > > Behalf Of Leon Portman
> > > > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > > element [was
> > > > RE:
> > > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > > >
> > > > > I agree with points below that passing actual CS SDP to
> > > SRS is a not
> > > > > good idea from security and layers separation point of view.
> > > > > Today's SRS implementations(at least that I know about)
> > > do not keep
> > > > > original codec information in the database for later
> > > retrieval. I am
> > > > > trying to think about use cases why SRS can be
> > interested in one,
> > > and
> > > > > except troubleshooting it is not very relevant.
> > > > >
> > > > > The main assumption is that SRC inspected CS SDP and
> > > extracted all
> > > > > relevant information like ip addresses, media line labels
> > > and infos
> > > > and
> > > > > reported it to SRS via metadata.
> > > >
> > > > Are you still suggesting here that we pass across some of the
> > > > parameters of CS SDP that you mentioned above to SRS via
> > metadata ?
> > > Are
> > > > there any applications at SRS which may require this
> information ?
> > > >
> > > > I vaguely remember during IETF 79 presentation that some
> > > folks (mainly
> > > > from video perspective) were asking for part of information
> > > related to
> > > > CS SDP to be passed in metadata. But not too sure about the
> > > use cases
> > > > for the same.
> > > > I would request people on the mailer list to speak up if
> > > there are any
> > > > use cases.
> > > >
> > > >
> > > > IMO if there is only some specific SRS applications that
> > need this,
> > > > it's better to pass it as extension data rather than
> having it as
> > > > attribute of MS block in the metadata.
> > > >
> > > >
> > > > Regards,
> > > > Ram
> > > >
> > > > >
> > > > > The main reason as I see if we want to be able to report
> > > CS SDP via
> > > > > metadata is for the case where SRS wants to sniff RS
> > RTP packets
> > > > > directly and not by forking from SRC but it is out of scope.
> > > > >
> > > > > Leon
> > > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On
> > > > > Behalf Of Paul Kyzivat
> > > > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > > > To: Elwell, John
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > > element [was
> > > > RE:
> > > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > > >
> > > > > I believe the codec parameters on the MS have been
> > there since my
> > > > first
> > > > > cut at the metadata model. Putting them there was just
> > speculation
> > > on
> > > > > my part, and doesn't imply any actual need known to me.
> > > > >
> > > > > If nobody feels they are necessary, then by all means
> > remove them.
> > > > >
> > > > >         Thanks,
> > > > >         Paul
> > > > >
> > > > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > > > >
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > > > >> Sent: 16 March 2011 01:25
> > > > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > > > >> Cc: siprec@ietf.org
> > > > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > > > >> [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01]
> > > > > >>
> > > > > > <snip/>
> > > > > >> <Partha>  It is the assumption done during metadata
> > format that
> > > RS
> > > > > >> SDP may be used as Codec params for stream. Please
> note that
> > > > format
> > > > > >> draft does not have codec param in stream metadata
> > element. But
> > > > the
> > > > > >> assumption does not seems to be working for all
> > > scenarios. So we
> > > > > need
> > > > > >> to find the way to represent CS Media stream in
> > > metadata format.
> > > > > >>
> > > > > >> Even before going into approach, I'm interested in knowing
> > > whether
> > > > > it
> > > > > >> is required for SRS to understand the exact codec or SDP
> > > parameter
> > > > > >> used in CS? RS may be transcoded/transrated and lost
> > the actual
> > > > > media
> > > > > >> information when it reaches SRS but the question is
> > > whether it is
> > > > > >> required to maintain the metadata in SRS even though
> > > media (RTP)
> > > > is
> > > > > >> changed to new format ?
> > > > > >>
> > > > > >> In case we decide to pass CS codec parameter to SRS. Two
> > > > approaches
> > > > > >> exist to solve this issue:
> > > > > >>
> > > > > >> 1) Tunnel complete each participant SDP inside
> stream element
> > > > using
> > > > > >> some new optional XML element. This approach is
> > straightforward
> > > > and
> > > > > >> scale for any CS as we are sending the complete set.
> > > The overhead
> > > > > >> will be increased in SRS to parse and store appropriately.
> > > > > >>
> > > > > >> 2) Identify the list of codec parameters *MUST*  be
> > passed from
> > > > SRC
> > > > > >> to SRS and create the new XML element for them. This
> > > is simple to
> > > > > >> implement as only portion of the SDP is passed
> > across but *may*
> > > > have
> > > > > >> scalability issue.
> > > > > >>
> > > > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > > > interested
> > > > > >> in hearing from you which way to go.
> > > > > >>
> > > > > >> </partha>
> > > > > > [JRE] I was basing my earlier comment on the fact that the
> > > metadata
> > > > > model seems to indicate that the Media Stream object
> > has CS codec
> > > > > parameters as an attribute. This is indeed questionable.
> > > I seem to
> > > > > remember somebody wanting this at some stage in the
> > past. From my
> > > > point
> > > > > of view, I don't think this information is needed by the
> > > SRS - it is
> > > > > historic information, nothing to do with the media
> > > actually sent to
> > > > the
> > > > > SRS, and of no use to the SRS, in my opinion.
> > > > > >
> > > > > > If people do think there is a reason for providing this
> > > information
> > > > > to the SRS, I don't think I would favour approach 1)
> > > above. The SDP
> > > > > could potentially contain all sorts of information other
> > > than codecs
> > > > > (codecs are only a small part, and the SDP will contain
> > > information
> > > > > like IP addresses, ports, security keys!!!, transport,
> > > non-recorded
> > > > > media descriptions (e.g., MSRP channel, BFCP channel), format
> > > > > parameters, SDP capability negotiation attributes, etc..
> > > > > >
> > > > > > Moreover, the offerer and answerer might have agreed several
> > > codecs
> > > > > in the SDP, so you need to look at RTP to see which codec is
> > > actually
> > > > > used. This can change on the fly.
> > > > > >
> > > > > > Finally, although the SRS's SIP/SDP stack will surely
> > > have and SDP
> > > > > parser, the XML metadata is intended for passing to an
> > > application.
> > > > > Requiring that application to contain an SDP parser is,
> > I think,
> > > > > unreasonable.
> > > > > >
> > > > > > So I have doubts as to whether it is really feasible to
> > > provide CS
> > > > > codec information in metadata to the SRS in a meaningful way,
> > > whether
> > > > > this be using approach 1) or approach 2), but I
> > > particularly dislike
> > > > > approach 1).
> > > > > >
> > > > > > John (as individual)
> > > > > _______________________________________________
> > > > > 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
> >
>

From Leon.Portman@nice.com  Thu Mar 17 07:16:03 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56C9D3A68AD for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 07:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[AWL=-0.935, BAYES_00=-2.599, MANGLED_FORM=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GdhOp0l552Y7 for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 07:16:01 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 882FE3A693F for <siprec@ietf.org>; Thu, 17 Mar 2011 07:16:00 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Thu, 17 Mar 2011 16:17:27 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
Date: Thu, 17 Mar 2011 16:17:27 +0200
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAABTHCIAAA3ufgAAH1vbAAAJh80AAD7KzgAAGCawA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A9491A69@TLVMBX01.nice.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com><07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA086A9649F5@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A623904CAEFE1@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964A62@MCHP058A.g lobal-ad	.net> <A11921905DA1564D9BCF64A6430A623904CAF00E@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964B5D@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A964B5D@MCHP058A.global-ad.net>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 14:16:03 -0000

I completely agree with John's points below. What is important is RS codec =
info and not CS.

Leon
-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
Sent: Thursday, March 17, 2011 4:03 PM
To: Parthasarathi R (partr); Leon Portman; Ram Mohan R (rmohanr); Paul Kyzi=
vat (pkyzivat)
Cc: siprec@ietf.org
Subject: RE: [siprec] CS Codec Parameter in stream XML element [was RE: Rev=
iew Request for draft-ram-siprec-metadata-format-01]



> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 17 March 2011 12:30
> To: Elwell, John; Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat
> (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE: Review Request for draft-ram-siprec-metadata-format-01]
>
> John,
>
> Please read inline.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 17, 2011 5:08 PM
> To: Parthasarathi R (partr); Leon Portman; Ram Mohan R (rmohanr); Paul
> Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>
> Partha,
>
> Approach 1 is fine, as far as representation of start/stop times is
> concerned.
>
> So if I understand correctly the unrecordable / unrecorded stream
> appears in both XML metadata and SDP, with XML containing the
> start/stop times and SDP containing the media type/content. So an SDP
> media description would exist for:
> - recorded streams;
> - streams offered by the SRC for recording but rejected by the SRS;
> - streams not offered by the SRC (unrecordable streams).
>
> The first one is fine and the second one we can't really avoid. I am
> rather uncomfortable about the third one, where there is an SDP media
> description describing a stream that does not exist in the RS. It
> clutters the SDP unnecessarily and I feel it is worthwhile having some
> minimal duplication (in XML and SDP) for recorded streams to avoid
> this addition to SDP for unrecordable streams.
>
> <Partha> I know of real audio end points (IP phones) which starts with
> "m" line having port 0 during the dialog creation stage and then add
> the appropriate port in the mid-dialog. Leon may be talking about one
> such video phone. AFAIK, "m" line having port 0 in the offer is not
> violating any of the RFC. So, those endpoint which creates CS with "m"
> line having
> port 0 during dialog creation shall map its RS dialog creation SDP
> with port 0 for "m" line  as well.
>
> It is upto SRS to record/store those metadata or not. Please let me
> know in case I'm missing something. </Partha>
[JRE] I agree it is valid SDP - I am just uncomfortable with the SRC offeri=
ng something that it doesn't even intend to use in the future. Normally a p=
ort 0 m-line in the initial offer implies a medium that might be turned on =
later, but I may be wrong.

>
> I also feel that media type and content description are logically part
> of the metadata and should appear in XML, because this is information
> the application needs.
>
> <Partha> IMO, the minimum required codec parameters for
> metadata in XML
> will easily grow till little bit less than complete SDP. For
> example, it
> is not required to pass crypto key or some other parameters.
> Some of the
> possible to be passed across are:
>
> 1)Direction attribute - To find the original direction attribute of CS
> (I explained the way to retrieve from RS SDP)
>
> 2)Codec - Finding CS codec in Transcoding scenario
[JRE] I don't see why this is relevant - I don't think we have a requiremen=
t. Also, even if CS codec information is made available to the SRS, this is=
 only the CS codec as seen by the SRC, and perhaps other codecs were used u=
pstream that are not visible to the SRC. For example, Remote party A transm=
its audio using G.723 to a mixer, and party B transmits audio using G.711 t=
o the mixer. The mixer then transmits audio using OPUS super-wideband to pa=
rty C, and the SRC is located at C's UA (or on the path between the mixer a=
nd C's UA). The SRC uses G.722, say, to send audio to the SRS and reports t=
hat the CS used OPUS super-wideband. What can the SRS learn from this? The =
audio quality will be constrained by the worst link, i.e., G.723 when A is =
talking.

>
> 3)ptime - Finding CS packetization time in Transrating scenario
[JRE] I don't think CS ptime is relevant. Also pTime doesn't give actual pa=
cketization time, which can vary during the session..

>
> 4)content -  To find the exact content description attribute
>
> 5)media type -  Exact media type of CS.
>
> 6)fmtp - This attribute plays vital role in video endpoints CS
[JRE] Again I don't see the relevance of particular formats used on the CS.=
 By the time media reaches the SRS, it has been reformatted in accordance w=
ith fmtp parameters for the RS (and in some cases mixed with other streams =
at the SRC before sending to the SRS) so I really don't see how knowledge o=
f the fmtp parameters used on the CS can help the SRC (with analysing the m=
edia, say).

>
> 7)bandwidth - To find the exact bandwidth used in Video scenario. Some
> QOS parameter may be used.
[JRE] Again I don't see the relevance.

>
> There should be a way to extend in case new attribute has to
> be added in
> XML which may fall under extensiondata itself. It was the
> reason that I
> proposed to pass SDP within XML earlier in codec parameter has to be
> passed in XML. As Leon mentioned, it is possible to pass the whole SDP
> through XML using content element of XML which will be seen as SIPREC
> extensiondata in CS.
[JRE] I agree with extensibility, and if there are future requirements to s=
end any of this information in XML, we could do that. But I fail to see any=
 motivation for defining these now. Also, as explained before, I am uncomfo=
rtable about encapsulating CS SDP within XML metadata.

John (as individual)


>
> In case you foresee that this parameter has to be discussed
> in detail to
> find the selective SDP attribute passing between SRC and SRS, I'll add
> in the open item for metadata format draft, Let us discuss in IETF-80
> meeting.
> </partha>
>
> SDP, on the other hand, is something the media engine needs
> in order to
> receive media correctly and pass the received media in some form up to
> the application for storage.
>
> John (as individual)
>
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > Sent: 17 March 2011 11:13
> > To: Elwell, John; Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat
> > (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> > RE: Review Request for draft-ram-siprec-metadata-format-01]
> >
> > John,
> >
> > I agree that your proposal will work. I'm trying to find few other
> > alternatives without duplication of data between SDP and XML.
> >
> > Approach 1: start-time and stop-time are optional XML element in
> > stream.
> > In the mentioned scenario, let stream element contains only label
> > element and no start & stop time elements which indicates
> that stream
> > is never activated within the given session.
> >
> > XML format for start-time & stop-time:
> >          <xs:element name=3D"start-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >
> > Approach 2: Add both start-time and stop-time in the same
> stream which
>
> > indicates that stream is not started.
> >
> > I prefer approach 1 which will solve the issue without
> duplication of
> > metadata in XML. Please let me know your opinion here.
> >
> > Leon,
> >
> > Please read inline.
> >
> > Thanks
> > Partha
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> > Sent: Thursday, March 17, 2011 3:44 PM
> > To: Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
> > RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > I think in these sort of situations it would be better to
> report the
> > non-recorded video stream in XML metadata. If the SRC uses
> an m-line
> > with port=3D0 to indicate start of an unrecordable video
> stream, I don't
>
> > see how the SRC can report the end of that unrecordable
> video stream
> > in SDP. XML seems a better option.
> >
> > Let me make a proposal. For each Media Stream in XML, attributes
> > should
> > indicate:
> > - The type of medium (audio, video,...).
> > - The content type of the medium (c.f., RFC 4796) if
> applicable, e.g.,
>
> > slides, speaker...
> > - The SDP label for that medium (absent if the SRC does not
> offer it
> > for recording).
> >
> > Yes, I know the first two items would be duplication of SDP
> (in cases
> > where the medium is offered for recording), but these two
> items would
> > be particularly useful in cases where the medium is not offered for
> > recording and therefore not in the SDP.
> >
> > John (as individual)
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 17 March 2011 07:36
> > > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > > RE: Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Regarding information, most basic one is when video started
> > and ended.
> >
> > <Partha> In the mentioned scenario, video is never started. Hope
> > Approach 1 serve your purpose </Partha>
> > >
> > > What about the configuration where SRC knows about video
> > (because it
> > > is inside CS SIP session) but is not able to fork video. Is
> > it still
> > > should offer video m-line?
> > >
> > <Partha> It is upto SRC to decide whether to indicate the
> m-line in RS
>
> > or not. The decision may be based on the SRC level support
> for video
> > recording, policy in the SRC to record video or not. IMO, it is
> > implementation specific and SIPREC solution SHOULD be
> flexible for all
>
> > kinds of SRC </partha>
> >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > > Sent: Thursday, March 17, 2011 9:26 AM
> > > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > > RE: Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Inline
> > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: Thursday, March 17, 2011 12:43 PM
> > > > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > Hi
> > > >
> > > > I agree that if SRS need something from SDP it will be
> > > better to pass
> > > > it via metadata extensions. I did some additional checks
> > > and currently
> > > > there is no such requirement from SRS point of view.
> > > > Regarding video, there was requirement to report video
> > > session even if
> > > > it is not recorded.  And if it is recorded then all relevant
> > > > information will be reported via RS SDP such as positions,
> > > sizes etc.
> > >
> > > For cases where Video is not recorded, there are two
> possibilities:
> > > 1) Video is offered by SRC in RS SDP to SRS but SRS choose
> > to reject
> > > video. In this case SRC can still continue to send updates
> > via RS SDP
> > > to SRS.
> > >
> > > 2) SRC may not have capability to record video and may not
> > offer video
> >
> > > to SRS in RS SDP.  In this case also we can send a offer
> (m=3D0) from
> > > SRC to SRS having video information.
> > >
> > >  My question here is - what information do we see a need to
> > report ?
> > > Is it just the information that video is part of CS or more
> > than that
> > > ?
> > >
> > > Ram
> > >
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > > > Sent: Thursday, March 17, 2011 9:06 AM
> > > > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > Hi Leon / All,
> > > >
> > > > See inline for my comments
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On
> > > > > Behalf Of Leon Portman
> > > > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > > element [was
> > > > RE:
> > > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > > >
> > > > > I agree with points below that passing actual CS SDP to
> > > SRS is a not
> > > > > good idea from security and layers separation point of view.
> > > > > Today's SRS implementations(at least that I know about)
> > > do not keep
> > > > > original codec information in the database for later
> > > retrieval. I am
> > > > > trying to think about use cases why SRS can be
> > interested in one,
> > > and
> > > > > except troubleshooting it is not very relevant.
> > > > >
> > > > > The main assumption is that SRC inspected CS SDP and
> > > extracted all
> > > > > relevant information like ip addresses, media line labels
> > > and infos
> > > > and
> > > > > reported it to SRS via metadata.
> > > >
> > > > Are you still suggesting here that we pass across some of the
> > > > parameters of CS SDP that you mentioned above to SRS via
> > metadata ?
> > > Are
> > > > there any applications at SRS which may require this
> information ?
> > > >
> > > > I vaguely remember during IETF 79 presentation that some
> > > folks (mainly
> > > > from video perspective) were asking for part of information
> > > related to
> > > > CS SDP to be passed in metadata. But not too sure about the
> > > use cases
> > > > for the same.
> > > > I would request people on the mailer list to speak up if
> > > there are any
> > > > use cases.
> > > >
> > > >
> > > > IMO if there is only some specific SRS applications that
> > need this,
> > > > it's better to pass it as extension data rather than
> having it as
> > > > attribute of MS block in the metadata.
> > > >
> > > >
> > > > Regards,
> > > > Ram
> > > >
> > > > >
> > > > > The main reason as I see if we want to be able to report
> > > CS SDP via
> > > > > metadata is for the case where SRS wants to sniff RS
> > RTP packets
> > > > > directly and not by forking from SRC but it is out of scope.
> > > > >
> > > > > Leon
> > > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On
> > > > > Behalf Of Paul Kyzivat
> > > > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > > > To: Elwell, John
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > > element [was
> > > > RE:
> > > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > > >
> > > > > I believe the codec parameters on the MS have been
> > there since my
> > > > first
> > > > > cut at the metadata model. Putting them there was just
> > speculation
> > > on
> > > > > my part, and doesn't imply any actual need known to me.
> > > > >
> > > > > If nobody feels they are necessary, then by all means
> > remove them.
> > > > >
> > > > >         Thanks,
> > > > >         Paul
> > > > >
> > > > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > > > >
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > > > >> Sent: 16 March 2011 01:25
> > > > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > > > >> Cc: siprec@ietf.org
> > > > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > > > >> [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01]
> > > > > >>
> > > > > > <snip/>
> > > > > >> <Partha>  It is the assumption done during metadata
> > format that
> > > RS
> > > > > >> SDP may be used as Codec params for stream. Please
> note that
> > > > format
> > > > > >> draft does not have codec param in stream metadata
> > element. But
> > > > the
> > > > > >> assumption does not seems to be working for all
> > > scenarios. So we
> > > > > need
> > > > > >> to find the way to represent CS Media stream in
> > > metadata format.
> > > > > >>
> > > > > >> Even before going into approach, I'm interested in knowing
> > > whether
> > > > > it
> > > > > >> is required for SRS to understand the exact codec or SDP
> > > parameter
> > > > > >> used in CS? RS may be transcoded/transrated and lost
> > the actual
> > > > > media
> > > > > >> information when it reaches SRS but the question is
> > > whether it is
> > > > > >> required to maintain the metadata in SRS even though
> > > media (RTP)
> > > > is
> > > > > >> changed to new format ?
> > > > > >>
> > > > > >> In case we decide to pass CS codec parameter to SRS. Two
> > > > approaches
> > > > > >> exist to solve this issue:
> > > > > >>
> > > > > >> 1) Tunnel complete each participant SDP inside
> stream element
> > > > using
> > > > > >> some new optional XML element. This approach is
> > straightforward
> > > > and
> > > > > >> scale for any CS as we are sending the complete set.
> > > The overhead
> > > > > >> will be increased in SRS to parse and store appropriately.
> > > > > >>
> > > > > >> 2) Identify the list of codec parameters *MUST*  be
> > passed from
> > > > SRC
> > > > > >> to SRS and create the new XML element for them. This
> > > is simple to
> > > > > >> implement as only portion of the SDP is passed
> > across but *may*
> > > > have
> > > > > >> scalability issue.
> > > > > >>
> > > > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > > > interested
> > > > > >> in hearing from you which way to go.
> > > > > >>
> > > > > >> </partha>
> > > > > > [JRE] I was basing my earlier comment on the fact that the
> > > metadata
> > > > > model seems to indicate that the Media Stream object
> > has CS codec
> > > > > parameters as an attribute. This is indeed questionable.
> > > I seem to
> > > > > remember somebody wanting this at some stage in the
> > past. From my
> > > > point
> > > > > of view, I don't think this information is needed by the
> > > SRS - it is
> > > > > historic information, nothing to do with the media
> > > actually sent to
> > > > the
> > > > > SRS, and of no use to the SRS, in my opinion.
> > > > > >
> > > > > > If people do think there is a reason for providing this
> > > information
> > > > > to the SRS, I don't think I would favour approach 1)
> > > above. The SDP
> > > > > could potentially contain all sorts of information other
> > > than codecs
> > > > > (codecs are only a small part, and the SDP will contain
> > > information
> > > > > like IP addresses, ports, security keys!!!, transport,
> > > non-recorded
> > > > > media descriptions (e.g., MSRP channel, BFCP channel), format
> > > > > parameters, SDP capability negotiation attributes, etc..
> > > > > >
> > > > > > Moreover, the offerer and answerer might have agreed several
> > > codecs
> > > > > in the SDP, so you need to look at RTP to see which codec is
> > > actually
> > > > > used. This can change on the fly.
> > > > > >
> > > > > > Finally, although the SRS's SIP/SDP stack will surely
> > > have and SDP
> > > > > parser, the XML metadata is intended for passing to an
> > > application.
> > > > > Requiring that application to contain an SDP parser is,
> > I think,
> > > > > unreasonable.
> > > > > >
> > > > > > So I have doubts as to whether it is really feasible to
> > > provide CS
> > > > > codec information in metadata to the SRS in a meaningful way,
> > > whether
> > > > > this be using approach 1) or approach 2), but I
> > > particularly dislike
> > > > > approach 1).
> > > > > >
> > > > > > John (as individual)
> > > > > _______________________________________________
> > > > > 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
> >
>

From eckelcu@cisco.com  Thu Mar 17 13:40:55 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 694523A6B06 for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 13:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.572
X-Spam-Level: 
X-Spam-Status: No, score=-10.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cfvezbRV+sG6 for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 13:40:54 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 627A33A6AF0 for <siprec@ietf.org>; Thu, 17 Mar 2011 13:40:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=4475; q=dns/txt; s=iport; t=1300394543; x=1301604143; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=OvPCItUPRt3PHCU9UWPzxpZFyAWDhQYS6xY3jMikIEw=; b=Sbur5Jdjd6VhJwDvJL0LaiSL+mTNIxNJTVFN68iDOgNvke97MDF2s0ng nqIkgbsbBRHrbTePnpzHlrl2mt16rL9pZTziHmdrPvSLGZ6y/vB0vrv1/ 1mdyzb0n6NYiknRSp+sf8d2xeOX4LP+OuTL5tlEHUTzebx2gcqeXYFRls I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjABAHgPgk2tJXG8/2dsb2JhbACYII0xd6clnC2FYwSFL4sC
X-IronPort-AV: E=Sophos;i="4.63,201,1299456000"; d="scan'208";a="668267395"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by sj-iport-6.cisco.com with ESMTP; 17 Mar 2011 20:42:22 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2HKgDYc025916;  Thu, 17 Mar 2011 20:42:22 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Mar 2011 13:31:48 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Mar 2011 13:30:56 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3219@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvjEUSsHcJ38+GcQ7elOYlEMOVDqwAByJ8wAHI6zjA=
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com> <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 17 Mar 2011 20:31:48.0540 (UTC) FILETIME=[571C37C0:01CBE4E2]
Cc: siprec@ietf.org
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 20:40:55 -0000

Please see single comment inline.

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Elwell, John
> Sent: Tuesday, March 15, 2011 6:56 AM
> To: Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Review Request for
draft-ram-siprec-metadata-format-01
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: 15 March 2011 13:03
> > To: Elwell, John
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > On 3/15/2011 7:22 AM, Elwell, John wrote:
> >
> > >>> 2. We perhaps need to think about mixed RS media streams,
> > >> i.e., where several CS media streams have been mixed to
> > >> produce a single RS media stream. In this case, the several
> > >> Media Stream objects would all point to the same SDP label, I
> > >> guess. This then brings into question the mode element (type
> > >> streamMode) - why is this needed? The fact that several Media
> > >> Stream objects (stream elements) point to the same label
> > >> would imply there has been mixing, so the mode element seems
> > >> to be redundant.
> > >>
> > >> My thinking is that situation is modeled as a single media
> > >> stream with
> > >> multiple participants.
> > > [JRE] I was confused by section 4.5 of the metadata model
> > draft. It does indeed seem to say that it represents an RS
> > media stream:
> > > "A Media Stream block shall have properties of media as
> > seen by SRC and sent to SRS."
> > > And hence your interpretation above would seem reasonable.
> > On the other hand, in 4.5.2 it says:
> > > "A Media Stream SHALL be associated with Participant and CS."
> > > This misled me. Also in 4.5.1:
> > > "Codec params - represents codec parameters of the CS media"
> > > This also seemed to imply the Media Stream object relates
> > to a CS media stream.
> > > Perhaps some clarification is needed in the Metadata draft.
> > > Anyway, assuming we go with your interpretation, I suppose
> > what we end up with is that if streams are mixed (whether
> > this be at an MCU, say, or just part of the SRC in order to
> > send the streams to the SRS), the net result will be
> > modelling as a single stream in the metadata. Is this a
> > common understanding?
> >
> > You may have a point here - that things are somewhat ambiguous.
> >
> > If we have two distinct media streams in the CS, and they are mixed
> > together by the SRC before sending to the SRS, then they could be
> > treated different ways:
> >
> > - The SRC could report this as a single media stream with multiple
> > participants. But then it would have to report its metadata as if it
> > were a single stream from a mixer.
> >
> > - The SRC could report it as multiple media streams from a metadata
> > perspective, but map them all onto the same RS media stream.
> > (This is a
> > possibility I had never considered/recognized.)
> >
> > Is there a desire to support both? If so, the metamodel and
mechanism
> > will probably need some tweaking.
> [JRE] Consider:
> "REQ-009: The mechanism MUST support the ability for an SRC to
>    deliver mixed audio streams from different parties of a given
>    Communication Session to an SRS."
> One particular case I believe this covers is the simple 2-party call,
where there are two media
> streams, one from A to B and the other from B to A. The SRC could mix
the two together into a single
> stream to the SRS. Certainly useful for bandwidth constrained
environments, but not so friendly
> towards speech analytics.
>=20
> John (as individual)

Once the stream is mixed meaning all packets have the same SSRC and
CSRC, I think there is no point in trying to represent it as anything
other than a single stream. If the metadata can indicate all the
individual participants in the mixed stream, that would be great, but I
doubt you will get this in all cases.
If it is a single RTP stream with multiple identifiable media streams
muxed together, then it would be good to model as independent streams.
In this case the different streams could be uniquely identified by a
SSRC or CSRC.=20

Cheers,
Charles

>=20
> >
> > 	Thanks,
> > 	Paul
> >
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From fluffy@cisco.com  Thu Mar 17 16:25:59 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D8B93A67AB for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 16:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.405
X-Spam-Level: 
X-Spam-Status: No, score=-109.405 tagged_above=-999 required=5 tests=[AWL=1.194, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NMlgRU31UZVD for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 16:25:57 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id EF9043A6B3C for <siprec@ietf.org>; Thu, 17 Mar 2011 16:25:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=62; q=dns/txt; s=iport; t=1300404444; x=1301614044; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=iuzDwHeTBRQpZ3rvC9FW8B8j1ZKKNJFr90UY1NFNmEw=; b=TTtdDDGVm8EDVqDa3snioxfAZqo+LXKOETBDpIifyTJ6qbVywqH3dKNg VzL24bdfeRWBppn1xgbRT9FnWigMeDgZ3QaOGY4L9YgjNmA/qkqwetsuS 4fCYUlD9tqK14RS4pzdVdbyKBm6EmWTUKHJwrgizwqjAa4E881oRy2xVk g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArkGAN81gk2tJV2b/2dsb2JhbACYYoxzd4hFAZ48nBmFYwSFL4cvg00
X-IronPort-AV: E=Sophos;i="4.63,202,1299456000"; d="scan'208";a="348512036"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by sj-iport-5.cisco.com with ESMTP; 17 Mar 2011 23:27:21 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2HNRLJD019513 for <siprec@ietf.org>; Thu, 17 Mar 2011 23:27:21 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 17 Mar 2011 17:30:12 -0600
Message-Id: <164C0619-A38D-4250-B9EE-AB9681584520@cisco.com>
To: siprec@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Subject: [siprec] drafts in agenda
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 17 Mar 2011 23:25:59 -0000

It seems like more drafts should be listed in the agenda. 


From partr@cisco.com  Thu Mar 17 23:53:39 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A98B3A6ADF for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 23:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.975
X-Spam-Level: 
X-Spam-Status: No, score=-9.975 tagged_above=-999 required=5 tests=[AWL=0.624,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jk7kYYZs9yuv for <siprec@core3.amsl.com>; Thu, 17 Mar 2011 23:53:38 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 696C33A6AD6 for <siprec@ietf.org>; Thu, 17 Mar 2011 23:53:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=5617; q=dns/txt; s=iport; t=1300431306; x=1301640906; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=JAF1IH7mjZvRO7NOJHWo1HtfWmz1R4cIOnlWadQTeSU=; b=J88EssKOekjKlNTzpozSz+79cd9nEy4lpqGikiDZwX9jlBVDGF/XlC6v M/7wJPZl5ocmGE9ycKg5Heht8IiUbfgUw+UeMVKWAjyKx5v9A+5K7ylB7 9BWJsp0fGA3S3VvLNl9XIF8fwl9SaZd2YOyNR8bkZbsZdLzxcsWCjFm9/ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAAGeegk2Q/khMgWdsb2JhbACYNo0xFAEBFiYliE2dX5wMhWMEhS+LCQ
X-IronPort-AV: E=Sophos;i="4.63,204,1299456000"; d="scan'208";a="79741513"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 18 Mar 2011 06:55:05 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2I6t4Th006549; Fri, 18 Mar 2011 06:55:05 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 18 Mar 2011 12:25:05 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 18 Mar 2011 12:25:03 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904CAF275@XMB-BGL-411.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3219@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvjEUSsHcJ38+GcQ7elOYlEMOVDqwAByJ8wAHI6zjAAFRKZAA==
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3219@xmb-sjc-234.amer.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 18 Mar 2011 06:55:05.0000 (UTC) FILETIME=[69232A80:01CBE539]
Cc: siprec@ietf.org
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 06:53:39 -0000

Charles,

Please read inline=20

Thanks
Partha

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Charles Eckel (eckelcu)
Sent: Friday, March 18, 2011 2:01 AM
To: Elwell, John; Paul Kyzivat (pkyzivat)
Cc: siprec@ietf.org
Subject: Re: [siprec] Review Request for
draft-ram-siprec-metadata-format-01

Please see single comment inline.

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Elwell, John
> Sent: Tuesday, March 15, 2011 6:56 AM
> To: Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Review Request for
draft-ram-siprec-metadata-format-01
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: 15 March 2011 13:03
> > To: Elwell, John
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Review Request for
> > draft-ram-siprec-metadata-format-01
> >
> > On 3/15/2011 7:22 AM, Elwell, John wrote:
> >
> > >>> 2. We perhaps need to think about mixed RS media streams,
> > >> i.e., where several CS media streams have been mixed to produce a

> > >> single RS media stream. In this case, the several Media Stream=20
> > >> objects would all point to the same SDP label, I guess. This then

> > >> brings into question the mode element (type
> > >> streamMode) - why is this needed? The fact that several Media=20
> > >> Stream objects (stream elements) point to the same label would=20
> > >> imply there has been mixing, so the mode element seems to be=20
> > >> redundant.
> > >>
> > >> My thinking is that situation is modeled as a single media stream

> > >> with multiple participants.
> > > [JRE] I was confused by section 4.5 of the metadata model
> > draft. It does indeed seem to say that it represents an RS media=20
> > stream:
> > > "A Media Stream block shall have properties of media as
> > seen by SRC and sent to SRS."
> > > And hence your interpretation above would seem reasonable.
> > On the other hand, in 4.5.2 it says:
> > > "A Media Stream SHALL be associated with Participant and CS."
> > > This misled me. Also in 4.5.1:
> > > "Codec params - represents codec parameters of the CS media"
> > > This also seemed to imply the Media Stream object relates
> > to a CS media stream.
> > > Perhaps some clarification is needed in the Metadata draft.
> > > Anyway, assuming we go with your interpretation, I suppose
> > what we end up with is that if streams are mixed (whether this be at

> > an MCU, say, or just part of the SRC in order to send the streams to

> > the SRS), the net result will be modelling as a single stream in the

> > metadata. Is this a common understanding?
> >
> > You may have a point here - that things are somewhat ambiguous.
> >
> > If we have two distinct media streams in the CS, and they are mixed=20
> > together by the SRC before sending to the SRS, then they could be=20
> > treated different ways:
> >
> > - The SRC could report this as a single media stream with multiple=20
> > participants. But then it would have to report its metadata as if it

> > were a single stream from a mixer.
> >
> > - The SRC could report it as multiple media streams from a metadata=20
> > perspective, but map them all onto the same RS media stream.
> > (This is a
> > possibility I had never considered/recognized.)
> >
> > Is there a desire to support both? If so, the metamodel and
mechanism
> > will probably need some tweaking.
> [JRE] Consider:
> "REQ-009: The mechanism MUST support the ability for an SRC to
>    deliver mixed audio streams from different parties of a given
>    Communication Session to an SRS."
> One particular case I believe this covers is the simple 2-party call,
where there are two media
> streams, one from A to B and the other from B to A. The SRC could mix
the two together into a single
> stream to the SRS. Certainly useful for bandwidth constrained
environments, but not so friendly
> towards speech analytics.
>=20
> John (as individual)

Once the stream is mixed meaning all packets have the same SSRC and
CSRC, I think there is no point in trying to represent it as anything
other than a single stream.=20
<Partha> I'm of the same opinion </Partha>

If the metadata can indicate all the individual participants in the
mixed stream, that would be great, but I doubt you will get this in all
cases.=20
<Partha> agreed </Partha>

If it is a single RTP stream with multiple identifiable media streams
muxed together, then it would be good to model as independent streams.
In this case the different streams could be uniquely identified by a
SSRC or CSRC.=20

<Partha> I wish to get more clarity for this scenario. In the mentioned
scenario, whether RFC 5576 ssrc attribute or some other attribute is
used in CS SDP to indicate RTP muxing in m-line. If so, the same
attribute shall be extended for RS session as well. There is no need to
push the information to metadata XML. In case there is no indication of
multiple stream in CS, it is possible that SRC may not able to indicate
explicitly in RS signaling but RTP muxed passed to SRS with different
SSRC or CSRC. </Partha>=20


Cheers,
Charles

>=20
> >
> > 	Thanks,
> > 	Paul
> >
> _______________________________________________
> 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

From john.elwell@siemens-enterprise.com  Fri Mar 18 01:08:51 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 384E53A680D for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 01:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id skRTzCXqd2Ag for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 01:08:50 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id AFD353A66B4 for <siprec@ietf.org>; Fri, 18 Mar 2011 01:08:49 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3791852; Fri, 18 Mar 2011 09:10:17 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 7419723F028E; Fri, 18 Mar 2011 09:10:17 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 18 Mar 2011 09:10:17 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
Date: Fri, 18 Mar 2011 09:10:15 +0100
Thread-Topic: [siprec] Review Request for draft-ram-siprec-metadata-format-01
Thread-Index: AcvjEUSsHcJ38+GcQ7elOYlEMOVDqwAByJ8wAHI6zjAAF8tFkA==
Message-ID: <A444A0F8084434499206E78C106220CA086A964E43@MCHP058A.global-ad.net>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com> <A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3219@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3219@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 08:08:51 -0000

=20

> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]=20
> Sent: 17 March 2011 20:31
> To: Elwell, John; Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Review Request for=20
> draft-ram-siprec-metadata-format-01
>=20
> Please see single comment inline.
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Elwell, John
> > Sent: Tuesday, March 15, 2011 6:56 AM
> > To: Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
> >=20
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > > Sent: 15 March 2011 13:03
> > > To: Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01
> > >
> > > On 3/15/2011 7:22 AM, Elwell, John wrote:
> > >
> > > >>> 2. We perhaps need to think about mixed RS media streams,
> > > >> i.e., where several CS media streams have been mixed to
> > > >> produce a single RS media stream. In this case, the several
> > > >> Media Stream objects would all point to the same SDP label, I
> > > >> guess. This then brings into question the mode element (type
> > > >> streamMode) - why is this needed? The fact that several Media
> > > >> Stream objects (stream elements) point to the same label
> > > >> would imply there has been mixing, so the mode element seems
> > > >> to be redundant.
> > > >>
> > > >> My thinking is that situation is modeled as a single media
> > > >> stream with
> > > >> multiple participants.
> > > > [JRE] I was confused by section 4.5 of the metadata model
> > > draft. It does indeed seem to say that it represents an RS
> > > media stream:
> > > > "A Media Stream block shall have properties of media as
> > > seen by SRC and sent to SRS."
> > > > And hence your interpretation above would seem reasonable.
> > > On the other hand, in 4.5.2 it says:
> > > > "A Media Stream SHALL be associated with Participant and CS."
> > > > This misled me. Also in 4.5.1:
> > > > "Codec params - represents codec parameters of the CS media"
> > > > This also seemed to imply the Media Stream object relates
> > > to a CS media stream.
> > > > Perhaps some clarification is needed in the Metadata draft.
> > > > Anyway, assuming we go with your interpretation, I suppose
> > > what we end up with is that if streams are mixed (whether
> > > this be at an MCU, say, or just part of the SRC in order to
> > > send the streams to the SRS), the net result will be
> > > modelling as a single stream in the metadata. Is this a
> > > common understanding?
> > >
> > > You may have a point here - that things are somewhat ambiguous.
> > >
> > > If we have two distinct media streams in the CS, and they=20
> are mixed
> > > together by the SRC before sending to the SRS, then they could be
> > > treated different ways:
> > >
> > > - The SRC could report this as a single media stream with multiple
> > > participants. But then it would have to report its=20
> metadata as if it
> > > were a single stream from a mixer.
> > >
> > > - The SRC could report it as multiple media streams from=20
> a metadata
> > > perspective, but map them all onto the same RS media stream.
> > > (This is a
> > > possibility I had never considered/recognized.)
> > >
> > > Is there a desire to support both? If so, the metamodel and
> mechanism
> > > will probably need some tweaking.
> > [JRE] Consider:
> > "REQ-009: The mechanism MUST support the ability for an SRC to
> >    deliver mixed audio streams from different parties of a given
> >    Communication Session to an SRS."
> > One particular case I believe this covers is the simple=20
> 2-party call,
> where there are two media
> > streams, one from A to B and the other from B to A. The SRC=20
> could mix
> the two together into a single
> > stream to the SRS. Certainly useful for bandwidth constrained
> environments, but not so friendly
> > towards speech analytics.
> >=20
> > John (as individual)
>=20
> Once the stream is mixed meaning all packets have the same SSRC and
> CSRC, I think there is no point in trying to represent it as anything
> other than a single stream. If the metadata can indicate all the
> individual participants in the mixed stream, that would be=20
> great, but I
> doubt you will get this in all cases.
> If it is a single RTP stream with multiple identifiable media streams
> muxed together, then it would be good to model as independent streams.
> In this case the different streams could be uniquely identified by a
> SSRC or CSRC.=20
[JRE] Yes, that might be a valid case (although I am not sure that CSRC wou=
ld be appropriate). Actually, this is something we haven't considered at al=
l - I will start a separate thread.

John (as individual)

>=20
> Cheers,
> Charles
>=20
> >=20
> > >
> > > 	Thanks,
> > > 	Paul
> > >
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> =

From john.elwell@siemens-enterprise.com  Fri Mar 18 01:09:59 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF4543A67F7 for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 01:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HI18382r6C3F for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 01:09:58 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 26E153A66B4 for <siprec@ietf.org>; Fri, 18 Mar 2011 01:09:57 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3798824 for siprec@ietf.org; Fri, 18 Mar 2011 09:11:26 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 81F4C23F028E for <siprec@ietf.org>; Fri, 18 Mar 2011 09:11:26 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 18 Mar 2011 09:11:26 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Fri, 18 Mar 2011 09:11:24 +0100
Thread-Topic: Multiplexing different participants' streams on the same port
Thread-Index: AcvlRBLrSWbjqO+eTN2hm6ZyFiLojw==
Message-ID: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 08:09:59 -0000

Something Charles mentioned in another thread triggered me to raise this.

We consider different participants in the CS as potentially producing separ=
ate media streams that the SRC sends to the SRS, where the SRC can send the=
m mixed or unmixed.

When sending them unmixed, up till now I think we have considered sending t=
hem to separate ports on the SRS and identifying them as separate m=3D line=
s in the SDP. Another possibility might be to multiplex the different strea=
ms on the same port and identify them by different SSRC values. I am not su=
re whether this would be a correct use of SSRC, and I suspect we would need=
 to check with AVTCORE. Recent discussions in other contexts (telepresence,=
 RTC-Web) have also drawn my attention to such possibilities. See also http=
s://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.

Of course, it would mean that we would have to rethink how we reference the=
 different streams from metadata.

I am not necessarily proposing such a change - I just want to make sure we =
have given it due consideration.

John (as individual)

 =

From srao@ctigroup.com  Fri Mar 18 03:32:33 2011
Return-Path: <srao@ctigroup.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B19283A68F4 for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 03:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4s0WT0vmZen7 for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 03:32:32 -0700 (PDT)
Received: from EXCHANGE2K3.ctigroup.com (etomernpv.ctigroup.com [64.132.87.194]) by core3.amsl.com (Postfix) with ESMTP id C0E3D3A68C9 for <siprec@ietf.org>; Fri, 18 Mar 2011 03:32:32 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 18 Mar 2011 06:33:57 -0400
Message-ID: <B03E298DC8DFC143A7584C166773CBF903A26A63@EXCHANGE2K3.ctigroup.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Multiplexing different participants' streams on the same port
Thread-Index: AcvlRBLrSWbjqO+eTN2hm6ZyFiLojwAE6lMQ
From: "Sid Rao" <srao@ctigroup.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
Subject: Re: [siprec] Multiplexing different participants' streams on the sameport
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 10:32:33 -0000

Just out of curiosity, apart from the extra socket this saves, what are
the actual technical drivers for such a solution?

Sid Rao

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Elwell, John
Sent: Friday, March 18, 2011 4:11 AM
To: siprec@ietf.org
Subject: [siprec] Multiplexing different participants' streams on the
sameport

Something Charles mentioned in another thread triggered me to raise
this.

We consider different participants in the CS as potentially producing
separate media streams that the SRC sends to the SRS, where the SRC can
send them mixed or unmixed.

When sending them unmixed, up till now I think we have considered
sending them to separate ports on the SRS and identifying them as
separate m=3D lines in the SDP. Another possibility might be to =
multiplex
the different streams on the same port and identify them by different
SSRC values. I am not sure whether this would be a correct use of SSRC,
and I suspect we would need to check with AVTCORE. Recent discussions in
other contexts (telepresence, RTC-Web) have also drawn my attention to
such possibilities. See also
https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.

Of course, it would mean that we would have to rethink how we reference
the different streams from metadata.

I am not necessarily proposing such a change - I just want to make sure
we have given it due consideration.

John (as individual)

=20
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

From partr@cisco.com  Fri Mar 18 03:39:11 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A06ED3A68C9 for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 03:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.99
X-Spam-Level: 
X-Spam-Status: No, score=-9.99 tagged_above=-999 required=5 tests=[AWL=0.609,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7N561ryqJoWB for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 03:39:10 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 656DC3A6AFE for <siprec@ietf.org>; Fri, 18 Mar 2011 03:39:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=2966; q=dns/txt; s=iport; t=1300444840; x=1301654440; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=SKTEpMBSAb/4UCt8FDMRkAmSINT1FqOGbPc5TvLvc5M=; b=Ljd4HK1j2w9zTTpKvBhCRsECG2t5oe3P5yTAAKIguSf7eFEfwPQM6hjT 9DuYS0EeqwefrUQMP72fDBMO+WS07ULNnjBnXb+SuslEj7qbWj91aQyRA BiIP+3GMWpXqTcHIySz2E2ktOdh+B1OSQ9xW+j3zljG0FSpGkCQ0Ace7Z s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAACLTgk2Q/khNgWdsb2JhbACYNo0xFAEBFiYlplKcDoJ7gmgEhS+LCQ
X-IronPort-AV: E=Sophos;i="4.63,204,1299456000"; d="scan'208";a="79780035"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 18 Mar 2011 10:40:38 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2IAeawY002426; Fri, 18 Mar 2011 10:40:38 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 18 Mar 2011 16:10:38 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 18 Mar 2011 16:10:36 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904CAF346@XMB-BGL-411.cisco.com>
In-Reply-To: <B03E298DC8DFC143A7584C166773CBF903A26A63@EXCHANGE2K3.ctigroup.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Multiplexing different participants' streams on thesameport
Thread-Index: AcvlRBLrSWbjqO+eTN2hm6ZyFiLojwAE6lMQAAAxsRA=
References: <B03E298DC8DFC143A7584C166773CBF903A26A63@EXCHANGE2K3.ctigroup.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Sid Rao" <srao@ctigroup.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>,  "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
X-OriginalArrivalTime: 18 Mar 2011 10:40:38.0320 (UTC) FILETIME=[EB9FEB00:01CBE558]
Subject: Re: [siprec] Multiplexing different participants' streams on thesameport
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 10:39:11 -0000

John/Charles,

To make my query in the single thread, I'm re-posting my earlier
question here:

"I wish to get more clarity for this scenario. In the mentioned
scenario, whether RFC 5576 ssrc attribute or some other attribute is
used in CS SDP to indicate RTP muxing in m-line. If so, the same
attribute shall be extended for RS session as well. There is no need to
push the information to metadata XML. In case there is no indication of
multiple stream in CS, it is possible that SRC may not able to indicate
explicitly in RS signaling but RTP muxed passed to SRS with different
SSRC or CSRC."

Thanks
Partha=20
=20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Sid Rao
Sent: Friday, March 18, 2011 4:04 PM
To: Elwell, John; siprec@ietf.org
Subject: Re: [siprec] Multiplexing different participants' streams on
thesameport

Just out of curiosity, apart from the extra socket this saves, what are
the actual technical drivers for such a solution?

Sid Rao

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Elwell, John
Sent: Friday, March 18, 2011 4:11 AM
To: siprec@ietf.org
Subject: [siprec] Multiplexing different participants' streams on the
sameport

Something Charles mentioned in another thread triggered me to raise
this.

We consider different participants in the CS as potentially producing
separate media streams that the SRC sends to the SRS, where the SRC can
send them mixed or unmixed.

When sending them unmixed, up till now I think we have considered
sending them to separate ports on the SRS and identifying them as
separate m=3D lines in the SDP. Another possibility might be to =
multiplex
the different streams on the same port and identify them by different
SSRC values. I am not sure whether this would be a correct use of SSRC,
and I suspect we would need to check with AVTCORE. Recent discussions in
other contexts (telepresence, RTC-Web) have also drawn my attention to
such possibilities. See also
https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.

Of course, it would mean that we would have to rethink how we reference
the different streams from metadata.

I am not necessarily proposing such a change - I just want to make sure
we have given it due consideration.

John (as individual)

=20
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From partr@cisco.com  Fri Mar 18 04:20:22 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 672C63A68AA for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 04:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.854
X-Spam-Level: 
X-Spam-Status: No, score=-8.854 tagged_above=-999 required=5 tests=[AWL=-0.555, BAYES_00=-2.599, MANGLED_FORM=2.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0l4C7e0DhcrW for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 04:20:20 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id C9BB03A6870 for <siprec@ietf.org>; Fri, 18 Mar 2011 04:20:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=23744; q=dns/txt; s=iport; t=1300447308; x=1301656908; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=0Azs98HPRtb6NtYKH/GHRD4yZ3VlHiFYbObxDdg2vN8=; b=S8AMDf0Q2SP8GCbFLc/emcDzZpYjMUGUECgM4pfz+L6ufmn/eyPngOUq wHjcTnMLRQ6hXdMS0XK7nI572TdcYL3AURBMx7ELl8p9Oqa0SMGiPr9KE 3ZAareAOvSm8HIpU33ZsPcQdWwmt9CFaIfwWln+Oo3zyFKoxOPL3DkVBX I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAAL7cgk2Q/khLgWdsb2JhbACYNo0xFAEBFiYliE2daZwHgnuCaASFL4sJ
X-IronPort-AV: E=Sophos;i="4.63,204,1299456000"; d="scan'208";a="79786718"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 18 Mar 2011 11:21:46 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2IBKxq6007123; Fri, 18 Mar 2011 11:21:46 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 18 Mar 2011 16:51:27 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 18 Mar 2011 16:51:25 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904CAF369@XMB-BGL-411.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A9491A69@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
Thread-Index: Acvj3snlsxhEMaLcQ0q1pHz03nfU7wAEZWXgACAtC6AAAEl4UAAAK/fQAAC1cUAABTHCIAAA3ufgAAH1vbAAAJh80AAD7KzgAAGCawAAKvZ2AA==
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6AA@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A964472@MCHP058A.global-ad.net><4D80BC11.206@cisco.com><07465C1D981ABC41A344374066AE1A2C38A94915C9@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B54F@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491700@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD05B8B569@XMB-BGL-417.cisco.com><07465C1D981ABC41A344374066AE1A2C38A9491733@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA086A9649F5@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A623904CAEFE1@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964A62@MCHP058A.g lobal-a d	.net> <A11 921905DA1564D9BCF64A6430A623904CAF00E@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A964B5D@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A9491A69@TLVMBX01.nice.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
X-OriginalArrivalTime: 18 Mar 2011 11:21:27.0226 (UTC) FILETIME=[9F4951A0:01CBE55E]
Cc: siprec@ietf.org
Subject: Re: [siprec] CS Codec Parameter in stream XML element [was RE: Review Request for draft-ram-siprec-metadata-format-01]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 11:20:22 -0000

Till now, we didn't hear for any use case which requires CS SDP
parameters. IMO, We will wait till 23rd Mar to identify any CS SDP
parameter is required to be passed across in metadata. Pls mention in
case more time is required to close CS SDP parameter issue.=20

In case there is no use case identified till that time, we will update
Sec 4.5.1 3rd Bullet of draft-ram-siprec-metadata as "Codec params -
represents codec parameters of RS media" in the next revision. Pls
suggest in case text has to be modified.

Apart from this, there is another issue associated in this mail thread.
John mentioned about some of the RS SDP attributes has to be duplicated
in metadata XML namely Content (RFC 4796), Mediatype (audio/video). Paul
wishes to analysis more on direction attribute to passed in XML. I doubt
that Charles is looking for RTP MUX information (RFC 5576) in XML
instead of SDP based on the another mail thread "Multiplexing different
participants' streams on the same port". I'm of the opinion that it is
better to be passed in RS SDP rather than in metadata XML because of the
following reasons:=20

1) It avoids duplication of data in the single message
2) All SDP extended attributes (like fmtp for video, ssrc for RTP
muxing, content for exact content type) will be reused in Recording
session without any change
3) Also provides the way to extend any new attributes comes in SDP
attribute without impact metadata general format.=20
4) In case duplication of attribute is allowed, creating the proper
demarcation whether the specific attribute falls under Metadata XML or
RS SDP will not be clear.

I wish to discuss more on this front in this mail thread.

Thanks
Partha
=20

-----Original Message-----
From: Leon Portman [mailto:Leon.Portman@nice.com]=20
Sent: Thursday, March 17, 2011 7:47 PM
To: Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmohanr); Paul
Kyzivat (pkyzivat)
Cc: siprec@ietf.org
Subject: RE: [siprec] CS Codec Parameter in stream XML element [was RE:
Review Request for draft-ram-siprec-metadata-format-01]


I completely agree with John's points below. What is important is RS
codec info and not CS.

Leon
-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
Sent: Thursday, March 17, 2011 4:03 PM
To: Parthasarathi R (partr); Leon Portman; Ram Mohan R (rmohanr); Paul
Kyzivat (pkyzivat)
Cc: siprec@ietf.org
Subject: RE: [siprec] CS Codec Parameter in stream XML element [was RE:
Review Request for draft-ram-siprec-metadata-format-01]



> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 17 March 2011 12:30
> To: Elwell, John; Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat
> (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE: Review Request for draft-ram-siprec-metadata-format-01]
>
> John,
>
> Please read inline.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 17, 2011 5:08 PM
> To: Parthasarathi R (partr); Leon Portman; Ram Mohan R (rmohanr); Paul

> Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> RE:
> Review Request for draft-ram-siprec-metadata-format-01]
>
> Partha,
>
> Approach 1 is fine, as far as representation of start/stop times is=20
> concerned.
>
> So if I understand correctly the unrecordable / unrecorded stream=20
> appears in both XML metadata and SDP, with XML containing the=20
> start/stop times and SDP containing the media type/content. So an SDP=20
> media description would exist for:
> - recorded streams;
> - streams offered by the SRC for recording but rejected by the SRS;
> - streams not offered by the SRC (unrecordable streams).
>
> The first one is fine and the second one we can't really avoid. I am=20
> rather uncomfortable about the third one, where there is an SDP media=20
> description describing a stream that does not exist in the RS. It=20
> clutters the SDP unnecessarily and I feel it is worthwhile having some

> minimal duplication (in XML and SDP) for recorded streams to avoid=20
> this addition to SDP for unrecordable streams.
>
> <Partha> I know of real audio end points (IP phones) which starts with

> "m" line having port 0 during the dialog creation stage and then add=20
> the appropriate port in the mid-dialog. Leon may be talking about one=20
> such video phone. AFAIK, "m" line having port 0 in the offer is not=20
> violating any of the RFC. So, those endpoint which creates CS with "m"
> line having
> port 0 during dialog creation shall map its RS dialog creation SDP=20
> with port 0 for "m" line  as well.
>
> It is upto SRS to record/store those metadata or not. Please let me=20
> know in case I'm missing something. </Partha>
[JRE] I agree it is valid SDP - I am just uncomfortable with the SRC
offering something that it doesn't even intend to use in the future.
Normally a port 0 m-line in the initial offer implies a medium that
might be turned on later, but I may be wrong.

>
> I also feel that media type and content description are logically part

> of the metadata and should appear in XML, because this is information=20
> the application needs.
>
> <Partha> IMO, the minimum required codec parameters for metadata in=20
> XML will easily grow till little bit less than complete SDP. For=20
> example, it is not required to pass crypto key or some other=20
> parameters.
> Some of the
> possible to be passed across are:
>
> 1)Direction attribute - To find the original direction attribute of CS

> (I explained the way to retrieve from RS SDP)
>
> 2)Codec - Finding CS codec in Transcoding scenario
[JRE] I don't see why this is relevant - I don't think we have a
requirement. Also, even if CS codec information is made available to the
SRS, this is only the CS codec as seen by the SRC, and perhaps other
codecs were used upstream that are not visible to the SRC. For example,
Remote party A transmits audio using G.723 to a mixer, and party B
transmits audio using G.711 to the mixer. The mixer then transmits audio
using OPUS super-wideband to party C, and the SRC is located at C's UA
(or on the path between the mixer and C's UA). The SRC uses G.722, say,
to send audio to the SRS and reports that the CS used OPUS
super-wideband. What can the SRS learn from this? The audio quality will
be constrained by the worst link, i.e., G.723 when A is talking.

>
> 3)ptime - Finding CS packetization time in Transrating scenario
[JRE] I don't think CS ptime is relevant. Also pTime doesn't give actual
packetization time, which can vary during the session..

>
> 4)content -  To find the exact content description attribute
>
> 5)media type -  Exact media type of CS.
>
> 6)fmtp - This attribute plays vital role in video endpoints CS
[JRE] Again I don't see the relevance of particular formats used on the
CS. By the time media reaches the SRS, it has been reformatted in
accordance with fmtp parameters for the RS (and in some cases mixed with
other streams at the SRC before sending to the SRS) so I really don't
see how knowledge of the fmtp parameters used on the CS can help the SRC
(with analysing the media, say).

>
> 7)bandwidth - To find the exact bandwidth used in Video scenario. Some

> QOS parameter may be used.
[JRE] Again I don't see the relevance.

>
> There should be a way to extend in case new attribute has to be added=20
> in XML which may fall under extensiondata itself. It was the reason=20
> that I proposed to pass SDP within XML earlier in codec parameter has=20
> to be passed in XML. As Leon mentioned, it is possible to pass the=20
> whole SDP through XML using content element of XML which will be seen=20
> as SIPREC extensiondata in CS.
[JRE] I agree with extensibility, and if there are future requirements
to send any of this information in XML, we could do that. But I fail to
see any motivation for defining these now. Also, as explained before, I
am uncomfortable about encapsulating CS SDP within XML metadata.

John (as individual)


>
> In case you foresee that this parameter has to be discussed in detail=20
> to find the selective SDP attribute passing between SRC and SRS, I'll=20
> add in the open item for metadata format draft, Let us discuss in=20
> IETF-80 meeting.
> </partha>
>
> SDP, on the other hand, is something the media engine needs in order=20
> to receive media correctly and pass the received media in some form up

> to the application for storage.
>
> John (as individual)
>
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > Sent: 17 March 2011 11:13
> > To: Elwell, John; Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat
> > (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] CS Codec Parameter in stream XML element [was
> > RE: Review Request for draft-ram-siprec-metadata-format-01]
> >
> > John,
> >
> > I agree that your proposal will work. I'm trying to find few other=20
> > alternatives without duplication of data between SDP and XML.
> >
> > Approach 1: start-time and stop-time are optional XML element in=20
> > stream.
> > In the mentioned scenario, let stream element contains only label=20
> > element and no start & stop time elements which indicates
> that stream
> > is never activated within the given session.
> >
> > XML format for start-time & stop-time:
> >          <xs:element name=3D"start-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >          <xs:element name=3D"stop-time" type=3D"xs:dateTime"
> >                 minOccurs=3D"0"/>
> >
> > Approach 2: Add both start-time and stop-time in the same
> stream which
>
> > indicates that stream is not started.
> >
> > I prefer approach 1 which will solve the issue without
> duplication of
> > metadata in XML. Please let me know your opinion here.
> >
> > Leon,
> >
> > Please read inline.
> >
> > Thanks
> > Partha
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> > Sent: Thursday, March 17, 2011 3:44 PM
> > To: Leon Portman; Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat)
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] CS Codec Parameter in stream XML element [was
> > RE:
> > Review Request for draft-ram-siprec-metadata-format-01]
> >
> > I think in these sort of situations it would be better to
> report the
> > non-recorded video stream in XML metadata. If the SRC uses
> an m-line
> > with port=3D0 to indicate start of an unrecordable video
> stream, I don't
>
> > see how the SRC can report the end of that unrecordable
> video stream
> > in SDP. XML seems a better option.
> >
> > Let me make a proposal. For each Media Stream in XML, attributes=20
> > should
> > indicate:
> > - The type of medium (audio, video,...).
> > - The content type of the medium (c.f., RFC 4796) if
> applicable, e.g.,
>
> > slides, speaker...
> > - The SDP label for that medium (absent if the SRC does not
> offer it
> > for recording).
> >
> > Yes, I know the first two items would be duplication of SDP
> (in cases
> > where the medium is offered for recording), but these two
> items would
> > be particularly useful in cases where the medium is not offered for=20
> > recording and therefore not in the SDP.
> >
> > John (as individual)
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 17 March 2011 07:36
> > > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > > RE: Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Regarding information, most basic one is when video started
> > and ended.
> >
> > <Partha> In the mentioned scenario, video is never started. Hope=20
> > Approach 1 serve your purpose </Partha>
> > >
> > > What about the configuration where SRC knows about video
> > (because it
> > > is inside CS SIP session) but is not able to fork video. Is
> > it still
> > > should offer video m-line?
> > >
> > <Partha> It is upto SRC to decide whether to indicate the
> m-line in RS
>
> > or not. The decision may be based on the SRC level support
> for video
> > recording, policy in the SRC to record video or not. IMO, it is=20
> > implementation specific and SIPREC solution SHOULD be
> flexible for all
>
> > kinds of SRC </partha>
> >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > > Sent: Thursday, March 17, 2011 9:26 AM
> > > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> element [was
> > > RE: Review Request for draft-ram-siprec-metadata-format-01]
> > >
> > > Inline
> > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: Thursday, March 17, 2011 12:43 PM
> > > > To: Ram Mohan R (rmohanr); Paul Kyzivat (pkyzivat); Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > Hi
> > > >
> > > > I agree that if SRS need something from SDP it will be
> > > better to pass
> > > > it via metadata extensions. I did some additional checks
> > > and currently
> > > > there is no such requirement from SRS point of view.
> > > > Regarding video, there was requirement to report video
> > > session even if
> > > > it is not recorded.  And if it is recorded then all relevant=20
> > > > information will be reported via RS SDP such as positions,
> > > sizes etc.
> > >
> > > For cases where Video is not recorded, there are two
> possibilities:
> > > 1) Video is offered by SRC in RS SDP to SRS but SRS choose
> > to reject
> > > video. In this case SRC can still continue to send updates
> > via RS SDP
> > > to SRS.
> > >
> > > 2) SRC may not have capability to record video and may not
> > offer video
> >
> > > to SRS in RS SDP.  In this case also we can send a offer
> (m=3D0) from
> > > SRC to SRS having video information.
> > >
> > >  My question here is - what information do we see a need to
> > report ?
> > > Is it just the information that video is part of CS or more
> > than that
> > > ?
> > >
> > > Ram
> > >
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: Ram Mohan R (rmohanr) [mailto:rmohanr@cisco.com]
> > > > Sent: Thursday, March 17, 2011 9:06 AM
> > > > To: Leon Portman; Paul Kyzivat (pkyzivat); Elwell, John
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] CS Codec Parameter in stream XML
> > element [was
> > > RE:
> > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > >
> > > > Hi Leon / All,
> > > >
> > > > See inline for my comments
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On
> > > > > Behalf Of Leon Portman
> > > > > Sent: Wednesday, March 16, 2011 9:16 PM
> > > > > To: Paul Kyzivat (pkyzivat); Elwell, John
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > > element [was
> > > > RE:
> > > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > > >
> > > > > I agree with points below that passing actual CS SDP to
> > > SRS is a not
> > > > > good idea from security and layers separation point of view.
> > > > > Today's SRS implementations(at least that I know about)
> > > do not keep
> > > > > original codec information in the database for later
> > > retrieval. I am
> > > > > trying to think about use cases why SRS can be
> > interested in one,
> > > and
> > > > > except troubleshooting it is not very relevant.
> > > > >
> > > > > The main assumption is that SRC inspected CS SDP and
> > > extracted all
> > > > > relevant information like ip addresses, media line labels
> > > and infos
> > > > and
> > > > > reported it to SRS via metadata.
> > > >
> > > > Are you still suggesting here that we pass across some of the=20
> > > > parameters of CS SDP that you mentioned above to SRS via
> > metadata ?
> > > Are
> > > > there any applications at SRS which may require this
> information ?
> > > >
> > > > I vaguely remember during IETF 79 presentation that some
> > > folks (mainly
> > > > from video perspective) were asking for part of information
> > > related to
> > > > CS SDP to be passed in metadata. But not too sure about the
> > > use cases
> > > > for the same.
> > > > I would request people on the mailer list to speak up if
> > > there are any
> > > > use cases.
> > > >
> > > >
> > > > IMO if there is only some specific SRS applications that
> > need this,
> > > > it's better to pass it as extension data rather than
> having it as
> > > > attribute of MS block in the metadata.
> > > >
> > > >
> > > > Regards,
> > > > Ram
> > > >
> > > > >
> > > > > The main reason as I see if we want to be able to report
> > > CS SDP via
> > > > > metadata is for the case where SRS wants to sniff RS
> > RTP packets
> > > > > directly and not by forking from SRC but it is out of scope.
> > > > >
> > > > > Leon
> > > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On
> > > > > Behalf Of Paul Kyzivat
> > > > > Sent: Wednesday, March 16, 2011 3:33 PM
> > > > > To: Elwell, John
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] CS Codec Parameter in stream XML
> > > element [was
> > > > RE:
> > > > > Review Request for draft-ram-siprec-metadata-format-01]
> > > > >
> > > > > I believe the codec parameters on the MS have been
> > there since my
> > > > first
> > > > > cut at the metadata model. Putting them there was just
> > speculation
> > > on
> > > > > my part, and doesn't imply any actual need known to me.
> > > > >
> > > > > If nobody feels they are necessary, then by all means
> > remove them.
> > > > >
> > > > >         Thanks,
> > > > >         Paul
> > > > >
> > > > > On 3/16/2011 3:34 AM, Elwell, John wrote:
> > > > > >
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > > > > >> Sent: 16 March 2011 01:25
> > > > > >> To: Elwell, John; Paul Kyzivat (pkyzivat)
> > > > > >> Cc: siprec@ietf.org
> > > > > >> Subject: CS Codec Parameter in stream XML element [was RE:
> > > > > >> [siprec] Review Request for
> > > draft-ram-siprec-metadata-format-01]
> > > > > >>
> > > > > > <snip/>
> > > > > >> <Partha>  It is the assumption done during metadata
> > format that
> > > RS
> > > > > >> SDP may be used as Codec params for stream. Please
> note that
> > > > format
> > > > > >> draft does not have codec param in stream metadata
> > element. But
> > > > the
> > > > > >> assumption does not seems to be working for all
> > > scenarios. So we
> > > > > need
> > > > > >> to find the way to represent CS Media stream in
> > > metadata format.
> > > > > >>
> > > > > >> Even before going into approach, I'm interested in knowing
> > > whether
> > > > > it
> > > > > >> is required for SRS to understand the exact codec or SDP
> > > parameter
> > > > > >> used in CS? RS may be transcoded/transrated and lost
> > the actual
> > > > > media
> > > > > >> information when it reaches SRS but the question is
> > > whether it is
> > > > > >> required to maintain the metadata in SRS even though
> > > media (RTP)
> > > > is
> > > > > >> changed to new format ?
> > > > > >>
> > > > > >> In case we decide to pass CS codec parameter to SRS. Two
> > > > approaches
> > > > > >> exist to solve this issue:
> > > > > >>
> > > > > >> 1) Tunnel complete each participant SDP inside
> stream element
> > > > using
> > > > > >> some new optional XML element. This approach is
> > straightforward
> > > > and
> > > > > >> scale for any CS as we are sending the complete set.
> > > The overhead
> > > > > >> will be increased in SRS to parse and store appropriately.
> > > > > >>
> > > > > >> 2) Identify the list of codec parameters *MUST*  be
> > passed from
> > > > SRC
> > > > > >> to SRS and create the new XML element for them. This
> > > is simple to
> > > > > >> implement as only portion of the SDP is passed
> > across but *may*
> > > > have
> > > > > >> scalability issue.
> > > > > >>
> > > > > >> I prefer 1st approach because it covers all scenarios. I'm
> > > > > interested
> > > > > >> in hearing from you which way to go.
> > > > > >>
> > > > > >> </partha>
> > > > > > [JRE] I was basing my earlier comment on the fact that the
> > > metadata
> > > > > model seems to indicate that the Media Stream object
> > has CS codec
> > > > > parameters as an attribute. This is indeed questionable.
> > > I seem to
> > > > > remember somebody wanting this at some stage in the
> > past. From my
> > > > point
> > > > > of view, I don't think this information is needed by the
> > > SRS - it is
> > > > > historic information, nothing to do with the media
> > > actually sent to
> > > > the
> > > > > SRS, and of no use to the SRS, in my opinion.
> > > > > >
> > > > > > If people do think there is a reason for providing this
> > > information
> > > > > to the SRS, I don't think I would favour approach 1)
> > > above. The SDP
> > > > > could potentially contain all sorts of information other
> > > than codecs
> > > > > (codecs are only a small part, and the SDP will contain
> > > information
> > > > > like IP addresses, ports, security keys!!!, transport,
> > > non-recorded
> > > > > media descriptions (e.g., MSRP channel, BFCP channel), format=20
> > > > > parameters, SDP capability negotiation attributes, etc..
> > > > > >
> > > > > > Moreover, the offerer and answerer might have agreed several
> > > codecs
> > > > > in the SDP, so you need to look at RTP to see which codec is
> > > actually
> > > > > used. This can change on the fly.
> > > > > >
> > > > > > Finally, although the SRS's SIP/SDP stack will surely
> > > have and SDP
> > > > > parser, the XML metadata is intended for passing to an
> > > application.
> > > > > Requiring that application to contain an SDP parser is,
> > I think,
> > > > > unreasonable.
> > > > > >
> > > > > > So I have doubts as to whether it is really feasible to
> > > provide CS
> > > > > codec information in metadata to the SRS in a meaningful way,
> > > whether
> > > > > this be using approach 1) or approach 2), but I
> > > particularly dislike
> > > > > approach 1).
> > > > > >
> > > > > > John (as individual)
> > > > > _______________________________________________
> > > > > 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
> >
>

From pkyzivat@cisco.com  Fri Mar 18 05:29:33 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E6B03A68ED for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 05:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.54
X-Spam-Level: 
X-Spam-Status: No, score=-110.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5Jo52uXVd9P for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 05:29:32 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 045AD3A68D3 for <siprec@ietf.org>; Fri, 18 Mar 2011 05:29:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=5963; q=dns/txt; s=iport; t=1300451461; x=1301661061; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=b28OXiRcGOh3Q/fDZTAmm0QkcBMo9bkxB+JMUbDYqIA=; b=V+Jb8mEoIGDgS9baNP0cbjtBBzzA+7le3hYTYrJV4fiTaEtTGGZj4KZZ tDXjW42OHm3ik0r0qgLa7tQPwR/1PSghl25RE2Zed8KD/FtMYmaBOdf/L Xdu5gPxrRYvDrOJHj6zWrHJHput2cDlvxvTTh3SglTUZXcxVP0GwuohIy 4=;
X-IronPort-AV: E=Sophos;i="4.63,205,1299456000"; d="scan'208";a="279552016"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by sj-iport-3.cisco.com with ESMTP; 18 Mar 2011 12:30:53 +0000
Received: from [161.44.174.126] (dhcp-161-44-174-126.cisco.com [161.44.174.126]) by rcdn-core2-5.cisco.com (8.14.3/8.14.3) with ESMTP id p2ICUrrT020691;  Fri, 18 Mar 2011 12:30:53 GMT
Message-ID: <4D83507C.2010403@cisco.com>
Date: Fri, 18 Mar 2011 08:30:52 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Parthasarathi R (partr)" <partr@cisco.com>
References: <A11921905DA1564D9BCF64A6430A623904B1E134@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086A89AD0A@MCHP058A.global-ad.net><4D7A6898.1060809@cisco.com><A444A0F8084434499206E78C106220CA086A89B579@MCHP058A.global-ad.net><4D7F636F.5060105@cisco.com><A444A0F8084434499206E78C106220CA086A89B6E7@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3219@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904CAF275@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904CAF275@XMB-BGL-411.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: siprec@ietf.org
Subject: Re: [siprec] Review Request for draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 12:29:33 -0000

ISTM the issue with a mixed stream with separate SSRC values is 
correlating the SSRC values to the signaling identities (URIs) of the 
participants. AFAIK there are currently no specifications for doing that.

	Thanks,
	Paul

On 3/18/2011 2:55 AM, Parthasarathi R (partr) wrote:
> Charles,
>
> Please read inline
>
> Thanks
> Partha
>
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
> Of Charles Eckel (eckelcu)
> Sent: Friday, March 18, 2011 2:01 AM
> To: Elwell, John; Paul Kyzivat (pkyzivat)
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>
> Please see single comment inline.
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Elwell, John
>> Sent: Tuesday, March 15, 2011 6:56 AM
>> To: Paul Kyzivat (pkyzivat)
>> Cc: siprec@ietf.org
>> Subject: Re: [siprec] Review Request for
> draft-ram-siprec-metadata-format-01
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>>> Sent: 15 March 2011 13:03
>>> To: Elwell, John
>>> Cc: siprec@ietf.org
>>> Subject: Re: [siprec] Review Request for
>>> draft-ram-siprec-metadata-format-01
>>>
>>> On 3/15/2011 7:22 AM, Elwell, John wrote:
>>>
>>>>>> 2. We perhaps need to think about mixed RS media streams,
>>>>> i.e., where several CS media streams have been mixed to produce a
>
>>>>> single RS media stream. In this case, the several Media Stream
>>>>> objects would all point to the same SDP label, I guess. This then
>
>>>>> brings into question the mode element (type
>>>>> streamMode) - why is this needed? The fact that several Media
>>>>> Stream objects (stream elements) point to the same label would
>>>>> imply there has been mixing, so the mode element seems to be
>>>>> redundant.
>>>>>
>>>>> My thinking is that situation is modeled as a single media stream
>
>>>>> with multiple participants.
>>>> [JRE] I was confused by section 4.5 of the metadata model
>>> draft. It does indeed seem to say that it represents an RS media
>>> stream:
>>>> "A Media Stream block shall have properties of media as
>>> seen by SRC and sent to SRS."
>>>> And hence your interpretation above would seem reasonable.
>>> On the other hand, in 4.5.2 it says:
>>>> "A Media Stream SHALL be associated with Participant and CS."
>>>> This misled me. Also in 4.5.1:
>>>> "Codec params - represents codec parameters of the CS media"
>>>> This also seemed to imply the Media Stream object relates
>>> to a CS media stream.
>>>> Perhaps some clarification is needed in the Metadata draft.
>>>> Anyway, assuming we go with your interpretation, I suppose
>>> what we end up with is that if streams are mixed (whether this be at
>
>>> an MCU, say, or just part of the SRC in order to send the streams to
>
>>> the SRS), the net result will be modelling as a single stream in the
>
>>> metadata. Is this a common understanding?
>>>
>>> You may have a point here - that things are somewhat ambiguous.
>>>
>>> If we have two distinct media streams in the CS, and they are mixed
>>> together by the SRC before sending to the SRS, then they could be
>>> treated different ways:
>>>
>>> - The SRC could report this as a single media stream with multiple
>>> participants. But then it would have to report its metadata as if it
>
>>> were a single stream from a mixer.
>>>
>>> - The SRC could report it as multiple media streams from a metadata
>>> perspective, but map them all onto the same RS media stream.
>>> (This is a
>>> possibility I had never considered/recognized.)
>>>
>>> Is there a desire to support both? If so, the metamodel and
> mechanism
>>> will probably need some tweaking.
>> [JRE] Consider:
>> "REQ-009: The mechanism MUST support the ability for an SRC to
>>     deliver mixed audio streams from different parties of a given
>>     Communication Session to an SRS."
>> One particular case I believe this covers is the simple 2-party call,
> where there are two media
>> streams, one from A to B and the other from B to A. The SRC could mix
> the two together into a single
>> stream to the SRS. Certainly useful for bandwidth constrained
> environments, but not so friendly
>> towards speech analytics.
>>
>> John (as individual)
>
> Once the stream is mixed meaning all packets have the same SSRC and
> CSRC, I think there is no point in trying to represent it as anything
> other than a single stream.
> <Partha>  I'm of the same opinion</Partha>
>
> If the metadata can indicate all the individual participants in the
> mixed stream, that would be great, but I doubt you will get this in all
> cases.
> <Partha>  agreed</Partha>
>
> If it is a single RTP stream with multiple identifiable media streams
> muxed together, then it would be good to model as independent streams.
> In this case the different streams could be uniquely identified by a
> SSRC or CSRC.
>
> <Partha>  I wish to get more clarity for this scenario. In the mentioned
> scenario, whether RFC 5576 ssrc attribute or some other attribute is
> used in CS SDP to indicate RTP muxing in m-line. If so, the same
> attribute shall be extended for RS session as well. There is no need to
> push the information to metadata XML. In case there is no indication of
> multiple stream in CS, it is possible that SRC may not able to indicate
> explicitly in RS signaling but RTP muxed passed to SRS with different
> SSRC or CSRC.</Partha>
>
>
> Cheers,
> Charles
>
>>
>>>
>>> 	Thanks,
>>> 	Paul
>>>
>> _______________________________________________
>> 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
>

From pkyzivat@cisco.com  Fri Mar 18 05:36:53 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C5B13A68ED for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 05:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.54
X-Spam-Level: 
X-Spam-Status: No, score=-110.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5SIs3Flnu-Y3 for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 05:36:52 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 6C0713A68D3 for <siprec@ietf.org>; Fri, 18 Mar 2011 05:36:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=1821; q=dns/txt; s=iport; t=1300451902; x=1301661502; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=u9hrkHumEb1P09KuFE0z8E+5ofkjTVOf2Ij+iGiAZHs=; b=MOWF8Ir2JctwitbSQJ3+P0O0Vc3kccZlPvn0aCJGCsHRbuQCl2p9+rEq /60SkWUK6kQKf+MYSUhAMoMM8p9+1t+qdIzGjJJXaMgqC+cflNA9S402P 4fez1LNf8paLUyPsjoHIh43SfNp7sCccguwbkox1Bpp+ivQHQ0jhO56XK M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArQHAMvugk2tJV2Y/2dsb2JhbACYdYx2d6Y2nBCCe4JoBIxjg08
X-IronPort-AV: E=Sophos;i="4.63,205,1299456000"; d="scan'208";a="321788265"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by sj-iport-2.cisco.com with ESMTP; 18 Mar 2011 12:38:21 +0000
Received: from [161.44.174.126] (dhcp-161-44-174-126.cisco.com [161.44.174.126]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2ICcKgM020275 for <siprec@ietf.org>; Fri, 18 Mar 2011 12:38:21 GMT
Message-ID: <4D83523C.8030306@cisco.com>
Date: Fri, 18 Mar 2011 08:38:20 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: siprec@ietf.org
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Multiplexing different participants' streams on the same	port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 12:36:54 -0000

I don't know if this is a good idea or not. But if we want to consider 
it, then we should probably enter into some discussion with CLUE, to see 
if there is any commonality.

Over in CLUE, this mixing of multiple streams over one RTP session has 
been brought up because it is a technique used in existing proprietary 
products. But the CLUE wg isn't yet to a point where it is ready to 
decide if this will be a requirement. And the AVT people have strong 
opinions on what is/isn't appropriate.

	Thanks,
	Paul

On 3/18/2011 4:11 AM, Elwell, John wrote:
> Something Charles mentioned in another thread triggered me to raise this.
>
> We consider different participants in the CS as potentially producing separate media streams that the SRC sends to the SRS, where the SRC can send them mixed or unmixed.
>
> When sending them unmixed, up till now I think we have considered sending them to separate ports on the SRS and identifying them as separate m= lines in the SDP. Another possibility might be to multiplex the different streams on the same port and identify them by different SSRC values. I am not sure whether this would be a correct use of SSRC, and I suspect we would need to check with AVTCORE. Recent discussions in other contexts (telepresence, RTC-Web) have also drawn my attention to such possibilities. See also https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
>
> Of course, it would mean that we would have to rethink how we reference the different streams from metadata.
>
> I am not necessarily proposing such a change - I just want to make sure we have given it due consideration.
>
> John (as individual)
>
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>

From john.elwell@siemens-enterprise.com  Fri Mar 18 06:57:50 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E63693A68B1 for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 06:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zvnPMkv2Sgi1 for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 06:57:49 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 948373A67FA for <siprec@ietf.org>; Fri, 18 Mar 2011 06:57:49 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3797962; Fri, 18 Mar 2011 14:59:17 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id A7C3923F028E; Fri, 18 Mar 2011 14:59:17 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 18 Mar 2011 14:59:17 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Sid Rao <srao@ctigroup.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Fri, 18 Mar 2011 14:59:16 +0100
Thread-Topic: [siprec] Multiplexing different participants' streams on the sameport
Thread-Index: AcvlRBLrSWbjqO+eTN2hm6ZyFiLojwAE6lMQAAcjdJA=
Message-ID: <A444A0F8084434499206E78C106220CA086A96506D@MCHP058A.global-ad.net>
References: <B03E298DC8DFC143A7584C166773CBF903A26A63@EXCHANGE2K3.ctigroup.com>
In-Reply-To: <B03E298DC8DFC143A7584C166773CBF903A26A63@EXCHANGE2K3.ctigroup.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Multiplexing different participants' streams on the sameport
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 13:57:51 -0000

Those who have proposed this in other contexts are concerned about:
- excessive use of NAT port bindings, which some feel might become a scarce=
 resource in some situations;
- the amount of ICE work that needs to be done.

Of course, these considerations will not apply to all deployments of SIPREC=
, so a one stream per port solution might be considered adequate. But it is=
 better to have this discussion now than later.

John
=20

> -----Original Message-----
> From: Sid Rao [mailto:srao@ctigroup.com]=20
> Sent: 18 March 2011 10:34
> To: Elwell, John; siprec@ietf.org
> Subject: RE: [siprec] Multiplexing different participants'=20
> streams on the sameport
>=20
> Just out of curiosity, apart from the extra socket this=20
> saves, what are
> the actual technical drivers for such a solution?
>=20
> Sid Rao
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf
> Of Elwell, John
> Sent: Friday, March 18, 2011 4:11 AM
> To: siprec@ietf.org
> Subject: [siprec] Multiplexing different participants' streams on the
> sameport
>=20
> Something Charles mentioned in another thread triggered me to raise
> this.
>=20
> We consider different participants in the CS as potentially producing
> separate media streams that the SRC sends to the SRS, where=20
> the SRC can
> send them mixed or unmixed.
>=20
> When sending them unmixed, up till now I think we have considered
> sending them to separate ports on the SRS and identifying them as
> separate m=3D lines in the SDP. Another possibility might be to=20
> multiplex
> the different streams on the same port and identify them by different
> SSRC values. I am not sure whether this would be a correct=20
> use of SSRC,
> and I suspect we would need to check with AVTCORE. Recent=20
> discussions in
> other contexts (telepresence, RTC-Web) have also drawn my attention to
> such possibilities. See also
> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
>=20
> Of course, it would mean that we would have to rethink how we=20
> reference
> the different streams from metadata.
>=20
> I am not necessarily proposing such a change - I just want to=20
> make sure
> we have given it due consideration.
>=20
> John (as individual)
>=20
> =20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
> =

From eckelcu@cisco.com  Fri Mar 18 08:08:16 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B695C3A691D for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 08:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.574
X-Spam-Level: 
X-Spam-Status: No, score=-10.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LVBQl2RW6-ZN for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 08:08:15 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 765073A691C for <siprec@ietf.org>; Fri, 18 Mar 2011 08:08:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=3495; q=dns/txt; s=iport; t=1300460985; x=1301670585; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=XNRSyTOLkOAhox6m9EcUOetqrVWogv6JEA+mPD4sS5o=; b=CdNMxc/9jAA0Ea9NNUzsXJcUvhqDplqYn42hKdAdjEXoZRiKTK4+Efkp 9iMHBDwgzBWupNOikUx1DuWhOFkqVlpZaI4YXErHSC6yzabL+UZE9ADlO cy2IzyJBQ1/3ngVfYj+8yvID3hXIhp/1H8o/15z24biCbOI2hQoKY2G8N Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMAAHQSg02tJXG9/2dsb2JhbACYNo02d6ZFnBGCe4JoBIUxiwc
X-IronPort-AV: E=Sophos;i="4.63,205,1299456000"; d="scan'208";a="668528273"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-6.cisco.com with ESMTP; 18 Mar 2011 15:09:44 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2IF9icJ029966 for <siprec@ietf.org>; Fri, 18 Mar 2011 15:09:44 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 18 Mar 2011 08:09:44 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 18 Mar 2011 08:09:43 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <4D83523C.8030306@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: AcvlaWIIK70D67ErTdeQ754hs4iSUgAErWSw
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net> <4D83523C.8030306@cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 18 Mar 2011 15:09:44.0308 (UTC) FILETIME=[83622B40:01CBE57E]
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Mar 2011 15:08:16 -0000

I agree with the comment regarding CLUE, so let me take a simpler
example, and audio mixer. This mixer may mix the audio from multiple
participants.

Participant 1 (P1)
Participant 2 (P2)
Participant 3 (P3)

P1 sends audio stream with SSRC-P1
P2 sends audio stream with SSCR-P2
P2 sends audio stream with SSCR-P3

MixerA(Ma)

Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
The SRC sends this stream to the SRS for recording. I suspect it might
change the SSRC to be SSRC-SRC but maintain the CSRC information
identifying P1/P2/P3.
I expect this would be modeled as a single stream with 3 participants
P1, P2, P3. The mapping of P1 to SSRC-P1 is captured in the RTCP data
sent by SRC to SRS. In this case, there is no need to anything in the
metadata.
However, if the CSRCs are not propagated all the way to the SRS, then
perhaps participant info would need to be communicated via the metadata.

Note, I do not pretend to have this all figured out; rather, I am
putting out some ideas to see if this gels with what others have in
mind.

Cheers,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Paul Kyzivat (pkyzivat)
> Sent: Friday, March 18, 2011 5:38 AM
> To: siprec@ietf.org
> Subject: Re: [siprec] Multiplexing different participants' streams on
the same port
>=20
> I don't know if this is a good idea or not. But if we want to consider
> it, then we should probably enter into some discussion with CLUE, to
see
> if there is any commonality.
>=20
> Over in CLUE, this mixing of multiple streams over one RTP session has
> been brought up because it is a technique used in existing proprietary
> products. But the CLUE wg isn't yet to a point where it is ready to
> decide if this will be a requirement. And the AVT people have strong
> opinions on what is/isn't appropriate.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/18/2011 4:11 AM, Elwell, John wrote:
> > Something Charles mentioned in another thread triggered me to raise
this.
> >
> > We consider different participants in the CS as potentially
producing separate media streams that
> the SRC sends to the SRS, where the SRC can send them mixed or
unmixed.
> >
> > When sending them unmixed, up till now I think we have considered
sending them to separate ports on
> the SRS and identifying them as separate m=3D lines in the SDP. =
Another
possibility might be to
> multiplex the different streams on the same port and identify them by
different SSRC values. I am not
> sure whether this would be a correct use of SSRC, and I suspect we
would need to check with AVTCORE.
> Recent discussions in other contexts (telepresence, RTC-Web) have also
drawn my attention to such
> possibilities. See also
https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
> >
> > Of course, it would mean that we would have to rethink how we
reference the different streams from
> metadata.
> >
> > I am not necessarily proposing such a change - I just want to make
sure we have given it due
> consideration.
> >
> > John (as individual)
> >
> >
> > _______________________________________________
> > 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

From partr@cisco.com  Fri Mar 18 19:51:21 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77AB13A6A56 for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 19:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.991
X-Spam-Level: 
X-Spam-Status: No, score=-9.991 tagged_above=-999 required=5 tests=[AWL=0.607,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1SYQXY6QoVPK for <siprec@core3.amsl.com>; Fri, 18 Mar 2011 19:51:20 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id E40073A6A28 for <siprec@ietf.org>; Fri, 18 Mar 2011 19:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=4239; q=dns/txt; s=iport; t=1300503170; x=1301712770; h=mime-version:subject:date:message-id:in-reply-to: references:from:to; bh=0AKK1Zs/NjhAZ1Nw3YuThfJdECmiq7bJSg1BapwhOws=; b=G3uc9fFpP2c4nnFMwccVjetZpmLyYMTv3O4J9ofNJx0WBWODl8e0HVN6 ZIQKrl/wqben/Op7kj1hnVF9X6iRRQAUE+PXzCcP3fKDzz4NGxzFEWFdT gvQ/ShTekrKMybQSu8EMg+L2s/QTBLa7C03bWDksgnkg9vy6lbk/YMvJJ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKe3g02Q/khMgWdsb2JhbACldBUBCwsmJYhNnyucDYVjBIUviwk
X-IronPort-AV: E=Sophos;i="4.63,209,1299456000"; d="scan'208,217";a="79872553"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 19 Mar 2011 02:52:42 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2J2qfDW016400; Sat, 19 Mar 2011 02:52:42 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 19 Mar 2011 08:22:41 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE5E0.B6894C37"
Date: Sat, 19 Mar 2011 08:22:37 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904CAF47D@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Is it required to pass metadata using non-sip mechanism [was RE: [siprec] Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwCdkkqA
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 19 Mar 2011 02:52:41.0321 (UTC) FILETIME=[B6D79D90:01CBE5E0]
Subject: [siprec] Is it required to pass metadata using non-sip mechanism [was RE: Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 19 Mar 2011 02:51:21 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE5E0.B6894C37
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,
=20
As per current SIPREC architecture document, metadata *MAY* be passed by
non-sip protocol mechanism as well. I'm interested in knowing whether
anybody is interested to pass metadata using non-sip mechanism or
specific requirement for the same.
=20
See below mail thread for more details
=20
Thanks
Partha
________________________________

From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
Sent: Tue 3/15/2011 9:30 PM
To: Parthasarathi R (partr)
Cc: Elwell, John; siprec@ietf.org
Subject: RE: Progressing the architecture document
 [snip]=20


>=20
> Sec 4.3.2 last bullet: is it required to pass metadata using
> non-sip mechanism?
>
[AndyH] I will remove this statement if that is ok with everyone.

<Partha> In case you foresee this requirement, Please start separate
mail thread as there are lot of implication in metadata format draft.
The current metadata format draft is designed for SIP and not for other
protocols </Partha>


> Thanks
> Partha



------_=_NextPart_001_01CBE5E0.B6894C37
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=3Dltr><HEAD><TITLE>RE: Progressing the architecture =
document</TITLE>
<META content=3D"text/html; charset=3Dus-ascii" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D763374602-19032011>Hi all,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D763374602-19032011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D763374602-19032011>As per current SIPREC architecture document, =
metadata=20
*MAY* be passed&nbsp;by non-sip protocol mechanism as well. I'm =
interested in=20
knowing whether anybody is interested to pass metadata using non-sip =
mechanism=20
or specific requirement for the same.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D763374602-19032011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D763374602-19032011>See below mail thread for more=20
details</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D763374602-19032011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D763374602-19032011>Thanks</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D763374602-19032011>Partha</SPAN></FONT></DIV>
<DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
<HR tabIndex=3D-1>
<FONT size=3D2><FONT face=3DTahoma><B>From:</B> Hutton, Andrew=20
[mailto:andrew.hutton@siemens-enterprise.com]<BR><B>Sent:</B> Tue =
3/15/2011 9:30=20
PM<BR><B>To:</B> Parthasarathi R (partr)<BR><B>Cc:</B> Elwell, John;=20
siprec@ietf.org<BR><B>Subject:</B> RE: Progressing the architecture=20
document<BR></FONT><SPAN class=3D763374602-19032011><FONT =
color=3D#0000ff=20
face=3DArial>&nbsp;[snip]&nbsp;</FONT></SPAN></FONT><BR></DIV>
<DIV>
<P><FONT size=3D2>&gt;&nbsp;<BR>&gt; Sec 4.3.2 last bullet: is it =
required to pass=20
metadata using<BR>&gt; non-sip mechanism?<BR>&gt;<BR>[AndyH] I will =
remove this=20
statement if that is ok with everyone.</FONT></P>
<P><FONT size=3D2>&lt;Partha&gt; In case you foresee this requirement, =
Please=20
start separate mail thread as there are lot of implication in metadata =
format=20
draft. The current metadata format draft is designed for SIP and not for =
other=20
protocols &lt;/Partha&gt;<BR><BR><BR>&gt; Thanks<BR>&gt;=20
Partha<BR></P></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01CBE5E0.B6894C37--

From pkyzivat@cisco.com  Sat Mar 19 14:26:19 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6366C3A6A07 for <siprec@core3.amsl.com>; Sat, 19 Mar 2011 14:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9RST1D2pBwvZ for <siprec@core3.amsl.com>; Sat, 19 Mar 2011 14:26:18 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 2285C3A69D0 for <siprec@ietf.org>; Sat, 19 Mar 2011 14:26:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=1511; q=dns/txt; s=iport; t=1300570069; x=1301779669; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=qvzXSrjGIpBy4Ek6IFClFlzxYaCV8DXEMTCqtJOaW9Q=; b=ijPf87+20p0bbIVt0yE82SJ2BnV6Uf71qB8fiFKN0gyOd6wmSUsATqFQ 5lofiPF/1+HI2hfrbCcVu9oz289JCIn0dpaDcJtwpXANxpByOf+WK1sUs 9P4et5euz1oQ921QfJV+9ceZ7/x3+Euxva6wTtNdyj85I1eGCuJTrmjhg 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4HAL+8hE2tJXG+/2dsb2JhbACYfIx5d6Y5myyFYwSMZ4NR
X-IronPort-AV: E=Sophos;i="4.63,212,1299456000"; d="scan'208";a="322186904"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by sj-iport-2.cisco.com with ESMTP; 19 Mar 2011 21:27:49 +0000
Received: from [10.86.254.236] ([10.86.254.236]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2JLRmr6027650 for <siprec@ietf.org>; Sat, 19 Mar 2011 21:27:48 GMT
Message-ID: <4D851FD4.7030808@cisco.com>
Date: Sat, 19 Mar 2011 17:27:48 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: siprec@ietf.org
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net>	<A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com> <A11921905DA1564D9BCF64A6430A623904CAF47D@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904CAF47D@XMB-BGL-411.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Is it required to pass metadata using non-sip mechanism [was RE: Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 19 Mar 2011 21:26:19 -0000

Partha,

AFAIK the point of such a statement is not that we should be specifying 
how to do it, but only not to exclude it from being done via mechanisms 
we have not specified.

	Thanks,
	Paul

On 3/18/2011 10:52 PM, Parthasarathi R (partr) wrote:
> Hi all,
> As per current SIPREC architecture document, metadata *MAY* be passed by
> non-sip protocol mechanism as well. I'm interested in knowing whether
> anybody is interested to pass metadata using non-sip mechanism or
> specific requirement for the same.
> See below mail thread for more details
> Thanks
> Partha
> ------------------------------------------------------------------------
> *From:* Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> *Sent:* Tue 3/15/2011 9:30 PM
> *To:* Parthasarathi R (partr)
> *Cc:* Elwell, John; siprec@ietf.org
> *Subject:* RE: Progressing the architecture document
> [snip]
>
>  >
>  > Sec 4.3.2 last bullet: is it required to pass metadata using
>  > non-sip mechanism?
>  >
> [AndyH] I will remove this statement if that is ok with everyone.
>
> <Partha> In case you foresee this requirement, Please start separate
> mail thread as there are lot of implication in metadata format draft.
> The current metadata format draft is designed for SIP and not for other
> protocols </Partha>
>
>
>  > Thanks
>  > Partha
>
>
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From Leon.Portman@nice.com  Sun Mar 20 14:33:51 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A0BF3A6BDF for <siprec@core3.amsl.com>; Sun, 20 Mar 2011 14:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.352
X-Spam-Level: 
X-Spam-Status: No, score=-2.352 tagged_above=-999 required=5 tests=[AWL=0.247,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zm8NdCg0q3lP for <siprec@core3.amsl.com>; Sun, 20 Mar 2011 14:33:47 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 4D6D63A6A06 for <siprec@ietf.org>; Sun, 20 Mar 2011 14:33:47 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Sun, 20 Mar 2011 23:35:17 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Sun, 20 Mar 2011 23:35:07 +0200
Thread-Topic: [siprec] Is it required to pass metadata using non-sip mechanism [was RE: Progressing the architecture document]
Thread-Index: AcvmfILR+qtq+/rOQWqFTwtYNgF2dwAye/MA
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A9492059@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com> <A11921905DA1564D9BCF64A6430A623904CAF47D@XMB-BGL-411.cisco.com> <4D851FD4.7030808@cisco.com>
In-Reply-To: <4D851FD4.7030808@cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Henry Lum <Henry.Lum@alcatel-lucent.com>
Subject: Re: [siprec] Is it required to pass metadata using non-sip mechanism [was RE: Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 20 Mar 2011 21:33:51 -0000

Yes, I think it is important to support out of band metadata reporting (via=
 non SIP such as webservice). If I remember correctly, it was also Henry's =
opinion.
Of course there should be some correlation identifier such as callId

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Paul Kyzivat
Sent: Saturday, March 19, 2011 11:28 PM
To: siprec@ietf.org
Subject: Re: [siprec] Is it required to pass metadata using non-sip mechani=
sm [was RE: Progressing the architecture document]

Partha,

AFAIK the point of such a statement is not that we should be specifying how=
 to do it, but only not to exclude it from being done via mechanisms we hav=
e not specified.

	Thanks,
	Paul

On 3/18/2011 10:52 PM, Parthasarathi R (partr) wrote:
> Hi all,
> As per current SIPREC architecture document, metadata *MAY* be passed=20
> by non-sip protocol mechanism as well. I'm interested in knowing=20
> whether anybody is interested to pass metadata using non-sip mechanism=20
> or specific requirement for the same.
> See below mail thread for more details Thanks Partha
> ----------------------------------------------------------------------
> --
> *From:* Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> *Sent:* Tue 3/15/2011 9:30 PM
> *To:* Parthasarathi R (partr)
> *Cc:* Elwell, John; siprec@ietf.org
> *Subject:* RE: Progressing the architecture document [snip]
>
>  >
>  > Sec 4.3.2 last bullet: is it required to pass metadata using  >=20
> non-sip mechanism?
>  >
> [AndyH] I will remove this statement if that is ok with everyone.
>
> <Partha> In case you foresee this requirement, Please start separate=20
> mail thread as there are lot of implication in metadata format draft.
> The current metadata format draft is designed for SIP and not for=20
> other protocols </Partha>
>
>
>  > Thanks
>  > Partha
>
>
>
> _______________________________________________
> 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

From partr@cisco.com  Sun Mar 20 18:34:51 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6104628B23E for <siprec@core3.amsl.com>; Sun, 20 Mar 2011 18:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.005
X-Spam-Level: 
X-Spam-Status: No, score=-10.005 tagged_above=-999 required=5 tests=[AWL=0.594, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h-blMzqMNeCu for <siprec@core3.amsl.com>; Sun, 20 Mar 2011 18:34:50 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id A5FF13A6ABC for <siprec@ietf.org>; Sun, 20 Mar 2011 18:34:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=3135; q=dns/txt; s=iport; t=1300671382; x=1301880982; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=LZ+YIG7cCQgZaR32aDxnJjb8OmYqvJtq4EpIMlLDgy8=; b=DX1uPxwkDdC78p/eyhZ2Gh5HFX4/gRQDHFDlW8XagxrVmvfnwKstlibo amVWlnyDIuko9PjhWDrew2NiJF/bpshnBU1DnNJKGehnY8H4ZtnfJLVrD 5NT0d33+XEnzpb473vEA1j1JG6OILg28FPj6EH0DMV1/wTZN97hFi1Uix Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As0AAPFHhk2Q/khLgWdsb2JhbACYM403FAEBFiYliE2bMJsYhWMEhTGLDQ
X-IronPort-AV: E=Sophos;i="4.63,216,1299456000"; d="scan'208";a="79981130"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 21 Mar 2011 01:36:21 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2L1aK3Z029472; Mon, 21 Mar 2011 01:36:20 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 21 Mar 2011 07:06:19 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 21 Mar 2011 07:06:18 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904CAF57C@XMB-BGL-411.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A9492059@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Is it required to pass metadata using non-sip mechanism [was RE: Progressing the architecture document]
Thread-Index: AcvmfILR+qtq+/rOQWqFTwtYNgF2dwAye/MAAAgkw5A=
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAF47D@XMB-BGL-411.cisco.com><4D851FD4.7030808@cisco.com> <07465C1D981ABC41A344374066AE1A2C38A9492059@TLVMBX01.nice.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 21 Mar 2011 01:36:19.0962 (UTC) FILETIME=[60F735A0:01CBE768]
Cc: Henry Lum <Henry.Lum@alcatel-lucent.com>
Subject: Re: [siprec] Is it required to pass metadata using non-sip mechanism [was RE: Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 21 Mar 2011 01:34:51 -0000

Leon,

I'll split recording metadata into two: SIPREC metadata (attributes
mentioned in draft-ram-siprec-metadata) & Non-SIPREC metadata.
Non-SIPREC metadata may use non-SIP mechanism (like webservice) for
passing metadata and Non-SIPREC metadata handling is outside the scope
of SIPREC.

I'm interested in knowing whether SIPREC metadata has to be passed using
non-SIP mechanism as it is within the scope of SIPREC.

Thanks
Partha

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Leon Portman
Sent: Monday, March 21, 2011 3:05 AM
To: Paul Kyzivat (pkyzivat); siprec@ietf.org
Cc: Henry Lum
Subject: Re: [siprec] Is it required to pass metadata using non-sip
mechanism [was RE: Progressing the architecture document]

Yes, I think it is important to support out of band metadata reporting
(via non SIP such as webservice). If I remember correctly, it was also
Henry's opinion.
Of course there should be some correlation identifier such as callId

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Paul Kyzivat
Sent: Saturday, March 19, 2011 11:28 PM
To: siprec@ietf.org
Subject: Re: [siprec] Is it required to pass metadata using non-sip
mechanism [was RE: Progressing the architecture document]

Partha,

AFAIK the point of such a statement is not that we should be specifying
how to do it, but only not to exclude it from being done via mechanisms
we have not specified.

	Thanks,
	Paul

On 3/18/2011 10:52 PM, Parthasarathi R (partr) wrote:
> Hi all,
> As per current SIPREC architecture document, metadata *MAY* be passed=20
> by non-sip protocol mechanism as well. I'm interested in knowing=20
> whether anybody is interested to pass metadata using non-sip mechanism

> or specific requirement for the same.
> See below mail thread for more details Thanks Partha
> ----------------------------------------------------------------------
> --
> *From:* Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> *Sent:* Tue 3/15/2011 9:30 PM
> *To:* Parthasarathi R (partr)
> *Cc:* Elwell, John; siprec@ietf.org
> *Subject:* RE: Progressing the architecture document [snip]
>
>  >
>  > Sec 4.3.2 last bullet: is it required to pass metadata using  >=20
> non-sip mechanism?
>  >
> [AndyH] I will remove this statement if that is ok with everyone.
>
> <Partha> In case you foresee this requirement, Please start separate=20
> mail thread as there are lot of implication in metadata format draft.
> The current metadata format draft is designed for SIP and not for=20
> other protocols </Partha>
>
>
>  > Thanks
>  > Partha
>
>
>
> _______________________________________________
> 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

From partr@cisco.com  Tue Mar 22 06:31:39 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27C6B3A6839 for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 06:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.018
X-Spam-Level: 
X-Spam-Status: No, score=-10.018 tagged_above=-999 required=5 tests=[AWL=0.580, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wQi392nJ76wa for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 06:31:37 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 439773A682B for <siprec@ietf.org>; Tue, 22 Mar 2011 06:31:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=6368; q=dns/txt; s=iport; t=1300800791; x=1302010391; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=dL0zjSZOM95H0nENlq/ZU1HKggW6BIgoFjWFyAvGDyQ=; b=D6Bsc3XJKhPpyinWxfXislD34Jn0ikkysaEzFs43eIt1vXWlF9E3SmR9 rgduooaw+av9l/dEdsCTBPq3HbpbRn8nChC9/HlQY8brcM1+sQ8YGvdY4 2sVzfmIEFML2/UeXan9u4KMsLLPkm9PzA7WeP57CiIQNEDq1F3CYNoKnU Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtIAAOtBiE2Q/khMgWdsb2JhbACYBY02FAEBFiYliE2ddZxvhWgEhTOLEA
X-IronPort-AV: E=Sophos;i="4.63,224,1299456000"; d="scan'208,217";a="22683366"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 22 Mar 2011 13:33:09 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2MDX8C8028336; Tue, 22 Mar 2011 13:33:09 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 22 Mar 2011 19:03:08 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE895.AE2DA09B"
Date: Tue, 22 Mar 2011 19:03:08 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Dialog state in the CS block of metadata model [was RE: Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdA
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 22 Mar 2011 13:33:08.0638 (UTC) FILETIME=[AE8C1BE0:01CBE895]
Cc: siprec@ietf.org
Subject: [siprec] Dialog state in the CS block of metadata model [was RE: Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 22 Mar 2011 13:31:39 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE895.AE2DA09B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The architecture document proposes to have dialog/session state in
Metadata model. To achieve this, "session state" attribute has to be
added in the CS block of Metadata model. The possible values for session
state are
=20
1) Trying
2) Proceeding
3) Early
4) Confirmed
5) Terminated=20
=20
Please let me know in case any objection to add this attribute in
Metadata model.
=20
Thanks
Partha=20

________________________________

From: Parthasarathi R (partr)=20
Sent: Wednesday, March 16, 2011 5:40 AM
To: Hutton, Andrew
Cc: Elwell, John; siprec@ietf.org
Subject: RE: Progressing the architecture document


> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 14 March 2011 17:05
> To: Elwell, John; siprec@ietf.org
> Subject: Re: [siprec] Progressing the architecture document


>=20
> Sec 4.3.1 whether 3rd bullet is required?
>=20

[AndyH]I assume it is as for example I assume it would be necessary to
record early-media and update the SRS when the dialog changes to the
confirmed or terminated state. Does not seem to be in the metadata draft
though. In the end I will either remove these bullets or align with the
metadata draft.
<Partha> It is a good point. Dialog state shall be added as one of the
optional attribute in CS metadata block with default value as
mid-dialog. This helps to differentiate between early dialog (ringback)
vs mid-dialog (normal conversation) in recording. In case of no
objection for this attribute in metadata model, we will add it. We will
work out metadata format once the consensus occurs for metadata model.
In case required, we will span separate mail thread to close this issue
</Partha>



------_=_NextPart_001_01CBE895.AE2DA09B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=3Dltr><HEAD><TITLE>RE: Progressing the architecture =
document</TITLE>
<META content=3D"text/html; charset=3Dus-ascii" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011>The architecture document proposes to have=20
dialog/session state in Metadata model. To achieve this, "session state" =

attribute has to be added in the CS block of Metadata model. The =
possible values=20
for session state are</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011>1) Trying</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011>2) Proceeding</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011>3) Early</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011>4) Confirmed</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011>5) Terminated&nbsp;</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011>Please let me know in case any objection to =
add this=20
attribute in Metadata model.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011>Thanks</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D470272211-22032011>Partha&nbsp;</SPAN></FONT></DIV><BR>
<DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
<HR tabIndex=3D-1>
<FONT size=3D2 face=3DTahoma><B>From:</B> Parthasarathi R (partr) =
<BR><B>Sent:</B>=20
Wednesday, March 16, 2011 5:40 AM<BR><B>To:</B> Hutton, =
Andrew<BR><B>Cc:</B>=20
Elwell, John; siprec@ietf.org<BR><B>Subject:</B> RE: Progressing the=20
architecture document<BR></FONT></DIV>
<DIV>
<P><FONT size=3D2>&gt; -----Original Message-----<BR>&gt; From:=20
siprec-bounces@ietf.org<BR>&gt; [<A=20
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>] On=20
Behalf Of Parthasarathi R (partr)<BR>&gt; Sent: 14 March 2011 =
17:05<BR>&gt; To:=20
Elwell, John; siprec@ietf.org<BR>&gt; Subject: Re: [siprec] Progressing =
the=20
architecture document<BR></FONT></P>
<P><FONT size=3D2>&gt;&nbsp;<BR>&gt; Sec 4.3.1 whether 3rd bullet is=20
required?<BR>&gt;&nbsp;<BR><BR>[AndyH]I assume it is as for example I =
assume it=20
would be necessary to record early-media and update the SRS when the =
dialog=20
changes to the confirmed or terminated state. Does not seem to be in the =

metadata draft though. In the end I will either remove these bullets or =
align=20
with the metadata draft.<BR>&lt;Partha&gt; It is a good point. Dialog =
state=20
shall be added as one of the&nbsp;optional&nbsp;attribute in CS metadata =
block=20
with default value as mid-dialog. This helps to differentiate between =
early=20
dialog (ringback) vs mid-dialog (normal conversation) in recording. In =
case of=20
no objection for this attribute in metadata model, we will add it. We =
will work=20
out metadata format once the consensus occurs for metadata model. In =
case=20
required, we will span separate mail thread to close this issue=20
&lt;/Partha&gt;<BR></FONT></P>
<P><FONT size=3D2><FONT color=3D#0000ff=20
face=3DArial></FONT></P></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01CBE895.AE2DA09B--

From Leon.Portman@nice.com  Tue Mar 22 07:09:26 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F71228C0D0 for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 07:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 tagged_above=-999 required=5 tests=[AWL=0.238,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GecTTzsu1iSO for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 07:09:25 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 0C2BF28C113 for <siprec@ietf.org>; Tue, 22 Mar 2011 07:09:25 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Tue, 22 Mar 2011 16:10:56 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Date: Tue, 22 Mar 2011 16:10:49 +0200
Thread-Topic: Dialog state in the CS block of metadata model [was RE: Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com> <A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: multipart/alternative; boundary="_000_07465C1D981ABC41A344374066AE1A2C38A960C8F0TLVMBX01nicec_"
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadata model [was RE:	Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 22 Mar 2011 14:09:26 -0000

--_000_07465C1D981ABC41A344374066AE1A2C38A960C8F0TLVMBX01nicec_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Should we have error state as well?

Leon

From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Parthasarathi R (partr)
Sent: Tuesday, March 22, 2011 3:33 PM
To: Parthasarathi R (partr); Hutton, Andrew
Cc: siprec@ietf.org
Subject: [siprec] Dialog state in the CS block of metadata model [was RE: P=
rogressing the architecture document]

The architecture document proposes to have dialog/session state in Metadata=
 model. To achieve this, "session state" attribute has to be added in the C=
S block of Metadata model. The possible values for session state are

1) Trying
2) Proceeding
3) Early
4) Confirmed
5) Terminated

Please let me know in case any objection to add this attribute in Metadata =
model.

Thanks
Partha

________________________________
From: Parthasarathi R (partr)
Sent: Wednesday, March 16, 2011 5:40 AM
To: Hutton, Andrew
Cc: Elwell, John; siprec@ietf.org
Subject: RE: Progressing the architecture document

> -----Original Message-----
> From: siprec-bounces@ietf.org<mailto:siprec-bounces@ietf.org>
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 14 March 2011 17:05
> To: Elwell, John; siprec@ietf.org<mailto:siprec@ietf.org>
> Subject: Re: [siprec] Progressing the architecture document

>
> Sec 4.3.1 whether 3rd bullet is required?
>

[AndyH]I assume it is as for example I assume it would be necessary to reco=
rd early-media and update the SRS when the dialog changes to the confirmed =
or terminated state. Does not seem to be in the metadata draft though. In t=
he end I will either remove these bullets or align with the metadata draft.
<Partha> It is a good point. Dialog state shall be added as one of the opti=
onal attribute in CS metadata block with default value as mid-dialog. This =
helps to differentiate between early dialog (ringback) vs mid-dialog (norma=
l conversation) in recording. In case of no objection for this attribute in=
 metadata model, we will add it. We will work out metadata format once the =
consensus occurs for metadata model. In case required, we will span separat=
e mail thread to close this issue </Partha>

--_000_07465C1D981ABC41A344374066AE1A2C38A960C8F0TLVMBX01nicec_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#def=
ault#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><title>RE: Progressing the architecture document</title=
><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Should we=
 have error state as well?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Leon<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div s=
tyle=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0c=
m'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tah=
oma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif"'> siprec-bounces@ietf.org [mailto:siprec-bounces@=
ietf.org] <b>On Behalf Of </b>Parthasarathi R (partr)<br><b>Sent:</b> Tuesd=
ay, March 22, 2011 3:33 PM<br><b>To:</b> Parthasarathi R (partr); Hutton, A=
ndrew<br><b>Cc:</b> siprec@ietf.org<br><b>Subject:</b> [siprec] Dialog stat=
e in the CS block of metadata model [was RE: Progressing the architecture d=
ocument]<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"=
Arial","sans-serif";color:blue'>The architecture document proposes to have =
dialog/session state in Metadata model. To achieve this, &quot;session stat=
e&quot; attribute has to be added in the CS block of Metadata model. The po=
ssible values for session state are</span><o:p></o:p></p><p class=3DMsoNorm=
al>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0p=
t;font-family:"Arial","sans-serif";color:blue'>1) Trying</span><o:p></o:p><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial"=
,"sans-serif";color:blue'>2) Proceeding</span><o:p></o:p></p><p class=3DMso=
Normal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";col=
or:blue'>3) Early</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'=
font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>4) Confirmed<=
/span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;f=
ont-family:"Arial","sans-serif";color:blue'>5) Terminated&nbsp;</span><o:p>=
</o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>=
Please let me know in case any objection to add this attribute in Metadata =
model.</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-s=
erif";color:blue'>Thanks</span><o:p></o:p></p><p class=3DMsoNormal><span st=
yle=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Partha=
&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><hr size=3D2 w=
idth=3D"100%" align=3Dcenter></div><p class=3DMsoNormal><b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Parthasarathi R=
 (partr) <br><b>Sent:</b> Wednesday, March 16, 2011 5:40 AM<br><b>To:</b> H=
utton, Andrew<br><b>Cc:</b> Elwell, John; siprec@ietf.org<br><b>Subject:</b=
> RE: Progressing the architecture document</span><o:p></o:p></p><div><p><s=
pan style=3D'font-size:10.0pt'>&gt; -----Original Message-----<br>&gt; From=
: <a href=3D"mailto:siprec-bounces@ietf.org">siprec-bounces@ietf.org</a><br=
>&gt; [<a href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@iet=
f.org</a>] On Behalf Of Parthasarathi R (partr)<br>&gt; Sent: 14 March 2011=
 17:05<br>&gt; To: Elwell, John; <a href=3D"mailto:siprec@ietf.org">siprec@=
ietf.org</a><br>&gt; Subject: Re: [siprec] Progressing the architecture doc=
ument</span><o:p></o:p></p><p><span style=3D'font-size:10.0pt'>&gt;&nbsp;<b=
r>&gt; Sec 4.3.1 whether 3rd bullet is required?<br>&gt;&nbsp;<br><br>[Andy=
H]I assume it is as for example I assume it would be necessary to record ea=
rly-media and update the SRS when the dialog changes to the confirmed or te=
rminated state. Does not seem to be in the metadata draft though. In the en=
d I will either remove these bullets or align with the metadata draft.<br>&=
lt;Partha&gt; It is a good point. Dialog state shall be added as one of the=
&nbsp;optional&nbsp;attribute in CS metadata block with default value as mi=
d-dialog. This helps to differentiate between early dialog (ringback) vs mi=
d-dialog (normal conversation) in recording. In case of no objection for th=
is attribute in metadata model, we will add it. We will work out metadata f=
ormat once the consensus occurs for metadata model. In case required, we wi=
ll span separate mail thread to close this issue &lt;/Partha&gt;</span><o:p=
></o:p></p></div></div></body></html>=

--_000_07465C1D981ABC41A344374066AE1A2C38A960C8F0TLVMBX01nicec_--

From andrew.hutton@siemens-enterprise.com  Tue Mar 22 09:00:31 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EA6A3A67A2 for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 09:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.116
X-Spam-Level: 
X-Spam-Status: No, score=-2.116 tagged_above=-999 required=5 tests=[AWL=0.482,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASp4PlVnSkjS for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 09:00:30 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id A6F033A63C9 for <siprec@ietf.org>; Tue, 22 Mar 2011 09:00:29 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3840553; Tue, 22 Mar 2011 17:02:01 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id E8E2C1EB82C6; Tue, 22 Mar 2011 17:02:01 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 22 Mar 2011 17:02:02 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, "Parthasarathi R (partr)" <partr@cisco.com>
Date: Tue, 22 Mar 2011 17:02:00 +0100
Thread-Topic: Dialog state in the CS block of metadata model [was RE: Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQA==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com> <A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E30B61E96D11MCHP058Agloba_"
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadata model [was RE:	Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 22 Mar 2011 16:00:31 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E30B61E96D11MCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

What would it be used for?

Regards
Andy

________________________________
From: Leon Portman [mailto:Leon.Portman@nice.com]
Sent: 22 March 2011 14:11
To: Parthasarathi R (partr); Hutton, Andrew
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was RE: Progre=
ssing the architecture document]

Should we have error state as well?

Leon

From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Parthasarathi R (partr)
Sent: Tuesday, March 22, 2011 3:33 PM
To: Parthasarathi R (partr); Hutton, Andrew
Cc: siprec@ietf.org
Subject: [siprec] Dialog state in the CS block of metadata model [was RE: P=
rogressing the architecture document]

The architecture document proposes to have dialog/session state in Metadata=
 model. To achieve this, "session state" attribute has to be added in the C=
S block of Metadata model. The possible values for session state are

1) Trying
2) Proceeding
3) Early
4) Confirmed
5) Terminated

Please let me know in case any objection to add this attribute in Metadata =
model.

Thanks
Partha

________________________________
From: Parthasarathi R (partr)
Sent: Wednesday, March 16, 2011 5:40 AM
To: Hutton, Andrew
Cc: Elwell, John; siprec@ietf.org
Subject: RE: Progressing the architecture document

> -----Original Message-----
> From: siprec-bounces@ietf.org<mailto:siprec-bounces@ietf.org>
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 14 March 2011 17:05
> To: Elwell, John; siprec@ietf.org<mailto:siprec@ietf.org>
> Subject: Re: [siprec] Progressing the architecture document

>
> Sec 4.3.1 whether 3rd bullet is required?
>

[AndyH]I assume it is as for example I assume it would be necessary to reco=
rd early-media and update the SRS when the dialog changes to the confirmed =
or terminated state. Does not seem to be in the metadata draft though. In t=
he end I will either remove these bullets or align with the metadata draft.
<Partha> It is a good point. Dialog state shall be added as one of the opti=
onal attribute in CS metadata block with default value as mid-dialog. This =
helps to differentiate between early dialog (ringback) vs mid-dialog (norma=
l conversation) in recording. In case of no objection for this attribute in=
 metadata model, we will add it. We will work out metadata format once the =
consensus occurs for metadata model. In case required, we will span separat=
e mail thread to close this issue </Partha>

--_000_101C6067BEC68246B0C3F6843BCCC1E30B61E96D11MCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD><TITLE>RE: Progres=
sing the architecture document</TITLE>
<META content=3D"text/html; charset=3Dus-ascii" http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19019"><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt 72.0pt 90.=
0pt; }
P.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12=
pt
}
LI.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12=
pt
}
DIV.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12=
pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
	FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0cm; FONT-SIZE: 12pt;=
 MARGIN-RIGHT: 0cm; mso-style-priority: 99; mso-margin-top-alt: auto; mso-m=
argin-bottom-alt: auto
}
P.MsoAcetate {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.EmailStyle18 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: perso=
nal-reply
}
SPAN.BalloonTextChar {
	FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link=
: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US link=3Dblue vLink=3Dpurple>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D128460116-22032011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>What would it be used for?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D128460116-22032011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D128460116-22032011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D128460116-22032011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Andy</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; MARGIN-RIGHT: 0px"=20
dir=3Dltr>
  <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>From:</B> Leon Portman=20
  [mailto:Leon.Portman@nice.com] <BR><B>Sent:</B> 22 March 2011=20
  14:11<BR><B>To:</B> Parthasarathi R (partr); Hutton, Andrew<BR><B>Cc:</B>=
=20
  siprec@ietf.org<BR><B>Subject:</B> RE: Dialog state in the CS block of=20
  metadata model [was RE: Progressing the architecture=20
  document]<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DWordSection1>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: =
11pt">Should=20
  we have error state as well?<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: =
11pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: =
11pt">Leon<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: =
11pt"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV>
  <DIV=20
  style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BO=
TTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
  <P class=3DMsoNormal><B><SPAN=20
  style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN=
></B><SPAN=20
  style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">=20
  siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] <B>On Behalf Of=
=20
  </B>Parthasarathi R (partr)<BR><B>Sent:</B> Tuesday, March 22, 2011 3:33=
=20
  PM<BR><B>To:</B> Parthasarathi R (partr); Hutton, Andrew<BR><B>Cc:</B>=20
  siprec@ietf.org<BR><B>Subject:</B> [siprec] Dialog state in the CS block =
of=20
  metadata model [was RE: Progressing the architecture=20
  document]<o:p></o:p></SPAN></P></DIV></DIV>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"=
>The=20
  architecture document proposes to have dialog/session state in Metadata m=
odel.=20
  To achieve this, "session state" attribute has to be added in the CS bloc=
k of=20
  Metadata model. The possible values for session state=20
are</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"=
>1)=20
  Trying</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"=
>2)=20
  Proceeding</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"=
>3)=20
  Early</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"=
>4)=20
  Confirmed</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"=
>5)=20
  Terminated&nbsp;</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"=
>Please=20
  let me know in case any objection to add this attribute in Metadata=20
  model.</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"=
>Thanks</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"=
>Partha&nbsp;</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal align=3Dcenter>
  <HR align=3Dcenter SIZE=3D2 width=3D"100%">
  </DIV>
  <P class=3DMsoNormal><B><SPAN=20
  style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN=
></B><SPAN=20
  style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Parthasara=
thi R=20
  (partr) <BR><B>Sent:</B> Wednesday, March 16, 2011 5:40 AM<BR><B>To:</B>=
=20
  Hutton, Andrew<BR><B>Cc:</B> Elwell, John; siprec@ietf.org<BR><B>Subject:=
</B>=20
  RE: Progressing the architecture document</SPAN><o:p></o:p></P>
  <DIV>
  <P><SPAN style=3D"FONT-SIZE: 10pt">&gt; -----Original Message-----<BR>&gt=
; From:=20
  <A href=3D"mailto:siprec-bounces@ietf.org">siprec-bounces@ietf.org</A><BR=
>&gt;=20
  [<A href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.or=
g</A>]=20
  On Behalf Of Parthasarathi R (partr)<BR>&gt; Sent: 14 March 2011 17:05<BR=
>&gt;=20
  To: Elwell, John; <A href=3D"mailto:siprec@ietf.org">siprec@ietf.org</A><=
BR>&gt;=20
  Subject: Re: [siprec] Progressing the architecture=20
  document</SPAN><o:p></o:p></P>
  <P><SPAN style=3D"FONT-SIZE: 10pt">&gt;&nbsp;<BR>&gt; Sec 4.3.1 whether 3=
rd=20
  bullet is required?<BR>&gt;&nbsp;<BR><BR>[AndyH]I assume it is as for exa=
mple=20
  I assume it would be necessary to record early-media and update the SRS w=
hen=20
  the dialog changes to the confirmed or terminated state. Does not seem to=
 be=20
  in the metadata draft though. In the end I will either remove these bulle=
ts or=20
  align with the metadata draft.<BR>&lt;Partha&gt; It is a good point. Dial=
og=20
  state shall be added as one of the&nbsp;optional&nbsp;attribute in CS met=
adata=20
  block with default value as mid-dialog. This helps to differentiate betwe=
en=20
  early dialog (ringback) vs mid-dialog (normal conversation) in recording.=
 In=20
  case of no objection for this attribute in metadata model, we will add it=
. We=20
  will work out metadata format once the consensus occurs for metadata mode=
l. In=20
  case required, we will span separate mail thread to close this issue=20
  &lt;/Partha&gt;</SPAN><o:p></o:p></P></DIV></DIV></BLOCKQUOTE></BODY></HT=
ML>

--_000_101C6067BEC68246B0C3F6843BCCC1E30B61E96D11MCHP058Agloba_--

From Leon.Portman@nice.com  Tue Mar 22 09:06:11 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 422E33A67A1 for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 09:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.231,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wgsfrXRQG4hP for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 09:06:05 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id B83C13A659A for <siprec@ietf.org>; Tue, 22 Mar 2011 09:06:04 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Tue, 22 Mar 2011 18:07:37 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>
Date: Tue, 22 Mar 2011 18:07:28 +0200
Thread-Topic: Dialog state in the CS block of metadata model [was RE: Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQ
Message-ID: <07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com> <A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com> <101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: multipart/alternative; boundary="_000_07465C1D981ABC41A344374066AE1A2C38A960C9CATLVMBX01nicec_"
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadata model [was RE:	Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 22 Mar 2011 16:06:11 -0000

--_000_07465C1D981ABC41A344374066AE1A2C38A960C9CATLVMBX01nicec_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

It can be either application level error or dialog level errors - like time=
out or failures.

Leon

From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
Sent: Tuesday, March 22, 2011 6:02 PM
To: Leon Portman; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was RE: Progre=
ssing the architecture document]

What would it be used for?

Regards
Andy

________________________________
From: Leon Portman [mailto:Leon.Portman@nice.com]
Sent: 22 March 2011 14:11
To: Parthasarathi R (partr); Hutton, Andrew
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was RE: Progre=
ssing the architecture document]
Should we have error state as well?

Leon

From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Parthasarathi R (partr)
Sent: Tuesday, March 22, 2011 3:33 PM
To: Parthasarathi R (partr); Hutton, Andrew
Cc: siprec@ietf.org
Subject: [siprec] Dialog state in the CS block of metadata model [was RE: P=
rogressing the architecture document]

The architecture document proposes to have dialog/session state in Metadata=
 model. To achieve this, "session state" attribute has to be added in the C=
S block of Metadata model. The possible values for session state are

1) Trying
2) Proceeding
3) Early
4) Confirmed
5) Terminated

Please let me know in case any objection to add this attribute in Metadata =
model.

Thanks
Partha

________________________________
From: Parthasarathi R (partr)
Sent: Wednesday, March 16, 2011 5:40 AM
To: Hutton, Andrew
Cc: Elwell, John; siprec@ietf.org
Subject: RE: Progressing the architecture document

> -----Original Message-----
> From: siprec-bounces@ietf.org<mailto:siprec-bounces@ietf.org>
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 14 March 2011 17:05
> To: Elwell, John; siprec@ietf.org<mailto:siprec@ietf.org>
> Subject: Re: [siprec] Progressing the architecture document

>
> Sec 4.3.1 whether 3rd bullet is required?
>

[AndyH]I assume it is as for example I assume it would be necessary to reco=
rd early-media and update the SRS when the dialog changes to the confirmed =
or terminated state. Does not seem to be in the metadata draft though. In t=
he end I will either remove these bullets or align with the metadata draft.
<Partha> It is a good point. Dialog state shall be added as one of the opti=
onal attribute in CS metadata block with default value as mid-dialog. This =
helps to differentiate between early dialog (ringback) vs mid-dialog (norma=
l conversation) in recording. In case of no objection for this attribute in=
 metadata model, we will add it. We will work out metadata format once the =
consensus occurs for metadata model. In case required, we will span separat=
e mail thread to close this issue </Partha>

--_000_07465C1D981ABC41A344374066AE1A2C38A960C9CATLVMBX01nicec_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#def=
ault#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><title>RE: Progressing the architecture document</title=
><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It can be=
 either application level error or dialog level errors &#8211; like timeout=
 or failures. <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'>Leon<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'bord=
er:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=
=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-=
serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'> Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.co=
m] <br><b>Sent:</b> Tuesday, March 22, 2011 6:02 PM<br><b>To:</b> Leon Port=
man; Parthasarathi R (partr)<br><b>Cc:</b> siprec@ietf.org<br><b>Subject:</=
b> RE: Dialog state in the CS block of metadata model [was RE: Progressing =
the architecture document]<o:p></o:p></span></p></div></div><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:10=
.0pt;font-family:"Arial","sans-serif";color:blue'>What would it be used for=
?</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f";color:blue'>Regards</span><o:p></o:p></p><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Andy</sp=
an><o:p></o:p></p><blockquote style=3D'border:none;border-right:solid blue =
1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-=
right:0cm;margin-bottom:5.0pt'><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><d=
iv class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><hr size=3D=
2 width=3D"100%" align=3Dcenter></div><p class=3DMsoNormal style=3D'margin-=
bottom:12.0pt'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","san=
s-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif"'> Leon Portman [mailto:Leon.Portman@nice.com] <br><b>Sent:=
</b> 22 March 2011 14:11<br><b>To:</b> Parthasarathi R (partr); Hutton, And=
rew<br><b>Cc:</b> siprec@ietf.org<br><b>Subject:</b> RE: Dialog state in th=
e CS block of metadata model [was RE: Progressing the architecture document=
]</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'>Should we have error sta=
te as well?<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'>Leon<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:=
none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DM=
soNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-seri=
f"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","s=
ans-serif"'> siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] <b>On=
 Behalf Of </b>Parthasarathi R (partr)<br><b>Sent:</b> Tuesday, March 22, 2=
011 3:33 PM<br><b>To:</b> Parthasarathi R (partr); Hutton, Andrew<br><b>Cc:=
</b> siprec@ietf.org<br><b>Subject:</b> [siprec] Dialog state in the CS blo=
ck of metadata model [was RE: Progressing the architecture document]<o:p></=
o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-se=
rif";color:blue'>The architecture document proposes to have dialog/session =
state in Metadata model. To achieve this, &quot;session state&quot; attribu=
te has to be added in the CS block of Metadata model. The possible values f=
or session state are</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"=
Arial","sans-serif";color:blue'>1) Trying</span><o:p></o:p></p><p class=3DM=
soNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";c=
olor:blue'>2) Proceeding</span><o:p></o:p></p><p class=3DMsoNormal><span st=
yle=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>3) Ear=
ly</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0p=
t;font-family:"Arial","sans-serif";color:blue'>4) Confirmed</span><o:p></o:=
p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Ari=
al","sans-serif";color:blue'>5) Terminated&nbsp;</span><o:p></o:p></p><p cl=
ass=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Please let me k=
now in case any objection to add this attribute in Metadata model.</span><o=
:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal=
><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blu=
e'>Thanks</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-siz=
e:10.0pt;font-family:"Arial","sans-serif";color:blue'>Partha&nbsp;</span><o=
:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div class=3DMsoNorm=
al align=3Dcenter style=3D'text-align:center'><hr size=3D2 width=3D"100%" a=
lign=3Dcenter></div><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt=
;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-siz=
e:10.0pt;font-family:"Tahoma","sans-serif"'> Parthasarathi R (partr) <br><b=
>Sent:</b> Wednesday, March 16, 2011 5:40 AM<br><b>To:</b> Hutton, Andrew<b=
r><b>Cc:</b> Elwell, John; siprec@ietf.org<br><b>Subject:</b> RE: Progressi=
ng the architecture document</span><o:p></o:p></p><div><p><span style=3D'fo=
nt-size:10.0pt'>&gt; -----Original Message-----<br>&gt; From: <a href=3D"ma=
ilto:siprec-bounces@ietf.org">siprec-bounces@ietf.org</a><br>&gt; [<a href=
=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</a>] On =
Behalf Of Parthasarathi R (partr)<br>&gt; Sent: 14 March 2011 17:05<br>&gt;=
 To: Elwell, John; <a href=3D"mailto:siprec@ietf.org">siprec@ietf.org</a><b=
r>&gt; Subject: Re: [siprec] Progressing the architecture document</span><o=
:p></o:p></p><p><span style=3D'font-size:10.0pt'>&gt;&nbsp;<br>&gt; Sec 4.3=
.1 whether 3rd bullet is required?<br>&gt;&nbsp;<br><br>[AndyH]I assume it =
is as for example I assume it would be necessary to record early-media and =
update the SRS when the dialog changes to the confirmed or terminated state=
. Does not seem to be in the metadata draft though. In the end I will eithe=
r remove these bullets or align with the metadata draft.<br>&lt;Partha&gt; =
It is a good point. Dialog state shall be added as one of the&nbsp;optional=
&nbsp;attribute in CS metadata block with default value as mid-dialog. This=
 helps to differentiate between early dialog (ringback) vs mid-dialog (norm=
al conversation) in recording. In case of no objection for this attribute i=
n metadata model, we will add it. We will work out metadata format once the=
 consensus occurs for metadata model. In case required, we will span separa=
te mail thread to close this issue &lt;/Partha&gt;</span><o:p></o:p></p></d=
iv></blockquote></div></body></html>=

--_000_07465C1D981ABC41A344374066AE1A2C38A960C9CATLVMBX01nicec_--

From john.elwell@siemens-enterprise.com  Tue Mar 22 10:41:26 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C4913A68B0 for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 10:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vfx8QzqsdwyK for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 10:41:25 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 3A6743A68AC for <siprec@ietf.org>; Tue, 22 Mar 2011 10:41:24 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3841327; Tue, 22 Mar 2011 18:42:55 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 508BE1EB82C3; Tue, 22 Mar 2011 18:42:54 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 22 Mar 2011 18:42:54 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Date: Tue, 22 Mar 2011 18:42:52 +0100
Thread-Topic: Dialog state in the CS block of metadata model [was RE: Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAA1G9iA=
Message-ID: <A444A0F8084434499206E78C106220CA086A9FE656@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com> <A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadata model [was RE: Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 22 Mar 2011 17:41:26 -0000

What would dialog state be used for?

John=20

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]=20
> Sent: 22 March 2011 13:33
> To: Parthasarathi R (partr); Hutton, Andrew
> Cc: Elwell, John; siprec@ietf.org
> Subject: Dialog state in the CS block of metadata model [was=20
> RE: Progressing the architecture document]
>=20
> The architecture document proposes to have dialog/session=20
> state in Metadata model. To achieve this, "session state"=20
> attribute has to be added in the CS block of Metadata model.=20
> The possible values for session state are
> =20
> 1) Trying
> 2) Proceeding
> 3) Early
> 4) Confirmed
> 5) Terminated=20
> =20
> Please let me know in case any objection to add this=20
> attribute in Metadata model.
> =20
> Thanks
> Partha=20
>=20
> ________________________________
>=20
> From: Parthasarathi R (partr)=20
> Sent: Wednesday, March 16, 2011 5:40 AM
> To: Hutton, Andrew
> Cc: Elwell, John; siprec@ietf.org
> Subject: RE: Progressing the architecture document
>=20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi=20
> R (partr)
> > Sent: 14 March 2011 17:05
> > To: Elwell, John; siprec@ietf.org
> > Subject: Re: [siprec] Progressing the architecture document
>=20
>=20
> >=20
> > Sec 4.3.1 whether 3rd bullet is required?
> >=20
>=20
> [AndyH]I assume it is as for example I assume it would be=20
> necessary to record early-media and update the SRS when the=20
> dialog changes to the confirmed or terminated state. Does not=20
> seem to be in the metadata draft though. In the end I will=20
> either remove these bullets or align with the metadata draft.
> <Partha> It is a good point. Dialog state shall be added as=20
> one of the optional attribute in CS metadata block with=20
> default value as mid-dialog. This helps to differentiate=20
> between early dialog (ringback) vs mid-dialog (normal=20
> conversation) in recording. In case of no objection for this=20
> attribute in metadata model, we will add it. We will work out=20
> metadata format once the consensus occurs for metadata model.=20
> In case required, we will span separate mail thread to close=20
> this issue </Partha>
>=20
>=20
> =

From partr@cisco.com  Tue Mar 22 17:25:09 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 095F228C105 for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 17:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.332
X-Spam-Level: 
X-Spam-Status: No, score=-9.332 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TkowaBxLKQP1 for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 17:25:06 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 3CEB728C0F8 for <siprec@ietf.org>; Tue, 22 Mar 2011 17:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=7567; q=dns/txt; s=iport; t=1300840000; x=1302049600; h=mime-version:subject:date:message-id:references:from:to: cc; bh=XagLNDnL26fYl0bS2VGoZBxRdeHlPa+Px9XQvfDhAa0=; b=ddwlhOzEnP9+BcYsvGqIYxI0a3RmWm6rKNZpCJN/7/ThdlS1d1yvjerM miZH6EGcUN+kO8deGF0OgXbou1e3SngFGuYMsOgFSdDfh1Es6gdXn3RUv M0cpnx63v3q0mojC+ThxpyrqeIGKy3Ums/++jn3fXk+B6y0CZQUAJaySW o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArwAALraiE2Q/khLgWdsb2JhbACYDIxgVhQBARYmJakRnBSFaQSFNIsS
X-IronPort-AV: E=Sophos;i="4.63,228,1299456000"; d="scan'208,217";a="80328275"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 23 Mar 2011 00:26:38 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2N0QbWq011745; Wed, 23 Mar 2011 00:26:38 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Mar 2011 05:56:37 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE8F0.F8A316A0"
Date: Wed, 23 Mar 2011 05:56:37 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A6BD@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Dialog state in the CS block of metadata model [was RE: Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAA1G9iAADajZ2A==
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com> <A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086A9FE656@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 23 Mar 2011 00:26:37.0726 (UTC) FILETIME=[F8FC23E0:01CBE8F0]
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadata model [was RE: Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 23 Mar 2011 00:25:09 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE8F0.F8A316A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John,
=20
As Andy mentioned in the below mail thread, One of the usecase for =
session state attribute is to understand whether CS is in early media or =
not. The other possible usecase is to indicate explicitly about CS =
termination within persistent recording.
=20
Thanks
Partha=20

________________________________

From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
Sent: Tue 3/22/2011 11:12 PM
To: Parthasarathi R (partr); Hutton, Andrew
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was RE: =
Progressing the architecture document]



What would dialog state be used for?

John

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 22 March 2011 13:33
> To: Parthasarathi R (partr); Hutton, Andrew
> Cc: Elwell, John; siprec@ietf.org
> Subject: Dialog state in the CS block of metadata model [was
> RE: Progressing the architecture document]
>
> The architecture document proposes to have dialog/session
> state in Metadata model. To achieve this, "session state"
> attribute has to be added in the CS block of Metadata model.
> The possible values for session state are
>=20
> 1) Trying
> 2) Proceeding
> 3) Early
> 4) Confirmed
> 5) Terminated
>=20
> Please let me know in case any objection to add this
> attribute in Metadata model.
>=20
> Thanks
> Partha
>
> ________________________________
>
> From: Parthasarathi R (partr)
> Sent: Wednesday, March 16, 2011 5:40 AM
> To: Hutton, Andrew
> Cc: Elwell, John; siprec@ietf.org
> Subject: RE: Progressing the architecture document
>
>
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
> R (partr)
> > Sent: 14 March 2011 17:05
> > To: Elwell, John; siprec@ietf.org
> > Subject: Re: [siprec] Progressing the architecture document
>
>
> >
> > Sec 4.3.1 whether 3rd bullet is required?
> >
>
> [AndyH]I assume it is as for example I assume it would be
> necessary to record early-media and update the SRS when the
> dialog changes to the confirmed or terminated state. Does not
> seem to be in the metadata draft though. In the end I will
> either remove these bullets or align with the metadata draft.
> <Partha> It is a good point. Dialog state shall be added as
> one of the optional attribute in CS metadata block with
> default value as mid-dialog. This helps to differentiate
> between early dialog (ringback) vs mid-dialog (normal
> conversation) in recording. In case of no objection for this
> attribute in metadata model, we will add it. We will work out
> metadata format once the consensus occurs for metadata model.
> In case required, we will span separate mail thread to close
> this issue </Partha>
>
>
>



------_=_NextPart_001_01CBE8F0.F8A316A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: Dialog state in the CS block of =
metadata model [was RE: Progressing the architecture document]</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText90861>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 =
face=3DArial>John,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>As Andy mentioned in the =
below mail thread, One of the usecase for&nbsp;session state =
attribute&nbsp;is&nbsp;to understand&nbsp;whether&nbsp;CS is in =
early&nbsp;media or not. The other possible usecase is&nbsp;to indicate =
explicitly about&nbsp;CS termination within =
persistent&nbsp;recording.</FONT></DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 =
face=3DArial>Partha</FONT>&nbsp;</DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> Elwell, John =
[mailto:john.elwell@siemens-enterprise.com]<BR><B>Sent:</B> Tue =
3/22/2011 11:12 PM<BR><B>To:</B> Parthasarathi R (partr); Hutton, =
Andrew<BR><B>Cc:</B> siprec@ietf.org<BR><B>Subject:</B> RE: Dialog state =
in the CS block of metadata model [was RE: Progressing the architecture =
document]<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>What would dialog state be used =
for?<BR><BR>John<BR><BR>&gt; -----Original Message-----<BR>&gt; From: =
Parthasarathi R (partr) [<A =
href=3D"mailto:partr@cisco.com">mailto:partr@cisco.com</A>]<BR>&gt; =
Sent: 22 March 2011 13:33<BR>&gt; To: Parthasarathi R (partr); Hutton, =
Andrew<BR>&gt; Cc: Elwell, John; siprec@ietf.org<BR>&gt; Subject: Dialog =
state in the CS block of metadata model [was<BR>&gt; RE: Progressing the =
architecture document]<BR>&gt;<BR>&gt; The architecture document =
proposes to have dialog/session<BR>&gt; state in Metadata model. To =
achieve this, "session state"<BR>&gt; attribute has to be added in the =
CS block of Metadata model.<BR>&gt; The possible values for session =
state are<BR>&gt;&nbsp;<BR>&gt; 1) Trying<BR>&gt; 2) Proceeding<BR>&gt; =
3) Early<BR>&gt; 4) Confirmed<BR>&gt; 5) =
Terminated<BR>&gt;&nbsp;<BR>&gt; Please let me know in case any =
objection to add this<BR>&gt; attribute in Metadata =
model.<BR>&gt;&nbsp;<BR>&gt; Thanks<BR>&gt; Partha<BR>&gt;<BR>&gt; =
________________________________<BR>&gt;<BR>&gt; From: Parthasarathi R =
(partr)<BR>&gt; Sent: Wednesday, March 16, 2011 5:40 AM<BR>&gt; To: =
Hutton, Andrew<BR>&gt; Cc: Elwell, John; siprec@ietf.org<BR>&gt; =
Subject: RE: Progressing the architecture =
document<BR>&gt;<BR>&gt;<BR>&gt; &gt; -----Original Message-----<BR>&gt; =
&gt; From: siprec-bounces@ietf.org<BR>&gt; &gt; [<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>] On Behalf Of Parthasarathi<BR>&gt; R (partr)<BR>&gt; &gt; Sent: 14 =
March 2011 17:05<BR>&gt; &gt; To: Elwell, John; siprec@ietf.org<BR>&gt; =
&gt; Subject: Re: [siprec] Progressing the architecture =
document<BR>&gt;<BR>&gt;<BR>&gt; &gt;<BR>&gt; &gt; Sec 4.3.1 whether 3rd =
bullet is required?<BR>&gt; &gt;<BR>&gt;<BR>&gt; [AndyH]I assume it is =
as for example I assume it would be<BR>&gt; necessary to record =
early-media and update the SRS when the<BR>&gt; dialog changes to the =
confirmed or terminated state. Does not<BR>&gt; seem to be in the =
metadata draft though. In the end I will<BR>&gt; either remove these =
bullets or align with the metadata draft.<BR>&gt; &lt;Partha&gt; It is a =
good point. Dialog state shall be added as<BR>&gt; one of the optional =
attribute in CS metadata block with<BR>&gt; default value as mid-dialog. =
This helps to differentiate<BR>&gt; between early dialog (ringback) vs =
mid-dialog (normal<BR>&gt; conversation) in recording. In case of no =
objection for this<BR>&gt; attribute in metadata model, we will add it. =
We will work out<BR>&gt; metadata format once the consensus occurs for =
metadata model.<BR>&gt; In case required, we will span separate mail =
thread to close<BR>&gt; this issue =
&lt;/Partha&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR></FONT></P></DIV></BODY></HTML=
>
------_=_NextPart_001_01CBE8F0.F8A316A0--

From partr@cisco.com  Tue Mar 22 17:41:16 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B0833A684A for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 17:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.329
X-Spam-Level: 
X-Spam-Status: No, score=-9.329 tagged_above=-999 required=5 tests=[AWL=-0.127, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRP9nINPL8y7 for <siprec@core3.amsl.com>; Tue, 22 Mar 2011 17:41:11 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id D38AB3A6847 for <siprec@ietf.org>; Tue, 22 Mar 2011 17:41:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=15118; q=dns/txt; s=iport; t=1300840964; x=1302050564; h=mime-version:subject:date:message-id:references:from:to: cc; bh=UlqJOV1A+EXv3mWPoMpYh01JgODg4jnOKWp/3g7kanM=; b=NbB5XEsngyZ5ACTmnuIJfpXEJuZiji0F75nyWWxoRadb9NLL7oLKiWNa /5IvhCtBmUdRJQEjoP2FM6Vu2CEhxDe9nprM9mgZ5jsa6TGDq1lC/ikaW KMrm8mKM+0RFzcEDDj2TlIlIJLmJf8NRHGgOzOuRAvyz+kmmqwMr5dsuQ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArwAAPjeiE2Q/khMgWdsb2JhbACCYZUrjGBWFAEBFiYliE2gNJwThWkEhTSLEg
X-IronPort-AV: E=Sophos;i="4.63,228,1299456000"; d="scan'208,217";a="22753630"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 23 Mar 2011 00:42:43 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2N0ggqC004998; Wed, 23 Mar 2011 00:42:42 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Mar 2011 06:12:42 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE8F3.37624931"
Date: Wed, 23 Mar 2011 06:12:41 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Dialog state in the CS block of metadata model [was RE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/Cmw=
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com> <A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com> <101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 23 Mar 2011 00:42:42.0136 (UTC) FILETIME=[37D16D80:01CBE8F3]
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadata model [was RE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 23 Mar 2011 00:41:16 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE8F3.37624931
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Leon,
=20
Shall we have optional "event" attribute to indicate the state change =
which is similar to "event" attribute in RFC 4235.  The "event" will =
include the following:
=20
1) cancelled
2) rejected
3) replaced
4) bye
5) error
6) timeout
=20
Thanks
Partha

________________________________

From: Leon Portman [mailto:Leon.Portman@nice.com]
Sent: Tue 3/22/2011 9:37 PM
To: Hutton, Andrew; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was =
RE:Progressing the architecture document]



It can be either application level error or dialog level errors - like =
timeout or failures.=20

=20

Leon

=20

From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]=20
Sent: Tuesday, March 22, 2011 6:02 PM
To: Leon Portman; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was RE: =
Progressing the architecture document]

=20

What would it be used for?

=20

Regards

Andy

	=20

________________________________

	From: Leon Portman [mailto:Leon.Portman@nice.com]=20
	Sent: 22 March 2011 14:11
	To: Parthasarathi R (partr); Hutton, Andrew
	Cc: siprec@ietf.org
	Subject: RE: Dialog state in the CS block of metadata model [was RE: =
Progressing the architecture document]

	Should we have error state as well?

	=20

	Leon

	=20

	From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On =
Behalf Of Parthasarathi R (partr)
	Sent: Tuesday, March 22, 2011 3:33 PM
	To: Parthasarathi R (partr); Hutton, Andrew
	Cc: siprec@ietf.org
	Subject: [siprec] Dialog state in the CS block of metadata model [was =
RE: Progressing the architecture document]

	=20

	The architecture document proposes to have dialog/session state in =
Metadata model. To achieve this, "session state" attribute has to be =
added in the CS block of Metadata model. The possible values for session =
state are

	=20

	1) Trying

	2) Proceeding

	3) Early

	4) Confirmed

	5) Terminated=20

	=20

	Please let me know in case any objection to add this attribute in =
Metadata model.

	=20

	Thanks

	Partha=20

	=20

________________________________

	From: Parthasarathi R (partr)=20
	Sent: Wednesday, March 16, 2011 5:40 AM
	To: Hutton, Andrew
	Cc: Elwell, John; siprec@ietf.org
	Subject: RE: Progressing the architecture document

	> -----Original Message-----
	> From: siprec-bounces@ietf.org
	> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
	> Sent: 14 March 2011 17:05
	> To: Elwell, John; siprec@ietf.org
	> Subject: Re: [siprec] Progressing the architecture document

	>=20
	> Sec 4.3.1 whether 3rd bullet is required?
	>=20
=09
	[AndyH]I assume it is as for example I assume it would be necessary to =
record early-media and update the SRS when the dialog changes to the =
confirmed or terminated state. Does not seem to be in the metadata draft =
though. In the end I will either remove these bullets or align with the =
metadata draft.
	<Partha> It is a good point. Dialog state shall be added as one of the =
optional attribute in CS metadata block with default value as =
mid-dialog. This helps to differentiate between early dialog (ringback) =
vs mid-dialog (normal conversation) in recording. In case of no =
objection for this attribute in metadata model, we will add it. We will =
work out metadata format once the consensus occurs for metadata model. =
In case required, we will span separate mail thread to close this issue =
</Partha>


------_=_NextPart_001_01CBE8F3.37624931
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: Progressing the architecture =
document</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928">=0A=
<STYLE><!--=0A=
                      =0A=
font-face=0A=
	{font-family:Calibri;}=0A=
font-face=0A=
	{font-family:Tahoma;}=0A=
                       =0A=
p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=
	{margin:0cm;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:12.0pt;=0A=
	font-family:"Times New Roman","serif";}=0A=
a:link, span.MsoHyperlink=0A=
	{=0A=
	color:blue;=0A=
	text-decoration:underline;}=0A=
a:visited, span.MsoHyperlinkFollowed=0A=
	{=0A=
	color:purple;=0A=
	text-decoration:underline;}=0A=
p=0A=
	{=0A=
	margin-right:0cm;=0A=
	margin-left:0cm;=0A=
	font-size:12.0pt;=0A=
	font-family:"Times New Roman","serif";}=0A=
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate=0A=
	{=0A=
	margin:0cm;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:8.0pt;=0A=
	font-family:"Tahoma","sans-serif";}=0A=
span.BalloonTextChar=0A=
	{=0A=
	font-family:"Tahoma","sans-serif";}=0A=
span.EmailStyle20=0A=
	{=0A=
	font-family:"Calibri","sans-serif";=0A=
	color:#1F497D;}=0A=
span.EmailStyle21=0A=
	{=0A=
	font-family:"Calibri","sans-serif";=0A=
	color:#1F497D;}=0A=
.MsoChpDefault=0A=
	{=0A=
	font-size:10.0pt;}=0A=
=0A=
div.WordSection1=0A=
	{page:WordSection1;}=0A=
--></STYLE>=0A=
</HEAD>=0A=
<BODY lang=3DEN-US link=3Dblue vLink=3Dpurple>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText12087>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 =
face=3DArial>Leon,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Shall we have =
optional&nbsp;"event" attribute to indicate the state change which is =
similar to "event"&nbsp;attribute in RFC 4235.&nbsp; The "event" will =
include the following:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>1) cancelled</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>2) rejected</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>3) replaced</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>4) bye</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>5) error</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>6) timeout</FONT></DIV><FONT =
size=3D2 face=3DArial></FONT></DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT></DIV>=0A=
<DIV dir=3Dltr><BR></DIV>=0A=
<DIV dir=3Dltr>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DTahoma><B>From:</B> Leon Portman =
[mailto:Leon.Portman@nice.com]<BR><B>Sent:</B> Tue 3/22/2011 9:37 =
PM<BR><B>To:</B> Hutton, Andrew; Parthasarathi R (partr)<BR><B>Cc:</B> =
siprec@ietf.org<BR><B>Subject:</B> RE: Dialog state in the CS block of =
metadata model [was RE:Progressing the architecture =
document]<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<DIV class=3DWordSection1>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">It can be either application level =
error or dialog level errors &#8211; like timeout or failures. =
</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Leon</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<DIV>=0A=
<DIV style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; =
PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: =
#b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">=0A=
<P class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: =
'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Hutton, =
Andrew [mailto:andrew.hutton@siemens-enterprise.com] <BR><B>Sent:</B> =
Tuesday, March 22, 2011 6:02 PM<BR><B>To:</B> Leon Portman; =
Parthasarathi R (partr)<BR><B>Cc:</B> siprec@ietf.org<BR><B>Subject:</B> =
RE: Dialog state in the CS block of metadata model [was RE: Progressing =
the architecture document]</SPAN></P></DIV></DIV>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">What would it be used for?</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Regards</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Andy</SPAN></P>=0A=
<BLOCKQUOTE style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium =
none; PADDING-BOTTOM: 0cm; MARGIN: 5pt 0cm 5pt 3.75pt; PADDING-LEFT: =
4pt; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; BORDER-RIGHT: blue =
1.5pt solid; PADDING-TOP: 0cm">=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal align=3Dcenter>=0A=
<HR align=3Dcenter SIZE=3D2 width=3D"100%">=0A=
</DIV>=0A=
<P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: =
10pt">From:</SPAN></B><SPAN style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; =
FONT-SIZE: 10pt"> Leon Portman [mailto:Leon.Portman@nice.com] =
<BR><B>Sent:</B> 22 March 2011 14:11<BR><B>To:</B> Parthasarathi R =
(partr); Hutton, Andrew<BR><B>Cc:</B> siprec@ietf.org<BR><B>Subject:</B> =
RE: Dialog state in the CS block of metadata model [was RE: Progressing =
the architecture document]</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Should we have error state as =
well?</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Leon</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<DIV>=0A=
<DIV style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; =
PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: =
#b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">=0A=
<P class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: =
'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> =
siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] <B>On Behalf Of =
</B>Parthasarathi R (partr)<BR><B>Sent:</B> Tuesday, March 22, 2011 3:33 =
PM<BR><B>To:</B> Parthasarathi R (partr); Hutton, Andrew<BR><B>Cc:</B> =
siprec@ietf.org<BR><B>Subject:</B> [siprec] Dialog state in the CS block =
of metadata model [was RE: Progressing the architecture =
document]</SPAN></P></DIV></DIV>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">The architecture document proposes to have =
dialog/session state in Metadata model. To achieve this, "session state" =
attribute has to be added in the CS block of Metadata model. The =
possible values for session state are</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">1) Trying</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">2) Proceeding</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">3) Early</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">4) Confirmed</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">5) Terminated&nbsp;</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Please let me know in case any objection =
to add this attribute in Metadata model.</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Thanks</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Partha&nbsp;</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal align=3Dcenter>=0A=
<HR align=3Dcenter SIZE=3D2 width=3D"100%">=0A=
</DIV>=0A=
<P class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: =
'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> =
Parthasarathi R (partr) <BR><B>Sent:</B> Wednesday, March 16, 2011 5:40 =
AM<BR><B>To:</B> Hutton, Andrew<BR><B>Cc:</B> Elwell, John; =
siprec@ietf.org<BR><B>Subject:</B> RE: Progressing the architecture =
document</SPAN></P>=0A=
<DIV>=0A=
<P><SPAN style=3D"FONT-SIZE: 10pt">&gt; -----Original =
Message-----<BR>&gt; From: <A =
href=3D"mailto:siprec-bounces@ietf.org">siprec-bounces@ietf.org</A><BR>&g=
t; [<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>] On Behalf Of Parthasarathi R (partr)<BR>&gt; Sent: 14 March 2011 =
17:05<BR>&gt; To: Elwell, John; <A =
href=3D"mailto:siprec@ietf.org">siprec@ietf.org</A><BR>&gt; Subject: Re: =
[siprec] Progressing the architecture document</SPAN></P>=0A=
<P><SPAN style=3D"FONT-SIZE: 10pt">&gt;&nbsp;<BR>&gt; Sec 4.3.1 whether =
3rd bullet is required?<BR>&gt;&nbsp;<BR><BR>[AndyH]I assume it is as =
for example I assume it would be necessary to record early-media and =
update the SRS when the dialog changes to the confirmed or terminated =
state. Does not seem to be in the metadata draft though. In the end I =
will either remove these bullets or align with the metadata =
draft.<BR>&lt;Partha&gt; It is a good point. Dialog state shall be added =
as one of the&nbsp;optional&nbsp;attribute in CS metadata block with =
default value as mid-dialog. This helps to differentiate between early =
dialog (ringback) vs mid-dialog (normal conversation) in recording. In =
case of no objection for this attribute in metadata model, we will add =
it. We will work out metadata format once the consensus occurs for =
metadata model. In case required, we will span separate mail thread to =
close this issue =
&lt;/Partha&gt;</SPAN></P></DIV></BLOCKQUOTE></DIV></DIV></BODY></HTML>
------_=_NextPart_001_01CBE8F3.37624931--

From gonzalo.camarillo@ericsson.com  Wed Mar 23 04:21:10 2011
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16BAD3A6819 for <siprec@core3.amsl.com>; Wed, 23 Mar 2011 04:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level: 
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3-8+OJd7uNZ for <siprec@core3.amsl.com>; Wed, 23 Mar 2011 04:21:08 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 92DCA3A6802 for <siprec@ietf.org>; Wed, 23 Mar 2011 04:21:08 -0700 (PDT)
X-AuditID: c1b4fb39-b7c6dae0000023f2-09-4d89d801e468
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 81.66.09202.108D98D4; Wed, 23 Mar 2011 12:22:41 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Wed, 23 Mar 2011 12:22:40 +0100
Received: from [131.160.37.44] (EV001E681B5FE2.lmf.ericsson.se [131.160.37.44])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 38F53245C for <siprec@ietf.org>; Wed, 23 Mar 2011 13:22:41 +0200 (EET)
Message-ID: <4D89D801.8040308@ericsson.com>
Date: Wed, 23 Mar 2011 13:22:41 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: siprec@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 23 Mar 2011 11:21:10 -0000

Hi,

the SIPREC WG requested the publication of the following draft a few
days ago. Please, find below my AD review.

https://datatracker.ietf.org/doc/draft-ietf-siprec-req/

Given that the draft contains both requirements and use cases, you may
want to edit the title so that it reads "Use Cases and Requirements for ..."

Typically, Section 1 contains the Introduction and Section 2 the
terminology. You may want to swap both sections.

Most of the requirements are phrased so that they describe capabilities
that need to be supported by the system (e.g., the mechanism MUST
provide the SRS with the means to ...) but that do not need to be
necessarily used (e.g., a particular use case may not make use of that
functionality). However, some requirements are phrased so that the
functionality needs to be used (e.g., the mechanism MUST provide the SRS
the wall clock time ...). Requirements 12, 22, 23, 27, 28, and 29 seem
to fall into the latter category. Could you please check whether that
was the intention with all those requirements?

A few requirements relate to the security and privacy related properties
of the SRC-SRS interface (e.g., requirements 24 and 29). However, the
draft does not discuss how the security and privacy of that interface
relate to the security and privacy level used for the CS being recorded.
For example, can the confidentiality level of the media going from the
SRC and the SRS be lower than that of the media flowing between the
actual participants of the CS? If you decide there should not be a
requirement on this area, you need to at least discuss this issue
(probably in Sections 6 or 7).

Once you address these comments, I will request the IETF-wide last call
for this draft.

Thanks,

Gonzalo


From rmohanr@cisco.com  Wed Mar 23 07:29:23 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 896C93A691C for <siprec@core3.amsl.com>; Wed, 23 Mar 2011 07:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.406
X-Spam-Level: 
X-Spam-Status: No, score=-10.406 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vic25uAzCY6l for <siprec@core3.amsl.com>; Wed, 23 Mar 2011 07:29:16 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 68E0C3A6918 for <siprec@ietf.org>; Wed, 23 Mar 2011 07:29:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=19831; q=dns/txt; s=iport; t=1300890649; x=1302100249; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=vTiCz1IqXXrQzIDYLHk+D7SfA/D2EYEhPvuDnpMvvg8=; b=NQAxRGlLukD8ZD4YkJKNSqpJnz3CdXyNZiUqrxzaQ7xF3+q58tdz7ING dsHcXyl3gICvSNFV1OfcngEm9GEWUSwGgrjgfV+mr/m3DdGHjBYjCVBdQ G8Rp2Jy+HIGY3EDLXFYgbpazMEEsQityJK8sNgllQuU9QJyq7rG9kBikM s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuAAAAKhiU2Q/khNgWdsb2JhbACCYZUrjTgUAQEWJiWITZ8onBiFaQSFNYsS
X-IronPort-AV: E=Sophos;i="4.63,231,1299456000"; d="scan'208,217";a="80467586"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 23 Mar 2011 14:30:43 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2NEUb8A015673; Wed, 23 Mar 2011 14:30:43 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Mar 2011 19:59:49 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE966.C387B7CE"
Date: Wed, 23 Mar 2011 19:59:45 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Dialog state in the CS block of metadata model [wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEA==
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 23 Mar 2011 14:29:49.0019 (UTC) FILETIME=[C3BED2B0:01CBE966]
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadata model [wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 23 Mar 2011 14:29:23 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE966.C387B7CE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am still trying to understand what is the significance of this
attribute w.r.t CS. Are we saying the attribute represents the state of
CS ?

Note that CS need not be one dialog.=20

For cases like Conference where there may be different participants, if
SRC happens to be Focus how do you derive/what is "session state" ?

For cases where B2BUA acts as SRC what is "session state" ?

=20

Ram

=20

From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Parthasarathi R (partr)
Sent: Wednesday, March 23, 2011 6:13 AM
To: Leon Portman; Hutton, Andrew
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadata model
[wasRE:Progressing the architecture document]

=20

Leon,

=20

Shall we have optional "event" attribute to indicate the state change
which is similar to "event" attribute in RFC 4235.  The "event" will
include the following:

=20

1) cancelled

2) rejected

3) replaced

4) bye

5) error

6) timeout

=20

Thanks

Partha

=20

________________________________

From: Leon Portman [mailto:Leon.Portman@nice.com]
Sent: Tue 3/22/2011 9:37 PM
To: Hutton, Andrew; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was
RE:Progressing the architecture document]

It can be either application level error or dialog level errors - like
timeout or failures.=20

=20

Leon

=20

From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]=20
Sent: Tuesday, March 22, 2011 6:02 PM
To: Leon Portman; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was RE:
Progressing the architecture document]

=20

What would it be used for?

=20

Regards

Andy

	=20

________________________________

	From: Leon Portman [mailto:Leon.Portman@nice.com]=20
	Sent: 22 March 2011 14:11
	To: Parthasarathi R (partr); Hutton, Andrew
	Cc: siprec@ietf.org
	Subject: RE: Dialog state in the CS block of metadata model [was
RE: Progressing the architecture document]

	Should we have error state as well?

	=20

	Leon

	=20

	From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
On Behalf Of Parthasarathi R (partr)
	Sent: Tuesday, March 22, 2011 3:33 PM
	To: Parthasarathi R (partr); Hutton, Andrew
	Cc: siprec@ietf.org
	Subject: [siprec] Dialog state in the CS block of metadata model
[was RE: Progressing the architecture document]

	=20

	The architecture document proposes to have dialog/session state
in Metadata model. To achieve this, "session state" attribute has to be
added in the CS block of Metadata model. The possible values for session
state are

	=20

	1) Trying

	2) Proceeding

	3) Early

	4) Confirmed

	5) Terminated=20

	=20

	Please let me know in case any objection to add this attribute
in Metadata model.

	=20

	Thanks

	Partha=20

	=20

________________________________

	From: Parthasarathi R (partr)=20
	Sent: Wednesday, March 16, 2011 5:40 AM
	To: Hutton, Andrew
	Cc: Elwell, John; siprec@ietf.org
	Subject: RE: Progressing the architecture document

	> -----Original Message-----
	> From: siprec-bounces@ietf.org
	> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
(partr)
	> Sent: 14 March 2011 17:05
	> To: Elwell, John; siprec@ietf.org
	> Subject: Re: [siprec] Progressing the architecture document

	>=20
	> Sec 4.3.1 whether 3rd bullet is required?
	>=20
=09
	[AndyH]I assume it is as for example I assume it would be
necessary to record early-media and update the SRS when the dialog
changes to the confirmed or terminated state. Does not seem to be in the
metadata draft though. In the end I will either remove these bullets or
align with the metadata draft.
	<Partha> It is a good point. Dialog state shall be added as one
of the optional attribute in CS metadata block with default value as
mid-dialog. This helps to differentiate between early dialog (ringback)
vs mid-dialog (normal conversation) in recording. In case of no
objection for this attribute in metadata model, we will add it. We will
work out metadata format once the consensus occurs for metadata model.
In case required, we will span separate mail thread to close this issue
</Partha>


------_=_NextPart_001_01CBE966.C387B7CE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><title>RE: Progressing the architecture =
document</title><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	font-family:"Tahoma","sans-serif";}
span.emailstyle20
	{mso-style-name:emailstyle20;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.emailstyle21
	{mso-style-name:emailstyle21;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I am still trying to understand what is the significance of this =
attribute w.r.t CS. Are we saying the attribute represents the state of =
CS ?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Note that CS need not be one dialog. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>For cases like Conference where there may be different participants, =
if SRC happens to be Focus how do you derive/what is &#8220;session =
state&#8221; ?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>For cases where B2BUA acts as SRC what is &#8220;session state&#8221; =
?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Ram<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] <b>On Behalf Of =
</b>Parthasarathi R (partr)<br><b>Sent:</b> Wednesday, March 23, 2011 =
6:13 AM<br><b>To:</b> Leon Portman; Hutton, Andrew<br><b>Cc:</b> =
siprec@ietf.org<br><b>Subject:</b> Re: [siprec] Dialog state in the CS =
block of metadata model [wasRE:Progressing the architecture =
document]<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
id=3DidOWAReplyText12087><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>L=
eon,</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Shall we =
have optional&nbsp;&quot;event&quot; attribute to indicate the state =
change which is similar to &quot;event&quot;&nbsp;attribute in RFC =
4235.&nbsp; The &quot;event&quot; will include the =
following:</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>1) =
cancelled</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>2) =
rejected</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>3) =
replaced</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>4) =
bye</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>5) =
error</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>6) =
timeout</span><o:p></o:p></p></div></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Thanks</span>=
<o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Partha</span>=
<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></div></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Leon Portman [mailto:Leon.Portman@nice.com]<br><b>Sent:</b> Tue =
3/22/2011 9:37 PM<br><b>To:</b> Hutton, Andrew; Parthasarathi R =
(partr)<br><b>Cc:</b> siprec@ietf.org<br><b>Subject:</b> RE: Dialog =
state in the CS block of metadata model [was RE:Progressing the =
architecture document]</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>It can be either application level error or dialog level errors =
&#8211; like timeout or failures. </span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Leon</span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com] =
<br><b>Sent:</b> Tuesday, March 22, 2011 6:02 PM<br><b>To:</b> Leon =
Portman; Parthasarathi R (partr)<br><b>Cc:</b> =
siprec@ietf.org<br><b>Subject:</b> RE: Dialog state in the CS block of =
metadata model [was RE: Progressing the architecture =
document]</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Wh=
at would it be used for?</span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Re=
gards</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>An=
dy</span><o:p></o:p></p><blockquote =
style=3D'border:none;border-right:solid blue 1.5pt;padding:0in 0in 0in =
0in;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.=
0pt'><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Leon Portman [mailto:Leon.Portman@nice.com] <br><b>Sent:</b> 22 March =
2011 14:11<br><b>To:</b> Parthasarathi R (partr); Hutton, =
Andrew<br><b>Cc:</b> siprec@ietf.org<br><b>Subject:</b> RE: Dialog state =
in the CS block of metadata model [was RE: Progressing the architecture =
document]</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Should we have error state as well?</span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Leon</span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] <b>On Behalf Of =
</b>Parthasarathi R (partr)<br><b>Sent:</b> Tuesday, March 22, 2011 3:33 =
PM<br><b>To:</b> Parthasarathi R (partr); Hutton, Andrew<br><b>Cc:</b> =
siprec@ietf.org<br><b>Subject:</b> [siprec] Dialog state in the CS block =
of metadata model [was RE: Progressing the architecture =
document]</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Th=
e architecture document proposes to have dialog/session state in =
Metadata model. To achieve this, &quot;session state&quot; attribute has =
to be added in the CS block of Metadata model. The possible values for =
session state are</span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>1)=
 Trying</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>2)=
 Proceeding</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>3)=
 Early</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>4)=
 Confirmed</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>5)=
 Terminated&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Pl=
ease let me know in case any objection to add this attribute in Metadata =
model.</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Th=
anks</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Pa=
rtha&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></div><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Parthasarathi R (partr) <br><b>Sent:</b> Wednesday, March 16, 2011 5:40 =
AM<br><b>To:</b> Hutton, Andrew<br><b>Cc:</b> Elwell, John; =
siprec@ietf.org<br><b>Subject:</b> RE: Progressing the architecture =
document</span><o:p></o:p></p><div><p><span =
style=3D'font-size:10.0pt'>&gt; -----Original Message-----<br>&gt; From: =
<a =
href=3D"mailto:siprec-bounces@ietf.org">siprec-bounces@ietf.org</a><br>&g=
t; [<a =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</a=
>] On Behalf Of Parthasarathi R (partr)<br>&gt; Sent: 14 March 2011 =
17:05<br>&gt; To: Elwell, John; <a =
href=3D"mailto:siprec@ietf.org">siprec@ietf.org</a><br>&gt; Subject: Re: =
[siprec] Progressing the architecture =
document</span><o:p></o:p></p><p><span =
style=3D'font-size:10.0pt'>&gt;&nbsp;<br>&gt; Sec 4.3.1 whether 3rd =
bullet is required?<br>&gt;&nbsp;<br><br>[AndyH]I assume it is as for =
example I assume it would be necessary to record early-media and update =
the SRS when the dialog changes to the confirmed or terminated state. =
Does not seem to be in the metadata draft though. In the end I will =
either remove these bullets or align with the metadata =
draft.<br>&lt;Partha&gt; It is a good point. Dialog state shall be added =
as one of the&nbsp;optional&nbsp;attribute in CS metadata block with =
default value as mid-dialog. This helps to differentiate between early =
dialog (ringback) vs mid-dialog (normal conversation) in recording. In =
case of no objection for this attribute in metadata model, we will add =
it. We will work out metadata format once the consensus occurs for =
metadata model. In case required, we will span separate mail thread to =
close this issue =
&lt;/Partha&gt;</span><o:p></o:p></p></div></blockquote></div></div></div=
></body></html>
------_=_NextPart_001_01CBE966.C387B7CE--

From partr@cisco.com  Wed Mar 23 19:34:26 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA2093A67D1 for <siprec@core3.amsl.com>; Wed, 23 Mar 2011 19:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.327
X-Spam-Level: 
X-Spam-Status: No, score=-9.327 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWEtvrGOzibA for <siprec@core3.amsl.com>; Wed, 23 Mar 2011 19:34:18 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 025EE3A67B7 for <siprec@ietf.org>; Wed, 23 Mar 2011 19:34:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=24718; q=dns/txt; s=iport; t=1300934151; x=1302143751; h=mime-version:subject:date:message-id:references:from:to: cc; bh=N1Q7XGj77hAnRIpK1WUyxxVrjuV9cOCq4SvNJBnaKpI=; b=I2Z1rLdhU4AsnqHat+dr3tvKJ9cFP0yBYYngdmjEZhWBmabnebIH1DKX iqTTvD3ol6LO2BXf5nRt756sLtGMdwccALtoj3lY1e5Nrn+WBHvZD/Trx 4hJ0hg1aMC0WONUGzN/XryZNSib6OybVTaDH9aOgudZEbHcyPeu8+7mev Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As0AAO5Kik2Q/khLgWdsb2JhbACCX5UsjF1aFAEBFiYliE2dEJw3hWkEhTWLEg
X-IronPort-AV: E=Sophos;i="4.63,235,1299456000"; d="scan'208,217";a="80543599"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 24 Mar 2011 02:35:50 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2O2ZnkX005174; Thu, 24 Mar 2011 02:35:49 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 24 Mar 2011 08:05:48 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBE9CC.2F36B420"
Date: Thu, 24 Mar 2011 08:05:48 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Dialog state in the CS block of metadata model [wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOF
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com> <35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 24 Mar 2011 02:35:48.0909 (UTC) FILETIME=[2F768DD0:01CBE9CC]
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadata model [wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 24 Mar 2011 02:34:26 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE9CC.2F36B420
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Ram,
=20
Please read inline.
=20
Thanks
Partha

________________________________

From: Ram Mohan R (rmohanr)
Sent: Wed 3/23/2011 7:59 PM
To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
Cc: siprec@ietf.org
Subject: RE: [siprec] Dialog state in the CS block of metadata model =
[wasRE:Progressing the architecture document]



I am still trying to understand what is the significance of this =
attribute w.r.t CS. Are we saying the attribute represents the state of =
CS ?

Note that CS need not be one dialog.=20

<Partha>  The attribute is to show the state of CS only. As it is not =
single dialog, I have mentioned as session state attribute </Partha>

For cases like Conference where there may be different participants, if =
SRC happens to be Focus how do you derive/what is "session state" ?

<Partha> I really don't know whether it is generic. My thought =
processing of session state for conference is as follows:

=20

1) First participant of conference early media (ivr play) may be =
considered as "early" state of session.

2) The session state is chaged to confirmed in case any one of the =
participant joined in the conference.=20

3) The session state is move to terminated when the last participant =
moved out of the conference.=20

=20

Please let me know in case other way to represent the session state of =
conference </partha>

=20

For cases where B2BUA acts as SRC what is "session state" ?

<partha> It looks straight forward for me. In B2BUA case ,=20

1) The stage where in two party is not connected, it is considered as =
early state.

2) when both are connected, it is confirmed state

3) In case of BYE received from any one of the party, then CS is =
considered as terminated state

=20

Please note that this is applicable for 3PCC as well.   </partha>

=20

Ram

=20

From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf =
Of Parthasarathi R (partr)
Sent: Wednesday, March 23, 2011 6:13 AM
To: Leon Portman; Hutton, Andrew
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadata model =
[wasRE:Progressing the architecture document]

=20

Leon,

=20

Shall we have optional "event" attribute to indicate the state change =
which is similar to "event" attribute in RFC 4235.  The "event" will =
include the following:

=20

1) cancelled

2) rejected

3) replaced

4) bye

5) error

6) timeout

=20

Thanks

Partha

=20

________________________________

From: Leon Portman [mailto:Leon.Portman@nice.com]
Sent: Tue 3/22/2011 9:37 PM
To: Hutton, Andrew; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was =
RE:Progressing the architecture document]

It can be either application level error or dialog level errors - like =
timeout or failures.=20

=20

Leon

=20

From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]=20
Sent: Tuesday, March 22, 2011 6:02 PM
To: Leon Portman; Parthasarathi R (partr)
Cc: siprec@ietf.org
Subject: RE: Dialog state in the CS block of metadata model [was RE: =
Progressing the architecture document]

=20

What would it be used for?

=20

Regards

Andy

	=20

________________________________

	From: Leon Portman [mailto:Leon.Portman@nice.com]=20
	Sent: 22 March 2011 14:11
	To: Parthasarathi R (partr); Hutton, Andrew
	Cc: siprec@ietf.org
	Subject: RE: Dialog state in the CS block of metadata model [was RE: =
Progressing the architecture document]

	Should we have error state as well?

	=20

	Leon

	=20

	From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On =
Behalf Of Parthasarathi R (partr)
	Sent: Tuesday, March 22, 2011 3:33 PM
	To: Parthasarathi R (partr); Hutton, Andrew
	Cc: siprec@ietf.org
	Subject: [siprec] Dialog state in the CS block of metadata model [was =
RE: Progressing the architecture document]

	=20

	The architecture document proposes to have dialog/session state in =
Metadata model. To achieve this, "session state" attribute has to be =
added in the CS block of Metadata model. The possible values for session =
state are

	=20

	1) Trying

	2) Proceeding

	3) Early

	4) Confirmed

	5) Terminated=20

	=20

	Please let me know in case any objection to add this attribute in =
Metadata model.

	=20

	Thanks

	Partha=20

	=20

________________________________

	From: Parthasarathi R (partr)=20
	Sent: Wednesday, March 16, 2011 5:40 AM
	To: Hutton, Andrew
	Cc: Elwell, John; siprec@ietf.org
	Subject: RE: Progressing the architecture document

	> -----Original Message-----
	> From: siprec-bounces@ietf.org
	> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
	> Sent: 14 March 2011 17:05
	> To: Elwell, John; siprec@ietf.org
	> Subject: Re: [siprec] Progressing the architecture document

	>=20
	> Sec 4.3.1 whether 3rd bullet is required?
	>=20
=09
	[AndyH]I assume it is as for example I assume it would be necessary to =
record early-media and update the SRS when the dialog changes to the =
confirmed or terminated state. Does not seem to be in the metadata draft =
though. In the end I will either remove these bullets or align with the =
metadata draft.
	<Partha> It is a good point. Dialog state shall be added as one of the =
optional attribute in CS metadata block with default value as =
mid-dialog. This helps to differentiate between early dialog (ringback) =
vs mid-dialog (normal conversation) in recording. In case of no =
objection for this attribute in metadata model, we will add it. We will =
work out metadata format once the consensus occurs for metadata model. =
In case required, we will span separate mail thread to close this issue =
</Partha>


------_=_NextPart_001_01CBE9CC.2F36B420
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: Progressing the architecture =
document</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928">=0A=
<STYLE><!--=0A=
                      =0A=
font-face=0A=
	{font-family:"Cambria Math";}=0A=
font-face=0A=
	{font-family:Calibri;}=0A=
font-face=0A=
	{font-family:Tahoma;}=0A=
                       =0A=
p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=
	{margin:0in;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:12.0pt;=0A=
	font-family:"Times New Roman","serif";}=0A=
a:link, span.MsoHyperlink=0A=
	{=0A=
	color:blue;=0A=
	text-decoration:underline;}=0A=
a:visited, span.MsoHyperlinkFollowed=0A=
	{=0A=
	color:purple;=0A=
	text-decoration:underline;}=0A=
p=0A=
	{=0A=
	margin-right:0in;=0A=
	margin-left:0in;=0A=
	font-size:12.0pt;=0A=
	font-family:"Times New Roman","serif";}=0A=
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate=0A=
	{=0A=
	margin:0in;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:8.0pt;=0A=
	font-family:"Tahoma","sans-serif";}=0A=
span.BalloonTextChar=0A=
	{=0A=
	font-family:"Tahoma","sans-serif";}=0A=
p.msochpdefault, li.msochpdefault, div.msochpdefault=0A=
	{=0A=
	margin-right:0in;=0A=
	margin-left:0in;=0A=
	font-size:10.0pt;=0A=
	font-family:"Times New Roman","serif";}=0A=
span.balloontextchar0=0A=
	{=0A=
	font-family:"Tahoma","sans-serif";}=0A=
span.emailstyle20=0A=
	{=0A=
	font-family:"Calibri","sans-serif";=0A=
	color:#1F497D;}=0A=
span.emailstyle21=0A=
	{=0A=
	font-family:"Calibri","sans-serif";=0A=
	color:#1F497D;}=0A=
span.EmailStyle24=0A=
	{=0A=
	font-family:"Calibri","sans-serif";=0A=
	color:#1F497D;}=0A=
.MsoChpDefault=0A=
	{=0A=
	font-size:10.0pt;}=0A=
=0A=
div.WordSection1=0A=
	{page:WordSection1;}=0A=
--></STYLE>=0A=
</HEAD>=0A=
<BODY lang=3DEN-US link=3Dblue vLink=3Dpurple>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText41749>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 =
face=3DArial>Ram,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Please read =
inline.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> Ram Mohan R =
(rmohanr)<BR><B>Sent:</B> Wed 3/23/2011 7:59 PM<BR><B>To:</B> =
Parthasarathi R (partr); Leon Portman; Hutton, Andrew<BR><B>Cc:</B> =
siprec@ietf.org<BR><B>Subject:</B> RE: [siprec] Dialog state in the CS =
block of metadata model [wasRE:Progressing the architecture =
document]<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<DIV class=3DWordSection1>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">I am still trying to understand what is =
the significance of this attribute w.r.t CS. Are we saying the attribute =
represents the state of CS ?</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Note that CS need not be one dialog. =
</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">&lt;Partha&gt;&nbsp; The attribute is =
to show the state of CS only.&nbsp;As it is not single dialog, I have =
mentioned as session state attribute&nbsp;&lt;/Partha&gt;</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">For cases like Conference where there =
may be different participants, if SRC happens to be Focus how do you =
derive/what is &#8220;session state&#8221; ?</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">&lt;Partha&gt; I really don't know =
whether it is generic. My thought processing&nbsp;of session state for =
conference is as follows:</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">1) First participant of conference =
early media (ivr play) may be considered as "early" state of =
session.</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">2)&nbsp;The </SPAN><SPAN =
style=3D"FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: =
11pt">session state is&nbsp;chaged to confirmed in case any one of the =
participant joined in the conference. </SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">3) The session state is move to =
terminated when the last participant moved out of the conference. =
</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Please let me know in case other way to =
represent the session state of conference &lt;/partha&gt;</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">For cases where B2BUA acts as SRC what =
is &#8220;session state&#8221; ?</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">&lt;partha&gt; It looks straight =
forward for me. In B2BUA case ,&nbsp;</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">1) The stage where in two party is not =
connected,&nbsp;it is considered as early state.</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">2) when&nbsp;both are connected, it is =
confirmed state</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">3) In case of BYE received from any one =
of the party, then CS is considered as&nbsp;terminated state</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Please note that&nbsp;this is =
applicable&nbsp;for 3PCC as =
well.&nbsp;&nbsp;&nbsp;&lt;/partha&gt;</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Ram</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN>&nbsp;</P>=0A=
<DIV style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; =
PADDING-BOTTOM: 0in; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0in">=0A=
<DIV>=0A=
<DIV style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; =
PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">=0A=
<P class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: =
'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> =
siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] <B>On Behalf Of =
</B>Parthasarathi R (partr)<BR><B>Sent:</B> Wednesday, March 23, 2011 =
6:13 AM<BR><B>To:</B> Leon Portman; Hutton, Andrew<BR><B>Cc:</B> =
siprec@ietf.org<BR><B>Subject:</B> Re: [siprec] Dialog state in the CS =
block of metadata model [wasRE:Progressing the architecture =
document]</SPAN></P></DIV></DIV>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<DIV id=3DidOWAReplyText12087>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: black; FONT-SIZE: 10pt">Leon,</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
FONT-SIZE: 10pt">Shall we have optional&nbsp;"event" attribute to =
indicate the state change which is similar to "event"&nbsp;attribute in =
RFC 4235.&nbsp; The "event" will include the following:</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
FONT-SIZE: 10pt">1) cancelled</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
FONT-SIZE: 10pt">2) rejected</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
FONT-SIZE: 10pt">3) replaced</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
FONT-SIZE: 10pt">4) bye</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
FONT-SIZE: 10pt">5) error</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
FONT-SIZE: 10pt">6) timeout</SPAN></P></DIV></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
FONT-SIZE: 10pt">Thanks</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
FONT-SIZE: 10pt">Partha</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal align=3Dcenter>=0A=
<HR align=3Dcenter SIZE=3D2 width=3D"100%">=0A=
</DIV></DIV>=0A=
<DIV>=0A=
<P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: =
10pt">From:</SPAN></B><SPAN style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; =
FONT-SIZE: 10pt"> Leon Portman =
[mailto:Leon.Portman@nice.com]<BR><B>Sent:</B> Tue 3/22/2011 9:37 =
PM<BR><B>To:</B> Hutton, Andrew; Parthasarathi R (partr)<BR><B>Cc:</B> =
siprec@ietf.org<BR><B>Subject:</B> RE: Dialog state in the CS block of =
metadata model [was RE:Progressing the architecture =
document]</SPAN></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">It can be either application level =
error or dialog level errors &#8211; like timeout or failures. =
</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Leon</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<DIV>=0A=
<DIV style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; =
PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">=0A=
<P class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: =
'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Hutton, =
Andrew [mailto:andrew.hutton@siemens-enterprise.com] <BR><B>Sent:</B> =
Tuesday, March 22, 2011 6:02 PM<BR><B>To:</B> Leon Portman; =
Parthasarathi R (partr)<BR><B>Cc:</B> siprec@ietf.org<BR><B>Subject:</B> =
RE: Dialog state in the CS block of metadata model [was RE: Progressing =
the architecture document]</SPAN></P></DIV></DIV>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">What would it be used for?</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Regards</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Andy</SPAN></P>=0A=
<BLOCKQUOTE style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium =
none; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; PADDING-LEFT: =
0in; PADDING-RIGHT: 0in; BORDER-TOP: medium none; BORDER-RIGHT: blue =
1.5pt solid; PADDING-TOP: 0in">=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal align=3Dcenter>=0A=
<HR align=3Dcenter SIZE=3D2 width=3D"100%">=0A=
</DIV>=0A=
<P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: =
10pt">From:</SPAN></B><SPAN style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; =
FONT-SIZE: 10pt"> Leon Portman [mailto:Leon.Portman@nice.com] =
<BR><B>Sent:</B> 22 March 2011 14:11<BR><B>To:</B> Parthasarathi R =
(partr); Hutton, Andrew<BR><B>Cc:</B> siprec@ietf.org<BR><B>Subject:</B> =
RE: Dialog state in the CS block of metadata model [was RE: Progressing =
the architecture document]</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Should we have error state as =
well?</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt">Leon</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<DIV>=0A=
<DIV style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; =
PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">=0A=
<P class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: =
'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> =
siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] <B>On Behalf Of =
</B>Parthasarathi R (partr)<BR><B>Sent:</B> Tuesday, March 22, 2011 3:33 =
PM<BR><B>To:</B> Parthasarathi R (partr); Hutton, Andrew<BR><B>Cc:</B> =
siprec@ietf.org<BR><B>Subject:</B> [siprec] Dialog state in the CS block =
of metadata model [was RE: Progressing the architecture =
document]</SPAN></P></DIV></DIV>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">The architecture document proposes to have =
dialog/session state in Metadata model. To achieve this, "session state" =
attribute has to be added in the CS block of Metadata model. The =
possible values for session state are</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">1) Trying</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">2) Proceeding</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">3) Early</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">4) Confirmed</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">5) Terminated&nbsp;</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Please let me know in case any objection =
to add this attribute in Metadata model.</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Thanks</SPAN></P>=0A=
<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Arial','sans-serif'; =
COLOR: blue; FONT-SIZE: 10pt">Partha&nbsp;</SPAN></P>=0A=
<P class=3DMsoNormal>&nbsp;</P>=0A=
<DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal align=3Dcenter>=0A=
<HR align=3Dcenter SIZE=3D2 width=3D"100%">=0A=
</DIV>=0A=
<P class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: =
'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN =
style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> =
Parthasarathi R (partr) <BR><B>Sent:</B> Wednesday, March 16, 2011 5:40 =
AM<BR><B>To:</B> Hutton, Andrew<BR><B>Cc:</B> Elwell, John; =
siprec@ietf.org<BR><B>Subject:</B> RE: Progressing the architecture =
document</SPAN></P>=0A=
<DIV>=0A=
<P><SPAN style=3D"FONT-SIZE: 10pt">&gt; -----Original =
Message-----<BR>&gt; From: <A =
href=3D"mailto:siprec-bounces@ietf.org">siprec-bounces@ietf.org</A><BR>&g=
t; [<A =
href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.org</A=
>] On Behalf Of Parthasarathi R (partr)<BR>&gt; Sent: 14 March 2011 =
17:05<BR>&gt; To: Elwell, John; <A =
href=3D"mailto:siprec@ietf.org">siprec@ietf.org</A><BR>&gt; Subject: Re: =
[siprec] Progressing the architecture document</SPAN></P>=0A=
<P><SPAN style=3D"FONT-SIZE: 10pt">&gt;&nbsp;<BR>&gt; Sec 4.3.1 whether =
3rd bullet is required?<BR>&gt;&nbsp;<BR><BR>[AndyH]I assume it is as =
for example I assume it would be necessary to record early-media and =
update the SRS when the dialog changes to the confirmed or terminated =
state. Does not seem to be in the metadata draft though. In the end I =
will either remove these bullets or align with the metadata =
draft.<BR>&lt;Partha&gt; It is a good point. Dialog state shall be added =
as one of the&nbsp;optional&nbsp;attribute in CS metadata block with =
default value as mid-dialog. This helps to differentiate between early =
dialog (ringback) vs mid-dialog (normal conversation) in recording. In =
case of no objection for this attribute in metadata model, we will add =
it. We will work out metadata format once the consensus occurs for =
metadata model. In case required, we will span separate mail thread to =
close this issue =
&lt;/Partha&gt;</SPAN></P></DIV></BLOCKQUOTE></DIV></DIV></DIV></DIV></BO=
DY></HTML>
------_=_NextPart_001_01CBE9CC.2F36B420--

From john.elwell@siemens-enterprise.com  Thu Mar 24 09:32:15 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5709728C0F8 for <siprec@core3.amsl.com>; Thu, 24 Mar 2011 09:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JR6LJYOLROMp for <siprec@core3.amsl.com>; Thu, 24 Mar 2011 09:32:14 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 9564828C0CE for <siprec@ietf.org>; Thu, 24 Mar 2011 09:32:13 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3865236; Thu, 24 Mar 2011 17:33:38 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 3BC931EB82AE; Thu, 24 Mar 2011 17:33:38 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 24 Mar 2011 17:33:38 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, Leon Portman <Leon.Portman@nice.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Date: Thu, 24 Mar 2011 17:33:37 +0100
Thread-Topic: [siprec] Dialog state in the CS block of metadata model [wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+A=
Message-ID: <A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com> <35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com> <A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadata model	[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 24 Mar 2011 16:32:15 -0000

This discussion gives me some concerns, echoing to some extent what Ram is =
saying.

SIPREC is about session recording, where a session is the information excha=
nged between participants in a CS (the media streams) plus metadata. The me=
tadata should provide additional information about the CS. This means infor=
mation about the communication SESSION, not about the SIP dialog that is us=
ed to control that session. With this in mind, consider the following point=
s, some of which have already been raised:

1. There may be more than one SIP dialog involved if the SRC is at a B2BUA =
or conference focus.

2. Does the CS necessarily need to be controlled by SIP? For example, it co=
uld be a PSTN call, an RTC-Web call or a Jingle call. None of these preclud=
e using SIP for the RS (that is what the charter of SIPREC is all about - a=
 SIP-based RS).

3. Somebody retrieving and playing back a recorded CS will be interested in=
 session-related events like participants leaving and joining (including th=
e first participants joining at the start of the CS and the last participan=
ts leaving a the end of the CS), media streams starting and ending and part=
icipants starting or stopping receipt of a media stream. In other words, ch=
anges of SESSION state, not dialog state.

4. Some of the SIP dialog states just don't seem relevant. The distinction =
between early dialog and full dialog in SIP does not necessarily correspond=
ing to any meaningful state change of the session. For example, A makes a c=
all to B and B answers and starts sending media. A receives and renders med=
ia (perhaps it has already received SDP answer, allowing it to verify the s=
ource of the media). Then A receives the 200 OK (transitioning from an earl=
y dialog to a full dialog) and continues to receive media. So although ther=
e is a dialog state change, there is not really a session state change.

The bit about dialog state in the architecture draft is, in my opinion, a l=
egacy from some earlier discussions, before we started having the metadata =
discussions. I think the metadata discussions have taken us in the right di=
rection.

John (as individual)


> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 24 March 2011 02:36
> To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Dialog state in the CS block of=20
> metadata model [wasRE:Progressing the architecture document]
>=20
> Ram,
> =20
> Please read inline.
> =20
> Thanks
> Partha
>=20
> ________________________________
>=20
> From: Ram Mohan R (rmohanr)
> Sent: Wed 3/23/2011 7:59 PM
> To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of=20
> metadata model [wasRE:Progressing the architecture document]
>=20
>=20
>=20
> I am still trying to understand what is the significance of=20
> this attribute w.r.t CS. Are we saying the attribute=20
> represents the state of CS ?
>=20
> Note that CS need not be one dialog.=20
>=20
> <Partha>  The attribute is to show the state of CS only. As=20
> it is not single dialog, I have mentioned as session state=20
> attribute </Partha>
>=20
> For cases like Conference where there may be different=20
> participants, if SRC happens to be Focus how do you=20
> derive/what is "session state" ?
>=20
> <Partha> I really don't know whether it is generic. My=20
> thought processing of session state for conference is as follows:
>=20
> =20
>=20
> 1) First participant of conference early media (ivr play) may=20
> be considered as "early" state of session.
>=20
> 2) The session state is chaged to confirmed in case any one=20
> of the participant joined in the conference.=20
>=20
> 3) The session state is move to terminated when the last=20
> participant moved out of the conference.=20
>=20
> =20
>=20
> Please let me know in case other way to represent the session=20
> state of conference </partha>
>=20
> =20
>=20
> For cases where B2BUA acts as SRC what is "session state" ?
>=20
> <partha> It looks straight forward for me. In B2BUA case ,=20
>=20
> 1) The stage where in two party is not connected, it is=20
> considered as early state.
>=20
> 2) when both are connected, it is confirmed state
>=20
> 3) In case of BYE received from any one of the party, then CS=20
> is considered as terminated state
>=20
> =20
>=20
> Please note that this is applicable for 3PCC as well.   </partha>
>=20
> =20
>=20
> Ram
>=20
> =20
>=20
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: Wednesday, March 23, 2011 6:13 AM
> To: Leon Portman; Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Dialog state in the CS block of=20
> metadata model [wasRE:Progressing the architecture document]
>=20
> =20
>=20
> Leon,
>=20
> =20
>=20
> Shall we have optional "event" attribute to indicate the=20
> state change which is similar to "event" attribute in RFC=20
> 4235.  The "event" will include the following:
>=20
> =20
>=20
> 1) cancelled
>=20
> 2) rejected
>=20
> 3) replaced
>=20
> 4) bye
>=20
> 5) error
>=20
> 6) timeout
>=20
> =20
>=20
> Thanks
>=20
> Partha
>=20
> =20
>=20
> ________________________________
>=20
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Tue 3/22/2011 9:37 PM
> To: Hutton, Andrew; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Dialog state in the CS block of metadata model=20
> [was RE:Progressing the architecture document]
>=20
> It can be either application level error or dialog level=20
> errors - like timeout or failures.=20
>=20
> =20
>=20
> Leon
>=20
> =20
>=20
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]=20
> Sent: Tuesday, March 22, 2011 6:02 PM
> To: Leon Portman; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Dialog state in the CS block of metadata model=20
> [was RE: Progressing the architecture document]
>=20
> =20
>=20
> What would it be used for?
>=20
> =20
>=20
> Regards
>=20
> Andy
>=20
> 	=20
>=20
> ________________________________
>=20
> 	From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> 	Sent: 22 March 2011 14:11
> 	To: Parthasarathi R (partr); Hutton, Andrew
> 	Cc: siprec@ietf.org
> 	Subject: RE: Dialog state in the CS block of metadata=20
> model [was RE: Progressing the architecture document]
>=20
> 	Should we have error state as well?
>=20
> 	=20
>=20
> 	Leon
>=20
> 	=20
>=20
> 	From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> 	Sent: Tuesday, March 22, 2011 3:33 PM
> 	To: Parthasarathi R (partr); Hutton, Andrew
> 	Cc: siprec@ietf.org
> 	Subject: [siprec] Dialog state in the CS block of=20
> metadata model [was RE: Progressing the architecture document]
>=20
> 	=20
>=20
> 	The architecture document proposes to have=20
> dialog/session state in Metadata model. To achieve this,=20
> "session state" attribute has to be added in the CS block of=20
> Metadata model. The possible values for session state are
>=20
> 	=20
>=20
> 	1) Trying
>=20
> 	2) Proceeding
>=20
> 	3) Early
>=20
> 	4) Confirmed
>=20
> 	5) Terminated=20
>=20
> 	=20
>=20
> 	Please let me know in case any objection to add this=20
> attribute in Metadata model.
>=20
> 	=20
>=20
> 	Thanks
>=20
> 	Partha=20
>=20
> 	=20
>=20
> ________________________________
>=20
> 	From: Parthasarathi R (partr)=20
> 	Sent: Wednesday, March 16, 2011 5:40 AM
> 	To: Hutton, Andrew
> 	Cc: Elwell, John; siprec@ietf.org
> 	Subject: RE: Progressing the architecture document
>=20
> 	> -----Original Message-----
> 	> From: siprec-bounces@ietf.org
> 	> [mailto:siprec-bounces@ietf.org] On Behalf Of=20
> Parthasarathi R (partr)
> 	> Sent: 14 March 2011 17:05
> 	> To: Elwell, John; siprec@ietf.org
> 	> Subject: Re: [siprec] Progressing the architecture document
>=20
> 	>=20
> 	> Sec 4.3.1 whether 3rd bullet is required?
> 	>=20
> =09
> 	[AndyH]I assume it is as for example I assume it would=20
> be necessary to record early-media and update the SRS when=20
> the dialog changes to the confirmed or terminated state. Does=20
> not seem to be in the metadata draft though. In the end I=20
> will either remove these bullets or align with the metadata draft.
> 	<Partha> It is a good point. Dialog state shall be=20
> added as one of the optional attribute in CS metadata block=20
> with default value as mid-dialog. This helps to differentiate=20
> between early dialog (ringback) vs mid-dialog (normal=20
> conversation) in recording. In case of no objection for this=20
> attribute in metadata model, we will add it. We will work out=20
> metadata format once the consensus occurs for metadata model.=20
> In case required, we will span separate mail thread to close=20
> this issue </Partha>
>=20
> =

From john.elwell@siemens-enterprise.com  Fri Mar 25 03:16:11 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EDFF3A6998 for <siprec@core3.amsl.com>; Fri, 25 Mar 2011 03:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDsf0LvAchCX for <siprec@core3.amsl.com>; Fri, 25 Mar 2011 03:16:10 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 5DD333A67B0 for <siprec@ietf.org>; Fri, 25 Mar 2011 03:16:10 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3884004 for siprec@ietf.org; Fri, 25 Mar 2011 11:17:45 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id EDB8623F0290 for <siprec@ietf.org>; Fri, 25 Mar 2011 11:17:44 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 25 Mar 2011 11:17:45 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Fri, 25 Mar 2011 11:17:44 +0100
Thread-Topic: Meeting materials for SIPREC session 2011-03-31 09.00-11.30 GMT+2
Thread-Index: Acvq1eFpVXiqB59KSnuEuF+DouC05w==
Message-ID: <A444A0F8084434499206E78C106220CA086AA5598B@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] Meeting materials for SIPREC session 2011-03-31 09.00-11.30 GMT+2
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 25 Mar 2011 10:16:11 -0000

Slides for metadata model and metadata format have already been uploaded to=
 the meeting materials repository:
https://datatracker.ietf.org/meeting/80/materials.html

Thanks to Partha for supplying these in good time.

1. Will other presenters please provide their slides a.s.a.p, or by Monday =
latest, so that the chairs can review them for making best use of meeting t=
ime? In particular, if we need a slot on Requirements, for addressing AD co=
mments, would Leon/Ken please let me have the slides a.s.a.p.?

2. Concerning the metadata model slides, we must focus on open issues. I se=
e several open issues listed in the slides, but no further information on t=
hese issues. Would Partha please give consideration to expanding on the ope=
n issues, by including either:
- a proposed resolution; or
- pros and cons if there are several ways forward.

3. Concerning the metadata format slides, the first 16 slides are all tutor=
ial - we should focus on open issues and next steps, so depending on time a=
vailability the chairs might ask to skip a lot of this.
Concerning the open issue on slide 19, I think this needs to be made slight=
ly clearer. My understanding was that the possibility of multiplexing on th=
e same port was mentioned as something to be considered (and possibly ruled=
 out), whereas the slide seems to assume we will be doing that and asks how=
 to represent it in the metadata. I guess the issue is primarily one for th=
e protocol milestone, and will impact that metadata model if that is the wa=
y the protocol discussions go. So perhaps it doesn't make sense to discuss =
this until the protocol discussions have taken place - currently that is la=
ter in the agenda.

John (as chair)




From Leon.Portman@nice.com  Sat Mar 26 02:29:42 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AE293A6908 for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 02:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.375
X-Spam-Level: 
X-Spam-Status: No, score=-2.375 tagged_above=-999 required=5 tests=[AWL=0.224,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ObOnGk+4HObm for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 02:29:41 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 70C0D3A6903 for <siprec@ietf.org>; Sat, 26 Mar 2011 02:29:40 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Sat, 26 Mar 2011 11:31:14 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Date: Sat, 26 Mar 2011 11:30:53 +0200
Thread-Topic: [siprec] Dialog state in the CS block of metadata model [wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcA==
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com> <35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com> <A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadata model	[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 26 Mar 2011 09:29:42 -0000

John Hello

I agree that SRS (and its application clients) interested in SESSION level =
events and not underlying DIALOG events. However we do need to support repo=
rting session state information per CS  participant that sometimes equals t=
o dialog level and sometimes not.

We could have define more application level state events like instead of TR=
YING - > RINGING etc. However they could be domain specific.

Leon

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Thursday, March 24, 2011 6:34 PM
To: Parthasarathi R (partr); Ram Mohan R (rmohanr); Leon Portman; Hutton, A=
ndrew
Cc: siprec@ietf.org
Subject: RE: [siprec] Dialog state in the CS block of metadata model [wasRE=
:Progressing the architecture document]

This discussion gives me some concerns, echoing to some extent what Ram is =
saying.

SIPREC is about session recording, where a session is the information excha=
nged between participants in a CS (the media streams) plus metadata. The me=
tadata should provide additional information about the CS. This means infor=
mation about the communication SESSION, not about the SIP dialog that is us=
ed to control that session. With this in mind, consider the following point=
s, some of which have already been raised:

1. There may be more than one SIP dialog involved if the SRC is at a B2BUA =
or conference focus.

2. Does the CS necessarily need to be controlled by SIP? For example, it co=
uld be a PSTN call, an RTC-Web call or a Jingle call. None of these preclud=
e using SIP for the RS (that is what the charter of SIPREC is all about - a=
 SIP-based RS).

3. Somebody retrieving and playing back a recorded CS will be interested in=
 session-related events like participants leaving and joining (including th=
e first participants joining at the start of the CS and the last participan=
ts leaving a the end of the CS), media streams starting and ending and part=
icipants starting or stopping receipt of a media stream. In other words, ch=
anges of SESSION state, not dialog state.

4. Some of the SIP dialog states just don't seem relevant. The distinction =
between early dialog and full dialog in SIP does not necessarily correspond=
ing to any meaningful state change of the session. For example, A makes a c=
all to B and B answers and starts sending media. A receives and renders med=
ia (perhaps it has already received SDP answer, allowing it to verify the s=
ource of the media). Then A receives the 200 OK (transitioning from an earl=
y dialog to a full dialog) and continues to receive media. So although ther=
e is a dialog state change, there is not really a session state change.

The bit about dialog state in the architecture draft is, in my opinion, a l=
egacy from some earlier discussions, before we started having the metadata =
discussions. I think the metadata discussions have taken us in the right di=
rection.

John (as individual)


> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: 24 March 2011 02:36
> To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Dialog state in the CS block of metadata model=20
> [wasRE:Progressing the architecture document]
>=20
> Ram,
> =20
> Please read inline.
> =20
> Thanks
> Partha
>=20
> ________________________________
>=20
> From: Ram Mohan R (rmohanr)
> Sent: Wed 3/23/2011 7:59 PM
> To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of metadata model=20
> [wasRE:Progressing the architecture document]
>=20
>=20
>=20
> I am still trying to understand what is the significance of this=20
> attribute w.r.t CS. Are we saying the attribute represents the state=20
> of CS ?
>=20
> Note that CS need not be one dialog.=20
>=20
> <Partha>  The attribute is to show the state of CS only. As it is not=20
> single dialog, I have mentioned as session state attribute </Partha>
>=20
> For cases like Conference where there may be different participants,=20
> if SRC happens to be Focus how do you derive/what is "session state" ?
>=20
> <Partha> I really don't know whether it is generic. My thought=20
> processing of session state for conference is as follows:
>=20
> =20
>=20
> 1) First participant of conference early media (ivr play) may be=20
> considered as "early" state of session.
>=20
> 2) The session state is chaged to confirmed in case any one of the=20
> participant joined in the conference.
>=20
> 3) The session state is move to terminated when the last participant=20
> moved out of the conference.
>=20
> =20
>=20
> Please let me know in case other way to represent the session state of=20
> conference </partha>
>=20
> =20
>=20
> For cases where B2BUA acts as SRC what is "session state" ?
>=20
> <partha> It looks straight forward for me. In B2BUA case ,
>=20
> 1) The stage where in two party is not connected, it is considered as=20
> early state.
>=20
> 2) when both are connected, it is confirmed state
>=20
> 3) In case of BYE received from any one of the party, then CS is=20
> considered as terminated state
>=20
> =20
>=20
> Please note that this is applicable for 3PCC as well.   </partha>
>=20
> =20
>=20
> Ram
>=20
> =20
>=20
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: Wednesday, March 23, 2011 6:13 AM
> To: Leon Portman; Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Dialog state in the CS block of metadata model=20
> [wasRE:Progressing the architecture document]
>=20
> =20
>=20
> Leon,
>=20
> =20
>=20
> Shall we have optional "event" attribute to indicate the state change=20
> which is similar to "event" attribute in RFC 4235.  The "event" will=20
> include the following:
>=20
> =20
>=20
> 1) cancelled
>=20
> 2) rejected
>=20
> 3) replaced
>=20
> 4) bye
>=20
> 5) error
>=20
> 6) timeout
>=20
> =20
>=20
> Thanks
>=20
> Partha
>=20
> =20
>=20
> ________________________________
>=20
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Tue 3/22/2011 9:37 PM
> To: Hutton, Andrew; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Dialog state in the CS block of metadata model [was=20
> RE:Progressing the architecture document]
>=20
> It can be either application level error or dialog level errors - like=20
> timeout or failures.
>=20
> =20
>=20
> Leon
>=20
> =20
>=20
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> Sent: Tuesday, March 22, 2011 6:02 PM
> To: Leon Portman; Parthasarathi R (partr)
> Cc: siprec@ietf.org
> Subject: RE: Dialog state in the CS block of metadata model [was RE:=20
> Progressing the architecture document]
>=20
> =20
>=20
> What would it be used for?
>=20
> =20
>=20
> Regards
>=20
> Andy
>=20
> 	=20
>=20
> ________________________________
>=20
> 	From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> 	Sent: 22 March 2011 14:11
> 	To: Parthasarathi R (partr); Hutton, Andrew
> 	Cc: siprec@ietf.org
> 	Subject: RE: Dialog state in the CS block of metadata model [was RE:=20
> Progressing the architecture document]
>=20
> 	Should we have error state as well?
>=20
> 	=20
>=20
> 	Leon
>=20
> 	=20
>=20
> 	From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> 	Sent: Tuesday, March 22, 2011 3:33 PM
> 	To: Parthasarathi R (partr); Hutton, Andrew
> 	Cc: siprec@ietf.org
> 	Subject: [siprec] Dialog state in the CS block of metadata model [was=20
> RE: Progressing the architecture document]
>=20
> 	=20
>=20
> 	The architecture document proposes to have dialog/session state in=20
> Metadata model. To achieve this, "session state" attribute has to be=20
> added in the CS block of Metadata model. The possible values for=20
> session state are
>=20
> 	=20
>=20
> 	1) Trying
>=20
> 	2) Proceeding
>=20
> 	3) Early
>=20
> 	4) Confirmed
>=20
> 	5) Terminated
>=20
> 	=20
>=20
> 	Please let me know in case any objection to add this attribute in=20
> Metadata model.
>=20
> 	=20
>=20
> 	Thanks
>=20
> 	Partha
>=20
> 	=20
>=20
> ________________________________
>=20
> 	From: Parthasarathi R (partr)=20
> 	Sent: Wednesday, March 16, 2011 5:40 AM
> 	To: Hutton, Andrew
> 	Cc: Elwell, John; siprec@ietf.org
> 	Subject: RE: Progressing the architecture document
>=20
> 	> -----Original Message-----
> 	> From: siprec-bounces@ietf.org
> 	> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R=20
> (partr)
> 	> Sent: 14 March 2011 17:05
> 	> To: Elwell, John; siprec@ietf.org
> 	> Subject: Re: [siprec] Progressing the architecture document
>=20
> 	>=20
> 	> Sec 4.3.1 whether 3rd bullet is required?
> 	>
> =09
> 	[AndyH]I assume it is as for example I assume it would be necessary=20
> to record early-media and update the SRS when the dialog changes to=20
> the confirmed or terminated state. Does not seem to be in the metadata=20
> draft though. In the end I will either remove these bullets or align=20
> with the metadata draft.
> 	<Partha> It is a good point. Dialog state shall be added as one of=20
> the optional attribute in CS metadata block with default value as=20
> mid-dialog. This helps to differentiate between early dialog=20
> (ringback) vs mid-dialog (normal
> conversation) in recording. In case of no objection for this attribute=20
> in metadata model, we will add it. We will work out metadata format=20
> once the consensus occurs for metadata model.
> In case required, we will span separate mail thread to close this=20
> issue </Partha>
>=20
>=20

From Leon.Portman@nice.com  Sat Mar 26 07:36:04 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D663D28C0D8 for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 07:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level: 
X-Spam-Status: No, score=-2.381 tagged_above=-999 required=5 tests=[AWL=0.218,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ynqXEf5DqFaJ for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 07:36:03 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 64D9E28B797 for <siprec@ietf.org>; Sat, 26 Mar 2011 07:36:03 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Sat, 26 Mar 2011 16:37:38 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "siprec@ietf.org" <siprec@ietf.org>, "Ken Rehor (krehor) (krehor@cisco.com)" <krehor@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Sat, 26 Mar 2011 16:36:48 +0200
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIA
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com>
References: <4D89D801.8040308@ericsson.com>
In-Reply-To: <4D89D801.8040308@ericsson.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 26 Mar 2011 14:36:05 -0000

Hi,

I want to touch security requirement: about security level of RS vs securit=
y level of CS. We had a long mailing list discussion (below) and it was dec=
ided not to have it, because it is more implementation details

http://www.ietf.org/mail-archive/web/siprec/current/msg01164.html

Regards

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Gonzalo Camarillo
Sent: Wednesday, March 23, 2011 1:23 PM
To: siprec@ietf.org
Subject: [siprec] AD review: draft-ietf-siprec-req-08

Hi,

the SIPREC WG requested the publication of the following draft a few days a=
go. Please, find below my AD review.

https://datatracker.ietf.org/doc/draft-ietf-siprec-req/

Given that the draft contains both requirements and use cases, you may want=
 to edit the title so that it reads "Use Cases and Requirements for ..."

Typically, Section 1 contains the Introduction and Section 2 the terminolog=
y. You may want to swap both sections.

Most of the requirements are phrased so that they describe capabilities tha=
t need to be supported by the system (e.g., the mechanism MUST provide the =
SRS with the means to ...) but that do not need to be necessarily used (e.g=
., a particular use case may not make use of that functionality). However, =
some requirements are phrased so that the functionality needs to be used (e=
.g., the mechanism MUST provide the SRS the wall clock time ...). Requireme=
nts 12, 22, 23, 27, 28, and 29 seem to fall into the latter category. Could=
 you please check whether that was the intention with all those requirement=
s?

A few requirements relate to the security and privacy related properties of=
 the SRC-SRS interface (e.g., requirements 24 and 29). However, the draft d=
oes not discuss how the security and privacy of that interface relate to th=
e security and privacy level used for the CS being recorded.
For example, can the confidentiality level of the media going from the SRC =
and the SRS be lower than that of the media flowing between the actual part=
icipants of the CS? If you decide there should not be a requirement on this=
 area, you need to at least discuss this issue (probably in Sections 6 or 7=
).

Once you address these comments, I will request the IETF-wide last call for=
 this draft.

Thanks,

Gonzalo

_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From eckelcu@cisco.com  Sat Mar 26 11:21:43 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70DB53A67D8 for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 11:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.556
X-Spam-Level: 
X-Spam-Status: No, score=-10.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gHBZlKA6Ri7 for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 11:21:42 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 62E363A67B2 for <siprec@ietf.org>; Sat, 26 Mar 2011 11:21:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=1422; q=dns/txt; s=iport; t=1301163798; x=1302373398; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=r4s4/cr6vS9wn0pm4jWfZZ22fhjMBp3wgdnDcyMWh3Y=; b=LZorRlHkucV284rAfARahW7UtQ7KWWunlEJQD9lmcRBseSg9ar2u2yv5 bWsNymtmIXUWDQ2+6gQ7zn/K8YeW26+mBXc2oX6O/GWgh/+Moln1Oa99t qq0ZFLeiPx+RJ8tho7vpKfBe4qsjdpySfWZLvgw5uSpxAGfswwEJFPxFr U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlAHACQujk2rRDoJ/2dsb2JhbACYaIx+d6Zwm1yFaQSFOosW
X-IronPort-AV: E=Sophos;i="4.63,248,1299456000"; d="scan'208";a="325085656"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-2.cisco.com with ESMTP; 26 Mar 2011 18:23:18 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2QINI9Z002504 for <siprec@ietf.org>; Sat, 26 Mar 2011 18:23:18 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 26 Mar 2011 11:23:18 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 26 Mar 2011 11:23:16 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86E9F@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: review comments on draft-ietf-siprec-architecture-01
Thread-Index: Acvr4t/8/sTKgbbNQSmx5Q79X0rBbg==
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: <siprec@ietf.org>
X-OriginalArrivalTime: 26 Mar 2011 18:23:18.0541 (UTC) FILETIME=[E14F7BD0:01CBEBE2]
Subject: [siprec] review comments on draft-ietf-siprec-architecture-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 26 Mar 2011 18:21:43 -0000

I started my review of the SIPREC drafts with the architecture document.
I have some nits and some concerns.
Let me state the concerns first.

Section 4.2 reads, "the Session Recording Client must decrypt any media
received on the Communication Session and, if required, re-encrypt the
media using a separate SRTP key for the Recording Session." Why must? I
imagine it could be done in some cases, but I do not see why it is a
must.

Section 4.2.1 reads, "Indicate support for the recording metadata event
package." I am not sure this is needed and do not think it should be
stated here.

Section 4.3.1, no sure why Dialog state of the Communication Session is
required.

Section 4.3.2, regarding the OPEN ISSUE, I think we decided on XML as
message body in re-INVITE or UPDATE.

Section 4.4 reads, "If the Session Recording Client is aware that the
remote UA is a recording aware UA then it MUST notify the UA using a SIP
based mechanism." Why MUST? It seems "should" is more appropriate as
other mechanisms may be used depending on the use case. Also, it seems
there should not be any normative language in this draft.

Section 6 reads, "SRTP is used for securing the Replicated Media." I
think other mechanisms should be allowed as well.

Nits

Section 4.2
Replace "Recording Session is a completely independent" with "Recording
Session is completely independent".

Cheers,
Charles

From eckelcu@cisco.com  Sat Mar 26 11:28:12 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96E6E3A67D7 for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 11:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.559
X-Spam-Level: 
X-Spam-Status: No, score=-10.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q8mO0OY6Q9oY for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 11:28:11 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id DBB1D3A67B2 for <siprec@ietf.org>; Sat, 26 Mar 2011 11:28:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=408; q=dns/txt; s=iport; t=1301164188; x=1302373788; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=VEq0n2QpR0rTGXRkqEeJ1GcStJ+w2jBGxIJvxd1HHvs=; b=l7ocEQmzW+XRaTZmKu2tckGiCzNtDZiVnilYsAYsoCu57jSNlBqxz0SD VMTLQLvDKcWspb88SfN72phHOOPTk2ozyennD3fLO7gcLKBZ37gIDfObq niLTUdz2aePo6v2pOQHVhuFkVJm7IeZP+2IQ9V8SvwtopFOpgDPJ9T4kr k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlAHAJQvjk2rRDoH/2dsb2JhbACYaIx+d6Zpm1yFaQSFOosW
X-IronPort-AV: E=Sophos;i="4.63,248,1299456000"; d="scan'208";a="418769038"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-1.cisco.com with ESMTP; 26 Mar 2011 18:29:15 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2QITFpT026963 for <siprec@ietf.org>; Sat, 26 Mar 2011 18:29:15 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 26 Mar 2011 11:29:15 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 26 Mar 2011 11:29:13 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA1@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: review comments in draft-ietf-siprec-req-08
Thread-Index: Acvr47UAX8D7l37XSfOnWkAVcgVa0Q==
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: <siprec@ietf.org>
X-OriginalArrivalTime: 26 Mar 2011 18:29:15.0345 (UTC) FILETIME=[B5FB7410:01CBEBE3]
Subject: [siprec] review comments in draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 26 Mar 2011 18:28:12 -0000

Section 3, it would be better to refer to arch draft for definitions
rather than repeating here and in other drafts.

Section 5, Req-024 conflicts with architecture draft. I think Req-024 is
correct and architecture document needs to be updated accordingly.

Section 6, change "although any user can terminate a CS" to "although
any user can terminate its participation in a CS."

Cheers,
Charles

From Leon.Portman@nice.com  Sat Mar 26 11:39:42 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAA193A680A for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 11:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.388
X-Spam-Level: 
X-Spam-Status: No, score=-2.388 tagged_above=-999 required=5 tests=[AWL=0.211,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zivZ6I4f-IqX for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 11:39:42 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 9D7003A67D8 for <siprec@ietf.org>; Sat, 26 Mar 2011 11:39:41 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Sat, 26 Mar 2011 20:41:17 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Sat, 26 Mar 2011 20:41:15 +0200
Thread-Topic: review comments in draft-ietf-siprec-req-08
Thread-Index: Acvr47UAX8D7l37XSfOnWkAVcgVa0QAAZH/g
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB466392@TLVMBX01.nice.com>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA1@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA1@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] review comments in draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 26 Mar 2011 18:39:43 -0000

Charles hi

Thank you very much. I agree with your comments

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Charles Eckel (eckelcu)
Sent: Saturday, March 26, 2011 8:29 PM
To: siprec@ietf.org
Subject: [siprec] review comments in draft-ietf-siprec-req-08

Section 3, it would be better to refer to arch draft for definitions rather=
 than repeating here and in other drafts.

Section 5, Req-024 conflicts with architecture draft. I think Req-024 is co=
rrect and architecture document needs to be updated accordingly.

Section 6, change "although any user can terminate a CS" to "although any u=
ser can terminate its participation in a CS."

Cheers,
Charles
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From eckelcu@cisco.com  Sat Mar 26 11:47:57 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 800F93A6812 for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 11:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.561
X-Spam-Level: 
X-Spam-Status: No, score=-10.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJ0yXWGEKmXh for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 11:47:56 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 835393A67D7 for <siprec@ietf.org>; Sat, 26 Mar 2011 11:47:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=1253; q=dns/txt; s=iport; t=1301165372; x=1302374972; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=fnk8LW2JKmKDQm4L2SwKdA0PahsUNS/emPICYwlymk0=; b=MKWWfXyDZJ3GPp9lKKrPEKHsC1WEaLRQNihyXOipEV/S+IEGIhpl2aRP T3NL5RWRHgOTQw8VLfV93Fj27jdsRNME3QWsmvPWGoI4YZ5RQ0/qv0gOb TWFZ2+vG6jcnPM5dcvfpU/rzql2rwzVzvIjEKCqNmfP7WHlLlN7vxjR5G E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlAHABs1jk2rRDoJ/2dsb2JhbACYaIx+d6Ztm1qCfIJtBIU6ixY
X-IronPort-AV: E=Sophos;i="4.63,248,1299456000"; d="scan'208";a="283217044"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 26 Mar 2011 18:49:14 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2QInEK7012788 for <siprec@ietf.org>; Sat, 26 Mar 2011 18:49:14 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 26 Mar 2011 11:49:14 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 26 Mar 2011 11:49:12 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA5@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comments on draft-portman-siprec-protocol-03
Thread-Index: Acvr5n/IFzsSBMIcSh2KPGblbWwyDA==
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: <siprec@ietf.org>
X-OriginalArrivalTime: 26 Mar 2011 18:49:14.0476 (UTC) FILETIME=[80B852C0:01CBEBE6]
Subject: [siprec] comments on draft-portman-siprec-protocol-03
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 26 Mar 2011 18:47:57 -0000

I have a few comments on this draft.

Section 2, Definitions. Reference definitions in architecture draft
instead or repeating here.

Section 4, "there are a couple" -> "there are several"

Figure 2. "RS INVITE (CallId + Participants) with SDP" seems to imply
participant info is in SIP headers. This is not the intention, is it?

Figure 4, title should change from "via SIP INFO" to via SIP UPDATE
request".

Section 5, change "does not have to have live within" to "does not have
to live within".

Section 5, remove last sentence regarding session timer.

Section 5.1.1, is it also the intention of the src feature tag that it
be used by a recording aware UA to identify/locate an SRC

Section 5.1.2, is it also the intention to be able to use this to
indicate ability to be an src or srs?

Section 5.2, reference RFC 3264.

Section 5.2, change "As SRS only receives RTP streams from SRS" to from
"SRC".

Section 5.3.2, change "may conveyed" to "may be conveyed".

Section 6.1, why is recording-aware an SDP attribute instead of a SIP
feature tag?

Section 6.3, instead of defining pref =3D "record" / "norecord" / =
"pause"
/ "resume" can we reuse indication =3D "on" / "off" / "paused"?

Cheers,
Charles
=20



From eckelcu@cisco.com  Sat Mar 26 12:03:17 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29F7C3A6817 for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 12:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.564
X-Spam-Level: 
X-Spam-Status: No, score=-10.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TAuISdND3BTP for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 12:03:16 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 2A0DE3A67F2 for <siprec@ietf.org>; Sat, 26 Mar 2011 12:03:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=1203; q=dns/txt; s=iport; t=1301166292; x=1302375892; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=WD3V1ajuersSb2IpIQEO3MQFP/LdNRoFbHnqtlqB8D4=; b=WlYpFnVqhy4wTDUE5/7ck8nELIZ232LYgWSS2dmaSMgtGkGBMriHA2rx FRktT/B+GoDF453hT217bUpdo+kWnSBX/Bfr5ogMJTxg2hq7TjuQU8e5r Hm/AkDLqytNAEweBuQF/VPBvPRXNTU1g58CnFhdTZ9bbIDBAFl7dPep7X o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlAHAHM4jk2rRDoH/2dsb2JhbACYaIx+d6Zvm1iFaQSFOosW
X-IronPort-AV: E=Sophos;i="4.63,248,1299456000"; d="scan'208";a="283221036"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-3.cisco.com with ESMTP; 26 Mar 2011 19:04:44 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2QJ4i2d008437 for <siprec@ietf.org>; Sat, 26 Mar 2011 19:04:44 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 26 Mar 2011 12:04:44 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 26 Mar 2011 12:04:42 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhg==
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: <siprec@ietf.org>
X-OriginalArrivalTime: 26 Mar 2011 19:04:44.0267 (UTC) FILETIME=[AAEB2BB0:01CBEBE8]
Subject: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 26 Mar 2011 19:03:17 -0000

I gave the draft and read and have the following comments.

Section 3. Think the metadata describes the recording session, not the
communication session. Replace "metamodel" with "metadata model", and
"MAY be conveyed in Recording Session" with "MAY be conveyed within the
Recording Session", and "time a change occurred by be assumed" with
"time a change occurred may be assumed".

Section 4, suggest rewording as, "The section describes each element of
the metadata model, and the attributes of each element. This section
also describes how the different elements are associated."

Section 4.1, RecordingRequestorID is not really an ID, it is more of a
type. I think RecordingRequestor is more appropriate. That said, I think
you also need a unique ID for the Recording Session, right?

Section 4.2.1, replace "SRC (or MAY be SRS)" with "SRC or SRS".

Section 4.3.2, why does a CS need two participants or more? What about
studio mode recording?

Section 4.4.1, what is participant type and what is its use, or why
needed?

Section 4.5, I think Media Stream requires a unique ID attribute as
well. Is the "Media Stream Reference" the SDP label attribute?

Thanks,
Charles




From eckelcu@cisco.com  Sat Mar 26 12:05:03 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 02CFB3A6811 for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 12:05:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.566
X-Spam-Level: 
X-Spam-Status: No, score=-10.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EMyPETMD8QyR for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 12:05:00 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 593233A67F2 for <siprec@ietf.org>; Sat, 26 Mar 2011 12:05:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=10764; q=dns/txt; s=iport; t=1301166396; x=1302375996; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=H9TqN0toAhqnKhfvoWUhwiB/gLRucXTCK20/omLxJgs=; b=efgTr7HB5AXrpWpYCDVhHbox0kP8fxPwcaWrc12mTf1fRybuDtL6q6+c dvcMF5LAv0c26p1//NfF8tAfrhpuIFCKqMBfADbWYnV+TJUJ6Lt6of0Z1 2xadNX5z05QfHW715WmSTczfUj/0LId+lKhZyNStN+uHpFCqRmrO2m7KI 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AioBAHM4jk2rRDoI/2dsb2JhbACYKY09d4hrngSbWIVpBIU6ixY
X-IronPort-AV: E=Sophos;i="4.63,248,1299456000"; d="scan'208";a="283221437"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 26 Mar 2011 19:06:36 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2QJ6aZK002689; Sat, 26 Mar 2011 19:06:36 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 26 Mar 2011 12:06:36 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 26 Mar 2011 12:06:33 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel	[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQ
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 26 Mar 2011 19:06:36.0411 (UTC) FILETIME=[EDC2FCB0:01CBEBE8]
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel	[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 26 Mar 2011 19:05:03 -0000

Hi Leon,

I am still having a hard time understanding why we need the session
state information per CS participant? Why is this required, who uses it,
and how?

Thanks,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Leon Portman
> Sent: Saturday, March 26, 2011 10:31 AM
> To: Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmohanr);
Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Dialog state in the CS block of metadatamodel
[wasRE:Progressing the
> architecture document]
>=20
> John Hello
>=20
> I agree that SRS (and its application clients) interested in SESSION
level events and not underlying
> DIALOG events. However we do need to support reporting session state
information per CS  participant
> that sometimes equals to dialog level and sometimes not.
>=20
> We could have define more application level state events like instead
of TRYING - > RINGING etc.
> However they could be domain specific.
>=20
> Leon
>=20
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 24, 2011 6:34 PM
> To: Parthasarathi R (partr); Ram Mohan R (rmohanr); Leon Portman;
Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of metadata model
[wasRE:Progressing the
> architecture document]
>=20
> This discussion gives me some concerns, echoing to some extent what
Ram is saying.
>=20
> SIPREC is about session recording, where a session is the information
exchanged between participants
> in a CS (the media streams) plus metadata. The metadata should provide
additional information about
> the CS. This means information about the communication SESSION, not
about the SIP dialog that is used
> to control that session. With this in mind, consider the following
points, some of which have already
> been raised:
>=20
> 1. There may be more than one SIP dialog involved if the SRC is at a
B2BUA or conference focus.
>=20
> 2. Does the CS necessarily need to be controlled by SIP? For example,
it could be a PSTN call, an RTC-
> Web call or a Jingle call. None of these preclude using SIP for the RS
(that is what the charter of
> SIPREC is all about - a SIP-based RS).
>=20
> 3. Somebody retrieving and playing back a recorded CS will be
interested in session-related events
> like participants leaving and joining (including the first
participants joining at the start of the CS
> and the last participants leaving a the end of the CS), media streams
starting and ending and
> participants starting or stopping receipt of a media stream. In other
words, changes of SESSION state,
> not dialog state.
>=20
> 4. Some of the SIP dialog states just don't seem relevant. The
distinction between early dialog and
> full dialog in SIP does not necessarily corresponding to any
meaningful state change of the session.
> For example, A makes a call to B and B answers and starts sending
media. A receives and renders media
> (perhaps it has already received SDP answer, allowing it to verify the
source of the media). Then A
> receives the 200 OK (transitioning from an early dialog to a full
dialog) and continues to receive
> media. So although there is a dialog state change, there is not really
a session state change.
>=20
> The bit about dialog state in the architecture draft is, in my
opinion, a legacy from some earlier
> discussions, before we started having the metadata discussions. I
think the metadata discussions have
> taken us in the right direction.
>=20
> John (as individual)
>=20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
(partr)
> > Sent: 24 March 2011 02:36
> > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Dialog state in the CS block of metadata model
> > [wasRE:Progressing the architecture document]
> >
> > Ram,
> >
> > Please read inline.
> >
> > Thanks
> > Partha
> >
> > ________________________________
> >
> > From: Ram Mohan R (rmohanr)
> > Sent: Wed 3/23/2011 7:59 PM
> > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of metadata model
> > [wasRE:Progressing the architecture document]
> >
> >
> >
> > I am still trying to understand what is the significance of this
> > attribute w.r.t CS. Are we saying the attribute represents the state
> > of CS ?
> >
> > Note that CS need not be one dialog.
> >
> > <Partha>  The attribute is to show the state of CS only. As it is
not
> > single dialog, I have mentioned as session state attribute </Partha>
> >
> > For cases like Conference where there may be different participants,
> > if SRC happens to be Focus how do you derive/what is "session state"
?
> >
> > <Partha> I really don't know whether it is generic. My thought
> > processing of session state for conference is as follows:
> >
> >
> >
> > 1) First participant of conference early media (ivr play) may be
> > considered as "early" state of session.
> >
> > 2) The session state is chaged to confirmed in case any one of the
> > participant joined in the conference.
> >
> > 3) The session state is move to terminated when the last participant
> > moved out of the conference.
> >
> >
> >
> > Please let me know in case other way to represent the session state
of
> > conference </partha>
> >
> >
> >
> > For cases where B2BUA acts as SRC what is "session state" ?
> >
> > <partha> It looks straight forward for me. In B2BUA case ,
> >
> > 1) The stage where in two party is not connected, it is considered
as
> > early state.
> >
> > 2) when both are connected, it is confirmed state
> >
> > 3) In case of BYE received from any one of the party, then CS is
> > considered as terminated state
> >
> >
> >
> > Please note that this is applicable for 3PCC as well.   </partha>
> >
> >
> >
> > Ram
> >
> >
> >
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
(partr)
> > Sent: Wednesday, March 23, 2011 6:13 AM
> > To: Leon Portman; Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Dialog state in the CS block of metadata model
> > [wasRE:Progressing the architecture document]
> >
> >
> >
> > Leon,
> >
> >
> >
> > Shall we have optional "event" attribute to indicate the state
change
> > which is similar to "event" attribute in RFC 4235.  The "event" will
> > include the following:
> >
> >
> >
> > 1) cancelled
> >
> > 2) rejected
> >
> > 3) replaced
> >
> > 4) bye
> >
> > 5) error
> >
> > 6) timeout
> >
> >
> >
> > Thanks
> >
> > Partha
> >
> >
> >
> > ________________________________
> >
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Tue 3/22/2011 9:37 PM
> > To: Hutton, Andrew; Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: RE: Dialog state in the CS block of metadata model [was
> > RE:Progressing the architecture document]
> >
> > It can be either application level error or dialog level errors -
like
> > timeout or failures.
> >
> >
> >
> > Leon
> >
> >
> >
> > From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> > Sent: Tuesday, March 22, 2011 6:02 PM
> > To: Leon Portman; Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: RE: Dialog state in the CS block of metadata model [was RE:
> > Progressing the architecture document]
> >
> >
> >
> > What would it be used for?
> >
> >
> >
> > Regards
> >
> > Andy
> >
> >
> >
> > ________________________________
> >
> > 	From: Leon Portman [mailto:Leon.Portman@nice.com]
> > 	Sent: 22 March 2011 14:11
> > 	To: Parthasarathi R (partr); Hutton, Andrew
> > 	Cc: siprec@ietf.org
> > 	Subject: RE: Dialog state in the CS block of metadata model [was
RE:
> > Progressing the architecture document]
> >
> > 	Should we have error state as well?
> >
> >
> >
> > 	Leon
> >
> >
> >
> > 	From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
(partr)
> > 	Sent: Tuesday, March 22, 2011 3:33 PM
> > 	To: Parthasarathi R (partr); Hutton, Andrew
> > 	Cc: siprec@ietf.org
> > 	Subject: [siprec] Dialog state in the CS block of metadata model
[was
> > RE: Progressing the architecture document]
> >
> >
> >
> > 	The architecture document proposes to have dialog/session state
in
> > Metadata model. To achieve this, "session state" attribute has to be
> > added in the CS block of Metadata model. The possible values for
> > session state are
> >
> >
> >
> > 	1) Trying
> >
> > 	2) Proceeding
> >
> > 	3) Early
> >
> > 	4) Confirmed
> >
> > 	5) Terminated
> >
> >
> >
> > 	Please let me know in case any objection to add this attribute
in
> > Metadata model.
> >
> >
> >
> > 	Thanks
> >
> > 	Partha
> >
> >
> >
> > ________________________________
> >
> > 	From: Parthasarathi R (partr)
> > 	Sent: Wednesday, March 16, 2011 5:40 AM
> > 	To: Hutton, Andrew
> > 	Cc: Elwell, John; siprec@ietf.org
> > 	Subject: RE: Progressing the architecture document
> >
> > 	> -----Original Message-----
> > 	> From: siprec-bounces@ietf.org
> > 	> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > (partr)
> > 	> Sent: 14 March 2011 17:05
> > 	> To: Elwell, John; siprec@ietf.org
> > 	> Subject: Re: [siprec] Progressing the architecture document
> >
> > 	>
> > 	> Sec 4.3.1 whether 3rd bullet is required?
> > 	>
> >
> > 	[AndyH]I assume it is as for example I assume it would be
necessary
> > to record early-media and update the SRS when the dialog changes to
> > the confirmed or terminated state. Does not seem to be in the
metadata
> > draft though. In the end I will either remove these bullets or align
> > with the metadata draft.
> > 	<Partha> It is a good point. Dialog state shall be added as one
of
> > the optional attribute in CS metadata block with default value as
> > mid-dialog. This helps to differentiate between early dialog
> > (ringback) vs mid-dialog (normal
> > conversation) in recording. In case of no objection for this
attribute
> > in metadata model, we will add it. We will work out metadata format
> > once the consensus occurs for metadata model.
> > In case required, we will span separate mail thread to close this
> > issue </Partha>
> >
> >
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From Leon.Portman@nice.com  Sat Mar 26 12:13:17 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B59643A695A for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 12:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.394
X-Spam-Level: 
X-Spam-Status: No, score=-2.394 tagged_above=-999 required=5 tests=[AWL=0.205,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkDqGT8QYbVR for <siprec@core3.amsl.com>; Sat, 26 Mar 2011 12:13:16 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id B02FD3A6952 for <siprec@ietf.org>; Sat, 26 Mar 2011 12:13:15 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Sat, 26 Mar 2011 21:14:51 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Date: Sat, 26 Mar 2011 21:14:48 +0200
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel [wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel	[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 26 Mar 2011 19:13:17 -0000

Charles Hi

Without participant session state, SRS will know only when participant is p=
art of the session and will not know about intermediate states like ringing=
, retrying etc.
I know that we have media stream information per participant but not sure t=
hat it is enough.

Leon
-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]=20
Sent: Saturday, March 26, 2011 9:07 PM
To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmoha=
nr); Hutton, Andrew
Cc: siprec@ietf.org
Subject: RE: [siprec] Dialog state in the CS block of metadatamodel [wasRE:=
Progressing the architecture document]

Hi Leon,

I am still having a hard time understanding why we need the session state i=
nformation per CS participant? Why is this required, who uses it, and how?

Thanks,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Leon Portman
> Sent: Saturday, March 26, 2011 10:31 AM
> To: Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmohanr);
Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Dialog state in the CS block of metadatamodel
[wasRE:Progressing the
> architecture document]
>=20
> John Hello
>=20
> I agree that SRS (and its application clients) interested in SESSION
level events and not underlying
> DIALOG events. However we do need to support reporting session state
information per CS  participant
> that sometimes equals to dialog level and sometimes not.
>=20
> We could have define more application level state events like instead
of TRYING - > RINGING etc.
> However they could be domain specific.
>=20
> Leon
>=20
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, March 24, 2011 6:34 PM
> To: Parthasarathi R (partr); Ram Mohan R (rmohanr); Leon Portman;
Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of metadata model
[wasRE:Progressing the
> architecture document]
>=20
> This discussion gives me some concerns, echoing to some extent what
Ram is saying.
>=20
> SIPREC is about session recording, where a session is the information
exchanged between participants
> in a CS (the media streams) plus metadata. The metadata should provide
additional information about
> the CS. This means information about the communication SESSION, not
about the SIP dialog that is used
> to control that session. With this in mind, consider the following
points, some of which have already
> been raised:
>=20
> 1. There may be more than one SIP dialog involved if the SRC is at a
B2BUA or conference focus.
>=20
> 2. Does the CS necessarily need to be controlled by SIP? For example,
it could be a PSTN call, an RTC-
> Web call or a Jingle call. None of these preclude using SIP for the RS
(that is what the charter of
> SIPREC is all about - a SIP-based RS).
>=20
> 3. Somebody retrieving and playing back a recorded CS will be
interested in session-related events
> like participants leaving and joining (including the first
participants joining at the start of the CS
> and the last participants leaving a the end of the CS), media streams
starting and ending and
> participants starting or stopping receipt of a media stream. In other
words, changes of SESSION state,
> not dialog state.
>=20
> 4. Some of the SIP dialog states just don't seem relevant. The
distinction between early dialog and
> full dialog in SIP does not necessarily corresponding to any
meaningful state change of the session.
> For example, A makes a call to B and B answers and starts sending
media. A receives and renders media
> (perhaps it has already received SDP answer, allowing it to verify the
source of the media). Then A
> receives the 200 OK (transitioning from an early dialog to a full
dialog) and continues to receive
> media. So although there is a dialog state change, there is not really
a session state change.
>=20
> The bit about dialog state in the architecture draft is, in my
opinion, a legacy from some earlier
> discussions, before we started having the metadata discussions. I
think the metadata discussions have
> taken us in the right direction.
>=20
> John (as individual)
>=20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
(partr)
> > Sent: 24 March 2011 02:36
> > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Dialog state in the CS block of metadata model=20
> > [wasRE:Progressing the architecture document]
> >
> > Ram,
> >
> > Please read inline.
> >
> > Thanks
> > Partha
> >
> > ________________________________
> >
> > From: Ram Mohan R (rmohanr)
> > Sent: Wed 3/23/2011 7:59 PM
> > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of metadata model=20
> > [wasRE:Progressing the architecture document]
> >
> >
> >
> > I am still trying to understand what is the significance of this=20
> > attribute w.r.t CS. Are we saying the attribute represents the state=20
> > of CS ?
> >
> > Note that CS need not be one dialog.
> >
> > <Partha>  The attribute is to show the state of CS only. As it is
not
> > single dialog, I have mentioned as session state attribute </Partha>
> >
> > For cases like Conference where there may be different participants,=20
> > if SRC happens to be Focus how do you derive/what is "session state"
?
> >
> > <Partha> I really don't know whether it is generic. My thought=20
> > processing of session state for conference is as follows:
> >
> >
> >
> > 1) First participant of conference early media (ivr play) may be=20
> > considered as "early" state of session.
> >
> > 2) The session state is chaged to confirmed in case any one of the=20
> > participant joined in the conference.
> >
> > 3) The session state is move to terminated when the last participant=20
> > moved out of the conference.
> >
> >
> >
> > Please let me know in case other way to represent the session state
of
> > conference </partha>
> >
> >
> >
> > For cases where B2BUA acts as SRC what is "session state" ?
> >
> > <partha> It looks straight forward for me. In B2BUA case ,
> >
> > 1) The stage where in two party is not connected, it is considered
as
> > early state.
> >
> > 2) when both are connected, it is confirmed state
> >
> > 3) In case of BYE received from any one of the party, then CS is=20
> > considered as terminated state
> >
> >
> >
> > Please note that this is applicable for 3PCC as well.   </partha>
> >
> >
> >
> > Ram
> >
> >
> >
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
(partr)
> > Sent: Wednesday, March 23, 2011 6:13 AM
> > To: Leon Portman; Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Dialog state in the CS block of metadata model=20
> > [wasRE:Progressing the architecture document]
> >
> >
> >
> > Leon,
> >
> >
> >
> > Shall we have optional "event" attribute to indicate the state
change
> > which is similar to "event" attribute in RFC 4235.  The "event" will=20
> > include the following:
> >
> >
> >
> > 1) cancelled
> >
> > 2) rejected
> >
> > 3) replaced
> >
> > 4) bye
> >
> > 5) error
> >
> > 6) timeout
> >
> >
> >
> > Thanks
> >
> > Partha
> >
> >
> >
> > ________________________________
> >
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Tue 3/22/2011 9:37 PM
> > To: Hutton, Andrew; Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: RE: Dialog state in the CS block of metadata model [was=20
> > RE:Progressing the architecture document]
> >
> > It can be either application level error or dialog level errors -
like
> > timeout or failures.
> >
> >
> >
> > Leon
> >
> >
> >
> > From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> > Sent: Tuesday, March 22, 2011 6:02 PM
> > To: Leon Portman; Parthasarathi R (partr)
> > Cc: siprec@ietf.org
> > Subject: RE: Dialog state in the CS block of metadata model [was RE:
> > Progressing the architecture document]
> >
> >
> >
> > What would it be used for?
> >
> >
> >
> > Regards
> >
> > Andy
> >
> >
> >
> > ________________________________
> >
> > 	From: Leon Portman [mailto:Leon.Portman@nice.com]
> > 	Sent: 22 March 2011 14:11
> > 	To: Parthasarathi R (partr); Hutton, Andrew
> > 	Cc: siprec@ietf.org
> > 	Subject: RE: Dialog state in the CS block of metadata model [was
RE:
> > Progressing the architecture document]
> >
> > 	Should we have error state as well?
> >
> >
> >
> > 	Leon
> >
> >
> >
> > 	From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
(partr)
> > 	Sent: Tuesday, March 22, 2011 3:33 PM
> > 	To: Parthasarathi R (partr); Hutton, Andrew
> > 	Cc: siprec@ietf.org
> > 	Subject: [siprec] Dialog state in the CS block of metadata model
[was
> > RE: Progressing the architecture document]
> >
> >
> >
> > 	The architecture document proposes to have dialog/session state
in
> > Metadata model. To achieve this, "session state" attribute has to be=20
> > added in the CS block of Metadata model. The possible values for=20
> > session state are
> >
> >
> >
> > 	1) Trying
> >
> > 	2) Proceeding
> >
> > 	3) Early
> >
> > 	4) Confirmed
> >
> > 	5) Terminated
> >
> >
> >
> > 	Please let me know in case any objection to add this attribute
in
> > Metadata model.
> >
> >
> >
> > 	Thanks
> >
> > 	Partha
> >
> >
> >
> > ________________________________
> >
> > 	From: Parthasarathi R (partr)
> > 	Sent: Wednesday, March 16, 2011 5:40 AM
> > 	To: Hutton, Andrew
> > 	Cc: Elwell, John; siprec@ietf.org
> > 	Subject: RE: Progressing the architecture document
> >
> > 	> -----Original Message-----
> > 	> From: siprec-bounces@ietf.org
> > 	> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > (partr)
> > 	> Sent: 14 March 2011 17:05
> > 	> To: Elwell, John; siprec@ietf.org
> > 	> Subject: Re: [siprec] Progressing the architecture document
> >
> > 	>
> > 	> Sec 4.3.1 whether 3rd bullet is required?
> > 	>
> >
> > 	[AndyH]I assume it is as for example I assume it would be
necessary
> > to record early-media and update the SRS when the dialog changes to=20
> > the confirmed or terminated state. Does not seem to be in the
metadata
> > draft though. In the end I will either remove these bullets or align=20
> > with the metadata draft.
> > 	<Partha> It is a good point. Dialog state shall be added as one
of
> > the optional attribute in CS metadata block with default value as=20
> > mid-dialog. This helps to differentiate between early dialog
> > (ringback) vs mid-dialog (normal
> > conversation) in recording. In case of no objection for this
attribute
> > in metadata model, we will add it. We will work out metadata format=20
> > once the consensus occurs for metadata model.
> > In case required, we will span separate mail thread to close this=20
> > issue </Partha>
> >
> >
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From john.elwell@siemens-enterprise.com  Sun Mar 27 01:31:56 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B38FB3A69B3 for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 01:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BOp0YEYRYe70 for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 01:31:55 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 0FA833A688F for <siprec@ietf.org>; Sun, 27 Mar 2011 01:31:54 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3904866; Sun, 27 Mar 2011 10:33:04 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 1EF151EB82B5; Sun, 27 Mar 2011 10:33:04 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Sun, 27 Mar 2011 10:33:04 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "siprec@ietf.org" <siprec@ietf.org>, "Ken Rehor (krehor) (krehor@cisco.com)" <krehor@cisco.com>
Date: Sun, 27 Mar 2011 10:33:01 +0200
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIAACWzYeA=
Message-ID: <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net>
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 27 Mar 2011 08:31:56 -0000

Yes, indeed we had the discussion and came up with reasons you can't tie th=
e two together. So as Gonzalo suggests, some of that discussion needs to be=
 captured in the Security Considerations section.

John

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 26 March 2011 14:37
> To: Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor)=20
> (krehor@cisco.com); Elwell, John
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Hi,
>=20
> I want to touch security requirement: about security level of=20
> RS vs security level of CS. We had a long mailing list=20
> discussion (below) and it was decided not to have it, because=20
> it is more implementation details
>=20
> http://www.ietf.org/mail-archive/web/siprec/current/msg01164.html
>=20
> Regards
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> Sent: Wednesday, March 23, 2011 1:23 PM
> To: siprec@ietf.org
> Subject: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Hi,
>=20
> the SIPREC WG requested the publication of the following=20
> draft a few days ago. Please, find below my AD review.
>=20
> https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
>=20
> Given that the draft contains both requirements and use=20
> cases, you may want to edit the title so that it reads "Use=20
> Cases and Requirements for ..."
>=20
> Typically, Section 1 contains the Introduction and Section 2=20
> the terminology. You may want to swap both sections.
>=20
> Most of the requirements are phrased so that they describe=20
> capabilities that need to be supported by the system (e.g.,=20
> the mechanism MUST provide the SRS with the means to ...) but=20
> that do not need to be necessarily used (e.g., a particular=20
> use case may not make use of that functionality). However,=20
> some requirements are phrased so that the functionality needs=20
> to be used (e.g., the mechanism MUST provide the SRS the wall=20
> clock time ...). Requirements 12, 22, 23, 27, 28, and 29 seem=20
> to fall into the latter category. Could you please check=20
> whether that was the intention with all those requirements?
>=20
> A few requirements relate to the security and privacy related=20
> properties of the SRC-SRS interface (e.g., requirements 24=20
> and 29). However, the draft does not discuss how the security=20
> and privacy of that interface relate to the security and=20
> privacy level used for the CS being recorded.
> For example, can the confidentiality level of the media going=20
> from the SRC and the SRS be lower than that of the media=20
> flowing between the actual participants of the CS? If you=20
> decide there should not be a requirement on this area, you=20
> need to at least discuss this issue (probably in Sections 6 or 7).
>=20
> Once you address these comments, I will request the IETF-wide=20
> last call for this draft.
>=20
> Thanks,
>=20
> Gonzalo
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From gonzalo.camarillo@ericsson.com  Sun Mar 27 01:34:23 2011
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 525ED3A69BE for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 01:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.601
X-Spam-Level: 
X-Spam-Status: No, score=-106.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWs0INJ2i8La for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 01:34:22 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id B1B333A688F for <siprec@ietf.org>; Sun, 27 Mar 2011 01:34:21 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bbbae000005311-ac-4d8ef6edafae
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id BA.45.21265.DE6FE8D4; Sun, 27 Mar 2011 10:35:57 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.137.0; Sun, 27 Mar 2011 10:35:57 +0200
Received: from [131.160.126.144] (rvi2-126-144.lmf.ericsson.se [131.160.126.144])	by mail.lmf.ericsson.se (Postfix) with ESMTP id A171224F0; Sun, 27 Mar 2011 11:35:55 +0300 (EEST)
Message-ID: <4D8EF6EA.1020603@ericsson.com>
Date: Sun, 27 Mar 2011 09:35:54 +0100
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: "siprec@ietf.org" <siprec@ietf.org>, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 27 Mar 2011 08:34:23 -0000

Hi,

exactly, the draft should reflect the conclusion of those discussions.

Thanks,

Gonzalo

On 27/03/2011 9:33 AM, Elwell, John wrote:
> Yes, indeed we had the discussion and came up with reasons you can't tie the two together. So as Gonzalo suggests, some of that discussion needs to be captured in the Security Considerations section.
> 
> John
> 
>> -----Original Message-----
>> From: Leon Portman [mailto:Leon.Portman@nice.com] 
>> Sent: 26 March 2011 14:37
>> To: Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor) 
>> (krehor@cisco.com); Elwell, John
>> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>>
>> Hi,
>>
>> I want to touch security requirement: about security level of 
>> RS vs security level of CS. We had a long mailing list 
>> discussion (below) and it was decided not to have it, because 
>> it is more implementation details
>>
>> http://www.ietf.org/mail-archive/web/siprec/current/msg01164.html
>>
>> Regards
>>
>> Leon
>>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org 
>> [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
>> Sent: Wednesday, March 23, 2011 1:23 PM
>> To: siprec@ietf.org
>> Subject: [siprec] AD review: draft-ietf-siprec-req-08
>>
>> Hi,
>>
>> the SIPREC WG requested the publication of the following 
>> draft a few days ago. Please, find below my AD review.
>>
>> https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
>>
>> Given that the draft contains both requirements and use 
>> cases, you may want to edit the title so that it reads "Use 
>> Cases and Requirements for ..."
>>
>> Typically, Section 1 contains the Introduction and Section 2 
>> the terminology. You may want to swap both sections.
>>
>> Most of the requirements are phrased so that they describe 
>> capabilities that need to be supported by the system (e.g., 
>> the mechanism MUST provide the SRS with the means to ...) but 
>> that do not need to be necessarily used (e.g., a particular 
>> use case may not make use of that functionality). However, 
>> some requirements are phrased so that the functionality needs 
>> to be used (e.g., the mechanism MUST provide the SRS the wall 
>> clock time ...). Requirements 12, 22, 23, 27, 28, and 29 seem 
>> to fall into the latter category. Could you please check 
>> whether that was the intention with all those requirements?
>>
>> A few requirements relate to the security and privacy related 
>> properties of the SRC-SRS interface (e.g., requirements 24 
>> and 29). However, the draft does not discuss how the security 
>> and privacy of that interface relate to the security and 
>> privacy level used for the CS being recorded.
>> For example, can the confidentiality level of the media going 
>> from the SRC and the SRS be lower than that of the media 
>> flowing between the actual participants of the CS? If you 
>> decide there should not be a requirement on this area, you 
>> need to at least discuss this issue (probably in Sections 6 or 7).
>>
>> Once you address these comments, I will request the IETF-wide 
>> last call for this draft.
>>
>> Thanks,
>>
>> Gonzalo
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec


From eckelcu@cisco.com  Sun Mar 27 02:33:57 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D06C628C10B for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 02:33:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.567
X-Spam-Level: 
X-Spam-Status: No, score=-10.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gQElbPLVoNZE for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 02:33:55 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 942A228C124 for <siprec@ietf.org>; Sun, 27 Mar 2011 02:33:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=13152; q=dns/txt; s=iport; t=1301218532; x=1302428132; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=lpPrdadA9QSv4b5x1tXTqnAG/URj6h59ji3TGqRscjg=; b=iPF4q+38tqGCMLU01WLfBlxK2ihYauquPRZ9qwBjlf2L+j89boU5n1kX ynS0NCI4zfHgHgFkckqmkndTXSWbVQ2kMn+4Mpo+HyqYGXpjqNdeahA58 Jga+GGJW/s9LiIPKRAMwQf08pd6vQtYw4vOItisP1Ui7XIXAV2Qg+U+dV s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggBAJsEj02rRDoH/2dsb2JhbACYI408d4hrnVmbAoVpBIU6ixc
X-IronPort-AV: E=Sophos;i="4.63,250,1299456000"; d="scan'208";a="325283504"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-2.cisco.com with ESMTP; 27 Mar 2011 09:35:32 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2R9ZWQG009659; Sun, 27 Mar 2011 09:35:32 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 27 Mar 2011 02:35:31 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 27 Mar 2011 02:35:29 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsA==
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 27 Mar 2011 09:35:31.0933 (UTC) FILETIME=[50F450D0:01CBEC62]
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 27 Mar 2011 09:33:57 -0000

Hi Leon,

Thank you for your patience in trying to explain this to me; however, I
still am not able to understand why the SRS might need to know this
information, or what it would do with it. Is it that you need to know
when a given participant was receiving the recorded media and when it
was not? If so, I do not think dialog state is sufficient. Is there some
other requirement or functionality addressed by the SRS having such
information?
Perhaps it is easier to discuss in person at the breakfast meeting
Wednesday or during the working group session.

Cheers,
Charles

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Saturday, March 26, 2011 8:15 PM
> To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R (partr);
Ram Mohan R (rmohanr); Hutton,
> Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
metadatamodel[wasRE:Progressing the architecture
> document]
>=20
> Charles Hi
>=20
> Without participant session state, SRS will know only when participant
is part of the session and will
> not know about intermediate states like ringing, retrying etc.
> I know that we have media stream information per participant but not
sure that it is enough.
>=20
> Leon
> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: Saturday, March 26, 2011 9:07 PM
> To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram Mohan R
(rmohanr); Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of metadatamodel
[wasRE:Progressing the
> architecture document]
>=20
> Hi Leon,
>=20
> I am still having a hard time understanding why we need the session
state information per CS
> participant? Why is this required, who uses it, and how?
>=20
> Thanks,
> Charles
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Leon Portman
> > Sent: Saturday, March 26, 2011 10:31 AM
> > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmohanr);
> Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Dialog state in the CS block of metadatamodel
> [wasRE:Progressing the
> > architecture document]
> >
> > John Hello
> >
> > I agree that SRS (and its application clients) interested in SESSION
> level events and not underlying
> > DIALOG events. However we do need to support reporting session state
> information per CS  participant
> > that sometimes equals to dialog level and sometimes not.
> >
> > We could have define more application level state events like
instead
> of TRYING - > RINGING etc.
> > However they could be domain specific.
> >
> > Leon
> >
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Thursday, March 24, 2011 6:34 PM
> > To: Parthasarathi R (partr); Ram Mohan R (rmohanr); Leon Portman;
> Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of metadata model
> [wasRE:Progressing the
> > architecture document]
> >
> > This discussion gives me some concerns, echoing to some extent what
> Ram is saying.
> >
> > SIPREC is about session recording, where a session is the
information
> exchanged between participants
> > in a CS (the media streams) plus metadata. The metadata should
provide
> additional information about
> > the CS. This means information about the communication SESSION, not
> about the SIP dialog that is used
> > to control that session. With this in mind, consider the following
> points, some of which have already
> > been raised:
> >
> > 1. There may be more than one SIP dialog involved if the SRC is at a
> B2BUA or conference focus.
> >
> > 2. Does the CS necessarily need to be controlled by SIP? For
example,
> it could be a PSTN call, an RTC-
> > Web call or a Jingle call. None of these preclude using SIP for the
RS
> (that is what the charter of
> > SIPREC is all about - a SIP-based RS).
> >
> > 3. Somebody retrieving and playing back a recorded CS will be
> interested in session-related events
> > like participants leaving and joining (including the first
> participants joining at the start of the CS
> > and the last participants leaving a the end of the CS), media
streams
> starting and ending and
> > participants starting or stopping receipt of a media stream. In
other
> words, changes of SESSION state,
> > not dialog state.
> >
> > 4. Some of the SIP dialog states just don't seem relevant. The
> distinction between early dialog and
> > full dialog in SIP does not necessarily corresponding to any
> meaningful state change of the session.
> > For example, A makes a call to B and B answers and starts sending
> media. A receives and renders media
> > (perhaps it has already received SDP answer, allowing it to verify
the
> source of the media). Then A
> > receives the 200 OK (transitioning from an early dialog to a full
> dialog) and continues to receive
> > media. So although there is a dialog state change, there is not
really
> a session state change.
> >
> > The bit about dialog state in the architecture draft is, in my
> opinion, a legacy from some earlier
> > discussions, before we started having the metadata discussions. I
> think the metadata discussions have
> > taken us in the right direction.
> >
> > John (as individual)
> >
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> (partr)
> > > Sent: 24 March 2011 02:36
> > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Dialog state in the CS block of metadata
model
> > > [wasRE:Progressing the architecture document]
> > >
> > > Ram,
> > >
> > > Please read inline.
> > >
> > > Thanks
> > > Partha
> > >
> > > ________________________________
> > >
> > > From: Ram Mohan R (rmohanr)
> > > Sent: Wed 3/23/2011 7:59 PM
> > > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of metadata
model
> > > [wasRE:Progressing the architecture document]
> > >
> > >
> > >
> > > I am still trying to understand what is the significance of this
> > > attribute w.r.t CS. Are we saying the attribute represents the
state
> > > of CS ?
> > >
> > > Note that CS need not be one dialog.
> > >
> > > <Partha>  The attribute is to show the state of CS only. As it is
> not
> > > single dialog, I have mentioned as session state attribute
</Partha>
> > >
> > > For cases like Conference where there may be different
participants,
> > > if SRC happens to be Focus how do you derive/what is "session
state"
> ?
> > >
> > > <Partha> I really don't know whether it is generic. My thought
> > > processing of session state for conference is as follows:
> > >
> > >
> > >
> > > 1) First participant of conference early media (ivr play) may be
> > > considered as "early" state of session.
> > >
> > > 2) The session state is chaged to confirmed in case any one of the
> > > participant joined in the conference.
> > >
> > > 3) The session state is move to terminated when the last
participant
> > > moved out of the conference.
> > >
> > >
> > >
> > > Please let me know in case other way to represent the session
state
> of
> > > conference </partha>
> > >
> > >
> > >
> > > For cases where B2BUA acts as SRC what is "session state" ?
> > >
> > > <partha> It looks straight forward for me. In B2BUA case ,
> > >
> > > 1) The stage where in two party is not connected, it is considered
> as
> > > early state.
> > >
> > > 2) when both are connected, it is confirmed state
> > >
> > > 3) In case of BYE received from any one of the party, then CS is
> > > considered as terminated state
> > >
> > >
> > >
> > > Please note that this is applicable for 3PCC as well.   </partha>
> > >
> > >
> > >
> > > Ram
> > >
> > >
> > >
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> (partr)
> > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > To: Leon Portman; Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Dialog state in the CS block of metadata
model
> > > [wasRE:Progressing the architecture document]
> > >
> > >
> > >
> > > Leon,
> > >
> > >
> > >
> > > Shall we have optional "event" attribute to indicate the state
> change
> > > which is similar to "event" attribute in RFC 4235.  The "event"
will
> > > include the following:
> > >
> > >
> > >
> > > 1) cancelled
> > >
> > > 2) rejected
> > >
> > > 3) replaced
> > >
> > > 4) bye
> > >
> > > 5) error
> > >
> > > 6) timeout
> > >
> > >
> > >
> > > Thanks
> > >
> > > Partha
> > >
> > >
> > >
> > > ________________________________
> > >
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: Tue 3/22/2011 9:37 PM
> > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > Cc: siprec@ietf.org
> > > Subject: RE: Dialog state in the CS block of metadata model [was
> > > RE:Progressing the architecture document]
> > >
> > > It can be either application level error or dialog level errors -
> like
> > > timeout or failures.
> > >
> > >
> > >
> > > Leon
> > >
> > >
> > >
> > > From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > To: Leon Portman; Parthasarathi R (partr)
> > > Cc: siprec@ietf.org
> > > Subject: RE: Dialog state in the CS block of metadata model [was
RE:
> > > Progressing the architecture document]
> > >
> > >
> > >
> > > What would it be used for?
> > >
> > >
> > >
> > > Regards
> > >
> > > Andy
> > >
> > >
> > >
> > > ________________________________
> > >
> > > 	From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > 	Sent: 22 March 2011 14:11
> > > 	To: Parthasarathi R (partr); Hutton, Andrew
> > > 	Cc: siprec@ietf.org
> > > 	Subject: RE: Dialog state in the CS block of metadata model [was
> RE:
> > > Progressing the architecture document]
> > >
> > > 	Should we have error state as well?
> > >
> > >
> > >
> > > 	Leon
> > >
> > >
> > >
> > > 	From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> (partr)
> > > 	Sent: Tuesday, March 22, 2011 3:33 PM
> > > 	To: Parthasarathi R (partr); Hutton, Andrew
> > > 	Cc: siprec@ietf.org
> > > 	Subject: [siprec] Dialog state in the CS block of metadata model
> [was
> > > RE: Progressing the architecture document]
> > >
> > >
> > >
> > > 	The architecture document proposes to have dialog/session state
> in
> > > Metadata model. To achieve this, "session state" attribute has to
be
> > > added in the CS block of Metadata model. The possible values for
> > > session state are
> > >
> > >
> > >
> > > 	1) Trying
> > >
> > > 	2) Proceeding
> > >
> > > 	3) Early
> > >
> > > 	4) Confirmed
> > >
> > > 	5) Terminated
> > >
> > >
> > >
> > > 	Please let me know in case any objection to add this attribute
> in
> > > Metadata model.
> > >
> > >
> > >
> > > 	Thanks
> > >
> > > 	Partha
> > >
> > >
> > >
> > > ________________________________
> > >
> > > 	From: Parthasarathi R (partr)
> > > 	Sent: Wednesday, March 16, 2011 5:40 AM
> > > 	To: Hutton, Andrew
> > > 	Cc: Elwell, John; siprec@ietf.org
> > > 	Subject: RE: Progressing the architecture document
> > >
> > > 	> -----Original Message-----
> > > 	> From: siprec-bounces@ietf.org
> > > 	> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > > (partr)
> > > 	> Sent: 14 March 2011 17:05
> > > 	> To: Elwell, John; siprec@ietf.org
> > > 	> Subject: Re: [siprec] Progressing the architecture document
> > >
> > > 	>
> > > 	> Sec 4.3.1 whether 3rd bullet is required?
> > > 	>
> > >
> > > 	[AndyH]I assume it is as for example I assume it would be
> necessary
> > > to record early-media and update the SRS when the dialog changes
to
> > > the confirmed or terminated state. Does not seem to be in the
> metadata
> > > draft though. In the end I will either remove these bullets or
align
> > > with the metadata draft.
> > > 	<Partha> It is a good point. Dialog state shall be added as one
> of
> > > the optional attribute in CS metadata block with default value as
> > > mid-dialog. This helps to differentiate between early dialog
> > > (ringback) vs mid-dialog (normal
> > > conversation) in recording. In case of no objection for this
> attribute
> > > in metadata model, we will add it. We will work out metadata
format
> > > once the consensus occurs for metadata model.
> > > In case required, we will span separate mail thread to close this
> > > issue </Partha>
> > >
> > >
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec

From Leon.Portman@nice.com  Sun Mar 27 03:46:34 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B16E13A659A for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 03:46:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0YISo7IWOZM for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 03:46:33 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 3DFDC3A6452 for <siprec@ietf.org>; Sun, 27 Mar 2011 03:46:32 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Sun, 27 Mar 2011 12:48:07 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Date: Sun, 27 Mar 2011 12:48:05 +0200
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsAAClqhQ
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 27 Mar 2011 10:46:34 -0000

Charles Hi

Yes, it will be good to discuss it face to face.

Just little background for such requirements. Today, especially for contact=
 centers, it is important for SRS to capture the information how long custo=
mer was waiting for agent to answer the call, which party hang up, how long=
 was the hold time, if it was blind transfer or consultation transfer. This=
 information important both from quality management point of view and custo=
mer experience point of view.  It is important also from compliance point o=
f view to detect if somebody actually received the media stream or still wa=
s in pending state or media stream was disconnected.

Leon

-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
Sent: Sunday, March 27, 2011 11:35 AM
To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmoha=
nr); Hutton, Andrew
Cc: siprec@ietf.org
Subject: RE: [siprec] Dialog state in the CS block of metadatamodel[wasRE:P=
rogressing the architecture document]

Hi Leon,

Thank you for your patience in trying to explain this to me; however, I sti=
ll am not able to understand why the SRS might need to know this informatio=
n, or what it would do with it. Is it that you need to know when a given pa=
rticipant was receiving the recorded media and when it was not? If so, I do=
 not think dialog state is sufficient. Is there some other requirement or f=
unctionality addressed by the SRS having such information?
Perhaps it is easier to discuss in person at the breakfast meeting Wednesda=
y or during the working group session.

Cheers,
Charles

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Saturday, March 26, 2011 8:15 PM
> To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R (partr);
Ram Mohan R (rmohanr); Hutton,
> Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
metadatamodel[wasRE:Progressing the architecture
> document]
>
> Charles Hi
>
> Without participant session state, SRS will know only when participant
is part of the session and will
> not know about intermediate states like ringing, retrying etc.
> I know that we have media stream information per participant but not
sure that it is enough.
>
> Leon
> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: Saturday, March 26, 2011 9:07 PM
> To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram Mohan R
(rmohanr); Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of metadatamodel
[wasRE:Progressing the
> architecture document]
>
> Hi Leon,
>
> I am still having a hard time understanding why we need the session
state information per CS
> participant? Why is this required, who uses it, and how?
>
> Thanks,
> Charles
>
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Leon Portman
> > Sent: Saturday, March 26, 2011 10:31 AM
> > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmohanr);
> Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Dialog state in the CS block of metadatamodel
> [wasRE:Progressing the
> > architecture document]
> >
> > John Hello
> >
> > I agree that SRS (and its application clients) interested in SESSION
> level events and not underlying
> > DIALOG events. However we do need to support reporting session state
> information per CS  participant
> > that sometimes equals to dialog level and sometimes not.
> >
> > We could have define more application level state events like
instead
> of TRYING - > RINGING etc.
> > However they could be domain specific.
> >
> > Leon
> >
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Thursday, March 24, 2011 6:34 PM
> > To: Parthasarathi R (partr); Ram Mohan R (rmohanr); Leon Portman;
> Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of metadata model
> [wasRE:Progressing the
> > architecture document]
> >
> > This discussion gives me some concerns, echoing to some extent what
> Ram is saying.
> >
> > SIPREC is about session recording, where a session is the
information
> exchanged between participants
> > in a CS (the media streams) plus metadata. The metadata should
provide
> additional information about
> > the CS. This means information about the communication SESSION, not
> about the SIP dialog that is used
> > to control that session. With this in mind, consider the following
> points, some of which have already
> > been raised:
> >
> > 1. There may be more than one SIP dialog involved if the SRC is at a
> B2BUA or conference focus.
> >
> > 2. Does the CS necessarily need to be controlled by SIP? For
example,
> it could be a PSTN call, an RTC-
> > Web call or a Jingle call. None of these preclude using SIP for the
RS
> (that is what the charter of
> > SIPREC is all about - a SIP-based RS).
> >
> > 3. Somebody retrieving and playing back a recorded CS will be
> interested in session-related events
> > like participants leaving and joining (including the first
> participants joining at the start of the CS
> > and the last participants leaving a the end of the CS), media
streams
> starting and ending and
> > participants starting or stopping receipt of a media stream. In
other
> words, changes of SESSION state,
> > not dialog state.
> >
> > 4. Some of the SIP dialog states just don't seem relevant. The
> distinction between early dialog and
> > full dialog in SIP does not necessarily corresponding to any
> meaningful state change of the session.
> > For example, A makes a call to B and B answers and starts sending
> media. A receives and renders media
> > (perhaps it has already received SDP answer, allowing it to verify
the
> source of the media). Then A
> > receives the 200 OK (transitioning from an early dialog to a full
> dialog) and continues to receive
> > media. So although there is a dialog state change, there is not
really
> a session state change.
> >
> > The bit about dialog state in the architecture draft is, in my
> opinion, a legacy from some earlier
> > discussions, before we started having the metadata discussions. I
> think the metadata discussions have
> > taken us in the right direction.
> >
> > John (as individual)
> >
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> (partr)
> > > Sent: 24 March 2011 02:36
> > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Dialog state in the CS block of metadata
model
> > > [wasRE:Progressing the architecture document]
> > >
> > > Ram,
> > >
> > > Please read inline.
> > >
> > > Thanks
> > > Partha
> > >
> > > ________________________________
> > >
> > > From: Ram Mohan R (rmohanr)
> > > Sent: Wed 3/23/2011 7:59 PM
> > > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of metadata
model
> > > [wasRE:Progressing the architecture document]
> > >
> > >
> > >
> > > I am still trying to understand what is the significance of this
> > > attribute w.r.t CS. Are we saying the attribute represents the
state
> > > of CS ?
> > >
> > > Note that CS need not be one dialog.
> > >
> > > <Partha>  The attribute is to show the state of CS only. As it is
> not
> > > single dialog, I have mentioned as session state attribute
</Partha>
> > >
> > > For cases like Conference where there may be different
participants,
> > > if SRC happens to be Focus how do you derive/what is "session
state"
> ?
> > >
> > > <Partha> I really don't know whether it is generic. My thought
> > > processing of session state for conference is as follows:
> > >
> > >
> > >
> > > 1) First participant of conference early media (ivr play) may be
> > > considered as "early" state of session.
> > >
> > > 2) The session state is chaged to confirmed in case any one of the
> > > participant joined in the conference.
> > >
> > > 3) The session state is move to terminated when the last
participant
> > > moved out of the conference.
> > >
> > >
> > >
> > > Please let me know in case other way to represent the session
state
> of
> > > conference </partha>
> > >
> > >
> > >
> > > For cases where B2BUA acts as SRC what is "session state" ?
> > >
> > > <partha> It looks straight forward for me. In B2BUA case ,
> > >
> > > 1) The stage where in two party is not connected, it is considered
> as
> > > early state.
> > >
> > > 2) when both are connected, it is confirmed state
> > >
> > > 3) In case of BYE received from any one of the party, then CS is
> > > considered as terminated state
> > >
> > >
> > >
> > > Please note that this is applicable for 3PCC as well.   </partha>
> > >
> > >
> > >
> > > Ram
> > >
> > >
> > >
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> (partr)
> > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > To: Leon Portman; Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Dialog state in the CS block of metadata
model
> > > [wasRE:Progressing the architecture document]
> > >
> > >
> > >
> > > Leon,
> > >
> > >
> > >
> > > Shall we have optional "event" attribute to indicate the state
> change
> > > which is similar to "event" attribute in RFC 4235.  The "event"
will
> > > include the following:
> > >
> > >
> > >
> > > 1) cancelled
> > >
> > > 2) rejected
> > >
> > > 3) replaced
> > >
> > > 4) bye
> > >
> > > 5) error
> > >
> > > 6) timeout
> > >
> > >
> > >
> > > Thanks
> > >
> > > Partha
> > >
> > >
> > >
> > > ________________________________
> > >
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: Tue 3/22/2011 9:37 PM
> > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > Cc: siprec@ietf.org
> > > Subject: RE: Dialog state in the CS block of metadata model [was
> > > RE:Progressing the architecture document]
> > >
> > > It can be either application level error or dialog level errors -
> like
> > > timeout or failures.
> > >
> > >
> > >
> > > Leon
> > >
> > >
> > >
> > > From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > To: Leon Portman; Parthasarathi R (partr)
> > > Cc: siprec@ietf.org
> > > Subject: RE: Dialog state in the CS block of metadata model [was
RE:
> > > Progressing the architecture document]
> > >
> > >
> > >
> > > What would it be used for?
> > >
> > >
> > >
> > > Regards
> > >
> > > Andy
> > >
> > >
> > >
> > > ________________________________
> > >
> > >   From: Leon Portman [mailto:Leon.Portman@nice.com]
> > >   Sent: 22 March 2011 14:11
> > >   To: Parthasarathi R (partr); Hutton, Andrew
> > >   Cc: siprec@ietf.org
> > >   Subject: RE: Dialog state in the CS block of metadata model [was
> RE:
> > > Progressing the architecture document]
> > >
> > >   Should we have error state as well?
> > >
> > >
> > >
> > >   Leon
> > >
> > >
> > >
> > >   From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> (partr)
> > >   Sent: Tuesday, March 22, 2011 3:33 PM
> > >   To: Parthasarathi R (partr); Hutton, Andrew
> > >   Cc: siprec@ietf.org
> > >   Subject: [siprec] Dialog state in the CS block of metadata model
> [was
> > > RE: Progressing the architecture document]
> > >
> > >
> > >
> > >   The architecture document proposes to have dialog/session state
> in
> > > Metadata model. To achieve this, "session state" attribute has to
be
> > > added in the CS block of Metadata model. The possible values for
> > > session state are
> > >
> > >
> > >
> > >   1) Trying
> > >
> > >   2) Proceeding
> > >
> > >   3) Early
> > >
> > >   4) Confirmed
> > >
> > >   5) Terminated
> > >
> > >
> > >
> > >   Please let me know in case any objection to add this attribute
> in
> > > Metadata model.
> > >
> > >
> > >
> > >   Thanks
> > >
> > >   Partha
> > >
> > >
> > >
> > > ________________________________
> > >
> > >   From: Parthasarathi R (partr)
> > >   Sent: Wednesday, March 16, 2011 5:40 AM
> > >   To: Hutton, Andrew
> > >   Cc: Elwell, John; siprec@ietf.org
> > >   Subject: RE: Progressing the architecture document
> > >
> > >   > -----Original Message-----
> > >   > From: siprec-bounces@ietf.org
> > >   > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > > (partr)
> > >   > Sent: 14 March 2011 17:05
> > >   > To: Elwell, John; siprec@ietf.org
> > >   > Subject: Re: [siprec] Progressing the architecture document
> > >
> > >   >
> > >   > Sec 4.3.1 whether 3rd bullet is required?
> > >   >
> > >
> > >   [AndyH]I assume it is as for example I assume it would be
> necessary
> > > to record early-media and update the SRS when the dialog changes
to
> > > the confirmed or terminated state. Does not seem to be in the
> metadata
> > > draft though. In the end I will either remove these bullets or
align
> > > with the metadata draft.
> > >   <Partha> It is a good point. Dialog state shall be added as one
> of
> > > the optional attribute in CS metadata block with default value as
> > > mid-dialog. This helps to differentiate between early dialog
> > > (ringback) vs mid-dialog (normal
> > > conversation) in recording. In case of no objection for this
> attribute
> > > in metadata model, we will add it. We will work out metadata
format
> > > once the consensus occurs for metadata model.
> > > In case required, we will span separate mail thread to close this
> > > issue </Partha>
> > >
> > >
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec

From pkyzivat@cisco.com  Sun Mar 27 03:56:40 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A7CD3A6774 for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 03:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r-RbaNgzdrLA for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 03:56:37 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id B8F9B3A676A for <siprec@ietf.org>; Sun, 27 Mar 2011 03:56:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=14550; q=dns/txt; s=iport; t=1301223493; x=1302433093; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=CQx7qAvuYw+aarfUUWUewYylD3ZtJYi4I/CkjVuPZHg=; b=cXNp3HmC+tlNS8PEs7MnpfvmYOkM+FXDF9LIxFnfdFmPzUsRTVze5Oti Mv997R2Y2OC9w5ve9QTAwM0IZ7JmLPz9amBOZWUobWOQAqoGqzur/QGS+ IFG4R/mYZOPcTmmwbgDhURMCTmbk1d/E+sJHam/1KmB5tJqwx4ohdk72S U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvcAAOAWj02Q/khNgWdsb2JhbACYI409FAEBFiYliGudCZp8hWkEjHeDVA
X-IronPort-AV: E=Sophos;i="4.63,250,1299456000"; d="scan'208";a="80968281"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 27 Mar 2011 10:58:12 +0000
Received: from [10.55.90.49] (dhcp-10-55-90-49.cisco.com [10.55.90.49]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2RAwCeb025192 for <siprec@ietf.org>; Sun, 27 Mar 2011 10:58:12 GMT
Message-ID: <4D8F1844.50001@cisco.com>
Date: Sun, 27 Mar 2011 06:58:12 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: siprec@ietf.org
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net>	<07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com>	<E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com>	<07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com>	<E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 27 Mar 2011 10:56:40 -0000

On 3/27/2011 6:48 AM, Leon Portman wrote:
> Charles Hi
>
> Yes, it will be good to discuss it face to face.
>
> Just little background for such requirements. Today, especially for contact centers, it is important for SRS to capture the information how long customer was waiting for agent to answer the call, which party hang up, how long was the hold time, if it was blind transfer or consultation transfer. This information important both from quality management point of view and customer experience point of view.  It is important also from compliance point of view to detect if somebody actually received the media stream or still was in pending state or media stream was disconnected.

Leon,

Is it still the case that some contact centers manage to keep the 
customer in an early dialog for an extended period of time, while 
treating with IVR, until a live agent is assigned?

	Thanks,
	Paul

> Leon
>
> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: Sunday, March 27, 2011 11:35 AM
> To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
>
> Hi Leon,
>
> Thank you for your patience in trying to explain this to me; however, I still am not able to understand why the SRS might need to know this information, or what it would do with it. Is it that you need to know when a given participant was receiving the recorded media and when it was not? If so, I do not think dialog state is sufficient. Is there some other requirement or functionality addressed by the SRS having such information?
> Perhaps it is easier to discuss in person at the breakfast meeting Wednesday or during the working group session.
>
> Cheers,
> Charles
>
>> -----Original Message-----
>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>> Sent: Saturday, March 26, 2011 8:15 PM
>> To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R (partr);
> Ram Mohan R (rmohanr); Hutton,
>> Andrew
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture
>> document]
>>
>> Charles Hi
>>
>> Without participant session state, SRS will know only when participant
> is part of the session and will
>> not know about intermediate states like ringing, retrying etc.
>> I know that we have media stream information per participant but not
> sure that it is enough.
>>
>> Leon
>> -----Original Message-----
>> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
>> Sent: Saturday, March 26, 2011 9:07 PM
>> To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram Mohan R
> (rmohanr); Hutton, Andrew
>> Cc: siprec@ietf.org
>> Subject: RE: [siprec] Dialog state in the CS block of metadatamodel
> [wasRE:Progressing the
>> architecture document]
>>
>> Hi Leon,
>>
>> I am still having a hard time understanding why we need the session
> state information per CS
>> participant? Why is this required, who uses it, and how?
>>
>> Thanks,
>> Charles
>>
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>> Behalf Of Leon Portman
>>> Sent: Saturday, March 26, 2011 10:31 AM
>>> To: Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmohanr);
>> Hutton, Andrew
>>> Cc: siprec@ietf.org
>>> Subject: Re: [siprec] Dialog state in the CS block of metadatamodel
>> [wasRE:Progressing the
>>> architecture document]
>>>
>>> John Hello
>>>
>>> I agree that SRS (and its application clients) interested in SESSION
>> level events and not underlying
>>> DIALOG events. However we do need to support reporting session state
>> information per CS  participant
>>> that sometimes equals to dialog level and sometimes not.
>>>
>>> We could have define more application level state events like
> instead
>> of TRYING ->  RINGING etc.
>>> However they could be domain specific.
>>>
>>> Leon
>>>
>>> -----Original Message-----
>>> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
>>> Sent: Thursday, March 24, 2011 6:34 PM
>>> To: Parthasarathi R (partr); Ram Mohan R (rmohanr); Leon Portman;
>> Hutton, Andrew
>>> Cc: siprec@ietf.org
>>> Subject: RE: [siprec] Dialog state in the CS block of metadata model
>> [wasRE:Progressing the
>>> architecture document]
>>>
>>> This discussion gives me some concerns, echoing to some extent what
>> Ram is saying.
>>>
>>> SIPREC is about session recording, where a session is the
> information
>> exchanged between participants
>>> in a CS (the media streams) plus metadata. The metadata should
> provide
>> additional information about
>>> the CS. This means information about the communication SESSION, not
>> about the SIP dialog that is used
>>> to control that session. With this in mind, consider the following
>> points, some of which have already
>>> been raised:
>>>
>>> 1. There may be more than one SIP dialog involved if the SRC is at a
>> B2BUA or conference focus.
>>>
>>> 2. Does the CS necessarily need to be controlled by SIP? For
> example,
>> it could be a PSTN call, an RTC-
>>> Web call or a Jingle call. None of these preclude using SIP for the
> RS
>> (that is what the charter of
>>> SIPREC is all about - a SIP-based RS).
>>>
>>> 3. Somebody retrieving and playing back a recorded CS will be
>> interested in session-related events
>>> like participants leaving and joining (including the first
>> participants joining at the start of the CS
>>> and the last participants leaving a the end of the CS), media
> streams
>> starting and ending and
>>> participants starting or stopping receipt of a media stream. In
> other
>> words, changes of SESSION state,
>>> not dialog state.
>>>
>>> 4. Some of the SIP dialog states just don't seem relevant. The
>> distinction between early dialog and
>>> full dialog in SIP does not necessarily corresponding to any
>> meaningful state change of the session.
>>> For example, A makes a call to B and B answers and starts sending
>> media. A receives and renders media
>>> (perhaps it has already received SDP answer, allowing it to verify
> the
>> source of the media). Then A
>>> receives the 200 OK (transitioning from an early dialog to a full
>> dialog) and continues to receive
>>> media. So although there is a dialog state change, there is not
> really
>> a session state change.
>>>
>>> The bit about dialog state in the architecture draft is, in my
>> opinion, a legacy from some earlier
>>> discussions, before we started having the metadata discussions. I
>> think the metadata discussions have
>>> taken us in the right direction.
>>>
>>> John (as individual)
>>>
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org
>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
>> (partr)
>>>> Sent: 24 March 2011 02:36
>>>> To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] Dialog state in the CS block of metadata
> model
>>>> [wasRE:Progressing the architecture document]
>>>>
>>>> Ram,
>>>>
>>>> Please read inline.
>>>>
>>>> Thanks
>>>> Partha
>>>>
>>>> ________________________________
>>>>
>>>> From: Ram Mohan R (rmohanr)
>>>> Sent: Wed 3/23/2011 7:59 PM
>>>> To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: [siprec] Dialog state in the CS block of metadata
> model
>>>> [wasRE:Progressing the architecture document]
>>>>
>>>>
>>>>
>>>> I am still trying to understand what is the significance of this
>>>> attribute w.r.t CS. Are we saying the attribute represents the
> state
>>>> of CS ?
>>>>
>>>> Note that CS need not be one dialog.
>>>>
>>>> <Partha>   The attribute is to show the state of CS only. As it is
>> not
>>>> single dialog, I have mentioned as session state attribute
> </Partha>
>>>>
>>>> For cases like Conference where there may be different
> participants,
>>>> if SRC happens to be Focus how do you derive/what is "session
> state"
>> ?
>>>>
>>>> <Partha>  I really don't know whether it is generic. My thought
>>>> processing of session state for conference is as follows:
>>>>
>>>>
>>>>
>>>> 1) First participant of conference early media (ivr play) may be
>>>> considered as "early" state of session.
>>>>
>>>> 2) The session state is chaged to confirmed in case any one of the
>>>> participant joined in the conference.
>>>>
>>>> 3) The session state is move to terminated when the last
> participant
>>>> moved out of the conference.
>>>>
>>>>
>>>>
>>>> Please let me know in case other way to represent the session
> state
>> of
>>>> conference</partha>
>>>>
>>>>
>>>>
>>>> For cases where B2BUA acts as SRC what is "session state" ?
>>>>
>>>> <partha>  It looks straight forward for me. In B2BUA case ,
>>>>
>>>> 1) The stage where in two party is not connected, it is considered
>> as
>>>> early state.
>>>>
>>>> 2) when both are connected, it is confirmed state
>>>>
>>>> 3) In case of BYE received from any one of the party, then CS is
>>>> considered as terminated state
>>>>
>>>>
>>>>
>>>> Please note that this is applicable for 3PCC as well.</partha>
>>>>
>>>>
>>>>
>>>> Ram
>>>>
>>>>
>>>>
>>>> From: siprec-bounces@ietf.org
>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
>> (partr)
>>>> Sent: Wednesday, March 23, 2011 6:13 AM
>>>> To: Leon Portman; Hutton, Andrew
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] Dialog state in the CS block of metadata
> model
>>>> [wasRE:Progressing the architecture document]
>>>>
>>>>
>>>>
>>>> Leon,
>>>>
>>>>
>>>>
>>>> Shall we have optional "event" attribute to indicate the state
>> change
>>>> which is similar to "event" attribute in RFC 4235.  The "event"
> will
>>>> include the following:
>>>>
>>>>
>>>>
>>>> 1) cancelled
>>>>
>>>> 2) rejected
>>>>
>>>> 3) replaced
>>>>
>>>> 4) bye
>>>>
>>>> 5) error
>>>>
>>>> 6) timeout
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Partha
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>> Sent: Tue 3/22/2011 9:37 PM
>>>> To: Hutton, Andrew; Parthasarathi R (partr)
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: Dialog state in the CS block of metadata model [was
>>>> RE:Progressing the architecture document]
>>>>
>>>> It can be either application level error or dialog level errors -
>> like
>>>> timeout or failures.
>>>>
>>>>
>>>>
>>>> Leon
>>>>
>>>>
>>>>
>>>> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
>>>> Sent: Tuesday, March 22, 2011 6:02 PM
>>>> To: Leon Portman; Parthasarathi R (partr)
>>>> Cc: siprec@ietf.org
>>>> Subject: RE: Dialog state in the CS block of metadata model [was
> RE:
>>>> Progressing the architecture document]
>>>>
>>>>
>>>>
>>>> What would it be used for?
>>>>
>>>>
>>>>
>>>> Regards
>>>>
>>>> Andy
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>>    From: Leon Portman [mailto:Leon.Portman@nice.com]
>>>>    Sent: 22 March 2011 14:11
>>>>    To: Parthasarathi R (partr); Hutton, Andrew
>>>>    Cc: siprec@ietf.org
>>>>    Subject: RE: Dialog state in the CS block of metadata model [was
>> RE:
>>>> Progressing the architecture document]
>>>>
>>>>    Should we have error state as well?
>>>>
>>>>
>>>>
>>>>    Leon
>>>>
>>>>
>>>>
>>>>    From: siprec-bounces@ietf.org
>>>> [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
>> (partr)
>>>>    Sent: Tuesday, March 22, 2011 3:33 PM
>>>>    To: Parthasarathi R (partr); Hutton, Andrew
>>>>    Cc: siprec@ietf.org
>>>>    Subject: [siprec] Dialog state in the CS block of metadata model
>> [was
>>>> RE: Progressing the architecture document]
>>>>
>>>>
>>>>
>>>>    The architecture document proposes to have dialog/session state
>> in
>>>> Metadata model. To achieve this, "session state" attribute has to
> be
>>>> added in the CS block of Metadata model. The possible values for
>>>> session state are
>>>>
>>>>
>>>>
>>>>    1) Trying
>>>>
>>>>    2) Proceeding
>>>>
>>>>    3) Early
>>>>
>>>>    4) Confirmed
>>>>
>>>>    5) Terminated
>>>>
>>>>
>>>>
>>>>    Please let me know in case any objection to add this attribute
>> in
>>>> Metadata model.
>>>>
>>>>
>>>>
>>>>    Thanks
>>>>
>>>>    Partha
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>>    From: Parthasarathi R (partr)
>>>>    Sent: Wednesday, March 16, 2011 5:40 AM
>>>>    To: Hutton, Andrew
>>>>    Cc: Elwell, John; siprec@ietf.org
>>>>    Subject: RE: Progressing the architecture document
>>>>
>>>>    >  -----Original Message-----
>>>>    >  From: siprec-bounces@ietf.org
>>>>    >  [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
>>>> (partr)
>>>>    >  Sent: 14 March 2011 17:05
>>>>    >  To: Elwell, John; siprec@ietf.org
>>>>    >  Subject: Re: [siprec] Progressing the architecture document
>>>>
>>>>    >
>>>>    >  Sec 4.3.1 whether 3rd bullet is required?
>>>>    >
>>>>
>>>>    [AndyH]I assume it is as for example I assume it would be
>> necessary
>>>> to record early-media and update the SRS when the dialog changes
> to
>>>> the confirmed or terminated state. Does not seem to be in the
>> metadata
>>>> draft though. In the end I will either remove these bullets or
> align
>>>> with the metadata draft.
>>>>    <Partha>  It is a good point. Dialog state shall be added as one
>> of
>>>> the optional attribute in CS metadata block with default value as
>>>> mid-dialog. This helps to differentiate between early dialog
>>>> (ringback) vs mid-dialog (normal
>>>> conversation) in recording. In case of no objection for this
>> attribute
>>>> in metadata model, we will add it. We will work out metadata
> format
>>>> once the consensus occurs for metadata model.
>>>> In case required, we will span separate mail thread to close this
>>>> issue</Partha>
>>>>
>>>>
>>> _______________________________________________
>>> 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
>

From john.elwell@siemens-enterprise.com  Sun Mar 27 06:48:39 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1587D3A684F for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 06:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05WdSrP8sShy for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 06:48:37 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id BCE093A683F for <siprec@ietf.org>; Sun, 27 Mar 2011 06:48:36 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3899184; Sun, 27 Mar 2011 15:49:54 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id B943E23F028E; Sun, 27 Mar 2011 15:49:54 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Sun, 27 Mar 2011 15:49:54 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Date: Sun, 27 Mar 2011 15:49:52 +0200
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsAAClqhQAAXOdEA=
Message-ID: <A444A0F8084434499206E78C106220CA0875AF2B09@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 27 Mar 2011 13:48:39 -0000

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 27 March 2011 11:48
> To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R
> (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture document]
>
> Charles Hi
>
> Yes, it will be good to discuss it face to face.
>
> Just little background for such requirements. Today,
> especially for contact centers, it is important for SRS to
> capture the information how long customer was waiting for
> agent to answer the call, which party hang up, how long was
> the hold time, if it was blind transfer or consultation
> transfer. This information important both from quality
> management point of view and customer experience point of
> view.
[JRE] (as chair) I think the group needs to consider whether this is within=
 scope. Looking at the requirements, we have:
"REQ-012 The mechanism MUST provide the SRS with metadata describing
   CSs that are being recorded, including the media being used and the
   identities of parties involved."
If we are not recording the session while the caller is waiting to be answe=
red, it seems we perhaps don't have a requirement for metadata about that. =
This seems to be more about call detail recording (CDR) rather than session=
 recording. We can by all means have this discussion, but I am concerned ab=
out scope creep.

> It is important also from compliance point of view to
> detect if somebody actually received the media stream or
> still was in pending state or media stream was disconnected.
[JRE] (as individual) I agree we should show a participant as receiving med=
ia only if the SRC believes media is actually being sent to that participan=
t (even then, there can be no guarantee it is received, e.g., because NAT o=
r firewall traversal isn't functioning properly, severe packet loss, speake=
r volume is muted, etc..). But I have doubts whether it is necessarily to t=
ry to account for periods when the SRC knows a participant is not receiving=
 media by saying it is because of alerting, hold or whatever.

John


>
> Leon
>
> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: Sunday, March 27, 2011 11:35 AM
> To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram
> Mohan R (rmohanr); Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture document]
>
> Hi Leon,
>
> Thank you for your patience in trying to explain this to me;
> however, I still am not able to understand why the SRS might
> need to know this information, or what it would do with it.
> Is it that you need to know when a given participant was
> receiving the recorded media and when it was not? If so, I do
> not think dialog state is sufficient. Is there some other
> requirement or functionality addressed by the SRS having such
> information?
> Perhaps it is easier to discuss in person at the breakfast
> meeting Wednesday or during the working group session.
>
> Cheers,
> Charles
>
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Saturday, March 26, 2011 8:15 PM
> > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R (partr);
> Ram Mohan R (rmohanr); Hutton,
> > Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture
> > document]
> >
> > Charles Hi
> >
> > Without participant session state, SRS will know only when
> participant
> is part of the session and will
> > not know about intermediate states like ringing, retrying etc.
> > I know that we have media stream information per participant but not
> sure that it is enough.
> >
> > Leon
> > -----Original Message-----
> > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > Sent: Saturday, March 26, 2011 9:07 PM
> > To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram Mohan R
> (rmohanr); Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of metadatamodel
> [wasRE:Progressing the
> > architecture document]
> >
> > Hi Leon,
> >
> > I am still having a hard time understanding why we need the session
> state information per CS
> > participant? Why is this required, who uses it, and how?
> >
> > Thanks,
> > Charles
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Leon Portman
> > > Sent: Saturday, March 26, 2011 10:31 AM
> > > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R (rmohanr);
> > Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Dialog state in the CS block of
> metadatamodel
> > [wasRE:Progressing the
> > > architecture document]
> > >
> > > John Hello
> > >
> > > I agree that SRS (and its application clients) interested
> in SESSION
> > level events and not underlying
> > > DIALOG events. However we do need to support reporting
> session state
> > information per CS  participant
> > > that sometimes equals to dialog level and sometimes not.
> > >
> > > We could have define more application level state events like
> instead
> > of TRYING - > RINGING etc.
> > > However they could be domain specific.
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > Sent: Thursday, March 24, 2011 6:34 PM
> > > To: Parthasarathi R (partr); Ram Mohan R (rmohanr); Leon Portman;
> > Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of
> metadata model
> > [wasRE:Progressing the
> > > architecture document]
> > >
> > > This discussion gives me some concerns, echoing to some
> extent what
> > Ram is saying.
> > >
> > > SIPREC is about session recording, where a session is the
> information
> > exchanged between participants
> > > in a CS (the media streams) plus metadata. The metadata should
> provide
> > additional information about
> > > the CS. This means information about the communication
> SESSION, not
> > about the SIP dialog that is used
> > > to control that session. With this in mind, consider the following
> > points, some of which have already
> > > been raised:
> > >
> > > 1. There may be more than one SIP dialog involved if the
> SRC is at a
> > B2BUA or conference focus.
> > >
> > > 2. Does the CS necessarily need to be controlled by SIP? For
> example,
> > it could be a PSTN call, an RTC-
> > > Web call or a Jingle call. None of these preclude using
> SIP for the
> RS
> > (that is what the charter of
> > > SIPREC is all about - a SIP-based RS).
> > >
> > > 3. Somebody retrieving and playing back a recorded CS will be
> > interested in session-related events
> > > like participants leaving and joining (including the first
> > participants joining at the start of the CS
> > > and the last participants leaving a the end of the CS), media
> streams
> > starting and ending and
> > > participants starting or stopping receipt of a media stream. In
> other
> > words, changes of SESSION state,
> > > not dialog state.
> > >
> > > 4. Some of the SIP dialog states just don't seem relevant. The
> > distinction between early dialog and
> > > full dialog in SIP does not necessarily corresponding to any
> > meaningful state change of the session.
> > > For example, A makes a call to B and B answers and starts sending
> > media. A receives and renders media
> > > (perhaps it has already received SDP answer, allowing it to verify
> the
> > source of the media). Then A
> > > receives the 200 OK (transitioning from an early dialog to a full
> > dialog) and continues to receive
> > > media. So although there is a dialog state change, there is not
> really
> > a session state change.
> > >
> > > The bit about dialog state in the architecture draft is, in my
> > opinion, a legacy from some earlier
> > > discussions, before we started having the metadata discussions. I
> > think the metadata discussions have
> > > taken us in the right direction.
> > >
> > > John (as individual)
> > >
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > (partr)
> > > > Sent: 24 March 2011 02:36
> > > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] Dialog state in the CS block of metadata
> model
> > > > [wasRE:Progressing the architecture document]
> > > >
> > > > Ram,
> > > >
> > > > Please read inline.
> > > >
> > > > Thanks
> > > > Partha
> > > >
> > > > ________________________________
> > > >
> > > > From: Ram Mohan R (rmohanr)
> > > > Sent: Wed 3/23/2011 7:59 PM
> > > > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of metadata
> model
> > > > [wasRE:Progressing the architecture document]
> > > >
> > > >
> > > >
> > > > I am still trying to understand what is the significance of this
> > > > attribute w.r.t CS. Are we saying the attribute represents the
> state
> > > > of CS ?
> > > >
> > > > Note that CS need not be one dialog.
> > > >
> > > > <Partha>  The attribute is to show the state of CS
> only. As it is
> > not
> > > > single dialog, I have mentioned as session state attribute
> </Partha>
> > > >
> > > > For cases like Conference where there may be different
> participants,
> > > > if SRC happens to be Focus how do you derive/what is "session
> state"
> > ?
> > > >
> > > > <Partha> I really don't know whether it is generic. My thought
> > > > processing of session state for conference is as follows:
> > > >
> > > >
> > > >
> > > > 1) First participant of conference early media (ivr play) may be
> > > > considered as "early" state of session.
> > > >
> > > > 2) The session state is chaged to confirmed in case any
> one of the
> > > > participant joined in the conference.
> > > >
> > > > 3) The session state is move to terminated when the last
> participant
> > > > moved out of the conference.
> > > >
> > > >
> > > >
> > > > Please let me know in case other way to represent the session
> state
> > of
> > > > conference </partha>
> > > >
> > > >
> > > >
> > > > For cases where B2BUA acts as SRC what is "session state" ?
> > > >
> > > > <partha> It looks straight forward for me. In B2BUA case ,
> > > >
> > > > 1) The stage where in two party is not connected, it is
> considered
> > as
> > > > early state.
> > > >
> > > > 2) when both are connected, it is confirmed state
> > > >
> > > > 3) In case of BYE received from any one of the party, then CS is
> > > > considered as terminated state
> > > >
> > > >
> > > >
> > > > Please note that this is applicable for 3PCC as well.
> </partha>
> > > >
> > > >
> > > >
> > > > Ram
> > > >
> > > >
> > > >
> > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > (partr)
> > > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > > To: Leon Portman; Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] Dialog state in the CS block of metadata
> model
> > > > [wasRE:Progressing the architecture document]
> > > >
> > > >
> > > >
> > > > Leon,
> > > >
> > > >
> > > >
> > > > Shall we have optional "event" attribute to indicate the state
> > change
> > > > which is similar to "event" attribute in RFC 4235.  The "event"
> will
> > > > include the following:
> > > >
> > > >
> > > >
> > > > 1) cancelled
> > > >
> > > > 2) rejected
> > > >
> > > > 3) replaced
> > > >
> > > > 4) bye
> > > >
> > > > 5) error
> > > >
> > > > 6) timeout
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > > Partha
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: Tue 3/22/2011 9:37 PM
> > > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: Dialog state in the CS block of metadata model [was
> > > > RE:Progressing the architecture document]
> > > >
> > > > It can be either application level error or dialog
> level errors -
> > like
> > > > timeout or failures.
> > > >
> > > >
> > > >
> > > > Leon
> > > >
> > > >
> > > >
> > > > From: Hutton, Andrew
> [mailto:andrew.hutton@siemens-enterprise.com]
> > > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > > To: Leon Portman; Parthasarathi R (partr)
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: Dialog state in the CS block of metadata model [was
> RE:
> > > > Progressing the architecture document]
> > > >
> > > >
> > > >
> > > > What would it be used for?
> > > >
> > > >
> > > >
> > > > Regards
> > > >
> > > > Andy
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > >   From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > >   Sent: 22 March 2011 14:11
> > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > >   Cc: siprec@ietf.org
> > > >   Subject: RE: Dialog state in the CS block of metadata
> model [was
> > RE:
> > > > Progressing the architecture document]
> > > >
> > > >   Should we have error state as well?
> > > >
> > > >
> > > >
> > > >   Leon
> > > >
> > > >
> > > >
> > > >   From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > (partr)
> > > >   Sent: Tuesday, March 22, 2011 3:33 PM
> > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > >   Cc: siprec@ietf.org
> > > >   Subject: [siprec] Dialog state in the CS block of
> metadata model
> > [was
> > > > RE: Progressing the architecture document]
> > > >
> > > >
> > > >
> > > >   The architecture document proposes to have
> dialog/session state
> > in
> > > > Metadata model. To achieve this, "session state"
> attribute has to
> be
> > > > added in the CS block of Metadata model. The possible values for
> > > > session state are
> > > >
> > > >
> > > >
> > > >   1) Trying
> > > >
> > > >   2) Proceeding
> > > >
> > > >   3) Early
> > > >
> > > >   4) Confirmed
> > > >
> > > >   5) Terminated
> > > >
> > > >
> > > >
> > > >   Please let me know in case any objection to add this attribute
> > in
> > > > Metadata model.
> > > >
> > > >
> > > >
> > > >   Thanks
> > > >
> > > >   Partha
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > >   From: Parthasarathi R (partr)
> > > >   Sent: Wednesday, March 16, 2011 5:40 AM
> > > >   To: Hutton, Andrew
> > > >   Cc: Elwell, John; siprec@ietf.org
> > > >   Subject: RE: Progressing the architecture document
> > > >
> > > >   > -----Original Message-----
> > > >   > From: siprec-bounces@ietf.org
> > > >   > [mailto:siprec-bounces@ietf.org] On Behalf Of
> Parthasarathi R
> > > > (partr)
> > > >   > Sent: 14 March 2011 17:05
> > > >   > To: Elwell, John; siprec@ietf.org
> > > >   > Subject: Re: [siprec] Progressing the architecture document
> > > >
> > > >   >
> > > >   > Sec 4.3.1 whether 3rd bullet is required?
> > > >   >
> > > >
> > > >   [AndyH]I assume it is as for example I assume it would be
> > necessary
> > > > to record early-media and update the SRS when the dialog changes
> to
> > > > the confirmed or terminated state. Does not seem to be in the
> > metadata
> > > > draft though. In the end I will either remove these bullets or
> align
> > > > with the metadata draft.
> > > >   <Partha> It is a good point. Dialog state shall be
> added as one
> > of
> > > > the optional attribute in CS metadata block with
> default value as
> > > > mid-dialog. This helps to differentiate between early dialog
> > > > (ringback) vs mid-dialog (normal
> > > > conversation) in recording. In case of no objection for this
> > attribute
> > > > in metadata model, we will add it. We will work out metadata
> format
> > > > once the consensus occurs for metadata model.
> > > > In case required, we will span separate mail thread to
> close this
> > > > issue </Partha>
> > > >
> > > >
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
>

From john.elwell@siemens-enterprise.com  Sun Mar 27 12:59:50 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57A5E3A6935 for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 12:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQMVPGmdSuKn for <siprec@core3.amsl.com>; Sun, 27 Mar 2011 12:59:49 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 1918D3A6934 for <siprec@ietf.org>; Sun, 27 Mar 2011 12:59:48 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3898776; Sun, 27 Mar 2011 22:01:23 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id F10B81EB82B4; Sun, 27 Mar 2011 22:01:22 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Sun, 27 Mar 2011 22:01:22 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Date: Sun, 27 Mar 2011 22:01:21 +0200
Thread-Topic: review comments in draft-ietf-siprec-req-08
Thread-Index: Acvr47UAX8D7l37XSfOnWkAVcgVa0QA1LRKw
Message-ID: <A444A0F8084434499206E78C106220CA0875AF2B2B@MCHP058A.global-ad.net>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA1@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA1@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] review comments in draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 27 Mar 2011 19:59:50 -0000

(Question for Gonzalo below)=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel (eckelcu)
> Sent: 26 March 2011 18:29
> To: siprec@ietf.org
> Subject: [siprec] review comments in draft-ietf-siprec-req-08
>=20
> Section 3, it would be better to refer to arch draft for definitions
> rather than repeating here and in other drafts.
[JRE] Since the requirements draft is first, I would say keep the definitio=
ns in the requirements draft and remove them from the architecture draft.

>=20
> Section 5, Req-024 conflicts with architecture draft. I think=20
> Req-024 is
> correct and architecture document needs to be updated accordingly.
[JRE] Yes, the architecture document should be aligned.

>=20
> Section 6, change "although any user can terminate a CS" to "although
> any user can terminate its participation in a CS."
[JRE] This sounds like a reasonable change, but don't forget that the docum=
ent has already left the WG and at present we are just addressing comments =
from the AD. However, I don't think this is controversial, so if the AD agr=
ees. Gonzalo?

John


>=20
> Cheers,
> Charles
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From andrew.hutton@siemens-enterprise.com  Mon Mar 28 00:11:59 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F4C13A6834 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 00:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.17
X-Spam-Level: 
X-Spam-Status: No, score=-2.17 tagged_above=-999 required=5 tests=[AWL=0.429,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Dnr8WJuvIw5 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 00:11:57 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 9F2813A681E for <siprec@ietf.org>; Mon, 28 Mar 2011 00:11:56 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3892020; Mon, 28 Mar 2011 09:13:28 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 23CCF1EB82AE; Mon, 28 Mar 2011 09:13:28 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 28 Mar 2011 09:13:28 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, Leon Portman <Leon.Portman@nice.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
Date: Mon, 28 Mar 2011 09:13:27 +0200
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsAAClqhQAAXOdEAADtUDkA==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED8E0@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2B09@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF2B09@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 07:11:59 -0000

Hi,

The draft-ietf-siprec-architecture has from the very beginning listed dialo=
g state as an example of what would be included in metadata which is why I =
raised the question.

However it is true to say this was put in the architecture document before =
we had firmed up the requirements or starting any indepth work on metadata =
so I could accept that the architecture draft simply got this wrong from th=
e start and it maybe should be removed. We could of course take the view th=
at if dialog events are important then the SRS could subscribe to the dialo=
g event package at the SRC and SIPREC does not need to touch this.

I don't think we can allow SIPREC metadata to extend as far as reporting ev=
erything that happens to the CS including how it is linked to other CS's an=
d what services are used on the CS (E.g. types of transfer etc.). This woul=
d quickly get very difficult to define and we would probably fail.

I would prefer to not report this state information in metadata than open u=
p the possibility of adding lots of complexity.

Regards
Andy









> -----Original Message-----
> From: Elwell, John
> Sent: 27 March 2011 14:50
> To: Leon Portman; Charles Eckel (eckelcu); Parthasarathi R
> (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture document]
>
>
>
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 27 March 2011 11:48
> > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R
> > (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel[wasRE:Progressing the architecture document]
> >
> > Charles Hi
> >
> > Yes, it will be good to discuss it face to face.
> >
> > Just little background for such requirements. Today,
> > especially for contact centers, it is important for SRS to
> > capture the information how long customer was waiting for
> > agent to answer the call, which party hang up, how long was
> > the hold time, if it was blind transfer or consultation
> > transfer. This information important both from quality
> > management point of view and customer experience point of
> > view.
> [JRE] (as chair) I think the group needs to consider whether
> this is within scope. Looking at the requirements, we have:
> "REQ-012 The mechanism MUST provide the SRS with metadata describing
>    CSs that are being recorded, including the media being used and the
>    identities of parties involved."
> If we are not recording the session while the caller is
> waiting to be answered, it seems we perhaps don't have a
> requirement for metadata about that. This seems to be more
> about call detail recording (CDR) rather than session
> recording. We can by all means have this discussion, but I am
> concerned about scope creep.
>
> > It is important also from compliance point of view to
> > detect if somebody actually received the media stream or
> > still was in pending state or media stream was disconnected.
> [JRE] (as individual) I agree we should show a participant as
> receiving media only if the SRC believes media is actually
> being sent to that participant (even then, there can be no
> guarantee it is received, e.g., because NAT or firewall
> traversal isn't functioning properly, severe packet loss,
> speaker volume is muted, etc..). But I have doubts whether it
> is necessarily to try to account for periods when the SRC
> knows a participant is not receiving media by saying it is
> because of alerting, hold or whatever.
>
> John
>
>
> >
> > Leon
> >
> > -----Original Message-----
> > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > Sent: Sunday, March 27, 2011 11:35 AM
> > To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram
> > Mohan R (rmohanr); Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel[wasRE:Progressing the architecture document]
> >
> > Hi Leon,
> >
> > Thank you for your patience in trying to explain this to me;
> > however, I still am not able to understand why the SRS might
> > need to know this information, or what it would do with it.
> > Is it that you need to know when a given participant was
> > receiving the recorded media and when it was not? If so, I do
> > not think dialog state is sufficient. Is there some other
> > requirement or functionality addressed by the SRS having such
> > information?
> > Perhaps it is easier to discuss in person at the breakfast
> > meeting Wednesday or during the working group session.
> >
> > Cheers,
> > Charles
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: Saturday, March 26, 2011 8:15 PM
> > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi
> R (partr);
> > Ram Mohan R (rmohanr); Hutton,
> > > Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel[wasRE:Progressing the architecture
> > > document]
> > >
> > > Charles Hi
> > >
> > > Without participant session state, SRS will know only when
> > participant
> > is part of the session and will
> > > not know about intermediate states like ringing, retrying etc.
> > > I know that we have media stream information per
> participant but not
> > sure that it is enough.
> > >
> > > Leon
> > > -----Original Message-----
> > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > Sent: Saturday, March 26, 2011 9:07 PM
> > > To: Leon Portman; Elwell, John; Parthasarathi R (partr);
> Ram Mohan R
> > (rmohanr); Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel
> > [wasRE:Progressing the
> > > architecture document]
> > >
> > > Hi Leon,
> > >
> > > I am still having a hard time understanding why we need
> the session
> > state information per CS
> > > participant? Why is this required, who uses it, and how?
> > >
> > > Thanks,
> > > Charles
> > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Leon Portman
> > > > Sent: Saturday, March 26, 2011 10:31 AM
> > > > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R
> (rmohanr);
> > > Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: Re: [siprec] Dialog state in the CS block of
> > metadatamodel
> > > [wasRE:Progressing the
> > > > architecture document]
> > > >
> > > > John Hello
> > > >
> > > > I agree that SRS (and its application clients) interested
> > in SESSION
> > > level events and not underlying
> > > > DIALOG events. However we do need to support reporting
> > session state
> > > information per CS  participant
> > > > that sometimes equals to dialog level and sometimes not.
> > > >
> > > > We could have define more application level state events like
> > instead
> > > of TRYING - > RINGING etc.
> > > > However they could be domain specific.
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > > Sent: Thursday, March 24, 2011 6:34 PM
> > > > To: Parthasarathi R (partr); Ram Mohan R (rmohanr);
> Leon Portman;
> > > Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > metadata model
> > > [wasRE:Progressing the
> > > > architecture document]
> > > >
> > > > This discussion gives me some concerns, echoing to some
> > extent what
> > > Ram is saying.
> > > >
> > > > SIPREC is about session recording, where a session is the
> > information
> > > exchanged between participants
> > > > in a CS (the media streams) plus metadata. The metadata should
> > provide
> > > additional information about
> > > > the CS. This means information about the communication
> > SESSION, not
> > > about the SIP dialog that is used
> > > > to control that session. With this in mind, consider
> the following
> > > points, some of which have already
> > > > been raised:
> > > >
> > > > 1. There may be more than one SIP dialog involved if the
> > SRC is at a
> > > B2BUA or conference focus.
> > > >
> > > > 2. Does the CS necessarily need to be controlled by SIP? For
> > example,
> > > it could be a PSTN call, an RTC-
> > > > Web call or a Jingle call. None of these preclude using
> > SIP for the
> > RS
> > > (that is what the charter of
> > > > SIPREC is all about - a SIP-based RS).
> > > >
> > > > 3. Somebody retrieving and playing back a recorded CS will be
> > > interested in session-related events
> > > > like participants leaving and joining (including the first
> > > participants joining at the start of the CS
> > > > and the last participants leaving a the end of the CS), media
> > streams
> > > starting and ending and
> > > > participants starting or stopping receipt of a media stream. In
> > other
> > > words, changes of SESSION state,
> > > > not dialog state.
> > > >
> > > > 4. Some of the SIP dialog states just don't seem relevant. The
> > > distinction between early dialog and
> > > > full dialog in SIP does not necessarily corresponding to any
> > > meaningful state change of the session.
> > > > For example, A makes a call to B and B answers and
> starts sending
> > > media. A receives and renders media
> > > > (perhaps it has already received SDP answer, allowing
> it to verify
> > the
> > > source of the media). Then A
> > > > receives the 200 OK (transitioning from an early dialog
> to a full
> > > dialog) and continues to receive
> > > > media. So although there is a dialog state change, there is not
> > really
> > > a session state change.
> > > >
> > > > The bit about dialog state in the architecture draft is, in my
> > > opinion, a legacy from some earlier
> > > > discussions, before we started having the metadata
> discussions. I
> > > think the metadata discussions have
> > > > taken us in the right direction.
> > > >
> > > > John (as individual)
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > > (partr)
> > > > > Sent: 24 March 2011 02:36
> > > > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] Dialog state in the CS block of metadata
> > model
> > > > > [wasRE:Progressing the architecture document]
> > > > >
> > > > > Ram,
> > > > >
> > > > > Please read inline.
> > > > >
> > > > > Thanks
> > > > > Partha
> > > > >
> > > > > ________________________________
> > > > >
> > > > > From: Ram Mohan R (rmohanr)
> > > > > Sent: Wed 3/23/2011 7:59 PM
> > > > > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of metadata
> > model
> > > > > [wasRE:Progressing the architecture document]
> > > > >
> > > > >
> > > > >
> > > > > I am still trying to understand what is the
> significance of this
> > > > > attribute w.r.t CS. Are we saying the attribute represents the
> > state
> > > > > of CS ?
> > > > >
> > > > > Note that CS need not be one dialog.
> > > > >
> > > > > <Partha>  The attribute is to show the state of CS
> > only. As it is
> > > not
> > > > > single dialog, I have mentioned as session state attribute
> > </Partha>
> > > > >
> > > > > For cases like Conference where there may be different
> > participants,
> > > > > if SRC happens to be Focus how do you derive/what is "session
> > state"
> > > ?
> > > > >
> > > > > <Partha> I really don't know whether it is generic. My thought
> > > > > processing of session state for conference is as follows:
> > > > >
> > > > >
> > > > >
> > > > > 1) First participant of conference early media (ivr
> play) may be
> > > > > considered as "early" state of session.
> > > > >
> > > > > 2) The session state is chaged to confirmed in case any
> > one of the
> > > > > participant joined in the conference.
> > > > >
> > > > > 3) The session state is move to terminated when the last
> > participant
> > > > > moved out of the conference.
> > > > >
> > > > >
> > > > >
> > > > > Please let me know in case other way to represent the session
> > state
> > > of
> > > > > conference </partha>
> > > > >
> > > > >
> > > > >
> > > > > For cases where B2BUA acts as SRC what is "session state" ?
> > > > >
> > > > > <partha> It looks straight forward for me. In B2BUA case ,
> > > > >
> > > > > 1) The stage where in two party is not connected, it is
> > considered
> > > as
> > > > > early state.
> > > > >
> > > > > 2) when both are connected, it is confirmed state
> > > > >
> > > > > 3) In case of BYE received from any one of the party,
> then CS is
> > > > > considered as terminated state
> > > > >
> > > > >
> > > > >
> > > > > Please note that this is applicable for 3PCC as well.
> > </partha>
> > > > >
> > > > >
> > > > >
> > > > > Ram
> > > > >
> > > > >
> > > > >
> > > > > From: siprec-bounces@ietf.org
> > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > > (partr)
> > > > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > > > To: Leon Portman; Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] Dialog state in the CS block of metadata
> > model
> > > > > [wasRE:Progressing the architecture document]
> > > > >
> > > > >
> > > > >
> > > > > Leon,
> > > > >
> > > > >
> > > > >
> > > > > Shall we have optional "event" attribute to indicate the state
> > > change
> > > > > which is similar to "event" attribute in RFC 4235.
> The "event"
> > will
> > > > > include the following:
> > > > >
> > > > >
> > > > >
> > > > > 1) cancelled
> > > > >
> > > > > 2) rejected
> > > > >
> > > > > 3) replaced
> > > > >
> > > > > 4) bye
> > > > >
> > > > > 5) error
> > > > >
> > > > > 6) timeout
> > > > >
> > > > >
> > > > >
> > > > > Thanks
> > > > >
> > > > > Partha
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > >
> > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > Sent: Tue 3/22/2011 9:37 PM
> > > > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: Dialog state in the CS block of metadata
> model [was
> > > > > RE:Progressing the architecture document]
> > > > >
> > > > > It can be either application level error or dialog
> > level errors -
> > > like
> > > > > timeout or failures.
> > > > >
> > > > >
> > > > >
> > > > > Leon
> > > > >
> > > > >
> > > > >
> > > > > From: Hutton, Andrew
> > [mailto:andrew.hutton@siemens-enterprise.com]
> > > > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > > > To: Leon Portman; Parthasarathi R (partr)
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: Dialog state in the CS block of metadata
> model [was
> > RE:
> > > > > Progressing the architecture document]
> > > > >
> > > > >
> > > > >
> > > > > What would it be used for?
> > > > >
> > > > >
> > > > >
> > > > > Regards
> > > > >
> > > > > Andy
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > >
> > > > >   From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > >   Sent: 22 March 2011 14:11
> > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > >   Cc: siprec@ietf.org
> > > > >   Subject: RE: Dialog state in the CS block of metadata
> > model [was
> > > RE:
> > > > > Progressing the architecture document]
> > > > >
> > > > >   Should we have error state as well?
> > > > >
> > > > >
> > > > >
> > > > >   Leon
> > > > >
> > > > >
> > > > >
> > > > >   From: siprec-bounces@ietf.org
> > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
> > > (partr)
> > > > >   Sent: Tuesday, March 22, 2011 3:33 PM
> > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > >   Cc: siprec@ietf.org
> > > > >   Subject: [siprec] Dialog state in the CS block of
> > metadata model
> > > [was
> > > > > RE: Progressing the architecture document]
> > > > >
> > > > >
> > > > >
> > > > >   The architecture document proposes to have
> > dialog/session state
> > > in
> > > > > Metadata model. To achieve this, "session state"
> > attribute has to
> > be
> > > > > added in the CS block of Metadata model. The possible
> values for
> > > > > session state are
> > > > >
> > > > >
> > > > >
> > > > >   1) Trying
> > > > >
> > > > >   2) Proceeding
> > > > >
> > > > >   3) Early
> > > > >
> > > > >   4) Confirmed
> > > > >
> > > > >   5) Terminated
> > > > >
> > > > >
> > > > >
> > > > >   Please let me know in case any objection to add
> this attribute
> > > in
> > > > > Metadata model.
> > > > >
> > > > >
> > > > >
> > > > >   Thanks
> > > > >
> > > > >   Partha
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > >
> > > > >   From: Parthasarathi R (partr)
> > > > >   Sent: Wednesday, March 16, 2011 5:40 AM
> > > > >   To: Hutton, Andrew
> > > > >   Cc: Elwell, John; siprec@ietf.org
> > > > >   Subject: RE: Progressing the architecture document
> > > > >
> > > > >   > -----Original Message-----
> > > > >   > From: siprec-bounces@ietf.org
> > > > >   > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > Parthasarathi R
> > > > > (partr)
> > > > >   > Sent: 14 March 2011 17:05
> > > > >   > To: Elwell, John; siprec@ietf.org
> > > > >   > Subject: Re: [siprec] Progressing the
> architecture document
> > > > >
> > > > >   >
> > > > >   > Sec 4.3.1 whether 3rd bullet is required?
> > > > >   >
> > > > >
> > > > >   [AndyH]I assume it is as for example I assume it would be
> > > necessary
> > > > > to record early-media and update the SRS when the
> dialog changes
> > to
> > > > > the confirmed or terminated state. Does not seem to be in the
> > > metadata
> > > > > draft though. In the end I will either remove these bullets or
> > align
> > > > > with the metadata draft.
> > > > >   <Partha> It is a good point. Dialog state shall be
> > added as one
> > > of
> > > > > the optional attribute in CS metadata block with
> > default value as
> > > > > mid-dialog. This helps to differentiate between early dialog
> > > > > (ringback) vs mid-dialog (normal
> > > > > conversation) in recording. In case of no objection for this
> > > attribute
> > > > > in metadata model, we will add it. We will work out metadata
> > format
> > > > > once the consensus occurs for metadata model.
> > > > > In case required, we will span separate mail thread to
> > close this
> > > > > issue </Partha>
> > > > >
> > > > >
> > > > _______________________________________________
> > > > siprec mailing list
> > > > siprec@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/siprec
> >
>

From Leon.Portman@nice.com  Mon Mar 28 00:37:49 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89FB73A68AA for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 00:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.404
X-Spam-Level: 
X-Spam-Status: No, score=-2.404 tagged_above=-999 required=5 tests=[AWL=0.195,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WOpVN7zEsSQL for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 00:37:48 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id CBE293A688C for <siprec@ietf.org>; Mon, 28 Mar 2011 00:37:47 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Mon, 28 Mar 2011 09:39:24 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "siprec@ietf.org" <siprec@ietf.org>, "Ken Rehor (krehor) (krehor@cisco.com)" <krehor@cisco.com>
Date: Mon, 28 Mar 2011 09:39:17 +0200
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIAACWzYeAAL84ccA==
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB46695E@TLVMBX01.nice.com>
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 07:37:49 -0000

I want to propose following additional text for the Security Considerations=
 section (after the last paragraph)

"Communication Sessions and Recording Sessions will require different secur=
ity levels both for signaling and media, depending on deployment configurat=
ions. For some environments, for example, SRS and SRC will be collocated in=
 a secure network region and will not require same protection level as CS o=
ver public network. For other environments, SRS can be located in a public =
cloud and RS will require higher protection level then CS. Because of these=
 reasons, there is not direct relation between security level of Communicat=
ion Sessions and Recording Sessions"

Leon


-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Sunday, March 27, 2011 10:33 AM
To: Leon Portman; Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor) (k=
rehor@cisco.com)
Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08

Yes, indeed we had the discussion and came up with reasons you can't tie th=
e two together. So as Gonzalo suggests, some of that discussion needs to be=
 captured in the Security Considerations section.

John

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 26 March 2011 14:37
> To: Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor)=20
> (krehor@cisco.com); Elwell, John
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Hi,
>=20
> I want to touch security requirement: about security level of RS vs=20
> security level of CS. We had a long mailing list discussion (below)=20
> and it was decided not to have it, because it is more implementation=20
> details
>=20
> http://www.ietf.org/mail-archive/web/siprec/current/msg01164.html
>=20
> Regards
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> Sent: Wednesday, March 23, 2011 1:23 PM
> To: siprec@ietf.org
> Subject: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Hi,
>=20
> the SIPREC WG requested the publication of the following draft a few=20
> days ago. Please, find below my AD review.
>=20
> https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
>=20
> Given that the draft contains both requirements and use cases, you may=20
> want to edit the title so that it reads "Use Cases and Requirements=20
> for ..."
>=20
> Typically, Section 1 contains the Introduction and Section 2 the=20
> terminology. You may want to swap both sections.
>=20
> Most of the requirements are phrased so that they describe=20
> capabilities that need to be supported by the system (e.g., the=20
> mechanism MUST provide the SRS with the means to ...) but that do not=20
> need to be necessarily used (e.g., a particular use case may not make=20
> use of that functionality). However, some requirements are phrased so=20
> that the functionality needs to be used (e.g., the mechanism MUST=20
> provide the SRS the wall clock time ...). Requirements 12, 22, 23, 27,=20
> 28, and 29 seem to fall into the latter category. Could you please=20
> check whether that was the intention with all those requirements?
>=20
> A few requirements relate to the security and privacy related=20
> properties of the SRC-SRS interface (e.g., requirements 24 and 29).=20
> However, the draft does not discuss how the security and privacy of=20
> that interface relate to the security and privacy level used for the=20
> CS being recorded.
> For example, can the confidentiality level of the media going from the=20
> SRC and the SRS be lower than that of the media flowing between the=20
> actual participants of the CS? If you decide there should not be a=20
> requirement on this area, you need to at least discuss this issue=20
> (probably in Sections 6 or 7).
>=20
> Once you address these comments, I will request the IETF-wide last=20
> call for this draft.
>=20
> Thanks,
>=20
> Gonzalo
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20

From krehor@cisco.com  Mon Mar 28 00:41:08 2011
Return-Path: <krehor@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B7AE3A68AA for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 00:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.998
X-Spam-Level: 
X-Spam-Status: No, score=-8.998 tagged_above=-999 required=5 tests=[AWL=1.601,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z6BRnrWiwfcy for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 00:41:07 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 3C9BB3A681D for <siprec@ietf.org>; Mon, 28 Mar 2011 00:41:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=krehor@cisco.com; l=4570; q=dns/txt; s=iport; t=1301298164; x=1302507764; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=svZJixXbBwt/bGN74xxoKBbcYU0UhWxjlWC7DyGfld8=; b=HsLTWnMxx3ZTaCgJGZXxjD5fdLh2eDtQvbQVUGCviUabXi0v7gjznhMc g/5APr0lVygXTbv39vGPB5S/aVH+s191NFJYZTApSo/UDPoR+sV8OFaDw bE/fkap2tPo8xvmMZbrRHA839nGmyyxhdeuLWHsSEwcjM6ofHAAj3j5JI c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwAAOk6kE2rRDoH/2dsb2JhbACYDY09d6VGmxyFaQSFOosX
X-IronPort-AV: E=Sophos;i="4.63,253,1299456000"; d="scan'208";a="283856777"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-3.cisco.com with ESMTP; 28 Mar 2011 07:42:28 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2S7gSBI023441; Mon, 28 Mar 2011 07:42:28 GMT
Received: from xmb-sjc-22e.amer.cisco.com ([128.107.191.115]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 00:42:27 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Mar 2011 00:42:23 -0700
Message-ID: <7744FE52C78D944587F03773EB45146109CD645D@xmb-sjc-22e.amer.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB46695E@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIAACWzYeAAL84ccAAAvaAQ
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB46695E@TLVMBX01.nice.com>
From: "Ken Rehor (krehor)" <krehor@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 28 Mar 2011 07:42:27.0794 (UTC) FILETIME=[AFB49B20:01CBED1B]
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 07:41:08 -0000

+1=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Monday, March 28, 2011 12:39 AM
> To: Elwell, John; Gonzalo Camarillo; siprec@ietf.org; Ken Rehor
(krehor)
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> I want to propose following additional text for the Security
Considerations
> section (after the last paragraph)
>=20
> "Communication Sessions and Recording Sessions will require different
> security levels both for signaling and media, depending on deployment
> configurations. For some environments, for example, SRS and SRC will
be
> collocated in a secure network region and will not require same
protection
> level as CS over public network. For other environments, SRS can be
located
> in a public cloud and RS will require higher protection level then CS.
> Because of these reasons, there is not direct relation between
security level
> of Communication Sessions and Recording Sessions"
>=20
> Leon
>=20
>=20
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Sunday, March 27, 2011 10:33 AM
> To: Leon Portman; Gonzalo Camarillo; siprec@ietf.org; Ken Rehor
(krehor)
> (krehor@cisco.com)
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Yes, indeed we had the discussion and came up with reasons you can't
tie the
> two together. So as Gonzalo suggests, some of that discussion needs to
be
> captured in the Security Considerations section.
>=20
> John
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 26 March 2011 14:37
> > To: Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor)
> > (krehor@cisco.com); Elwell, John
> > Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
> >
> > Hi,
> >
> > I want to touch security requirement: about security level of RS vs
> > security level of CS. We had a long mailing list discussion (below)
> > and it was decided not to have it, because it is more implementation
> > details
> >
> > http://www.ietf.org/mail-archive/web/siprec/current/msg01164.html
> >
> > Regards
> >
> > Leon
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> > Sent: Wednesday, March 23, 2011 1:23 PM
> > To: siprec@ietf.org
> > Subject: [siprec] AD review: draft-ietf-siprec-req-08
> >
> > Hi,
> >
> > the SIPREC WG requested the publication of the following draft a few
> > days ago. Please, find below my AD review.
> >
> > https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> >
> > Given that the draft contains both requirements and use cases, you
may
> > want to edit the title so that it reads "Use Cases and Requirements
> > for ..."
> >
> > Typically, Section 1 contains the Introduction and Section 2 the
> > terminology. You may want to swap both sections.
> >
> > Most of the requirements are phrased so that they describe
> > capabilities that need to be supported by the system (e.g., the
> > mechanism MUST provide the SRS with the means to ...) but that do
not
> > need to be necessarily used (e.g., a particular use case may not
make
> > use of that functionality). However, some requirements are phrased
so
> > that the functionality needs to be used (e.g., the mechanism MUST
> > provide the SRS the wall clock time ...). Requirements 12, 22, 23,
27,
> > 28, and 29 seem to fall into the latter category. Could you please
> > check whether that was the intention with all those requirements?
> >
> > A few requirements relate to the security and privacy related
> > properties of the SRC-SRS interface (e.g., requirements 24 and 29).
> > However, the draft does not discuss how the security and privacy of
> > that interface relate to the security and privacy level used for the
> > CS being recorded.
> > For example, can the confidentiality level of the media going from
the
> > SRC and the SRS be lower than that of the media flowing between the
> > actual participants of the CS? If you decide there should not be a
> > requirement on this area, you need to at least discuss this issue
> > (probably in Sections 6 or 7).
> >
> > Once you address these comments, I will request the IETF-wide last
> > call for this draft.
> >
> > Thanks,
> >
> > Gonzalo
> >
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >

From eckelcu@cisco.com  Mon Mar 28 01:07:32 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C8AA3A6912 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.569
X-Spam-Level: 
X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aOKa8+lcTfrs for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:07:31 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id F274A3A68E4 for <siprec@ietf.org>; Mon, 28 Mar 2011 01:07:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=5280; q=dns/txt; s=iport; t=1301299748; x=1302509348; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=P40x+/QMTl4x+L8EGgGhc2ceE4+tu7xoOHIGXWG2ilU=; b=CD3LMP+7l2ZC37jBUFcdX3gcn3ZE587GfIaHDlsar+XUbiC0gwMlGLHx Dvik1DajVWV2oI839miA2B9noYw/XY5h/uKyiowAPzNh6rjDU21PBEgB+ r7TvFM4uQELUMmUBwGJU9+jlhql1g73PjRgEpBxfT2CxWuiXrsBZNgRJF M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwAAAFBkE2rRDoI/2dsb2JhbACYDY09d6VFmyaFaQSFOosX
X-IronPort-AV: E=Sophos;i="4.63,253,1299456000"; d="scan'208";a="283869552"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 28 Mar 2011 08:09:08 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2S898Kn003482; Mon, 28 Mar 2011 08:09:08 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 01:09:08 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Mar 2011 01:09:04 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E381E8@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <7744FE52C78D944587F03773EB45146109CD645D@xmb-sjc-22e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIAACWzYeAAL84ccAAAvaAQAADwVTA=
References: <4D89D801.8040308@ericsson.com><07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB46695E@TLVMBX01.nice.com> <7744FE52C78D944587F03773EB45146109CD645D@xmb-sjc-22e.amer.cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Ken Rehor (krehor)" <krehor@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 28 Mar 2011 08:09:08.0097 (UTC) FILETIME=[698F7710:01CBED1F]
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 08:07:32 -0000

Works for me as well.

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Ken Rehor (krehor)
> Sent: Monday, March 28, 2011 9:42 AM
> To: Leon Portman; Elwell, John; Gonzalo Camarillo; siprec@ietf.org
> Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> +1
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Monday, March 28, 2011 12:39 AM
> > To: Elwell, John; Gonzalo Camarillo; siprec@ietf.org; Ken Rehor
> (krehor)
> > Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
> >
> > I want to propose following additional text for the Security
> Considerations
> > section (after the last paragraph)
> >
> > "Communication Sessions and Recording Sessions will require
different
> > security levels both for signaling and media, depending on
deployment
> > configurations. For some environments, for example, SRS and SRC will
> be
> > collocated in a secure network region and will not require same
> protection
> > level as CS over public network. For other environments, SRS can be
> located
> > in a public cloud and RS will require higher protection level then
CS.
> > Because of these reasons, there is not direct relation between
> security level
> > of Communication Sessions and Recording Sessions"
> >
> > Leon
> >
> >
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Sunday, March 27, 2011 10:33 AM
> > To: Leon Portman; Gonzalo Camarillo; siprec@ietf.org; Ken Rehor
> (krehor)
> > (krehor@cisco.com)
> > Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
> >
> > Yes, indeed we had the discussion and came up with reasons you can't
> tie the
> > two together. So as Gonzalo suggests, some of that discussion needs
to
> be
> > captured in the Security Considerations section.
> >
> > John
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 26 March 2011 14:37
> > > To: Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor)
> > > (krehor@cisco.com); Elwell, John
> > > Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
> > >
> > > Hi,
> > >
> > > I want to touch security requirement: about security level of RS
vs
> > > security level of CS. We had a long mailing list discussion
(below)
> > > and it was decided not to have it, because it is more
implementation
> > > details
> > >
> > > http://www.ietf.org/mail-archive/web/siprec/current/msg01164.html
> > >
> > > Regards
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> > > Sent: Wednesday, March 23, 2011 1:23 PM
> > > To: siprec@ietf.org
> > > Subject: [siprec] AD review: draft-ietf-siprec-req-08
> > >
> > > Hi,
> > >
> > > the SIPREC WG requested the publication of the following draft a
few
> > > days ago. Please, find below my AD review.
> > >
> > > https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> > >
> > > Given that the draft contains both requirements and use cases, you
> may
> > > want to edit the title so that it reads "Use Cases and
Requirements
> > > for ..."
> > >
> > > Typically, Section 1 contains the Introduction and Section 2 the
> > > terminology. You may want to swap both sections.
> > >
> > > Most of the requirements are phrased so that they describe
> > > capabilities that need to be supported by the system (e.g., the
> > > mechanism MUST provide the SRS with the means to ...) but that do
> not
> > > need to be necessarily used (e.g., a particular use case may not
> make
> > > use of that functionality). However, some requirements are phrased
> so
> > > that the functionality needs to be used (e.g., the mechanism MUST
> > > provide the SRS the wall clock time ...). Requirements 12, 22, 23,
> 27,
> > > 28, and 29 seem to fall into the latter category. Could you please
> > > check whether that was the intention with all those requirements?
> > >
> > > A few requirements relate to the security and privacy related
> > > properties of the SRC-SRS interface (e.g., requirements 24 and
29).
> > > However, the draft does not discuss how the security and privacy
of
> > > that interface relate to the security and privacy level used for
the
> > > CS being recorded.
> > > For example, can the confidentiality level of the media going from
> the
> > > SRC and the SRS be lower than that of the media flowing between
the
> > > actual participants of the CS? If you decide there should not be a
> > > requirement on this area, you need to at least discuss this issue
> > > (probably in Sections 6 or 7).
> > >
> > > Once you address these comments, I will request the IETF-wide last
> > > call for this draft.
> > >
> > > Thanks,
> > >
> > > Gonzalo
> > >
> > > _______________________________________________
> > > 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

From andrew.hutton@siemens-enterprise.com  Mon Mar 28 01:10:56 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0CE23A690E for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.213
X-Spam-Level: 
X-Spam-Status: No, score=-2.213 tagged_above=-999 required=5 tests=[AWL=0.386,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YfFV50srysZO for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:10:52 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 45DA93A6912 for <siprec@ietf.org>; Mon, 28 Mar 2011 01:10:49 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3892858; Mon, 28 Mar 2011 10:12:26 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 0EE101EB82B4; Mon, 28 Mar 2011 10:12:25 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 28 Mar 2011 10:12:25 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 28 Mar 2011 10:12:24 +0200
Thread-Topic: review comments on draft-ietf-siprec-architecture-01
Thread-Index: Acvr4t/8/sTKgbbNQSmx5Q79X0rBbgBNr1Mw
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED94E@MCHP058A.global-ad.net>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86E9F@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86E9F@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] review comments on draft-ietf-siprec-architecture-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 08:10:56 -0000

Hi Charles,

Thanks for the comments, see below.

Regards
Andy=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel (eckelcu)
> Sent: 26 March 2011 18:23
> To: siprec@ietf.org
> Subject: [siprec] review comments on draft-ietf-siprec-architecture-01
>=20
> I started my review of the SIPREC drafts with the=20
> architecture document.
> I have some nits and some concerns.
> Let me state the concerns first.
>=20
> Section 4.2 reads, "the Session Recording Client must decrypt=20
> any media
> received on the Communication Session and, if required, re-encrypt the
> media using a separate SRTP key for the Recording Session."=20
> Why must? I
> imagine it could be done in some cases, but I do not see why it is a
> must.
>=20

[AndyH] - This will be removed in the next update it was there due to some =
old requirements which have now been removed.


> Section 4.2.1 reads, "Indicate support for the recording=20
> metadata event
> package." I am not sure this is needed and do not think it should be
> stated here.
>=20

[AndyH] This is also tentatively removed in the next draft due to comments =
from Partha. It is not an architectural issue anyway but my personal opinio=
n is that some indication from the SRC as to whether it supports sending me=
tadata would be useful.


> Section 4.3.1, no sure why Dialog state of the Communication=20
> Session is
> required.
>

[AndyH] - This is currently under debate I am also tending towards thinking=
 it is not needed.
=20
> Section 4.3.2, regarding the OPEN ISSUE, I think we decided on XML as
> message body in re-INVITE or UPDATE.
>=20

[AndyH] - Agreed removed from next version.


> Section 4.4 reads, "If the Session Recording Client is aware that the
> remote UA is a recording aware UA then it MUST notify the UA=20
> using a SIP
> based mechanism." Why MUST? It seems "should" is more appropriate as
> other mechanisms may be used depending on the use case. Also, it seems
> there should not be any normative language in this draft.
>=20

[AndyH] - The next version will only state that it is the SRC's responsible=
 for the notifications and not mandate the mechanism. All normative languag=
e will also be removed. Hope this will be ok.

> Section 6 reads, "SRTP is used for securing the Replicated Media." I
> think other mechanisms should be allowed as well.

[AndyH] - What do you suggest we should say here? I guess anything that can=
 be negotiated via SIP/SDP is within scope so we could say something more g=
eneric.

>=20
> Nits
>=20
> Section 4.2
> Replace "Recording Session is a completely independent" with=20
> "Recording
> Session is completely independent".

[AndyH] - Done.

>=20
> Cheers,
> Charles
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From eckelcu@cisco.com  Mon Mar 28 01:18:45 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D7C73A68EE for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.57
X-Spam-Level: 
X-Spam-Status: No, score=-10.57 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5zuWUI3OCQz5 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:18:43 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 56B773A68A6 for <siprec@ietf.org>; Mon, 28 Mar 2011 01:18:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=4119; q=dns/txt; s=iport; t=1301300421; x=1302510021; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=WZrQTWSmULVa95CsVXQrDPjb7LfKwdGmyGQ2eaPhbLs=; b=EsdakduxVvDh2UB9V3p9QEqqdYwxPdkBFwE3rT/yCCqaW+l7DVNHrFBA 80dDNYS7dHZNOD/0k52IwaMIfDoshhqHJ8WoISPerecDcbvQWRPIBAqDl 5vW18GAIjswbfhxH4LmYKIO/ItTHU3h2AaGEJ9EX1MncuLuDwXhlco9TM o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwAAJtDkE2rRDoI/2dsb2JhbACYDo09d4hrnGmbJoVpBIU6ixc
X-IronPort-AV: E=Sophos;i="4.63,253,1299456000"; d="scan'208";a="419270052"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-1.cisco.com with ESMTP; 28 Mar 2011 08:19:53 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2S8JrAh011382; Mon, 28 Mar 2011 08:19:53 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 01:19:53 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Mar 2011 01:19:51 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E381EB@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED94E@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: review comments on draft-ietf-siprec-architecture-01
Thread-Index: Acvr4t/8/sTKgbbNQSmx5Q79X0rBbgBNr1MwAAG1GIA=
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86E9F@xmb-sjc-234.amer.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED94E@MCHP058A.global-ad.net>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 28 Mar 2011 08:19:53.0437 (UTC) FILETIME=[EA3688D0:01CBED20]
Subject: Re: [siprec] review comments on draft-ietf-siprec-architecture-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 08:18:45 -0000

Hi Andy,

Thank you for your response. It seems we are in agreement on all points.
Regarding your question:

> Section 6 reads, "SRTP is used for securing the Replicated Media." I
> think other mechanisms should be allowed as well.

[AndyH] - What do you suggest we should say here? I guess anything that
can be negotiated via SIP/SDP is within scope so we could say something
more generic.

I think we do not need to mention anything specific here as I do not
think SIPREC has any special requirements. The requirement to support
separate security mechanism for CS than RS in some cases is already
covered in another thread, and I agree with what was proposed there.

Cheers,
Charles

> -----Original Message-----
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> Sent: Monday, March 28, 2011 10:12 AM
> To: Charles Eckel (eckelcu); siprec@ietf.org
> Subject: RE: review comments on draft-ietf-siprec-architecture-01
>=20
> Hi Charles,
>=20
> Thanks for the comments, see below.
>=20
> Regards
> Andy
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel
(eckelcu)
> > Sent: 26 March 2011 18:23
> > To: siprec@ietf.org
> > Subject: [siprec] review comments on
draft-ietf-siprec-architecture-01
> >
> > I started my review of the SIPREC drafts with the
> > architecture document.
> > I have some nits and some concerns.
> > Let me state the concerns first.
> >
> > Section 4.2 reads, "the Session Recording Client must decrypt
> > any media
> > received on the Communication Session and, if required, re-encrypt
the
> > media using a separate SRTP key for the Recording Session."
> > Why must? I
> > imagine it could be done in some cases, but I do not see why it is a
> > must.
> >
>=20
> [AndyH] - This will be removed in the next update it was there due to
some old requirements which have
> now been removed.
>=20
>=20
> > Section 4.2.1 reads, "Indicate support for the recording
> > metadata event
> > package." I am not sure this is needed and do not think it should be
> > stated here.
> >
>=20
> [AndyH] This is also tentatively removed in the next draft due to
comments from Partha. It is not an
> architectural issue anyway but my personal opinion is that some
indication from the SRC as to whether
> it supports sending metadata would be useful.
>=20
>=20
> > Section 4.3.1, no sure why Dialog state of the Communication
> > Session is
> > required.
> >
>=20
> [AndyH] - This is currently under debate I am also tending towards
thinking it is not needed.
>=20
> > Section 4.3.2, regarding the OPEN ISSUE, I think we decided on XML
as
> > message body in re-INVITE or UPDATE.
> >
>=20
> [AndyH] - Agreed removed from next version.
>=20
>=20
> > Section 4.4 reads, "If the Session Recording Client is aware that
the
> > remote UA is a recording aware UA then it MUST notify the UA
> > using a SIP
> > based mechanism." Why MUST? It seems "should" is more appropriate as
> > other mechanisms may be used depending on the use case. Also, it
seems
> > there should not be any normative language in this draft.
> >
>=20
> [AndyH] - The next version will only state that it is the SRC's
responsible for the notifications and
> not mandate the mechanism. All normative language will also be
removed. Hope this will be ok.
>=20
> > Section 6 reads, "SRTP is used for securing the Replicated Media." I
> > think other mechanisms should be allowed as well.
>=20
> [AndyH] - What do you suggest we should say here? I guess anything
that can be negotiated via SIP/SDP
> is within scope so we could say something more generic.
>=20
> >
> > Nits
> >
> > Section 4.2
> > Replace "Recording Session is a completely independent" with
> > "Recording
> > Session is completely independent".
>=20
> [AndyH] - Done.
>=20
> >
> > Cheers,
> > Charles
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >

From gonzalo.camarillo@ericsson.com  Mon Mar 28 01:20:28 2011
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EABA3A6910 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.601
X-Spam-Level: 
X-Spam-Status: No, score=-106.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bTNqfvgzaRMR for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:20:26 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id F345A3A683C for <siprec@ietf.org>; Mon, 28 Mar 2011 01:20:25 -0700 (PDT)
X-AuditID: c1b4fb39-b7c6dae0000023f2-69-4d90452a46ef
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id FF.05.09202.A25409D4; Mon, 28 Mar 2011 10:22:02 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Mon, 28 Mar 2011 10:22:02 +0200
Received: from [131.160.126.174] (rvi2-126-174.lmf.ericsson.se [131.160.126.174])	by mail.lmf.ericsson.se (Postfix) with ESMTP id A355A253A; Mon, 28 Mar 2011 11:22:01 +0300 (EEST)
Message-ID: <4D904527.4020801@ericsson.com>
Date: Mon, 28 Mar 2011 09:21:59 +0100
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA1@xmb-sjc-234.amer.cisco.com> <A444A0F8084434499206E78C106220CA0875AF2B2B@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF2B2B@MCHP058A.global-ad.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] review comments in draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 08:20:28 -0000

Hi,

yes, improving the document in this way is of course OK.

Thanks,

Gonzalo

On 27/03/2011 9:01 PM, Elwell, John wrote:
> (Question for Gonzalo below) 
> 
>> -----Original Message-----
>> From: siprec-bounces@ietf.org 
>> [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel (eckelcu)
>> Sent: 26 March 2011 18:29
>> To: siprec@ietf.org
>> Subject: [siprec] review comments in draft-ietf-siprec-req-08
>>
>> Section 3, it would be better to refer to arch draft for definitions
>> rather than repeating here and in other drafts.
> [JRE] Since the requirements draft is first, I would say keep the definitions in the requirements draft and remove them from the architecture draft.
> 
>>
>> Section 5, Req-024 conflicts with architecture draft. I think 
>> Req-024 is
>> correct and architecture document needs to be updated accordingly.
> [JRE] Yes, the architecture document should be aligned.
> 
>>
>> Section 6, change "although any user can terminate a CS" to "although
>> any user can terminate its participation in a CS."
> [JRE] This sounds like a reasonable change, but don't forget that the document has already left the WG and at present we are just addressing comments from the AD. However, I don't think this is controversial, so if the AD agrees. Gonzalo?
> 
> John
> 
> 
>>
>> Cheers,
>> Charles
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec


From gonzalo.camarillo@ericsson.com  Mon Mar 28 01:22:38 2011
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF2503A68EE for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.601
X-Spam-Level: 
X-Spam-Status: No, score=-106.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hztQ6jUiXF0C for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:22:36 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id E3EE13A683C for <siprec@ietf.org>; Mon, 28 Mar 2011 01:22:35 -0700 (PDT)
X-AuditID: c1b4fb39-b7c6dae0000023f2-0a-4d9045ace845
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id DF.85.09202.CA5409D4; Mon, 28 Mar 2011 10:24:12 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Mon, 28 Mar 2011 10:24:12 +0200
Received: from [131.160.126.174] (rvi2-126-174.lmf.ericsson.se [131.160.126.174])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 6DD40253A; Mon, 28 Mar 2011 11:24:11 +0300 (EEST)
Message-ID: <4D9045A9.8060202@ericsson.com>
Date: Mon, 28 Mar 2011 09:24:09 +0100
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Leon Portman <Leon.Portman@nice.com>
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB46695E@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB46695E@TLVMBX01.nice.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 08:22:38 -0000

Hi,

this text is OK.

Thanks,

Gonzalo

On 28/03/2011 8:39 AM, Leon Portman wrote:
> I want to propose following additional text for the Security Considerations section (after the last paragraph)
> 
> "Communication Sessions and Recording Sessions will require different security levels both for signaling and media, depending on deployment configurations. For some environments, for example, SRS and SRC will be collocated in a secure network region and will not require same protection level as CS over public network. For other environments, SRS can be located in a public cloud and RS will require higher protection level then CS. Because of these reasons, there is not direct relation between security level of Communication Sessions and Recording Sessions"
> 
> Leon
> 
> 
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com] 
> Sent: Sunday, March 27, 2011 10:33 AM
> To: Leon Portman; Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor) (krehor@cisco.com)
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
> 
> Yes, indeed we had the discussion and came up with reasons you can't tie the two together. So as Gonzalo suggests, some of that discussion needs to be captured in the Security Considerations section.
> 
> John
> 
>> -----Original Message-----
>> From: Leon Portman [mailto:Leon.Portman@nice.com]
>> Sent: 26 March 2011 14:37
>> To: Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor) 
>> (krehor@cisco.com); Elwell, John
>> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>>
>> Hi,
>>
>> I want to touch security requirement: about security level of RS vs 
>> security level of CS. We had a long mailing list discussion (below) 
>> and it was decided not to have it, because it is more implementation 
>> details
>>
>> http://www.ietf.org/mail-archive/web/siprec/current/msg01164.html
>>
>> Regards
>>
>> Leon
>>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org
>> [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
>> Sent: Wednesday, March 23, 2011 1:23 PM
>> To: siprec@ietf.org
>> Subject: [siprec] AD review: draft-ietf-siprec-req-08
>>
>> Hi,
>>
>> the SIPREC WG requested the publication of the following draft a few 
>> days ago. Please, find below my AD review.
>>
>> https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
>>
>> Given that the draft contains both requirements and use cases, you may 
>> want to edit the title so that it reads "Use Cases and Requirements 
>> for ..."
>>
>> Typically, Section 1 contains the Introduction and Section 2 the 
>> terminology. You may want to swap both sections.
>>
>> Most of the requirements are phrased so that they describe 
>> capabilities that need to be supported by the system (e.g., the 
>> mechanism MUST provide the SRS with the means to ...) but that do not 
>> need to be necessarily used (e.g., a particular use case may not make 
>> use of that functionality). However, some requirements are phrased so 
>> that the functionality needs to be used (e.g., the mechanism MUST 
>> provide the SRS the wall clock time ...). Requirements 12, 22, 23, 27, 
>> 28, and 29 seem to fall into the latter category. Could you please 
>> check whether that was the intention with all those requirements?
>>
>> A few requirements relate to the security and privacy related 
>> properties of the SRC-SRS interface (e.g., requirements 24 and 29). 
>> However, the draft does not discuss how the security and privacy of 
>> that interface relate to the security and privacy level used for the 
>> CS being recorded.
>> For example, can the confidentiality level of the media going from the 
>> SRC and the SRS be lower than that of the media flowing between the 
>> actual participants of the CS? If you decide there should not be a 
>> requirement on this area, you need to at least discuss this issue 
>> (probably in Sections 6 or 7).
>>
>> Once you address these comments, I will request the IETF-wide last 
>> call for this draft.
>>
>> Thanks,
>>
>> Gonzalo
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>>


From Leon.Portman@nice.com  Mon Mar 28 01:37:19 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D7F03A6893 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.409
X-Spam-Level: 
X-Spam-Status: No, score=-2.409 tagged_above=-999 required=5 tests=[AWL=0.190,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mX-fr7uYkJxR for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:37:18 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id EDD143A6929 for <siprec@ietf.org>; Mon, 28 Mar 2011 01:37:15 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Mon, 28 Mar 2011 10:38:52 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "siprec@ietf.org" <siprec@ietf.org>, "Ken Rehor (krehor) (krehor@cisco.com)" <krehor@cisco.com>
Date: Mon, 28 Mar 2011 10:38:49 +0200
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIAACWzYeAAMoBucA==
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB4669E2@TLVMBX01.nice.com>
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 08:37:19 -0000

> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> Sent: Wednesday, March 23, 2011 1:23 PM
> To: siprec@ietf.org
> Subject: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Hi,
>=20
> the SIPREC WG requested the publication of the following draft a few=20
> days ago. Please, find below my AD review.
>=20
> https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
>=20
> Given that the draft contains both requirements and use cases, you may=20
> want to edit the title so that it reads "Use Cases and Requirements=20
> for ..."
>=20
> Typically, Section 1 contains the Introduction and Section 2 the=20
> terminology. You may want to swap both sections.
>=20
> Most of the requirements are phrased so that they describe=20
> capabilities that need to be supported by the system (e.g., the=20
> mechanism MUST provide the SRS with the means to ...) but that do not=20
> need to be necessarily used (e.g., a particular use case may not make=20
> use of that functionality). However, some requirements are phrased so=20
> that the functionality needs to be used (e.g., the mechanism MUST=20
> provide the SRS the wall clock time ...). Requirements 12, 22, 23, 27,=20
> 28, and 29 seem to fall into the latter category. Could you please=20
> check whether that was the intention with all those requirements?
>=20
> A few requirements relate to the security and privacy related=20
> properties of the SRC-SRS interface (e.g., requirements 24 and 29).=20
> However, the draft does not discuss how the security and privacy of=20
> that interface relate to the security and privacy level used for the=20
> CS being recorded.
> For example, can the confidentiality level of the media going from the=20
> SRC and the SRS be lower than that of the media flowing between the=20
> actual participants of the CS? If you decide there should not be a=20
> requirement on this area, you need to at least discuss this issue=20
> (probably in Sections 6 or 7).
>=20
> Once you address these comments, I will request the IETF-wide last=20
> call for this draft.
>=20
> Thanks,
>=20
> Gonzalo
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20

From partr@cisco.com  Mon Mar 28 01:40:47 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5743C3A6856 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:40:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.723
X-Spam-Level: 
X-Spam-Status: No, score=-9.723 tagged_above=-999 required=5 tests=[AWL=0.276,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GoV+Um8dycLO for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:40:46 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 5E5003A684B for <siprec@ietf.org>; Mon, 28 Mar 2011 01:40:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=6902; q=dns/txt; s=iport; t=1301301743; x=1302511343; h=mime-version:subject:date:message-id:in-reply-to: references:from:to; bh=25stvFVf+QxQmS523F31LsNEMiUBLrVOAbAZLaUeCIw=; b=T/0efuPmDXcHa7KbltK2kHo7i8f4mrH0IS/7rY8NTIQn6R/uwLpMk9wj 1LL/SVrCsnyUeQ6JY/QZEsdd1UCY9AC/wkirF2RpVEPqbVKdYjEqSd/Fw lFmjyyu/9cawgKXjTnxEXxHYAvKNCj1pZg/r9ooXvUKT2JrO73G1ooO+o w=;
X-Files: RTP Mux example.txt : 1090
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AucAAIZJkE2Q/khMgWdsb2JhbACYDY09FAEBFiYliGudMJsugnyCbQSFOIsZ
X-IronPort-AV: E=Sophos;i="4.63,253,1299456000";  d="txt'?scan'208";a="23411851"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 28 Mar 2011 08:42:21 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2S8ftVN032157 for <siprec@ietf.org>; Mon, 28 Mar 2011 08:42:21 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 14:12:11 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CBED24.07BCC087"
Date: Mon, 28 Mar 2011 14:12:08 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: AcvlaWIIK70D67ErTdeQ754hs4iSUgAErWSwAejioLA=
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 28 Mar 2011 08:42:11.0675 (UTC) FILETIME=[07DD72B0:01CBED24]
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 08:40:47 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBED24.07BCC087
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Charles,

IMO, the current metadata model helps to address RTP MUX streams as
well. In terms of model, multiple participants (P1, P2, P3) metadata
block points to the single stream (S1) and stream block contains SSRC &
CSRC information. IOW, SIPREC model abstract RTP MUX stream within media
stream block.  Please let me know in case you feel that model does not
address it.

In case of metadata format, multiple "participant" elements have send
element with single stream element. The stream element has a label
attribute which points to the m-line which contains "ssrc" attribute
with CNAME parameter. I attached the example for your reference and The
example is the one of the way to represent RTP-MUX stream in the
metadata format. Please let me know the issues with this format and
example.

I agree with Paul and you that we need to understand how RTP mux stream
will be standardized but IMO, it is not the limiting factor for SIPREC
as of now.

Thanks
Partha

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Charles Eckel (eckelcu)
Sent: Friday, March 18, 2011 8:40 PM
To: Paul Kyzivat (pkyzivat); siprec@ietf.org
Subject: Re: [siprec] Multiplexing different participants' streams on
thesame port

I agree with the comment regarding CLUE, so let me take a simpler
example, and audio mixer. This mixer may mix the audio from multiple
participants.

Participant 1 (P1)
Participant 2 (P2)
Participant 3 (P3)

P1 sends audio stream with SSRC-P1
P2 sends audio stream with SSCR-P2
P2 sends audio stream with SSCR-P3

MixerA(Ma)

Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
The SRC sends this stream to the SRS for recording. I suspect it might
change the SSRC to be SSRC-SRC but maintain the CSRC information
identifying P1/P2/P3.
I expect this would be modeled as a single stream with 3 participants
P1, P2, P3. The mapping of P1 to SSRC-P1 is captured in the RTCP data
sent by SRC to SRS. In this case, there is no need to anything in the
metadata.
However, if the CSRCs are not propagated all the way to the SRS, then
perhaps participant info would need to be communicated via the metadata.

Note, I do not pretend to have this all figured out; rather, I am
putting out some ideas to see if this gels with what others have in
mind.

Cheers,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Paul Kyzivat (pkyzivat)
> Sent: Friday, March 18, 2011 5:38 AM
> To: siprec@ietf.org
> Subject: Re: [siprec] Multiplexing different participants' streams on
the same port
>=20
> I don't know if this is a good idea or not. But if we want to consider

> it, then we should probably enter into some discussion with CLUE, to
see
> if there is any commonality.
>=20
> Over in CLUE, this mixing of multiple streams over one RTP session has

> been brought up because it is a technique used in existing proprietary

> products. But the CLUE wg isn't yet to a point where it is ready to=20
> decide if this will be a requirement. And the AVT people have strong=20
> opinions on what is/isn't appropriate.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/18/2011 4:11 AM, Elwell, John wrote:
> > Something Charles mentioned in another thread triggered me to raise
this.
> >
> > We consider different participants in the CS as potentially
producing separate media streams that
> the SRC sends to the SRS, where the SRC can send them mixed or
unmixed.
> >
> > When sending them unmixed, up till now I think we have considered
sending them to separate ports on
> the SRS and identifying them as separate m=3D lines in the SDP. =
Another
possibility might be to
> multiplex the different streams on the same port and identify them by
different SSRC values. I am not
> sure whether this would be a correct use of SSRC, and I suspect we
would need to check with AVTCORE.
> Recent discussions in other contexts (telepresence, RTC-Web) have also
drawn my attention to such
> possibilities. See also
https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
> >
> > Of course, it would mean that we would have to rethink how we
reference the different streams from
> metadata.
> >
> > I am not necessarily proposing such a change - I just want to make
sure we have given it due
> consideration.
> >
> > John (as individual)
> >
> >
> > _______________________________________________
> > 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

------_=_NextPart_001_01CBED24.07BCC087
Content-Type: text/plain;
	name="RTP Mux example.txt"
Content-Transfer-Encoding: base64
Content-Description: RTP Mux example.txt
Content-Disposition: attachment;
	filename="RTP Mux example.txt"

ICAgICA8cGFydGljaXBhbnQNCiAgICAgICAgICAgaWQ9InVybjp1dWlkOmIyYjdjMTEyLTU5ODIt
NDY5ZC05MDA3LTZkZGJlY2NhNjRkMyINCiAgICAgICAgICAgc2Vzc2lvbj0idXJuOnV1aWQ6ODU1
YTVkZWQtODQyMC00NTZkLWE3MGYtNmRhMWVlYWViNDI1Ij4NCiAgICAgICAgICAgPGFvcj5zaXA6
cGFydGhhQHJjMS5jaXNjby5jb208L2Fvcj4NCiAgICAgICAgICAgPHNlbmQ+DQogICAgICAgICAg
ICAgICA8aWQ+dXJuOnV1aWQ6OGI1M2YzZGUtZGEzOS00ODQ2LTkzYzctZWU1ZTVmOGY2ZjBiPC9p
ZD4NCiAgICAgICAgICAgPC9zZW5kPg0KICAgICAgPC9wYXJ0aWNpcGFudD4NCiAgICAgIDxwYXJ0
aWNpcGFudA0KICAgICAgICAgICAgaWQ9InVybjp1dWlkOmNkMjdjZmExLTJiZGQtNDgzMC1hNjUz
LTcwMzc0ZDEwZjEwMyINCiAgICAgICAgICAgIHNlc3Npb249InVybjp1dWlkOjg1NWE1ZGVkLTg0
MjAtNDU2ZC1hNzBmLTZkYTFlZWFlYjQyNSI+DQogICAgICAgICAgICA8YW9yPnNpcDpwYXVsQHJj
MS5jaXNjby5jb208L2Fvcj4NCiAgICAgICAgICAgIDxzZW5kPg0KICAgICAgICAgICAgICAgPGlk
PnVybjp1dWlkOjhiNTNmM2RlLWRhMzktNDg0Ni05M2M3LWVlNWU1ZjhmNmYwYjwvaWQ+DQogICAg
ICAgICAgIDwvc2VuZD4NCiAgICAgIDwvcGFydGljaXBhbnQ+DQogICAgICA8c3RyZWFtIGlkPSJ1
cm46dXVpZDo4YjUzZjNkZS1kYTM5LTQ4NDYtOTNjNy1lZTVlNWY4ZjZmMGIiDQogICAgICAgICAg
ICBzZXNzaW9uPSJ1cm46dXVpZDo4NTVhNWRlZC04NDIwLTQ1NmQtYTcwZi02ZGExZWVhZWI0MjUi
Pg0KICAgICAgICAgICAgPHN0YXJ0LXRpbWU+MjAxMC0xMi0xNlQyMzo0MTowN1o8L3N0YXJ0LXRp
bWU+DQogICAgICAgICAgICA8bGFiZWw+OTc8L2xhYmVsPg0KICAgICAgPC9zdHJlYW0+DQoNClNE
UCBwYXJ0Og0KDQogICBtPWF1ZGlvIDUxMzcyIFJUUC9BVlAgMA0KICAgYT1ydHBtYXA6MCBQQ01V
LzgwMDANCiAgIGE9c3NyYzoxMjM0NSBjbmFtZTpwYXJ0aGFAcmMxLmNpc2NvLmNvbQ0KICAgYT1z
c3JjOjY3ODkwIGNuYW1lOnBhdWxAcmMxLmNpc2NvLmNvbQ0KICAgYT1sYWJlbDo5Nw0KICAgYT1z
ZW5kb25seQ==

------_=_NextPart_001_01CBED24.07BCC087--

From Leon.Portman@nice.com  Mon Mar 28 01:41:14 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15EF33A6856 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.414
X-Spam-Level: 
X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5 tests=[AWL=0.185,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xczh+GuREpux for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 01:41:13 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id C04C53A684B for <siprec@ietf.org>; Mon, 28 Mar 2011 01:41:12 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Mon, 28 Mar 2011 10:42:49 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "siprec@ietf.org" <siprec@ietf.org>, "Ken Rehor (krehor) (krehor@cisco.com)" <krehor@cisco.com>
Date: Mon, 28 Mar 2011 10:42:47 +0200
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIAACWzYeAAMoBucAAAC7XA
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB4669F4@TLVMBX01.nice.com>
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 08:41:14 -0000

Hi,

Following AD comments, I am proposing to indicate that following requiremen=
ts are mandatory to implement, in contrast for other requirements that are =
mandatory for the protocol to support but optional for implementation depen=
ding use cases:

1. REQ-001 - implement SIP based protocol
2. REQ-012  - metadata reporting support=20
3. REQ-013 - map between participant and  media=20
4. REQ-022 - wall clock reporting for media synchronization
5. REQ-023 - wall clock, assuming pause/resume is used=20
6. REQ 27-30 are mandatory security requirements

Leon

-----Original Message-----
From: Leon Portman=20
Sent: Monday, March 28, 2011 10:39 AM
To: 'Elwell, John'; Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor) =
(krehor@cisco.com)
Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08

> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> Sent: Wednesday, March 23, 2011 1:23 PM
> To: siprec@ietf.org
> Subject: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Hi,
>=20
> the SIPREC WG requested the publication of the following draft a few=20
> days ago. Please, find below my AD review.
>=20
> https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
>=20
> Given that the draft contains both requirements and use cases, you may=20
> want to edit the title so that it reads "Use Cases and Requirements=20
> for ..."
>=20
> Typically, Section 1 contains the Introduction and Section 2 the=20
> terminology. You may want to swap both sections.
>=20
> Most of the requirements are phrased so that they describe=20
> capabilities that need to be supported by the system (e.g., the=20
> mechanism MUST provide the SRS with the means to ...) but that do not=20
> need to be necessarily used (e.g., a particular use case may not make=20
> use of that functionality). However, some requirements are phrased so=20
> that the functionality needs to be used (e.g., the mechanism MUST=20
> provide the SRS the wall clock time ...). Requirements 12, 22, 23, 27,=20
> 28, and 29 seem to fall into the latter category. Could you please=20
> check whether that was the intention with all those requirements?
>=20
> A few requirements relate to the security and privacy related=20
> properties of the SRC-SRS interface (e.g., requirements 24 and 29).
> However, the draft does not discuss how the security and privacy of=20
> that interface relate to the security and privacy level used for the=20
> CS being recorded.
> For example, can the confidentiality level of the media going from the=20
> SRC and the SRS be lower than that of the media flowing between the=20
> actual participants of the CS? If you decide there should not be a=20
> requirement on this area, you need to at least discuss this issue=20
> (probably in Sections 6 or 7).
>=20
> Once you address these comments, I will request the IETF-wide last=20
> call for this draft.
>=20
> Thanks,
>=20
> Gonzalo
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20

From john.elwell@siemens-enterprise.com  Mon Mar 28 02:02:48 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4ADA73A68EF for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 02:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id seZuBpYXy5Lx for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 02:02:47 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 052B13A683A for <siprec@ietf.org>; Mon, 28 Mar 2011 02:02:46 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3893661; Mon, 28 Mar 2011 11:04:22 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id ACFA11EB82AE; Mon, 28 Mar 2011 11:04:22 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 28 Mar 2011 11:04:23 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "siprec@ietf.org" <siprec@ietf.org>, "Ken Rehor (krehor) (krehor@cisco.com)" <krehor@cisco.com>
Date: Mon, 28 Mar 2011 11:04:20 +0200
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIAACWzYeAAL84ccAADZn4A
Message-ID: <A444A0F8084434499206E78C106220CA0875AF2C4C@MCHP058A.global-ad.net>
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB46695E@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB46695E@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 09:02:48 -0000

With some editorial changes:

"Communication Sessions and Recording Sessions will require different secur=
ity levels both for signaling and media, depending on deployment configurat=
ions. For some environments, for example, SRS and SRC will be collocated in=
 a secure network region and therefore the RS will not require the same pro=
tection level as a CS that extends over a public network, for example. For =
other environments, the SRS can be located in a public cloud, for example, =
and the RS will require a higher protection level than the CS. For these re=
asons, there is not a direct relationship between the security level of Com=
munication Sessions and the security level of Recording Sessions."=20

John

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 28 March 2011 08:39
> To: Elwell, John; Gonzalo Camarillo; siprec@ietf.org; Ken=20
> Rehor (krehor) (krehor@cisco.com)
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> I want to propose following additional text for the Security=20
> Considerations section (after the last paragraph)
>=20
> "Communication Sessions and Recording Sessions will require=20
> different security levels both for signaling and media,=20
> depending on deployment configurations. For some=20
> environments, for example, SRS and SRC will be collocated in=20
> a secure network region and will not require same protection=20
> level as CS over public network. For other environments, SRS=20
> can be located in a public cloud and RS will require higher=20
> protection level then CS. Because of these reasons, there is=20
> not direct relation between security level of Communication=20
> Sessions and Recording Sessions"
>=20
> Leon
>=20
>=20
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
> Sent: Sunday, March 27, 2011 10:33 AM
> To: Leon Portman; Gonzalo Camarillo; siprec@ietf.org; Ken=20
> Rehor (krehor) (krehor@cisco.com)
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Yes, indeed we had the discussion and came up with reasons=20
> you can't tie the two together. So as Gonzalo suggests, some=20
> of that discussion needs to be captured in the Security=20
> Considerations section.
>=20
> John
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 26 March 2011 14:37
> > To: Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor)=20
> > (krehor@cisco.com); Elwell, John
> > Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
> >=20
> > Hi,
> >=20
> > I want to touch security requirement: about security level of RS vs=20
> > security level of CS. We had a long mailing list discussion (below)=20
> > and it was decided not to have it, because it is more=20
> implementation=20
> > details
> >=20
> > http://www.ietf.org/mail-archive/web/siprec/current/msg01164.html
> >=20
> > Regards
> >=20
> > Leon
> >=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> > Sent: Wednesday, March 23, 2011 1:23 PM
> > To: siprec@ietf.org
> > Subject: [siprec] AD review: draft-ietf-siprec-req-08
> >=20
> > Hi,
> >=20
> > the SIPREC WG requested the publication of the following=20
> draft a few=20
> > days ago. Please, find below my AD review.
> >=20
> > https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> >=20
> > Given that the draft contains both requirements and use=20
> cases, you may=20
> > want to edit the title so that it reads "Use Cases and Requirements=20
> > for ..."
> >=20
> > Typically, Section 1 contains the Introduction and Section 2 the=20
> > terminology. You may want to swap both sections.
> >=20
> > Most of the requirements are phrased so that they describe=20
> > capabilities that need to be supported by the system (e.g., the=20
> > mechanism MUST provide the SRS with the means to ...) but=20
> that do not=20
> > need to be necessarily used (e.g., a particular use case=20
> may not make=20
> > use of that functionality). However, some requirements are=20
> phrased so=20
> > that the functionality needs to be used (e.g., the mechanism MUST=20
> > provide the SRS the wall clock time ...). Requirements 12,=20
> 22, 23, 27,=20
> > 28, and 29 seem to fall into the latter category. Could you please=20
> > check whether that was the intention with all those requirements?
> >=20
> > A few requirements relate to the security and privacy related=20
> > properties of the SRC-SRS interface (e.g., requirements 24 and 29).=20
> > However, the draft does not discuss how the security and privacy of=20
> > that interface relate to the security and privacy level=20
> used for the=20
> > CS being recorded.
> > For example, can the confidentiality level of the media=20
> going from the=20
> > SRC and the SRS be lower than that of the media flowing between the=20
> > actual participants of the CS? If you decide there should not be a=20
> > requirement on this area, you need to at least discuss this issue=20
> > (probably in Sections 6 or 7).
> >=20
> > Once you address these comments, I will request the IETF-wide last=20
> > call for this draft.
> >=20
> > Thanks,
> >=20
> > Gonzalo
> >=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >=20
> =

From john.elwell@siemens-enterprise.com  Mon Mar 28 02:16:49 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A7813A6A1F for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 02:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YLp0ob81UGIW for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 02:16:48 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 5661C3A6917 for <siprec@ietf.org>; Mon, 28 Mar 2011 02:16:48 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3903867; Mon, 28 Mar 2011 11:18:25 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id F1DAC1EB82B4; Mon, 28 Mar 2011 11:18:24 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 28 Mar 2011 11:18:25 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "siprec@ietf.org" <siprec@ietf.org>, "Ken Rehor (krehor) (krehor@cisco.com)" <krehor@cisco.com>
Date: Mon, 28 Mar 2011 11:18:23 +0200
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIAACWzYeAAMoBucAAAC7XAAAD7QOA=
Message-ID: <A444A0F8084434499206E78C106220CA0875AF2C61@MCHP058A.global-ad.net>
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB4669F4@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB4669F4@TLVMBX01.nice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 09:16:49 -0000

I disagree with this. The purpose of a requirements document is to document=
 requirements on the solution. The solutions document(s) should give requir=
ements on implementations. When reviewing the requirements document I had n=
ot interpreted any on the requirements as being requirements on implementat=
ions.=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 28 March 2011 09:43
> To: Elwell, John; Gonzalo Camarillo; siprec@ietf.org; Ken=20
> Rehor (krehor) (krehor@cisco.com)
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Hi,
>=20
> Following AD comments, I am proposing to indicate that=20
> following requirements are mandatory to implement, in=20
> contrast for other requirements that are mandatory for the=20
> protocol to support but optional for implementation depending=20
> use cases:
>=20
> 1. REQ-001 - implement SIP based protocol
[JRE] This is clearly stated as a requirement the mechanism and should rema=
in that way.

> 2. REQ-012  - metadata reporting support=20
[JRE] Ditto. Perhaps the words could be improved by saying "The mechanism M=
UST include a means for providing the SRS...."

> 3. REQ-013 - map between participant and  media=20
[JRE] "The mechanism MUST include a means for the SRS to be able to correla=
te..."

> 4. REQ-022 - wall clock reporting for media synchronization
[JRE] "The mechanism MUST include a means for the SRS to receive ..."

> 5. REQ-023 - wall clock, assuming pause/resume is used=20
[JRE] Similar

> 6. REQ 27-30 are mandatory security requirements
[JRE] REQ-027-029: "The mechanism MUST include a means for ensuring..."
I think REQ-030 is fine as is.

John (as individual)

>=20
> Leon
>=20
> -----Original Message-----
> From: Leon Portman=20
> Sent: Monday, March 28, 2011 10:39 AM
> To: 'Elwell, John'; Gonzalo Camarillo; siprec@ietf.org; Ken=20
> Rehor (krehor) (krehor@cisco.com)
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> > Sent: Wednesday, March 23, 2011 1:23 PM
> > To: siprec@ietf.org
> > Subject: [siprec] AD review: draft-ietf-siprec-req-08
> >=20
> > Hi,
> >=20
> > the SIPREC WG requested the publication of the following=20
> draft a few=20
> > days ago. Please, find below my AD review.
> >=20
> > https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> >=20
> > Given that the draft contains both requirements and use=20
> cases, you may=20
> > want to edit the title so that it reads "Use Cases and Requirements=20
> > for ..."
> >=20
> > Typically, Section 1 contains the Introduction and Section 2 the=20
> > terminology. You may want to swap both sections.
> >=20
> > Most of the requirements are phrased so that they describe=20
> > capabilities that need to be supported by the system (e.g., the=20
> > mechanism MUST provide the SRS with the means to ...) but=20
> that do not=20
> > need to be necessarily used (e.g., a particular use case=20
> may not make=20
> > use of that functionality). However, some requirements are=20
> phrased so=20
> > that the functionality needs to be used (e.g., the mechanism MUST=20
> > provide the SRS the wall clock time ...). Requirements 12,=20
> 22, 23, 27,=20
> > 28, and 29 seem to fall into the latter category. Could you please=20
> > check whether that was the intention with all those requirements?
> >=20
> > A few requirements relate to the security and privacy related=20
> > properties of the SRC-SRS interface (e.g., requirements 24 and 29).
> > However, the draft does not discuss how the security and privacy of=20
> > that interface relate to the security and privacy level=20
> used for the=20
> > CS being recorded.
> > For example, can the confidentiality level of the media=20
> going from the=20
> > SRC and the SRS be lower than that of the media flowing between the=20
> > actual participants of the CS? If you decide there should not be a=20
> > requirement on this area, you need to at least discuss this issue=20
> > (probably in Sections 6 or 7).
> >=20
> > Once you address these comments, I will request the IETF-wide last=20
> > call for this draft.
> >=20
> > Thanks,
> >=20
> > Gonzalo
> >=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >=20
> =

From eckelcu@cisco.com  Mon Mar 28 06:33:45 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F3CE3A6818 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 06:33:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.572
X-Spam-Level: 
X-Spam-Status: No, score=-10.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZkOgEGGIbvE for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 06:33:42 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 479A03A67EB for <siprec@ietf.org>; Mon, 28 Mar 2011 06:33:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=21061; q=dns/txt; s=iport; t=1301319320; x=1302528920; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=wPO0uEZVtNasAOtDIWlFl+gGceW/zK1dwfviNfGQlvg=; b=c4mStvopESyMaq9ubCinACqQ8a+k9TcbO5olRGOCOhsELlcFOnhU1Tcr S7vtEEfxKfH796tsYoBkolBiUvZA4fJZF1+V7HdxeBfgKswGRgDeJDgsz PXnNgk2TCEDLmgGWvUrdlDpsdijeDSZfuTRvNObL4u81X2LjMvZrsEaJB w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBAIaNkE2rRDoH/2dsb2JhbACYAI0/d4hrniebaIMPgloEhTqLFw
X-IronPort-AV: E=Sophos;i="4.63,255,1299456000"; d="scan'208";a="419432008"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-1.cisco.com with ESMTP; 28 Mar 2011 13:35:19 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2SDZJqA005661; Mon, 28 Mar 2011 13:35:19 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 06:35:19 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Mar 2011 06:35:16 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E38202@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED8E0@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsAAClqhQAAXOdEAADtUDkAAjidVA
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com> <E1CB F4C7095A 3D4CAAAEAD09 FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2B09@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED8E0@MCHP058A.global-ad.net>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Leon Portman" <Leon.Portman@nice.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
X-OriginalArrivalTime: 28 Mar 2011 13:35:19.0491 (UTC) FILETIME=[FB053130:01CBED4C]
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 13:33:45 -0000

I agree with this approach. Hopefully Leon and others that saw the need
for this state information can confirm if it works for them.

Cheers,
Charles

> -----Original Message-----
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> Sent: Monday, March 28, 2011 9:13 AM
> To: Elwell, John; Leon Portman; Charles Eckel (eckelcu); Parthasarathi
R (partr); Ram Mohan R
> (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
metadatamodel[wasRE:Progressing the architecture
> document]
>=20
> Hi,
>=20
> The draft-ietf-siprec-architecture has from the very beginning listed
dialog state as an example of
> what would be included in metadata which is why I raised the question.
>=20
> However it is true to say this was put in the architecture document
before we had firmed up the
> requirements or starting any indepth work on metadata so I could
accept that the architecture draft
> simply got this wrong from the start and it maybe should be removed.
We could of course take the view
> that if dialog events are important then the SRS could subscribe to
the dialog event package at the
> SRC and SIPREC does not need to touch this.
>=20
> I don't think we can allow SIPREC metadata to extend as far as
reporting everything that happens to
> the CS including how it is linked to other CS's and what services are
used on the CS (E.g. types of
> transfer etc.). This would quickly get very difficult to define and we
would probably fail.
>=20
> I would prefer to not report this state information in metadata than
open up the possibility of adding
> lots of complexity.
>=20
> Regards
> Andy
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: Elwell, John
> > Sent: 27 March 2011 14:50
> > To: Leon Portman; Charles Eckel (eckelcu); Parthasarathi R
> > (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel[wasRE:Progressing the architecture document]
> >
> >
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 27 March 2011 11:48
> > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R
> > > (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel[wasRE:Progressing the architecture document]
> > >
> > > Charles Hi
> > >
> > > Yes, it will be good to discuss it face to face.
> > >
> > > Just little background for such requirements. Today,
> > > especially for contact centers, it is important for SRS to
> > > capture the information how long customer was waiting for
> > > agent to answer the call, which party hang up, how long was
> > > the hold time, if it was blind transfer or consultation
> > > transfer. This information important both from quality
> > > management point of view and customer experience point of
> > > view.
> > [JRE] (as chair) I think the group needs to consider whether
> > this is within scope. Looking at the requirements, we have:
> > "REQ-012 The mechanism MUST provide the SRS with metadata describing
> >    CSs that are being recorded, including the media being used and
the
> >    identities of parties involved."
> > If we are not recording the session while the caller is
> > waiting to be answered, it seems we perhaps don't have a
> > requirement for metadata about that. This seems to be more
> > about call detail recording (CDR) rather than session
> > recording. We can by all means have this discussion, but I am
> > concerned about scope creep.
> >
> > > It is important also from compliance point of view to
> > > detect if somebody actually received the media stream or
> > > still was in pending state or media stream was disconnected.
> > [JRE] (as individual) I agree we should show a participant as
> > receiving media only if the SRC believes media is actually
> > being sent to that participant (even then, there can be no
> > guarantee it is received, e.g., because NAT or firewall
> > traversal isn't functioning properly, severe packet loss,
> > speaker volume is muted, etc..). But I have doubts whether it
> > is necessarily to try to account for periods when the SRC
> > knows a participant is not receiving media by saying it is
> > because of alerting, hold or whatever.
> >
> > John
> >
> >
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > Sent: Sunday, March 27, 2011 11:35 AM
> > > To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram
> > > Mohan R (rmohanr); Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel[wasRE:Progressing the architecture document]
> > >
> > > Hi Leon,
> > >
> > > Thank you for your patience in trying to explain this to me;
> > > however, I still am not able to understand why the SRS might
> > > need to know this information, or what it would do with it.
> > > Is it that you need to know when a given participant was
> > > receiving the recorded media and when it was not? If so, I do
> > > not think dialog state is sufficient. Is there some other
> > > requirement or functionality addressed by the SRS having such
> > > information?
> > > Perhaps it is easier to discuss in person at the breakfast
> > > meeting Wednesday or during the working group session.
> > >
> > > Cheers,
> > > Charles
> > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: Saturday, March 26, 2011 8:15 PM
> > > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi
> > R (partr);
> > > Ram Mohan R (rmohanr); Hutton,
> > > > Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel[wasRE:Progressing the architecture
> > > > document]
> > > >
> > > > Charles Hi
> > > >
> > > > Without participant session state, SRS will know only when
> > > participant
> > > is part of the session and will
> > > > not know about intermediate states like ringing, retrying etc.
> > > > I know that we have media stream information per
> > participant but not
> > > sure that it is enough.
> > > >
> > > > Leon
> > > > -----Original Message-----
> > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > Sent: Saturday, March 26, 2011 9:07 PM
> > > > To: Leon Portman; Elwell, John; Parthasarathi R (partr);
> > Ram Mohan R
> > > (rmohanr); Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel
> > > [wasRE:Progressing the
> > > > architecture document]
> > > >
> > > > Hi Leon,
> > > >
> > > > I am still having a hard time understanding why we need
> > the session
> > > state information per CS
> > > > participant? Why is this required, who uses it, and how?
> > > >
> > > > Thanks,
> > > > Charles
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On
> > > > Behalf Of Leon Portman
> > > > > Sent: Saturday, March 26, 2011 10:31 AM
> > > > > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R
> > (rmohanr);
> > > > Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] Dialog state in the CS block of
> > > metadatamodel
> > > > [wasRE:Progressing the
> > > > > architecture document]
> > > > >
> > > > > John Hello
> > > > >
> > > > > I agree that SRS (and its application clients) interested
> > > in SESSION
> > > > level events and not underlying
> > > > > DIALOG events. However we do need to support reporting
> > > session state
> > > > information per CS  participant
> > > > > that sometimes equals to dialog level and sometimes not.
> > > > >
> > > > > We could have define more application level state events like
> > > instead
> > > > of TRYING - > RINGING etc.
> > > > > However they could be domain specific.
> > > > >
> > > > > Leon
> > > > >
> > > > > -----Original Message-----
> > > > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > > > Sent: Thursday, March 24, 2011 6:34 PM
> > > > > To: Parthasarathi R (partr); Ram Mohan R (rmohanr);
> > Leon Portman;
> > > > Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadata model
> > > > [wasRE:Progressing the
> > > > > architecture document]
> > > > >
> > > > > This discussion gives me some concerns, echoing to some
> > > extent what
> > > > Ram is saying.
> > > > >
> > > > > SIPREC is about session recording, where a session is the
> > > information
> > > > exchanged between participants
> > > > > in a CS (the media streams) plus metadata. The metadata should
> > > provide
> > > > additional information about
> > > > > the CS. This means information about the communication
> > > SESSION, not
> > > > about the SIP dialog that is used
> > > > > to control that session. With this in mind, consider
> > the following
> > > > points, some of which have already
> > > > > been raised:
> > > > >
> > > > > 1. There may be more than one SIP dialog involved if the
> > > SRC is at a
> > > > B2BUA or conference focus.
> > > > >
> > > > > 2. Does the CS necessarily need to be controlled by SIP? For
> > > example,
> > > > it could be a PSTN call, an RTC-
> > > > > Web call or a Jingle call. None of these preclude using
> > > SIP for the
> > > RS
> > > > (that is what the charter of
> > > > > SIPREC is all about - a SIP-based RS).
> > > > >
> > > > > 3. Somebody retrieving and playing back a recorded CS will be
> > > > interested in session-related events
> > > > > like participants leaving and joining (including the first
> > > > participants joining at the start of the CS
> > > > > and the last participants leaving a the end of the CS), media
> > > streams
> > > > starting and ending and
> > > > > participants starting or stopping receipt of a media stream.
In
> > > other
> > > > words, changes of SESSION state,
> > > > > not dialog state.
> > > > >
> > > > > 4. Some of the SIP dialog states just don't seem relevant. The
> > > > distinction between early dialog and
> > > > > full dialog in SIP does not necessarily corresponding to any
> > > > meaningful state change of the session.
> > > > > For example, A makes a call to B and B answers and
> > starts sending
> > > > media. A receives and renders media
> > > > > (perhaps it has already received SDP answer, allowing
> > it to verify
> > > the
> > > > source of the media). Then A
> > > > > receives the 200 OK (transitioning from an early dialog
> > to a full
> > > > dialog) and continues to receive
> > > > > media. So although there is a dialog state change, there is
not
> > > really
> > > > a session state change.
> > > > >
> > > > > The bit about dialog state in the architecture draft is, in my
> > > > opinion, a legacy from some earlier
> > > > > discussions, before we started having the metadata
> > discussions. I
> > > > think the metadata discussions have
> > > > > taken us in the right direction.
> > > > >
> > > > > John (as individual)
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: siprec-bounces@ietf.org
> > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
R
> > > > (partr)
> > > > > > Sent: 24 March 2011 02:36
> > > > > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] Dialog state in the CS block of
metadata
> > > model
> > > > > > [wasRE:Progressing the architecture document]
> > > > > >
> > > > > > Ram,
> > > > > >
> > > > > > Please read inline.
> > > > > >
> > > > > > Thanks
> > > > > > Partha
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > > From: Ram Mohan R (rmohanr)
> > > > > > Sent: Wed 3/23/2011 7:59 PM
> > > > > > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: [siprec] Dialog state in the CS block of
metadata
> > > model
> > > > > > [wasRE:Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > > I am still trying to understand what is the
> > significance of this
> > > > > > attribute w.r.t CS. Are we saying the attribute represents
the
> > > state
> > > > > > of CS ?
> > > > > >
> > > > > > Note that CS need not be one dialog.
> > > > > >
> > > > > > <Partha>  The attribute is to show the state of CS
> > > only. As it is
> > > > not
> > > > > > single dialog, I have mentioned as session state attribute
> > > </Partha>
> > > > > >
> > > > > > For cases like Conference where there may be different
> > > participants,
> > > > > > if SRC happens to be Focus how do you derive/what is
"session
> > > state"
> > > > ?
> > > > > >
> > > > > > <Partha> I really don't know whether it is generic. My
thought
> > > > > > processing of session state for conference is as follows:
> > > > > >
> > > > > >
> > > > > >
> > > > > > 1) First participant of conference early media (ivr
> > play) may be
> > > > > > considered as "early" state of session.
> > > > > >
> > > > > > 2) The session state is chaged to confirmed in case any
> > > one of the
> > > > > > participant joined in the conference.
> > > > > >
> > > > > > 3) The session state is move to terminated when the last
> > > participant
> > > > > > moved out of the conference.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Please let me know in case other way to represent the
session
> > > state
> > > > of
> > > > > > conference </partha>
> > > > > >
> > > > > >
> > > > > >
> > > > > > For cases where B2BUA acts as SRC what is "session state" ?
> > > > > >
> > > > > > <partha> It looks straight forward for me. In B2BUA case ,
> > > > > >
> > > > > > 1) The stage where in two party is not connected, it is
> > > considered
> > > > as
> > > > > > early state.
> > > > > >
> > > > > > 2) when both are connected, it is confirmed state
> > > > > >
> > > > > > 3) In case of BYE received from any one of the party,
> > then CS is
> > > > > > considered as terminated state
> > > > > >
> > > > > >
> > > > > >
> > > > > > Please note that this is applicable for 3PCC as well.
> > > </partha>
> > > > > >
> > > > > >
> > > > > >
> > > > > > Ram
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: siprec-bounces@ietf.org
> > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
R
> > > > (partr)
> > > > > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > > > > To: Leon Portman; Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] Dialog state in the CS block of
metadata
> > > model
> > > > > > [wasRE:Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > > Leon,
> > > > > >
> > > > > >
> > > > > >
> > > > > > Shall we have optional "event" attribute to indicate the
state
> > > > change
> > > > > > which is similar to "event" attribute in RFC 4235.
> > The "event"
> > > will
> > > > > > include the following:
> > > > > >
> > > > > >
> > > > > >
> > > > > > 1) cancelled
> > > > > >
> > > > > > 2) rejected
> > > > > >
> > > > > > 3) replaced
> > > > > >
> > > > > > 4) bye
> > > > > >
> > > > > > 5) error
> > > > > >
> > > > > > 6) timeout
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Partha
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > Sent: Tue 3/22/2011 9:37 PM
> > > > > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: Dialog state in the CS block of metadata
> > model [was
> > > > > > RE:Progressing the architecture document]
> > > > > >
> > > > > > It can be either application level error or dialog
> > > level errors -
> > > > like
> > > > > > timeout or failures.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Leon
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: Hutton, Andrew
> > > [mailto:andrew.hutton@siemens-enterprise.com]
> > > > > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > > > > To: Leon Portman; Parthasarathi R (partr)
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: Dialog state in the CS block of metadata
> > model [was
> > > RE:
> > > > > > Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > > What would it be used for?
> > > > > >
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Andy
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > >   From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > >   Sent: 22 March 2011 14:11
> > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > >   Cc: siprec@ietf.org
> > > > > >   Subject: RE: Dialog state in the CS block of metadata
> > > model [was
> > > > RE:
> > > > > > Progressing the architecture document]
> > > > > >
> > > > > >   Should we have error state as well?
> > > > > >
> > > > > >
> > > > > >
> > > > > >   Leon
> > > > > >
> > > > > >
> > > > > >
> > > > > >   From: siprec-bounces@ietf.org
> > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
R
> > > > (partr)
> > > > > >   Sent: Tuesday, March 22, 2011 3:33 PM
> > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > >   Cc: siprec@ietf.org
> > > > > >   Subject: [siprec] Dialog state in the CS block of
> > > metadata model
> > > > [was
> > > > > > RE: Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > >   The architecture document proposes to have
> > > dialog/session state
> > > > in
> > > > > > Metadata model. To achieve this, "session state"
> > > attribute has to
> > > be
> > > > > > added in the CS block of Metadata model. The possible
> > values for
> > > > > > session state are
> > > > > >
> > > > > >
> > > > > >
> > > > > >   1) Trying
> > > > > >
> > > > > >   2) Proceeding
> > > > > >
> > > > > >   3) Early
> > > > > >
> > > > > >   4) Confirmed
> > > > > >
> > > > > >   5) Terminated
> > > > > >
> > > > > >
> > > > > >
> > > > > >   Please let me know in case any objection to add
> > this attribute
> > > > in
> > > > > > Metadata model.
> > > > > >
> > > > > >
> > > > > >
> > > > > >   Thanks
> > > > > >
> > > > > >   Partha
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > >   From: Parthasarathi R (partr)
> > > > > >   Sent: Wednesday, March 16, 2011 5:40 AM
> > > > > >   To: Hutton, Andrew
> > > > > >   Cc: Elwell, John; siprec@ietf.org
> > > > > >   Subject: RE: Progressing the architecture document
> > > > > >
> > > > > >   > -----Original Message-----
> > > > > >   > From: siprec-bounces@ietf.org
> > > > > >   > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > > Parthasarathi R
> > > > > > (partr)
> > > > > >   > Sent: 14 March 2011 17:05
> > > > > >   > To: Elwell, John; siprec@ietf.org
> > > > > >   > Subject: Re: [siprec] Progressing the
> > architecture document
> > > > > >
> > > > > >   >
> > > > > >   > Sec 4.3.1 whether 3rd bullet is required?
> > > > > >   >
> > > > > >
> > > > > >   [AndyH]I assume it is as for example I assume it would be
> > > > necessary
> > > > > > to record early-media and update the SRS when the
> > dialog changes
> > > to
> > > > > > the confirmed or terminated state. Does not seem to be in
the
> > > > metadata
> > > > > > draft though. In the end I will either remove these bullets
or
> > > align
> > > > > > with the metadata draft.
> > > > > >   <Partha> It is a good point. Dialog state shall be
> > > added as one
> > > > of
> > > > > > the optional attribute in CS metadata block with
> > > default value as
> > > > > > mid-dialog. This helps to differentiate between early dialog
> > > > > > (ringback) vs mid-dialog (normal
> > > > > > conversation) in recording. In case of no objection for this
> > > > attribute
> > > > > > in metadata model, we will add it. We will work out metadata
> > > format
> > > > > > once the consensus occurs for metadata model.
> > > > > > In case required, we will span separate mail thread to
> > > close this
> > > > > > issue </Partha>
> > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > siprec mailing list
> > > > > siprec@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/siprec
> > >
> >

From Leon.Portman@nice.com  Mon Mar 28 06:44:11 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77B823A693C for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 06:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.419
X-Spam-Level: 
X-Spam-Status: No, score=-2.419 tagged_above=-999 required=5 tests=[AWL=0.180,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PhjD5WxEg0TY for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 06:44:09 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id 410D33A67E3 for <siprec@ietf.org>; Mon, 28 Mar 2011 06:44:08 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Mon, 28 Mar 2011 15:45:44 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
Date: Mon, 28 Mar 2011 15:45:36 +0200
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsAAClqhQAAXOdEAADtUDkAAjidVAAABgrFA=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB466C1B@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com> <E1CBF4C7095A 3D4CAAAEAD09	FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2B09@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED8E0@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E38202@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E38202@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 13:44:11 -0000

Charles Hi

Just to make clear, I don't think SRS should receive dialog level state eve=
nts about all  CS dialogs. I think that we should to support reporting high=
 level session events.
I understand the complexity of that and Ok to keep it open or next phase ex=
tensions

Leon

-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
Sent: Monday, March 28, 2011 3:35 PM
To: Hutton, Andrew; Elwell, John; Leon Portman; Parthasarathi R (partr); Ra=
m Mohan R (rmohanr)
Cc: siprec@ietf.org
Subject: RE: [siprec] Dialog state in the CS block of metadatamodel[wasRE:P=
rogressing the architecture document]

I agree with this approach. Hopefully Leon and others that saw the need for=
 this state information can confirm if it works for them.

Cheers,
Charles

> -----Original Message-----
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> Sent: Monday, March 28, 2011 9:13 AM
> To: Elwell, John; Leon Portman; Charles Eckel (eckelcu); Parthasarathi
R (partr); Ram Mohan R
> (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
metadatamodel[wasRE:Progressing the architecture
> document]
>
> Hi,
>
> The draft-ietf-siprec-architecture has from the very beginning listed
dialog state as an example of
> what would be included in metadata which is why I raised the question.
>
> However it is true to say this was put in the architecture document
before we had firmed up the
> requirements or starting any indepth work on metadata so I could
accept that the architecture draft
> simply got this wrong from the start and it maybe should be removed.
We could of course take the view
> that if dialog events are important then the SRS could subscribe to
the dialog event package at the
> SRC and SIPREC does not need to touch this.
>
> I don't think we can allow SIPREC metadata to extend as far as
reporting everything that happens to
> the CS including how it is linked to other CS's and what services are
used on the CS (E.g. types of
> transfer etc.). This would quickly get very difficult to define and we
would probably fail.
>
> I would prefer to not report this state information in metadata than
open up the possibility of adding
> lots of complexity.
>
> Regards
> Andy
>
>
>
>
>
>
>
>
>
> > -----Original Message-----
> > From: Elwell, John
> > Sent: 27 March 2011 14:50
> > To: Leon Portman; Charles Eckel (eckelcu); Parthasarathi R (partr);
> > Ram Mohan R (rmohanr); Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel[wasRE:Progressing the architecture document]
> >
> >
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 27 March 2011 11:48
> > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R
> > > (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel[wasRE:Progressing the architecture document]
> > >
> > > Charles Hi
> > >
> > > Yes, it will be good to discuss it face to face.
> > >
> > > Just little background for such requirements. Today, especially
> > > for contact centers, it is important for SRS to capture the
> > > information how long customer was waiting for agent to answer the
> > > call, which party hang up, how long was the hold time, if it was
> > > blind transfer or consultation transfer. This information
> > > important both from quality management point of view and customer
> > > experience point of view.
> > [JRE] (as chair) I think the group needs to consider whether this is
> > within scope. Looking at the requirements, we have:
> > "REQ-012 The mechanism MUST provide the SRS with metadata describing
> >    CSs that are being recorded, including the media being used and
the
> >    identities of parties involved."
> > If we are not recording the session while the caller is waiting to
> > be answered, it seems we perhaps don't have a requirement for
> > metadata about that. This seems to be more about call detail
> > recording (CDR) rather than session recording. We can by all means
> > have this discussion, but I am concerned about scope creep.
> >
> > > It is important also from compliance point of view to detect if
> > > somebody actually received the media stream or still was in
> > > pending state or media stream was disconnected.
> > [JRE] (as individual) I agree we should show a participant as
> > receiving media only if the SRC believes media is actually being
> > sent to that participant (even then, there can be no guarantee it is
> > received, e.g., because NAT or firewall traversal isn't functioning
> > properly, severe packet loss, speaker volume is muted, etc..). But I
> > have doubts whether it is necessarily to try to account for periods
> > when the SRC knows a participant is not receiving media by saying it
> > is because of alerting, hold or whatever.
> >
> > John
> >
> >
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > Sent: Sunday, March 27, 2011 11:35 AM
> > > To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram Mohan
> > > R (rmohanr); Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel[wasRE:Progressing the architecture document]
> > >
> > > Hi Leon,
> > >
> > > Thank you for your patience in trying to explain this to me;
> > > however, I still am not able to understand why the SRS might need
> > > to know this information, or what it would do with it.
> > > Is it that you need to know when a given participant was receiving
> > > the recorded media and when it was not? If so, I do not think
> > > dialog state is sufficient. Is there some other requirement or
> > > functionality addressed by the SRS having such information?
> > > Perhaps it is easier to discuss in person at the breakfast meeting
> > > Wednesday or during the working group session.
> > >
> > > Cheers,
> > > Charles
> > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: Saturday, March 26, 2011 8:15 PM
> > > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi
> > R (partr);
> > > Ram Mohan R (rmohanr); Hutton,
> > > > Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel[wasRE:Progressing the architecture
> > > > document]
> > > >
> > > > Charles Hi
> > > >
> > > > Without participant session state, SRS will know only when
> > > participant
> > > is part of the session and will
> > > > not know about intermediate states like ringing, retrying etc.
> > > > I know that we have media stream information per
> > participant but not
> > > sure that it is enough.
> > > >
> > > > Leon
> > > > -----Original Message-----
> > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > Sent: Saturday, March 26, 2011 9:07 PM
> > > > To: Leon Portman; Elwell, John; Parthasarathi R (partr);
> > Ram Mohan R
> > > (rmohanr); Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel
> > > [wasRE:Progressing the
> > > > architecture document]
> > > >
> > > > Hi Leon,
> > > >
> > > > I am still having a hard time understanding why we need
> > the session
> > > state information per CS
> > > > participant? Why is this required, who uses it, and how?
> > > >
> > > > Thanks,
> > > > Charles
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On
> > > > Behalf Of Leon Portman
> > > > > Sent: Saturday, March 26, 2011 10:31 AM
> > > > > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R
> > (rmohanr);
> > > > Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] Dialog state in the CS block of
> > > metadatamodel
> > > > [wasRE:Progressing the
> > > > > architecture document]
> > > > >
> > > > > John Hello
> > > > >
> > > > > I agree that SRS (and its application clients) interested
> > > in SESSION
> > > > level events and not underlying
> > > > > DIALOG events. However we do need to support reporting
> > > session state
> > > > information per CS  participant
> > > > > that sometimes equals to dialog level and sometimes not.
> > > > >
> > > > > We could have define more application level state events like
> > > instead
> > > > of TRYING - > RINGING etc.
> > > > > However they could be domain specific.
> > > > >
> > > > > Leon
> > > > >
> > > > > -----Original Message-----
> > > > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > > > Sent: Thursday, March 24, 2011 6:34 PM
> > > > > To: Parthasarathi R (partr); Ram Mohan R (rmohanr);
> > Leon Portman;
> > > > Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadata model
> > > > [wasRE:Progressing the
> > > > > architecture document]
> > > > >
> > > > > This discussion gives me some concerns, echoing to some
> > > extent what
> > > > Ram is saying.
> > > > >
> > > > > SIPREC is about session recording, where a session is the
> > > information
> > > > exchanged between participants
> > > > > in a CS (the media streams) plus metadata. The metadata should
> > > provide
> > > > additional information about
> > > > > the CS. This means information about the communication
> > > SESSION, not
> > > > about the SIP dialog that is used
> > > > > to control that session. With this in mind, consider
> > the following
> > > > points, some of which have already
> > > > > been raised:
> > > > >
> > > > > 1. There may be more than one SIP dialog involved if the
> > > SRC is at a
> > > > B2BUA or conference focus.
> > > > >
> > > > > 2. Does the CS necessarily need to be controlled by SIP? For
> > > example,
> > > > it could be a PSTN call, an RTC-
> > > > > Web call or a Jingle call. None of these preclude using
> > > SIP for the
> > > RS
> > > > (that is what the charter of
> > > > > SIPREC is all about - a SIP-based RS).
> > > > >
> > > > > 3. Somebody retrieving and playing back a recorded CS will be
> > > > interested in session-related events
> > > > > like participants leaving and joining (including the first
> > > > participants joining at the start of the CS
> > > > > and the last participants leaving a the end of the CS), media
> > > streams
> > > > starting and ending and
> > > > > participants starting or stopping receipt of a media stream.
In
> > > other
> > > > words, changes of SESSION state,
> > > > > not dialog state.
> > > > >
> > > > > 4. Some of the SIP dialog states just don't seem relevant. The
> > > > distinction between early dialog and
> > > > > full dialog in SIP does not necessarily corresponding to any
> > > > meaningful state change of the session.
> > > > > For example, A makes a call to B and B answers and
> > starts sending
> > > > media. A receives and renders media
> > > > > (perhaps it has already received SDP answer, allowing
> > it to verify
> > > the
> > > > source of the media). Then A
> > > > > receives the 200 OK (transitioning from an early dialog
> > to a full
> > > > dialog) and continues to receive
> > > > > media. So although there is a dialog state change, there is
not
> > > really
> > > > a session state change.
> > > > >
> > > > > The bit about dialog state in the architecture draft is, in my
> > > > opinion, a legacy from some earlier
> > > > > discussions, before we started having the metadata
> > discussions. I
> > > > think the metadata discussions have
> > > > > taken us in the right direction.
> > > > >
> > > > > John (as individual)
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: siprec-bounces@ietf.org
> > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
R
> > > > (partr)
> > > > > > Sent: 24 March 2011 02:36
> > > > > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] Dialog state in the CS block of
metadata
> > > model
> > > > > > [wasRE:Progressing the architecture document]
> > > > > >
> > > > > > Ram,
> > > > > >
> > > > > > Please read inline.
> > > > > >
> > > > > > Thanks
> > > > > > Partha
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > > From: Ram Mohan R (rmohanr)
> > > > > > Sent: Wed 3/23/2011 7:59 PM
> > > > > > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: [siprec] Dialog state in the CS block of
metadata
> > > model
> > > > > > [wasRE:Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > > I am still trying to understand what is the
> > significance of this
> > > > > > attribute w.r.t CS. Are we saying the attribute represents
the
> > > state
> > > > > > of CS ?
> > > > > >
> > > > > > Note that CS need not be one dialog.
> > > > > >
> > > > > > <Partha>  The attribute is to show the state of CS
> > > only. As it is
> > > > not
> > > > > > single dialog, I have mentioned as session state attribute
> > > </Partha>
> > > > > >
> > > > > > For cases like Conference where there may be different
> > > participants,
> > > > > > if SRC happens to be Focus how do you derive/what is
"session
> > > state"
> > > > ?
> > > > > >
> > > > > > <Partha> I really don't know whether it is generic. My
thought
> > > > > > processing of session state for conference is as follows:
> > > > > >
> > > > > >
> > > > > >
> > > > > > 1) First participant of conference early media (ivr
> > play) may be
> > > > > > considered as "early" state of session.
> > > > > >
> > > > > > 2) The session state is chaged to confirmed in case any
> > > one of the
> > > > > > participant joined in the conference.
> > > > > >
> > > > > > 3) The session state is move to terminated when the last
> > > participant
> > > > > > moved out of the conference.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Please let me know in case other way to represent the
session
> > > state
> > > > of
> > > > > > conference </partha>
> > > > > >
> > > > > >
> > > > > >
> > > > > > For cases where B2BUA acts as SRC what is "session state" ?
> > > > > >
> > > > > > <partha> It looks straight forward for me. In B2BUA case ,
> > > > > >
> > > > > > 1) The stage where in two party is not connected, it is
> > > considered
> > > > as
> > > > > > early state.
> > > > > >
> > > > > > 2) when both are connected, it is confirmed state
> > > > > >
> > > > > > 3) In case of BYE received from any one of the party,
> > then CS is
> > > > > > considered as terminated state
> > > > > >
> > > > > >
> > > > > >
> > > > > > Please note that this is applicable for 3PCC as well.
> > > </partha>
> > > > > >
> > > > > >
> > > > > >
> > > > > > Ram
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: siprec-bounces@ietf.org
> > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
R
> > > > (partr)
> > > > > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > > > > To: Leon Portman; Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] Dialog state in the CS block of
metadata
> > > model
> > > > > > [wasRE:Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > > Leon,
> > > > > >
> > > > > >
> > > > > >
> > > > > > Shall we have optional "event" attribute to indicate the
state
> > > > change
> > > > > > which is similar to "event" attribute in RFC 4235.
> > The "event"
> > > will
> > > > > > include the following:
> > > > > >
> > > > > >
> > > > > >
> > > > > > 1) cancelled
> > > > > >
> > > > > > 2) rejected
> > > > > >
> > > > > > 3) replaced
> > > > > >
> > > > > > 4) bye
> > > > > >
> > > > > > 5) error
> > > > > >
> > > > > > 6) timeout
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Partha
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > Sent: Tue 3/22/2011 9:37 PM
> > > > > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: Dialog state in the CS block of metadata
> > model [was
> > > > > > RE:Progressing the architecture document]
> > > > > >
> > > > > > It can be either application level error or dialog
> > > level errors -
> > > > like
> > > > > > timeout or failures.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Leon
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: Hutton, Andrew
> > > [mailto:andrew.hutton@siemens-enterprise.com]
> > > > > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > > > > To: Leon Portman; Parthasarathi R (partr)
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: Dialog state in the CS block of metadata
> > model [was
> > > RE:
> > > > > > Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > > What would it be used for?
> > > > > >
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Andy
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > >   From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > >   Sent: 22 March 2011 14:11
> > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > >   Cc: siprec@ietf.org
> > > > > >   Subject: RE: Dialog state in the CS block of metadata
> > > model [was
> > > > RE:
> > > > > > Progressing the architecture document]
> > > > > >
> > > > > >   Should we have error state as well?
> > > > > >
> > > > > >
> > > > > >
> > > > > >   Leon
> > > > > >
> > > > > >
> > > > > >
> > > > > >   From: siprec-bounces@ietf.org
> > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
R
> > > > (partr)
> > > > > >   Sent: Tuesday, March 22, 2011 3:33 PM
> > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > >   Cc: siprec@ietf.org
> > > > > >   Subject: [siprec] Dialog state in the CS block of
> > > metadata model
> > > > [was
> > > > > > RE: Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > >   The architecture document proposes to have
> > > dialog/session state
> > > > in
> > > > > > Metadata model. To achieve this, "session state"
> > > attribute has to
> > > be
> > > > > > added in the CS block of Metadata model. The possible
> > values for
> > > > > > session state are
> > > > > >
> > > > > >
> > > > > >
> > > > > >   1) Trying
> > > > > >
> > > > > >   2) Proceeding
> > > > > >
> > > > > >   3) Early
> > > > > >
> > > > > >   4) Confirmed
> > > > > >
> > > > > >   5) Terminated
> > > > > >
> > > > > >
> > > > > >
> > > > > >   Please let me know in case any objection to add
> > this attribute
> > > > in
> > > > > > Metadata model.
> > > > > >
> > > > > >
> > > > > >
> > > > > >   Thanks
> > > > > >
> > > > > >   Partha
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > >   From: Parthasarathi R (partr)
> > > > > >   Sent: Wednesday, March 16, 2011 5:40 AM
> > > > > >   To: Hutton, Andrew
> > > > > >   Cc: Elwell, John; siprec@ietf.org
> > > > > >   Subject: RE: Progressing the architecture document
> > > > > >
> > > > > >   > -----Original Message-----
> > > > > >   > From: siprec-bounces@ietf.org
> > > > > >   > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > > Parthasarathi R
> > > > > > (partr)
> > > > > >   > Sent: 14 March 2011 17:05
> > > > > >   > To: Elwell, John; siprec@ietf.org
> > > > > >   > Subject: Re: [siprec] Progressing the
> > architecture document
> > > > > >
> > > > > >   >
> > > > > >   > Sec 4.3.1 whether 3rd bullet is required?
> > > > > >   >
> > > > > >
> > > > > >   [AndyH]I assume it is as for example I assume it would be
> > > > necessary
> > > > > > to record early-media and update the SRS when the
> > dialog changes
> > > to
> > > > > > the confirmed or terminated state. Does not seem to be in
the
> > > > metadata
> > > > > > draft though. In the end I will either remove these bullets
or
> > > align
> > > > > > with the metadata draft.
> > > > > >   <Partha> It is a good point. Dialog state shall be
> > > added as one
> > > > of
> > > > > > the optional attribute in CS metadata block with
> > > default value as
> > > > > > mid-dialog. This helps to differentiate between early dialog
> > > > > > (ringback) vs mid-dialog (normal
> > > > > > conversation) in recording. In case of no objection for this
> > > > attribute
> > > > > > in metadata model, we will add it. We will work out metadata
> > > format
> > > > > > once the consensus occurs for metadata model.
> > > > > > In case required, we will span separate mail thread to
> > > close this
> > > > > > issue </Partha>
> > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > siprec mailing list
> > > > > siprec@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/siprec
> > >
> >

From john.elwell@siemens-enterprise.com  Mon Mar 28 08:03:00 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 943B43A6A35 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 08:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ujgVPv0vbUjr for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 08:02:59 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 4ABBE3A6A2F for <siprec@ietf.org>; Mon, 28 Mar 2011 08:02:58 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3917566; Mon, 28 Mar 2011 17:04:33 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id CB6EC23F028E; Mon, 28 Mar 2011 17:04:33 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 28 Mar 2011 17:04:33 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 28 Mar 2011 17:04:32 +0200
Thread-Topic: review comments on draft-ietf-siprec-architecture-01
Thread-Index: Acvr4t/8/sTKgbbNQSmx5Q79X0rBbgBNr1MwAAG1GIAADjIXYA==
Message-ID: <A444A0F8084434499206E78C106220CA0875AF2EDA@MCHP058A.global-ad.net>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86E9F@xmb-sjc-234.amer.cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED94E@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E381EB@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E381EB@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] review comments on draft-ietf-siprec-architecture-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 15:03:00 -0000

I agree it is probably not necessary to say anything in the architecture do=
cument. Whether we need to say something in the protocol document remains t=
o be seen. SRTP is the only IETF-standardized means of securing RTP, so I e=
xpect it at least to be mentioned somewhere in the protocol document.

John
=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel (eckelcu)
> Sent: 28 March 2011 09:20
> To: Hutton, Andrew; siprec@ietf.org
> Subject: Re: [siprec] review comments on=20
> draft-ietf-siprec-architecture-01
>=20
> Hi Andy,
>=20
> Thank you for your response. It seems we are in agreement on=20
> all points.
> Regarding your question:
>=20
> > Section 6 reads, "SRTP is used for securing the Replicated Media." I
> > think other mechanisms should be allowed as well.
>=20
> [AndyH] - What do you suggest we should say here? I guess=20
> anything that
> can be negotiated via SIP/SDP is within scope so we could say=20
> something
> more generic.
>=20
> I think we do not need to mention anything specific here as I do not
> think SIPREC has any special requirements. The requirement to support
> separate security mechanism for CS than RS in some cases is already
> covered in another thread, and I agree with what was proposed there.
>=20
> Cheers,
> Charles
>=20
> > -----Original Message-----
> > From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> > Sent: Monday, March 28, 2011 10:12 AM
> > To: Charles Eckel (eckelcu); siprec@ietf.org
> > Subject: RE: review comments on draft-ietf-siprec-architecture-01
> >=20
> > Hi Charles,
> >=20
> > Thanks for the comments, see below.
> >=20
> > Regards
> > Andy
> >=20
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel
> (eckelcu)
> > > Sent: 26 March 2011 18:23
> > > To: siprec@ietf.org
> > > Subject: [siprec] review comments on
> draft-ietf-siprec-architecture-01
> > >
> > > I started my review of the SIPREC drafts with the
> > > architecture document.
> > > I have some nits and some concerns.
> > > Let me state the concerns first.
> > >
> > > Section 4.2 reads, "the Session Recording Client must decrypt
> > > any media
> > > received on the Communication Session and, if required, re-encrypt
> the
> > > media using a separate SRTP key for the Recording Session."
> > > Why must? I
> > > imagine it could be done in some cases, but I do not see=20
> why it is a
> > > must.
> > >
> >=20
> > [AndyH] - This will be removed in the next update it was=20
> there due to
> some old requirements which have
> > now been removed.
> >=20
> >=20
> > > Section 4.2.1 reads, "Indicate support for the recording
> > > metadata event
> > > package." I am not sure this is needed and do not think=20
> it should be
> > > stated here.
> > >
> >=20
> > [AndyH] This is also tentatively removed in the next draft due to
> comments from Partha. It is not an
> > architectural issue anyway but my personal opinion is that some
> indication from the SRC as to whether
> > it supports sending metadata would be useful.
> >=20
> >=20
> > > Section 4.3.1, no sure why Dialog state of the Communication
> > > Session is
> > > required.
> > >
> >=20
> > [AndyH] - This is currently under debate I am also tending towards
> thinking it is not needed.
> >=20
> > > Section 4.3.2, regarding the OPEN ISSUE, I think we decided on XML
> as
> > > message body in re-INVITE or UPDATE.
> > >
> >=20
> > [AndyH] - Agreed removed from next version.
> >=20
> >=20
> > > Section 4.4 reads, "If the Session Recording Client is aware that
> the
> > > remote UA is a recording aware UA then it MUST notify the UA
> > > using a SIP
> > > based mechanism." Why MUST? It seems "should" is more=20
> appropriate as
> > > other mechanisms may be used depending on the use case. Also, it
> seems
> > > there should not be any normative language in this draft.
> > >
> >=20
> > [AndyH] - The next version will only state that it is the SRC's
> responsible for the notifications and
> > not mandate the mechanism. All normative language will also be
> removed. Hope this will be ok.
> >=20
> > > Section 6 reads, "SRTP is used for securing the=20
> Replicated Media." I
> > > think other mechanisms should be allowed as well.
> >=20
> > [AndyH] - What do you suggest we should say here? I guess anything
> that can be negotiated via SIP/SDP
> > is within scope so we could say something more generic.
> >=20
> > >
> > > Nits
> > >
> > > Section 4.2
> > > Replace "Recording Session is a completely independent" with
> > > "Recording
> > > Session is completely independent".
> >=20
> > [AndyH] - Done.
> >=20
> > >
> > > Cheers,
> > > Charles
> > > _______________________________________________
> > > 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
> =

From partr@cisco.com  Mon Mar 28 09:51:43 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB6F93A6859 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 09:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.028
X-Spam-Level: 
X-Spam-Status: No, score=-10.028 tagged_above=-999 required=5 tests=[AWL=0.571, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xEdPhn5P2Jo3 for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 09:51:41 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id C809E3A67A1 for <siprec@ietf.org>; Mon, 28 Mar 2011 09:51:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=22691; q=dns/txt; s=iport; t=1301331198; x=1302540798; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=44MMmoROkGb6tdeNssgxHkAsLrUsAsQazPh8WDt+ce0=; b=Z4N9lLkL6HeEQ0YWdfp/i57sO6Q5X3CQaVPpEwluDwqA0jXDLR7KX8j+ vnW7nq6HYH/fnW7m2NYcfjCFwv0zBYFHogjwh6Lv1IREL+3PGyUTHazsj 9T6GokYDWE1TWFSd8Ei+rB3nH7wWagcbwnImyRNFj1mQr3SZFeTMz2zMB k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBAE68kE2Q/khMgWdsb2JhbACYBY1AFQEWJiWIa54mnAiDD4JaBIU4ixk
X-IronPort-AV: E=Sophos;i="4.63,256,1299456000"; d="scan'208";a="23492750"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 28 Mar 2011 16:53:16 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2SGrFes022179; Mon, 28 Mar 2011 16:53:15 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 22:23:15 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Mar 2011 22:23:15 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904DA218D@XMB-BGL-411.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB466C1B@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsAAClqhQAAXOdEAADtUDkAAjidVAAABgrFAAAo/hIA==
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com> <E1CB F4C7095A 3D4CAAAEAD09 FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2B09@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED8E0@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E38202@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466C1B@TLVMBX01.nice.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
X-OriginalArrivalTime: 28 Mar 2011 16:53:15.0162 (UTC) FILETIME=[A178C7A0:01CBED68]
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Mar 2011 16:51:43 -0000

The question of "session" state is raised in my mind mainly to
distinguish between early media (Media before session establishment)
from normal media. Without the information in SIPREC metadata, the early
media will be associated with UAS participant's media stream. I'm
interested in knowing whether SIPREC solution has to differentiate
between early media from normal media.

As per John below mail, there is no need to differentiate as per the
current requirement. If most of the folks feel so, I'm fine with not
including "session state" in metadata.

Thanks
Partha=20

-----Original Message-----
From: Leon Portman [mailto:Leon.Portman@nice.com]=20
Sent: Monday, March 28, 2011 7:16 PM
To: Charles Eckel (eckelcu); Hutton, Andrew; Elwell, John; Parthasarathi
R (partr); Ram Mohan R (rmohanr)
Cc: siprec@ietf.org
Subject: RE: [siprec] Dialog state in the CS block of
metadatamodel[wasRE:Progressing the architecture document]

Charles Hi

Just to make clear, I don't think SRS should receive dialog level state
events about all  CS dialogs. I think that we should to support
reporting high level session events.
I understand the complexity of that and Ok to keep it open or next phase
extensions

Leon

-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
Sent: Monday, March 28, 2011 3:35 PM
To: Hutton, Andrew; Elwell, John; Leon Portman; Parthasarathi R (partr);
Ram Mohan R (rmohanr)
Cc: siprec@ietf.org
Subject: RE: [siprec] Dialog state in the CS block of
metadatamodel[wasRE:Progressing the architecture document]

I agree with this approach. Hopefully Leon and others that saw the need
for this state information can confirm if it works for them.

Cheers,
Charles

> -----Original Message-----
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> Sent: Monday, March 28, 2011 9:13 AM
> To: Elwell, John; Leon Portman; Charles Eckel (eckelcu); Parthasarathi
R (partr); Ram Mohan R
> (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
metadatamodel[wasRE:Progressing the architecture
> document]
>
> Hi,
>
> The draft-ietf-siprec-architecture has from the very beginning listed
dialog state as an example of
> what would be included in metadata which is why I raised the question.
>
> However it is true to say this was put in the architecture document
before we had firmed up the
> requirements or starting any indepth work on metadata so I could
accept that the architecture draft
> simply got this wrong from the start and it maybe should be removed.
We could of course take the view
> that if dialog events are important then the SRS could subscribe to
the dialog event package at the
> SRC and SIPREC does not need to touch this.
>
> I don't think we can allow SIPREC metadata to extend as far as
reporting everything that happens to
> the CS including how it is linked to other CS's and what services are
used on the CS (E.g. types of
> transfer etc.). This would quickly get very difficult to define and we
would probably fail.
>
> I would prefer to not report this state information in metadata than
open up the possibility of adding
> lots of complexity.
>
> Regards
> Andy
>
>
>
>
>
>
>
>
>
> > -----Original Message-----
> > From: Elwell, John
> > Sent: 27 March 2011 14:50
> > To: Leon Portman; Charles Eckel (eckelcu); Parthasarathi R (partr);=20
> > Ram Mohan R (rmohanr); Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of=20
> > metadatamodel[wasRE:Progressing the architecture document]
> >
> >
> >
> > > -----Original Message-----
> > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > Sent: 27 March 2011 11:48
> > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R=20
> > > (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of=20
> > > metadatamodel[wasRE:Progressing the architecture document]
> > >
> > > Charles Hi
> > >
> > > Yes, it will be good to discuss it face to face.
> > >
> > > Just little background for such requirements. Today, especially=20
> > > for contact centers, it is important for SRS to capture the=20
> > > information how long customer was waiting for agent to answer the=20
> > > call, which party hang up, how long was the hold time, if it was=20
> > > blind transfer or consultation transfer. This information=20
> > > important both from quality management point of view and customer=20
> > > experience point of view.
> > [JRE] (as chair) I think the group needs to consider whether this is

> > within scope. Looking at the requirements, we have:
> > "REQ-012 The mechanism MUST provide the SRS with metadata describing
> >    CSs that are being recorded, including the media being used and
the
> >    identities of parties involved."
> > If we are not recording the session while the caller is waiting to=20
> > be answered, it seems we perhaps don't have a requirement for=20
> > metadata about that. This seems to be more about call detail=20
> > recording (CDR) rather than session recording. We can by all means=20
> > have this discussion, but I am concerned about scope creep.
> >
> > > It is important also from compliance point of view to detect if=20
> > > somebody actually received the media stream or still was in=20
> > > pending state or media stream was disconnected.
> > [JRE] (as individual) I agree we should show a participant as=20
> > receiving media only if the SRC believes media is actually being=20
> > sent to that participant (even then, there can be no guarantee it is

> > received, e.g., because NAT or firewall traversal isn't functioning=20
> > properly, severe packet loss, speaker volume is muted, etc..). But I

> > have doubts whether it is necessarily to try to account for periods=20
> > when the SRC knows a participant is not receiving media by saying it

> > is because of alerting, hold or whatever.
> >
> > John
> >
> >
> > >
> > > Leon
> > >
> > > -----Original Message-----
> > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > Sent: Sunday, March 27, 2011 11:35 AM
> > > To: Leon Portman; Elwell, John; Parthasarathi R (partr); Ram Mohan

> > > R (rmohanr); Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of=20
> > > metadatamodel[wasRE:Progressing the architecture document]
> > >
> > > Hi Leon,
> > >
> > > Thank you for your patience in trying to explain this to me;=20
> > > however, I still am not able to understand why the SRS might need=20
> > > to know this information, or what it would do with it.
> > > Is it that you need to know when a given participant was receiving

> > > the recorded media and when it was not? If so, I do not think=20
> > > dialog state is sufficient. Is there some other requirement or=20
> > > functionality addressed by the SRS having such information?
> > > Perhaps it is easier to discuss in person at the breakfast meeting

> > > Wednesday or during the working group session.
> > >
> > > Cheers,
> > > Charles
> > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: Saturday, March 26, 2011 8:15 PM
> > > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi
> > R (partr);
> > > Ram Mohan R (rmohanr); Hutton,
> > > > Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel[wasRE:Progressing the architecture
> > > > document]
> > > >
> > > > Charles Hi
> > > >
> > > > Without participant session state, SRS will know only when
> > > participant
> > > is part of the session and will
> > > > not know about intermediate states like ringing, retrying etc.
> > > > I know that we have media stream information per
> > participant but not
> > > sure that it is enough.
> > > >
> > > > Leon
> > > > -----Original Message-----
> > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > Sent: Saturday, March 26, 2011 9:07 PM
> > > > To: Leon Portman; Elwell, John; Parthasarathi R (partr);
> > Ram Mohan R
> > > (rmohanr); Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel
> > > [wasRE:Progressing the
> > > > architecture document]
> > > >
> > > > Hi Leon,
> > > >
> > > > I am still having a hard time understanding why we need
> > the session
> > > state information per CS
> > > > participant? Why is this required, who uses it, and how?
> > > >
> > > > Thanks,
> > > > Charles
> > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On
> > > > Behalf Of Leon Portman
> > > > > Sent: Saturday, March 26, 2011 10:31 AM
> > > > > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R
> > (rmohanr);
> > > > Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: Re: [siprec] Dialog state in the CS block of
> > > metadatamodel
> > > > [wasRE:Progressing the
> > > > > architecture document]
> > > > >
> > > > > John Hello
> > > > >
> > > > > I agree that SRS (and its application clients) interested
> > > in SESSION
> > > > level events and not underlying
> > > > > DIALOG events. However we do need to support reporting
> > > session state
> > > > information per CS  participant
> > > > > that sometimes equals to dialog level and sometimes not.
> > > > >
> > > > > We could have define more application level state events like
> > > instead
> > > > of TRYING - > RINGING etc.
> > > > > However they could be domain specific.
> > > > >
> > > > > Leon
> > > > >
> > > > > -----Original Message-----
> > > > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > > > Sent: Thursday, March 24, 2011 6:34 PM
> > > > > To: Parthasarathi R (partr); Ram Mohan R (rmohanr);
> > Leon Portman;
> > > > Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadata model
> > > > [wasRE:Progressing the
> > > > > architecture document]
> > > > >
> > > > > This discussion gives me some concerns, echoing to some
> > > extent what
> > > > Ram is saying.
> > > > >
> > > > > SIPREC is about session recording, where a session is the
> > > information
> > > > exchanged between participants
> > > > > in a CS (the media streams) plus metadata. The metadata should
> > > provide
> > > > additional information about
> > > > > the CS. This means information about the communication
> > > SESSION, not
> > > > about the SIP dialog that is used
> > > > > to control that session. With this in mind, consider
> > the following
> > > > points, some of which have already
> > > > > been raised:
> > > > >
> > > > > 1. There may be more than one SIP dialog involved if the
> > > SRC is at a
> > > > B2BUA or conference focus.
> > > > >
> > > > > 2. Does the CS necessarily need to be controlled by SIP? For
> > > example,
> > > > it could be a PSTN call, an RTC-
> > > > > Web call or a Jingle call. None of these preclude using
> > > SIP for the
> > > RS
> > > > (that is what the charter of
> > > > > SIPREC is all about - a SIP-based RS).
> > > > >
> > > > > 3. Somebody retrieving and playing back a recorded CS will be
> > > > interested in session-related events
> > > > > like participants leaving and joining (including the first
> > > > participants joining at the start of the CS
> > > > > and the last participants leaving a the end of the CS), media
> > > streams
> > > > starting and ending and
> > > > > participants starting or stopping receipt of a media stream.
In
> > > other
> > > > words, changes of SESSION state,
> > > > > not dialog state.
> > > > >
> > > > > 4. Some of the SIP dialog states just don't seem relevant. The
> > > > distinction between early dialog and
> > > > > full dialog in SIP does not necessarily corresponding to any
> > > > meaningful state change of the session.
> > > > > For example, A makes a call to B and B answers and
> > starts sending
> > > > media. A receives and renders media
> > > > > (perhaps it has already received SDP answer, allowing
> > it to verify
> > > the
> > > > source of the media). Then A
> > > > > receives the 200 OK (transitioning from an early dialog
> > to a full
> > > > dialog) and continues to receive
> > > > > media. So although there is a dialog state change, there is
not
> > > really
> > > > a session state change.
> > > > >
> > > > > The bit about dialog state in the architecture draft is, in my
> > > > opinion, a legacy from some earlier
> > > > > discussions, before we started having the metadata
> > discussions. I
> > > > think the metadata discussions have
> > > > > taken us in the right direction.
> > > > >
> > > > > John (as individual)
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: siprec-bounces@ietf.org=20
> > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
R
> > > > (partr)
> > > > > > Sent: 24 March 2011 02:36
> > > > > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] Dialog state in the CS block of
metadata
> > > model
> > > > > > [wasRE:Progressing the architecture document]
> > > > > >
> > > > > > Ram,
> > > > > >
> > > > > > Please read inline.
> > > > > >
> > > > > > Thanks
> > > > > > Partha
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > > From: Ram Mohan R (rmohanr)
> > > > > > Sent: Wed 3/23/2011 7:59 PM
> > > > > > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: [siprec] Dialog state in the CS block of
metadata
> > > model
> > > > > > [wasRE:Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > > I am still trying to understand what is the
> > significance of this
> > > > > > attribute w.r.t CS. Are we saying the attribute represents
the
> > > state
> > > > > > of CS ?
> > > > > >
> > > > > > Note that CS need not be one dialog.
> > > > > >
> > > > > > <Partha>  The attribute is to show the state of CS
> > > only. As it is
> > > > not
> > > > > > single dialog, I have mentioned as session state attribute
> > > </Partha>
> > > > > >
> > > > > > For cases like Conference where there may be different
> > > participants,
> > > > > > if SRC happens to be Focus how do you derive/what is
"session
> > > state"
> > > > ?
> > > > > >
> > > > > > <Partha> I really don't know whether it is generic. My
thought
> > > > > > processing of session state for conference is as follows:
> > > > > >
> > > > > >
> > > > > >
> > > > > > 1) First participant of conference early media (ivr
> > play) may be
> > > > > > considered as "early" state of session.
> > > > > >
> > > > > > 2) The session state is chaged to confirmed in case any
> > > one of the
> > > > > > participant joined in the conference.
> > > > > >
> > > > > > 3) The session state is move to terminated when the last
> > > participant
> > > > > > moved out of the conference.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Please let me know in case other way to represent the
session
> > > state
> > > > of
> > > > > > conference </partha>
> > > > > >
> > > > > >
> > > > > >
> > > > > > For cases where B2BUA acts as SRC what is "session state" ?
> > > > > >
> > > > > > <partha> It looks straight forward for me. In B2BUA case ,
> > > > > >
> > > > > > 1) The stage where in two party is not connected, it is
> > > considered
> > > > as
> > > > > > early state.
> > > > > >
> > > > > > 2) when both are connected, it is confirmed state
> > > > > >
> > > > > > 3) In case of BYE received from any one of the party,
> > then CS is
> > > > > > considered as terminated state
> > > > > >
> > > > > >
> > > > > >
> > > > > > Please note that this is applicable for 3PCC as well.
> > > </partha>
> > > > > >
> > > > > >
> > > > > >
> > > > > > Ram
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: siprec-bounces@ietf.org=20
> > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
R
> > > > (partr)
> > > > > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > > > > To: Leon Portman; Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] Dialog state in the CS block of
metadata
> > > model
> > > > > > [wasRE:Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > > Leon,
> > > > > >
> > > > > >
> > > > > >
> > > > > > Shall we have optional "event" attribute to indicate the
state
> > > > change
> > > > > > which is similar to "event" attribute in RFC 4235.
> > The "event"
> > > will
> > > > > > include the following:
> > > > > >
> > > > > >
> > > > > >
> > > > > > 1) cancelled
> > > > > >
> > > > > > 2) rejected
> > > > > >
> > > > > > 3) replaced
> > > > > >
> > > > > > 4) bye
> > > > > >
> > > > > > 5) error
> > > > > >
> > > > > > 6) timeout
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Partha
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > Sent: Tue 3/22/2011 9:37 PM
> > > > > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: Dialog state in the CS block of metadata
> > model [was
> > > > > > RE:Progressing the architecture document]
> > > > > >
> > > > > > It can be either application level error or dialog
> > > level errors -
> > > > like
> > > > > > timeout or failures.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Leon
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: Hutton, Andrew
> > > [mailto:andrew.hutton@siemens-enterprise.com]
> > > > > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > > > > To: Leon Portman; Parthasarathi R (partr)
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: Dialog state in the CS block of metadata
> > model [was
> > > RE:
> > > > > > Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > > What would it be used for?
> > > > > >
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Andy
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > >   From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > >   Sent: 22 March 2011 14:11
> > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > >   Cc: siprec@ietf.org
> > > > > >   Subject: RE: Dialog state in the CS block of metadata
> > > model [was
> > > > RE:
> > > > > > Progressing the architecture document]
> > > > > >
> > > > > >   Should we have error state as well?
> > > > > >
> > > > > >
> > > > > >
> > > > > >   Leon
> > > > > >
> > > > > >
> > > > > >
> > > > > >   From: siprec-bounces@ietf.org=20
> > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi
R
> > > > (partr)
> > > > > >   Sent: Tuesday, March 22, 2011 3:33 PM
> > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > >   Cc: siprec@ietf.org
> > > > > >   Subject: [siprec] Dialog state in the CS block of
> > > metadata model
> > > > [was
> > > > > > RE: Progressing the architecture document]
> > > > > >
> > > > > >
> > > > > >
> > > > > >   The architecture document proposes to have
> > > dialog/session state
> > > > in
> > > > > > Metadata model. To achieve this, "session state"
> > > attribute has to
> > > be
> > > > > > added in the CS block of Metadata model. The possible
> > values for
> > > > > > session state are
> > > > > >
> > > > > >
> > > > > >
> > > > > >   1) Trying
> > > > > >
> > > > > >   2) Proceeding
> > > > > >
> > > > > >   3) Early
> > > > > >
> > > > > >   4) Confirmed
> > > > > >
> > > > > >   5) Terminated
> > > > > >
> > > > > >
> > > > > >
> > > > > >   Please let me know in case any objection to add
> > this attribute
> > > > in
> > > > > > Metadata model.
> > > > > >
> > > > > >
> > > > > >
> > > > > >   Thanks
> > > > > >
> > > > > >   Partha
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > >   From: Parthasarathi R (partr)
> > > > > >   Sent: Wednesday, March 16, 2011 5:40 AM
> > > > > >   To: Hutton, Andrew
> > > > > >   Cc: Elwell, John; siprec@ietf.org
> > > > > >   Subject: RE: Progressing the architecture document
> > > > > >
> > > > > >   > -----Original Message-----
> > > > > >   > From: siprec-bounces@ietf.org
> > > > > >   > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > > Parthasarathi R
> > > > > > (partr)
> > > > > >   > Sent: 14 March 2011 17:05
> > > > > >   > To: Elwell, John; siprec@ietf.org
> > > > > >   > Subject: Re: [siprec] Progressing the
> > architecture document
> > > > > >
> > > > > >   >
> > > > > >   > Sec 4.3.1 whether 3rd bullet is required?
> > > > > >   >
> > > > > >
> > > > > >   [AndyH]I assume it is as for example I assume it would be
> > > > necessary
> > > > > > to record early-media and update the SRS when the
> > dialog changes
> > > to
> > > > > > the confirmed or terminated state. Does not seem to be in
the
> > > > metadata
> > > > > > draft though. In the end I will either remove these bullets
or
> > > align
> > > > > > with the metadata draft.
> > > > > >   <Partha> It is a good point. Dialog state shall be
> > > added as one
> > > > of
> > > > > > the optional attribute in CS metadata block with
> > > default value as
> > > > > > mid-dialog. This helps to differentiate between early dialog
> > > > > > (ringback) vs mid-dialog (normal
> > > > > > conversation) in recording. In case of no objection for this
> > > > attribute
> > > > > > in metadata model, we will add it. We will work out metadata
> > > format
> > > > > > once the consensus occurs for metadata model.
> > > > > > In case required, we will span separate mail thread to
> > > close this
> > > > > > issue </Partha>
> > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > siprec mailing list
> > > > > siprec@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/siprec
> > >
> >

From john.elwell@siemens-enterprise.com  Mon Mar 28 22:07:23 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E35DA3A6AAD for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 22:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKldpdnA3JcG for <siprec@core3.amsl.com>; Mon, 28 Mar 2011 22:07:19 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 3D8973A6802 for <siprec@ietf.org>; Mon, 28 Mar 2011 22:07:11 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3924340; Tue, 29 Mar 2011 07:08:48 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id BDF531EB82B4; Tue, 29 Mar 2011 07:08:48 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 29 Mar 2011 07:08:48 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, Leon Portman <Leon.Portman@nice.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
Date: Tue, 29 Mar 2011 07:08:47 +0200
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsAAClqhQAAXOdEAADtUDkAAjidVAAABgrFAAAo/hIAAdpARg
Message-ID: <A444A0F8084434499206E78C106220CA0875AF3066@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com> <E1CB F4C7095A	3D4CAAAEAD09		FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2B09@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED8E0@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E38202@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466C1B@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A623904DA218D@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904DA218D@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 05:07:23 -0000

Partha,

I think the real distinction you wish to make is between media coming from =
a particular participant (associated with the UAS) and media coming from so=
me other entity (e.g., media server). In my view the latter case, if we cho=
ose to record it, comes from a different "participant". It has nothing to d=
o with whether it is deemed early or regular from a SIP dialog perspective.

John (as individual)


> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 28 March 2011 17:53
> To: Leon Portman; Charles Eckel (eckelcu); Hutton, Andrew;
> Elwell, John; Ram Mohan R (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture document]
>
>
> The question of "session" state is raised in my mind mainly to
> distinguish between early media (Media before session establishment)
> from normal media. Without the information in SIPREC
> metadata, the early
> media will be associated with UAS participant's media stream. I'm
> interested in knowing whether SIPREC solution has to differentiate
> between early media from normal media.
>
> As per John below mail, there is no need to differentiate as per the
> current requirement. If most of the folks feel so, I'm fine with not
> including "session state" in metadata.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Monday, March 28, 2011 7:16 PM
> To: Charles Eckel (eckelcu); Hutton, Andrew; Elwell, John;
> Parthasarathi
> R (partr); Ram Mohan R (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture document]
>
> Charles Hi
>
> Just to make clear, I don't think SRS should receive dialog
> level state
> events about all  CS dialogs. I think that we should to support
> reporting high level session events.
> I understand the complexity of that and Ok to keep it open or
> next phase
> extensions
>
> Leon
>
> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: Monday, March 28, 2011 3:35 PM
> To: Hutton, Andrew; Elwell, John; Leon Portman; Parthasarathi
> R (partr);
> Ram Mohan R (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture document]
>
> I agree with this approach. Hopefully Leon and others that
> saw the need
> for this state information can confirm if it works for them.
>
> Cheers,
> Charles
>
> > -----Original Message-----
> > From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> > Sent: Monday, March 28, 2011 9:13 AM
> > To: Elwell, John; Leon Portman; Charles Eckel (eckelcu);
> Parthasarathi
> R (partr); Ram Mohan R
> > (rmohanr)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture
> > document]
> >
> > Hi,
> >
> > The draft-ietf-siprec-architecture has from the very
> beginning listed
> dialog state as an example of
> > what would be included in metadata which is why I raised
> the question.
> >
> > However it is true to say this was put in the architecture document
> before we had firmed up the
> > requirements or starting any indepth work on metadata so I could
> accept that the architecture draft
> > simply got this wrong from the start and it maybe should be removed.
> We could of course take the view
> > that if dialog events are important then the SRS could subscribe to
> the dialog event package at the
> > SRC and SIPREC does not need to touch this.
> >
> > I don't think we can allow SIPREC metadata to extend as far as
> reporting everything that happens to
> > the CS including how it is linked to other CS's and what
> services are
> used on the CS (E.g. types of
> > transfer etc.). This would quickly get very difficult to
> define and we
> would probably fail.
> >
> > I would prefer to not report this state information in metadata than
> open up the possibility of adding
> > lots of complexity.
> >
> > Regards
> > Andy
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Elwell, John
> > > Sent: 27 March 2011 14:50
> > > To: Leon Portman; Charles Eckel (eckelcu); Parthasarathi
> R (partr);
> > > Ram Mohan R (rmohanr); Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel[wasRE:Progressing the architecture document]
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: 27 March 2011 11:48
> > > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R
> > > > (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > metadatamodel[wasRE:Progressing the architecture document]
> > > >
> > > > Charles Hi
> > > >
> > > > Yes, it will be good to discuss it face to face.
> > > >
> > > > Just little background for such requirements. Today, especially
> > > > for contact centers, it is important for SRS to capture the
> > > > information how long customer was waiting for agent to
> answer the
> > > > call, which party hang up, how long was the hold time,
> if it was
> > > > blind transfer or consultation transfer. This information
> > > > important both from quality management point of view
> and customer
> > > > experience point of view.
> > > [JRE] (as chair) I think the group needs to consider
> whether this is
>
> > > within scope. Looking at the requirements, we have:
> > > "REQ-012 The mechanism MUST provide the SRS with metadata
> describing
> > >    CSs that are being recorded, including the media being used and
> the
> > >    identities of parties involved."
> > > If we are not recording the session while the caller is
> waiting to
> > > be answered, it seems we perhaps don't have a requirement for
> > > metadata about that. This seems to be more about call detail
> > > recording (CDR) rather than session recording. We can by
> all means
> > > have this discussion, but I am concerned about scope creep.
> > >
> > > > It is important also from compliance point of view to detect if
> > > > somebody actually received the media stream or still was in
> > > > pending state or media stream was disconnected.
> > > [JRE] (as individual) I agree we should show a participant as
> > > receiving media only if the SRC believes media is actually being
> > > sent to that participant (even then, there can be no
> guarantee it is
>
> > > received, e.g., because NAT or firewall traversal isn't
> functioning
> > > properly, severe packet loss, speaker volume is muted,
> etc..). But I
>
> > > have doubts whether it is necessarily to try to account
> for periods
> > > when the SRC knows a participant is not receiving media
> by saying it
>
> > > is because of alerting, hold or whatever.
> > >
> > > John
> > >
> > >
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > Sent: Sunday, March 27, 2011 11:35 AM
> > > > To: Leon Portman; Elwell, John; Parthasarathi R
> (partr); Ram Mohan
>
> > > > R (rmohanr); Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > metadatamodel[wasRE:Progressing the architecture document]
> > > >
> > > > Hi Leon,
> > > >
> > > > Thank you for your patience in trying to explain this to me;
> > > > however, I still am not able to understand why the SRS
> might need
> > > > to know this information, or what it would do with it.
> > > > Is it that you need to know when a given participant
> was receiving
>
> > > > the recorded media and when it was not? If so, I do not think
> > > > dialog state is sufficient. Is there some other requirement or
> > > > functionality addressed by the SRS having such information?
> > > > Perhaps it is easier to discuss in person at the
> breakfast meeting
>
> > > > Wednesday or during the working group session.
> > > >
> > > > Cheers,
> > > > Charles
> > > >
> > > > > -----Original Message-----
> > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > Sent: Saturday, March 26, 2011 8:15 PM
> > > > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi
> > > R (partr);
> > > > Ram Mohan R (rmohanr); Hutton,
> > > > > Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > metadatamodel[wasRE:Progressing the architecture
> > > > > document]
> > > > >
> > > > > Charles Hi
> > > > >
> > > > > Without participant session state, SRS will know only when
> > > > participant
> > > > is part of the session and will
> > > > > not know about intermediate states like ringing, retrying etc.
> > > > > I know that we have media stream information per
> > > participant but not
> > > > sure that it is enough.
> > > > >
> > > > > Leon
> > > > > -----Original Message-----
> > > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > > Sent: Saturday, March 26, 2011 9:07 PM
> > > > > To: Leon Portman; Elwell, John; Parthasarathi R (partr);
> > > Ram Mohan R
> > > > (rmohanr); Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel
> > > > [wasRE:Progressing the
> > > > > architecture document]
> > > > >
> > > > > Hi Leon,
> > > > >
> > > > > I am still having a hard time understanding why we need
> > > the session
> > > > state information per CS
> > > > > participant? Why is this required, who uses it, and how?
> > > > >
> > > > > Thanks,
> > > > > Charles
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On
> > > > > Behalf Of Leon Portman
> > > > > > Sent: Saturday, March 26, 2011 10:31 AM
> > > > > > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R
> > > (rmohanr);
> > > > > Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] Dialog state in the CS block of
> > > > metadatamodel
> > > > > [wasRE:Progressing the
> > > > > > architecture document]
> > > > > >
> > > > > > John Hello
> > > > > >
> > > > > > I agree that SRS (and its application clients) interested
> > > > in SESSION
> > > > > level events and not underlying
> > > > > > DIALOG events. However we do need to support reporting
> > > > session state
> > > > > information per CS  participant
> > > > > > that sometimes equals to dialog level and sometimes not.
> > > > > >
> > > > > > We could have define more application level state
> events like
> > > > instead
> > > > > of TRYING - > RINGING etc.
> > > > > > However they could be domain specific.
> > > > > >
> > > > > > Leon
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Elwell, John
> [mailto:john.elwell@siemens-enterprise.com]
> > > > > > Sent: Thursday, March 24, 2011 6:34 PM
> > > > > > To: Parthasarathi R (partr); Ram Mohan R (rmohanr);
> > > Leon Portman;
> > > > > Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > metadata model
> > > > > [wasRE:Progressing the
> > > > > > architecture document]
> > > > > >
> > > > > > This discussion gives me some concerns, echoing to some
> > > > extent what
> > > > > Ram is saying.
> > > > > >
> > > > > > SIPREC is about session recording, where a session is the
> > > > information
> > > > > exchanged between participants
> > > > > > in a CS (the media streams) plus metadata. The
> metadata should
> > > > provide
> > > > > additional information about
> > > > > > the CS. This means information about the communication
> > > > SESSION, not
> > > > > about the SIP dialog that is used
> > > > > > to control that session. With this in mind, consider
> > > the following
> > > > > points, some of which have already
> > > > > > been raised:
> > > > > >
> > > > > > 1. There may be more than one SIP dialog involved if the
> > > > SRC is at a
> > > > > B2BUA or conference focus.
> > > > > >
> > > > > > 2. Does the CS necessarily need to be controlled by SIP? For
> > > > example,
> > > > > it could be a PSTN call, an RTC-
> > > > > > Web call or a Jingle call. None of these preclude using
> > > > SIP for the
> > > > RS
> > > > > (that is what the charter of
> > > > > > SIPREC is all about - a SIP-based RS).
> > > > > >
> > > > > > 3. Somebody retrieving and playing back a recorded
> CS will be
> > > > > interested in session-related events
> > > > > > like participants leaving and joining (including the first
> > > > > participants joining at the start of the CS
> > > > > > and the last participants leaving a the end of the
> CS), media
> > > > streams
> > > > > starting and ending and
> > > > > > participants starting or stopping receipt of a media stream.
> In
> > > > other
> > > > > words, changes of SESSION state,
> > > > > > not dialog state.
> > > > > >
> > > > > > 4. Some of the SIP dialog states just don't seem
> relevant. The
> > > > > distinction between early dialog and
> > > > > > full dialog in SIP does not necessarily corresponding to any
> > > > > meaningful state change of the session.
> > > > > > For example, A makes a call to B and B answers and
> > > starts sending
> > > > > media. A receives and renders media
> > > > > > (perhaps it has already received SDP answer, allowing
> > > it to verify
> > > > the
> > > > > source of the media). Then A
> > > > > > receives the 200 OK (transitioning from an early dialog
> > > to a full
> > > > > dialog) and continues to receive
> > > > > > media. So although there is a dialog state change, there is
> not
> > > > really
> > > > > a session state change.
> > > > > >
> > > > > > The bit about dialog state in the architecture
> draft is, in my
> > > > > opinion, a legacy from some earlier
> > > > > > discussions, before we started having the metadata
> > > discussions. I
> > > > > think the metadata discussions have
> > > > > > taken us in the right direction.
> > > > > >
> > > > > > John (as individual)
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: siprec-bounces@ietf.org
> > > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of
> Parthasarathi
> R
> > > > > (partr)
> > > > > > > Sent: 24 March 2011 02:36
> > > > > > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: Re: [siprec] Dialog state in the CS block of
> metadata
> > > > model
> > > > > > > [wasRE:Progressing the architecture document]
> > > > > > >
> > > > > > > Ram,
> > > > > > >
> > > > > > > Please read inline.
> > > > > > >
> > > > > > > Thanks
> > > > > > > Partha
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > > From: Ram Mohan R (rmohanr)
> > > > > > > Sent: Wed 3/23/2011 7:59 PM
> > > > > > > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: RE: [siprec] Dialog state in the CS block of
> metadata
> > > > model
> > > > > > > [wasRE:Progressing the architecture document]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I am still trying to understand what is the
> > > significance of this
> > > > > > > attribute w.r.t CS. Are we saying the attribute represents
> the
> > > > state
> > > > > > > of CS ?
> > > > > > >
> > > > > > > Note that CS need not be one dialog.
> > > > > > >
> > > > > > > <Partha>  The attribute is to show the state of CS
> > > > only. As it is
> > > > > not
> > > > > > > single dialog, I have mentioned as session state attribute
> > > > </Partha>
> > > > > > >
> > > > > > > For cases like Conference where there may be different
> > > > participants,
> > > > > > > if SRC happens to be Focus how do you derive/what is
> "session
> > > > state"
> > > > > ?
> > > > > > >
> > > > > > > <Partha> I really don't know whether it is generic. My
> thought
> > > > > > > processing of session state for conference is as follows:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 1) First participant of conference early media (ivr
> > > play) may be
> > > > > > > considered as "early" state of session.
> > > > > > >
> > > > > > > 2) The session state is chaged to confirmed in case any
> > > > one of the
> > > > > > > participant joined in the conference.
> > > > > > >
> > > > > > > 3) The session state is move to terminated when the last
> > > > participant
> > > > > > > moved out of the conference.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Please let me know in case other way to represent the
> session
> > > > state
> > > > > of
> > > > > > > conference </partha>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > For cases where B2BUA acts as SRC what is
> "session state" ?
> > > > > > >
> > > > > > > <partha> It looks straight forward for me. In B2BUA case ,
> > > > > > >
> > > > > > > 1) The stage where in two party is not connected, it is
> > > > considered
> > > > > as
> > > > > > > early state.
> > > > > > >
> > > > > > > 2) when both are connected, it is confirmed state
> > > > > > >
> > > > > > > 3) In case of BYE received from any one of the party,
> > > then CS is
> > > > > > > considered as terminated state
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Please note that this is applicable for 3PCC as well.
> > > > </partha>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Ram
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From: siprec-bounces@ietf.org
> > > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of
> Parthasarathi
> R
> > > > > (partr)
> > > > > > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > > > > > To: Leon Portman; Hutton, Andrew
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: Re: [siprec] Dialog state in the CS block of
> metadata
> > > > model
> > > > > > > [wasRE:Progressing the architecture document]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Leon,
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Shall we have optional "event" attribute to indicate the
> state
> > > > > change
> > > > > > > which is similar to "event" attribute in RFC 4235.
> > > The "event"
> > > > will
> > > > > > > include the following:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 1) cancelled
> > > > > > >
> > > > > > > 2) rejected
> > > > > > >
> > > > > > > 3) replaced
> > > > > > >
> > > > > > > 4) bye
> > > > > > >
> > > > > > > 5) error
> > > > > > >
> > > > > > > 6) timeout
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Partha
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > > Sent: Tue 3/22/2011 9:37 PM
> > > > > > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: RE: Dialog state in the CS block of metadata
> > > model [was
> > > > > > > RE:Progressing the architecture document]
> > > > > > >
> > > > > > > It can be either application level error or dialog
> > > > level errors -
> > > > > like
> > > > > > > timeout or failures.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Leon
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From: Hutton, Andrew
> > > > [mailto:andrew.hutton@siemens-enterprise.com]
> > > > > > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > > > > > To: Leon Portman; Parthasarathi R (partr)
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: RE: Dialog state in the CS block of metadata
> > > model [was
> > > > RE:
> > > > > > > Progressing the architecture document]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > What would it be used for?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Regards
> > > > > > >
> > > > > > > Andy
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > >   From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > >   Sent: 22 March 2011 14:11
> > > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > > >   Cc: siprec@ietf.org
> > > > > > >   Subject: RE: Dialog state in the CS block of metadata
> > > > model [was
> > > > > RE:
> > > > > > > Progressing the architecture document]
> > > > > > >
> > > > > > >   Should we have error state as well?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   Leon
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   From: siprec-bounces@ietf.org
> > > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of
> Parthasarathi
> R
> > > > > (partr)
> > > > > > >   Sent: Tuesday, March 22, 2011 3:33 PM
> > > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > > >   Cc: siprec@ietf.org
> > > > > > >   Subject: [siprec] Dialog state in the CS block of
> > > > metadata model
> > > > > [was
> > > > > > > RE: Progressing the architecture document]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   The architecture document proposes to have
> > > > dialog/session state
> > > > > in
> > > > > > > Metadata model. To achieve this, "session state"
> > > > attribute has to
> > > > be
> > > > > > > added in the CS block of Metadata model. The possible
> > > values for
> > > > > > > session state are
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   1) Trying
> > > > > > >
> > > > > > >   2) Proceeding
> > > > > > >
> > > > > > >   3) Early
> > > > > > >
> > > > > > >   4) Confirmed
> > > > > > >
> > > > > > >   5) Terminated
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   Please let me know in case any objection to add
> > > this attribute
> > > > > in
> > > > > > > Metadata model.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   Thanks
> > > > > > >
> > > > > > >   Partha
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > >   From: Parthasarathi R (partr)
> > > > > > >   Sent: Wednesday, March 16, 2011 5:40 AM
> > > > > > >   To: Hutton, Andrew
> > > > > > >   Cc: Elwell, John; siprec@ietf.org
> > > > > > >   Subject: RE: Progressing the architecture document
> > > > > > >
> > > > > > >   > -----Original Message-----
> > > > > > >   > From: siprec-bounces@ietf.org
> > > > > > >   > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > > > Parthasarathi R
> > > > > > > (partr)
> > > > > > >   > Sent: 14 March 2011 17:05
> > > > > > >   > To: Elwell, John; siprec@ietf.org
> > > > > > >   > Subject: Re: [siprec] Progressing the
> > > architecture document
> > > > > > >
> > > > > > >   >
> > > > > > >   > Sec 4.3.1 whether 3rd bullet is required?
> > > > > > >   >
> > > > > > >
> > > > > > >   [AndyH]I assume it is as for example I assume
> it would be
> > > > > necessary
> > > > > > > to record early-media and update the SRS when the
> > > dialog changes
> > > > to
> > > > > > > the confirmed or terminated state. Does not seem to be in
> the
> > > > > metadata
> > > > > > > draft though. In the end I will either remove
> these bullets
> or
> > > > align
> > > > > > > with the metadata draft.
> > > > > > >   <Partha> It is a good point. Dialog state shall be
> > > > added as one
> > > > > of
> > > > > > > the optional attribute in CS metadata block with
> > > > default value as
> > > > > > > mid-dialog. This helps to differentiate between
> early dialog
> > > > > > > (ringback) vs mid-dialog (normal
> > > > > > > conversation) in recording. In case of no
> objection for this
> > > > > attribute
> > > > > > > in metadata model, we will add it. We will work
> out metadata
> > > > format
> > > > > > > once the consensus occurs for metadata model.
> > > > > > > In case required, we will span separate mail thread to
> > > > close this
> > > > > > > issue </Partha>
> > > > > > >
> > > > > > >
> > > > > > _______________________________________________
> > > > > > siprec mailing list
> > > > > > siprec@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/siprec
> > > >
> > >
>

From Leon.Portman@nice.com  Tue Mar 29 00:00:01 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA5BB3A683F for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 00:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.423
X-Spam-Level: 
X-Spam-Status: No, score=-2.423 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kr-fdaN-QtaX for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 00:00:00 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id D4AFC3A676A for <siprec@ietf.org>; Mon, 28 Mar 2011 23:59:59 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Tue, 29 Mar 2011 09:01:37 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "siprec@ietf.org" <siprec@ietf.org>, "Ken Rehor (krehor) (krehor@cisco.com)" <krehor@cisco.com>
Date: Tue, 29 Mar 2011 09:01:33 +0200
Thread-Topic: [siprec] AD review: draft-ietf-siprec-req-08
Thread-Index: AcvpTKPHjf4hADHdT4KT/3tOBxh5KgCdfrIAACWzYeAAMoBucAAAC7XAAAD7QOAALeEzEA==
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB5D445B@TLVMBX01.nice.com>
References: <4D89D801.8040308@ericsson.com> <07465C1D981ABC41A344374066AE1A2C38AB466348@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2AF1@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB4669F4@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2C61@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF2C61@MCHP058A.global-ad.net>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] AD review: draft-ietf-siprec-req-08
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 07:00:01 -0000

Ok, we will update the document with the below.

Thanks

Leon

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Monday, March 28, 2011 11:18 AM
To: Leon Portman; Gonzalo Camarillo; siprec@ietf.org; Ken Rehor (krehor) (k=
rehor@cisco.com)
Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08

I disagree with this. The purpose of a requirements document is to document=
 requirements on the solution. The solutions document(s) should give requir=
ements on implementations. When reviewing the requirements document I had n=
ot interpreted any on the requirements as being requirements on implementat=
ions.=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 28 March 2011 09:43
> To: Elwell, John; Gonzalo Camarillo; siprec@ietf.org; Ken Rehor=20
> (krehor) (krehor@cisco.com)
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> Hi,
>=20
> Following AD comments, I am proposing to indicate that following=20
> requirements are mandatory to implement, in contrast for other=20
> requirements that are mandatory for the protocol to support but=20
> optional for implementation depending use cases:
>=20
> 1. REQ-001 - implement SIP based protocol
[JRE] This is clearly stated as a requirement the mechanism and should rema=
in that way.

> 2. REQ-012  - metadata reporting support
[JRE] Ditto. Perhaps the words could be improved by saying "The mechanism M=
UST include a means for providing the SRS...."

> 3. REQ-013 - map between participant and  media=20
[JRE] "The mechanism MUST include a means for the SRS to be able to correla=
te..."

> 4. REQ-022 - wall clock reporting for media synchronization
[JRE] "The mechanism MUST include a means for the SRS to receive ..."

> 5. REQ-023 - wall clock, assuming pause/resume is used=20
[JRE] Similar

> 6. REQ 27-30 are mandatory security requirements
[JRE] REQ-027-029: "The mechanism MUST include a means for ensuring..."
I think REQ-030 is fine as is.

John (as individual)

>=20
> Leon
>=20
> -----Original Message-----
> From: Leon Portman=20
> Sent: Monday, March 28, 2011 10:39 AM
> To: 'Elwell, John'; Gonzalo Camarillo; siprec@ietf.org; Ken=20
> Rehor (krehor) (krehor@cisco.com)
> Subject: RE: [siprec] AD review: draft-ietf-siprec-req-08
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> > Sent: Wednesday, March 23, 2011 1:23 PM
> > To: siprec@ietf.org
> > Subject: [siprec] AD review: draft-ietf-siprec-req-08
> >=20
> > Hi,
> >=20
> > the SIPREC WG requested the publication of the following=20
> draft a few=20
> > days ago. Please, find below my AD review.
> >=20
> > https://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> >=20
> > Given that the draft contains both requirements and use=20
> cases, you may=20
> > want to edit the title so that it reads "Use Cases and Requirements=20
> > for ..."
> >=20
> > Typically, Section 1 contains the Introduction and Section 2 the=20
> > terminology. You may want to swap both sections.
> >=20
> > Most of the requirements are phrased so that they describe=20
> > capabilities that need to be supported by the system (e.g., the=20
> > mechanism MUST provide the SRS with the means to ...) but=20
> that do not=20
> > need to be necessarily used (e.g., a particular use case=20
> may not make=20
> > use of that functionality). However, some requirements are=20
> phrased so=20
> > that the functionality needs to be used (e.g., the mechanism MUST=20
> > provide the SRS the wall clock time ...). Requirements 12,=20
> 22, 23, 27,=20
> > 28, and 29 seem to fall into the latter category. Could you please=20
> > check whether that was the intention with all those requirements?
> >=20
> > A few requirements relate to the security and privacy related=20
> > properties of the SRC-SRS interface (e.g., requirements 24 and 29).
> > However, the draft does not discuss how the security and privacy of=20
> > that interface relate to the security and privacy level=20
> used for the=20
> > CS being recorded.
> > For example, can the confidentiality level of the media=20
> going from the=20
> > SRC and the SRS be lower than that of the media flowing between the=20
> > actual participants of the CS? If you decide there should not be a=20
> > requirement on this area, you need to at least discuss this issue=20
> > (probably in Sections 6 or 7).
> >=20
> > Once you address these comments, I will request the IETF-wide last=20
> > call for this draft.
> >=20
> > Thanks,
> >=20
> > Gonzalo
> >=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >=20
>=20

From partr@cisco.com  Tue Mar 29 01:28:56 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26FCB3A688A for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 01:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[AWL=0.560, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TSI7tWTkwZSE for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 01:28:54 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 1C77A3A6873 for <siprec@ietf.org>; Tue, 29 Mar 2011 01:28:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=2479; q=dns/txt; s=iport; t=1301387432; x=1302597032; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=GRfsE4fGwZYmBJ9gmQ1v2VJRU1JgJiPE2c6+gnM/pi8=; b=K0EuSJmmDM+6s0gZ5h2yLL2nhcZ/s6l1GM/2/VbA6u/5CuhyfnsNkArg AeYzmjzxnn+8LJdt3vNcZyrQ7DMhmKrAiwPQge4WYSUhc/calwJTFkorJ gh/kgb5VHswCKe541P1d5CoYP6tRwDhaSPHvyjNTEdObH4+r6SQiUkPh5 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au4AAISXkU2Q/khLgWdsb2JhbACYD403FAEBFiYlp0KcQ4VqBIU6iyI
X-IronPort-AV: E=Sophos;i="4.63,260,1299456000"; d="scan'208";a="23578165"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 29 Mar 2011 08:30:31 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2T8UTGI012963 for <siprec@ietf.org>; Tue, 29 Mar 2011 08:30:31 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Mar 2011 14:00:30 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Mar 2011 14:00:30 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhgBO/qTg
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 29 Mar 2011 08:30:30.0431 (UTC) FILETIME=[904DDAF0:01CBEDEB]
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 08:28:56 -0000

Charles,

Thanks for review the document. Please read inline.

Thanks
Partha=20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Charles Eckel (eckelcu)
Sent: Sunday, March 27, 2011 12:35 AM
To: siprec@ietf.org
Subject: [siprec] comments on draft-ram-siprec-metadata-04

I gave the draft and read and have the following comments.

Section 3. Think the metadata describes the recording session, not the
communication session. Replace "metamodel" with "metadata model", and
"MAY be conveyed in Recording Session" with "MAY be conveyed within the
Recording Session", and "time a change occurred by be assumed" with
"time a change occurred may be assumed".

Section 4, suggest rewording as, "The section describes each element of
the metadata model, and the attributes of each element. This section
also describes how the different elements are associated."

Section 4.1, RecordingRequestorID is not really an ID, it is more of a
type. I think RecordingRequestor is more appropriate.


<Partha>Agreed. We will update in the next revision </partha>

 That said, I think you also need a unique ID for the Recording Session,
right?
<partha>  Please clarify whether you are interested in AOR of RS or just
ID. In the model, Recording (1..*) is related to CSG (0..*) and there is
no need of separate attribute for unique id. In the metadata format, URN
UUID in CSG (group) & recording exist which helps to visualize the
association </partha>

Section 4.2.1, replace "SRC (or MAY be SRS)" with "SRC or SRS".
<Partha>Agreed. We will update in the next revision </partha>

Section 4.3.2, why does a CS need two participants or more? What about
studio mode recording?

Section 4.4.1, what is participant type and what is its use, or why
needed?
<partha> This attribute has to be removed as per the last interim
meeting. We will update in the next revision. </partha>

Section 4.5, I think Media Stream requires a unique ID attribute as
well.=20
<partha> As mentioned above in the model draft, the association between
CS and participant is shown. In terms of format draft, it is represented
by URN UUID </partha>
Is the "Media Stream Reference" the SDP label attribute?
<partha> Your understanding is correct </partha>


Thanks,
Charles



_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From partr@cisco.com  Tue Mar 29 01:48:32 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C1EB3A690E for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 01:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.05
X-Spam-Level: 
X-Spam-Status: No, score=-10.05 tagged_above=-999 required=5 tests=[AWL=0.549,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0pYfdq9BjwbO for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 01:48:30 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id B058A3A6930 for <siprec@ietf.org>; Tue, 29 Mar 2011 01:48:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=25920; q=dns/txt; s=iport; t=1301388607; x=1302598207; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=XfOvjO3wt8jcl/FUphSI6KgsDxR1YpAbtbZWAZyezbg=; b=IPHAIt6cQY4LqBv3ALiL7BtaMQ9ud8mivvr+LGQB9CryMuhItBl0IRpG J7b1h5QeqxlG5r22ElN7KNQbZcrJDluVgWL2Vzy+T6pOnPC6XiK/YYfTy XVWQurpCjBgEIRf2Zemu0eZJy/eXigBQTdJ5DulPcBcFEkTieN96zThHC I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au0AADCckU2Q/khNgWdsb2JhbACYD403FAEBCwsmJYh5nlicQoMPglsEhTqLIg
X-IronPort-AV: E=Sophos;i="4.63,260,1299456000"; d="scan'208";a="23582442"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 29 Mar 2011 08:50:05 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2T8o48W009150; Tue, 29 Mar 2011 08:50:04 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Mar 2011 14:20:04 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Mar 2011 14:20:03 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904DA23A5@XMB-BGL-411.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF3066@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsAAClqhQAAXOdEAADtUDkAAjidVAAABgrFAAAo/hIAAdpARgAAc8P9A=
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com> <E1CB F4C7095 A	3D4CAAAEAD 09		FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2B09@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED8E0@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E38202@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466C1B@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A623904DA218D@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA0875AF3066@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Leon Portman" <Leon.Portman@nice.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
X-OriginalArrivalTime: 29 Mar 2011 08:50:04.0038 (UTC) FILETIME=[4BD41260:01CBEDEE]
Cc: siprec@ietf.org
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 08:48:32 -0000

John,

I agree with you in case of media server participant sends "ringback"
media stream during the early dialog and later stage, the callee
participant sends actual stream of the session using another
offer/answer exchange. It is also possible that callee sends "ringback"
media stream  wherein there is no difference between early or regular
media in terms of metadata information.

Having said that, it "may" or "may not" be matter whether the devices of
the participant automatically creates the media stream or participant
actually creates media stream.

Thanks
Partha

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Tuesday, March 29, 2011 10:39 AM
To: Parthasarathi R (partr); Leon Portman; Charles Eckel (eckelcu);
Hutton, Andrew; Ram Mohan R (rmohanr)
Cc: siprec@ietf.org
Subject: RE: [siprec] Dialog state in the CS block of
metadatamodel[wasRE:Progressing the architecture document]

Partha,

I think the real distinction you wish to make is between media coming
from a particular participant (associated with the UAS) and media coming
from some other entity (e.g., media server). In my view the latter case,
if we choose to record it, comes from a different "participant". It has
nothing to do with whether it is deemed early or regular from a SIP
dialog perspective.

John (as individual)


> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 28 March 2011 17:53
> To: Leon Portman; Charles Eckel (eckelcu); Hutton, Andrew; Elwell,=20
> John; Ram Mohan R (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of=20
> metadatamodel[wasRE:Progressing the architecture document]
>
>
> The question of "session" state is raised in my mind mainly to=20
> distinguish between early media (Media before session establishment)=20
> from normal media. Without the information in SIPREC metadata, the=20
> early media will be associated with UAS participant's media stream.=20
> I'm interested in knowing whether SIPREC solution has to differentiate

> between early media from normal media.
>
> As per John below mail, there is no need to differentiate as per the=20
> current requirement. If most of the folks feel so, I'm fine with not=20
> including "session state" in metadata.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: Monday, March 28, 2011 7:16 PM
> To: Charles Eckel (eckelcu); Hutton, Andrew; Elwell, John;=20
> Parthasarathi R (partr); Ram Mohan R (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of=20
> metadatamodel[wasRE:Progressing the architecture document]
>
> Charles Hi
>
> Just to make clear, I don't think SRS should receive dialog level=20
> state events about all  CS dialogs. I think that we should to support=20
> reporting high level session events.
> I understand the complexity of that and Ok to keep it open or next=20
> phase extensions
>
> Leon
>
> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> Sent: Monday, March 28, 2011 3:35 PM
> To: Hutton, Andrew; Elwell, John; Leon Portman; Parthasarathi R=20
> (partr); Ram Mohan R (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of=20
> metadatamodel[wasRE:Progressing the architecture document]
>
> I agree with this approach. Hopefully Leon and others that saw the=20
> need for this state information can confirm if it works for them.
>
> Cheers,
> Charles
>
> > -----Original Message-----
> > From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> > Sent: Monday, March 28, 2011 9:13 AM
> > To: Elwell, John; Leon Portman; Charles Eckel (eckelcu);
> Parthasarathi
> R (partr); Ram Mohan R
> > (rmohanr)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture
> > document]
> >
> > Hi,
> >
> > The draft-ietf-siprec-architecture has from the very
> beginning listed
> dialog state as an example of
> > what would be included in metadata which is why I raised
> the question.
> >
> > However it is true to say this was put in the architecture document
> before we had firmed up the
> > requirements or starting any indepth work on metadata so I could
> accept that the architecture draft
> > simply got this wrong from the start and it maybe should be removed.
> We could of course take the view
> > that if dialog events are important then the SRS could subscribe to
> the dialog event package at the
> > SRC and SIPREC does not need to touch this.
> >
> > I don't think we can allow SIPREC metadata to extend as far as
> reporting everything that happens to
> > the CS including how it is linked to other CS's and what
> services are
> used on the CS (E.g. types of
> > transfer etc.). This would quickly get very difficult to
> define and we
> would probably fail.
> >
> > I would prefer to not report this state information in metadata than
> open up the possibility of adding
> > lots of complexity.
> >
> > Regards
> > Andy
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Elwell, John
> > > Sent: 27 March 2011 14:50
> > > To: Leon Portman; Charles Eckel (eckelcu); Parthasarathi
> R (partr);
> > > Ram Mohan R (rmohanr); Hutton, Andrew
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of=20
> > > metadatamodel[wasRE:Progressing the architecture document]
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > Sent: 27 March 2011 11:48
> > > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R=20
> > > > (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of=20
> > > > metadatamodel[wasRE:Progressing the architecture document]
> > > >
> > > > Charles Hi
> > > >
> > > > Yes, it will be good to discuss it face to face.
> > > >
> > > > Just little background for such requirements. Today, especially=20
> > > > for contact centers, it is important for SRS to capture the=20
> > > > information how long customer was waiting for agent to
> answer the
> > > > call, which party hang up, how long was the hold time,
> if it was
> > > > blind transfer or consultation transfer. This information=20
> > > > important both from quality management point of view
> and customer
> > > > experience point of view.
> > > [JRE] (as chair) I think the group needs to consider
> whether this is
>
> > > within scope. Looking at the requirements, we have:
> > > "REQ-012 The mechanism MUST provide the SRS with metadata
> describing
> > >    CSs that are being recorded, including the media being used and
> the
> > >    identities of parties involved."
> > > If we are not recording the session while the caller is
> waiting to
> > > be answered, it seems we perhaps don't have a requirement for=20
> > > metadata about that. This seems to be more about call detail=20
> > > recording (CDR) rather than session recording. We can by
> all means
> > > have this discussion, but I am concerned about scope creep.
> > >
> > > > It is important also from compliance point of view to detect if=20
> > > > somebody actually received the media stream or still was in=20
> > > > pending state or media stream was disconnected.
> > > [JRE] (as individual) I agree we should show a participant as=20
> > > receiving media only if the SRC believes media is actually being=20
> > > sent to that participant (even then, there can be no
> guarantee it is
>
> > > received, e.g., because NAT or firewall traversal isn't
> functioning
> > > properly, severe packet loss, speaker volume is muted,
> etc..). But I
>
> > > have doubts whether it is necessarily to try to account
> for periods
> > > when the SRC knows a participant is not receiving media
> by saying it
>
> > > is because of alerting, hold or whatever.
> > >
> > > John
> > >
> > >
> > > >
> > > > Leon
> > > >
> > > > -----Original Message-----
> > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > Sent: Sunday, March 27, 2011 11:35 AM
> > > > To: Leon Portman; Elwell, John; Parthasarathi R
> (partr); Ram Mohan
>
> > > > R (rmohanr); Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of=20
> > > > metadatamodel[wasRE:Progressing the architecture document]
> > > >
> > > > Hi Leon,
> > > >
> > > > Thank you for your patience in trying to explain this to me;=20
> > > > however, I still am not able to understand why the SRS
> might need
> > > > to know this information, or what it would do with it.
> > > > Is it that you need to know when a given participant
> was receiving
>
> > > > the recorded media and when it was not? If so, I do not think=20
> > > > dialog state is sufficient. Is there some other requirement or=20
> > > > functionality addressed by the SRS having such information?
> > > > Perhaps it is easier to discuss in person at the
> breakfast meeting
>
> > > > Wednesday or during the working group session.
> > > >
> > > > Cheers,
> > > > Charles
> > > >
> > > > > -----Original Message-----
> > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > Sent: Saturday, March 26, 2011 8:15 PM
> > > > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi
> > > R (partr);
> > > > Ram Mohan R (rmohanr); Hutton,
> > > > > Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > metadatamodel[wasRE:Progressing the architecture
> > > > > document]
> > > > >
> > > > > Charles Hi
> > > > >
> > > > > Without participant session state, SRS will know only when
> > > > participant
> > > > is part of the session and will
> > > > > not know about intermediate states like ringing, retrying etc.
> > > > > I know that we have media stream information per
> > > participant but not
> > > > sure that it is enough.
> > > > >
> > > > > Leon
> > > > > -----Original Message-----
> > > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > > Sent: Saturday, March 26, 2011 9:07 PM
> > > > > To: Leon Portman; Elwell, John; Parthasarathi R (partr);
> > > Ram Mohan R
> > > > (rmohanr); Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > metadatamodel
> > > > [wasRE:Progressing the
> > > > > architecture document]
> > > > >
> > > > > Hi Leon,
> > > > >
> > > > > I am still having a hard time understanding why we need
> > > the session
> > > > state information per CS
> > > > > participant? Why is this required, who uses it, and how?
> > > > >
> > > > > Thanks,
> > > > > Charles
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On
> > > > > Behalf Of Leon Portman
> > > > > > Sent: Saturday, March 26, 2011 10:31 AM
> > > > > > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R
> > > (rmohanr);
> > > > > Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: Re: [siprec] Dialog state in the CS block of
> > > > metadatamodel
> > > > > [wasRE:Progressing the
> > > > > > architecture document]
> > > > > >
> > > > > > John Hello
> > > > > >
> > > > > > I agree that SRS (and its application clients) interested
> > > > in SESSION
> > > > > level events and not underlying
> > > > > > DIALOG events. However we do need to support reporting
> > > > session state
> > > > > information per CS  participant
> > > > > > that sometimes equals to dialog level and sometimes not.
> > > > > >
> > > > > > We could have define more application level state
> events like
> > > > instead
> > > > > of TRYING - > RINGING etc.
> > > > > > However they could be domain specific.
> > > > > >
> > > > > > Leon
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Elwell, John
> [mailto:john.elwell@siemens-enterprise.com]
> > > > > > Sent: Thursday, March 24, 2011 6:34 PM
> > > > > > To: Parthasarathi R (partr); Ram Mohan R (rmohanr);
> > > Leon Portman;
> > > > > Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > metadata model
> > > > > [wasRE:Progressing the
> > > > > > architecture document]
> > > > > >
> > > > > > This discussion gives me some concerns, echoing to some
> > > > extent what
> > > > > Ram is saying.
> > > > > >
> > > > > > SIPREC is about session recording, where a session is the
> > > > information
> > > > > exchanged between participants
> > > > > > in a CS (the media streams) plus metadata. The
> metadata should
> > > > provide
> > > > > additional information about
> > > > > > the CS. This means information about the communication
> > > > SESSION, not
> > > > > about the SIP dialog that is used
> > > > > > to control that session. With this in mind, consider
> > > the following
> > > > > points, some of which have already
> > > > > > been raised:
> > > > > >
> > > > > > 1. There may be more than one SIP dialog involved if the
> > > > SRC is at a
> > > > > B2BUA or conference focus.
> > > > > >
> > > > > > 2. Does the CS necessarily need to be controlled by SIP? For
> > > > example,
> > > > > it could be a PSTN call, an RTC-
> > > > > > Web call or a Jingle call. None of these preclude using
> > > > SIP for the
> > > > RS
> > > > > (that is what the charter of
> > > > > > SIPREC is all about - a SIP-based RS).
> > > > > >
> > > > > > 3. Somebody retrieving and playing back a recorded
> CS will be
> > > > > interested in session-related events
> > > > > > like participants leaving and joining (including the first
> > > > > participants joining at the start of the CS
> > > > > > and the last participants leaving a the end of the
> CS), media
> > > > streams
> > > > > starting and ending and
> > > > > > participants starting or stopping receipt of a media stream.
> In
> > > > other
> > > > > words, changes of SESSION state,
> > > > > > not dialog state.
> > > > > >
> > > > > > 4. Some of the SIP dialog states just don't seem
> relevant. The
> > > > > distinction between early dialog and
> > > > > > full dialog in SIP does not necessarily corresponding to any
> > > > > meaningful state change of the session.
> > > > > > For example, A makes a call to B and B answers and
> > > starts sending
> > > > > media. A receives and renders media
> > > > > > (perhaps it has already received SDP answer, allowing
> > > it to verify
> > > > the
> > > > > source of the media). Then A
> > > > > > receives the 200 OK (transitioning from an early dialog
> > > to a full
> > > > > dialog) and continues to receive
> > > > > > media. So although there is a dialog state change, there is
> not
> > > > really
> > > > > a session state change.
> > > > > >
> > > > > > The bit about dialog state in the architecture
> draft is, in my
> > > > > opinion, a legacy from some earlier
> > > > > > discussions, before we started having the metadata
> > > discussions. I
> > > > > think the metadata discussions have
> > > > > > taken us in the right direction.
> > > > > >
> > > > > > John (as individual)
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: siprec-bounces@ietf.org=20
> > > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of
> Parthasarathi
> R
> > > > > (partr)
> > > > > > > Sent: 24 March 2011 02:36
> > > > > > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: Re: [siprec] Dialog state in the CS block of
> metadata
> > > > model
> > > > > > > [wasRE:Progressing the architecture document]
> > > > > > >
> > > > > > > Ram,
> > > > > > >
> > > > > > > Please read inline.
> > > > > > >
> > > > > > > Thanks
> > > > > > > Partha
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > > From: Ram Mohan R (rmohanr)
> > > > > > > Sent: Wed 3/23/2011 7:59 PM
> > > > > > > To: Parthasarathi R (partr); Leon Portman; Hutton, Andrew
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: RE: [siprec] Dialog state in the CS block of
> metadata
> > > > model
> > > > > > > [wasRE:Progressing the architecture document]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I am still trying to understand what is the
> > > significance of this
> > > > > > > attribute w.r.t CS. Are we saying the attribute represents
> the
> > > > state
> > > > > > > of CS ?
> > > > > > >
> > > > > > > Note that CS need not be one dialog.
> > > > > > >
> > > > > > > <Partha>  The attribute is to show the state of CS
> > > > only. As it is
> > > > > not
> > > > > > > single dialog, I have mentioned as session state attribute
> > > > </Partha>
> > > > > > >
> > > > > > > For cases like Conference where there may be different
> > > > participants,
> > > > > > > if SRC happens to be Focus how do you derive/what is
> "session
> > > > state"
> > > > > ?
> > > > > > >
> > > > > > > <Partha> I really don't know whether it is generic. My
> thought
> > > > > > > processing of session state for conference is as follows:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 1) First participant of conference early media (ivr
> > > play) may be
> > > > > > > considered as "early" state of session.
> > > > > > >
> > > > > > > 2) The session state is chaged to confirmed in case any
> > > > one of the
> > > > > > > participant joined in the conference.
> > > > > > >
> > > > > > > 3) The session state is move to terminated when the last
> > > > participant
> > > > > > > moved out of the conference.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Please let me know in case other way to represent the
> session
> > > > state
> > > > > of
> > > > > > > conference </partha>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > For cases where B2BUA acts as SRC what is
> "session state" ?
> > > > > > >
> > > > > > > <partha> It looks straight forward for me. In B2BUA case ,
> > > > > > >
> > > > > > > 1) The stage where in two party is not connected, it is
> > > > considered
> > > > > as
> > > > > > > early state.
> > > > > > >
> > > > > > > 2) when both are connected, it is confirmed state
> > > > > > >
> > > > > > > 3) In case of BYE received from any one of the party,
> > > then CS is
> > > > > > > considered as terminated state
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Please note that this is applicable for 3PCC as well.
> > > > </partha>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Ram
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From: siprec-bounces@ietf.org=20
> > > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of
> Parthasarathi
> R
> > > > > (partr)
> > > > > > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > > > > > To: Leon Portman; Hutton, Andrew
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: Re: [siprec] Dialog state in the CS block of
> metadata
> > > > model
> > > > > > > [wasRE:Progressing the architecture document]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Leon,
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Shall we have optional "event" attribute to indicate the
> state
> > > > > change
> > > > > > > which is similar to "event" attribute in RFC 4235.
> > > The "event"
> > > > will
> > > > > > > include the following:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 1) cancelled
> > > > > > >
> > > > > > > 2) rejected
> > > > > > >
> > > > > > > 3) replaced
> > > > > > >
> > > > > > > 4) bye
> > > > > > >
> > > > > > > 5) error
> > > > > > >
> > > > > > > 6) timeout
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Partha
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > > Sent: Tue 3/22/2011 9:37 PM
> > > > > > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: RE: Dialog state in the CS block of metadata
> > > model [was
> > > > > > > RE:Progressing the architecture document]
> > > > > > >
> > > > > > > It can be either application level error or dialog
> > > > level errors -
> > > > > like
> > > > > > > timeout or failures.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Leon
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From: Hutton, Andrew
> > > > [mailto:andrew.hutton@siemens-enterprise.com]
> > > > > > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > > > > > To: Leon Portman; Parthasarathi R (partr)
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: RE: Dialog state in the CS block of metadata
> > > model [was
> > > > RE:
> > > > > > > Progressing the architecture document]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > What would it be used for?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Regards
> > > > > > >
> > > > > > > Andy
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > >   From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > >   Sent: 22 March 2011 14:11
> > > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > > >   Cc: siprec@ietf.org
> > > > > > >   Subject: RE: Dialog state in the CS block of metadata
> > > > model [was
> > > > > RE:
> > > > > > > Progressing the architecture document]
> > > > > > >
> > > > > > >   Should we have error state as well?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   Leon
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   From: siprec-bounces@ietf.org=20
> > > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of
> Parthasarathi
> R
> > > > > (partr)
> > > > > > >   Sent: Tuesday, March 22, 2011 3:33 PM
> > > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > > >   Cc: siprec@ietf.org
> > > > > > >   Subject: [siprec] Dialog state in the CS block of
> > > > metadata model
> > > > > [was
> > > > > > > RE: Progressing the architecture document]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   The architecture document proposes to have
> > > > dialog/session state
> > > > > in
> > > > > > > Metadata model. To achieve this, "session state"
> > > > attribute has to
> > > > be
> > > > > > > added in the CS block of Metadata model. The possible
> > > values for
> > > > > > > session state are
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   1) Trying
> > > > > > >
> > > > > > >   2) Proceeding
> > > > > > >
> > > > > > >   3) Early
> > > > > > >
> > > > > > >   4) Confirmed
> > > > > > >
> > > > > > >   5) Terminated
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   Please let me know in case any objection to add
> > > this attribute
> > > > > in
> > > > > > > Metadata model.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >   Thanks
> > > > > > >
> > > > > > >   Partha
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > >   From: Parthasarathi R (partr)
> > > > > > >   Sent: Wednesday, March 16, 2011 5:40 AM
> > > > > > >   To: Hutton, Andrew
> > > > > > >   Cc: Elwell, John; siprec@ietf.org
> > > > > > >   Subject: RE: Progressing the architecture document
> > > > > > >
> > > > > > >   > -----Original Message-----
> > > > > > >   > From: siprec-bounces@ietf.org
> > > > > > >   > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > > > Parthasarathi R
> > > > > > > (partr)
> > > > > > >   > Sent: 14 March 2011 17:05
> > > > > > >   > To: Elwell, John; siprec@ietf.org
> > > > > > >   > Subject: Re: [siprec] Progressing the
> > > architecture document
> > > > > > >
> > > > > > >   >
> > > > > > >   > Sec 4.3.1 whether 3rd bullet is required?
> > > > > > >   >
> > > > > > >
> > > > > > >   [AndyH]I assume it is as for example I assume
> it would be
> > > > > necessary
> > > > > > > to record early-media and update the SRS when the
> > > dialog changes
> > > > to
> > > > > > > the confirmed or terminated state. Does not seem to be in
> the
> > > > > metadata
> > > > > > > draft though. In the end I will either remove
> these bullets
> or
> > > > align
> > > > > > > with the metadata draft.
> > > > > > >   <Partha> It is a good point. Dialog state shall be
> > > > added as one
> > > > > of
> > > > > > > the optional attribute in CS metadata block with
> > > > default value as
> > > > > > > mid-dialog. This helps to differentiate between
> early dialog
> > > > > > > (ringback) vs mid-dialog (normal
> > > > > > > conversation) in recording. In case of no
> objection for this
> > > > > attribute
> > > > > > > in metadata model, we will add it. We will work
> out metadata
> > > > format
> > > > > > > once the consensus occurs for metadata model.
> > > > > > > In case required, we will span separate mail thread to
> > > > close this
> > > > > > > issue </Partha>
> > > > > > >
> > > > > > >
> > > > > > _______________________________________________
> > > > > > siprec mailing list
> > > > > > siprec@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/siprec
> > > >
> > >
>

From Leon.Portman@nice.com  Tue Mar 29 04:20:25 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB2F13A693E for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 04:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level: 
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZIMzbj29yO7u for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 04:20:24 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by core3.amsl.com (Postfix) with ESMTP id E63D53A681B for <siprec@ietf.org>; Tue, 29 Mar 2011 04:20:23 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Tue, 29 Mar 2011 13:22:01 +0200
From: Leon Portman <Leon.Portman@nice.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Tue, 29 Mar 2011 13:21:58 +0200
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: AcvlaWIIK70D67ErTdeQ754hs4iSUgAErWSwAejioLAAOOO58A==
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com>
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Multiplexing different participants' streams on the	same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 11:20:25 -0000

I like it.=20

Quick question. In metadata we are using "<aor>" attribute but in SDP, it i=
s "CNAME"? Can we use the same?

Leon



-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Parthasarathi R (partr)
Sent: Monday, March 28, 2011 10:42 AM
To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat); siprec@ietf.org
Subject: Re: [siprec] Multiplexing different participants' streams on the s=
ame port

Charles,

IMO, the current metadata model helps to address RTP MUX streams as well. I=
n terms of model, multiple participants (P1, P2, P3) metadata block points =
to the single stream (S1) and stream block contains SSRC & CSRC information=
. IOW, SIPREC model abstract RTP MUX stream within media stream block.  Ple=
ase let me know in case you feel that model does not address it.

In case of metadata format, multiple "participant" elements have send eleme=
nt with single stream element. The stream element has a label attribute whi=
ch points to the m-line which contains "ssrc" attribute with CNAME paramete=
r. I attached the example for your reference and The example is the one of =
the way to represent RTP-MUX stream in the metadata format. Please let me k=
now the issues with this format and example.

I agree with Paul and you that we need to understand how RTP mux stream wil=
l be standardized but IMO, it is not the limiting factor for SIPREC as of n=
ow.

Thanks
Partha

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Charles Eckel (eckelcu)
Sent: Friday, March 18, 2011 8:40 PM
To: Paul Kyzivat (pkyzivat); siprec@ietf.org
Subject: Re: [siprec] Multiplexing different participants' streams on thesa=
me port

I agree with the comment regarding CLUE, so let me take a simpler example, =
and audio mixer. This mixer may mix the audio from multiple participants.

Participant 1 (P1)
Participant 2 (P2)
Participant 3 (P3)

P1 sends audio stream with SSRC-P1
P2 sends audio stream with SSCR-P2
P2 sends audio stream with SSCR-P3

MixerA(Ma)

Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
The SRC sends this stream to the SRS for recording. I suspect it might chan=
ge the SSRC to be SSRC-SRC but maintain the CSRC information identifying P1=
/P2/P3.
I expect this would be modeled as a single stream with 3 participants P1, P=
2, P3. The mapping of P1 to SSRC-P1 is captured in the RTCP data sent by SR=
C to SRS. In this case, there is no need to anything in the metadata.
However, if the CSRCs are not propagated all the way to the SRS, then perha=
ps participant info would need to be communicated via the metadata.

Note, I do not pretend to have this all figured out; rather, I am putting o=
ut some ideas to see if this gels with what others have in mind.

Cheers,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Paul Kyzivat (pkyzivat)
> Sent: Friday, March 18, 2011 5:38 AM
> To: siprec@ietf.org
> Subject: Re: [siprec] Multiplexing different participants' streams on
the same port
>=20
> I don't know if this is a good idea or not. But if we want to consider

> it, then we should probably enter into some discussion with CLUE, to
see
> if there is any commonality.
>=20
> Over in CLUE, this mixing of multiple streams over one RTP session has

> been brought up because it is a technique used in existing proprietary

> products. But the CLUE wg isn't yet to a point where it is ready to=20
> decide if this will be a requirement. And the AVT people have strong=20
> opinions on what is/isn't appropriate.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/18/2011 4:11 AM, Elwell, John wrote:
> > Something Charles mentioned in another thread triggered me to raise
this.
> >
> > We consider different participants in the CS as potentially
producing separate media streams that
> the SRC sends to the SRS, where the SRC can send them mixed or
unmixed.
> >
> > When sending them unmixed, up till now I think we have considered
sending them to separate ports on
> the SRS and identifying them as separate m=3D lines in the SDP. Another
possibility might be to
> multiplex the different streams on the same port and identify them by
different SSRC values. I am not
> sure whether this would be a correct use of SSRC, and I suspect we
would need to check with AVTCORE.
> Recent discussions in other contexts (telepresence, RTC-Web) have also
drawn my attention to such
> possibilities. See also
https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
> >
> > Of course, it would mean that we would have to rethink how we
reference the different streams from
> metadata.
> >
> > I am not necessarily proposing such a change - I just want to make
sure we have given it due
> consideration.
> >
> > John (as individual)
> >
> >
> > _______________________________________________
> > 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

From john.elwell@siemens-enterprise.com  Tue Mar 29 04:26:49 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63F5C28C0EE for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 04:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UAASzacZdHb6 for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 04:26:48 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 01A733A67C2 for <siprec@ietf.org>; Tue, 29 Mar 2011 04:26:47 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3923172 for siprec@ietf.org; Tue, 29 Mar 2011 13:28:24 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id C85F123F0290 for <siprec@ietf.org>; Tue, 29 Mar 2011 13:28:24 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Tue, 29 Mar 2011 13:28:25 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Tue, 29 Mar 2011 13:28:23 +0200
Thread-Topic: Multiplexing different participants' streams on the same port
Thread-Index: AcvlRBLrSWbjqO+eTN2hm6ZyFiLojwIvtrtw
Message-ID: <A444A0F8084434499206E78C106220CA0875AF329C@MCHP058A.global-ad.net>
Keywords: SIPREC
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 11:26:49 -0000

I would like to revive this discussion. I had a chat with a couple of RTP e=
xperts (Colin Perkins, Magnus Westerlund), and they felt that the more natu=
ral way of sending to an SRS streams of the same medium on behalf of two or=
 more parties would be to send them on the same port with different SSRC va=
lues. This means we would need to get from a participant-stream in the meta=
data model to an SSRC value. There may be different possibilities here (e.g=
., metadata contains CNAME as well as label, and SDP media description cont=
ains CNAME to SSRC mapping). There are SDP extensions that might help here,=
 which I won't try to go in to here.

Multiplexing different parties on the same port, rather than additional por=
ts, has the benefit of port saving, which might be an issue for the SRS (wh=
ich already has to provide sufficient ports for multiple recording sessions=
 and multiple media on those sessions). It might also be an issue for NATs.=
 Reducing the number of ports would also reduce the amount of ICE processin=
g, if ICE is used.

Likewise RTP-RTCP multiplexing would achieve benefits.

I would like to visit this briefly in the SIPREC session on Thursday, under=
 the protocol discussion.

John (as chair)

> -----Original Message-----
> From: Elwell, John=20
> Sent: 18 March 2011 08:11
> To: siprec@ietf.org
> Subject: Multiplexing different participants' streams on the same port
>=20
> Something Charles mentioned in another thread triggered me to=20
> raise this.
>=20
> We consider different participants in the CS as potentially=20
> producing separate media streams that the SRC sends to the=20
> SRS, where the SRC can send them mixed or unmixed.
>=20
> When sending them unmixed, up till now I think we have=20
> considered sending them to separate ports on the SRS and=20
> identifying them as separate m=3D lines in the SDP. Another=20
> possibility might be to multiplex the different streams on=20
> the same port and identify them by different SSRC values. I=20
> am not sure whether this would be a correct use of SSRC, and=20
> I suspect we would need to check with AVTCORE. Recent=20
> discussions in other contexts (telepresence, RTC-Web) have=20
> also drawn my attention to such possibilities. See also=20
> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
>=20
> Of course, it would mean that we would have to rethink how we=20
> reference the different streams from metadata.
>=20
> I am not necessarily proposing such a change - I just want to=20
> make sure we have given it due consideration.
>=20
> John (as individual)
>=20
>  =

From pkyzivat@cisco.com  Tue Mar 29 05:21:51 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8D753A6783 for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 05:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2kTU4vyYmKN for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 05:21:50 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id E147E3A67B6 for <siprec@ietf.org>; Tue, 29 Mar 2011 05:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=6213; q=dns/txt; s=iport; t=1301401408; x=1302611008; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=iFHdXLze6XJ8RsY4H2XLNkAXAurBgO9Nob5G5T1dGho=; b=d+ER+syKEkNq95fEHO1SXyJNJuVYnO2EFZKFAFxrdMdggeaStuy8y+jz wxgDPhreKD5V2BxAvp25BlmiW+18gV6vXNJF3l4wIgl3ncMPcY9yz7zaH FYtv0tyVDyDeQ8TKDgIYJp5rrsHB7bBodQqpDv5y23ZHbbVxO+ks+Gqrt k=;
X-IronPort-AV: E=Sophos;i="4.63,262,1299456000"; d="scan'208";a="23628117"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 29 Mar 2011 12:23:27 +0000
Received: from [10.61.85.87] (ams3-vpn-dhcp5464.cisco.com [10.61.85.87]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2TCNRp8021549; Tue, 29 Mar 2011 12:23:27 GMT
Message-ID: <4D91CF3F.1010809@cisco.com>
Date: Tue, 29 Mar 2011 08:23:27 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Leon Portman <Leon.Portman@nice.com>
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com>	<E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 12:21:51 -0000

On 3/29/2011 7:21 AM, Leon Portman wrote:
> I like it.
>
> Quick question. In metadata we are using "<aor>" attribute but in SDP, it is "CNAME"? Can we use the same?

Charles knows more than I about RTP. AFAIK CNAME is an essentially 
arbitrary string that is assigned by the media source. (Are their 
constraints on its length or format?) Perhaps it could be formatted as a 
sip AOR, perhaps not. Even if it *could*, in practice *will* it be? ISTM 
it would not be wise to count on these being the same.

We should probably allow participants to specify their cname as well as 
their AOR. This may get complicated if the same participant ends up with 
differing media streams it sends.

I also wonder if the SRC will always know the CNAMEs of the streams. I 
suspect we can't count on that.

	Thanks,
	Paul

> Leon
>
>
>
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of Parthasarathi R (partr)
> Sent: Monday, March 28, 2011 10:42 AM
> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat); siprec@ietf.org
> Subject: Re: [siprec] Multiplexing different participants' streams on the same port
>
> Charles,
>
> IMO, the current metadata model helps to address RTP MUX streams as well. In terms of model, multiple participants (P1, P2, P3) metadata block points to the single stream (S1) and stream block contains SSRC&  CSRC information. IOW, SIPREC model abstract RTP MUX stream within media stream block.  Please let me know in case you feel that model does not address it.
>
> In case of metadata format, multiple "participant" elements have send element with single stream element. The stream element has a label attribute which points to the m-line which contains "ssrc" attribute with CNAME parameter. I attached the example for your reference and The example is the one of the way to represent RTP-MUX stream in the metadata format. Please let me know the issues with this format and example.
>
> I agree with Paul and you that we need to understand how RTP mux stream will be standardized but IMO, it is not the limiting factor for SIPREC as of now.
>
> Thanks
> Partha
>
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel (eckelcu)
> Sent: Friday, March 18, 2011 8:40 PM
> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
> Subject: Re: [siprec] Multiplexing different participants' streams on thesame port
>
> I agree with the comment regarding CLUE, so let me take a simpler example, and audio mixer. This mixer may mix the audio from multiple participants.
>
> Participant 1 (P1)
> Participant 2 (P2)
> Participant 3 (P3)
>
> P1 sends audio stream with SSRC-P1
> P2 sends audio stream with SSCR-P2
> P2 sends audio stream with SSCR-P3
>
> MixerA(Ma)
>
> Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
> SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
> The SRC sends this stream to the SRS for recording. I suspect it might change the SSRC to be SSRC-SRC but maintain the CSRC information identifying P1/P2/P3.
> I expect this would be modeled as a single stream with 3 participants P1, P2, P3. The mapping of P1 to SSRC-P1 is captured in the RTCP data sent by SRC to SRS. In this case, there is no need to anything in the metadata.
> However, if the CSRCs are not propagated all the way to the SRS, then perhaps participant info would need to be communicated via the metadata.
>
> Note, I do not pretend to have this all figured out; rather, I am putting out some ideas to see if this gels with what others have in mind.
>
> Cheers,
> Charles
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Paul Kyzivat (pkyzivat)
>> Sent: Friday, March 18, 2011 5:38 AM
>> To: siprec@ietf.org
>> Subject: Re: [siprec] Multiplexing different participants' streams on
> the same port
>>
>> I don't know if this is a good idea or not. But if we want to consider
>
>> it, then we should probably enter into some discussion with CLUE, to
> see
>> if there is any commonality.
>>
>> Over in CLUE, this mixing of multiple streams over one RTP session has
>
>> been brought up because it is a technique used in existing proprietary
>
>> products. But the CLUE wg isn't yet to a point where it is ready to
>> decide if this will be a requirement. And the AVT people have strong
>> opinions on what is/isn't appropriate.
>>
>> 	Thanks,
>> 	Paul
>>
>> On 3/18/2011 4:11 AM, Elwell, John wrote:
>>> Something Charles mentioned in another thread triggered me to raise
> this.
>>>
>>> We consider different participants in the CS as potentially
> producing separate media streams that
>> the SRC sends to the SRS, where the SRC can send them mixed or
> unmixed.
>>>
>>> When sending them unmixed, up till now I think we have considered
> sending them to separate ports on
>> the SRS and identifying them as separate m= lines in the SDP. Another
> possibility might be to
>> multiplex the different streams on the same port and identify them by
> different SSRC values. I am not
>> sure whether this would be a correct use of SSRC, and I suspect we
> would need to check with AVTCORE.
>> Recent discussions in other contexts (telepresence, RTC-Web) have also
> drawn my attention to such
>> possibilities. See also
> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
>>>
>>> Of course, it would mean that we would have to rethink how we
> reference the different streams from
>> metadata.
>>>
>>> I am not necessarily proposing such a change - I just want to make
> sure we have given it due
>> consideration.
>>>
>>> John (as individual)
>>>
>>>
>>> _______________________________________________
>>> 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
>

From pkyzivat@cisco.com  Tue Mar 29 05:24:49 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC3E83A6784 for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 05:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOQOsGcWL55C for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 05:24:45 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 2FD083A67A8 for <siprec@ietf.org>; Tue, 29 Mar 2011 05:24:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=2960; q=dns/txt; s=iport; t=1301401583; x=1302611183; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=2UeknAo6Q1P4hryGHgtJjlEq/z8hDo5yP58t3p5sb7Y=; b=DnqcFHHUIFOIUUdwN1B7LxY3Hh+7osivW12NZCUFEkgteG0/5tDUt3fX o7bMjx41kDE1AWnGR0sL9Rm8uqhdtY9KcDids/ITLkBoTFj8Vlvkvo2Py /cJav9EtoFUbkaEiahee+xWbLnYrmx1zlp6C2IF1jKlOlLeQL3Nk7t7Ev I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIHAD7PkU2Q/khLgWdsb2JhbACYTox3FAEBFiYlqF2cS4J8gm4EjQKDVA
X-IronPort-AV: E=Sophos;i="4.63,262,1299456000"; d="scan'208";a="81290694"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 29 Mar 2011 12:26:21 +0000
Received: from [10.61.85.87] (ams3-vpn-dhcp5464.cisco.com [10.61.85.87]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2TCQKgo026171 for <siprec@ietf.org>; Tue, 29 Mar 2011 12:26:20 GMT
Message-ID: <4D91CFEC.8060808@cisco.com>
Date: Tue, 29 Mar 2011 08:26:20 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: siprec@ietf.org
References: <A444A0F8084434499206E78C106220CA0875AF329C@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF329C@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 12:24:49 -0000

John,

ISTM that we could *allow* this, but that we should not require that the 
SRC do it this way. (It may not have enough control to do it that way.)

	Thanks,
	Paul

On 3/29/2011 7:28 AM, Elwell, John wrote:
> I would like to revive this discussion. I had a chat with a couple of RTP experts (Colin Perkins, Magnus Westerlund), and they felt that the more natural way of sending to an SRS streams of the same medium on behalf of two or more parties would be to send them on the same port with different SSRC values. This means we would need to get from a participant-stream in the metadata model to an SSRC value. There may be different possibilities here (e.g., metadata contains CNAME as well as label, and SDP media description contains CNAME to SSRC mapping). There are SDP extensions that might help here, which I won't try to go in to here.
>
> Multiplexing different parties on the same port, rather than additional ports, has the benefit of port saving, which might be an issue for the SRS (which already has to provide sufficient ports for multiple recording sessions and multiple media on those sessions). It might also be an issue for NATs. Reducing the number of ports would also reduce the amount of ICE processing, if ICE is used.
>
> Likewise RTP-RTCP multiplexing would achieve benefits.
>
> I would like to visit this briefly in the SIPREC session on Thursday, under the protocol discussion.
>
> John (as chair)
>
>> -----Original Message-----
>> From: Elwell, John
>> Sent: 18 March 2011 08:11
>> To: siprec@ietf.org
>> Subject: Multiplexing different participants' streams on the same port
>>
>> Something Charles mentioned in another thread triggered me to
>> raise this.
>>
>> We consider different participants in the CS as potentially
>> producing separate media streams that the SRC sends to the
>> SRS, where the SRC can send them mixed or unmixed.
>>
>> When sending them unmixed, up till now I think we have
>> considered sending them to separate ports on the SRS and
>> identifying them as separate m= lines in the SDP. Another
>> possibility might be to multiplex the different streams on
>> the same port and identify them by different SSRC values. I
>> am not sure whether this would be a correct use of SSRC, and
>> I suspect we would need to check with AVTCORE. Recent
>> discussions in other contexts (telepresence, RTC-Web) have
>> also drawn my attention to such possibilities. See also
>> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
>>
>> Of course, it would mean that we would have to rethink how we
>> reference the different streams from metadata.
>>
>> I am not necessarily proposing such a change - I just want to
>> make sure we have given it due consideration.
>>
>> John (as individual)
>>
>>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>

From john.elwell@siemens-enterprise.com  Tue Mar 29 05:44:57 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06DF43A67F0 for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 05:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pq1hZw6kMvBy for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 05:44:56 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id F29A43A67DB for <siprec@ietf.org>; Tue, 29 Mar 2011 05:44:55 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3915135 for siprec@ietf.org; Tue, 29 Mar 2011 14:46:17 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 22FB41EB82AE for <siprec@ietf.org>; Tue, 29 Mar 2011 14:46:17 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 29 Mar 2011 14:46:17 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Tue, 29 Mar 2011 14:46:15 +0200
Thread-Topic: Updated agenda / presentations
Thread-Index: AcvuD0qhFj2KuR+MREeIifet8EIyjA==
Message-ID: <A444A0F8084434499206E78C106220CA0875AF3320@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] Updated agenda / presentations
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 12:44:57 -0000

The agenda has been updated slightly and presentations are now uploaded.

John

 =

From partr@cisco.com  Tue Mar 29 07:01:27 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF4993A63D2 for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 07:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.07
X-Spam-Level: 
X-Spam-Status: No, score=-10.07 tagged_above=-999 required=5 tests=[AWL=0.529,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6dzpk1lof3AM for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 07:01:26 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 83BB03A6803 for <siprec@ietf.org>; Tue, 29 Mar 2011 07:01:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=2938; q=dns/txt; s=iport; t=1301407385; x=1302616985; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=cdoG1dWa61yN8yMALlDSZDQ7TwhSNPHiIb/EPTXDPwk=; b=cLz4Onk4O5TPCOAJAjVGALavUsGoLw9HyZEghl7cY2IlQPyqGQMW8hd9 mLYSwlNajUmkCjSGAMjB3U6UGXJWk4IvD1cqmzP4kLjIHkTVHkn389kyn nz88au7CpTibQzfCEaRSpfLNXu2G4D8lUSnQdQjbRJ2asnnH3QB97W4ei U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYAAAnmkU2Q/khLgWdsb2JhbACYEI09FAEBFiYlqGCcQ4J8gm4EhTqLIg
X-IronPort-AV: E=Sophos;i="4.63,262,1299456000"; d="scan'208";a="23643997"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 29 Mar 2011 14:03:04 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2TE33ee000909; Tue, 29 Mar 2011 14:03:03 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Mar 2011 19:33:03 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Mar 2011 19:33:01 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904E97306@XMB-BGL-411.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA086AA5598B@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Meeting materials for SIPREC session 2011-03-3109.00-11.30 GMT+2
Thread-Index: Acvq1eFpVXiqB59KSnuEuF+DouC05wDNVlyQ
References: <A444A0F8084434499206E78C106220CA086AA5598B@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 29 Mar 2011 14:03:03.0181 (UTC) FILETIME=[0511E3D0:01CBEE1A]
Subject: Re: [siprec] Meeting materials for SIPREC session 2011-03-3109.00-11.30 GMT+2
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 14:01:28 -0000

John,

Thanks for your comments. Please read inline.

Thanks
Partha=20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Elwell, John
Sent: Friday, March 25, 2011 3:48 PM
To: siprec@ietf.org
Subject: [siprec] Meeting materials for SIPREC session
2011-03-3109.00-11.30 GMT+2

Slides for metadata model and metadata format have already been uploaded
to the meeting materials repository:
https://datatracker.ietf.org/meeting/80/materials.html

Thanks to Partha for supplying these in good time.

1. Will other presenters please provide their slides a.s.a.p, or by
Monday latest, so that the chairs can review them for making best use of
meeting time? In particular, if we need a slot on Requirements, for
addressing AD comments, would Leon/Ken please let me have the slides
a.s.a.p.?

2. Concerning the metadata model slides, we must focus on open issues. I
see several open issues listed in the slides, but no further information
on these issues.
<Partha> In each of the slide, I have added "optional start/stop timer"
attribute as an open item because this attribute comes into picture
while we designing metadata format. Let us  identify the possible
metadata blocks not to have "start/stop" time attribute </partha>

 Would Partha please give consideration to expanding on the open issues,
by including either:
- a proposed resolution; or
- pros and cons if there are several ways forward.

3. Concerning the metadata format slides, the first 16 slides are all
tutorial - we should focus on open issues and next steps, so depending
on time availability the chairs might ask to skip a lot of this.
<partha> Agreed. As you mentioned, the basic idea is to give the
background & rationale behind the current format. I will run through
this slide in case time permits </partha>

Concerning the open issue on slide 19, I think this needs to be made
slightly clearer. My understanding was that the possibility of
multiplexing on the same port was mentioned as something to be
considered (and possibly ruled out), whereas the slide seems to assume
we will be doing that and asks how to represent it in the metadata.
<partha> As you mentioned in the recent mail, we will explore the way to
represent multiplexed stream in metadata format  </partha>
 I guess the issue is primarily one for the protocol milestone, and will
impact that metadata model if that is the way the protocol discussions
go.=20
<partha> metadata model accommodates as codec parameter attribute. The
open issue is how to represent in the metadata format </partha>
So perhaps it doesn't make sense to discuss this until the protocol
discussions have taken place - currently that is later in the agenda.

John (as chair)



_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From eckelcu@cisco.com  Tue Mar 29 07:20:32 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3445A3A6A26 for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 07:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.573
X-Spam-Level: 
X-Spam-Status: No, score=-10.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g7nT0ZV4VsvH for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 07:20:20 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 926623A67E3 for <siprec@ietf.org>; Tue, 29 Mar 2011 07:20:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=7287; q=dns/txt; s=iport; t=1301408514; x=1302618114; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=86/tTiwEBG+wPJLBN6URRwnurkHfAfQeEi/n6fVaavk=; b=FOnMxhOs8ZgSbRa8maSoA66ZU+5s9srOuxWciywTqbv7kzhCoXLr0Bmc WZ3HOoWWralBOqzDNf1f3QpAwIjpiS4Rdi7EVT7ex2Tt/zL1if0BtTMVn bCgqaR8SE2ePdd7M0DUHWrbNT0RIZyZmNnEIfwKQ4nLnW8+wPVcbbv4Yn 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMAAHvpkU2rRDoH/2dsb2JhbACYEI09d6g8nEeCfIJuBIU8iyA
X-IronPort-AV: E=Sophos;i="4.63,262,1299456000"; d="scan'208";a="420228827"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-1.cisco.com with ESMTP; 29 Mar 2011 14:21:42 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2TELf18002180; Tue, 29 Mar 2011 14:21:42 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Mar 2011 07:20:40 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Mar 2011 07:20:38 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <4D91CF3F.1010809@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: AcvuDB10rj518AwUSCuz6HBMGimE0wAD/MXA
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com>	<E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com> <4D91CF3F.1010809@cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>
X-OriginalArrivalTime: 29 Mar 2011 14:20:40.0544 (UTC) FILETIME=[7B4EAE00:01CBEE1C]
Cc: siprec@ietf.org
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 14:20:33 -0000

For the format and value of the CNAME, I suggest having a look at
"Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names
(CNAMEs)", draft-ietf-avt-rtp-cnames-05.=20
If the SIP AOR is meant to be the AOR registered by the participant,
this is almost certainly going to be something different.
The participant AOR is per participant. The CNAME is per media stream.

Cheers,
Charles

> -----Original Message-----
> From: Paul Kyzivat (pkyzivat)
> Sent: Tuesday, March 29, 2011 2:23 PM
> To: Leon Portman
> Cc: Parthasarathi R (partr); Charles Eckel (eckelcu); siprec@ietf.org
> Subject: Re: [siprec] Multiplexing different participants' streams on
the same port
>=20
>=20
>=20
> On 3/29/2011 7:21 AM, Leon Portman wrote:
> > I like it.
> >
> > Quick question. In metadata we are using "<aor>" attribute but in
SDP, it is "CNAME"? Can we use the
> same?
>=20
> Charles knows more than I about RTP. AFAIK CNAME is an essentially
> arbitrary string that is assigned by the media source. (Are their
> constraints on its length or format?) Perhaps it could be formatted as
a
> sip AOR, perhaps not. Even if it *could*, in practice *will* it be?
ISTM
> it would not be wise to count on these being the same.
>=20
> We should probably allow participants to specify their cname as well
as
> their AOR. This may get complicated if the same participant ends up
with
> differing media streams it sends.
>=20
> I also wonder if the SRC will always know the CNAMEs of the streams. I
> suspect we can't count on that.
>=20
> 	Thanks,
> 	Paul
>=20
> > Leon
> >
> >
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Parthasarathi R (partr)
> > Sent: Monday, March 28, 2011 10:42 AM
> > To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat);
siprec@ietf.org
> > Subject: Re: [siprec] Multiplexing different participants' streams
on the same port
> >
> > Charles,
> >
> > IMO, the current metadata model helps to address RTP MUX streams as
well. In terms of model,
> multiple participants (P1, P2, P3) metadata block points to the single
stream (S1) and stream block
> contains SSRC&  CSRC information. IOW, SIPREC model abstract RTP MUX
stream within media stream block.
> Please let me know in case you feel that model does not address it.
> >
> > In case of metadata format, multiple "participant" elements have
send element with single stream
> element. The stream element has a label attribute which points to the
m-line which contains "ssrc"
> attribute with CNAME parameter. I attached the example for your
reference and The example is the one
> of the way to represent RTP-MUX stream in the metadata format. Please
let me know the issues with this
> format and example.
> >
> > I agree with Paul and you that we need to understand how RTP mux
stream will be standardized but
> IMO, it is not the limiting factor for SIPREC as of now.
> >
> > Thanks
> > Partha
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Charles Eckel (eckelcu)
> > Sent: Friday, March 18, 2011 8:40 PM
> > To: Paul Kyzivat (pkyzivat); siprec@ietf.org
> > Subject: Re: [siprec] Multiplexing different participants' streams
on thesame port
> >
> > I agree with the comment regarding CLUE, so let me take a simpler
example, and audio mixer. This
> mixer may mix the audio from multiple participants.
> >
> > Participant 1 (P1)
> > Participant 2 (P2)
> > Participant 3 (P3)
> >
> > P1 sends audio stream with SSRC-P1
> > P2 sends audio stream with SSCR-P2
> > P2 sends audio stream with SSCR-P3
> >
> > MixerA(Ma)
> >
> > Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
> > SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
> > The SRC sends this stream to the SRS for recording. I suspect it
might change the SSRC to be SSRC-
> SRC but maintain the CSRC information identifying P1/P2/P3.
> > I expect this would be modeled as a single stream with 3
participants P1, P2, P3. The mapping of P1
> to SSRC-P1 is captured in the RTCP data sent by SRC to SRS. In this
case, there is no need to anything
> in the metadata.
> > However, if the CSRCs are not propagated all the way to the SRS,
then perhaps participant info would
> need to be communicated via the metadata.
> >
> > Note, I do not pretend to have this all figured out; rather, I am
putting out some ideas to see if
> this gels with what others have in mind.
> >
> > Cheers,
> > Charles
> >
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Paul Kyzivat (pkyzivat)
> >> Sent: Friday, March 18, 2011 5:38 AM
> >> To: siprec@ietf.org
> >> Subject: Re: [siprec] Multiplexing different participants' streams
on
> > the same port
> >>
> >> I don't know if this is a good idea or not. But if we want to
consider
> >
> >> it, then we should probably enter into some discussion with CLUE,
to
> > see
> >> if there is any commonality.
> >>
> >> Over in CLUE, this mixing of multiple streams over one RTP session
has
> >
> >> been brought up because it is a technique used in existing
proprietary
> >
> >> products. But the CLUE wg isn't yet to a point where it is ready to
> >> decide if this will be a requirement. And the AVT people have
strong
> >> opinions on what is/isn't appropriate.
> >>
> >> 	Thanks,
> >> 	Paul
> >>
> >> On 3/18/2011 4:11 AM, Elwell, John wrote:
> >>> Something Charles mentioned in another thread triggered me to
raise
> > this.
> >>>
> >>> We consider different participants in the CS as potentially
> > producing separate media streams that
> >> the SRC sends to the SRS, where the SRC can send them mixed or
> > unmixed.
> >>>
> >>> When sending them unmixed, up till now I think we have considered
> > sending them to separate ports on
> >> the SRS and identifying them as separate m=3D lines in the SDP.
Another
> > possibility might be to
> >> multiplex the different streams on the same port and identify them
by
> > different SSRC values. I am not
> >> sure whether this would be a correct use of SSRC, and I suspect we
> > would need to check with AVTCORE.
> >> Recent discussions in other contexts (telepresence, RTC-Web) have
also
> > drawn my attention to such
> >> possibilities. See also
> > https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
> >>>
> >>> Of course, it would mean that we would have to rethink how we
> > reference the different streams from
> >> metadata.
> >>>
> >>> I am not necessarily proposing such a change - I just want to make
> > sure we have given it due
> >> consideration.
> >>>
> >>> John (as individual)
> >>>
> >>>
> >>> _______________________________________________
> >>> 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
> >

From eckelcu@cisco.com  Tue Mar 29 07:36:21 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 65BB23A6844 for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 07:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.574
X-Spam-Level: 
X-Spam-Status: No, score=-10.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VogtQLVsH-2m for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 07:36:20 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 3B2563A6921 for <siprec@ietf.org>; Tue, 29 Mar 2011 07:36:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=3204; q=dns/txt; s=iport; t=1301409478; x=1302619078; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=BW0dBr8Y8BKlpgBtXuO9Dwg3M7metcO7RfCjhpTe94w=; b=kTBzkwDB3kduh9bH6hoAFh2s0KKogt+VlU+9WmDiNc0kEq1NX+0xK267 CF8D1H79tEnTcNqaiQkMD4CZsxmin0JSlLWRsnUWZFNNtL+oQwCdktS0p h2pnNGqqiV+v6PyOA03T0GQtv8nOU9NSRio9/KQn7+es19/m0UMphTEw4 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMAAC3ukU2tJXG9/2dsb2JhbACYEY09d4h5nzOcS4VqBIU8iyA
X-IronPort-AV: E=Sophos;i="4.63,262,1299456000"; d="scan'208";a="420240638"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-1.cisco.com with ESMTP; 29 Mar 2011 14:37:58 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2TEbvrw017995 for <siprec@ietf.org>; Tue, 29 Mar 2011 14:37:57 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Mar 2011 07:37:57 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Mar 2011 07:37:55 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhgBO/qTgAD5pH0A=
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 29 Mar 2011 14:37:57.0327 (UTC) FILETIME=[E54735F0:01CBEE1E]
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 14:36:21 -0000

Hi Partha,

Thanks for your response. This addresses all of my concerns. Please see
one additional clarification inline.=20

> -----Original Message-----
> From: Parthasarathi R (partr)
> Sent: Tuesday, March 29, 2011 10:31 AM
> To: Charles Eckel (eckelcu); siprec@ietf.org
> Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> Charles,
>=20
> Thanks for review the document. Please read inline.
>=20
> Thanks
> Partha
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Charles Eckel (eckelcu)
> Sent: Sunday, March 27, 2011 12:35 AM
> To: siprec@ietf.org
> Subject: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> I gave the draft and read and have the following comments.
>=20
> Section 3. Think the metadata describes the recording session, not the
communication session. Replace
> "metamodel" with "metadata model", and "MAY be conveyed in Recording
Session" with "MAY be conveyed
> within the Recording Session", and "time a change occurred by be
assumed" with "time a change occurred
> may be assumed".
>=20
> Section 4, suggest rewording as, "The section describes each element
of the metadata model, and the
> attributes of each element. This section also describes how the
different elements are associated."
>=20
> Section 4.1, RecordingRequestorID is not really an ID, it is more of a
type. I think
> RecordingRequestor is more appropriate.
>=20
>=20
> <Partha>Agreed. We will update in the next revision </partha>
>=20
>  That said, I think you also need a unique ID for the Recording
Session, right?
> <partha>  Please clarify whether you are interested in AOR of RS or
just ID. In the model, Recording
> (1..*) is related to CSG (0..*) and there is no need of separate
attribute for unique id. In the
> metadata format, URN UUID in CSG (group) & recording exist which helps
to visualize the association
> </partha>

I am assuming there is a need to distinguish one RS from another RS, and
that is the reason I was recommending adding a unique ID. This ID would
not be the RS AOR as that may not be unique.

Cheers,
Charles

> Section 4.2.1, replace "SRC (or MAY be SRS)" with "SRC or SRS".
> <Partha>Agreed. We will update in the next revision </partha>
>=20
> Section 4.3.2, why does a CS need two participants or more? What about
studio mode recording?
>=20
> Section 4.4.1, what is participant type and what is its use, or why
needed?
> <partha> This attribute has to be removed as per the last interim
meeting. We will update in the next
> revision. </partha>
>=20
> Section 4.5, I think Media Stream requires a unique ID attribute as
well.
> <partha> As mentioned above in the model draft, the association
between CS and participant is shown.
> In terms of format draft, it is represented by URN UUID </partha>
> Is the "Media Stream Reference" the SDP label attribute?
> <partha> Your understanding is correct </partha>
>=20
>=20
> Thanks,
> Charles
>=20
>=20
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From pkyzivat@cisco.com  Tue Mar 29 14:38:58 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FFCE3A6AC5 for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 14:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jbDyDOM2TJ0c for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 14:38:56 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 077763A6AB5 for <siprec@ietf.org>; Tue, 29 Mar 2011 14:38:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=7612; q=dns/txt; s=iport; t=1301434835; x=1302644435; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=DIKvepGROKebnuVeopmFNEn8hPkZ/3fIZUhYx62R88M=; b=ezIQnK7pw4y6k2/YyTmVH64sRUsbbdOtHikex8TefyZUxvRLdq/wBLy2 H1fqmeBSVmBMOI4wKi7UBTQZXD26E5b3aQ/+yyVMjpz2XGnuY0AOGv0oi 42Gewwz3pJxap50vMmDwOqcw3ljWIy4KB46io0pK9OYXop3EeTrEHOdNc A=;
X-IronPort-AV: E=Sophos;i="4.63,264,1299456000"; d="scan'208";a="81365003"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 29 Mar 2011 21:40:33 +0000
Received: from [10.61.105.172] (dhcp-10-61-105-172.cisco.com [10.61.105.172]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2TLeWTP008853; Tue, 29 Mar 2011 21:40:32 GMT
Message-ID: <4D9251D0.5020006@cisco.com>
Date: Tue, 29 Mar 2011 17:40:32 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com>	<E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com> <4D91CF3F.1010809@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: siprec@ietf.org, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 21:38:58 -0000

Charles,

*In practice* how are cnames set for sip calls?
I'm assuming they are something canned and unrelated to the signaling 
identity.

	Thanks,
	Paul

On 3/29/2011 10:20 AM, Charles Eckel (eckelcu) wrote:
> For the format and value of the CNAME, I suggest having a look at
> "Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names
> (CNAMEs)", draft-ietf-avt-rtp-cnames-05.
> If the SIP AOR is meant to be the AOR registered by the participant,
> this is almost certainly going to be something different.
> The participant AOR is per participant. The CNAME is per media stream.
>
> Cheers,
> Charles
>
>> -----Original Message-----
>> From: Paul Kyzivat (pkyzivat)
>> Sent: Tuesday, March 29, 2011 2:23 PM
>> To: Leon Portman
>> Cc: Parthasarathi R (partr); Charles Eckel (eckelcu); siprec@ietf.org
>> Subject: Re: [siprec] Multiplexing different participants' streams on
> the same port
>>
>>
>>
>> On 3/29/2011 7:21 AM, Leon Portman wrote:
>>> I like it.
>>>
>>> Quick question. In metadata we are using "<aor>" attribute but in
> SDP, it is "CNAME"? Can we use the
>> same?
>>
>> Charles knows more than I about RTP. AFAIK CNAME is an essentially
>> arbitrary string that is assigned by the media source. (Are their
>> constraints on its length or format?) Perhaps it could be formatted as
> a
>> sip AOR, perhaps not. Even if it *could*, in practice *will* it be?
> ISTM
>> it would not be wise to count on these being the same.
>>
>> We should probably allow participants to specify their cname as well
> as
>> their AOR. This may get complicated if the same participant ends up
> with
>> differing media streams it sends.
>>
>> I also wonder if the SRC will always know the CNAMEs of the streams. I
>> suspect we can't count on that.
>>
>> 	Thanks,
>> 	Paul
>>
>>> Leon
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Parthasarathi R (partr)
>>> Sent: Monday, March 28, 2011 10:42 AM
>>> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat);
> siprec@ietf.org
>>> Subject: Re: [siprec] Multiplexing different participants' streams
> on the same port
>>>
>>> Charles,
>>>
>>> IMO, the current metadata model helps to address RTP MUX streams as
> well. In terms of model,
>> multiple participants (P1, P2, P3) metadata block points to the single
> stream (S1) and stream block
>> contains SSRC&   CSRC information. IOW, SIPREC model abstract RTP MUX
> stream within media stream block.
>> Please let me know in case you feel that model does not address it.
>>>
>>> In case of metadata format, multiple "participant" elements have
> send element with single stream
>> element. The stream element has a label attribute which points to the
> m-line which contains "ssrc"
>> attribute with CNAME parameter. I attached the example for your
> reference and The example is the one
>> of the way to represent RTP-MUX stream in the metadata format. Please
> let me know the issues with this
>> format and example.
>>>
>>> I agree with Paul and you that we need to understand how RTP mux
> stream will be standardized but
>> IMO, it is not the limiting factor for SIPREC as of now.
>>>
>>> Thanks
>>> Partha
>>>
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Charles Eckel (eckelcu)
>>> Sent: Friday, March 18, 2011 8:40 PM
>>> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
>>> Subject: Re: [siprec] Multiplexing different participants' streams
> on thesame port
>>>
>>> I agree with the comment regarding CLUE, so let me take a simpler
> example, and audio mixer. This
>> mixer may mix the audio from multiple participants.
>>>
>>> Participant 1 (P1)
>>> Participant 2 (P2)
>>> Participant 3 (P3)
>>>
>>> P1 sends audio stream with SSRC-P1
>>> P2 sends audio stream with SSCR-P2
>>> P2 sends audio stream with SSCR-P3
>>>
>>> MixerA(Ma)
>>>
>>> Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
>>> SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
>>> The SRC sends this stream to the SRS for recording. I suspect it
> might change the SSRC to be SSRC-
>> SRC but maintain the CSRC information identifying P1/P2/P3.
>>> I expect this would be modeled as a single stream with 3
> participants P1, P2, P3. The mapping of P1
>> to SSRC-P1 is captured in the RTCP data sent by SRC to SRS. In this
> case, there is no need to anything
>> in the metadata.
>>> However, if the CSRCs are not propagated all the way to the SRS,
> then perhaps participant info would
>> need to be communicated via the metadata.
>>>
>>> Note, I do not pretend to have this all figured out; rather, I am
> putting out some ideas to see if
>> this gels with what others have in mind.
>>>
>>> Cheers,
>>> Charles
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf Of Paul Kyzivat (pkyzivat)
>>>> Sent: Friday, March 18, 2011 5:38 AM
>>>> To: siprec@ietf.org
>>>> Subject: Re: [siprec] Multiplexing different participants' streams
> on
>>> the same port
>>>>
>>>> I don't know if this is a good idea or not. But if we want to
> consider
>>>
>>>> it, then we should probably enter into some discussion with CLUE,
> to
>>> see
>>>> if there is any commonality.
>>>>
>>>> Over in CLUE, this mixing of multiple streams over one RTP session
> has
>>>
>>>> been brought up because it is a technique used in existing
> proprietary
>>>
>>>> products. But the CLUE wg isn't yet to a point where it is ready to
>>>> decide if this will be a requirement. And the AVT people have
> strong
>>>> opinions on what is/isn't appropriate.
>>>>
>>>> 	Thanks,
>>>> 	Paul
>>>>
>>>> On 3/18/2011 4:11 AM, Elwell, John wrote:
>>>>> Something Charles mentioned in another thread triggered me to
> raise
>>> this.
>>>>>
>>>>> We consider different participants in the CS as potentially
>>> producing separate media streams that
>>>> the SRC sends to the SRS, where the SRC can send them mixed or
>>> unmixed.
>>>>>
>>>>> When sending them unmixed, up till now I think we have considered
>>> sending them to separate ports on
>>>> the SRS and identifying them as separate m= lines in the SDP.
> Another
>>> possibility might be to
>>>> multiplex the different streams on the same port and identify them
> by
>>> different SSRC values. I am not
>>>> sure whether this would be a correct use of SSRC, and I suspect we
>>> would need to check with AVTCORE.
>>>> Recent discussions in other contexts (telepresence, RTC-Web) have
> also
>>> drawn my attention to such
>>>> possibilities. See also
>>> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
>>>>>
>>>>> Of course, it would mean that we would have to rethink how we
>>> reference the different streams from
>>>> metadata.
>>>>>
>>>>> I am not necessarily proposing such a change - I just want to make
>>> sure we have given it due
>>>> consideration.
>>>>>
>>>>> John (as individual)
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>

From john.elwell@siemens-enterprise.com  Tue Mar 29 14:45:33 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3408328C0EE for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 14:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJAnxyhc+N9e for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 14:45:30 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 2B81D3A6AB6 for <siprec@ietf.org>; Tue, 29 Mar 2011 14:45:29 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3940324; Tue, 29 Mar 2011 23:47:07 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id DB5071EB82B4; Tue, 29 Mar 2011 23:47:07 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 29 Mar 2011 23:47:07 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, Leon Portman <Leon.Portman@nice.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
Date: Tue, 29 Mar 2011 23:47:05 +0200
Thread-Topic: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
Thread-Index: AcvY+qyFanmfNOL5Qlq3osURZ2w4qAJbzb1IACUhGWAAGstGAwFGdfdAAAXbWKAAA+XmQAAAGhNQABG/CmwAHSHXEAAZDuOFABzjR+AAVixTcAAUeoQQAAAj4EAAHgihsAAClqhQAAXOdEAADtUDkAAjidVAAABgrFAAAo/hIAAdpARgAAc8P9AAG6geUA==
Message-ID: <A444A0F8084434499206E78C106220CA0875AF35D5@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA06C2C503BF@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A1@XMB-BGL-411.cisco.com><101C6067BEC68246B0C3F6843BCCC1E30B61DB3370@MCHP058A.global-ad.net><A11921905DA1564D9BCF64A6430A62390293A6A6@XMB-BGL-411.cisco.com><A11921905DA1564D9BCF64A6430A623904CAFBA7@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38A960C8F0@TLVMBX01.nice.com><101C6067BEC68246B0C3F6843BCCC1E30B61E96D11@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38A960C9CA@TLVMBX01.nice.com><A11921905DA1564D9BCF64A6430A62390293A6BE@XMB-BGL-411.cisco.com><35BCE99A477D6A4986FB2216D8CF2CFD05CC9E38@XMB-BGL-417.cisco.com><A11921905DA1564D9BCF64A6430A62390293A6C8@XMB-BGL-411.cisco.com><A444A0F8084434499206E78C106220CA086AA5575C@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB466335@TLVMBX01.nice.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EAA@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB46639F@TLVMBX01.nice.com> <E1CB F4C7095	A	3D4CAAAEAD	09		FBB8E08C03D86EE9@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466603@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875AF2B09@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E30B6D1ED8E0@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E38202@xmb-sjc-234.amer.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB466C1B@TLVMBX01.nice.com> <A11921905DA1564D9BCF64A6430A623904DA218D@XMB-BGL-411.cisco.com> <A444A0F8084434499206E78C106220CA0875AF3066@MCHP058A.global-ad.net> <A11921905DA1564D9BCF64A6430A623904DA23A5@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904DA23A5@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Dialog state in the CS block of metadatamodel[wasRE:Progressing the architecture document]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 21:45:33 -0000

> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> Sent: 29 March 2011 09:50
> To: Elwell, John; Leon Portman; Charles Eckel (eckelcu);
> Hutton, Andrew; Ram Mohan R (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture document]
>
> John,
>
> I agree with you in case of media server participant sends "ringback"
> media stream during the early dialog and later stage, the callee
> participant sends actual stream of the session using another
> offer/answer exchange. It is also possible that callee sends
> "ringback"
> media stream  wherein there is no difference between early or regular
> media in terms of metadata information.
>
> Having said that, it "may" or "may not" be matter whether the
> devices of
> the participant automatically creates the media stream or participant
> actually creates media stream.
[JRE] The SRC, depending on where it is located on the path of the CS, migh=
t be unable to determine whether media comes from a user or from the user's=
 device. Only an SRC collocated with the user's device can determine this. =
A B2BUA would be unable to determine it, for example. So is it really worth=
 trying to send information about this if, in many situations, the informat=
ion will not be available?

John (as individual)


>
> Thanks
> Partha
>
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Tuesday, March 29, 2011 10:39 AM
> To: Parthasarathi R (partr); Leon Portman; Charles Eckel (eckelcu);
> Hutton, Andrew; Ram Mohan R (rmohanr)
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Dialog state in the CS block of
> metadatamodel[wasRE:Progressing the architecture document]
>
> Partha,
>
> I think the real distinction you wish to make is between media coming
> from a particular participant (associated with the UAS) and
> media coming
> from some other entity (e.g., media server). In my view the
> latter case,
> if we choose to record it, comes from a different
> "participant". It has
> nothing to do with whether it is deemed early or regular from a SIP
> dialog perspective.
>
> John (as individual)
>
>
> > -----Original Message-----
> > From: Parthasarathi R (partr) [mailto:partr@cisco.com]
> > Sent: 28 March 2011 17:53
> > To: Leon Portman; Charles Eckel (eckelcu); Hutton, Andrew; Elwell,
> > John; Ram Mohan R (rmohanr)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel[wasRE:Progressing the architecture document]
> >
> >
> > The question of "session" state is raised in my mind mainly to
> > distinguish between early media (Media before session
> establishment)
> > from normal media. Without the information in SIPREC metadata, the
> > early media will be associated with UAS participant's media stream.
> > I'm interested in knowing whether SIPREC solution has to
> differentiate
>
> > between early media from normal media.
> >
> > As per John below mail, there is no need to differentiate
> as per the
> > current requirement. If most of the folks feel so, I'm fine
> with not
> > including "session state" in metadata.
> >
> > Thanks
> > Partha
> >
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: Monday, March 28, 2011 7:16 PM
> > To: Charles Eckel (eckelcu); Hutton, Andrew; Elwell, John;
> > Parthasarathi R (partr); Ram Mohan R (rmohanr)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel[wasRE:Progressing the architecture document]
> >
> > Charles Hi
> >
> > Just to make clear, I don't think SRS should receive dialog level
> > state events about all  CS dialogs. I think that we should
> to support
> > reporting high level session events.
> > I understand the complexity of that and Ok to keep it open or next
> > phase extensions
> >
> > Leon
> >
> > -----Original Message-----
> > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > Sent: Monday, March 28, 2011 3:35 PM
> > To: Hutton, Andrew; Elwell, John; Leon Portman; Parthasarathi R
> > (partr); Ram Mohan R (rmohanr)
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel[wasRE:Progressing the architecture document]
> >
> > I agree with this approach. Hopefully Leon and others that saw the
> > need for this state information can confirm if it works for them.
> >
> > Cheers,
> > Charles
> >
> > > -----Original Message-----
> > > From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> > > Sent: Monday, March 28, 2011 9:13 AM
> > > To: Elwell, John; Leon Portman; Charles Eckel (eckelcu);
> > Parthasarathi
> > R (partr); Ram Mohan R
> > > (rmohanr)
> > > Cc: siprec@ietf.org
> > > Subject: RE: [siprec] Dialog state in the CS block of
> > metadatamodel[wasRE:Progressing the architecture
> > > document]
> > >
> > > Hi,
> > >
> > > The draft-ietf-siprec-architecture has from the very
> > beginning listed
> > dialog state as an example of
> > > what would be included in metadata which is why I raised
> > the question.
> > >
> > > However it is true to say this was put in the
> architecture document
> > before we had firmed up the
> > > requirements or starting any indepth work on metadata so I could
> > accept that the architecture draft
> > > simply got this wrong from the start and it maybe should
> be removed.
> > We could of course take the view
> > > that if dialog events are important then the SRS could
> subscribe to
> > the dialog event package at the
> > > SRC and SIPREC does not need to touch this.
> > >
> > > I don't think we can allow SIPREC metadata to extend as far as
> > reporting everything that happens to
> > > the CS including how it is linked to other CS's and what
> > services are
> > used on the CS (E.g. types of
> > > transfer etc.). This would quickly get very difficult to
> > define and we
> > would probably fail.
> > >
> > > I would prefer to not report this state information in
> metadata than
> > open up the possibility of adding
> > > lots of complexity.
> > >
> > > Regards
> > > Andy
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Elwell, John
> > > > Sent: 27 March 2011 14:50
> > > > To: Leon Portman; Charles Eckel (eckelcu); Parthasarathi
> > R (partr);
> > > > Ram Mohan R (rmohanr); Hutton, Andrew
> > > > Cc: siprec@ietf.org
> > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > metadatamodel[wasRE:Progressing the architecture document]
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > Sent: 27 March 2011 11:48
> > > > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi R
> > > > > (partr); Ram Mohan R (rmohanr); Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > > metadatamodel[wasRE:Progressing the architecture document]
> > > > >
> > > > > Charles Hi
> > > > >
> > > > > Yes, it will be good to discuss it face to face.
> > > > >
> > > > > Just little background for such requirements. Today,
> especially
> > > > > for contact centers, it is important for SRS to capture the
> > > > > information how long customer was waiting for agent to
> > answer the
> > > > > call, which party hang up, how long was the hold time,
> > if it was
> > > > > blind transfer or consultation transfer. This information
> > > > > important both from quality management point of view
> > and customer
> > > > > experience point of view.
> > > > [JRE] (as chair) I think the group needs to consider
> > whether this is
> >
> > > > within scope. Looking at the requirements, we have:
> > > > "REQ-012 The mechanism MUST provide the SRS with metadata
> > describing
> > > >    CSs that are being recorded, including the media
> being used and
> > the
> > > >    identities of parties involved."
> > > > If we are not recording the session while the caller is
> > waiting to
> > > > be answered, it seems we perhaps don't have a requirement for
> > > > metadata about that. This seems to be more about call detail
> > > > recording (CDR) rather than session recording. We can by
> > all means
> > > > have this discussion, but I am concerned about scope creep.
> > > >
> > > > > It is important also from compliance point of view to
> detect if
> > > > > somebody actually received the media stream or still was in
> > > > > pending state or media stream was disconnected.
> > > > [JRE] (as individual) I agree we should show a participant as
> > > > receiving media only if the SRC believes media is
> actually being
> > > > sent to that participant (even then, there can be no
> > guarantee it is
> >
> > > > received, e.g., because NAT or firewall traversal isn't
> > functioning
> > > > properly, severe packet loss, speaker volume is muted,
> > etc..). But I
> >
> > > > have doubts whether it is necessarily to try to account
> > for periods
> > > > when the SRC knows a participant is not receiving media
> > by saying it
> >
> > > > is because of alerting, hold or whatever.
> > > >
> > > > John
> > > >
> > > >
> > > > >
> > > > > Leon
> > > > >
> > > > > -----Original Message-----
> > > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > > Sent: Sunday, March 27, 2011 11:35 AM
> > > > > To: Leon Portman; Elwell, John; Parthasarathi R
> > (partr); Ram Mohan
> >
> > > > > R (rmohanr); Hutton, Andrew
> > > > > Cc: siprec@ietf.org
> > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > > metadatamodel[wasRE:Progressing the architecture document]
> > > > >
> > > > > Hi Leon,
> > > > >
> > > > > Thank you for your patience in trying to explain this to me;
> > > > > however, I still am not able to understand why the SRS
> > might need
> > > > > to know this information, or what it would do with it.
> > > > > Is it that you need to know when a given participant
> > was receiving
> >
> > > > > the recorded media and when it was not? If so, I do not think
> > > > > dialog state is sufficient. Is there some other
> requirement or
> > > > > functionality addressed by the SRS having such information?
> > > > > Perhaps it is easier to discuss in person at the
> > breakfast meeting
> >
> > > > > Wednesday or during the working group session.
> > > > >
> > > > > Cheers,
> > > > > Charles
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > Sent: Saturday, March 26, 2011 8:15 PM
> > > > > > To: Charles Eckel (eckelcu); Elwell, John; Parthasarathi
> > > > R (partr);
> > > > > Ram Mohan R (rmohanr); Hutton,
> > > > > > Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > > metadatamodel[wasRE:Progressing the architecture
> > > > > > document]
> > > > > >
> > > > > > Charles Hi
> > > > > >
> > > > > > Without participant session state, SRS will know only when
> > > > > participant
> > > > > is part of the session and will
> > > > > > not know about intermediate states like ringing,
> retrying etc.
> > > > > > I know that we have media stream information per
> > > > participant but not
> > > > > sure that it is enough.
> > > > > >
> > > > > > Leon
> > > > > > -----Original Message-----
> > > > > > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
> > > > > > Sent: Saturday, March 26, 2011 9:07 PM
> > > > > > To: Leon Portman; Elwell, John; Parthasarathi R (partr);
> > > > Ram Mohan R
> > > > > (rmohanr); Hutton, Andrew
> > > > > > Cc: siprec@ietf.org
> > > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > metadatamodel
> > > > > [wasRE:Progressing the
> > > > > > architecture document]
> > > > > >
> > > > > > Hi Leon,
> > > > > >
> > > > > > I am still having a hard time understanding why we need
> > > > the session
> > > > > state information per CS
> > > > > > participant? Why is this required, who uses it, and how?
> > > > > >
> > > > > > Thanks,
> > > > > > Charles
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org] On
> > > > > > Behalf Of Leon Portman
> > > > > > > Sent: Saturday, March 26, 2011 10:31 AM
> > > > > > > To: Elwell, John; Parthasarathi R (partr); Ram Mohan R
> > > > (rmohanr);
> > > > > > Hutton, Andrew
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: Re: [siprec] Dialog state in the CS block of
> > > > > metadatamodel
> > > > > > [wasRE:Progressing the
> > > > > > > architecture document]
> > > > > > >
> > > > > > > John Hello
> > > > > > >
> > > > > > > I agree that SRS (and its application clients) interested
> > > > > in SESSION
> > > > > > level events and not underlying
> > > > > > > DIALOG events. However we do need to support reporting
> > > > > session state
> > > > > > information per CS  participant
> > > > > > > that sometimes equals to dialog level and sometimes not.
> > > > > > >
> > > > > > > We could have define more application level state
> > events like
> > > > > instead
> > > > > > of TRYING - > RINGING etc.
> > > > > > > However they could be domain specific.
> > > > > > >
> > > > > > > Leon
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Elwell, John
> > [mailto:john.elwell@siemens-enterprise.com]
> > > > > > > Sent: Thursday, March 24, 2011 6:34 PM
> > > > > > > To: Parthasarathi R (partr); Ram Mohan R (rmohanr);
> > > > Leon Portman;
> > > > > > Hutton, Andrew
> > > > > > > Cc: siprec@ietf.org
> > > > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > > > > metadata model
> > > > > > [wasRE:Progressing the
> > > > > > > architecture document]
> > > > > > >
> > > > > > > This discussion gives me some concerns, echoing to some
> > > > > extent what
> > > > > > Ram is saying.
> > > > > > >
> > > > > > > SIPREC is about session recording, where a session is the
> > > > > information
> > > > > > exchanged between participants
> > > > > > > in a CS (the media streams) plus metadata. The
> > metadata should
> > > > > provide
> > > > > > additional information about
> > > > > > > the CS. This means information about the communication
> > > > > SESSION, not
> > > > > > about the SIP dialog that is used
> > > > > > > to control that session. With this in mind, consider
> > > > the following
> > > > > > points, some of which have already
> > > > > > > been raised:
> > > > > > >
> > > > > > > 1. There may be more than one SIP dialog involved if the
> > > > > SRC is at a
> > > > > > B2BUA or conference focus.
> > > > > > >
> > > > > > > 2. Does the CS necessarily need to be controlled
> by SIP? For
> > > > > example,
> > > > > > it could be a PSTN call, an RTC-
> > > > > > > Web call or a Jingle call. None of these preclude using
> > > > > SIP for the
> > > > > RS
> > > > > > (that is what the charter of
> > > > > > > SIPREC is all about - a SIP-based RS).
> > > > > > >
> > > > > > > 3. Somebody retrieving and playing back a recorded
> > CS will be
> > > > > > interested in session-related events
> > > > > > > like participants leaving and joining (including the first
> > > > > > participants joining at the start of the CS
> > > > > > > and the last participants leaving a the end of the
> > CS), media
> > > > > streams
> > > > > > starting and ending and
> > > > > > > participants starting or stopping receipt of a
> media stream.
> > In
> > > > > other
> > > > > > words, changes of SESSION state,
> > > > > > > not dialog state.
> > > > > > >
> > > > > > > 4. Some of the SIP dialog states just don't seem
> > relevant. The
> > > > > > distinction between early dialog and
> > > > > > > full dialog in SIP does not necessarily
> corresponding to any
> > > > > > meaningful state change of the session.
> > > > > > > For example, A makes a call to B and B answers and
> > > > starts sending
> > > > > > media. A receives and renders media
> > > > > > > (perhaps it has already received SDP answer, allowing
> > > > it to verify
> > > > > the
> > > > > > source of the media). Then A
> > > > > > > receives the 200 OK (transitioning from an early dialog
> > > > to a full
> > > > > > dialog) and continues to receive
> > > > > > > media. So although there is a dialog state
> change, there is
> > not
> > > > > really
> > > > > > a session state change.
> > > > > > >
> > > > > > > The bit about dialog state in the architecture
> > draft is, in my
> > > > > > opinion, a legacy from some earlier
> > > > > > > discussions, before we started having the metadata
> > > > discussions. I
> > > > > > think the metadata discussions have
> > > > > > > taken us in the right direction.
> > > > > > >
> > > > > > > John (as individual)
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: siprec-bounces@ietf.org
> > > > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > Parthasarathi
> > R
> > > > > > (partr)
> > > > > > > > Sent: 24 March 2011 02:36
> > > > > > > > To: Ram Mohan R (rmohanr); Leon Portman; Hutton, Andrew
> > > > > > > > Cc: siprec@ietf.org
> > > > > > > > Subject: Re: [siprec] Dialog state in the CS block of
> > metadata
> > > > > model
> > > > > > > > [wasRE:Progressing the architecture document]
> > > > > > > >
> > > > > > > > Ram,
> > > > > > > >
> > > > > > > > Please read inline.
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > > Partha
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > >
> > > > > > > > From: Ram Mohan R (rmohanr)
> > > > > > > > Sent: Wed 3/23/2011 7:59 PM
> > > > > > > > To: Parthasarathi R (partr); Leon Portman;
> Hutton, Andrew
> > > > > > > > Cc: siprec@ietf.org
> > > > > > > > Subject: RE: [siprec] Dialog state in the CS block of
> > metadata
> > > > > model
> > > > > > > > [wasRE:Progressing the architecture document]
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > I am still trying to understand what is the
> > > > significance of this
> > > > > > > > attribute w.r.t CS. Are we saying the attribute
> represents
> > the
> > > > > state
> > > > > > > > of CS ?
> > > > > > > >
> > > > > > > > Note that CS need not be one dialog.
> > > > > > > >
> > > > > > > > <Partha>  The attribute is to show the state of CS
> > > > > only. As it is
> > > > > > not
> > > > > > > > single dialog, I have mentioned as session
> state attribute
> > > > > </Partha>
> > > > > > > >
> > > > > > > > For cases like Conference where there may be different
> > > > > participants,
> > > > > > > > if SRC happens to be Focus how do you derive/what is
> > "session
> > > > > state"
> > > > > > ?
> > > > > > > >
> > > > > > > > <Partha> I really don't know whether it is generic. My
> > thought
> > > > > > > > processing of session state for conference is
> as follows:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > 1) First participant of conference early media (ivr
> > > > play) may be
> > > > > > > > considered as "early" state of session.
> > > > > > > >
> > > > > > > > 2) The session state is chaged to confirmed in case any
> > > > > one of the
> > > > > > > > participant joined in the conference.
> > > > > > > >
> > > > > > > > 3) The session state is move to terminated when the last
> > > > > participant
> > > > > > > > moved out of the conference.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Please let me know in case other way to represent the
> > session
> > > > > state
> > > > > > of
> > > > > > > > conference </partha>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > For cases where B2BUA acts as SRC what is
> > "session state" ?
> > > > > > > >
> > > > > > > > <partha> It looks straight forward for me. In
> B2BUA case ,
> > > > > > > >
> > > > > > > > 1) The stage where in two party is not connected, it is
> > > > > considered
> > > > > > as
> > > > > > > > early state.
> > > > > > > >
> > > > > > > > 2) when both are connected, it is confirmed state
> > > > > > > >
> > > > > > > > 3) In case of BYE received from any one of the party,
> > > > then CS is
> > > > > > > > considered as terminated state
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Please note that this is applicable for 3PCC as well.
> > > > > </partha>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Ram
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > From: siprec-bounces@ietf.org
> > > > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > Parthasarathi
> > R
> > > > > > (partr)
> > > > > > > > Sent: Wednesday, March 23, 2011 6:13 AM
> > > > > > > > To: Leon Portman; Hutton, Andrew
> > > > > > > > Cc: siprec@ietf.org
> > > > > > > > Subject: Re: [siprec] Dialog state in the CS block of
> > metadata
> > > > > model
> > > > > > > > [wasRE:Progressing the architecture document]
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Leon,
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Shall we have optional "event" attribute to indicate the
> > state
> > > > > > change
> > > > > > > > which is similar to "event" attribute in RFC 4235.
> > > > The "event"
> > > > > will
> > > > > > > > include the following:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > 1) cancelled
> > > > > > > >
> > > > > > > > 2) rejected
> > > > > > > >
> > > > > > > > 3) replaced
> > > > > > > >
> > > > > > > > 4) bye
> > > > > > > >
> > > > > > > > 5) error
> > > > > > > >
> > > > > > > > 6) timeout
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > Partha
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > >
> > > > > > > > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > > > Sent: Tue 3/22/2011 9:37 PM
> > > > > > > > To: Hutton, Andrew; Parthasarathi R (partr)
> > > > > > > > Cc: siprec@ietf.org
> > > > > > > > Subject: RE: Dialog state in the CS block of metadata
> > > > model [was
> > > > > > > > RE:Progressing the architecture document]
> > > > > > > >
> > > > > > > > It can be either application level error or dialog
> > > > > level errors -
> > > > > > like
> > > > > > > > timeout or failures.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Leon
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > From: Hutton, Andrew
> > > > > [mailto:andrew.hutton@siemens-enterprise.com]
> > > > > > > > Sent: Tuesday, March 22, 2011 6:02 PM
> > > > > > > > To: Leon Portman; Parthasarathi R (partr)
> > > > > > > > Cc: siprec@ietf.org
> > > > > > > > Subject: RE: Dialog state in the CS block of metadata
> > > > model [was
> > > > > RE:
> > > > > > > > Progressing the architecture document]
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > What would it be used for?
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Regards
> > > > > > > >
> > > > > > > > Andy
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > >
> > > > > > > >   From: Leon Portman [mailto:Leon.Portman@nice.com]
> > > > > > > >   Sent: 22 March 2011 14:11
> > > > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > > > >   Cc: siprec@ietf.org
> > > > > > > >   Subject: RE: Dialog state in the CS block of metadata
> > > > > model [was
> > > > > > RE:
> > > > > > > > Progressing the architecture document]
> > > > > > > >
> > > > > > > >   Should we have error state as well?
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >   Leon
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >   From: siprec-bounces@ietf.org
> > > > > > > > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > Parthasarathi
> > R
> > > > > > (partr)
> > > > > > > >   Sent: Tuesday, March 22, 2011 3:33 PM
> > > > > > > >   To: Parthasarathi R (partr); Hutton, Andrew
> > > > > > > >   Cc: siprec@ietf.org
> > > > > > > >   Subject: [siprec] Dialog state in the CS block of
> > > > > metadata model
> > > > > > [was
> > > > > > > > RE: Progressing the architecture document]
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >   The architecture document proposes to have
> > > > > dialog/session state
> > > > > > in
> > > > > > > > Metadata model. To achieve this, "session state"
> > > > > attribute has to
> > > > > be
> > > > > > > > added in the CS block of Metadata model. The possible
> > > > values for
> > > > > > > > session state are
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >   1) Trying
> > > > > > > >
> > > > > > > >   2) Proceeding
> > > > > > > >
> > > > > > > >   3) Early
> > > > > > > >
> > > > > > > >   4) Confirmed
> > > > > > > >
> > > > > > > >   5) Terminated
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >   Please let me know in case any objection to add
> > > > this attribute
> > > > > > in
> > > > > > > > Metadata model.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >   Thanks
> > > > > > > >
> > > > > > > >   Partha
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > >
> > > > > > > >   From: Parthasarathi R (partr)
> > > > > > > >   Sent: Wednesday, March 16, 2011 5:40 AM
> > > > > > > >   To: Hutton, Andrew
> > > > > > > >   Cc: Elwell, John; siprec@ietf.org
> > > > > > > >   Subject: RE: Progressing the architecture document
> > > > > > > >
> > > > > > > >   > -----Original Message-----
> > > > > > > >   > From: siprec-bounces@ietf.org
> > > > > > > >   > [mailto:siprec-bounces@ietf.org] On Behalf Of
> > > > > Parthasarathi R
> > > > > > > > (partr)
> > > > > > > >   > Sent: 14 March 2011 17:05
> > > > > > > >   > To: Elwell, John; siprec@ietf.org
> > > > > > > >   > Subject: Re: [siprec] Progressing the
> > > > architecture document
> > > > > > > >
> > > > > > > >   >
> > > > > > > >   > Sec 4.3.1 whether 3rd bullet is required?
> > > > > > > >   >
> > > > > > > >
> > > > > > > >   [AndyH]I assume it is as for example I assume
> > it would be
> > > > > > necessary
> > > > > > > > to record early-media and update the SRS when the
> > > > dialog changes
> > > > > to
> > > > > > > > the confirmed or terminated state. Does not
> seem to be in
> > the
> > > > > > metadata
> > > > > > > > draft though. In the end I will either remove
> > these bullets
> > or
> > > > > align
> > > > > > > > with the metadata draft.
> > > > > > > >   <Partha> It is a good point. Dialog state shall be
> > > > > added as one
> > > > > > of
> > > > > > > > the optional attribute in CS metadata block with
> > > > > default value as
> > > > > > > > mid-dialog. This helps to differentiate between
> > early dialog
> > > > > > > > (ringback) vs mid-dialog (normal
> > > > > > > > conversation) in recording. In case of no
> > objection for this
> > > > > > attribute
> > > > > > > > in metadata model, we will add it. We will work
> > out metadata
> > > > > format
> > > > > > > > once the consensus occurs for metadata model.
> > > > > > > > In case required, we will span separate mail thread to
> > > > > close this
> > > > > > > > issue </Partha>
> > > > > > > >
> > > > > > > >
> > > > > > > _______________________________________________
> > > > > > > siprec mailing list
> > > > > > > siprec@ietf.org
> > > > > > > https://www.ietf.org/mailman/listinfo/siprec
> > > > >
> > > >
> >
>

From eckelcu@cisco.com  Tue Mar 29 15:04:29 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C854D3A6ACC for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 15:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.575
X-Spam-Level: 
X-Spam-Status: No, score=-10.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DQLd3fHNeHG for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 15:04:26 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id DF6E23A6825 for <siprec@ietf.org>; Tue, 29 Mar 2011 15:04:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=8739; q=dns/txt; s=iport; t=1301436365; x=1302645965; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=2VE1NeVmBUxvDTQshV6K5cY2SDXi414louz14/Rjao8=; b=LlSSht/LFGbBV0PJGgDaBa4K9za9+lvBIvzwO4RMdxoKYlPG/zoL/IO8 ZUzAcBCfJxKgREBGDVdDncLCC/UJRNh5Z9AdAJfimRJInq0FzCbTy7LJ0 IMzRUXDQHo+Mk8n8UpZrp3uYuCEceLyJ6Pd/p7O+BBRkwIrr6MgZ2et2U U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEBAO5Wkk2rRDoI/2dsb2JhbACYD41Ad59QnGeCfAGCbQSFPIsgiUI
X-IronPort-AV: E=Sophos;i="4.63,265,1299456000"; d="scan'208";a="672789829"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-6.cisco.com with ESMTP; 29 Mar 2011 22:06:02 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2TM62hN001124; Tue, 29 Mar 2011 22:06:02 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Mar 2011 15:06:02 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Mar 2011 15:05:59 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <4D9251D0.5020006@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: AcvuWfDEbSaUPY4tTRSCGnsvDfvonAAAwY9A
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com>	<E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com> <4D91CF3F.1010809@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com> <4D9251D0.5020006@cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 29 Mar 2011 22:06:02.0675 (UTC) FILETIME=[7E31C030:01CBEE5D]
Cc: siprec@ietf.org, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 22:04:29 -0000

Typically they appear in RTCP only, and not in SIP or SDP. The RTCP
identify the mapping of CNAME to SSRC. In the SDP, you can specify the
SSRC for a media stream as described in RFC 5576 - Source-Specific Media
Attributes in the Session Description Protocol (SDP). I am not sure if
there are many existing implementations that do this.

Cheers,
Charles

> -----Original Message-----
> From: Paul Kyzivat (pkyzivat)
> Sent: Tuesday, March 29, 2011 11:41 PM
> To: Charles Eckel (eckelcu)
> Cc: Leon Portman; Parthasarathi R (partr); siprec@ietf.org
> Subject: Re: [siprec] Multiplexing different participants' streams on
the same port
>=20
> Charles,
>=20
> *In practice* how are cnames set for sip calls?
> I'm assuming they are something canned and unrelated to the signaling
> identity.
>=20
> 	Thanks,
> 	Paul
>=20
> On 3/29/2011 10:20 AM, Charles Eckel (eckelcu) wrote:
> > For the format and value of the CNAME, I suggest having a look at
> > "Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names
> > (CNAMEs)", draft-ietf-avt-rtp-cnames-05.
> > If the SIP AOR is meant to be the AOR registered by the participant,
> > this is almost certainly going to be something different.
> > The participant AOR is per participant. The CNAME is per media
stream.
> >
> > Cheers,
> > Charles
> >
> >> -----Original Message-----
> >> From: Paul Kyzivat (pkyzivat)
> >> Sent: Tuesday, March 29, 2011 2:23 PM
> >> To: Leon Portman
> >> Cc: Parthasarathi R (partr); Charles Eckel (eckelcu);
siprec@ietf.org
> >> Subject: Re: [siprec] Multiplexing different participants' streams
on
> > the same port
> >>
> >>
> >>
> >> On 3/29/2011 7:21 AM, Leon Portman wrote:
> >>> I like it.
> >>>
> >>> Quick question. In metadata we are using "<aor>" attribute but in
> > SDP, it is "CNAME"? Can we use the
> >> same?
> >>
> >> Charles knows more than I about RTP. AFAIK CNAME is an essentially
> >> arbitrary string that is assigned by the media source. (Are their
> >> constraints on its length or format?) Perhaps it could be formatted
as
> > a
> >> sip AOR, perhaps not. Even if it *could*, in practice *will* it be?
> > ISTM
> >> it would not be wise to count on these being the same.
> >>
> >> We should probably allow participants to specify their cname as
well
> > as
> >> their AOR. This may get complicated if the same participant ends up
> > with
> >> differing media streams it sends.
> >>
> >> I also wonder if the SRC will always know the CNAMEs of the
streams. I
> >> suspect we can't count on that.
> >>
> >> 	Thanks,
> >> 	Paul
> >>
> >>> Leon
> >>>
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Parthasarathi R (partr)
> >>> Sent: Monday, March 28, 2011 10:42 AM
> >>> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat);
> > siprec@ietf.org
> >>> Subject: Re: [siprec] Multiplexing different participants' streams
> > on the same port
> >>>
> >>> Charles,
> >>>
> >>> IMO, the current metadata model helps to address RTP MUX streams
as
> > well. In terms of model,
> >> multiple participants (P1, P2, P3) metadata block points to the
single
> > stream (S1) and stream block
> >> contains SSRC&   CSRC information. IOW, SIPREC model abstract RTP
MUX
> > stream within media stream block.
> >> Please let me know in case you feel that model does not address it.
> >>>
> >>> In case of metadata format, multiple "participant" elements have
> > send element with single stream
> >> element. The stream element has a label attribute which points to
the
> > m-line which contains "ssrc"
> >> attribute with CNAME parameter. I attached the example for your
> > reference and The example is the one
> >> of the way to represent RTP-MUX stream in the metadata format.
Please
> > let me know the issues with this
> >> format and example.
> >>>
> >>> I agree with Paul and you that we need to understand how RTP mux
> > stream will be standardized but
> >> IMO, it is not the limiting factor for SIPREC as of now.
> >>>
> >>> Thanks
> >>> Partha
> >>>
> >>> -----Original Message-----
> >>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Charles Eckel (eckelcu)
> >>> Sent: Friday, March 18, 2011 8:40 PM
> >>> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
> >>> Subject: Re: [siprec] Multiplexing different participants' streams
> > on thesame port
> >>>
> >>> I agree with the comment regarding CLUE, so let me take a simpler
> > example, and audio mixer. This
> >> mixer may mix the audio from multiple participants.
> >>>
> >>> Participant 1 (P1)
> >>> Participant 2 (P2)
> >>> Participant 3 (P3)
> >>>
> >>> P1 sends audio stream with SSRC-P1
> >>> P2 sends audio stream with SSCR-P2
> >>> P2 sends audio stream with SSCR-P3
> >>>
> >>> MixerA(Ma)
> >>>
> >>> Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
> >>> SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
> >>> The SRC sends this stream to the SRS for recording. I suspect it
> > might change the SSRC to be SSRC-
> >> SRC but maintain the CSRC information identifying P1/P2/P3.
> >>> I expect this would be modeled as a single stream with 3
> > participants P1, P2, P3. The mapping of P1
> >> to SSRC-P1 is captured in the RTCP data sent by SRC to SRS. In this
> > case, there is no need to anything
> >> in the metadata.
> >>> However, if the CSRCs are not propagated all the way to the SRS,
> > then perhaps participant info would
> >> need to be communicated via the metadata.
> >>>
> >>> Note, I do not pretend to have this all figured out; rather, I am
> > putting out some ideas to see if
> >> this gels with what others have in mind.
> >>>
> >>> Cheers,
> >>> Charles
> >>>
> >>>> -----Original Message-----
> >>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> >>> Behalf Of Paul Kyzivat (pkyzivat)
> >>>> Sent: Friday, March 18, 2011 5:38 AM
> >>>> To: siprec@ietf.org
> >>>> Subject: Re: [siprec] Multiplexing different participants'
streams
> > on
> >>> the same port
> >>>>
> >>>> I don't know if this is a good idea or not. But if we want to
> > consider
> >>>
> >>>> it, then we should probably enter into some discussion with CLUE,
> > to
> >>> see
> >>>> if there is any commonality.
> >>>>
> >>>> Over in CLUE, this mixing of multiple streams over one RTP
session
> > has
> >>>
> >>>> been brought up because it is a technique used in existing
> > proprietary
> >>>
> >>>> products. But the CLUE wg isn't yet to a point where it is ready
to
> >>>> decide if this will be a requirement. And the AVT people have
> > strong
> >>>> opinions on what is/isn't appropriate.
> >>>>
> >>>> 	Thanks,
> >>>> 	Paul
> >>>>
> >>>> On 3/18/2011 4:11 AM, Elwell, John wrote:
> >>>>> Something Charles mentioned in another thread triggered me to
> > raise
> >>> this.
> >>>>>
> >>>>> We consider different participants in the CS as potentially
> >>> producing separate media streams that
> >>>> the SRC sends to the SRS, where the SRC can send them mixed or
> >>> unmixed.
> >>>>>
> >>>>> When sending them unmixed, up till now I think we have
considered
> >>> sending them to separate ports on
> >>>> the SRS and identifying them as separate m=3D lines in the SDP.
> > Another
> >>> possibility might be to
> >>>> multiplex the different streams on the same port and identify
them
> > by
> >>> different SSRC values. I am not
> >>>> sure whether this would be a correct use of SSRC, and I suspect
we
> >>> would need to check with AVTCORE.
> >>>> Recent discussions in other contexts (telepresence, RTC-Web) have
> > also
> >>> drawn my attention to such
> >>>> possibilities. See also
> >>> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
> >>>>>
> >>>>> Of course, it would mean that we would have to rethink how we
> >>> reference the different streams from
> >>>> metadata.
> >>>>>
> >>>>> I am not necessarily proposing such a change - I just want to
make
> >>> sure we have given it due
> >>>> consideration.
> >>>>>
> >>>>> John (as individual)
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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
> >>>
> >

From pkyzivat@cisco.com  Tue Mar 29 15:12:19 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 81F563A68A9 for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 15:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z7lddYR+03gS for <siprec@core3.amsl.com>; Tue, 29 Mar 2011 15:12:18 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 6644228C0DB for <siprec@ietf.org>; Tue, 29 Mar 2011 15:12:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=9376; q=dns/txt; s=iport; t=1301436836; x=1302646436; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ah0XxLuPcjLV9ZfbbbYtMLid15vOpcAphsPkoI+v2as=; b=JE8Q1c9BFGakSWv9009/4/fr4S5wR3lws65RrjQ6AgPof2fJ4M7WwtJB 8sLdGoQ6ol5UE4+v6c4qfiPfyiOXPOKaIuI2TzUJ9H507IIWy88bPre/1 hpC0dmVZgTTyD3kYhB85w0x7h/dIIWXziPOJFEvMQ9R0og8FCyEFibT0c A=;
X-IronPort-AV: E=Sophos;i="4.63,265,1299456000"; d="scan'208";a="23695755"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 29 Mar 2011 22:13:55 +0000
Received: from [10.61.105.172] (dhcp-10-61-105-172.cisco.com [10.61.105.172]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2TMDtoi021684; Tue, 29 Mar 2011 22:13:55 GMT
Message-ID: <4D9259A3.9080908@cisco.com>
Date: Tue, 29 Mar 2011 18:13:55 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com>	<E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com> <4D91CF3F.1010809@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com> <4D9251D0.5020006@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: siprec@ietf.org, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 22:12:19 -0000

On 3/29/2011 6:05 PM, Charles Eckel (eckelcu) wrote:
> Typically they appear in RTCP only, and not in SIP or SDP.

I understand that.

I'm just wondering what is done by typical sip devices that handle both 
media and signaling - e.g. phones and gateways. Presumably *something* 
is put in for the cname. But I suspect that layering will result in the 
media layer doing its own thing without knowledge of what sort of names 
are being used in the signaling layer.

If so, just reporting the cname in the metadata might not provide any 
benefit if it can't be correlated with some signaling name.

	Thanks,
	Paul

  The RTCP
> identify the mapping of CNAME to SSRC. In the SDP, you can specify the
> SSRC for a media stream as described in RFC 5576 - Source-Specific Media
> Attributes in the Session Description Protocol (SDP). I am not sure if
> there are many existing implementations that do this.
>
> Cheers,
> Charles
>
>> -----Original Message-----
>> From: Paul Kyzivat (pkyzivat)
>> Sent: Tuesday, March 29, 2011 11:41 PM
>> To: Charles Eckel (eckelcu)
>> Cc: Leon Portman; Parthasarathi R (partr); siprec@ietf.org
>> Subject: Re: [siprec] Multiplexing different participants' streams on
> the same port
>>
>> Charles,
>>
>> *In practice* how are cnames set for sip calls?
>> I'm assuming they are something canned and unrelated to the signaling
>> identity.
>>
>> 	Thanks,
>> 	Paul
>>
>> On 3/29/2011 10:20 AM, Charles Eckel (eckelcu) wrote:
>>> For the format and value of the CNAME, I suggest having a look at
>>> "Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names
>>> (CNAMEs)", draft-ietf-avt-rtp-cnames-05.
>>> If the SIP AOR is meant to be the AOR registered by the participant,
>>> this is almost certainly going to be something different.
>>> The participant AOR is per participant. The CNAME is per media
> stream.
>>>
>>> Cheers,
>>> Charles
>>>
>>>> -----Original Message-----
>>>> From: Paul Kyzivat (pkyzivat)
>>>> Sent: Tuesday, March 29, 2011 2:23 PM
>>>> To: Leon Portman
>>>> Cc: Parthasarathi R (partr); Charles Eckel (eckelcu);
> siprec@ietf.org
>>>> Subject: Re: [siprec] Multiplexing different participants' streams
> on
>>> the same port
>>>>
>>>>
>>>>
>>>> On 3/29/2011 7:21 AM, Leon Portman wrote:
>>>>> I like it.
>>>>>
>>>>> Quick question. In metadata we are using "<aor>" attribute but in
>>> SDP, it is "CNAME"? Can we use the
>>>> same?
>>>>
>>>> Charles knows more than I about RTP. AFAIK CNAME is an essentially
>>>> arbitrary string that is assigned by the media source. (Are their
>>>> constraints on its length or format?) Perhaps it could be formatted
> as
>>> a
>>>> sip AOR, perhaps not. Even if it *could*, in practice *will* it be?
>>> ISTM
>>>> it would not be wise to count on these being the same.
>>>>
>>>> We should probably allow participants to specify their cname as
> well
>>> as
>>>> their AOR. This may get complicated if the same participant ends up
>>> with
>>>> differing media streams it sends.
>>>>
>>>> I also wonder if the SRC will always know the CNAMEs of the
> streams. I
>>>> suspect we can't count on that.
>>>>
>>>> 	Thanks,
>>>> 	Paul
>>>>
>>>>> Leon
>>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf Of Parthasarathi R (partr)
>>>>> Sent: Monday, March 28, 2011 10:42 AM
>>>>> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat);
>>> siprec@ietf.org
>>>>> Subject: Re: [siprec] Multiplexing different participants' streams
>>> on the same port
>>>>>
>>>>> Charles,
>>>>>
>>>>> IMO, the current metadata model helps to address RTP MUX streams
> as
>>> well. In terms of model,
>>>> multiple participants (P1, P2, P3) metadata block points to the
> single
>>> stream (S1) and stream block
>>>> contains SSRC&    CSRC information. IOW, SIPREC model abstract RTP
> MUX
>>> stream within media stream block.
>>>> Please let me know in case you feel that model does not address it.
>>>>>
>>>>> In case of metadata format, multiple "participant" elements have
>>> send element with single stream
>>>> element. The stream element has a label attribute which points to
> the
>>> m-line which contains "ssrc"
>>>> attribute with CNAME parameter. I attached the example for your
>>> reference and The example is the one
>>>> of the way to represent RTP-MUX stream in the metadata format.
> Please
>>> let me know the issues with this
>>>> format and example.
>>>>>
>>>>> I agree with Paul and you that we need to understand how RTP mux
>>> stream will be standardized but
>>>> IMO, it is not the limiting factor for SIPREC as of now.
>>>>>
>>>>> Thanks
>>>>> Partha
>>>>>
>>>>> -----Original Message-----
>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>> Behalf Of Charles Eckel (eckelcu)
>>>>> Sent: Friday, March 18, 2011 8:40 PM
>>>>> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
>>>>> Subject: Re: [siprec] Multiplexing different participants' streams
>>> on thesame port
>>>>>
>>>>> I agree with the comment regarding CLUE, so let me take a simpler
>>> example, and audio mixer. This
>>>> mixer may mix the audio from multiple participants.
>>>>>
>>>>> Participant 1 (P1)
>>>>> Participant 2 (P2)
>>>>> Participant 3 (P3)
>>>>>
>>>>> P1 sends audio stream with SSRC-P1
>>>>> P2 sends audio stream with SSCR-P2
>>>>> P2 sends audio stream with SSCR-P3
>>>>>
>>>>> MixerA(Ma)
>>>>>
>>>>> Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
>>>>> SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
>>>>> The SRC sends this stream to the SRS for recording. I suspect it
>>> might change the SSRC to be SSRC-
>>>> SRC but maintain the CSRC information identifying P1/P2/P3.
>>>>> I expect this would be modeled as a single stream with 3
>>> participants P1, P2, P3. The mapping of P1
>>>> to SSRC-P1 is captured in the RTCP data sent by SRC to SRS. In this
>>> case, there is no need to anything
>>>> in the metadata.
>>>>> However, if the CSRCs are not propagated all the way to the SRS,
>>> then perhaps participant info would
>>>> need to be communicated via the metadata.
>>>>>
>>>>> Note, I do not pretend to have this all figured out; rather, I am
>>> putting out some ideas to see if
>>>> this gels with what others have in mind.
>>>>>
>>>>> Cheers,
>>>>> Charles
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>> Behalf Of Paul Kyzivat (pkyzivat)
>>>>>> Sent: Friday, March 18, 2011 5:38 AM
>>>>>> To: siprec@ietf.org
>>>>>> Subject: Re: [siprec] Multiplexing different participants'
> streams
>>> on
>>>>> the same port
>>>>>>
>>>>>> I don't know if this is a good idea or not. But if we want to
>>> consider
>>>>>
>>>>>> it, then we should probably enter into some discussion with CLUE,
>>> to
>>>>> see
>>>>>> if there is any commonality.
>>>>>>
>>>>>> Over in CLUE, this mixing of multiple streams over one RTP
> session
>>> has
>>>>>
>>>>>> been brought up because it is a technique used in existing
>>> proprietary
>>>>>
>>>>>> products. But the CLUE wg isn't yet to a point where it is ready
> to
>>>>>> decide if this will be a requirement. And the AVT people have
>>> strong
>>>>>> opinions on what is/isn't appropriate.
>>>>>>
>>>>>> 	Thanks,
>>>>>> 	Paul
>>>>>>
>>>>>> On 3/18/2011 4:11 AM, Elwell, John wrote:
>>>>>>> Something Charles mentioned in another thread triggered me to
>>> raise
>>>>> this.
>>>>>>>
>>>>>>> We consider different participants in the CS as potentially
>>>>> producing separate media streams that
>>>>>> the SRC sends to the SRS, where the SRC can send them mixed or
>>>>> unmixed.
>>>>>>>
>>>>>>> When sending them unmixed, up till now I think we have
> considered
>>>>> sending them to separate ports on
>>>>>> the SRS and identifying them as separate m= lines in the SDP.
>>> Another
>>>>> possibility might be to
>>>>>> multiplex the different streams on the same port and identify
> them
>>> by
>>>>> different SSRC values. I am not
>>>>>> sure whether this would be a correct use of SSRC, and I suspect
> we
>>>>> would need to check with AVTCORE.
>>>>>> Recent discussions in other contexts (telepresence, RTC-Web) have
>>> also
>>>>> drawn my attention to such
>>>>>> possibilities. See also
>>>>> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
>>>>>>>
>>>>>>> Of course, it would mean that we would have to rethink how we
>>>>> reference the different streams from
>>>>>> metadata.
>>>>>>>
>>>>>>> I am not necessarily proposing such a change - I just want to
> make
>>>>> sure we have given it due
>>>>>> consideration.
>>>>>>>
>>>>>>> John (as individual)
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>
>

From john.elwell@siemens-enterprise.com  Wed Mar 30 01:59:06 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 036093A694C for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 01:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eseyOenq1f94 for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 01:59:05 -0700 (PDT)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id BEF173A6957 for <siprec@ietf.org>; Wed, 30 Mar 2011 01:59:04 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3928464; Wed, 30 Mar 2011 11:00:38 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 8E2E91EB82B4; Wed, 30 Mar 2011 11:00:38 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 30 Mar 2011 11:00:38 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Wed, 30 Mar 2011 11:00:38 +0200
Thread-Topic: [siprec] comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhgBO/qTgAD5pH0AAJpm4YA==
Message-ID: <A444A0F8084434499206E78C106220CA0875AF36FF@MCHP058A.global-ad.net>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Mar 2011 08:59:06 -0000

=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel (eckelcu)
> Sent: 29 March 2011 15:38
> To: Parthasarathi R (partr); siprec@ietf.org
> Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> Hi Partha,
>=20
> Thanks for your response. This addresses all of my concerns.=20
> Please see
> one additional clarification inline.=20
>=20
> > -----Original Message-----
> > From: Parthasarathi R (partr)
> > Sent: Tuesday, March 29, 2011 10:31 AM
> > To: Charles Eckel (eckelcu); siprec@ietf.org
> > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> >=20
> > Charles,
> >=20
> > Thanks for review the document. Please read inline.
> >=20
> > Thanks
> > Partha
> >=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Charles Eckel (eckelcu)
> > Sent: Sunday, March 27, 2011 12:35 AM
> > To: siprec@ietf.org
> > Subject: [siprec] comments on draft-ram-siprec-metadata-04
> >=20
> > I gave the draft and read and have the following comments.
> >=20
> > Section 3. Think the metadata describes the recording=20
> session, not the
> communication session. Replace
> > "metamodel" with "metadata model", and "MAY be conveyed in Recording
> Session" with "MAY be conveyed
> > within the Recording Session", and "time a change occurred by be
> assumed" with "time a change occurred
> > may be assumed".
[JRE] I am not sure exactly what text Charles was commenting on, but in my =
opinion metadata describes a CS (and how media streams in the RS relate to =
that CS), rather than describing the RS.

John (as individual)



> >=20
> > Section 4, suggest rewording as, "The section describes each element
> of the metadata model, and the
> > attributes of each element. This section also describes how the
> different elements are associated."
> >=20
> > Section 4.1, RecordingRequestorID is not really an ID, it=20
> is more of a
> type. I think
> > RecordingRequestor is more appropriate.
> >=20
> >=20
> > <Partha>Agreed. We will update in the next revision </partha>
> >=20
> >  That said, I think you also need a unique ID for the Recording
> Session, right?
> > <partha>  Please clarify whether you are interested in AOR of RS or
> just ID. In the model, Recording
> > (1..*) is related to CSG (0..*) and there is no need of separate
> attribute for unique id. In the
> > metadata format, URN UUID in CSG (group) & recording exist=20
> which helps
> to visualize the association
> > </partha>
>=20
> I am assuming there is a need to distinguish one RS from=20
> another RS, and
> that is the reason I was recommending adding a unique ID.=20
> This ID would
> not be the RS AOR as that may not be unique.
>=20
> Cheers,
> Charles
>=20
> > Section 4.2.1, replace "SRC (or MAY be SRS)" with "SRC or SRS".
> > <Partha>Agreed. We will update in the next revision </partha>
> >=20
> > Section 4.3.2, why does a CS need two participants or more?=20
> What about
> studio mode recording?
> >=20
> > Section 4.4.1, what is participant type and what is its use, or why
> needed?
> > <partha> This attribute has to be removed as per the last interim
> meeting. We will update in the next
> > revision. </partha>
> >=20
> > Section 4.5, I think Media Stream requires a unique ID attribute as
> well.
> > <partha> As mentioned above in the model draft, the association
> between CS and participant is shown.
> > In terms of format draft, it is represented by URN UUID </partha>
> > Is the "Media Stream Reference" the SDP label attribute?
> > <partha> Your understanding is correct </partha>
> >=20
> >=20
> > Thanks,
> > Charles
> >=20
> >=20
> >=20
> > _______________________________________________
> > 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
> =

From partr@cisco.com  Wed Mar 30 04:18:54 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 344CC3A6961 for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 04:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.079
X-Spam-Level: 
X-Spam-Status: No, score=-10.079 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egB4uVyJKycM for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 04:18:52 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 644DF3A6947 for <siprec@ietf.org>; Wed, 30 Mar 2011 04:18:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=3746; q=dns/txt; s=iport; t=1301484031; x=1302693631; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=TolDCnRluuH8eAJ7U6I7GPJWPPABe6arFeDaxMdo6Ts=; b=TYsZfScvxP7PRz9mRtq2ROp2KtX+iStVC6ZNyJ2HeE+0WW2vxCM7rMLD 4XN7f6zbEHacAuBktwiROjYCiiSrn4P2SH0wZKo+6Q+6GoUl6PaMofKqx NDws559XLGRbTZ7iqNzfxt4f8yXU0xUw48nbvNfhU/ZazazkR9/Ism9+5 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As4AABARk02Q/khMgWdsb2JhbACYEY09FAEBFiYliHmYa5xXhWoEhT2LJA
X-IronPort-AV: E=Sophos;i="4.63,268,1299456000"; d="scan'208";a="23782913"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 30 Mar 2011 11:20:30 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2UBKSgc002952 for <siprec@ietf.org>; Wed, 30 Mar 2011 11:20:30 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Mar 2011 16:50:28 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 30 Mar 2011 16:50:27 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904E9762C@XMB-BGL-411.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhgBO/qTgAD5pH0AAKwBdgA==
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 30 Mar 2011 11:20:28.0946 (UTC) FILETIME=[79817F20:01CBEECC]
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Mar 2011 11:18:54 -0000

Charles,

Please read inline

Thanks
Partha=20

-----Original Message-----
From: Charles Eckel (eckelcu)=20
Sent: Tuesday, March 29, 2011 8:08 PM
To: Parthasarathi R (partr); 'siprec@ietf.org'
Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04

Hi Partha,

Thanks for your response. This addresses all of my concerns. Please see
one additional clarification inline.=20

> -----Original Message-----
> From: Parthasarathi R (partr)
> Sent: Tuesday, March 29, 2011 10:31 AM
> To: Charles Eckel (eckelcu); siprec@ietf.org
> Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> Charles,
>=20
> Thanks for review the document. Please read inline.
>=20
> Thanks
> Partha
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> Behalf Of Charles Eckel (eckelcu)
> Sent: Sunday, March 27, 2011 12:35 AM
> To: siprec@ietf.org
> Subject: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> I gave the draft and read and have the following comments.
>=20
> Section 3. Think the metadata describes the recording session, not the

> communication session. Replace "metamodel" with "metadata model", and=20
> "MAY be conveyed in Recording Session" with "MAY be conveyed within=20
> the Recording Session", and "time a change occurred by be assumed"
with "time a change occurred may be assumed".
>=20
> Section 4, suggest rewording as, "The section describes each element=20
> of the metadata model, and the attributes of each element. This
section also describes how the different elements are associated."
>=20
> Section 4.1, RecordingRequestorID is not really an ID, it is more of a

> type. I think RecordingRequestor is more appropriate.
>=20
>=20
> <Partha>Agreed. We will update in the next revision </partha>
>=20
>  That said, I think you also need a unique ID for the Recording
Session, right?
> <partha>  Please clarify whether you are interested in AOR of RS or=20
> just ID. In the model, Recording
> (1..*) is related to CSG (0..*) and there is no need of separate=20
> attribute for unique id. In the metadata format, URN UUID in CSG=20
> (group) & recording exist which helps to visualize the association=20
> </partha>

I am assuming there is a need to distinguish one RS from another RS, and
that is the reason I was recommending adding a unique ID.=20

<Partha> The next revision will be updated with "unique ID" attribute in
the recording session block.

In the metadata format, each recording element is uniquely identified by
having URN UUID recording attribute. </Partha>=20

This ID would not be the RS AOR as that may not be unique.

Cheers,
Charles

> Section 4.2.1, replace "SRC (or MAY be SRS)" with "SRC or SRS".
> <Partha>Agreed. We will update in the next revision </partha>
>=20
> Section 4.3.2, why does a CS need two participants or more? What about
studio mode recording?
>=20
> Section 4.4.1, what is participant type and what is its use, or why
needed?
> <partha> This attribute has to be removed as per the last interim=20
> meeting. We will update in the next revision. </partha>
>=20
> Section 4.5, I think Media Stream requires a unique ID attribute as
well.
> <partha> As mentioned above in the model draft, the association
between CS and participant is shown.
> In terms of format draft, it is represented by URN UUID </partha> Is=20
> the "Media Stream Reference" the SDP label attribute?
> <partha> Your understanding is correct </partha>
>=20
>=20
> Thanks,
> Charles
>=20
>=20
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From HKaplan@acmepacket.com  Wed Mar 30 05:56:36 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99DA328C12F for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 05:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.089
X-Spam-Level: 
X-Spam-Status: No, score=-0.089 tagged_above=-999 required=5 tests=[AWL=-1.389, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id stwZ5ko0+sIE for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 05:56:35 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 120953A6A1C for <siprec@ietf.org>; Wed, 30 Mar 2011 05:56:35 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 30 Mar 2011 08:58:13 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Wed, 30 Mar 2011 08:58:13 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Date: Wed, 30 Mar 2011 08:58:11 -0400
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: Acvu2iDEP0/GCHfoQNiJ2FdGZI6pDA==
Message-ID: <2C2317AF-C679-4977-9150-EF99B6FC3B4B@acmepacket.com>
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com> <4D91CF3F.1010809@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com> <4D9251D0.5020006@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com> <4D9259A3.9080908@cisco.com>
In-Reply-To: <4D9259A3.9080908@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAUA=
Cc: "siprec@ietf.org" <siprec@ietf.org>, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Mar 2011 12:56:36 -0000

In practice we see all kinds of things in the RTCP cname, often unrelated t=
o signaling info.
But you can't rely on it anyway, since you can't rely on there being any RT=
CP.

Furthermore, although I've (shockingly) seen some devices indicate SSRC in =
SDP per RFC 5576, it's rare... which means you won't know the SSRC at call =
setup time, so it won't be available to send in metadata at that time, requ=
iring an update.

I humbly suggest that UDP port numbers are not in short supply, and using o=
ne per stream is both simple and effective.

-hadriel


On Mar 29, 2011, at 6:13 PM, Paul Kyzivat wrote:

> On 3/29/2011 6:05 PM, Charles Eckel (eckelcu) wrote:
>> Typically they appear in RTCP only, and not in SIP or SDP.
>=20
> I understand that.
>=20
> I'm just wondering what is done by typical sip devices that handle both
> media and signaling - e.g. phones and gateways. Presumably *something*
> is put in for the cname. But I suspect that layering will result in the
> media layer doing its own thing without knowledge of what sort of names
> are being used in the signaling layer.
>=20
> If so, just reporting the cname in the metadata might not provide any
> benefit if it can't be correlated with some signaling name.
>=20
>        Thanks,
>        Paul
>=20
>  The RTCP
>> identify the mapping of CNAME to SSRC. In the SDP, you can specify the
>> SSRC for a media stream as described in RFC 5576 - Source-Specific Media
>> Attributes in the Session Description Protocol (SDP). I am not sure if
>> there are many existing implementations that do this.
>>=20
>> Cheers,
>> Charles
>>=20
>>> -----Original Message-----
>>> From: Paul Kyzivat (pkyzivat)
>>> Sent: Tuesday, March 29, 2011 11:41 PM
>>> To: Charles Eckel (eckelcu)
>>> Cc: Leon Portman; Parthasarathi R (partr); siprec@ietf.org
>>> Subject: Re: [siprec] Multiplexing different participants' streams on
>> the same port
>>>=20
>>> Charles,
>>>=20
>>> *In practice* how are cnames set for sip calls?
>>> I'm assuming they are something canned and unrelated to the signaling
>>> identity.
>>>=20
>>>     Thanks,
>>>     Paul
>>>=20
>>> On 3/29/2011 10:20 AM, Charles Eckel (eckelcu) wrote:
>>>> For the format and value of the CNAME, I suggest having a look at
>>>> "Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names
>>>> (CNAMEs)", draft-ietf-avt-rtp-cnames-05.
>>>> If the SIP AOR is meant to be the AOR registered by the participant,
>>>> this is almost certainly going to be something different.
>>>> The participant AOR is per participant. The CNAME is per media
>> stream.
>>>>=20
>>>> Cheers,
>>>> Charles
>>>>=20
>>>>> -----Original Message-----
>>>>> From: Paul Kyzivat (pkyzivat)
>>>>> Sent: Tuesday, March 29, 2011 2:23 PM
>>>>> To: Leon Portman
>>>>> Cc: Parthasarathi R (partr); Charles Eckel (eckelcu);
>> siprec@ietf.org
>>>>> Subject: Re: [siprec] Multiplexing different participants' streams
>> on
>>>> the same port
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> On 3/29/2011 7:21 AM, Leon Portman wrote:
>>>>>> I like it.
>>>>>>=20
>>>>>> Quick question. In metadata we are using "<aor>" attribute but in
>>>> SDP, it is "CNAME"? Can we use the
>>>>> same?
>>>>>=20
>>>>> Charles knows more than I about RTP. AFAIK CNAME is an essentially
>>>>> arbitrary string that is assigned by the media source. (Are their
>>>>> constraints on its length or format?) Perhaps it could be formatted
>> as
>>>> a
>>>>> sip AOR, perhaps not. Even if it *could*, in practice *will* it be?
>>>> ISTM
>>>>> it would not be wise to count on these being the same.
>>>>>=20
>>>>> We should probably allow participants to specify their cname as
>> well
>>>> as
>>>>> their AOR. This may get complicated if the same participant ends up
>>>> with
>>>>> differing media streams it sends.
>>>>>=20
>>>>> I also wonder if the SRC will always know the CNAMEs of the
>> streams. I
>>>>> suspect we can't count on that.
>>>>>=20
>>>>>   Thanks,
>>>>>   Paul
>>>>>=20
>>>>>> Leon
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>> Behalf Of Parthasarathi R (partr)
>>>>>> Sent: Monday, March 28, 2011 10:42 AM
>>>>>> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat);
>>>> siprec@ietf.org
>>>>>> Subject: Re: [siprec] Multiplexing different participants' streams
>>>> on the same port
>>>>>>=20
>>>>>> Charles,
>>>>>>=20
>>>>>> IMO, the current metadata model helps to address RTP MUX streams
>> as
>>>> well. In terms of model,
>>>>> multiple participants (P1, P2, P3) metadata block points to the
>> single
>>>> stream (S1) and stream block
>>>>> contains SSRC&    CSRC information. IOW, SIPREC model abstract RTP
>> MUX
>>>> stream within media stream block.
>>>>> Please let me know in case you feel that model does not address it.
>>>>>>=20
>>>>>> In case of metadata format, multiple "participant" elements have
>>>> send element with single stream
>>>>> element. The stream element has a label attribute which points to
>> the
>>>> m-line which contains "ssrc"
>>>>> attribute with CNAME parameter. I attached the example for your
>>>> reference and The example is the one
>>>>> of the way to represent RTP-MUX stream in the metadata format.
>> Please
>>>> let me know the issues with this
>>>>> format and example.
>>>>>>=20
>>>>>> I agree with Paul and you that we need to understand how RTP mux
>>>> stream will be standardized but
>>>>> IMO, it is not the limiting factor for SIPREC as of now.
>>>>>>=20
>>>>>> Thanks
>>>>>> Partha
>>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>> Behalf Of Charles Eckel (eckelcu)
>>>>>> Sent: Friday, March 18, 2011 8:40 PM
>>>>>> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
>>>>>> Subject: Re: [siprec] Multiplexing different participants' streams
>>>> on thesame port
>>>>>>=20
>>>>>> I agree with the comment regarding CLUE, so let me take a simpler
>>>> example, and audio mixer. This
>>>>> mixer may mix the audio from multiple participants.
>>>>>>=20
>>>>>> Participant 1 (P1)
>>>>>> Participant 2 (P2)
>>>>>> Participant 3 (P3)
>>>>>>=20
>>>>>> P1 sends audio stream with SSRC-P1
>>>>>> P2 sends audio stream with SSCR-P2
>>>>>> P2 sends audio stream with SSCR-P3
>>>>>>=20
>>>>>> MixerA(Ma)
>>>>>>=20
>>>>>> Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
>>>>>> SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
>>>>>> The SRC sends this stream to the SRS for recording. I suspect it
>>>> might change the SSRC to be SSRC-
>>>>> SRC but maintain the CSRC information identifying P1/P2/P3.
>>>>>> I expect this would be modeled as a single stream with 3
>>>> participants P1, P2, P3. The mapping of P1
>>>>> to SSRC-P1 is captured in the RTCP data sent by SRC to SRS. In this
>>>> case, there is no need to anything
>>>>> in the metadata.
>>>>>> However, if the CSRCs are not propagated all the way to the SRS,
>>>> then perhaps participant info would
>>>>> need to be communicated via the metadata.
>>>>>>=20
>>>>>> Note, I do not pretend to have this all figured out; rather, I am
>>>> putting out some ideas to see if
>>>>> this gels with what others have in mind.
>>>>>>=20
>>>>>> Cheers,
>>>>>> Charles
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
>>>>>> Behalf Of Paul Kyzivat (pkyzivat)
>>>>>>> Sent: Friday, March 18, 2011 5:38 AM
>>>>>>> To: siprec@ietf.org
>>>>>>> Subject: Re: [siprec] Multiplexing different participants'
>> streams
>>>> on
>>>>>> the same port
>>>>>>>=20
>>>>>>> I don't know if this is a good idea or not. But if we want to
>>>> consider
>>>>>>=20
>>>>>>> it, then we should probably enter into some discussion with CLUE,
>>>> to
>>>>>> see
>>>>>>> if there is any commonality.
>>>>>>>=20
>>>>>>> Over in CLUE, this mixing of multiple streams over one RTP
>> session
>>>> has
>>>>>>=20
>>>>>>> been brought up because it is a technique used in existing
>>>> proprietary
>>>>>>=20
>>>>>>> products. But the CLUE wg isn't yet to a point where it is ready
>> to
>>>>>>> decide if this will be a requirement. And the AVT people have
>>>> strong
>>>>>>> opinions on what is/isn't appropriate.
>>>>>>>=20
>>>>>>> Thanks,
>>>>>>> Paul
>>>>>>>=20
>>>>>>> On 3/18/2011 4:11 AM, Elwell, John wrote:
>>>>>>>> Something Charles mentioned in another thread triggered me to
>>>> raise
>>>>>> this.
>>>>>>>>=20
>>>>>>>> We consider different participants in the CS as potentially
>>>>>> producing separate media streams that
>>>>>>> the SRC sends to the SRS, where the SRC can send them mixed or
>>>>>> unmixed.
>>>>>>>>=20
>>>>>>>> When sending them unmixed, up till now I think we have
>> considered
>>>>>> sending them to separate ports on
>>>>>>> the SRS and identifying them as separate m=3D lines in the SDP.
>>>> Another
>>>>>> possibility might be to
>>>>>>> multiplex the different streams on the same port and identify
>> them
>>>> by
>>>>>> different SSRC values. I am not
>>>>>>> sure whether this would be a correct use of SSRC, and I suspect
>> we
>>>>>> would need to check with AVTCORE.
>>>>>>> Recent discussions in other contexts (telepresence, RTC-Web) have
>>>> also
>>>>>> drawn my attention to such
>>>>>>> possibilities. See also
>>>>>> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
>>>>>>>>=20
>>>>>>>> Of course, it would mean that we would have to rethink how we
>>>>>> reference the different streams from
>>>>>>> metadata.
>>>>>>>>=20
>>>>>>>> I am not necessarily proposing such a change - I just want to
>> make
>>>>>> sure we have given it due
>>>>>>> consideration.
>>>>>>>>=20
>>>>>>>> John (as individual)
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> _______________________________________________
>>>>>>>> siprec mailing list
>>>>>>>> siprec@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>=20
>>>>=20
>>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From john.elwell@siemens-enterprise.com  Wed Mar 30 07:54:48 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A897D3A6A1F for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 07:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.636
X-Spam-Level: 
X-Spam-Status: No, score=-100.636 tagged_above=-999 required=5 tests=[AWL=-1.936, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74GAz0EwWo3z for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 07:54:47 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id A97D33A6983 for <siprec@ietf.org>; Wed, 30 Mar 2011 07:54:43 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3952211; Wed, 30 Mar 2011 16:56:21 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id C10FD23F0294; Wed, 30 Mar 2011 16:56:21 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Wed, 30 Mar 2011 16:56:21 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Wed, 30 Mar 2011 16:56:20 +0200
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: Acvu2iDEP0/GCHfoQNiJ2FdGZI6pDAAEB0yw
Message-ID: <A444A0F8084434499206E78C106220CA0875AF3984@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com> <4D91CF3F.1010809@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com> <4D9251D0.5020006@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com> <4D9259A3.9080908@cisco.com> <2C2317AF-C679-4977-9150-EF99B6FC3B4B@acmepacket.com>
In-Reply-To: <2C2317AF-C679-4977-9150-EF99B6FC3B4B@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Mar 2011 14:54:48 -0000

Yes, this was the sort of discussion I was trying to provoke. Of course, SR=
C and SRS implementations will need to be upgraded to support the SIPREC pr=
otocol requirements, so requiring some extra things is not out of the quest=
ion. Clearly one consideration might be whether middleboxes might block suc=
h features?

John (as chair)
=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Hadriel Kaplan
> Sent: 30 March 2011 13:58
> To: Paul Kyzivat
> Cc: siprec@ietf.org; Leon Portman
> Subject: Re: [siprec] Multiplexing different participants'=20
> streams on the same port
>=20
>=20
> In practice we see all kinds of things in the RTCP cname,=20
> often unrelated to signaling info.
> But you can't rely on it anyway, since you can't rely on=20
> there being any RTCP.
>=20
> Furthermore, although I've (shockingly) seen some devices=20
> indicate SSRC in SDP per RFC 5576, it's rare... which means=20
> you won't know the SSRC at call setup time, so it won't be=20
> available to send in metadata at that time, requiring an update.
>=20
> I humbly suggest that UDP port numbers are not in short=20
> supply, and using one per stream is both simple and effective.
>=20
> -hadriel
>=20
>=20
> On Mar 29, 2011, at 6:13 PM, Paul Kyzivat wrote:
>=20
> > On 3/29/2011 6:05 PM, Charles Eckel (eckelcu) wrote:
> >> Typically they appear in RTCP only, and not in SIP or SDP.
> >=20
> > I understand that.
> >=20
> > I'm just wondering what is done by typical sip devices that=20
> handle both
> > media and signaling - e.g. phones and gateways. Presumably=20
> *something*
> > is put in for the cname. But I suspect that layering will=20
> result in the
> > media layer doing its own thing without knowledge of what=20
> sort of names
> > are being used in the signaling layer.
> >=20
> > If so, just reporting the cname in the metadata might not=20
> provide any
> > benefit if it can't be correlated with some signaling name.
> >=20
> >        Thanks,
> >        Paul
> >=20
> >  The RTCP
> >> identify the mapping of CNAME to SSRC. In the SDP, you can=20
> specify the
> >> SSRC for a media stream as described in RFC 5576 -=20
> Source-Specific Media
> >> Attributes in the Session Description Protocol (SDP). I am=20
> not sure if
> >> there are many existing implementations that do this.
> >>=20
> >> Cheers,
> >> Charles
> >>=20
> >>> -----Original Message-----
> >>> From: Paul Kyzivat (pkyzivat)
> >>> Sent: Tuesday, March 29, 2011 11:41 PM
> >>> To: Charles Eckel (eckelcu)
> >>> Cc: Leon Portman; Parthasarathi R (partr); siprec@ietf.org
> >>> Subject: Re: [siprec] Multiplexing different=20
> participants' streams on
> >> the same port
> >>>=20
> >>> Charles,
> >>>=20
> >>> *In practice* how are cnames set for sip calls?
> >>> I'm assuming they are something canned and unrelated to=20
> the signaling
> >>> identity.
> >>>=20
> >>>     Thanks,
> >>>     Paul
> >>>=20
> >>> On 3/29/2011 10:20 AM, Charles Eckel (eckelcu) wrote:
> >>>> For the format and value of the CNAME, I suggest having a look at
> >>>> "Guidelines for Choosing RTP Control Protocol (RTCP)=20
> Canonical Names
> >>>> (CNAMEs)", draft-ietf-avt-rtp-cnames-05.
> >>>> If the SIP AOR is meant to be the AOR registered by the=20
> participant,
> >>>> this is almost certainly going to be something different.
> >>>> The participant AOR is per participant. The CNAME is per media
> >> stream.
> >>>>=20
> >>>> Cheers,
> >>>> Charles
> >>>>=20
> >>>>> -----Original Message-----
> >>>>> From: Paul Kyzivat (pkyzivat)
> >>>>> Sent: Tuesday, March 29, 2011 2:23 PM
> >>>>> To: Leon Portman
> >>>>> Cc: Parthasarathi R (partr); Charles Eckel (eckelcu);
> >> siprec@ietf.org
> >>>>> Subject: Re: [siprec] Multiplexing different=20
> participants' streams
> >> on
> >>>> the same port
> >>>>>=20
> >>>>>=20
> >>>>>=20
> >>>>> On 3/29/2011 7:21 AM, Leon Portman wrote:
> >>>>>> I like it.
> >>>>>>=20
> >>>>>> Quick question. In metadata we are using "<aor>"=20
> attribute but in
> >>>> SDP, it is "CNAME"? Can we use the
> >>>>> same?
> >>>>>=20
> >>>>> Charles knows more than I about RTP. AFAIK CNAME is an=20
> essentially
> >>>>> arbitrary string that is assigned by the media source.=20
> (Are their
> >>>>> constraints on its length or format?) Perhaps it could=20
> be formatted
> >> as
> >>>> a
> >>>>> sip AOR, perhaps not. Even if it *could*, in practice=20
> *will* it be?
> >>>> ISTM
> >>>>> it would not be wise to count on these being the same.
> >>>>>=20
> >>>>> We should probably allow participants to specify their cname as
> >> well
> >>>> as
> >>>>> their AOR. This may get complicated if the same=20
> participant ends up
> >>>> with
> >>>>> differing media streams it sends.
> >>>>>=20
> >>>>> I also wonder if the SRC will always know the CNAMEs of the
> >> streams. I
> >>>>> suspect we can't count on that.
> >>>>>=20
> >>>>>   Thanks,
> >>>>>   Paul
> >>>>>=20
> >>>>>> Leon
> >>>>>>=20
> >>>>>>=20
> >>>>>>=20
> >>>>>> -----Original Message-----
> >>>>>> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On
> >>>> Behalf Of Parthasarathi R (partr)
> >>>>>> Sent: Monday, March 28, 2011 10:42 AM
> >>>>>> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat);
> >>>> siprec@ietf.org
> >>>>>> Subject: Re: [siprec] Multiplexing different=20
> participants' streams
> >>>> on the same port
> >>>>>>=20
> >>>>>> Charles,
> >>>>>>=20
> >>>>>> IMO, the current metadata model helps to address RTP=20
> MUX streams
> >> as
> >>>> well. In terms of model,
> >>>>> multiple participants (P1, P2, P3) metadata block points to the
> >> single
> >>>> stream (S1) and stream block
> >>>>> contains SSRC&    CSRC information. IOW, SIPREC model=20
> abstract RTP
> >> MUX
> >>>> stream within media stream block.
> >>>>> Please let me know in case you feel that model does not=20
> address it.
> >>>>>>=20
> >>>>>> In case of metadata format, multiple "participant"=20
> elements have
> >>>> send element with single stream
> >>>>> element. The stream element has a label attribute which=20
> points to
> >> the
> >>>> m-line which contains "ssrc"
> >>>>> attribute with CNAME parameter. I attached the example for your
> >>>> reference and The example is the one
> >>>>> of the way to represent RTP-MUX stream in the metadata format.
> >> Please
> >>>> let me know the issues with this
> >>>>> format and example.
> >>>>>>=20
> >>>>>> I agree with Paul and you that we need to understand=20
> how RTP mux
> >>>> stream will be standardized but
> >>>>> IMO, it is not the limiting factor for SIPREC as of now.
> >>>>>>=20
> >>>>>> Thanks
> >>>>>> Partha
> >>>>>>=20
> >>>>>> -----Original Message-----
> >>>>>> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On
> >>>> Behalf Of Charles Eckel (eckelcu)
> >>>>>> Sent: Friday, March 18, 2011 8:40 PM
> >>>>>> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
> >>>>>> Subject: Re: [siprec] Multiplexing different=20
> participants' streams
> >>>> on thesame port
> >>>>>>=20
> >>>>>> I agree with the comment regarding CLUE, so let me=20
> take a simpler
> >>>> example, and audio mixer. This
> >>>>> mixer may mix the audio from multiple participants.
> >>>>>>=20
> >>>>>> Participant 1 (P1)
> >>>>>> Participant 2 (P2)
> >>>>>> Participant 3 (P3)
> >>>>>>=20
> >>>>>> P1 sends audio stream with SSRC-P1
> >>>>>> P2 sends audio stream with SSCR-P2
> >>>>>> P2 sends audio stream with SSCR-P3
> >>>>>>=20
> >>>>>> MixerA(Ma)
> >>>>>>=20
> >>>>>> Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
> >>>>>> SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
> >>>>>> The SRC sends this stream to the SRS for recording. I=20
> suspect it
> >>>> might change the SSRC to be SSRC-
> >>>>> SRC but maintain the CSRC information identifying P1/P2/P3.
> >>>>>> I expect this would be modeled as a single stream with 3
> >>>> participants P1, P2, P3. The mapping of P1
> >>>>> to SSRC-P1 is captured in the RTCP data sent by SRC to=20
> SRS. In this
> >>>> case, there is no need to anything
> >>>>> in the metadata.
> >>>>>> However, if the CSRCs are not propagated all the way=20
> to the SRS,
> >>>> then perhaps participant info would
> >>>>> need to be communicated via the metadata.
> >>>>>>=20
> >>>>>> Note, I do not pretend to have this all figured out;=20
> rather, I am
> >>>> putting out some ideas to see if
> >>>>> this gels with what others have in mind.
> >>>>>>=20
> >>>>>> Cheers,
> >>>>>> Charles
> >>>>>>=20
> >>>>>>> -----Original Message-----
> >>>>>>> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On
> >>>>>> Behalf Of Paul Kyzivat (pkyzivat)
> >>>>>>> Sent: Friday, March 18, 2011 5:38 AM
> >>>>>>> To: siprec@ietf.org
> >>>>>>> Subject: Re: [siprec] Multiplexing different participants'
> >> streams
> >>>> on
> >>>>>> the same port
> >>>>>>>=20
> >>>>>>> I don't know if this is a good idea or not. But if we want to
> >>>> consider
> >>>>>>=20
> >>>>>>> it, then we should probably enter into some=20
> discussion with CLUE,
> >>>> to
> >>>>>> see
> >>>>>>> if there is any commonality.
> >>>>>>>=20
> >>>>>>> Over in CLUE, this mixing of multiple streams over one RTP
> >> session
> >>>> has
> >>>>>>=20
> >>>>>>> been brought up because it is a technique used in existing
> >>>> proprietary
> >>>>>>=20
> >>>>>>> products. But the CLUE wg isn't yet to a point where=20
> it is ready
> >> to
> >>>>>>> decide if this will be a requirement. And the AVT people have
> >>>> strong
> >>>>>>> opinions on what is/isn't appropriate.
> >>>>>>>=20
> >>>>>>> Thanks,
> >>>>>>> Paul
> >>>>>>>=20
> >>>>>>> On 3/18/2011 4:11 AM, Elwell, John wrote:
> >>>>>>>> Something Charles mentioned in another thread triggered me to
> >>>> raise
> >>>>>> this.
> >>>>>>>>=20
> >>>>>>>> We consider different participants in the CS as potentially
> >>>>>> producing separate media streams that
> >>>>>>> the SRC sends to the SRS, where the SRC can send them mixed or
> >>>>>> unmixed.
> >>>>>>>>=20
> >>>>>>>> When sending them unmixed, up till now I think we have
> >> considered
> >>>>>> sending them to separate ports on
> >>>>>>> the SRS and identifying them as separate m=3D lines in the SDP.
> >>>> Another
> >>>>>> possibility might be to
> >>>>>>> multiplex the different streams on the same port and identify
> >> them
> >>>> by
> >>>>>> different SSRC values. I am not
> >>>>>>> sure whether this would be a correct use of SSRC, and=20
> I suspect
> >> we
> >>>>>> would need to check with AVTCORE.
> >>>>>>> Recent discussions in other contexts (telepresence,=20
> RTC-Web) have
> >>>> also
> >>>>>> drawn my attention to such
> >>>>>>> possibilities. See also
> >>>>>>=20
> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
> >>>>>>>>=20
> >>>>>>>> Of course, it would mean that we would have to rethink how we
> >>>>>> reference the different streams from
> >>>>>>> metadata.
> >>>>>>>>=20
> >>>>>>>> I am not necessarily proposing such a change - I just want to
> >> make
> >>>>>> sure we have given it due
> >>>>>>> consideration.
> >>>>>>>>=20
> >>>>>>>> John (as individual)
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>> _______________________________________________
> >>>>>>>> siprec mailing list
> >>>>>>>> siprec@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
> >>>>>>>>=20
> >>>>>>> _______________________________________________
> >>>>>>> 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
> >>>>>>=20
> >>>>=20
> >>=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From john.elwell@siemens-enterprise.com  Wed Mar 30 08:01:05 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FC1D3A6AA0 for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 08:01:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.617
X-Spam-Level: 
X-Spam-Status: No, score=-100.617 tagged_above=-999 required=5 tests=[AWL=-1.917, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5GiO-GPoFnuE for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 08:01:04 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 85BB43A6847 for <siprec@ietf.org>; Wed, 30 Mar 2011 08:01:03 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3952358; Wed, 30 Mar 2011 17:02:41 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id DF3A71EB82B4; Wed, 30 Mar 2011 17:02:41 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 30 Mar 2011 17:02:42 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Wed, 30 Mar 2011 17:02:40 +0200
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: Acvu2iDEP0/GCHfoQNiJ2FdGZI6pDAAEITXg
Message-ID: <A444A0F8084434499206E78C106220CA0875AF398F@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com> <4D91CF3F.1010809@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com> <4D9251D0.5020006@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com> <4D9259A3.9080908@cisco.com> <2C2317AF-C679-4977-9150-EF99B6FC3B4B@acmepacket.com>
In-Reply-To: <2C2317AF-C679-4977-9150-EF99B6FC3B4B@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Mar 2011 15:01:05 -0000

(this time as individual)

It occurs to me that if you just indicate, say, audio in the m-line and a g=
iven codec, middleboxes doing call admission control might make some assump=
tions about bandwidth and assume just a single stream at the rate concerned=
. Putting several such streams over the same path, from different participa=
nts, might cause problems. Any opinions?

John=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Hadriel Kaplan
> Sent: 30 March 2011 13:58
> To: Paul Kyzivat
> Cc: siprec@ietf.org; Leon Portman
> Subject: Re: [siprec] Multiplexing different participants'=20
> streams on the same port
>=20
>=20
> In practice we see all kinds of things in the RTCP cname,=20
> often unrelated to signaling info.
> But you can't rely on it anyway, since you can't rely on=20
> there being any RTCP.
>=20
> Furthermore, although I've (shockingly) seen some devices=20
> indicate SSRC in SDP per RFC 5576, it's rare... which means=20
> you won't know the SSRC at call setup time, so it won't be=20
> available to send in metadata at that time, requiring an update.
>=20
> I humbly suggest that UDP port numbers are not in short=20
> supply, and using one per stream is both simple and effective.
>=20
> -hadriel
>=20
>=20
> On Mar 29, 2011, at 6:13 PM, Paul Kyzivat wrote:
>=20
> > On 3/29/2011 6:05 PM, Charles Eckel (eckelcu) wrote:
> >> Typically they appear in RTCP only, and not in SIP or SDP.
> >=20
> > I understand that.
> >=20
> > I'm just wondering what is done by typical sip devices that=20
> handle both
> > media and signaling - e.g. phones and gateways. Presumably=20
> *something*
> > is put in for the cname. But I suspect that layering will=20
> result in the
> > media layer doing its own thing without knowledge of what=20
> sort of names
> > are being used in the signaling layer.
> >=20
> > If so, just reporting the cname in the metadata might not=20
> provide any
> > benefit if it can't be correlated with some signaling name.
> >=20
> >        Thanks,
> >        Paul
> >=20
> >  The RTCP
> >> identify the mapping of CNAME to SSRC. In the SDP, you can=20
> specify the
> >> SSRC for a media stream as described in RFC 5576 -=20
> Source-Specific Media
> >> Attributes in the Session Description Protocol (SDP). I am=20
> not sure if
> >> there are many existing implementations that do this.
> >>=20
> >> Cheers,
> >> Charles
> >>=20
> >>> -----Original Message-----
> >>> From: Paul Kyzivat (pkyzivat)
> >>> Sent: Tuesday, March 29, 2011 11:41 PM
> >>> To: Charles Eckel (eckelcu)
> >>> Cc: Leon Portman; Parthasarathi R (partr); siprec@ietf.org
> >>> Subject: Re: [siprec] Multiplexing different=20
> participants' streams on
> >> the same port
> >>>=20
> >>> Charles,
> >>>=20
> >>> *In practice* how are cnames set for sip calls?
> >>> I'm assuming they are something canned and unrelated to=20
> the signaling
> >>> identity.
> >>>=20
> >>>     Thanks,
> >>>     Paul
> >>>=20
> >>> On 3/29/2011 10:20 AM, Charles Eckel (eckelcu) wrote:
> >>>> For the format and value of the CNAME, I suggest having a look at
> >>>> "Guidelines for Choosing RTP Control Protocol (RTCP)=20
> Canonical Names
> >>>> (CNAMEs)", draft-ietf-avt-rtp-cnames-05.
> >>>> If the SIP AOR is meant to be the AOR registered by the=20
> participant,
> >>>> this is almost certainly going to be something different.
> >>>> The participant AOR is per participant. The CNAME is per media
> >> stream.
> >>>>=20
> >>>> Cheers,
> >>>> Charles
> >>>>=20
> >>>>> -----Original Message-----
> >>>>> From: Paul Kyzivat (pkyzivat)
> >>>>> Sent: Tuesday, March 29, 2011 2:23 PM
> >>>>> To: Leon Portman
> >>>>> Cc: Parthasarathi R (partr); Charles Eckel (eckelcu);
> >> siprec@ietf.org
> >>>>> Subject: Re: [siprec] Multiplexing different=20
> participants' streams
> >> on
> >>>> the same port
> >>>>>=20
> >>>>>=20
> >>>>>=20
> >>>>> On 3/29/2011 7:21 AM, Leon Portman wrote:
> >>>>>> I like it.
> >>>>>>=20
> >>>>>> Quick question. In metadata we are using "<aor>"=20
> attribute but in
> >>>> SDP, it is "CNAME"? Can we use the
> >>>>> same?
> >>>>>=20
> >>>>> Charles knows more than I about RTP. AFAIK CNAME is an=20
> essentially
> >>>>> arbitrary string that is assigned by the media source.=20
> (Are their
> >>>>> constraints on its length or format?) Perhaps it could=20
> be formatted
> >> as
> >>>> a
> >>>>> sip AOR, perhaps not. Even if it *could*, in practice=20
> *will* it be?
> >>>> ISTM
> >>>>> it would not be wise to count on these being the same.
> >>>>>=20
> >>>>> We should probably allow participants to specify their cname as
> >> well
> >>>> as
> >>>>> their AOR. This may get complicated if the same=20
> participant ends up
> >>>> with
> >>>>> differing media streams it sends.
> >>>>>=20
> >>>>> I also wonder if the SRC will always know the CNAMEs of the
> >> streams. I
> >>>>> suspect we can't count on that.
> >>>>>=20
> >>>>>   Thanks,
> >>>>>   Paul
> >>>>>=20
> >>>>>> Leon
> >>>>>>=20
> >>>>>>=20
> >>>>>>=20
> >>>>>> -----Original Message-----
> >>>>>> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On
> >>>> Behalf Of Parthasarathi R (partr)
> >>>>>> Sent: Monday, March 28, 2011 10:42 AM
> >>>>>> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat);
> >>>> siprec@ietf.org
> >>>>>> Subject: Re: [siprec] Multiplexing different=20
> participants' streams
> >>>> on the same port
> >>>>>>=20
> >>>>>> Charles,
> >>>>>>=20
> >>>>>> IMO, the current metadata model helps to address RTP=20
> MUX streams
> >> as
> >>>> well. In terms of model,
> >>>>> multiple participants (P1, P2, P3) metadata block points to the
> >> single
> >>>> stream (S1) and stream block
> >>>>> contains SSRC&    CSRC information. IOW, SIPREC model=20
> abstract RTP
> >> MUX
> >>>> stream within media stream block.
> >>>>> Please let me know in case you feel that model does not=20
> address it.
> >>>>>>=20
> >>>>>> In case of metadata format, multiple "participant"=20
> elements have
> >>>> send element with single stream
> >>>>> element. The stream element has a label attribute which=20
> points to
> >> the
> >>>> m-line which contains "ssrc"
> >>>>> attribute with CNAME parameter. I attached the example for your
> >>>> reference and The example is the one
> >>>>> of the way to represent RTP-MUX stream in the metadata format.
> >> Please
> >>>> let me know the issues with this
> >>>>> format and example.
> >>>>>>=20
> >>>>>> I agree with Paul and you that we need to understand=20
> how RTP mux
> >>>> stream will be standardized but
> >>>>> IMO, it is not the limiting factor for SIPREC as of now.
> >>>>>>=20
> >>>>>> Thanks
> >>>>>> Partha
> >>>>>>=20
> >>>>>> -----Original Message-----
> >>>>>> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On
> >>>> Behalf Of Charles Eckel (eckelcu)
> >>>>>> Sent: Friday, March 18, 2011 8:40 PM
> >>>>>> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
> >>>>>> Subject: Re: [siprec] Multiplexing different=20
> participants' streams
> >>>> on thesame port
> >>>>>>=20
> >>>>>> I agree with the comment regarding CLUE, so let me=20
> take a simpler
> >>>> example, and audio mixer. This
> >>>>> mixer may mix the audio from multiple participants.
> >>>>>>=20
> >>>>>> Participant 1 (P1)
> >>>>>> Participant 2 (P2)
> >>>>>> Participant 3 (P3)
> >>>>>>=20
> >>>>>> P1 sends audio stream with SSRC-P1
> >>>>>> P2 sends audio stream with SSCR-P2
> >>>>>> P2 sends audio stream with SSCR-P3
> >>>>>>=20
> >>>>>> MixerA(Ma)
> >>>>>>=20
> >>>>>> Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
> >>>>>> SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
> >>>>>> The SRC sends this stream to the SRS for recording. I=20
> suspect it
> >>>> might change the SSRC to be SSRC-
> >>>>> SRC but maintain the CSRC information identifying P1/P2/P3.
> >>>>>> I expect this would be modeled as a single stream with 3
> >>>> participants P1, P2, P3. The mapping of P1
> >>>>> to SSRC-P1 is captured in the RTCP data sent by SRC to=20
> SRS. In this
> >>>> case, there is no need to anything
> >>>>> in the metadata.
> >>>>>> However, if the CSRCs are not propagated all the way=20
> to the SRS,
> >>>> then perhaps participant info would
> >>>>> need to be communicated via the metadata.
> >>>>>>=20
> >>>>>> Note, I do not pretend to have this all figured out;=20
> rather, I am
> >>>> putting out some ideas to see if
> >>>>> this gels with what others have in mind.
> >>>>>>=20
> >>>>>> Cheers,
> >>>>>> Charles
> >>>>>>=20
> >>>>>>> -----Original Message-----
> >>>>>>> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On
> >>>>>> Behalf Of Paul Kyzivat (pkyzivat)
> >>>>>>> Sent: Friday, March 18, 2011 5:38 AM
> >>>>>>> To: siprec@ietf.org
> >>>>>>> Subject: Re: [siprec] Multiplexing different participants'
> >> streams
> >>>> on
> >>>>>> the same port
> >>>>>>>=20
> >>>>>>> I don't know if this is a good idea or not. But if we want to
> >>>> consider
> >>>>>>=20
> >>>>>>> it, then we should probably enter into some=20
> discussion with CLUE,
> >>>> to
> >>>>>> see
> >>>>>>> if there is any commonality.
> >>>>>>>=20
> >>>>>>> Over in CLUE, this mixing of multiple streams over one RTP
> >> session
> >>>> has
> >>>>>>=20
> >>>>>>> been brought up because it is a technique used in existing
> >>>> proprietary
> >>>>>>=20
> >>>>>>> products. But the CLUE wg isn't yet to a point where=20
> it is ready
> >> to
> >>>>>>> decide if this will be a requirement. And the AVT people have
> >>>> strong
> >>>>>>> opinions on what is/isn't appropriate.
> >>>>>>>=20
> >>>>>>> Thanks,
> >>>>>>> Paul
> >>>>>>>=20
> >>>>>>> On 3/18/2011 4:11 AM, Elwell, John wrote:
> >>>>>>>> Something Charles mentioned in another thread triggered me to
> >>>> raise
> >>>>>> this.
> >>>>>>>>=20
> >>>>>>>> We consider different participants in the CS as potentially
> >>>>>> producing separate media streams that
> >>>>>>> the SRC sends to the SRS, where the SRC can send them mixed or
> >>>>>> unmixed.
> >>>>>>>>=20
> >>>>>>>> When sending them unmixed, up till now I think we have
> >> considered
> >>>>>> sending them to separate ports on
> >>>>>>> the SRS and identifying them as separate m=3D lines in the SDP.
> >>>> Another
> >>>>>> possibility might be to
> >>>>>>> multiplex the different streams on the same port and identify
> >> them
> >>>> by
> >>>>>> different SSRC values. I am not
> >>>>>>> sure whether this would be a correct use of SSRC, and=20
> I suspect
> >> we
> >>>>>> would need to check with AVTCORE.
> >>>>>>> Recent discussions in other contexts (telepresence,=20
> RTC-Web) have
> >>>> also
> >>>>>> drawn my attention to such
> >>>>>>> possibilities. See also
> >>>>>>=20
> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
> >>>>>>>>=20
> >>>>>>>> Of course, it would mean that we would have to rethink how we
> >>>>>> reference the different streams from
> >>>>>>> metadata.
> >>>>>>>>=20
> >>>>>>>> I am not necessarily proposing such a change - I just want to
> >> make
> >>>>>> sure we have given it due
> >>>>>>> consideration.
> >>>>>>>>=20
> >>>>>>>> John (as individual)
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>> _______________________________________________
> >>>>>>>> siprec mailing list
> >>>>>>>> siprec@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
> >>>>>>>>=20
> >>>>>>> _______________________________________________
> >>>>>>> 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
> >>>>>>=20
> >>>>=20
> >>=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From partr@cisco.com  Wed Mar 30 09:54:34 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A31128C108 for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 09:54:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.139
X-Spam-Level: 
X-Spam-Status: No, score=-8.139 tagged_above=-999 required=5 tests=[AWL=-1.439, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nhz4J+uyaX3J for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 09:54:32 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 5A4A03A6A66 for <siprec@ietf.org>; Wed, 30 Mar 2011 09:54:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=13329; q=dns/txt; s=iport; t=1301504171; x=1302713771; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=eKkwFn+cQRI+oUDWNMWkWoxguSiwJCsVD0k04swljIg=; b=S3/+L+pX5NzbfetyZnlJBbbGNFTuhy0nfNpvKi7oDgn2EwafwCDqF9Q1 iPdqrfEQGefgq0T05gx5eTZtTG8jiwYwhBPqlUIsPPFpd/x9amT8K/b/o nLns3Tt+z6m8c7CcgBBs/RSfQSl+HORFZHT+uRrT8CSj7y1GJDHN+FeMY o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUAAEVgk02tJV2b/2dsb2JhbACYEY1Bd4h5mDucV4J8AYJtBIU9iySJQw
X-IronPort-AV: E=Sophos;i="4.63,269,1299456000"; d="scan'208";a="285868030"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by sj-iport-3.cisco.com with ESMTP; 30 Mar 2011 16:56:10 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2UGu5n2027752; Wed, 30 Mar 2011 16:56:10 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Mar 2011 22:26:09 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 30 Mar 2011 22:26:07 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904E976BB@XMB-BGL-411.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF398F@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: Acvu2iDEP0/GCHfoQNiJ2FdGZI6pDAAEITXgAAOnvkA=
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com><E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com><A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com><4D91CF3F.1010809@cisco.com><E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com><4D9251D0.5020006@cisco.com><E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com><4D9259A3.9080908@cisco.com><2C2317AF-C679-4977-9150-EF99B6FC3B4B@acmepacket.com> <A444A0F8084434499206E78C106220CA0875AF398F@MCHP058A.global-ad.net>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Hadriel Kaplan" <HKaplan@acmepacket.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 30 Mar 2011 16:56:09.0229 (UTC) FILETIME=[5E0CCBD0:01CBEEFB]
Cc: siprec@ietf.org, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Mar 2011 16:54:34 -0000

John/Hadriel,

Please read inline.

Thanks
Partha=20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Elwell, John
Sent: Wednesday, March 30, 2011 8:33 PM
To: Hadriel Kaplan; Paul Kyzivat (pkyzivat)
Cc: siprec@ietf.org; Leon Portman
Subject: Re: [siprec] Multiplexing different participants' streams on
the same port

(this time as individual)

It occurs to me that if you just indicate, say, audio in the m-line and
a given codec, middleboxes doing call admission control might make some
assumptions about bandwidth and assume just a single stream at the rate
concerned.=20
<partha> IMO, This problem will be solved in case bandwidth attribute
under the single stream is populated properly. If it is the problem,
then the problem is outside the scope of SIPREC. </partha>

Putting several such streams over the same path, from different
participants, might cause problems. Any opinions?

John=20

> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Hadriel Kaplan
> Sent: 30 March 2011 13:58
> To: Paul Kyzivat
> Cc: siprec@ietf.org; Leon Portman
> Subject: Re: [siprec] Multiplexing different participants'=20
> streams on the same port
>=20
>=20
> In practice we see all kinds of things in the RTCP cname, often=20
> unrelated to signaling info.
> But you can't rely on it anyway, since you can't rely on there being=20
> any RTCP.
>=20
> Furthermore, although I've (shockingly) seen some devices indicate=20
> SSRC in SDP per RFC 5576, it's rare...
<partha> May take time to adopt..As less RTP MUX in single stream
implementation may be one of the reason. </partha>
 which means you won't know the=20
> SSRC at call setup time, so it won't be available to send in metadata=20
> at that time, requiring an update.
>=20
<partha> I guess that it is possible to populate SSRC while offer is
sent out and it is implementation specific </partha>
 =20
> I humbly suggest that UDP port numbers are not in short supply, and=20
> using one per stream is both simple and effective.
<partha> may not always the case. There are nightmare with multiple
m-lines passing through some middle boxes </partha?>
>=20
> -hadriel
>=20
>=20
> On Mar 29, 2011, at 6:13 PM, Paul Kyzivat wrote:
>=20
> > On 3/29/2011 6:05 PM, Charles Eckel (eckelcu) wrote:
> >> Typically they appear in RTCP only, and not in SIP or SDP.
> >=20
> > I understand that.
> >=20
> > I'm just wondering what is done by typical sip devices that
> handle both
> > media and signaling - e.g. phones and gateways. Presumably
> *something*
> > is put in for the cname. But I suspect that layering will
> result in the
> > media layer doing its own thing without knowledge of what
> sort of names
> > are being used in the signaling layer.
> >=20
> > If so, just reporting the cname in the metadata might not
> provide any
> > benefit if it can't be correlated with some signaling name.
> >=20
> >        Thanks,
> >        Paul
> >=20
> >  The RTCP
> >> identify the mapping of CNAME to SSRC. In the SDP, you can
> specify the
> >> SSRC for a media stream as described in RFC 5576 -
> Source-Specific Media
> >> Attributes in the Session Description Protocol (SDP). I am
> not sure if
> >> there are many existing implementations that do this.
> >>=20
> >> Cheers,
> >> Charles
> >>=20
> >>> -----Original Message-----
> >>> From: Paul Kyzivat (pkyzivat)
> >>> Sent: Tuesday, March 29, 2011 11:41 PM
> >>> To: Charles Eckel (eckelcu)
> >>> Cc: Leon Portman; Parthasarathi R (partr); siprec@ietf.org
> >>> Subject: Re: [siprec] Multiplexing different
> participants' streams on
> >> the same port
> >>>=20
> >>> Charles,
> >>>=20
> >>> *In practice* how are cnames set for sip calls?
> >>> I'm assuming they are something canned and unrelated to
> the signaling
> >>> identity.
> >>>=20
> >>>     Thanks,
> >>>     Paul
> >>>=20
> >>> On 3/29/2011 10:20 AM, Charles Eckel (eckelcu) wrote:
> >>>> For the format and value of the CNAME, I suggest having a look at

> >>>> "Guidelines for Choosing RTP Control Protocol (RTCP)
> Canonical Names
> >>>> (CNAMEs)", draft-ietf-avt-rtp-cnames-05.
> >>>> If the SIP AOR is meant to be the AOR registered by the
> participant,
> >>>> this is almost certainly going to be something different.
> >>>> The participant AOR is per participant. The CNAME is per media
> >> stream.
> >>>>=20
> >>>> Cheers,
> >>>> Charles
> >>>>=20
> >>>>> -----Original Message-----
> >>>>> From: Paul Kyzivat (pkyzivat)
> >>>>> Sent: Tuesday, March 29, 2011 2:23 PM
> >>>>> To: Leon Portman
> >>>>> Cc: Parthasarathi R (partr); Charles Eckel (eckelcu);
> >> siprec@ietf.org
> >>>>> Subject: Re: [siprec] Multiplexing different
> participants' streams
> >> on
> >>>> the same port
> >>>>>=20
> >>>>>=20
> >>>>>=20
> >>>>> On 3/29/2011 7:21 AM, Leon Portman wrote:
> >>>>>> I like it.
> >>>>>>=20
> >>>>>> Quick question. In metadata we are using "<aor>"=20
> attribute but in
> >>>> SDP, it is "CNAME"? Can we use the
> >>>>> same?
> >>>>>=20
> >>>>> Charles knows more than I about RTP. AFAIK CNAME is an
> essentially
> >>>>> arbitrary string that is assigned by the media source.=20
> (Are their
> >>>>> constraints on its length or format?) Perhaps it could
> be formatted
> >> as
> >>>> a
> >>>>> sip AOR, perhaps not. Even if it *could*, in practice
> *will* it be?
> >>>> ISTM
> >>>>> it would not be wise to count on these being the same.
> >>>>>=20
> >>>>> We should probably allow participants to specify their cname as
> >> well
> >>>> as
> >>>>> their AOR. This may get complicated if the same
> participant ends up
> >>>> with
> >>>>> differing media streams it sends.
> >>>>>=20
> >>>>> I also wonder if the SRC will always know the CNAMEs of the
> >> streams. I
> >>>>> suspect we can't count on that.
> >>>>>=20
> >>>>>   Thanks,
> >>>>>   Paul
> >>>>>=20
> >>>>>> Leon
> >>>>>>=20
> >>>>>>=20
> >>>>>>=20
> >>>>>> -----Original Message-----
> >>>>>> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On
> >>>> Behalf Of Parthasarathi R (partr)
> >>>>>> Sent: Monday, March 28, 2011 10:42 AM
> >>>>>> To: Charles Eckel (eckelcu); Paul Kyzivat (pkyzivat);
> >>>> siprec@ietf.org
> >>>>>> Subject: Re: [siprec] Multiplexing different
> participants' streams
> >>>> on the same port
> >>>>>>=20
> >>>>>> Charles,
> >>>>>>=20
> >>>>>> IMO, the current metadata model helps to address RTP
> MUX streams
> >> as
> >>>> well. In terms of model,
> >>>>> multiple participants (P1, P2, P3) metadata block points to the
> >> single
> >>>> stream (S1) and stream block
> >>>>> contains SSRC&    CSRC information. IOW, SIPREC model=20
> abstract RTP
> >> MUX
> >>>> stream within media stream block.
> >>>>> Please let me know in case you feel that model does not
> address it.
> >>>>>>=20
> >>>>>> In case of metadata format, multiple "participant"=20
> elements have
> >>>> send element with single stream
> >>>>> element. The stream element has a label attribute which
> points to
> >> the
> >>>> m-line which contains "ssrc"
> >>>>> attribute with CNAME parameter. I attached the example for your
> >>>> reference and The example is the one
> >>>>> of the way to represent RTP-MUX stream in the metadata format.
> >> Please
> >>>> let me know the issues with this
> >>>>> format and example.
> >>>>>>=20
> >>>>>> I agree with Paul and you that we need to understand
> how RTP mux
> >>>> stream will be standardized but
> >>>>> IMO, it is not the limiting factor for SIPREC as of now.
> >>>>>>=20
> >>>>>> Thanks
> >>>>>> Partha
> >>>>>>=20
> >>>>>> -----Original Message-----
> >>>>>> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On
> >>>> Behalf Of Charles Eckel (eckelcu)
> >>>>>> Sent: Friday, March 18, 2011 8:40 PM
> >>>>>> To: Paul Kyzivat (pkyzivat); siprec@ietf.org
> >>>>>> Subject: Re: [siprec] Multiplexing different
> participants' streams
> >>>> on thesame port
> >>>>>>=20
> >>>>>> I agree with the comment regarding CLUE, so let me
> take a simpler
> >>>> example, and audio mixer. This
> >>>>> mixer may mix the audio from multiple participants.
> >>>>>>=20
> >>>>>> Participant 1 (P1)
> >>>>>> Participant 2 (P2)
> >>>>>> Participant 3 (P3)
> >>>>>>=20
> >>>>>> P1 sends audio stream with SSRC-P1
> >>>>>> P2 sends audio stream with SSCR-P2
> >>>>>> P2 sends audio stream with SSCR-P3
> >>>>>>=20
> >>>>>> MixerA(Ma)
> >>>>>>=20
> >>>>>> Ma sends mixed audio stream with SSRC SSRC-Ma and CSRC
> >>>>>> SSRC-P1/SSRC-P2/SSRC-P3 as part of the CS.
> >>>>>> The SRC sends this stream to the SRS for recording. I
> suspect it
> >>>> might change the SSRC to be SSRC-
> >>>>> SRC but maintain the CSRC information identifying P1/P2/P3.
> >>>>>> I expect this would be modeled as a single stream with 3
> >>>> participants P1, P2, P3. The mapping of P1
> >>>>> to SSRC-P1 is captured in the RTCP data sent by SRC to
> SRS. In this
> >>>> case, there is no need to anything
> >>>>> in the metadata.
> >>>>>> However, if the CSRCs are not propagated all the way
> to the SRS,
> >>>> then perhaps participant info would
> >>>>> need to be communicated via the metadata.
> >>>>>>=20
> >>>>>> Note, I do not pretend to have this all figured out;
> rather, I am
> >>>> putting out some ideas to see if
> >>>>> this gels with what others have in mind.
> >>>>>>=20
> >>>>>> Cheers,
> >>>>>> Charles
> >>>>>>=20
> >>>>>>> -----Original Message-----
> >>>>>>> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On
> >>>>>> Behalf Of Paul Kyzivat (pkyzivat)
> >>>>>>> Sent: Friday, March 18, 2011 5:38 AM
> >>>>>>> To: siprec@ietf.org
> >>>>>>> Subject: Re: [siprec] Multiplexing different participants'
> >> streams
> >>>> on
> >>>>>> the same port
> >>>>>>>=20
> >>>>>>> I don't know if this is a good idea or not. But if we want to
> >>>> consider
> >>>>>>=20
> >>>>>>> it, then we should probably enter into some
> discussion with CLUE,
> >>>> to
> >>>>>> see
> >>>>>>> if there is any commonality.
> >>>>>>>=20
> >>>>>>> Over in CLUE, this mixing of multiple streams over one RTP
> >> session
> >>>> has
> >>>>>>=20
> >>>>>>> been brought up because it is a technique used in existing
> >>>> proprietary
> >>>>>>=20
> >>>>>>> products. But the CLUE wg isn't yet to a point where
> it is ready
> >> to
> >>>>>>> decide if this will be a requirement. And the AVT people have
> >>>> strong
> >>>>>>> opinions on what is/isn't appropriate.
> >>>>>>>=20
> >>>>>>> Thanks,
> >>>>>>> Paul
> >>>>>>>=20
> >>>>>>> On 3/18/2011 4:11 AM, Elwell, John wrote:
> >>>>>>>> Something Charles mentioned in another thread triggered me to
> >>>> raise
> >>>>>> this.
> >>>>>>>>=20
> >>>>>>>> We consider different participants in the CS as potentially
> >>>>>> producing separate media streams that
> >>>>>>> the SRC sends to the SRS, where the SRC can send them mixed or
> >>>>>> unmixed.
> >>>>>>>>=20
> >>>>>>>> When sending them unmixed, up till now I think we have
> >> considered
> >>>>>> sending them to separate ports on
> >>>>>>> the SRS and identifying them as separate m=3D lines in the =
SDP.
> >>>> Another
> >>>>>> possibility might be to
> >>>>>>> multiplex the different streams on the same port and identify
> >> them
> >>>> by
> >>>>>> different SSRC values. I am not
> >>>>>>> sure whether this would be a correct use of SSRC, and
> I suspect
> >> we
> >>>>>> would need to check with AVTCORE.
> >>>>>>> Recent discussions in other contexts (telepresence,
> RTC-Web) have
> >>>> also
> >>>>>> drawn my attention to such
> >>>>>>> possibilities. See also
> >>>>>>=20
> https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/.
> >>>>>>>>=20
> >>>>>>>> Of course, it would mean that we would have to rethink how we
> >>>>>> reference the different streams from
> >>>>>>> metadata.
> >>>>>>>>=20
> >>>>>>>> I am not necessarily proposing such a change - I just want to
> >> make
> >>>>>> sure we have given it due
> >>>>>>> consideration.
> >>>>>>>>=20
> >>>>>>>> John (as individual)
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>> _______________________________________________
> >>>>>>>> siprec mailing list
> >>>>>>>> siprec@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
> >>>>>>>>=20
> >>>>>>> _______________________________________________
> >>>>>>> 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
> >>>>>>=20
> >>>>=20
> >>=20
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From HKaplan@acmepacket.com  Wed Mar 30 13:01:42 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC98828C0DE for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 13:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.026
X-Spam-Level: 
X-Spam-Status: No, score=0.026 tagged_above=-999 required=5 tests=[AWL=-1.274,  BAYES_00=-2.599, FB_CIALIS_LEO3=3.899]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c2202SmoCwS8 for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 13:01:42 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id ED3563A6BC1 for <siprec@ietf.org>; Wed, 30 Mar 2011 13:01:41 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 30 Mar 2011 16:03:20 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Wed, 30 Mar 2011 16:03:20 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Wed, 30 Mar 2011 16:03:19 -0400
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: AcvvFYRMjVt6Tn9DTiukMu6uJYcBjg==
Message-ID: <9E2E57D3-F714-4B0A-B737-A5CD712EC519@acmepacket.com>
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com> <4D91CF3F.1010809@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com> <4D9251D0.5020006@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com> <4D9259A3.9080908@cisco.com> <2C2317AF-C679-4977-9150-EF99B6FC3B4B@acmepacket.com> <A444A0F8084434499206E78C106220CA0875AF3984@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF3984@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAgAAAUAAAAFT
Cc: "siprec@ietf.org" <siprec@ietf.org>, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Mar 2011 20:01:42 -0000

Maybe I misunderstood the context of this thread.  The email thread appeare=
d to be about using the SSRCs or cnames of the real participant streams, no=
t new ones of the session recording client.  In other words, in RTP RFC 355=
0 lingo the recording client would be doing a RTP translator model vs. an R=
TP mixer or endpoint model.  But based on your comments below I take it  yo=
u're talking about the recording client being a mixer or endpoint model ins=
tead?  If so, then sure you could make the recording client do whatever you=
 want. (and pay the price penalty for doing so)

-hadriel


On Mar 30, 2011, at 10:56 AM, Elwell, John wrote:

> Yes, this was the sort of discussion I was trying to provoke. Of course, =
SRC and SRS implementations will need to be upgraded to support the SIPREC =
protocol requirements, so requiring some extra things is not out of the que=
stion. Clearly one consideration might be whether middleboxes might block s=
uch features?
>=20
> John (as chair)
>=20
>=20
>> -----Original Message-----
>> From: siprec-bounces@ietf.org
>> [mailto:siprec-bounces@ietf.org] On Behalf Of Hadriel Kaplan
>> Sent: 30 March 2011 13:58
>> To: Paul Kyzivat
>> Cc: siprec@ietf.org; Leon Portman
>> Subject: Re: [siprec] Multiplexing different participants'
>> streams on the same port
>>=20
>>=20
>> In practice we see all kinds of things in the RTCP cname,
>> often unrelated to signaling info.
>> But you can't rely on it anyway, since you can't rely on
>> there being any RTCP.
>>=20
>> Furthermore, although I've (shockingly) seen some devices
>> indicate SSRC in SDP per RFC 5576, it's rare... which means
>> you won't know the SSRC at call setup time, so it won't be
>> available to send in metadata at that time, requiring an update.
>>=20
>> I humbly suggest that UDP port numbers are not in short
>> supply, and using one per stream is both simple and effective.
>>=20
>> -hadriel


From Henry.Lum@alcatel-lucent.com  Wed Mar 30 13:28:14 2011
Return-Path: <Henry.Lum@alcatel-lucent.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB59228C0DE for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 13:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.319
X-Spam-Level: 
X-Spam-Status: No, score=-4.319 tagged_above=-999 required=5 tests=[AWL=-2.219, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NQdNGLC0ntWz for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 13:28:12 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 813CE3A6A2A for <siprec@ietf.org>; Wed, 30 Mar 2011 13:28:12 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p2UKTn0O017287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Mar 2011 15:29:49 -0500 (CDT)
Received: from relay-out2.dc (relay-out2.dc.genesyslab.com [172.22.68.188]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p2UKTjAu027143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 30 Mar 2011 15:29:47 -0500
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out2.dc (8.13.8+Sun/8.13.8) with ESMTP id p2UKTjBK013715; Wed, 30 Mar 2011 13:29:45 -0700 (PDT)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.93]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Mar 2011 13:29:44 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 30 Mar 2011 13:29:39 -0700
Message-ID: <059AF07365DC474393A19A3AF187DF7406DCF5C9@NAHALD.us.int.genesyslab.com>
In-Reply-To: <9E2E57D3-F714-4B0A-B737-A5CD712EC519@acmepacket.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Multiplexing different participants' streams on the same port
Thread-Index: AcvvFYRMjVt6Tn9DTiukMu6uJYcBjgAAhVaQ
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com><E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com><A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com><07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com><4D91CF3F.1010809@cisco.com><E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com><4D9251D0.5020006@cisco.com><E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com><4D9259A3.9080908@cisco.com><2C2317AF-C679-4977-9150-EF99B6FC3B4B@acmepacket.com><A444A0F8084434499206E78C106220CA0875AF3984@MCHP058A.global-ad.net> <9E2E57D3-F714-4B0A-B737-A5CD712EC519@acmepacket.com>
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: "Hadriel Kaplan" <HKaplan@acmepacket.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
X-OriginalArrivalTime: 30 Mar 2011 20:29:44.0892 (UTC) FILETIME=[34C7C7C0:01CBEF19]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: siprec@ietf.org, Leon Portman <Leon.Portman@nice.com>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Mar 2011 20:28:14 -0000

One of the downside I see with multiplexing of streams is not being able
to pause/resume a recorded stream for a specific participant. Our
current proposed mechanism is to reINVITE with a=3Dinactive but this
pauses all the participant streams in the m=3D line. We could come up wit=
h
another mechanism to pause/resume at a finer granularity, but then we
could end up with multiple mechanisms for this feature.

Henry

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Hadriel Kaplan
> Sent: Wednesday, March 30, 2011 4:03 PM
> To: Elwell, John
> Cc: siprec@ietf.org; Leon Portman
> Subject: Re: [siprec] Multiplexing different participants' streams on
> the same port
>=20
>=20
> Maybe I misunderstood the context of this thread.  The email thread
> appeared to be about using the SSRCs or cnames of the real participant
> streams, not new ones of the session recording client.  In other
words,
> in RTP RFC 3550 lingo the recording client would be doing a RTP
> translator model vs. an RTP mixer or endpoint model.  But based on
your
> comments below I take it  you're talking about the recording client
> being a mixer or endpoint model instead?  If so, then sure you could
> make the recording client do whatever you want. (and pay the price
> penalty for doing so)
>=20
> -hadriel
>=20
>=20
> On Mar 30, 2011, at 10:56 AM, Elwell, John wrote:
>=20
> > Yes, this was the sort of discussion I was trying to provoke. Of
> course, SRC and SRS implementations will need to be upgraded to
support
> the SIPREC protocol requirements, so requiring some extra things is
not
> out of the question. Clearly one consideration might be whether
> middleboxes might block such features?
> >
> > John (as chair)
> >
> >
> >> -----Original Message-----
> >> From: siprec-bounces@ietf.org
> >> [mailto:siprec-bounces@ietf.org] On Behalf Of Hadriel Kaplan
> >> Sent: 30 March 2011 13:58
> >> To: Paul Kyzivat
> >> Cc: siprec@ietf.org; Leon Portman
> >> Subject: Re: [siprec] Multiplexing different participants'
> >> streams on the same port
> >>
> >>
> >> In practice we see all kinds of things in the RTCP cname,
> >> often unrelated to signaling info.
> >> But you can't rely on it anyway, since you can't rely on
> >> there being any RTCP.
> >>
> >> Furthermore, although I've (shockingly) seen some devices
> >> indicate SSRC in SDP per RFC 5576, it's rare... which means
> >> you won't know the SSRC at call setup time, so it won't be
> >> available to send in metadata at that time, requiring an update.
> >>
> >> I humbly suggest that UDP port numbers are not in short
> >> supply, and using one per stream is both simple and effective.
> >>
> >> -hadriel
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

				=09
-------------------------------------------------------------------------=
------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co=
nfidential and proprietary information of Alcatel-Lucent and/or its affil=
iated entities. Access by the intended recipient only is authorized. Any =
liability arising from any party acting, or refraining from acting, on an=
y information contained in this e-mail is hereby excluded. If you are not=
 the intended recipient, please notify the sender immediately, destroy th=
e original transmission and its attachments and do not disclose the conte=
nts to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Copyright in this e-mail and any attachments belo=
ngs to Alcatel-Lucent and/or its affiliated entities.
				=09

From stpeter@stpeter.im  Wed Mar 30 15:23:40 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 281963A6BDD for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 15:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.895
X-Spam-Level: 
X-Spam-Status: No, score=-101.895 tagged_above=-999 required=5 tests=[AWL=-1.096, BAYES_00=-2.599, J_CHICKENPOX_210=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_29=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRaSeM5KToCQ for <siprec@core3.amsl.com>; Wed, 30 Mar 2011 15:23:39 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 25E823A6BDB for <siprec@ietf.org>; Wed, 30 Mar 2011 15:23:39 -0700 (PDT)
Received: from dhcp-12cb.meeting.ietf.org (64-103-25-233.cisco.com [64.103.25.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E196F40022 for <siprec@ietf.org>; Wed, 30 Mar 2011 16:27:05 -0600 (MDT)
Message-ID: <4D93ADCB.2050106@stpeter.im>
Date: Thu, 31 Mar 2011 00:25:15 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: siprec@ietf.org
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms060609090707020101050207"
Subject: [siprec] draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Mar 2011 22:23:40 -0000

This is a cryptographically signed message in MIME format.

--------------ms060609090707020101050207
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Here is some quick feedback on draft-ram-siprec-metadata-format-01. I
hope to review it more fully soon.

1. I would change application/recording to application/recording+xml in
accordance with RFC 3023 (many specs illustrate the use of XML media
types -- see for example RFC 4287).

2. The large number of <extensiondata/> elements is a bit confusing in
the examples.

3. In Section 5.1, the example has one <extensiondata/> element
qualified by the 'urn:ietf:params:xml:ns:siprec' namespace (no other
namespace is defined) and then multiple <extensiondata/> elements
qualified by other namespaces ('http://example.com/groupapp',
'http://example.com/sessionapp', etc.). Although those other namespaces
are certainly *allowed* to use "extensiondata" as an element name
(that's the beauty of namespaces), it is confusing in this document.
Perhaps you even meant to have <extensiondata/> elements qualified by
the 'urn:ietf:params:xml:ns:siprec' and then child elements qualified by
other namespaces (in accordance with the schema). However, that is not
clear in the spec.

4. There is no built-in datatype for xs:urnuuid, xs:streamMode,
xs:requester, and so on. See W3C XML Schema Part 2:

   http://www.w3.org/TR/xmlschema-2/#built-in-datatypes

5. The data in the <name/> elements with xml:lang=3D"it" really should be=

Giulietta Capuleti and Romeo Montecchi. ;-)

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms060609090707020101050207
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDMz
MDIyMjUxNVowIwYJKoZIhvcNAQkEMRYEFCNUz1wvOYur0pJokUITkHOZQSlmMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQCYRKPIdahmA9aWLwjYoS9kb/5JJ+YVQrLz458KdH+oQm0122rA2G7jZUO2
4kJx2h8sz61E8n3E6gXCBuundx207/hxiOjGjFJdrUtRvIbZGSRr/2dgiG7mAb0ilgssdnBC
wnQjx0dvIQnV86laKrcOoly67sn2jhAolW9Jw1rfMesPSlgaRK8xYXrcZhxU53Jx8HBIF78s
WSUAuRKhJtnpwLb4p7SLVHW4bGgQHId3g0YjkesMZ/Ao0E+CoVyH8G4fi9lVi1N1Ca6tNKek
t6LMclW8aMPnP4hszz0x9w1WJHFo826izWfRpHA5Dc/+XL+tYyuifMUnEGHPDoN9E088AAAA
AAAA
--------------ms060609090707020101050207--

From pkyzivat@cisco.com  Thu Mar 31 00:46:27 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9670D28C1BC for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 00:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.65
X-Spam-Level: 
X-Spam-Status: No, score=-108.65 tagged_above=-999 required=5 tests=[AWL=-1.950, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cD+lcNfulPFT for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 00:46:26 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 3AD3928C0D0 for <siprec@ietf.org>; Thu, 31 Mar 2011 00:46:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=2698; q=dns/txt; s=iport; t=1301557686; x=1302767286; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rjFss30p8Tkh+NQniM1avKVqDkJqhVj7aG2yth7MxpI=; b=RhkQvH7M/C0GPhkNFlMgjSdjQqUDYJiZkgwrbwrlD3/tuadE0McV3Ql5 hUBoZWbZCiPTs0RWTB6cftJg5mi/UYEblqyEvG2TOFOHA26n0iUhiMrGM p4t1pa74deIN4Ca8XFdKTAmX2FOzEddB+GzpT2VJoAfN8g2SM8FKr6gAP o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtoDACAxlE2Q/khMgWdsb2JhbAClTxQBARYmJaJenAeFawSNEYNV
X-IronPort-AV: E=Sophos;i="4.63,274,1299456000"; d="scan'208";a="23900398"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 31 Mar 2011 07:48:05 +0000
Received: from [10.61.90.224] (ams3-vpn-dhcp6881.cisco.com [10.61.90.224]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2V7m4BO026588; Thu, 31 Mar 2011 07:48:04 GMT
Message-ID: <4D9431B4.9080300@cisco.com>
Date: Thu, 31 Mar 2011 03:48:04 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <A444A0F8084434499206E78C106220CA086A964E46@MCHP058A.global-ad.net><4D83523C.8030306@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE3489@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A623904DA2008@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB5D463C@TLVMBX01.nice.com> <4D91CF3F.1010809@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386D8@xmb-sjc-234.amer.cisco.com> <4D9251D0.5020006@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E389D5@xmb-sjc-234.amer.cisco.com> <4D9259A3.9080908@cisco.com> <2C2317AF-C679-4977-9150-EF99B6FC3B4B@acmepacket.com> <A444A0F8084434499206E78C106220CA0875AF3984@MCHP058A.global-ad.net> <9E2E57D3-F714-4B0A-B737-A5CD712EC519@acmepacket.com>
In-Reply-To: <9E2E57D3-F714-4B0A-B737-A5CD712EC519@acmepacket.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Leon Portman <Leon.Portman@nice.com>, "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Multiplexing different participants' streams on the same port
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 07:46:27 -0000

The way I took this is:

- the SRC could combine multiple CS streams into a single
   RS m-line, while distinguishing the streams by CNAME.

- the SRC could be receiving a "mixed" stream from CS
   and have info about the CNAMEs and their relationship
   to participans that it wants to pass on

- the SRC could be receiving a stream with multiple
   CNAMEs but not know anything about them, and so describe
   the participant(s) as it knows them without regard to
   CNAMEs.

- the SRC could be passing every CS stream as a separate
   m-line in the RS, with one participant for each.
   Probably each will have a single CNAME but this will not
   be mentioned.

	Thanks,
	Paul

On 3/30/2011 4:03 PM, Hadriel Kaplan wrote:
>
> Maybe I misunderstood the context of this thread.  The email thread appeared to be about using the SSRCs or cnames of the real participant streams, not new ones of the session recording client.  In other words, in RTP RFC 3550 lingo the recording client would be doing a RTP translator model vs. an RTP mixer or endpoint model.  But based on your comments below I take it  you're talking about the recording client being a mixer or endpoint model instead?  If so, then sure you could make the recording client do whatever you want. (and pay the price penalty for doing so)
>
> -hadriel
>
>
> On Mar 30, 2011, at 10:56 AM, Elwell, John wrote:
>
>> Yes, this was the sort of discussion I was trying to provoke. Of course, SRC and SRS implementations will need to be upgraded to support the SIPREC protocol requirements, so requiring some extra things is not out of the question. Clearly one consideration might be whether middleboxes might block such features?
>>
>> John (as chair)
>>
>>
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org
>>> [mailto:siprec-bounces@ietf.org] On Behalf Of Hadriel Kaplan
>>> Sent: 30 March 2011 13:58
>>> To: Paul Kyzivat
>>> Cc: siprec@ietf.org; Leon Portman
>>> Subject: Re: [siprec] Multiplexing different participants'
>>> streams on the same port
>>>
>>>
>>> In practice we see all kinds of things in the RTCP cname,
>>> often unrelated to signaling info.
>>> But you can't rely on it anyway, since you can't rely on
>>> there being any RTCP.
>>>
>>> Furthermore, although I've (shockingly) seen some devices
>>> indicate SSRC in SDP per RFC 5576, it's rare... which means
>>> you won't know the SSRC at call setup time, so it won't be
>>> available to send in metadata at that time, requiring an update.
>>>
>>> I humbly suggest that UDP port numbers are not in short
>>> supply, and using one per stream is both simple and effective.
>>>
>>> -hadriel
>
>

From pkyzivat@cisco.com  Thu Mar 31 01:53:33 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D93FD3A6AD5 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 01:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.56
X-Spam-Level: 
X-Spam-Status: No, score=-109.56 tagged_above=-999 required=5 tests=[AWL=-0.761, BAYES_00=-2.599, J_CHICKENPOX_210=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_29=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7kIGOg2r-K3 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 01:53:32 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id E61E328C0FE for <siprec@ietf.org>; Thu, 31 Mar 2011 01:53:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=1876; q=dns/txt; s=iport; t=1301561711; x=1302771311; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=svcqp23SkV2a/HoBg9zt5UYxoQibp+WzfuhDqoGQRYE=; b=YCxcKNhN3s3aSNzaB+Kq/x/r3EPHppXYVE4R2fah9kDOPh+L8l94pjsS 6CyJvb9qVZn6/Mnck+FsV+wgwiuSw/NmbJXHKdpK3hC9nY1UikNbiROew Y5UcK2hkMohmfNjIuls+BC/1NQNIn2cxajRjcQDpqOhK2bZ3r7HWv2ZsQ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtsDAJhAlE2Q/khLgWdsb2JhbACERqEJFAEBFiYlokSLPpBHgSiDTHcEjRGDVQ
X-IronPort-AV: E=Sophos;i="4.63,274,1299456000"; d="scan'208";a="23911739"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 31 Mar 2011 08:55:10 +0000
Received: from [10.61.90.224] (ams3-vpn-dhcp6881.cisco.com [10.61.90.224]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2V8tAiQ014060; Thu, 31 Mar 2011 08:55:10 GMT
Message-ID: <4D94416E.7070102@cisco.com>
Date: Thu, 31 Mar 2011 04:55:10 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Joe Hildebrand <joe.hildebrand@webex.com>, "siprec@ietf.org" <siprec@ietf.org>
References: <4D93ADCB.2050106@stpeter.im>
In-Reply-To: <4D93ADCB.2050106@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 08:53:34 -0000

Peter/Joe,

Do either of you have any time in the remainder of the week when some of 
us could sit and try to sort out the right way to do the extension data? 
I doubt it would take very long.

	Thanks,
	Paul

On 3/30/2011 6:25 PM, Peter Saint-Andre wrote:
> Here is some quick feedback on draft-ram-siprec-metadata-format-01. I
> hope to review it more fully soon.
>
> 1. I would change application/recording to application/recording+xml in
> accordance with RFC 3023 (many specs illustrate the use of XML media
> types -- see for example RFC 4287).
>
> 2. The large number of<extensiondata/>  elements is a bit confusing in
> the examples.
>
> 3. In Section 5.1, the example has one<extensiondata/>  element
> qualified by the 'urn:ietf:params:xml:ns:siprec' namespace (no other
> namespace is defined) and then multiple<extensiondata/>  elements
> qualified by other namespaces ('http://example.com/groupapp',
> 'http://example.com/sessionapp', etc.). Although those other namespaces
> are certainly *allowed* to use "extensiondata" as an element name
> (that's the beauty of namespaces), it is confusing in this document.
> Perhaps you even meant to have<extensiondata/>  elements qualified by
> the 'urn:ietf:params:xml:ns:siprec' and then child elements qualified by
> other namespaces (in accordance with the schema). However, that is not
> clear in the spec.
>
> 4. There is no built-in datatype for xs:urnuuid, xs:streamMode,
> xs:requester, and so on. See W3C XML Schema Part 2:
>
>     http://www.w3.org/TR/xmlschema-2/#built-in-datatypes
>
> 5. The data in the<name/>  elements with xml:lang="it" really should be
> Giulietta Capuleti and Romeo Montecchi. ;-)
>
> Peter
>
>
>
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From stpeter@stpeter.im  Thu Mar 31 02:05:13 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6099628C1BF for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 02:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.583
X-Spam-Level: 
X-Spam-Status: No, score=-101.583 tagged_above=-999 required=5 tests=[AWL=-0.784, BAYES_00=-2.599, J_CHICKENPOX_210=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_29=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dK98z+uEKgfR for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 02:05:12 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 11DA328C1B6 for <siprec@ietf.org>; Thu, 31 Mar 2011 02:05:12 -0700 (PDT)
Received: from dhcp-12cb.meeting.ietf.org (dhcp-12cb.meeting.ietf.org [130.129.18.203]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9D69540022; Thu, 31 Mar 2011 03:08:41 -0600 (MDT)
Message-ID: <4D944429.10607@stpeter.im>
Date: Thu, 31 Mar 2011 11:06:49 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <4D93ADCB.2050106@stpeter.im> <4D94416E.7070102@cisco.com>
In-Reply-To: <4D94416E.7070102@cisco.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010205070802020502050307"
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 09:05:13 -0000

This is a cryptographically signed message in MIME format.

--------------ms010205070802020502050307
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I am booked through 11 PM tonight.

Tomorrow I have the following windows of time:

07:00-07:30
15:15-16:00

Naturally that time might get filled if issues come up in some of my
working groups. :)

On 3/31/11 10:55 AM, Paul Kyzivat wrote:
> Peter/Joe,
>=20
> Do either of you have any time in the remainder of the week when some o=
f
> us could sit and try to sort out the right way to do the extension data=
?
> I doubt it would take very long.
>=20
>     Thanks,
>     Paul
>=20
> On 3/30/2011 6:25 PM, Peter Saint-Andre wrote:
>> Here is some quick feedback on draft-ram-siprec-metadata-format-01. I
>> hope to review it more fully soon.
>>
>> 1. I would change application/recording to application/recording+xml i=
n
>> accordance with RFC 3023 (many specs illustrate the use of XML media
>> types -- see for example RFC 4287).
>>
>> 2. The large number of<extensiondata/>  elements is a bit confusing in=

>> the examples.
>>
>> 3. In Section 5.1, the example has one<extensiondata/>  element
>> qualified by the 'urn:ietf:params:xml:ns:siprec' namespace (no other
>> namespace is defined) and then multiple<extensiondata/>  elements
>> qualified by other namespaces ('http://example.com/groupapp',
>> 'http://example.com/sessionapp', etc.). Although those other namespace=
s
>> are certainly *allowed* to use "extensiondata" as an element name
>> (that's the beauty of namespaces), it is confusing in this document.
>> Perhaps you even meant to have<extensiondata/>  elements qualified by
>> the 'urn:ietf:params:xml:ns:siprec' and then child elements qualified =
by
>> other namespaces (in accordance with the schema). However, that is not=

>> clear in the spec.
>>
>> 4. There is no built-in datatype for xs:urnuuid, xs:streamMode,
>> xs:requester, and so on. See W3C XML Schema Part 2:
>>
>>     http://www.w3.org/TR/xmlschema-2/#built-in-datatypes
>>
>> 5. The data in the<name/>  elements with xml:lang=3D"it" really should=
 be
>> Giulietta Capuleti and Romeo Montecchi. ;-)
>>
>> Peter
>>
>>
>>
>>
>> _______________________________________________
>> 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


--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms010205070802020502050307
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDMz
MTA5MDY0OVowIwYJKoZIhvcNAQkEMRYEFN9GPyU3OSrs1wcR3kDW5JOxsHsjMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQAmyBInd5RWiPsbS4sYJD1H10xTpaZjun+2i5IY1MW72Fg2veAtPxiOnM/l
X6qjRflt+SGbPvjg5cfJJvX0BBaYZ8EOYL3MuxmB7V+2wT0BGznCaY+zQua263aFKXOdV7xp
tNZhiwbcQcJFRBYwWx6UFvlQe3ZkPUrQZpn4Hc3P1P7JQR9PGfF5CPIakifBUeR5AIsuJ97g
famA21RrC9ZLFNUdPZ0VynAxYT8Q6HnG0oLGaeBIjDz15CNe5V1wohuXmA6swU6/B+rqgiWf
uHo0dXldHC43dCbGZrQusQVNFdmenLD8P+QbDSbSHF/R+8CbGJZP8RGErQuQ3gCejXH4AAAA
AAAA
--------------ms010205070802020502050307--

From john.elwell@siemens-enterprise.com  Thu Mar 31 02:31:02 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45F7A3A6949 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 02:30:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XaaXZT7qcTvG for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 02:30:51 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id B2C4728C227 for <siprec@ietf.org>; Thu, 31 Mar 2011 02:29:46 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3956261 for siprec@ietf.org; Thu, 31 Mar 2011 11:31:25 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 335DB23F028E for <siprec@ietf.org>; Thu, 31 Mar 2011 11:31:25 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 31 Mar 2011 11:31:25 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 31 Mar 2011 11:31:24 +0200
Thread-Topic: IETF 80 SIPREC meeting notes
Thread-Index: AcvvhfA1erHBn/i8RIWZpVd7lJpdbQAAFVIA
Message-ID: <A444A0F8084434499206E78C106220CA0875D11FE7@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A444A0F8084434499206E78C106220CA0875D11FE7MCHP058Agloba_"
MIME-Version: 1.0
Subject: [siprec] FW: IETF 80 SIPREC meeting notes
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 09:31:02 -0000

--_000_A444A0F8084434499206E78C106220CA0875D11FE7MCHP058Agloba_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Ken's notes from the meeting - I will produce minutes in due course.

John

________________________________
From: Ken Rehor (krehor) [mailto:krehor@cisco.com]
Sent: 31 March 2011 10:28
To: Elwell, John
Subject: IETF 80 SIPREC meeting notes


SIPREC

Architecture - Andy Hutton

-01 about to expire, -02 in preparation, will be published shortly



Interaction with MEDIACTRL


=B7         Proposal: do not need another figure to show the SRC case

=B7         Partha will provide a diagram that he proposes for discussion o=
n the list



Interaction with Conference Focus

=B7         Request for diagram

=B7         Will be included in -02 draft


"Metadata supported" indication

=B7         Remove the statement from architecture draft, more of a protoco=
l issue rather than architecture issue


Metadata content

=B7         Remove this list and refer to metadata model document


Metadata delivery

=B7         Remove this list and refer to

=B7         Continue to allow non-SIP means

=B7         =3D=3D> Hadrial agrees, but not include specific implementation=
 details (such as INVITE or UPDATE), defer to protocol spec

=B7         =3D=3D> Keith Drage agreed

Security Considerations

=B7         Remove comments about decryption

=B7         Remove requirement for SRTP



Metadata model
Partha

Updated draft to be submitted after this meeting

Open item: optional start/stop time attribute to be added?

Paul Kyzivat:

JRE: don't tie SIP session level to Recording Session level so that updatin=
g

Joe Hildebrand:  is there something that indicates the final 'end' of the r=
ecording session?

Paul: only if we tie the end of the SIP session to the Recording Session

Brian: how do we know we're done updating metadata?

JRE: end time of recording session doesn't make sense

Charles Eckel: fuzzy for persistent recording session; start/stop must addr=
ess this.

Joe: even if not persistent, there's no end time because other metadata mig=
ht continue to flow

Hadriel:  eventually the Recording Session will end (with a BYE, timer, etc=
.)

JRE: continue discussion on the list

Paul: maybe this means we have the model wrong; all the items contained wit=
hin might be wrong


Communication Session Group start/stop time
JRE: a group of CSs together, do we need a start/stop for the group?
BR: solution is the same as the previous issue


Communication Session start/stop time
JRE:  "YES" we need CS start/stop time


Session State Attribute
BR: not useful
Hadriel: agree. However, we need to figure out what STOP time is:  BYE, etc=
.?

JRE: conclusion we won't include it


Participant
JRE: how do we have indication a participant left? How do we know they're c=
ontributing media streams?
Paul: we don't distinguish between a participant in the CS vs media streams

Media Stream
Same as Participant
Need codec params of Recording Session SDP; continue discussion on list
Open item: Include model of metadata of media *not* recorded
Ken: suggest that we need this requirement

NEXT STEPS

=B7         Request for review of metadata-00 on the mailer

=B7         WGLC

=B7         Align metadata format draft with metadata model draft
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D


Metadata format

Partha

Leon: what is the lifetime of the unique ID?
BR: please add a better example
Paul: IDs must be globally unique for all time
Hadriel: "most horrible thing I've ever seen" - large, and forces a particu=
lar database structure
JRE: still an individual draft, so please propose another solution


Partial XML update
(lots of discussion, continue on mailing list)


Extension Data Element Example

BR: <structure> and <whatever> won't work, must be part of a namespace
Joe: depends on implementation
Peter Saint-Andre:


=B7         Overall need better examples

Open issue: ID generation scope

Open issue: codec parameters in stream element

Duplicate RS SDP in Stream XML?

JRE: in general I don't like duplication, but it may be useful for applicat=
ions
Paul: direction attribute may not be explicit enough
Hadriel:
Leon:


=B7         Continue discussion on the list


Open issue: multiplexing different participants' streams on the same port

(postpone until protocol discussion)


Next Steps
Create Milestone for this topic?
Hadriel: combine metadata model with metadata format
JRE: (consensus)
Paul: suggest merging metadata model with architecture;  merge format and p=
rotocol
BR: continue discussion on list - what makes the most sense for content of =
various documents
JRE: key is to gain agreement on the metadata model and updates, and extens=
ion data; identifiers for both

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D

Protocol

Leon Portman

Partial metadata support:
INVITE and UPDATE for metadata transport

=E8  UPDATE for mid-session updates

Metadata snapshot support

Partha:  REINVITE instead of UPDATE?
Leon:  yes
JRE: benefit of UPDATE is not requirement of offer/answer
Partha: REINVITE or UPDATE?
Hadriel: why reinvite? If SDP chnages it can be updated
BR: is there a reason any particular method can't be used?
Hadriel: why not INFO?

Not all implementations of INFO

Paul: if we require INFO, then we would have to require an INFO package
Hadriel: packages for INFO were defined for this
Charles: still need INFO for complete metadata?
Leon: will use UPDATE


Multiplexing multiple streams


Charles: important to not mandate one mechanism or another
JRE: but mandating something provides interop
Hadriel: 2 or more ways of doing something guarantees non-interop; the othe=
r benefits are edge cases
Paul: might already have this issue e.g. case of conference
Hadriel: disagree.   (discussion of whether the RS gets the conference rost=
er)
Paul: this is an explicit way of representing a participant by cname
Hadriel: Need to clarify "what is the model" the SRC - SRS?  Translator, Mi=
xer, Endpoint?
Leon: but in the architecture doc or protocol?

=E8  Take to list



Recording Awareness

JRE: on media level or session/dialog level?
Paul: legal precedence are about audio. What about video for hearing impair=
ed people? There are different ways of alerting people.
BR: list discussion
Andy: need this at the SIP layer as well as SDP layer
Charles: at the SDP layer it may not be appropriate, so should be at SIP la=
yer.


Recording Indications

BR: just like 'hold' - currently use SDP to cause indication, but also poss=
ible to do at SIP layer
JRE: consensus that this is only on the media layer but will confirm on lis=
t


Recording Preferences

Charles: can we reduce the number of options?
Leon: the words carry specific semantic meanings
Hadriel:  SDP are not commands
Paul: if per media, must be in the SDP
JRE: media or session level?  Consensus is that we must be able to allow a =
user to say they'd permit recording of audio but not video (for example)


OPEN ITEMS;

JRE: not quite ready for WG item yet, but maybe at the next meeting
BR: any big issues with this?  No room comments so it seems we're heading t=
owards making this a WG item


JRE: next virtual meeting middle of May































For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--_000_A444A0F8084434499206E78C106220CA0875D11FE7MCHP058Agloba_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19019">
<STYLE>@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
	MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE:=
 11pt; mso-style-priority: 34
}
LI.MsoListParagraph {
	MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE:=
 11pt; mso-style-priority: 34
}
DIV.MsoListParagraph {
	MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE:=
 11pt; mso-style-priority: 34
}
SPAN.EmailStyle17 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: pe=
rsonal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US link=3Dblue vLink=3Dpurple>
<DIV><SPAN class=3D088283009-31032011><FONT color=3D#0000ff size=3D2 face=
=3DArial>Ken's=20
notes from the meeting - I will produce minutes in due=20
course.</FONT></SPAN></DIV>
<DIV><SPAN class=3D088283009-31032011><FONT color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D088283009-31032011><FONT color=3D#0000ff size=3D2=20
face=3DArial>John</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; MARGIN-RIGHT: 0px"=20
dir=3Dltr>
  <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>From:</B> Ken Rehor (krehor)=20
  [mailto:krehor@cisco.com] <BR><B>Sent:</B> 31 March 2011 10:28<BR><B>To:<=
/B>=20
  Elwell, John<BR><B>Subject:</B> IETF 80 SIPREC meeting=20
  notes<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DWordSection1>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">SIPREC<o:p></o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Architecture =96 And=
y=20
  Hutton<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">-01 about to expire,=
 -02 in=20
  preparation, will be published shortly<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Interaction with=20
  MEDIACTRL<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l6 level1 lfo1"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Proposal: =
do not=20
  need another figure to show the SRC case<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l6 level1 lfo1"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Partha wil=
l=20
  provide a diagram that he proposes for discussion on the=20
  list<o:p></o:p></SPAN></P>
  <P class=3DMsoListParagraph><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Interaction with Con=
ference=20
  Focus<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Request fo=
r=20
  diagram<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Will be in=
cluded=20
  in -02 draft<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">=93Metadata supporte=
d=94=20
  indication<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo3"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Remove the=
=20
  statement from architecture draft, more of a protocol issue rather than=20
  architecture issue<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Metadata=20
  content<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo3"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Remove thi=
s list=20
  and refer to metadata model document<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Metadata=20
  delivery<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo3"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Remove thi=
s list=20
  and refer to <o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo3"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Continue t=
o allow=20
  non-SIP means<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo3"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN=20
  style=3D"FONT-FAMILY: Wingdings; FONT-SIZE: 10pt">=E8</SPAN><SPAN=20
  style=3D"FONT-SIZE: 10pt"> Hadrial agrees, but not include specific=20
  implementation details (such as INVITE or UPDATE), defer to protocol=20
  spec<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo3"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN=20
  style=3D"FONT-FAMILY: Wingdings; FONT-SIZE: 10pt">=E8</SPAN><SPAN=20
  style=3D"FONT-SIZE: 10pt"> Keith Drage agreed<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Security=20
  Considerations<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; MARGIN-LEFT: 0.25in; mso-list: l4 level=
1 lfo4"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Remove com=
ments=20
  about decryption<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; MARGIN-LEFT: 0.25in; mso-list: l4 level=
1 lfo4"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Remove=20
  requirement for SRTP<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Metadata=20
  model<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Partha<o:p></o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Updated draft to be =
submitted=20
  after this meeting<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Open item: optional=
=20
  start/stop time attribute to be added?<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Paul Kyzivat:&nbsp; <o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: don=92t tie SIP session level to Recording=
 Session=20
  level so that updating<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Joe Hildebrand:&nbsp; is there something that=20
  indicates the final =91end=92 of the recording session?<o:p></o:p></SPAN>=
</P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Paul: only if we tie the end of the SIP session=
 to the=20
  Recording Session<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Brian: how do we know we=92re done updating=20
  metadata?<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: end time of recording session doesn=92t ma=
ke=20
  sense<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Charles Eckel: fuzzy for persistent recording s=
ession;=20
  start/stop must address this.&nbsp; <o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Joe: even if not persistent, there=92s no end t=
ime=20
  because other metadata might continue to flow<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Hadriel:&nbsp; eventually the Recording Session=
 will=20
  end (with a BYE, timer, etc.)<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: continue discussion on the=20
  list<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Paul: maybe this means we have the model wrong;=
 all=20
  the items contained within might be wrong<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Communication Sessio=
n Group=20
  start/stop time<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: a group of CSs together, do we need a star=
t/stop=20
  for the group?<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">BR: solution is the same as the previous=20
  issue<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Communication Sessio=
n=20
  start/stop time<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE:&nbsp; =93YES=94 we need CS start/stop=20
  time<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Session State=20
  Attribute<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">BR: not useful<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Hadriel: agree. However, we need to figure out =
what=20
  STOP time is:&nbsp; BYE, etc.?<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: conclusion we won=92t include=20
  it<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Participant<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: how do we have indication a participant le=
ft? How=20
  do we know they=92re contributing media streams?<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Paul: we don=92t distinguish between a particip=
ant in=20
  the CS vs media streams<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Media=20
  Stream<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Same as Participant<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Need codec params of Recording Session SDP; con=
tinue=20
  discussion on list<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Open item: Include model of metadata of media=20
  *<B>not</B>* recorded<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 1in" class=3DMsoNormal><SPAN style=3D"FONT-SIZE:=
 10pt">Ken:=20
  suggest that we need this requirement<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">NEXT=20
  STEPS<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l3 level1 lfo5"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Request fo=
r=20
  review of metadata-00 on the mailer<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l3 level1 lfo5"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN=20
  style=3D"FONT-SIZE: 10pt">WGLC<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l3 level1 lfo5"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Align meta=
data=20
  format draft with metadata model draft<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></SPAN></P=
>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Metadata=20
  format<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Partha <o:p></o:p></=
SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Leon: what is the li=
fetime of=20
  the unique ID? <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">BR: please add a bet=
ter=20
  example<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Paul: IDs must be gl=
obally=20
  unique for all time<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Hadriel: =93most hor=
rible thing=20
  I=92ve ever seen=94 =96 large, and forces a particular database=20
  structure<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">JRE: still an indivi=
dual=20
  draft, so please propose another solution<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Partial XML=20
  update<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">(lots of discussion,=
 continue=20
  on mailing list)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Extension Data Eleme=
nt=20
  Example<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">BR: &lt;structure&gt=
; and=20
  &lt;whatever&gt; won=92t work, must be part of a namespace<o:p></o:p></SP=
AN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Joe: depends on=20
  implementation<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Peter Saint-Andre:&n=
bsp;=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l5 level1 lfo6"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Overall ne=
ed=20
  better examples<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Open issue: ID gener=
ation=20
  scope<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Open issue: codec pa=
rameters=20
  in stream element<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Duplicate RS SDP in Stream XML?<o:p></o:p></SPA=
N></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: in general I don=92t like duplication, but=
 it may=20
  be useful for applications<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Paul: direction attribute may not be explicit=20
  enough<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Hadriel: <o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Leon: <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; mso-list: l5 level1 lfo6"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Symbol; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=B7<SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Continue=20
  discussion on the list<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Open issue: multiple=
xing=20
  different participants=92 streams on the same port<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">(postpone until prot=
ocol=20
  discussion)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Next=20
  Steps<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Create Milestone for=
 this=20
  topic?<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Hadriel: combine metadata model with metadata=20
  format<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: (consensus)<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Paul: suggest merging metadata model with=20
  architecture; &nbsp;merge format and protocol<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">BR: continue discussion on list =96 what makes =
the most=20
  sense for content of various documents<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: key is to gain agreement on the metadata m=
odel=20
  and updates, and extension data; identifiers for both<o:p></o:p></SPAN></=
P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt">Protocol<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Leon=20
  Portman<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Partial metadata=20
  support:<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">INVITE and UPDATE for metadata=20
  transport<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; MARGIN-LEFT: 0.75in; mso-list: l2 level=
1 lfo7"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Wingdings; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=E8<SPAN style=3D"FONT: 7pt 'Times New Roman'"=
>&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">UPDATE for=
=20
  mid-session updates<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Metadata snapshot=20
  support<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Partha:&nbsp; REINVITE instead of UPDATE?=20
  <o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Leon:&nbsp; yes<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">JRE: benefit of UPDATE is not requirement of=20
  offer/answer<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Partha: REINVITE or UPDATE?<o:p></o:p></SPAN></=
P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Hadriel: why reinvite? If SDP chnages it can be=
=20
  updated<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">BR: is there a reason any particular method can=
=92t be=20
  used?<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Hadriel: why not INFO?<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Not all implementations of INFO<o:p></o:p></SPA=
N></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Paul: if we require INFO, then we would have to=
=20
  require an INFO package<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Hadriel: packages for INFO were defined for=20
  this<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Charles: still need INFO for complete=20
  metadata?<o:p></o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt">Leon: will use UPDATE<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Multiplexing multipl=
e=20
  streams<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Charles: important t=
o not=20
  mandate one mechanism or another<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">JRE: but mandating s=
omething=20
  provides interop<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Hadriel: 2 or more w=
ays of=20
  doing something guarantees non-interop; the other benefits are edge=20
  cases<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Paul: might already =
have this=20
  issue e.g. case of conference<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Hadriel:=20
  disagree.&nbsp;&nbsp; (discussion of whether the RS gets the conference=20
  roster)<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Paul: this is an exp=
licit way=20
  of representing a participant by cname<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Hadriel: Need to cla=
rify=20
  =93what is the model=94 the SRC =96 SRS? &nbsp;Translator, Mixer,=20
  Endpoint?<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Leon: but in the arc=
hitecture=20
  doc or protocol?<o:p></o:p></SPAN></P>
  <P style=3D"TEXT-INDENT: -0.25in; MARGIN-LEFT: 0.75in; mso-list: l2 level=
1 lfo7"=20
  class=3DMsoListParagraph><![if !supportLists]><SPAN=20
  style=3D"FONT-FAMILY: Wingdings; FONT-SIZE: 10pt"><SPAN=20
  style=3D"mso-list: Ignore">=E8<SPAN style=3D"FONT: 7pt 'Times New Roman'"=
>&nbsp;=20
  </SPAN></SPAN></SPAN><![endif]><SPAN style=3D"FONT-SIZE: 10pt">Take to=20
  list<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Recording=20
  Awareness<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">JRE: on media level =
or=20
  session/dialog level?<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Paul: legal preceden=
ce are=20
  about audio. What about video for hearing impaired people? There are diff=
erent=20
  ways of alerting people.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">BR: list=20
  discussion<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Andy: need this at t=
he SIP=20
  layer as well as SDP layer<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Charles: at the SDP =
layer it=20
  may not be appropriate, so should be at SIP layer. <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Recording=20
  Indications<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">BR: just like =91hol=
d=92 =96=20
  currently use SDP to cause indication, but also possible to do at SIP=20
  layer<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">JRE: consensus that =
this is=20
  only on the media layer but will confirm on list<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Recording=20
  Preferences<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Charles: can we redu=
ce the=20
  number of options?<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Leon: the words carr=
y=20
  specific semantic meanings<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Hadriel: &nbsp;SDP a=
re not=20
  commands<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">Paul: if per media, =
must be=20
  in the SDP<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">JRE: media or sessio=
n=20
  level?&nbsp; Consensus is that we must be able to allow a user to say the=
y=92d=20
  permit recording of audio but not video (for example)<o:p></o:p></SPAN></=
P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">OPEN=20
  ITEMS;<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">JRE: not quite ready=
 for WG=20
  item yet, but maybe at the next meeting<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">BR: any big issues w=
ith=20
  this?&nbsp; No room comments so it seems we=92re heading towards making t=
his a=20
  WG item<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">JRE: next virtual me=
eting=20
  middle of May<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P style=3D"MARGIN-LEFT: 0.5in" class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 8pt">For corporate=
 legal=20
  information go=20
  to:<BR>http://www.cisco.com/web/about/doing_business/legal/cri/index.html=
<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

--_000_A444A0F8084434499206E78C106220CA0875D11FE7MCHP058Agloba_--

From john.elwell@siemens-enterprise.com  Thu Mar 31 02:31:52 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 012CD28C20C for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 02:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.649
X-Spam-Level: 
X-Spam-Status: No, score=-101.649 tagged_above=-999 required=5 tests=[AWL=-0.850, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, J_CHICKENPOX_62=0.6, J_CHICKENPOX_64=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g0WHCL3i6Lc1 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 02:31:48 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 43B0428C209 for <siprec@ietf.org>; Thu, 31 Mar 2011 02:31:21 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3962651 for siprec@ietf.org; Thu, 31 Mar 2011 11:33:00 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 36A951EB82AE for <siprec@ietf.org>; Thu, 31 Mar 2011 11:33:00 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 31 Mar 2011 11:33:00 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 31 Mar 2011 11:32:59 +0200
Thread-Topic: Notes
Thread-Index: Acvvhp+0H2bDzSPyQlCt7UvKtlLhnQ==
Message-ID: <A444A0F8084434499206E78C106220CA0875D11FEB@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] Notes
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 09:31:52 -0000

Michael Proctor's notes from meeting - I will produce minutes in due course=
.

John

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D

SIPREC - Thursday 9am (Barcelona)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D

draft-ietf-siprec-req - Ken Rehor
Ken presented his slides, with minor clarifications from John Elwell.
No other comments.

draft-ietf-siprec-architecture - Andy Hutton
Andy presented his slides:
Open issue: Figure to show how to decompose SRC?
  Parthasarathi:=20
    Makes decomposition more obvious? - Would like picture of SRC like SRS.
    Will supply ascii art for review on list in next few days.
Request for Conference Focus Interaction diagram (act as SRC)
  Andy to produce and update in next version.
Proposal: Remove metadata supported indication statement?
  No objections.
Proposal: Remove list of metadata content, reference the model instead
  No objections.
Proposal: List INVITE/UPDATE + non-SIP means only for metadata delivery?
  Hadriel Kaplan: Agrees, but don't mention specific methods
    (e.g. INVITE/UPDATE)
  Keith Drage: Clarified that this repeats stuff in the protocol document.
Proposal: Remove section of Security Considerations
  No objections.
Proposal: Remove requirement for SRTP from Security Considerations
  No objections.

draft-ram-siprec-metadata - Parthasarathi R
Partha presented his slides.
Open item:  Optional start/stop time attribute for Recording Session?
  Paul Kyzivat: Expressed similar concerns.
  Joe Hildebrand: Updates to metadata may have no known last event.
  Chair summary: Endtime doesn't make sense - we can never figure it out.
  Hadriel Kaplan: How is there not a 'stop time' for the recording session?
  Chair: Take this to the list.  Dispute over whether a recording session
    can have a meaningful stop time.
  Paul Kyzivat: Does this mean we have the model wrong?
  Chair: That will make an interesting list discussion!
Open item: Optional start/stop time attribute for Communication Session Gro=
up?
  No opinions expressed. Same problems as previous item.
Open item: Optional start/stop time attribute for Communication Session?
  No objections to saying YES.
Open item: Should session state attribute indicate trying/proceed/early/con=
firmed/terminated?
  Brian Rosen(as person): Doesn't seem useful.
  Hadriel Kaplan: Agrees, but notes that session stop time needs to be
    defined (on BYE, or 200 to BYE etc).
  Consensus to not include session state attribute.
Open item: Optional start/stop time attribute for Participant?
  John Elwell(as person): How do we know a participant has left?
  Paul Kyzivat: You can start/stop relationships to other entities,
    not necessarily stop a participant?  Need to capture all nuances.
  Brian Rosen(as person): Need to be clear this is session start/stop
    for this participants.  Other indications for media etc.
  Was consensus reached? ~~~ Check audio ~~~
Open item: Media stream: Codec params text change
  Not clear - taken to mailing list.
Open item: Media stream: Need to model unrecorded media streams (offered ce=
rtain types, not accepted by SRS)?
  Ken Rehon: Yes
  Consensus is yes.

draft-ram-siprec-metadata-format - Parthasarathi R
Partha presented his slides.
Discussion on recording metadata example:
  Leon: What is the lifetime of the ids?
  Brian Rosen: Add example for metadata example.
  Paul Kyzivat: IDs are UUIDs - universal lifetime.
  Hadriel Kaplan: Insanely complicated.  Forces particular data=20
    representation on implementors.
  Joe Hildebrand: Still deciding XML processing semantics - nailing down
    syntax best done after this.  UUIDs can be invented on sending side
    which allows updates before waiting for a round trip for allocation.
  Paul Kyzivat: Different key strategies have been considered, scope for
    alternative approaches and a beauty contest.
  Chair: Does anyone other than Hadriel have concerns?
  Hadriel Kaplan:  To reiterate - this forces a particular data
    representation on the database, not simply a beauty contest.
  Chair: Tentatively proceed with rest of slides/issues - partial consensus=
.
Partial XML update:
  Hadriel Kaplan: Use a single UUID for the parent element, not one ID for
    each leaf.
  Paul Kyzivat: This will prevent referring to an element in a completely
    different context.  No requirement for this yet, but...
  Joe Hildebrand:  Hadriel's approach requires coordination for creation
    of simple short ids - UUIDs means you can forget this problem.
  Hadriel Kaplan: Paul's problem can be handled by referring to the parent
    id and then the sub-id.  Think namespaces.
  Joe Hildebrand: Can use other URIs if you want? ~~~ Check audio ~~~
Extension Data Element Example:
  Brian Rosen: That won't work.
  Joe Hildebrand:=20
  Paul Kyzivat: Type of parent is not clear from just a UUID.  Implies
    painful database type.
  John Elwell: More mailing list discussion required.
  StPeter: XML problems defining the extensiondata
  Paul Kyzivat: Consider it an expression of intent
  Joe Hildebrand: ~~~ Check audio ~~~
  StPeter: Thinks the examples are just wrong.
  John Elwell: More mailing list discussion required.
Open issue: ID generation scope
  Chair: Repetition of previous discussion
Open issue: Codec parameter in stream element
  John Elwell (as person): In general, dislikes duplication.  Not much
    of an issue here - we can solve this.
  Paul Kyzivat: Direction attribute is most concerning.  Maybe draw some
    inferences, but not explicit enough to know.  SRS could convert info
    from SDP.
  John Elwell: Let's have that discussion offline.
  Hadriel Kaplan: Asking for conflicts with SDP.
  Leon Portman: ~~~ Check audio ~~~
  Chair: Running out of time - continue discussion on list re relationship
    between metadata in XML and SDP from recording session.
Open issue: Multiplexing different participants' streams on same port
  Chair: Is this premature before discussing the protocol?
Create milestone for this topic?
  Brian Rosen: Should we merge model and format in one document?
  Hadriel Kaplan: Yes
  Paul Kyzivat: Conceptually, model should merge with architecture, and
    maybe format and protocol should merge.  Doesn't much care.
  Brian Rosen:  What would a newbie expect?  What would make most sense?
Chair: Too early to consider adopting.
  Home in on questions of identifiers and metadata model/updates, and exten=
sion data.

draft-portman-siprec-protocol - Leon Portman
Leon presented his slides.
Partial Metadata Support: INFO will be removed from next version.
Metadata Snapshot Support:
  Parthi: Can we use reINVITE instead of UPDATE?
  Leon: Yes.
  John Elwell: reINVITE forces SDP renegotiation, which is sometimes
    useful but not always.
  Hadriel Kaplan: This should be a SIP layer decision, not a SIPREC decisio=
n.
  Brian Rosen: Is there a reason we should restrict e.g. OPTIONS for metada=
ta?
  Hadriel Kaplan: No
  Paul Kyzivat:  Using INFO would require info-package, but we wouldn't use
    same package for INVITE/UPDATE etc, hence extra work.
  Hadriel Kaplan: ~~~ Check audio ~~~
  Charles?: Do we need INFO to request full snapshot?
  Leon: No - other mechanisms exist.
  Parthi: ~~~ Check audio ~~~
Multiplexing media streams:
  Charles?: We shouldn't mandate one mechanism or another.
  John Elwell: Not mandating anything leads to non-interop.
  Hadriel Kaplan: 2 ways to do something leads to non-interop.  Not seen
    good reasons to require multiplexing.
  Parthi: Just a negotiation.
  (many): Not it isn't
  John Elwell: Not sure there is an explicit negotiation for this.
  Paul Kyzivat: We haven't introduced a new issue.
  Hadriel Kaplan: Disagrees.
  (stopped following the nuances of the argument here - sorry)
  Paul Kyzivat: Can we get the relationship between roster and CNAMEs?
    Would be nice to pass this information if you ever have it?
  John Elwell: Clarifying which session we are talking about SSRCs/CNAMEs
  Hadriel Kaplan: What is your RTP model? Translator or endpoint?
  Chairs: We need to sort this out - good list discussion.
  Charles?: Hoping SRC wouldn't need to transcode.  Wouldn't rule it out
    but doesn't want to force it.
  Brian Rosen: Need to define what SRS must accept, and what SRC could use.
  Gonzalo: Let's make sure rtcweb,clue and siprec are all on the same page.
  Brian Rosen: Cope with what is thrown at us, not dictate.
Recording awareness: SDP attribute a=3Drecording-aware
  John Elwell: Is this SDP or SIP layer?
  Paul Kyzivat: What about accessibility?  'Tones' for deaf ppl using sign =
language?
  Brian Rosen: Is there a way to indicate recording other than by in-band m=
edia?
  More list discussion.
  Andy Hutton: Def need at SIP layer, maybe at SDP layer too.
  More list discussion.
  Charles?: Need at SIP layer, because SDP layer implies in-band - like Pau=
lK's comments.
    A recording-aware UA would be able to alert the user in a more appropri=
ate manner.
  More list discussion.
Recording indications: on/off/paused: session or media level?
  Brian Rosen: Analgous to 'hold' which is done by sendrecv at media level
  Consensus for media level
Recording preferences: record/norecord/pause/resume: session or media level=
?
  Charles?: Wants to minimise sdp attributes.
  John Elwell: Let's focus on which level we want it at?
  Hadriel Kaplan: Is this a command?  If so, it doesn't belong in SDP.
  Paul Kyzivat: If per medium, realistically needs to be SDP.  SDP has thin=
gs
    that are declared or negotiated.
  John Elwell: Let's focus on which level we want it at?
  Brian Rosen: Does anyone think it isn't media level?
  No dissenting opinions.
  Brian Rosen: Seek expert advice on whether it is appropriate for SDP.
Open Items: Sync/Async error handling
  No substantive discussion.
Open Items: Session Timer usage
  No substantive discussion.
Open Items: Metadata support discovery
  No substantive discussion.
John Elwell: More items to tie down, not in a position to adopt just yet.
Brian Rosen: Is anyone planning another draft? Is there any question of 'if=
'
  this will become a wg item.  No response, so assuming this is a case of
  'when' not 'if' this becomes a wg item.
John Elwell: Planning another virtual meeting in May. =

From pkyzivat@cisco.com  Thu Mar 31 05:17:45 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C3153A6AC4 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 05:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.509
X-Spam-Level: 
X-Spam-Status: No, score=-109.509 tagged_above=-999 required=5 tests=[AWL=-0.710, BAYES_00=-2.599, J_CHICKENPOX_210=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_29=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TA0pZHFp6BCV for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 05:17:44 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 64B583A6767 for <siprec@ietf.org>; Thu, 31 Mar 2011 05:17:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=2656; q=dns/txt; s=iport; t=1301573964; x=1302783564; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=jTKYQOt993wOPvfFN5MXqIkzTSJFKEzffQjujZzfFr4=; b=W1VCZq5hAcPYn0ocqxaP3auXcuEf47m+U5YHuXi4B3JNZwkK7EiAwqdO N7iHxF6JgCAUQlHsjDt1y7x02/25KNoYCyyuNRNm3ZKPiloCFtYUzyUWE Ouxw1Ti+S71uOYgOwZcaowefb+FK/mkc3IOHX0yxjnynzsfyFkksrhp04 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtsDAB5wlE2Q/khNgWdsb2JhbACERqEHFAEBFiYliHmZXIs+kFKBKINMdwSNEYNV
X-IronPort-AV: E=Sophos;i="4.63,275,1299456000"; d="scan'208";a="23945269"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 31 Mar 2011 12:19:23 +0000
Received: from [10.61.86.68] (ams3-vpn-dhcp5701.cisco.com [10.61.86.68]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2VCJNIr016773; Thu, 31 Mar 2011 12:19:23 GMT
Message-ID: <4D94714B.8010102@cisco.com>
Date: Thu, 31 Mar 2011 08:19:23 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4D93ADCB.2050106@stpeter.im> <4D94416E.7070102@cisco.com> <4D944429.10607@stpeter.im>
In-Reply-To: <4D944429.10607@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 12:17:45 -0000

On 3/31/2011 5:06 AM, Peter Saint-Andre wrote:
> I am booked through 11 PM tonight.
>
> Tomorrow I have the following windows of time:
>
> 07:00-07:30
> 15:15-16:00
>
> Naturally that time might get filled if issues come up in some of my
> working groups. :)

But you also have 11-12pm tonite? :-)
(That is much better for me than the others.)

Maybe its just too late in the week to hope for this.
We can take it to the list.

	Thanks,
	Paul

> On 3/31/11 10:55 AM, Paul Kyzivat wrote:
>> Peter/Joe,
>>
>> Do either of you have any time in the remainder of the week when some of
>> us could sit and try to sort out the right way to do the extension data?
>> I doubt it would take very long.
>>
>>      Thanks,
>>      Paul
>>
>> On 3/30/2011 6:25 PM, Peter Saint-Andre wrote:
>>> Here is some quick feedback on draft-ram-siprec-metadata-format-01. I
>>> hope to review it more fully soon.
>>>
>>> 1. I would change application/recording to application/recording+xml in
>>> accordance with RFC 3023 (many specs illustrate the use of XML media
>>> types -- see for example RFC 4287).
>>>
>>> 2. The large number of<extensiondata/>   elements is a bit confusing in
>>> the examples.
>>>
>>> 3. In Section 5.1, the example has one<extensiondata/>   element
>>> qualified by the 'urn:ietf:params:xml:ns:siprec' namespace (no other
>>> namespace is defined) and then multiple<extensiondata/>   elements
>>> qualified by other namespaces ('http://example.com/groupapp',
>>> 'http://example.com/sessionapp', etc.). Although those other namespaces
>>> are certainly *allowed* to use "extensiondata" as an element name
>>> (that's the beauty of namespaces), it is confusing in this document.
>>> Perhaps you even meant to have<extensiondata/>   elements qualified by
>>> the 'urn:ietf:params:xml:ns:siprec' and then child elements qualified by
>>> other namespaces (in accordance with the schema). However, that is not
>>> clear in the spec.
>>>
>>> 4. There is no built-in datatype for xs:urnuuid, xs:streamMode,
>>> xs:requester, and so on. See W3C XML Schema Part 2:
>>>
>>>      http://www.w3.org/TR/xmlschema-2/#built-in-datatypes
>>>
>>> 5. The data in the<name/>   elements with xml:lang="it" really should be
>>> Giulietta Capuleti and Romeo Montecchi. ;-)
>>>
>>> Peter
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>
>

From Internet-Drafts@ietf.org  Thu Mar 31 07:00:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EA2D28C0F7; Thu, 31 Mar 2011 07:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 83duRcKCdtPR; Thu, 31 Mar 2011 07:00:01 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7ED2F3A6BE1; Thu, 31 Mar 2011 07:00:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.14
Message-ID: <20110331140001.19024.14899.idtracker@localhost>
Date: Thu, 31 Mar 2011 07:00:01 -0700
Cc: siprec@ietf.org
Subject: [siprec] I-D Action:draft-ietf-siprec-req-09.txt
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 14:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP Recording Working Group of the IETF.


	Title           : Use Cases and Requirements for SIP-based Media Recording (SIPREC)
	Author(s)       : K. Rehor, et al.
	Filename        : draft-ietf-siprec-req-09.txt
	Pages           : 15
	Date            : 2011-03-31

Session recording is a critical requirement in many business
communications environments such as call centers and financial
trading floors.  In some of these environments, all calls must be
recorded for regulatory and compliance reasons.  In others, calls may
be recorded for quality control or business analytics.

Recording is typically performed by sending a copy of the session
media to the recording devices.  This document specifies requirements
for extensions to SIP that will manage delivery of RTP media to a
recording device.  This is being referred to as SIP-based Media
Recording.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-siprec-req-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-siprec-req-09.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-31064850.I-D@ietf.org>


--NextPart--

From sorton@broadsoft.com  Thu Mar 31 08:30:12 2011
Return-Path: <sorton@broadsoft.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 401A83A6983 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 08:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.123
X-Spam-Level: 
X-Spam-Status: No, score=0.123 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_210=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_29=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QzcYOLFnrsZ1 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 08:30:11 -0700 (PDT)
Received: from smtp-out01.seaservers.net (smtpedge.partnerhosted.com [173.225.22.21]) by core3.amsl.com (Postfix) with ESMTP id 5F1C03A680E for <siprec@ietf.org>; Thu, 31 Mar 2011 08:30:11 -0700 (PDT)
Received: from EXMBXCLUS01.citservers.local ([fe80::a488:d1ec:a706:3a6d]) by CASUMHUB02.citservers.local ([::1]) with mapi; Thu, 31 Mar 2011 08:31:52 -0700
From: Scott Orton <sorton@broadsoft.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, Peter Saint-Andre <stpeter@stpeter.im>
Date: Thu, 31 Mar 2011 08:28:30 -0700
Thread-Topic: [siprec] draft-ram-siprec-metadata-format-01
Thread-Index: AcvvneGYaEpydjZiTmOKSohan6QgKQAGBOGg
Message-ID: <21866C7FE177A4449B9136B5B24B1B130BC01128BC@EXMBXCLUS01.citservers.local>
References: <4D93ADCB.2050106@stpeter.im> <4D94416E.7070102@cisco.com> <4D944429.10607@stpeter.im> <4D94714B.8010102@cisco.com>
In-Reply-To: <4D94714B.8010102@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 15:30:12 -0000

Here is some feedback on draft-ram-siprec-metadata-format-01.=20

In the xml schema, the group is not listed as an element in the sequence fo=
r the recording-metadata, which conflicts with the example in 5.1.

In addition, I found it confusing that the extension data is included in th=
e participant type but not included in any of the other defined elements in=
 the recording-metadata. I think it might be good idea to include the exten=
sion data as last element in the sequences for the group, session, etc. As =
that would eliminate the need for the parent attribute in the extension dat=
a assuming it stays close to its current format.


Regards,
   Scott
 =20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Paul Kyzivat
Sent: Thursday, March 31, 2011 7:19 AM
To: Peter Saint-Andre
Cc: siprec@ietf.org
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01



On 3/31/2011 5:06 AM, Peter Saint-Andre wrote:
> I am booked through 11 PM tonight.
>
> Tomorrow I have the following windows of time:
>
> 07:00-07:30
> 15:15-16:00
>
> Naturally that time might get filled if issues come up in some of my
> working groups. :)

But you also have 11-12pm tonite? :-)
(That is much better for me than the others.)

Maybe its just too late in the week to hope for this.
We can take it to the list.

	Thanks,
	Paul

> On 3/31/11 10:55 AM, Paul Kyzivat wrote:
>> Peter/Joe,
>>
>> Do either of you have any time in the remainder of the week when some of
>> us could sit and try to sort out the right way to do the extension data?
>> I doubt it would take very long.
>>
>>      Thanks,
>>      Paul
>>
>> On 3/30/2011 6:25 PM, Peter Saint-Andre wrote:
>>> Here is some quick feedback on draft-ram-siprec-metadata-format-01. I
>>> hope to review it more fully soon.
>>>
>>> 1. I would change application/recording to application/recording+xml in
>>> accordance with RFC 3023 (many specs illustrate the use of XML media
>>> types -- see for example RFC 4287).
>>>
>>> 2. The large number of<extensiondata/>   elements is a bit confusing in
>>> the examples.
>>>
>>> 3. In Section 5.1, the example has one<extensiondata/>   element
>>> qualified by the 'urn:ietf:params:xml:ns:siprec' namespace (no other
>>> namespace is defined) and then multiple<extensiondata/>   elements
>>> qualified by other namespaces ('http://example.com/groupapp',
>>> 'http://example.com/sessionapp', etc.). Although those other namespaces
>>> are certainly *allowed* to use "extensiondata" as an element name
>>> (that's the beauty of namespaces), it is confusing in this document.
>>> Perhaps you even meant to have<extensiondata/>   elements qualified by
>>> the 'urn:ietf:params:xml:ns:siprec' and then child elements qualified b=
y
>>> other namespaces (in accordance with the schema). However, that is not
>>> clear in the spec.
>>>
>>> 4. There is no built-in datatype for xs:urnuuid, xs:streamMode,
>>> xs:requester, and so on. See W3C XML Schema Part 2:
>>>
>>>      http://www.w3.org/TR/xmlschema-2/#built-in-datatypes
>>>
>>> 5. The data in the<name/>   elements with xml:lang=3D"it" really should=
 be
>>> Giulietta Capuleti and Romeo Montecchi. ;-)
>>>
>>> Peter
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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

From partr@cisco.com  Thu Mar 31 08:40:41 2011
Return-Path: <partr@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB8773A694C for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 08:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.163
X-Spam-Level: 
X-Spam-Status: No, score=-9.163 tagged_above=-999 required=5 tests=[AWL=-0.364, BAYES_00=-2.599, J_CHICKENPOX_210=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_29=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GB1oFdwMaGy3 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 08:40:40 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id DB4983A6844 for <siprec@ietf.org>; Thu, 31 Mar 2011 08:40:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=4878; q=dns/txt; s=iport; t=1301586140; x=1302795740; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=qDTk7h3nrTQdK5vFFXj+u5uRRzOXKV+jKA1ZqtDCBiA=; b=Tjdkz+iWVC2Gr1THvt0hnuexm4EN0KErZ5hC1Y0gh+R2fSzPhVfcu6/P J3vikhMEQKVoaHrYW+AwxDCT8HAtaDNOl1kmc3KcAblOPhoN7REGbHoOj kmwM5Pa7R3eE2CNTE57rqTWz+7BhDV0LOnxzNzIkz+uHe8QtQ10mWHWEh w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYAAP2flE2Q/khNgWdsb2JhbACYDY1AFAEBFiYliHmaQZwfhWsEhT+LLQ
X-IronPort-AV: E=Sophos;i="4.63,276,1299456000"; d="scan'208";a="23981749"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 31 Mar 2011 15:42:14 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2VFgBeg030750; Thu, 31 Mar 2011 15:42:14 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 31 Mar 2011 21:12:13 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 31 Mar 2011 21:12:11 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623904E979BB@XMB-BGL-411.cisco.com>
In-Reply-To: <21866C7FE177A4449B9136B5B24B1B130BC01128BC@EXMBXCLUS01.citservers.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] draft-ram-siprec-metadata-format-01
Thread-Index: AcvvneGYaEpydjZiTmOKSohan6QgKQAGBOGgAADiJqA=
References: <4D93ADCB.2050106@stpeter.im> <4D94416E.7070102@cisco.com><4D944429.10607@stpeter.im> <4D94714B.8010102@cisco.com> <21866C7FE177A4449B9136B5B24B1B130BC01128BC@EXMBXCLUS01.citservers.local>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Scott Orton" <sorton@broadsoft.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, "Peter Saint-Andre" <stpeter@stpeter.im>
X-OriginalArrivalTime: 31 Mar 2011 15:42:13.0125 (UTC) FILETIME=[3456CB50:01CBEFBA]
Cc: siprec@ietf.org
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 15:40:41 -0000

Scott,

Thanks for the feedback.

Thanks
Partha

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Scott Orton
Sent: Thursday, March 31, 2011 8:59 PM
To: Paul Kyzivat (pkyzivat); Peter Saint-Andre
Cc: siprec@ietf.org
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01

Here is some feedback on draft-ram-siprec-metadata-format-01.=20

In the xml schema, the group is not listed as an element in the sequence
for the recording-metadata, which conflicts with the example in 5.1.

<Partha> Agreed. I'll update in the next revision </partha>

In addition, I found it confusing that the extension data is included in
the participant type but not included in any of the other defined
elements in the recording-metadata. I think it might be good idea to
include the extension data as last element in the sequences for the
group, session, etc. As that would eliminate the need for the parent
attribute in the extension data assuming it stays close to its current
format.

<partha> It purely depend on whether extension-data has to be partially
passed across separately or not. Currently mechanism allows to pass
extension data partially within RS whereas in case it is an element
within any of the metadata block element like participant, stream then
it has to be passed across with any change in that particular metadata
block element.

In case everyone feels that there is no need to pass extensiondata
explicitly, it realy simply the solution as there is no need another
open item like parent id within extensiondata </partha>


Regards,
   Scott
 =20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Paul Kyzivat
Sent: Thursday, March 31, 2011 7:19 AM
To: Peter Saint-Andre
Cc: siprec@ietf.org
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01



On 3/31/2011 5:06 AM, Peter Saint-Andre wrote:
> I am booked through 11 PM tonight.
>
> Tomorrow I have the following windows of time:
>
> 07:00-07:30
> 15:15-16:00
>
> Naturally that time might get filled if issues come up in some of my=20
> working groups. :)

But you also have 11-12pm tonite? :-)
(That is much better for me than the others.)

Maybe its just too late in the week to hope for this.
We can take it to the list.

	Thanks,
	Paul

> On 3/31/11 10:55 AM, Paul Kyzivat wrote:
>> Peter/Joe,
>>
>> Do either of you have any time in the remainder of the week when some

>> of us could sit and try to sort out the right way to do the extension
data?
>> I doubt it would take very long.
>>
>>      Thanks,
>>      Paul
>>
>> On 3/30/2011 6:25 PM, Peter Saint-Andre wrote:
>>> Here is some quick feedback on draft-ram-siprec-metadata-format-01.=20
>>> I hope to review it more fully soon.
>>>
>>> 1. I would change application/recording to application/recording+xml

>>> in accordance with RFC 3023 (many specs illustrate the use of XML=20
>>> media types -- see for example RFC 4287).
>>>
>>> 2. The large number of<extensiondata/>   elements is a bit confusing
in
>>> the examples.
>>>
>>> 3. In Section 5.1, the example has one<extensiondata/>   element
>>> qualified by the 'urn:ietf:params:xml:ns:siprec' namespace (no other
>>> namespace is defined) and then multiple<extensiondata/>   elements
>>> qualified by other namespaces ('http://example.com/groupapp',=20
>>> 'http://example.com/sessionapp', etc.). Although those other=20
>>> namespaces are certainly *allowed* to use "extensiondata" as an=20
>>> element name (that's the beauty of namespaces), it is confusing in
this document.
>>> Perhaps you even meant to have<extensiondata/>   elements qualified
by
>>> the 'urn:ietf:params:xml:ns:siprec' and then child elements=20
>>> qualified by other namespaces (in accordance with the schema).=20
>>> However, that is not clear in the spec.
>>>
>>> 4. There is no built-in datatype for xs:urnuuid, xs:streamMode,=20
>>> xs:requester, and so on. See W3C XML Schema Part 2:
>>>
>>>      http://www.w3.org/TR/xmlschema-2/#built-in-datatypes
>>>
>>> 5. The data in the<name/>   elements with xml:lang=3D"it" really
should be
>>> Giulietta Capuleti and Romeo Montecchi. ;-)
>>>
>>> Peter
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From eckelcu@cisco.com  Thu Mar 31 09:08:54 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77F4928B797 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.576
X-Spam-Level: 
X-Spam-Status: No, score=-10.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W21vTjhGnaFK for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:08:53 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 495C03A6C11 for <siprec@ietf.org>; Thu, 31 Mar 2011 09:08:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=4827; q=dns/txt; s=iport; t=1301587833; x=1302797433; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=DmeFQ7pexqvcNfPbnSXFIKK869f4KuLY3vSNZ/rSF0A=; b=TAQMePMcvFKOIxgdgTIS9EXgYzk6xvJPWvWaMCqhYfqHrdOTrDRd0XcA NlMpHb+KWzXmMQ11uZ7uOw8m+TNZI520cjJNJ+KFoznIuEH4O9u+mf2RJ EMrPNPQryL9MghX6ktz2f3eqAZZ5Mo7lcM7B9uM5rU04mPp7NO9PikOo+ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgABADqnlE2rRDoI/2dsb2JhbACYEo1Ad4h5mkWcJ4VrBIVBiys
X-IronPort-AV: E=Sophos;i="4.63,276,1299456000"; d="scan'208";a="286650942"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 31 Mar 2011 16:10:32 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2VGAWHp017684; Thu, 31 Mar 2011 16:10:32 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 31 Mar 2011 09:10:32 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 31 Mar 2011 09:10:30 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E3902E@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875AF36FF@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhgBO/qTgAD5pH0AAJpm4YABBRncA
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com><A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com> <A444A0F8084434499206E78C106220CA0875AF36FF@MCHP058A.global-ad.net>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Parthasarathi R (partr)" <partr@cisco.com>, <siprec@ietf.org>
X-OriginalArrivalTime: 31 Mar 2011 16:10:32.0565 (UTC) FILETIME=[2948C250:01CBEFBE]
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 16:08:54 -0000

Hi John,

Please see inline.

> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Wednesday, March 30, 2011 11:01 AM
> To: Charles Eckel (eckelcu); Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
>=20
>=20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel
(eckelcu)
> > Sent: 29 March 2011 15:38
> > To: Parthasarathi R (partr); siprec@ietf.org
> > Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
> >
> > Hi Partha,
> >
> > Thanks for your response. This addresses all of my concerns.
> > Please see
> > one additional clarification inline.
> >
> > > -----Original Message-----
> > > From: Parthasarathi R (partr)
> > > Sent: Tuesday, March 29, 2011 10:31 AM
> > > To: Charles Eckel (eckelcu); siprec@ietf.org
> > > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> > >
> > > Charles,
> > >
> > > Thanks for review the document. Please read inline.
> > >
> > > Thanks
> > > Partha
> > >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of Charles Eckel (eckelcu)
> > > Sent: Sunday, March 27, 2011 12:35 AM
> > > To: siprec@ietf.org
> > > Subject: [siprec] comments on draft-ram-siprec-metadata-04
> > >
> > > I gave the draft and read and have the following comments.
> > >
> > > Section 3. Think the metadata describes the recording
> > session, not the
> > communication session. Replace
> > > "metamodel" with "metadata model", and "MAY be conveyed in
Recording
> > Session" with "MAY be conveyed
> > > within the Recording Session", and "time a change occurred by be
> > assumed" with "time a change occurred
> > > may be assumed".
> [JRE] I am not sure exactly what text Charles was commenting on, but
in my opinion metadata describes
> a CS (and how media streams in the RS relate to that CS), rather than
describing the RS.
>=20
> John (as individual)

The metadata model is anchored by an element for the RS. This recording
session contains 0 or more CS group each with 1 or more CS. This is what
led to my comment that the metadata model describes an RS rather than a
CS.

Cheers,
Charles

>=20
>=20
> > >
> > > Section 4, suggest rewording as, "The section describes each
element
> > of the metadata model, and the
> > > attributes of each element. This section also describes how the
> > different elements are associated."
> > >
> > > Section 4.1, RecordingRequestorID is not really an ID, it
> > is more of a
> > type. I think
> > > RecordingRequestor is more appropriate.
> > >
> > >
> > > <Partha>Agreed. We will update in the next revision </partha>
> > >
> > >  That said, I think you also need a unique ID for the Recording
> > Session, right?
> > > <partha>  Please clarify whether you are interested in AOR of RS
or
> > just ID. In the model, Recording
> > > (1..*) is related to CSG (0..*) and there is no need of separate
> > attribute for unique id. In the
> > > metadata format, URN UUID in CSG (group) & recording exist
> > which helps
> > to visualize the association
> > > </partha>
> >
> > I am assuming there is a need to distinguish one RS from
> > another RS, and
> > that is the reason I was recommending adding a unique ID.
> > This ID would
> > not be the RS AOR as that may not be unique.
> >
> > Cheers,
> > Charles
> >
> > > Section 4.2.1, replace "SRC (or MAY be SRS)" with "SRC or SRS".
> > > <Partha>Agreed. We will update in the next revision </partha>
> > >
> > > Section 4.3.2, why does a CS need two participants or more?
> > What about
> > studio mode recording?
> > >
> > > Section 4.4.1, what is participant type and what is its use, or
why
> > needed?
> > > <partha> This attribute has to be removed as per the last interim
> > meeting. We will update in the next
> > > revision. </partha>
> > >
> > > Section 4.5, I think Media Stream requires a unique ID attribute
as
> > well.
> > > <partha> As mentioned above in the model draft, the association
> > between CS and participant is shown.
> > > In terms of format draft, it is represented by URN UUID </partha>
> > > Is the "Media Stream Reference" the SDP label attribute?
> > > <partha> Your understanding is correct </partha>
> > >
> > >
> > > Thanks,
> > > Charles
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> >

From sorton@broadsoft.com  Thu Mar 31 09:23:04 2011
Return-Path: <sorton@broadsoft.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C80E43A69BF for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.123
X-Spam-Level: 
X-Spam-Status: No, score=0.123 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_210=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_29=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CSkGnoOjTqye for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:23:02 -0700 (PDT)
Received: from smtp-out01.seaservers.net (smtpedge.partnerhosted.com [173.225.22.21]) by core3.amsl.com (Postfix) with ESMTP id C179A3A6932 for <siprec@ietf.org>; Thu, 31 Mar 2011 09:23:02 -0700 (PDT)
Received: from EXMBXCLUS01.citservers.local ([fe80::a488:d1ec:a706:3a6d]) by CASUMHUB02.citservers.local ([::1]) with mapi; Thu, 31 Mar 2011 09:24:44 -0700
From: Scott Orton <sorton@broadsoft.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, Peter Saint-Andre <stpeter@stpeter.im>
Date: Thu, 31 Mar 2011 09:21:18 -0700
Thread-Topic: [siprec] draft-ram-siprec-metadata-format-01
Thread-Index: AcvvneGYaEpydjZiTmOKSohan6QgKQAGBOGgAADiJqAAAD+KEA==
Message-ID: <21866C7FE177A4449B9136B5B24B1B130BC01128FB@EXMBXCLUS01.citservers.local>
References: <4D93ADCB.2050106@stpeter.im> <4D94416E.7070102@cisco.com><4D944429.10607@stpeter.im> <4D94714B.8010102@cisco.com> <21866C7FE177A4449B9136B5B24B1B130BC01128BC@EXMBXCLUS01.citservers.local> <A11921905DA1564D9BCF64A6430A623904E979BB@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623904E979BB@XMB-BGL-411.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 16:23:04 -0000

Inline comments.

-----Original Message-----
From: Parthasarathi R (partr) [mailto:partr@cisco.com]=20
Sent: Thursday, March 31, 2011 10:42 AM
To: Scott Orton; Paul Kyzivat (pkyzivat); Peter Saint-Andre
Cc: siprec@ietf.org
Subject: RE: [siprec] draft-ram-siprec-metadata-format-01

Scott,

Thanks for the feedback.

Thanks
Partha

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Scott Orton
Sent: Thursday, March 31, 2011 8:59 PM
To: Paul Kyzivat (pkyzivat); Peter Saint-Andre
Cc: siprec@ietf.org
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01

Here is some feedback on draft-ram-siprec-metadata-format-01.=20

In the xml schema, the group is not listed as an element in the sequence
for the recording-metadata, which conflicts with the example in 5.1.

<Partha> Agreed. I'll update in the next revision </partha>

In addition, I found it confusing that the extension data is included in
the participant type but not included in any of the other defined
elements in the recording-metadata. I think it might be good idea to
include the extension data as last element in the sequences for the
group, session, etc. As that would eliminate the need for the parent
attribute in the extension data assuming it stays close to its current
format.

<partha> It purely depend on whether extension-data has to be partially
passed across separately or not. Currently mechanism allows to pass
extension data partially within RS whereas in case it is an element
within any of the metadata block element like participant, stream then
it has to be passed across with any change in that particular metadata
block element.


<Scott> I see the advantages of it being separate for the partial update. I=
 would just like it to be consistent. Either in each element or in none of =
the elements. I think the key to deciding where to include the extension da=
ta is how a partial update should treat the data. If for example in the ini=
tial metadata you send to the SRS there is extensiondata associated with th=
e participant. Then in an UPDATE the partial metadata for the participant u=
pdate the stop-time, but does not include the extensiondata. How is the SRS=
 expected to handle the lack of extensiondata? Should it treat it as the ex=
tensiondata is no longer relevant and delete it or should it assume it is n=
ot changed. If it should treat it as unchanged then how do you delete the e=
xtension data if it is no longer relevant. Since the definition of the exte=
nsion data requires at least one string there is no way to remove it. All t=
his leads me to believe that the extension data should be part of each elem=
ent and there should be no generic extensiondata element in the recording-m=
etadata.  </Scott>

In case everyone feels that there is no need to pass extensiondata
explicitly, it realy simply the solution as there is no need another
open item like parent id within extensiondata </partha>
=20

Regards,
   Scott
 =20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Paul Kyzivat
Sent: Thursday, March 31, 2011 7:19 AM
To: Peter Saint-Andre
Cc: siprec@ietf.org
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01



On 3/31/2011 5:06 AM, Peter Saint-Andre wrote:
> I am booked through 11 PM tonight.
>
> Tomorrow I have the following windows of time:
>
> 07:00-07:30
> 15:15-16:00
>
> Naturally that time might get filled if issues come up in some of my=20
> working groups. :)

But you also have 11-12pm tonite? :-)
(That is much better for me than the others.)

Maybe its just too late in the week to hope for this.
We can take it to the list.

	Thanks,
	Paul

> On 3/31/11 10:55 AM, Paul Kyzivat wrote:
>> Peter/Joe,
>>
>> Do either of you have any time in the remainder of the week when some

>> of us could sit and try to sort out the right way to do the extension
data?
>> I doubt it would take very long.
>>
>>      Thanks,
>>      Paul
>>
>> On 3/30/2011 6:25 PM, Peter Saint-Andre wrote:
>>> Here is some quick feedback on draft-ram-siprec-metadata-format-01.=20
>>> I hope to review it more fully soon.
>>>
>>> 1. I would change application/recording to application/recording+xml

>>> in accordance with RFC 3023 (many specs illustrate the use of XML=20
>>> media types -- see for example RFC 4287).
>>>
>>> 2. The large number of<extensiondata/>   elements is a bit confusing
in
>>> the examples.
>>>
>>> 3. In Section 5.1, the example has one<extensiondata/>   element
>>> qualified by the 'urn:ietf:params:xml:ns:siprec' namespace (no other
>>> namespace is defined) and then multiple<extensiondata/>   elements
>>> qualified by other namespaces ('http://example.com/groupapp',=20
>>> 'http://example.com/sessionapp', etc.). Although those other=20
>>> namespaces are certainly *allowed* to use "extensiondata" as an=20
>>> element name (that's the beauty of namespaces), it is confusing in
this document.
>>> Perhaps you even meant to have<extensiondata/>   elements qualified
by
>>> the 'urn:ietf:params:xml:ns:siprec' and then child elements=20
>>> qualified by other namespaces (in accordance with the schema).=20
>>> However, that is not clear in the spec.
>>>
>>> 4. There is no built-in datatype for xs:urnuuid, xs:streamMode,=20
>>> xs:requester, and so on. See W3C XML Schema Part 2:
>>>
>>>      http://www.w3.org/TR/xmlschema-2/#built-in-datatypes
>>>
>>> 5. The data in the<name/>   elements with xml:lang=3D"it" really
should be
>>> Giulietta Capuleti and Romeo Montecchi. ;-)
>>>
>>> Peter
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From john.elwell@siemens-enterprise.com  Thu Mar 31 09:28:06 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDB8A3A6B32 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H5tJOBh3NQeW for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:28:05 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id A2DFB3A6B24 for <siprec@ietf.org>; Thu, 31 Mar 2011 09:28:02 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3964643; Thu, 31 Mar 2011 18:29:41 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 3907E23F0290; Thu, 31 Mar 2011 18:29:41 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 31 Mar 2011 18:29:41 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 31 Mar 2011 18:29:39 +0200
Thread-Topic: [siprec] comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhgBO/qTgAD5pH0AAJpm4YABBRncAAAC5KqA=
Message-ID: <A444A0F8084434499206E78C106220CA0875D122FB@MCHP058A.global-ad.net>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com><A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com> <A444A0F8084434499206E78C106220CA0875AF36FF@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E3902E@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E3902E@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 16:28:07 -0000

Charles,

OK, I see how you got there, but really it describes the CSs (and CS groups=
) that are being carried in the RS. Any ideas how better to word it?

John=20

> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]=20
> Sent: 31 March 2011 17:11
> To: Elwell, John; Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> Hi John,
>=20
> Please see inline.
>=20
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Wednesday, March 30, 2011 11:01 AM
> > To: Charles Eckel (eckelcu); Parthasarathi R (partr);=20
> siprec@ietf.org
> > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel
> (eckelcu)
> > > Sent: 29 March 2011 15:38
> > > To: Parthasarathi R (partr); siprec@ietf.org
> > > Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
> > >
> > > Hi Partha,
> > >
> > > Thanks for your response. This addresses all of my concerns.
> > > Please see
> > > one additional clarification inline.
> > >
> > > > -----Original Message-----
> > > > From: Parthasarathi R (partr)
> > > > Sent: Tuesday, March 29, 2011 10:31 AM
> > > > To: Charles Eckel (eckelcu); siprec@ietf.org
> > > > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> > > >
> > > > Charles,
> > > >
> > > > Thanks for review the document. Please read inline.
> > > >
> > > > Thanks
> > > > Partha
> > > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Charles Eckel (eckelcu)
> > > > Sent: Sunday, March 27, 2011 12:35 AM
> > > > To: siprec@ietf.org
> > > > Subject: [siprec] comments on draft-ram-siprec-metadata-04
> > > >
> > > > I gave the draft and read and have the following comments.
> > > >
> > > > Section 3. Think the metadata describes the recording
> > > session, not the
> > > communication session. Replace
> > > > "metamodel" with "metadata model", and "MAY be conveyed in
> Recording
> > > Session" with "MAY be conveyed
> > > > within the Recording Session", and "time a change occurred by be
> > > assumed" with "time a change occurred
> > > > may be assumed".
> > [JRE] I am not sure exactly what text Charles was commenting on, but
> in my opinion metadata describes
> > a CS (and how media streams in the RS relate to that CS),=20
> rather than
> describing the RS.
> >=20
> > John (as individual)
>=20
> The metadata model is anchored by an element for the RS. This=20
> recording
> session contains 0 or more CS group each with 1 or more CS.=20
> This is what
> led to my comment that the metadata model describes an RS=20
> rather than a
> CS.
>=20
> Cheers,
> Charles
>=20
> >=20
> >=20
> > > >
> > > > Section 4, suggest rewording as, "The section describes each
> element
> > > of the metadata model, and the
> > > > attributes of each element. This section also describes how the
> > > different elements are associated."
> > > >
> > > > Section 4.1, RecordingRequestorID is not really an ID, it
> > > is more of a
> > > type. I think
> > > > RecordingRequestor is more appropriate.
> > > >
> > > >
> > > > <Partha>Agreed. We will update in the next revision </partha>
> > > >
> > > >  That said, I think you also need a unique ID for the Recording
> > > Session, right?
> > > > <partha>  Please clarify whether you are interested in AOR of RS
> or
> > > just ID. In the model, Recording
> > > > (1..*) is related to CSG (0..*) and there is no need of separate
> > > attribute for unique id. In the
> > > > metadata format, URN UUID in CSG (group) & recording exist
> > > which helps
> > > to visualize the association
> > > > </partha>
> > >
> > > I am assuming there is a need to distinguish one RS from
> > > another RS, and
> > > that is the reason I was recommending adding a unique ID.
> > > This ID would
> > > not be the RS AOR as that may not be unique.
> > >
> > > Cheers,
> > > Charles
> > >
> > > > Section 4.2.1, replace "SRC (or MAY be SRS)" with "SRC or SRS".
> > > > <Partha>Agreed. We will update in the next revision </partha>
> > > >
> > > > Section 4.3.2, why does a CS need two participants or more?
> > > What about
> > > studio mode recording?
> > > >
> > > > Section 4.4.1, what is participant type and what is its use, or
> why
> > > needed?
> > > > <partha> This attribute has to be removed as per the=20
> last interim
> > > meeting. We will update in the next
> > > > revision. </partha>
> > > >
> > > > Section 4.5, I think Media Stream requires a unique ID attribute
> as
> > > well.
> > > > <partha> As mentioned above in the model draft, the association
> > > between CS and participant is shown.
> > > > In terms of format draft, it is represented by URN UUID=20
> </partha>
> > > > Is the "Media Stream Reference" the SDP label attribute?
> > > > <partha> Your understanding is correct </partha>
> > > >
> > > >
> > > > Thanks,
> > > > Charles
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> =

From sorton@broadsoft.com  Thu Mar 31 09:44:59 2011
Return-Path: <sorton@broadsoft.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DDB33A699E for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ue2e+NlnZ1Y0 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:44:58 -0700 (PDT)
Received: from smtp-out01.seaservers.net (smtpedge.partnerhosted.com [173.225.22.21]) by core3.amsl.com (Postfix) with ESMTP id 61A5B3A6930 for <siprec@ietf.org>; Thu, 31 Mar 2011 09:44:58 -0700 (PDT)
Received: from EXMBXCLUS01.citservers.local ([fe80:0000:0000:0000:a488:d1ec:167.6.58.109]) by casumhub01.citservers.local ([172.16.98.57]) with mapi; Thu, 31 Mar 2011 09:46:37 -0700
From: Scott Orton <sorton@broadsoft.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Parthasarathi R (partr)" <partr@cisco.com>,  "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 31 Mar 2011 09:43:15 -0700
Thread-Topic: [siprec] comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhgBO/qTgAD5pH0AAJpm4YABBRncAAAC5KqAAABl2UA==
Message-ID: <21866C7FE177A4449B9136B5B24B1B130BC011290A@EXMBXCLUS01.citservers.local>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com><A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com> <A444A0F8084434499206E78C106220CA0875AF36FF@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E3902E@xmb-sjc-234.amer.cisco.com> <A444A0F8084434499206E78C106220CA0875D122FB@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875D122FB@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 16:44:59 -0000

John, Charles, Partha,
   I have a question. What is the purpose of the CS Group? I do not see it =
adding anything to the metadata. To me it seems that the whole purpose of t=
he metadata is to describe the recording session to the SRS. Looking at the=
 requirements I see 3 relationships that the spec is attempting to describe=
:=20

A one to one relationship - one communication session to one recording sess=
ion
A one to many relationship - one communication session with multiple Record=
ing sessions
                           - one Recording session made up of multiple comm=
unications sessions

The current metadata format allows all of these and I do not see what the g=
roup is adding.

Regards,
    Scott

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Elwell, John
Sent: Thursday, March 31, 2011 11:30 AM
To: Charles Eckel (eckelcu); Parthasarathi R (partr); siprec@ietf.org
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04

Charles,

OK, I see how you got there, but really it describes the CSs (and CS groups=
) that are being carried in the RS. Any ideas how better to word it?

John=20

> -----Original Message-----
> From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]=20
> Sent: 31 March 2011 17:11
> To: Elwell, John; Parthasarathi R (partr); siprec@ietf.org
> Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> Hi John,
>=20
> Please see inline.
>=20
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > Sent: Wednesday, March 30, 2011 11:01 AM
> > To: Charles Eckel (eckelcu); Parthasarathi R (partr);=20
> siprec@ietf.org
> > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel
> (eckelcu)
> > > Sent: 29 March 2011 15:38
> > > To: Parthasarathi R (partr); siprec@ietf.org
> > > Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
> > >
> > > Hi Partha,
> > >
> > > Thanks for your response. This addresses all of my concerns.
> > > Please see
> > > one additional clarification inline.
> > >
> > > > -----Original Message-----
> > > > From: Parthasarathi R (partr)
> > > > Sent: Tuesday, March 29, 2011 10:31 AM
> > > > To: Charles Eckel (eckelcu); siprec@ietf.org
> > > > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> > > >
> > > > Charles,
> > > >
> > > > Thanks for review the document. Please read inline.
> > > >
> > > > Thanks
> > > > Partha
> > > >
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of Charles Eckel (eckelcu)
> > > > Sent: Sunday, March 27, 2011 12:35 AM
> > > > To: siprec@ietf.org
> > > > Subject: [siprec] comments on draft-ram-siprec-metadata-04
> > > >
> > > > I gave the draft and read and have the following comments.
> > > >
> > > > Section 3. Think the metadata describes the recording
> > > session, not the
> > > communication session. Replace
> > > > "metamodel" with "metadata model", and "MAY be conveyed in
> Recording
> > > Session" with "MAY be conveyed
> > > > within the Recording Session", and "time a change occurred by be
> > > assumed" with "time a change occurred
> > > > may be assumed".
> > [JRE] I am not sure exactly what text Charles was commenting on, but
> in my opinion metadata describes
> > a CS (and how media streams in the RS relate to that CS),=20
> rather than
> describing the RS.
> >=20
> > John (as individual)
>=20
> The metadata model is anchored by an element for the RS. This=20
> recording
> session contains 0 or more CS group each with 1 or more CS.=20
> This is what
> led to my comment that the metadata model describes an RS=20
> rather than a
> CS.
>=20
> Cheers,
> Charles
>=20
> >=20
> >=20
> > > >
> > > > Section 4, suggest rewording as, "The section describes each
> element
> > > of the metadata model, and the
> > > > attributes of each element. This section also describes how the
> > > different elements are associated."
> > > >
> > > > Section 4.1, RecordingRequestorID is not really an ID, it
> > > is more of a
> > > type. I think
> > > > RecordingRequestor is more appropriate.
> > > >
> > > >
> > > > <Partha>Agreed. We will update in the next revision </partha>
> > > >
> > > >  That said, I think you also need a unique ID for the Recording
> > > Session, right?
> > > > <partha>  Please clarify whether you are interested in AOR of RS
> or
> > > just ID. In the model, Recording
> > > > (1..*) is related to CSG (0..*) and there is no need of separate
> > > attribute for unique id. In the
> > > > metadata format, URN UUID in CSG (group) & recording exist
> > > which helps
> > > to visualize the association
> > > > </partha>
> > >
> > > I am assuming there is a need to distinguish one RS from
> > > another RS, and
> > > that is the reason I was recommending adding a unique ID.
> > > This ID would
> > > not be the RS AOR as that may not be unique.
> > >
> > > Cheers,
> > > Charles
> > >
> > > > Section 4.2.1, replace "SRC (or MAY be SRS)" with "SRC or SRS".
> > > > <Partha>Agreed. We will update in the next revision </partha>
> > > >
> > > > Section 4.3.2, why does a CS need two participants or more?
> > > What about
> > > studio mode recording?
> > > >
> > > > Section 4.4.1, what is participant type and what is its use, or
> why
> > > needed?
> > > > <partha> This attribute has to be removed as per the=20
> last interim
> > > meeting. We will update in the next
> > > > revision. </partha>
> > > >
> > > > Section 4.5, I think Media Stream requires a unique ID attribute
> as
> > > well.
> > > > <partha> As mentioned above in the model draft, the association
> > > between CS and participant is shown.
> > > > In terms of format draft, it is represented by URN UUID=20
> </partha>
> > > > Is the "Media Stream Reference" the SDP label attribute?
> > > > <partha> Your understanding is correct </partha>
> > > >
> > > >
> > > > Thanks,
> > > > Charles
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
> > >
>=20
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From john.elwell@siemens-enterprise.com  Thu Mar 31 09:48:24 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E247D3A699E for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n2eu+Wb7+QlC for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 09:48:23 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id A5D5A3A6930 for <siprec@ietf.org>; Thu, 31 Mar 2011 09:48:22 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3971318; Thu, 31 Mar 2011 18:50:01 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 8EBA823F028E; Thu, 31 Mar 2011 18:50:01 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 31 Mar 2011 18:50:01 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Scott Orton <sorton@broadsoft.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 31 Mar 2011 18:49:59 +0200
Thread-Topic: [siprec] comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhgBO/qTgAD5pH0AAJpm4YABBRncAAAC5KqAAABl2UAAAlZ6w
Message-ID: <A444A0F8084434499206E78C106220CA0875D12311@MCHP058A.global-ad.net>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com><A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com> <A444A0F8084434499206E78C106220CA0875AF36FF@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E3902E@xmb-sjc-234.amer.cisco.com> <A444A0F8084434499206E78C106220CA0875D122FB@MCHP058A.global-ad.net> <21866C7FE177A4449B9136B5B24B1B130BC011290A@EXMBXCLUS01.citservers.local>
In-Reply-To: <21866C7FE177A4449B9136B5B24B1B130BC011290A@EXMBXCLUS01.citservers.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 16:48:25 -0000

Scott,

Some folks wanted to be able to group related CSs together (e.g., a CS betw=
een a customer and an agent and a second CS resulting from the customer bei=
ng transferred to a second agent). I will leave it to those folks to add to=
 this.

John (chair hat on)
=20

> -----Original Message-----
> From: Scott Orton [mailto:sorton@broadsoft.com]=20
> Sent: 31 March 2011 17:43
> To: Elwell, John; Charles Eckel (eckelcu); Parthasarathi R=20
> (partr); siprec@ietf.org
> Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> John, Charles, Partha,
>    I have a question. What is the purpose of the CS Group? I=20
> do not see it adding anything to the metadata. To me it seems=20
> that the whole purpose of the metadata is to describe the=20
> recording session to the SRS. Looking at the requirements I=20
> see 3 relationships that the spec is attempting to describe:=20
>=20
> A one to one relationship - one communication session to one=20
> recording session
> A one to many relationship - one communication session with=20
> multiple Recording sessions
>                            - one Recording session made up of=20
> multiple communications sessions
>=20
> The current metadata format allows all of these and I do not=20
> see what the group is adding.
>=20
> Regards,
>     Scott
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> Sent: Thursday, March 31, 2011 11:30 AM
> To: Charles Eckel (eckelcu); Parthasarathi R (partr); siprec@ietf.org
> Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> Charles,
>=20
> OK, I see how you got there, but really it describes the CSs=20
> (and CS groups) that are being carried in the RS. Any ideas=20
> how better to word it?
>=20
> John=20
>=20
> > -----Original Message-----
> > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]=20
> > Sent: 31 March 2011 17:11
> > To: Elwell, John; Parthasarathi R (partr); siprec@ietf.org
> > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> >=20
> > Hi John,
> >=20
> > Please see inline.
> >=20
> > > -----Original Message-----
> > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > Sent: Wednesday, March 30, 2011 11:01 AM
> > > To: Charles Eckel (eckelcu); Parthasarathi R (partr);=20
> > siprec@ietf.org
> > > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> > >=20
> > >=20
> > >=20
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel
> > (eckelcu)
> > > > Sent: 29 March 2011 15:38
> > > > To: Parthasarathi R (partr); siprec@ietf.org
> > > > Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
> > > >
> > > > Hi Partha,
> > > >
> > > > Thanks for your response. This addresses all of my concerns.
> > > > Please see
> > > > one additional clarification inline.
> > > >
> > > > > -----Original Message-----
> > > > > From: Parthasarathi R (partr)
> > > > > Sent: Tuesday, March 29, 2011 10:31 AM
> > > > > To: Charles Eckel (eckelcu); siprec@ietf.org
> > > > > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> > > > >
> > > > > Charles,
> > > > >
> > > > > Thanks for review the document. Please read inline.
> > > > >
> > > > > Thanks
> > > > > Partha
> > > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org=20
> > [mailto:siprec-bounces@ietf.org] On
> > > > Behalf Of Charles Eckel (eckelcu)
> > > > > Sent: Sunday, March 27, 2011 12:35 AM
> > > > > To: siprec@ietf.org
> > > > > Subject: [siprec] comments on draft-ram-siprec-metadata-04
> > > > >
> > > > > I gave the draft and read and have the following comments.
> > > > >
> > > > > Section 3. Think the metadata describes the recording
> > > > session, not the
> > > > communication session. Replace
> > > > > "metamodel" with "metadata model", and "MAY be conveyed in
> > Recording
> > > > Session" with "MAY be conveyed
> > > > > within the Recording Session", and "time a change=20
> occurred by be
> > > > assumed" with "time a change occurred
> > > > > may be assumed".
> > > [JRE] I am not sure exactly what text Charles was=20
> commenting on, but
> > in my opinion metadata describes
> > > a CS (and how media streams in the RS relate to that CS),=20
> > rather than
> > describing the RS.
> > >=20
> > > John (as individual)
> >=20
> > The metadata model is anchored by an element for the RS. This=20
> > recording
> > session contains 0 or more CS group each with 1 or more CS.=20
> > This is what
> > led to my comment that the metadata model describes an RS=20
> > rather than a
> > CS.
> >=20
> > Cheers,
> > Charles
> >=20
> > >=20
> > >=20
> > > > >
> > > > > Section 4, suggest rewording as, "The section describes each
> > element
> > > > of the metadata model, and the
> > > > > attributes of each element. This section also=20
> describes how the
> > > > different elements are associated."
> > > > >
> > > > > Section 4.1, RecordingRequestorID is not really an ID, it
> > > > is more of a
> > > > type. I think
> > > > > RecordingRequestor is more appropriate.
> > > > >
> > > > >
> > > > > <Partha>Agreed. We will update in the next revision </partha>
> > > > >
> > > > >  That said, I think you also need a unique ID for the=20
> Recording
> > > > Session, right?
> > > > > <partha>  Please clarify whether you are interested=20
> in AOR of RS
> > or
> > > > just ID. In the model, Recording
> > > > > (1..*) is related to CSG (0..*) and there is no need=20
> of separate
> > > > attribute for unique id. In the
> > > > > metadata format, URN UUID in CSG (group) & recording exist
> > > > which helps
> > > > to visualize the association
> > > > > </partha>
> > > >
> > > > I am assuming there is a need to distinguish one RS from
> > > > another RS, and
> > > > that is the reason I was recommending adding a unique ID.
> > > > This ID would
> > > > not be the RS AOR as that may not be unique.
> > > >
> > > > Cheers,
> > > > Charles
> > > >
> > > > > Section 4.2.1, replace "SRC (or MAY be SRS)" with=20
> "SRC or SRS".
> > > > > <Partha>Agreed. We will update in the next revision </partha>
> > > > >
> > > > > Section 4.3.2, why does a CS need two participants or more?
> > > > What about
> > > > studio mode recording?
> > > > >
> > > > > Section 4.4.1, what is participant type and what is=20
> its use, or
> > why
> > > > needed?
> > > > > <partha> This attribute has to be removed as per the=20
> > last interim
> > > > meeting. We will update in the next
> > > > > revision. </partha>
> > > > >
> > > > > Section 4.5, I think Media Stream requires a unique=20
> ID attribute
> > as
> > > > well.
> > > > > <partha> As mentioned above in the model draft, the=20
> association
> > > > between CS and participant is shown.
> > > > > In terms of format draft, it is represented by URN UUID=20
> > </partha>
> > > > > Is the "Media Stream Reference" the SDP label attribute?
> > > > > <partha> Your understanding is correct </partha>
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Charles
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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
> > > >
> >=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From sorton@broadsoft.com  Thu Mar 31 11:49:44 2011
Return-Path: <sorton@broadsoft.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6E213A6B7C for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 11:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xf1SEz-ZRKOp for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 11:49:43 -0700 (PDT)
Received: from smtp-out01.seaservers.net (smtpedge.partnerhosted.com [173.225.22.21]) by core3.amsl.com (Postfix) with ESMTP id A588F3A6A7C for <siprec@ietf.org>; Thu, 31 Mar 2011 11:49:43 -0700 (PDT)
Received: from EXMBXCLUS01.citservers.local ([fe80:0000:0000:0000:a488:d1ec:167.6.58.109]) by casumhub01.citservers.local ([172.16.98.57]) with mapi; Thu, 31 Mar 2011 11:51:23 -0700
From: Scott Orton <sorton@broadsoft.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Parthasarathi R (partr)" <partr@cisco.com>,  "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 31 Mar 2011 11:47:59 -0700
Thread-Topic: [siprec] comments on draft-ram-siprec-metadata-04
Thread-Index: Acvr6KoPYFMcjPlASk+pOtN532GUhgBO/qTgAD5pH0AAJpm4YABBRncAAAC5KqAAABl2UAAAlZ6wAAOH8AA=
Message-ID: <21866C7FE177A4449B9136B5B24B1B130BC011294A@EXMBXCLUS01.citservers.local>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03D86EA9@xmb-sjc-234.amer.cisco.com><A11921905DA1564D9BCF64A6430A623904DA2395@XMB-BGL-411.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E386E1@xmb-sjc-234.amer.cisco.com> <A444A0F8084434499206E78C106220CA0875AF36FF@MCHP058A.global-ad.net> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03E3902E@xmb-sjc-234.amer.cisco.com> <A444A0F8084434499206E78C106220CA0875D122FB@MCHP058A.global-ad.net> <21866C7FE177A4449B9136B5B24B1B130BC011290A@EXMBXCLUS01.citservers.local> <A444A0F8084434499206E78C106220CA0875D12311@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875D12311@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 18:49:44 -0000

John,
    Thanks for the information.

   In that case I would like to see the CS group be made optional. Rather t=
han the CS pointing to the CS Group, I would like to suggest that the CS po=
int to the RS and have the CS group stand alone where it would just have it=
s own ID and then a list of CS ids that belong to the group.

Scott

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Thursday, March 31, 2011 11:50 AM
To: Scott Orton; Charles Eckel (eckelcu); Parthasarathi R (partr); siprec@i=
etf.org
Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04

Scott,

Some folks wanted to be able to group related CSs together (e.g., a CS betw=
een a customer and an agent and a second CS resulting from the customer bei=
ng transferred to a second agent). I will leave it to those folks to add to=
 this.

John (chair hat on)
=20

> -----Original Message-----
> From: Scott Orton [mailto:sorton@broadsoft.com]=20
> Sent: 31 March 2011 17:43
> To: Elwell, John; Charles Eckel (eckelcu); Parthasarathi R=20
> (partr); siprec@ietf.org
> Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> John, Charles, Partha,
>    I have a question. What is the purpose of the CS Group? I=20
> do not see it adding anything to the metadata. To me it seems=20
> that the whole purpose of the metadata is to describe the=20
> recording session to the SRS. Looking at the requirements I=20
> see 3 relationships that the spec is attempting to describe:=20
>=20
> A one to one relationship - one communication session to one=20
> recording session
> A one to many relationship - one communication session with=20
> multiple Recording sessions
>                            - one Recording session made up of=20
> multiple communications sessions
>=20
> The current metadata format allows all of these and I do not=20
> see what the group is adding.
>=20
> Regards,
>     Scott
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> Sent: Thursday, March 31, 2011 11:30 AM
> To: Charles Eckel (eckelcu); Parthasarathi R (partr); siprec@ietf.org
> Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
>=20
> Charles,
>=20
> OK, I see how you got there, but really it describes the CSs=20
> (and CS groups) that are being carried in the RS. Any ideas=20
> how better to word it?
>=20
> John=20
>=20
> > -----Original Message-----
> > From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]=20
> > Sent: 31 March 2011 17:11
> > To: Elwell, John; Parthasarathi R (partr); siprec@ietf.org
> > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> >=20
> > Hi John,
> >=20
> > Please see inline.
> >=20
> > > -----Original Message-----
> > > From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > > Sent: Wednesday, March 30, 2011 11:01 AM
> > > To: Charles Eckel (eckelcu); Parthasarathi R (partr);=20
> > siprec@ietf.org
> > > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> > >=20
> > >=20
> > >=20
> > > > -----Original Message-----
> > > > From: siprec-bounces@ietf.org
> > > > [mailto:siprec-bounces@ietf.org] On Behalf Of Charles Eckel
> > (eckelcu)
> > > > Sent: 29 March 2011 15:38
> > > > To: Parthasarathi R (partr); siprec@ietf.org
> > > > Subject: Re: [siprec] comments on draft-ram-siprec-metadata-04
> > > >
> > > > Hi Partha,
> > > >
> > > > Thanks for your response. This addresses all of my concerns.
> > > > Please see
> > > > one additional clarification inline.
> > > >
> > > > > -----Original Message-----
> > > > > From: Parthasarathi R (partr)
> > > > > Sent: Tuesday, March 29, 2011 10:31 AM
> > > > > To: Charles Eckel (eckelcu); siprec@ietf.org
> > > > > Subject: RE: [siprec] comments on draft-ram-siprec-metadata-04
> > > > >
> > > > > Charles,
> > > > >
> > > > > Thanks for review the document. Please read inline.
> > > > >
> > > > > Thanks
> > > > > Partha
> > > > >
> > > > > -----Original Message-----
> > > > > From: siprec-bounces@ietf.org=20
> > [mailto:siprec-bounces@ietf.org] On
> > > > Behalf Of Charles Eckel (eckelcu)
> > > > > Sent: Sunday, March 27, 2011 12:35 AM
> > > > > To: siprec@ietf.org
> > > > > Subject: [siprec] comments on draft-ram-siprec-metadata-04
> > > > >
> > > > > I gave the draft and read and have the following comments.
> > > > >
> > > > > Section 3. Think the metadata describes the recording
> > > > session, not the
> > > > communication session. Replace
> > > > > "metamodel" with "metadata model", and "MAY be conveyed in
> > Recording
> > > > Session" with "MAY be conveyed
> > > > > within the Recording Session", and "time a change=20
> occurred by be
> > > > assumed" with "time a change occurred
> > > > > may be assumed".
> > > [JRE] I am not sure exactly what text Charles was=20
> commenting on, but
> > in my opinion metadata describes
> > > a CS (and how media streams in the RS relate to that CS),=20
> > rather than
> > describing the RS.
> > >=20
> > > John (as individual)
> >=20
> > The metadata model is anchored by an element for the RS. This=20
> > recording
> > session contains 0 or more CS group each with 1 or more CS.=20
> > This is what
> > led to my comment that the metadata model describes an RS=20
> > rather than a
> > CS.
> >=20
> > Cheers,
> > Charles
> >=20
> > >=20
> > >=20
> > > > >
> > > > > Section 4, suggest rewording as, "The section describes each
> > element
> > > > of the metadata model, and the
> > > > > attributes of each element. This section also=20
> describes how the
> > > > different elements are associated."
> > > > >
> > > > > Section 4.1, RecordingRequestorID is not really an ID, it
> > > > is more of a
> > > > type. I think
> > > > > RecordingRequestor is more appropriate.
> > > > >
> > > > >
> > > > > <Partha>Agreed. We will update in the next revision </partha>
> > > > >
> > > > >  That said, I think you also need a unique ID for the=20
> Recording
> > > > Session, right?
> > > > > <partha>  Please clarify whether you are interested=20
> in AOR of RS
> > or
> > > > just ID. In the model, Recording
> > > > > (1..*) is related to CSG (0..*) and there is no need=20
> of separate
> > > > attribute for unique id. In the
> > > > > metadata format, URN UUID in CSG (group) & recording exist
> > > > which helps
> > > > to visualize the association
> > > > > </partha>
> > > >
> > > > I am assuming there is a need to distinguish one RS from
> > > > another RS, and
> > > > that is the reason I was recommending adding a unique ID.
> > > > This ID would
> > > > not be the RS AOR as that may not be unique.
> > > >
> > > > Cheers,
> > > > Charles
> > > >
> > > > > Section 4.2.1, replace "SRC (or MAY be SRS)" with=20
> "SRC or SRS".
> > > > > <Partha>Agreed. We will update in the next revision </partha>
> > > > >
> > > > > Section 4.3.2, why does a CS need two participants or more?
> > > > What about
> > > > studio mode recording?
> > > > >
> > > > > Section 4.4.1, what is participant type and what is=20
> its use, or
> > why
> > > > needed?
> > > > > <partha> This attribute has to be removed as per the=20
> > last interim
> > > > meeting. We will update in the next
> > > > > revision. </partha>
> > > > >
> > > > > Section 4.5, I think Media Stream requires a unique=20
> ID attribute
> > as
> > > > well.
> > > > > <partha> As mentioned above in the model draft, the=20
> association
> > > > between CS and participant is shown.
> > > > > In terms of format draft, it is represented by URN UUID=20
> > </partha>
> > > > > Is the "Media Stream Reference" the SDP label attribute?
> > > > > <partha> Your understanding is correct </partha>
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Charles
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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
> > > >
> >=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20

From spromano@unina.it  Thu Mar 31 12:28:52 2011
Return-Path: <spromano@unina.it>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B34DB3A6B96 for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 12:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.533
X-Spam-Level: 
X-Spam-Status: No, score=-100.533 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H6wMwOqhPDIT for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 12:28:49 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id DC0FE3A6B99 for <siprec@ietf.org>; Thu, 31 Mar 2011 12:28:48 -0700 (PDT)
Received: from [130.129.23.172] (dhcp-17ac.meeting.ietf.org [130.129.23.172]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id p2VJUQZk029659 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 31 Mar 2011 21:30:27 +0200
Message-ID: <4D94D644.3060205@unina.it>
Date: Thu, 31 Mar 2011 21:30:12 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; it; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: "siprec@ietf.org" <siprec@ietf.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "info@meetecho.com" <info@meetecho.com>
Subject: [siprec] SIPREC session recondings
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Mar 2011 19:28:53 -0000

Dear all,

the full recordings (synchronized video, audio, slides and jabber room)
of today's SIPREC session is available at the following URL:

http://ietf.conf.meetecho.com

Since the session was quite long (and the associated files quite big...) we split it in two parts. Both of them are on the mentioned site.

Please be advised that the application we use to playout the recordings is a standard JNLP java app. JNLP is just a simple way to get Java applications
started from the network, taking care of library dependencies and the like automatically. We reassure you that the only thing the application does
is retrieve the SMIL description file, i.e. a standard way to describe a synchronized view of all the involved media, and in turn download the media
content itself. After that, the playout starts allowing you to seek.

An ad-hoc player was needed since our approach towards the SMIL description at the moment slightly differs from the standard in a few parts: a 100%
SMIL compliant representation of the recordings is about to come.

In case of problems with the playout, just drop an e-mail to
ietf-support@meetecho.com.

Cheers,

Simon

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From HKaplan@acmepacket.com  Thu Mar 31 17:41:07 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4EBF3A6B5C for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 17:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.839
X-Spam-Level: 
X-Spam-Status: No, score=-1.839 tagged_above=-999 required=5 tests=[AWL=0.760,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IL2Cp--jNj2S for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 17:41:07 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 11ADB3A6B2D for <siprec@ietf.org>; Thu, 31 Mar 2011 17:41:06 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 31 Mar 2011 20:42:45 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Thu, 31 Mar 2011 20:42:45 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Thu, 31 Mar 2011 20:42:42 -0400
Thread-Topic: extensionData in XML
Thread-Index: AcvwBbcMs0/nMvprR/2jlIqM3jVdpA==
Message-ID: <BA74ED8D-88B4-4DD6-9FFB-0D51B16F9871@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAgAAAUAAAAFT
Subject: [siprec] extensionData in XML
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 01 Apr 2011 00:41:07 -0000

Howdy,
With regards to the extensionData concept and XML, I have a few basic quest=
ions.  I am by no means an XML expert so it could just be my lack of knowle=
dge which makes me confused.  If so, just tell me to RTFM.

draft-ram-siprec-metadata-04 says in section 4.6:
   A recording metadata object contains additional data not specified as
   part of siprec.  This is intended to accommodate future standards
   track extensions, as well as vendor and user specific extensions.
   The mechanism MUST provide a means of unambiguously distinguishing
   such extension data.

What confuses me is I didn't think XML had to do such machinations to accom=
modate this need.  I thought we could just specify in our RFCs that unknown=
 XML elements and attributes MUST be ignored, so that future RFCs could add=
 them without having to leave specific "blob" XML elements to carry such da=
ta.  Or at least that's what we've done so far in SIP RFCs with XML bodies,=
 afaik.  I also thought XML had a namespace model that could be used to dis=
ambiguate proprietary elements from standard ones.  If both of those theori=
es are correct, why do we need to define an extensionData element?=20

-hadriel

