
From nobody Fri Mar  7 04:47:55 2014
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE3F01A013F for <siprec@ietfa.amsl.com>; Fri,  7 Mar 2014 04:47:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.448
X-Spam-Level: 
X-Spam-Status: No, score=-9.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vh9iqrilKMFh for <siprec@ietfa.amsl.com>; Fri,  7 Mar 2014 04:47:52 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 4FCF91A0116 for <siprec@ietf.org>; Fri,  7 Mar 2014 04:47:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1158; q=dns/txt; s=iport; t=1394196468; x=1395406068; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=W5hdlfw5NnwCR/N6nl4V4Af/uLPfZBvk/yOqpWZ1rCI=; b=kU7J65milhwRjo55UKfXuOIwMHtUrhBIQG/xDJsf8GFB6FAcfBeQUBIH uhDw+A065KWqOGPMr0YGTj4edlgaAf+MURT5vm07cW8sxb5ueGbTDsF3J CdsXWb67hKxkM0yyWmsOLHV714Nt6lgy5kUZGRUsZRIjdldN4IEeHCoeK k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAJC/GVOtJV2Y/2dsb2JhbABagwaBEsI5FnSCLDouDxQBPkInBIgMnzOwNxeTGgSYQ5Irgy2CKw
X-IronPort-AV: E=Sophos;i="4.97,607,1389744000"; d="scan'208";a="25685839"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-4.cisco.com with ESMTP; 07 Mar 2014 12:47:46 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s27ClkeY019382 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <siprec@ietf.org>; Fri, 7 Mar 2014 12:47:46 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.8]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Fri, 7 Mar 2014 06:47:45 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: SRC notification of recording to participants in CS
Thread-Index: AQHPOgNvyaHKIQ18vEuUzh1Ll+/FwQ==
Date: Fri, 7 Mar 2014 12:47:44 +0000
Message-ID: <CF3F7073.2238D%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.21.73.32]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <45F46ED04210874594B52FA395C4D778@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/l2U7_Xi5ee_zZMWQgJSwdFHzzyY
Subject: [siprec] SRC notification of recording to participants in CS
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 07 Mar 2014 12:47:54 -0000

Section 5.3 currently reads as follows:

The SRC is responsible to provide recording indications to the
   participants in the CS.


Section 6.1.2 elaborates on this:

For the communication session, the SRC MUST provide recording
   indication to all participants in the CS.  A participant UA in a CS
   can indicate that it is recording-aware by providing the "record-
   aware" option tag, and the SRC MUST provide recording indications in
   the new SDP a=3Drecord attribute described in the SDP Handling section.
   In the absence of the "record-aware" option tag, meaning that the
   participant UA is not recording-aware, an SRC MUST provide recording
   indications through other means such as playing a tone inband, if the
   SRC is required to do so (e.g. based on policies).


And 7.3.1 discussed this in the context of a conference:

When a CS is traversed through multiple UAs such as a B2BUA or a
   conference focus, each UA involved in the CS that is aware that the
   CS is being recorded MUST provide the recording indication through
   the a=3Drecord attribute to all other parties in the CS.


Cheers,
Charles




From nobody Mon Mar 10 17:33:32 2014
Return-Path: <partha@parthasarathi.co.in>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA1371A0672 for <siprec@ietfa.amsl.com>; Mon, 10 Mar 2014 17:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.699
X-Spam-Level: 
X-Spam-Status: No, score=0.699 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8CdLNW79yxW for <siprec@ietfa.amsl.com>; Mon, 10 Mar 2014 17:33:28 -0700 (PDT)
Received: from outbound.mailhostbox.com (smtp.mailhostbox.com [162.222.225.58]) by ietfa.amsl.com (Postfix) with ESMTP id E9FA41A0670 for <siprec@ietf.org>; Mon, 10 Mar 2014 17:33:27 -0700 (PDT)
Received: from userPC (unknown [122.167.111.4]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id 1126B14D8B0A; Tue, 11 Mar 2014 00:33:19 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1394498002; bh=Xpg69WSI1YICcob4HtLLURi3G78CqNVxR1+ZhCfBUy0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=CmSsKGnTBGbrs5VUx8QK4GzgXipLVIEvY2Tl/cNB6j2l1nejBy/xlVaAWLjiIE1a2 dGBg6jUWXmkJ/BZm4lJXs/5fY/xgcieLEmn+MWjgWsLtDFAXywljSryVAAavK0NG9z m3kFZFEgzi7T9vMy1t7t9a4aVD6lpx7BmiJtqBa8=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: <Gerben.Stam@nice.com>
Date: Tue, 11 Mar 2014 06:03:03 +0530
Message-ID: <001c01cf3cc1$7b0ce0f0$7126a2d0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac88wXMMO1NuT/MET1OLER8Y8eq5RA==
Content-Language: en-us
x-cr-hashedpuzzle: E55H FQJA F+YW Hfa8 H7Tb IJur KJRX M+dF OUT/ Oewa QbNz T8C+ UH30 WFsZ YsPT Y0wZ; 2; ZwBlAHIAYgBlAG4ALgBzAHQAYQBtAEAAbgBpAGMAZQAuAGMAbwBtADsAcwBpAHAAcgBlAGMAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {7D6341E8-9DBC-4CCD-9033-D2C837F543EA}; cABhAHIAdABoAGEAQABwAGEAcgB0AGgAYQBzAGEAcgBhAHQAaABpAC4AYwBvAC4AaQBuAA==; Tue, 11 Mar 2014 00:32:58 GMT; UwBJAFAAUgBFAEMAIABtAGUAdABhAGQAYQB0AGEAIABlAHgAYQBtAHAAbABlACAAYwBvAG0AbQBlAG4AdABzAA==
x-cr-puzzleid: {7D6341E8-9DBC-4CCD-9033-D2C837F543EA}
X-CTCH-RefID: str=0001.0A020204.531E59D1.009E, ss=2, re=0.000, recu=0.000, reip=0.000, cl=2, cld=1, fgs=64
X-CTCH-VOD: Unknown
X-CTCH-Spam: Suspect
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 64
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 172.18.214.93
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/k2UZgU_BVo7Wd03F1wkzBAETEO4
Cc: siprec@ietf.org
Subject: [siprec] SIPREC metadata example comments
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 11 Mar 2014 00:33:31 -0000

Hi Gerben,

In IETF-89 SIPREC meeting, you have mentioned about two issues related to
SIRPEC metadata 

1) Trading scenario wherein the participant added/removed very quickly as it
is conference. Here the concern is that all participant are required to be
forwarded SRC to SRS whenever there is a change in participants.

<Solution> Sec 3.3.3 of
http://tools.ietf.org/html/draft-ietf-siprec-callflows-02#page-24 explains
how to add/remove participant without sending every participant. Please let
me know in case you have any difficulties in using this solution.
</solution>

2) Group is interpreted differently in trading scenario. 

Please look into Sec 3.5 of
http://tools.ietf.org/html/draft-ietf-siprec-callflows-02#page-28 as it is a
trading scenario to understand the one of the possible usage with group.
Having said that, I'm not very clear about your problem statement. Please
clarify in case I didn't understand your concern.

Thanks
Partha


From nobody Tue Mar 11 01:29:32 2014
Return-Path: <finlay.fraser@bt.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 402031A03E0 for <siprec@ietfa.amsl.com>; Tue, 11 Mar 2014 01:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wGP9FhBSULp7 for <siprec@ietfa.amsl.com>; Tue, 11 Mar 2014 01:29:26 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [62.239.224.235]) by ietfa.amsl.com (Postfix) with ESMTP id 740FA1A03DB for <siprec@ietf.org>; Tue, 11 Mar 2014 01:29:26 -0700 (PDT)
Received: from EVMHT69-UKRD.domain1.systemhost.net (10.36.3.129) by RDW083A006ED62.bt.com (10.187.98.11) with Microsoft SMTP Server (TLS) id 14.3.169.1; Tue, 11 Mar 2014 08:29:22 +0000
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.2.69]) by EVMHT69-UKRD.domain1.systemhost.net ([10.36.3.129]) with mapi; Tue, 11 Mar 2014 08:29:19 +0000
From: <finlay.fraser@bt.com>
To: <partha@parthasarathi.co.in>, <Gerben.Stam@nice.com>
Date: Tue, 11 Mar 2014 08:29:18 +0000
Thread-Topic: [siprec] SIPREC metadata example comments
Thread-Index: Ac88wXMMO1NuT/MET1OLER8Y8eq5RAAQWpgn
Message-ID: <67DAF295CD01EB44AE6EA8A51F6ABF0A43559C0758@EMV62-UKRD.domain1.systemhost.net>
References: <001c01cf3cc1$7b0ce0f0$7126a2d0$@co.in>
In-Reply-To: <001c01cf3cc1$7b0ce0f0$7126a2d0$@co.in>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/aTHGI7BF_wlp7UjeHxzVgcNCV3I
Cc: siprec@ietf.org
Subject: Re: [siprec] SIPREC metadata example comments
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 11 Mar 2014 08:29:31 -0000

Partha

Are you saying RFC4575 is mandatory package for SIPREC support and would ha=
ve to be available.

If not and there is no RFC4575 feed available how does the participant know=
 about all the other parties and their state if they are not sent in the Me=
tadata UPDATE.

Or have I missed the meaning of the paragraph

On the use of groups in trading

We have a use case where two communication sessions that are established wi=
th one or more parties merge together to form a single call. We need a way =
to tag all legs of the call to indicate this. To do this we propose to use =
Group so the two CS will stay the same but both will now share a group tag.

Note it is also possible for merge calls to be merged. When this happens a =
new group tag will be added.
In this way a VR can find original CS and be aware that it was merged and f=
rom the merge tags it can locate all other parties in the call.

If there is a better way to deal with this pleases let me know.


Finlay Fraser
Annandale House
1 Hanworth Road
Sunbury on Thames
TW16 5DJ
BT IP Tel: +44 (0)1932773310 | Mob: +44(0)7711860228 | E: finlay.fraser@bt.=
com
________________________________________
From: siprec [siprec-bounces@ietf.org] On Behalf Of Parthasarathi R [partha=
@parthasarathi.co.in]
Sent: 11 March 2014 00:33
To: Gerben.Stam@nice.com
Cc: siprec@ietf.org
Subject: [siprec] SIPREC metadata example comments

Hi Gerben,

In IETF-89 SIPREC meeting, you have mentioned about two issues related to
SIRPEC metadata

1) Trading scenario wherein the participant added/removed very quickly as i=
t
is conference. Here the concern is that all participant are required to be
forwarded SRC to SRS whenever there is a change in participants.

<Solution> Sec 3.3.3 of
http://tools.ietf.org/html/draft-ietf-siprec-callflows-02#page-24 explains
how to add/remove participant without sending every participant. Please let
me know in case you have any difficulties in using this solution.
</solution>

2) Group is interpreted differently in trading scenario.

Please look into Sec 3.5 of
http://tools.ietf.org/html/draft-ietf-siprec-callflows-02#page-28 as it is =
a
trading scenario to understand the one of the possible usage with group.
Having said that, I'm not very clear about your problem statement. Please
clarify in case I didn't understand your concern.

Thanks
Partha

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


From nobody Tue Mar 11 04:48:39 2014
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9A2A1A068D for <siprec@ietfa.amsl.com>; Tue, 11 Mar 2014 04:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level: 
X-Spam-Status: No, score=-15.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2_BvBXmURRo for <siprec@ietfa.amsl.com>; Tue, 11 Mar 2014 04:48:35 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9404B1A066C for <siprec@ietf.org>; Tue, 11 Mar 2014 04:48:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3969; q=dns/txt; s=iport; t=1394538510; x=1395748110; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=8b71r5+J1GkTfIxlBtKdgDHFZ8MkwrqVXCRv5A44Xo0=; b=bit/COSNdKdWkIpfBaRTadPrOIVZlfIYkNW50BUElXnDIV5q7vRXs6Zk VcqybRCUBtYALLBkvXryTDjPWWLbCRQsk3nG+02N5wFNKkqMn7cFQANQb 9jJxXclqpCM3YTHKWEx+egIyDWfNdb8EamOaqjoCf5E/V4G/C1O79QshC Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAKr3HlOtJXG8/2dsb2JhbABagwY7V8BoT4EgFnSCJQEBAQQBAQFlBgsMBAIBCBEDAQEBLycLHQgCBAENBRuHXg3QeheOMSsHAgSEMgSJGY8sgTKQe4Mtgis
X-IronPort-AV: E=Sophos;i="4.97,630,1389744000"; d="scan'208";a="309281871"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 11 Mar 2014 11:48:29 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id s2BBmT8L012896 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Mar 2014 11:48:29 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.129]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Tue, 11 Mar 2014 06:48:29 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "finlay.fraser@bt.com" <finlay.fraser@bt.com>, "partha@parthasarathi.co.in" <partha@parthasarathi.co.in>, "Gerben.Stam@nice.com" <Gerben.Stam@nice.com>
Thread-Topic: [siprec] SIPREC metadata example comments
Thread-Index: AQHPPR/RGuM4Kd8dwUawEqFUPJjgfA==
Date: Tue, 11 Mar 2014 11:48:29 +0000
Message-ID: <CF44F352.8227B%rmohanr@cisco.com>
References: <001c01cf3cc1$7b0ce0f0$7126a2d0$@co.in> <67DAF295CD01EB44AE6EA8A51F6ABF0A43559C0758@EMV62-UKRD.domain1.systemhost.net>
In-Reply-To: <67DAF295CD01EB44AE6EA8A51F6ABF0A43559C0758@EMV62-UKRD.domain1.systemhost.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [173.39.64.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B8E84F5DDB19C34D8D8E6678EF1224E4@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/QS4sxUSh8rbSHaCVgZN4P9xktiw
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] SIPREC metadata example comments
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 11 Mar 2014 11:48:38 -0000

Please see inline for some comments

-----Original Message-----
From: "finlay.fraser@bt.com" <finlay.fraser@bt.com>
Date: Tuesday, 11 March 2014 1:59 pm
To: "partha@parthasarathi.co.in" <partha@parthasarathi.co.in>,
"Gerben.Stam@nice.com" <Gerben.Stam@nice.com>
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] SIPREC metadata example comments

>Partha
>
>Are you saying RFC4575 is mandatory package for SIPREC support and would
>have to be available.

No. SIPREC does not mandate you to have RFC4575. It is up to the SRC
(participant in the conference in this example) to learn the details of
the other participant in the conference session before it sends snapshot
of metadata to SRS. It may use RFC4575 method by subscribing to a
conference focus or use some other means to get the details. We are not
mandating to use RFC4575 only.

SIPREC only talks about how a SRC sends(the protocol semantics) metadata
to SRS and semantics of metadata(XML schema). How SRC gets the information
that fills up metadata is purely a application logic and IMO need not be
defined in the on-wire protocol.

>
>If not and there is no RFC4575 feed available how does the participant
>know about all the other parties and their state if they are not sent in
>the Metadata UPDATE
>
>Or have I missed the meaning of the paragraph
>
>On the use of groups in trading
>
>We have a use case where two communication sessions that are established
>with one or more parties merge together to form a single call. We need a
>way to tag all legs of the call to indicate this. To do this we propose
>to use Group so the two CS will stay the same but both will now share a
>group tag.

Yes. CS-group is specifically is meant for this purpose. If a application
wants to link two CS=B9s it can use this CS-group and tag them together.
Your understanding is correct here.

Regards,
Ram

>
>Note it is also possible for merge calls to be merged. When this happens
>a new group tag will be added.
>In this way a VR can find original CS and be aware that it was merged and
>from the merge tags it can locate all other parties in the call.
>
>If there is a better way to deal with this pleases let me know.
>
>
>Finlay Fraser
>Annandale House
>1 Hanworth Road
>Sunbury on Thames
>TW16 5DJ
>BT IP Tel: +44 (0)1932773310 | Mob: +44(0)7711860228 | E:
>finlay.fraser@bt.com
>________________________________________
>From: siprec [siprec-bounces@ietf.org] On Behalf Of Parthasarathi R
>[partha@parthasarathi.co.in]
>Sent: 11 March 2014 00:33
>To: Gerben.Stam@nice.com
>Cc: siprec@ietf.org
>Subject: [siprec] SIPREC metadata example comments
>
>Hi Gerben,
>
>In IETF-89 SIPREC meeting, you have mentioned about two issues related to
>SIRPEC metadata
>
>1) Trading scenario wherein the participant added/removed very quickly as
>it
>is conference. Here the concern is that all participant are required to be
>forwarded SRC to SRS whenever there is a change in participants.
>
><Solution> Sec 3.3.3 of
>http://tools.ietf.org/html/draft-ietf-siprec-callflows-02#page-24 explains
>how to add/remove participant without sending every participant. Please
>let
>me know in case you have any difficulties in using this solution.
></solution>
>
>2) Group is interpreted differently in trading scenario.
>
>Please look into Sec 3.5 of
>http://tools.ietf.org/html/draft-ietf-siprec-callflows-02#page-28 as it
>is a
>trading scenario to understand the one of the possible usage with group.
>Having said that, I'm not very clear about your problem statement. Please
>clarify in case I didn't understand your concern.
>
>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 nobody Thu Mar 13 08:46:18 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDD831A0873 for <siprec@ietfa.amsl.com>; Thu, 13 Mar 2014 08:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.547
X-Spam-Level: 
X-Spam-Status: No, score=-0.547 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bezlsvw0IlTf for <siprec@ietfa.amsl.com>; Thu, 13 Mar 2014 08:46:13 -0700 (PDT)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 452731A088B for <siprec@ietf.org>; Thu, 13 Mar 2014 08:46:13 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id 106EE1EB8623 for <siprec@ietf.org>; Thu, 13 Mar 2014 16:46:06 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.208]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0174.001; Thu, 13 Mar 2014 16:46:05 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: IETF89 SIPEC Minutes
Thread-Index: Ac8+01fvqD1RaRrcT2KkjG8WK4bHfg==
Date: Thu, 13 Mar 2014 15:46:05 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17D35165@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: multipart/alternative; boundary="_000_9F33F40F6F2CD847824537F3C4E37DDF17D35165MCHP04MSXglobal_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/1mxQtJq3utpr3xnCvg0q3U9cUQ0
Subject: [siprec] IETF89 SIPEC Minutes
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 13 Mar 2014 15:46:15 -0000

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

Hi All,

It was great to see so many of you in London last week.

I posted the raw notes that Christine kindly made during the meeting please=
 let me know if you spot any major mistakes or missing actions.

http://www.ietf.org/proceedings/89/minutes/minutes-89-siprec

I take a closer look at them myself shortly.

Regards
Andy


--_000_9F33F40F6F2CD847824537F3C4E37DDF17D35165MCHP04MSXglobal_
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"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>Hi All,</div>
<div>&nbsp;</div>
<div>It was great to see so many of you in London last week.</div>
<div>&nbsp;</div>
<div>I posted the raw notes that Christine kindly made during the meeting p=
lease let me know if you spot any major mistakes or missing actions.</div>
<div>&nbsp;</div>
<div><a href=3D"http://www.ietf.org/proceedings/89/minutes/minutes-89-sipre=
c"><font color=3D"blue"><u>http://www.ietf.org/proceedings/89/minutes/minut=
es-89-siprec</u></font></a> </div>
<div>&nbsp;</div>
<div>I take a closer look at them myself shortly.</div>
<div>&nbsp;</div>
<div>Regards<br>

Andy</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_9F33F40F6F2CD847824537F3C4E37DDF17D35165MCHP04MSXglobal_--


From nobody Thu Mar 13 11:49:31 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED7301A093D for <siprec@ietfa.amsl.com>; Thu, 13 Mar 2014 11:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zec3tv0xdyCJ for <siprec@ietfa.amsl.com>; Thu, 13 Mar 2014 11:49:27 -0700 (PDT)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 38C691A058E for <siprec@ietf.org>; Thu, 13 Mar 2014 11:49:27 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id 25E4323F0678; Thu, 13 Mar 2014 19:49:20 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.208]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0174.001; Thu, 13 Mar 2014 19:49:19 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: SIPREC Milestone Update.
Thread-Index: AQHPPuzxMCDLaWKnsESlQX1WYgfyVg==
Date: Thu, 13 Mar 2014 18:49:19 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net>
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/buqFAa9mTnUh46xTiHx2WXSN2gw
Subject: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 13 Mar 2014 18:49:30 -0000

During the IETF89 SIPREC meeting a discrepancy was identified between my sl=
ides showing the proposed new milestones and Paul's slides.

The chairs slides stated the following milestone:

"??? 2014 	Protocol and metadata for capturing the content (RFC 4796) of th=
e media stream".

Whilst Paul's conference recording slides stated

"Dec 2014	Protocol and metadata for recording of document & application sha=
ring to IESG as Proposed Standard RFC"

I posted this suggested change to the list as can be seen in the message be=
low and received no comments. The rational for the suggestion is also given=
 in the text below but is basically that we did not have consensus for reco=
rding of document and application sharing just for video with reference to =
the content.

Please give feedback as to whether the milestone with reference to RFC 4796=
 makes sense.

Regards
Andy





> -----Original Message-----
> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
> Andrew
> Sent: 23 December 2013 15:24
> To: Paul Kyzivat; siprec@ietf.org
> Subject: Re: [siprec] Reminder: Additional use cases for draft-kyzivat-
> siprec-conference-use-cases-00
>=20
> Hi All,
>=20
> Since nobody posted any new uses cases I went back to our discussion in
> Vancouver and tried to see what we appeared to have consensus on in the
> meeting.
>=20
> From that I have formed a proposal for a charter update which is given
> below and also attached (with changes highlighted).
>=20
> It seems everybody agreed that we need to clarify that SIPREC is
> limited to SIP based systems and that MSRP recording needs to be added.
>=20
> It also seemed to me that there was no consensus on adding the generic
> case of document/application sharing but if this was limited to being a
> video session in which the content type (RFC 4796) formed part of the
> metadata then probably we would have consensus.  So I included a
> suggested reference to this as a milestone please comment on whether
> this makes sense.
>=20
> There was a lot of discussion in the Vancouver meeting about defining a
> generic mechanism to record media without the need to come back to
> SIPREC every time new media types or metadata needs to be recorded.
> There has been no use cases submitted or discussion on possible
> mechanism since the meeting so I see no way to progress this at
> present.
>=20
>=20
> Please can provide comments and Paul and others who stated they would
> contribute can you confirm that you still intend to do so and that this
> charter proposal is acceptable to you.
>=20
> Regards
> Andy
>=20
>=20
>=20
> =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
> SUGGESTED CHARTER - UPDATE
> =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
>=20
> 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, business analytics, or consumer protection. Recording
> is typically done by sending a copy of the media to the recording
> devices. The working group will determine requirements and produce a
> specification for a protocol that will manage delivery of media, in SIP
> based systems (including audio, video, MSRP instant message sessions)
> from an end-point that originates media, or that has access to it, to a
> recording device. PBX and recording vendors today implement
> proprietary, incompatible mechanisms to facilitate recording. A
> standard protocol will reduce the complexity and cost of providing such
> recording services.
>=20
> The group will define these issues and rationalize with IETF standards
> and practices. This includes encryption, NAT traversal, operations and
> manageability, SIP-enabled firewalls, authorization, and security.
> The scope explicitly does not include recording any of the extended
> session attributes being defined by the CLUE WG. (These may be
> addressed by a subsequent effort.)
>=20
> The group will produce:
>=20
> * Updated Requirements, Use Cases, Architecture draft
>=20
> * Specification for Session Recording Protocol and Metadata
>=20
> Milestones
>=20
> DONE   	Use Cases and Requirements to IESG as Informational RFC
> MAR 2014 	Submit Architecture to IESG as Informational RFC
> JUN 2014 	Submit protocol draft to IESG as Proposed Standard RFC
> AUG 2014 	Submit Metadata model and format to IESG as Proposed
> Standard RFC
> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an informational
> RFC
> ??? 2014 	Conference Recording Use Cases and Requirements to IESG as
> Informational RFC
> ??? 2014 	Conference Recording Architecture to IESG as Informational
> RFC
> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
> Proposed Standard RFC
> ??? 2014 	Protocol and metadata for capturing the content (RFC 4796)
> of the media stream.
>=20
>=20
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
>=20
> > -----Original Message-----
> > From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Paul
> Kyzivat
> > Sent: 21 November 2013 18:44
> > To: siprec@ietf.org
> > Subject: Re: [siprec] Reminder: Additional use cases for draft-
> kyzivat-
> > siprec-conference-use-cases-00
> >
> > I still haven't seen anything on this subject.
> > I *thought* there were multiple people in the siprec session in
> > Vancouver that seemed to have other use cases related to media.
> >
> > If so, better speak up, or IIUC we are going to treat the use cases
> we
> > have as bounding the new scope.
> >
> > 	Thanks,
> > 	Paul
> >
> > On 11/15/13 9:31 AM, Paul Kyzivat wrote:
> > > One of the action items from the meeting last week was:
> > >
> > >> chairs: use cases to the list in the next couple of weeks.  After
> > that,
> > >> we will decide if we need charter language.  If your use case is
> not
> > >> contributed, it will not be considered in the milestones.
> > >
> > > The above is a little vague about the timing. Two weeks from the
> end
> > of
> > > the meeting would be Friday, November 23. (Hopefully the chairs
> will
> > > clarify this.)
> > >
> > > This is important because there was some desire to tighten up the
> > scope
> > > of the rechartering to encompass only the mentioned use cases.
> > >
> > > I'll be happy to incorporate additional popular use cases even
> before
> > > this draft becomes a wg draft. (But please send text.)
> > >
> > > While the name of the draft is about conferences, the use cases
> > include
> > > additional media support. (Maybe we should rename the draft.) And
> it
> > > seemed that much of the interest was about additional media.
> > >
> > >      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 nobody Fri Mar 14 07:36:35 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC051A014F for <siprec@ietfa.amsl.com>; Fri, 14 Mar 2014 07:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFuYhWVC8Evy for <siprec@ietfa.amsl.com>; Fri, 14 Mar 2014 07:36:31 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id A210E1A0154 for <siprec@ietf.org>; Fri, 14 Mar 2014 07:36:31 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta02.westchester.pa.mail.comcast.net with comcast id dQcg1n0070bG4ec51ScQl6; Fri, 14 Mar 2014 14:36:24 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta03.westchester.pa.mail.comcast.net with comcast id dScQ1n00L3ZTu2S3PScQwg; Fri, 14 Mar 2014 14:36:24 +0000
Message-ID: <532313E8.2070904@alum.mit.edu>
Date: Fri, 14 Mar 2014 10:36:24 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Hutton, Andrew" <andrew.hutton@unify.com>,  "siprec@ietf.org" <siprec@ietf.org>
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1394807784; bh=TgJjriw668/LshEg8WWiC+PWobfXTmSu8Js8pb3Bjq8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=QkPl5QS6wFaxQHhpxSwvcd4V5yAHY1nArGpQpzFcPdKoTNad6qFuPeYMtJjdQVzMU bTrVdszVv0nFekI9NYA+/bviDCw3SbIP8MSZ6Hol8dH4NJqKP7uW76RN4H9Rz8EIuU LxM2dqCKOM779FeuITR8jHZ1rcnH5GBGe4L0q/Ou63FfMEcX/btueovKARmJDjOScH BogXseSQtM2roqBjU5mZ+wHZHRxPGDJaCcCyIiiQRcOZCVFNubmaey6LksFhdvOVOS +4Ji9b0OWIduUxM2STnSbMkPyzMMCmUsZ/S44HdJduRx0eUGmaqBT6MelcdTW1bz0U XTT0rSO+Vvk9A==
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/7XxgHO8L4yYXKpvlzWVVhAeh3Pk
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 14 Mar 2014 14:36:34 -0000

Andy,

On 3/13/14 2:49 PM, Hutton, Andrew wrote:
> During the IETF89 SIPREC meeting a discrepancy was identified between my slides showing the proposed new milestones and Paul's slides.
>
> The chairs slides stated the following milestone:
>
> "??? 2014 	Protocol and metadata for capturing the content (RFC 4796) of the media stream".
>
> Whilst Paul's conference recording slides stated
>
> "Dec 2014	Protocol and metadata for recording of document & application sharing to IESG as Proposed Standard RFC"
>
> I posted this suggested change to the list as can be seen in the message below and received no comments. The rational for the suggestion is also given in the text below but is basically that we did not have consensus for recording of document and application sharing just for video with reference to the content.
>
> Please give feedback as to whether the milestone with reference to RFC 4796 makes sense.

IMO limiting this to RFC 4796 is too narrow for the milestone. It may 
turn out that 4796 is *part* of the mechanism, but I certainly don't 
want to be limited to that. While it needs discussion, I have in mind to 
capture additional metadata, such as:
- the distinction between document, application, and screen sharing
- the name of the document or application

These won't always be available, but if they are they would be useful to 
record.

Also, while the intent is to capture presentations using video (and 
perhaps audio) media streams, we *may* also want to say something about 
*how* this is done.

And, if the presentation media includes audio as well as video, and the 
audio is distinct from the "room audio", we may want metadata to tie the 
audio and video together.

Note that I've phrased the above as *may* because IMO this stuff is all 
subject to debate. But I would like it to be within the scope of the 
milestone.

That is why I phrased the milestone the way I did.

The date for the milestone is another question. The December date is 
probably a little optimistic, but I'd rather do that than have it be 
pessimistic and just dawdle. But in the end the milestone dates are 
really up to the chairs and ADs.

	Thanks,
	Paul

> Regards
> Andy
>
>
>
>
>
>> -----Original Message-----
>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
>> Andrew
>> Sent: 23 December 2013 15:24
>> To: Paul Kyzivat; siprec@ietf.org
>> Subject: Re: [siprec] Reminder: Additional use cases for draft-kyzivat-
>> siprec-conference-use-cases-00
>>
>> Hi All,
>>
>> Since nobody posted any new uses cases I went back to our discussion in
>> Vancouver and tried to see what we appeared to have consensus on in the
>> meeting.
>>
>>  From that I have formed a proposal for a charter update which is given
>> below and also attached (with changes highlighted).
>>
>> It seems everybody agreed that we need to clarify that SIPREC is
>> limited to SIP based systems and that MSRP recording needs to be added.
>>
>> It also seemed to me that there was no consensus on adding the generic
>> case of document/application sharing but if this was limited to being a
>> video session in which the content type (RFC 4796) formed part of the
>> metadata then probably we would have consensus.  So I included a
>> suggested reference to this as a milestone please comment on whether
>> this makes sense.
>>
>> There was a lot of discussion in the Vancouver meeting about defining a
>> generic mechanism to record media without the need to come back to
>> SIPREC every time new media types or metadata needs to be recorded.
>> There has been no use cases submitted or discussion on possible
>> mechanism since the meeting so I see no way to progress this at
>> present.
>>
>>
>> Please can provide comments and Paul and others who stated they would
>> contribute can you confirm that you still intend to do so and that this
>> charter proposal is acceptable to you.
>>
>> Regards
>> Andy
>>
>>
>>
>> =====================================
>> SUGGESTED CHARTER - UPDATE
>> =====================================
>>
>> 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, business analytics, or consumer protection. Recording
>> is typically done by sending a copy of the media to the recording
>> devices. The working group will determine requirements and produce a
>> specification for a protocol that will manage delivery of media, in SIP
>> based systems (including audio, video, MSRP instant message sessions)
>> from an end-point that originates media, or that has access to it, to a
>> recording device. PBX and recording vendors today implement
>> proprietary, incompatible mechanisms to facilitate recording. A
>> standard protocol will reduce the complexity and cost of providing such
>> recording services.
>>
>> The group will define these issues and rationalize with IETF standards
>> and practices. This includes encryption, NAT traversal, operations and
>> manageability, SIP-enabled firewalls, authorization, and security.
>> The scope explicitly does not include recording any of the extended
>> session attributes being defined by the CLUE WG. (These may be
>> addressed by a subsequent effort.)
>>
>> The group will produce:
>>
>> * Updated Requirements, Use Cases, Architecture draft
>>
>> * Specification for Session Recording Protocol and Metadata
>>
>> Milestones
>>
>> DONE   	Use Cases and Requirements to IESG as Informational RFC
>> MAR 2014 	Submit Architecture to IESG as Informational RFC
>> JUN 2014 	Submit protocol draft to IESG as Proposed Standard RFC
>> AUG 2014 	Submit Metadata model and format to IESG as Proposed
>> Standard RFC
>> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an informational
>> RFC
>> ??? 2014 	Conference Recording Use Cases and Requirements to IESG as
>> Informational RFC
>> ??? 2014 	Conference Recording Architecture to IESG as Informational
>> RFC
>> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
>> Proposed Standard RFC
>> ??? 2014 	Protocol and metadata for capturing the content (RFC 4796)
>> of the media stream.
>>
>>
>> =======================================================================
>> =====================
>>
>>
>>
>>> -----Original Message-----
>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Paul
>> Kyzivat
>>> Sent: 21 November 2013 18:44
>>> To: siprec@ietf.org
>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
>> kyzivat-
>>> siprec-conference-use-cases-00
>>>
>>> I still haven't seen anything on this subject.
>>> I *thought* there were multiple people in the siprec session in
>>> Vancouver that seemed to have other use cases related to media.
>>>
>>> If so, better speak up, or IIUC we are going to treat the use cases
>> we
>>> have as bounding the new scope.
>>>
>>> 	Thanks,
>>> 	Paul
>>>
>>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
>>>> One of the action items from the meeting last week was:
>>>>
>>>>> chairs: use cases to the list in the next couple of weeks.  After
>>> that,
>>>>> we will decide if we need charter language.  If your use case is
>> not
>>>>> contributed, it will not be considered in the milestones.
>>>>
>>>> The above is a little vague about the timing. Two weeks from the
>> end
>>> of
>>>> the meeting would be Friday, November 23. (Hopefully the chairs
>> will
>>>> clarify this.)
>>>>
>>>> This is important because there was some desire to tighten up the
>>> scope
>>>> of the rechartering to encompass only the mentioned use cases.
>>>>
>>>> I'll be happy to incorporate additional popular use cases even
>> before
>>>> this draft becomes a wg draft. (But please send text.)
>>>>
>>>> While the name of the draft is about conferences, the use cases
>>> include
>>>> additional media support. (Maybe we should rename the draft.) And
>> it
>>>> seemed that much of the interest was about additional media.
>>>>
>>>>       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 nobody Mon Mar 17 15:21:37 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2320B1A063A for <siprec@ietfa.amsl.com>; Mon, 17 Mar 2014 15:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vZxUFCTrvu3z for <siprec@ietfa.amsl.com>; Mon, 17 Mar 2014 15:21:34 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:17]) by ietfa.amsl.com (Postfix) with ESMTP id EA4B01A031D for <siprec@ietf.org>; Mon, 17 Mar 2014 15:21:33 -0700 (PDT)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta10.westchester.pa.mail.comcast.net with comcast id eboN1n0061HzFnQ5AmMRr8; Mon, 17 Mar 2014 22:21:25 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta14.westchester.pa.mail.comcast.net with comcast id emMR1n00V3ZTu2S3amMRxb; Mon, 17 Mar 2014 22:21:25 +0000
Message-ID: <53277565.9040506@alum.mit.edu>
Date: Mon, 17 Mar 2014 18:21:25 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "siprec@ietf.org" <siprec@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395094885; bh=QS4geJBB+kZqX9twmEZf65LablTafr4fWFwBPzIp/1c=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=SK8WznnL3Qdq/xGIM0+ZiLOIuU53u5i/J6SwcVVe6Dn5r4YRj1KAKIINumS/I4AwF +sWXpAWVXm5UrHkpg9125/wzsHyI54HrKiIY91RVc3yma+05IndY1SqjMeVfBKPTMn EsFfRmtoW3qbcoH4eSgPiz0rtUrrsx2UAZzcxDT8CMUhyGPlCl0omsJQN0lf3VncRX mEKbxCIZIZyws4p0PnkcdQBYAYqe/y6/r3FE5APrei+QqIpDDX1o7gc8wYTKiQP92o 5gYEyNk2cDktrk8USWs5lE9yiNCU8UHUuMht+gQm9L+cf0GHRMzwHF0F/WbHoymqvz fta4aNYEuqHtQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/YbJV4MVNk6U-HmC5S8JpGpkxzVQ
Subject: [siprec] adoption of conf drafts
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 17 Mar 2014 22:21:35 -0000

In my presentation in London I talked about two drafts:

- draft-kyzivat-siprec-conference-use-cases-01
- draft-yan-siprec-msrp-recording-00

Toward the end of that presentation, the chair asked about adoption. The 
following is from the minutes:

Chair - is this ready to be adopted as a WG item yet?
Paul - use cases, approaching
Chair (Brian) - approaching what I need - speaking personally, exactly 
what I wanted to see in this work
Paul - want more discussion on the list - it is a framework at this 
stage - time to speak up - no strong preference -
Chair - please read the documents and send comments to the list - we 
want to move this document along

I have a couple of questions about this:

- was the question about adoption in regard to the use cases document,
   the msrp document, or both?

- how do you want to proceed on this? Do you want to make a proposal
   to adopt and ask for comments on that?

In any case, I ask for people to review and comment on both of these drafts.

	Thanks,
	Paul


From nobody Thu Mar 20 02:13:45 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F4C11A0691 for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 02:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Orf_AoQS43Jc for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 02:13:41 -0700 (PDT)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1F01A034A for <siprec@ietf.org>; Thu, 20 Mar 2014 02:13:40 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id D2CE923F05FF; Thu, 20 Mar 2014 10:13:30 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.208]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0174.001; Thu, 20 Mar 2014 10:13:30 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: SIPREC Milestone Update.
Thread-Index: AQHPPuzxMCDLaWKnsESlQX1WYgfyVprglu4AgAki16A=
Date: Thu, 20 Mar 2014 09:13:29 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net>
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net> <532313E8.2070904@alum.mit.edu>
In-Reply-To: <532313E8.2070904@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/vCFyNzD6AQaab4NurIyyWKgQaxg
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 20 Mar 2014 09:13:43 -0000

Paul,

The feedback we had during the IETF88 (Vancouver) meeting was that we could=
 not extend SIPREC to generically cover "document & application" sharing as=
 there is no standard to base this on.=20

Can you suggest a milestone that is more precise that we can get consensus =
on?

Andy



> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> Sent: 14 March 2014 14:36
> To: Hutton, Andrew; siprec@ietf.org
> Subject: Re: SIPREC Milestone Update.
>=20
> Andy,
>=20
> On 3/13/14 2:49 PM, Hutton, Andrew wrote:
> > During the IETF89 SIPREC meeting a discrepancy was identified between
> my slides showing the proposed new milestones and Paul's slides.
> >
> > The chairs slides stated the following milestone:
> >
> > "??? 2014 	Protocol and metadata for capturing the content (RFC
> 4796) of the media stream".
> >
> > Whilst Paul's conference recording slides stated
> >
> > "Dec 2014	Protocol and metadata for recording of document &
> application sharing to IESG as Proposed Standard RFC"
> >
> > I posted this suggested change to the list as can be seen in the
> message below and received no comments. The rational for the suggestion
> is also given in the text below but is basically that we did not have
> consensus for recording of document and application sharing just for
> video with reference to the content.
> >
> > Please give feedback as to whether the milestone with reference to
> RFC 4796 makes sense.
>=20
> IMO limiting this to RFC 4796 is too narrow for the milestone. It may
> turn out that 4796 is *part* of the mechanism, but I certainly don't
> want to be limited to that. While it needs discussion, I have in mind
> to
> capture additional metadata, such as:
> - the distinction between document, application, and screen sharing
> - the name of the document or application
>=20
> These won't always be available, but if they are they would be useful
> to
> record.
>=20
> Also, while the intent is to capture presentations using video (and
> perhaps audio) media streams, we *may* also want to say something about
> *how* this is done.
>=20
> And, if the presentation media includes audio as well as video, and the
> audio is distinct from the "room audio", we may want metadata to tie
> the
> audio and video together.
>=20
> Note that I've phrased the above as *may* because IMO this stuff is all
> subject to debate. But I would like it to be within the scope of the
> milestone.
>=20
> That is why I phrased the milestone the way I did.
>=20
> The date for the milestone is another question. The December date is
> probably a little optimistic, but I'd rather do that than have it be
> pessimistic and just dawdle. But in the end the milestone dates are
> really up to the chairs and ADs.
>=20
> 	Thanks,
> 	Paul
>=20
> > Regards
> > Andy
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
> >> Andrew
> >> Sent: 23 December 2013 15:24
> >> To: Paul Kyzivat; siprec@ietf.org
> >> Subject: Re: [siprec] Reminder: Additional use cases for draft-
> kyzivat-
> >> siprec-conference-use-cases-00
> >>
> >> Hi All,
> >>
> >> Since nobody posted any new uses cases I went back to our discussion
> in
> >> Vancouver and tried to see what we appeared to have consensus on in
> the
> >> meeting.
> >>
> >>  From that I have formed a proposal for a charter update which is
> given
> >> below and also attached (with changes highlighted).
> >>
> >> It seems everybody agreed that we need to clarify that SIPREC is
> >> limited to SIP based systems and that MSRP recording needs to be
> added.
> >>
> >> It also seemed to me that there was no consensus on adding the
> generic
> >> case of document/application sharing but if this was limited to
> being a
> >> video session in which the content type (RFC 4796) formed part of
> the
> >> metadata then probably we would have consensus.  So I included a
> >> suggested reference to this as a milestone please comment on whether
> >> this makes sense.
> >>
> >> There was a lot of discussion in the Vancouver meeting about
> defining a
> >> generic mechanism to record media without the need to come back to
> >> SIPREC every time new media types or metadata needs to be recorded.
> >> There has been no use cases submitted or discussion on possible
> >> mechanism since the meeting so I see no way to progress this at
> >> present.
> >>
> >>
> >> Please can provide comments and Paul and others who stated they
> would
> >> contribute can you confirm that you still intend to do so and that
> this
> >> charter proposal is acceptable to you.
> >>
> >> Regards
> >> Andy
> >>
> >>
> >>
> >> =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
> >> SUGGESTED CHARTER - UPDATE
> >> =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
> >>
> >> 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, business analytics, or consumer protection.
> Recording
> >> is typically done by sending a copy of the media to the recording
> >> devices. The working group will determine requirements and produce a
> >> specification for a protocol that will manage delivery of media, in
> SIP
> >> based systems (including audio, video, MSRP instant message
> sessions)
> >> from an end-point that originates media, or that has access to it,
> to a
> >> recording device. PBX and recording vendors today implement
> >> proprietary, incompatible mechanisms to facilitate recording. A
> >> standard protocol will reduce the complexity and cost of providing
> such
> >> recording services.
> >>
> >> The group will define these issues and rationalize with IETF
> standards
> >> and practices. This includes encryption, NAT traversal, operations
> and
> >> manageability, SIP-enabled firewalls, authorization, and security.
> >> The scope explicitly does not include recording any of the extended
> >> session attributes being defined by the CLUE WG. (These may be
> >> addressed by a subsequent effort.)
> >>
> >> The group will produce:
> >>
> >> * Updated Requirements, Use Cases, Architecture draft
> >>
> >> * Specification for Session Recording Protocol and Metadata
> >>
> >> Milestones
> >>
> >> DONE   	Use Cases and Requirements to IESG as Informational RFC
> >> MAR 2014 	Submit Architecture to IESG as Informational RFC
> >> JUN 2014 	Submit protocol draft to IESG as Proposed Standard
> RFC
> >> AUG 2014 	Submit Metadata model and format to IESG as Proposed
> >> Standard RFC
> >> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an
> informational
> >> RFC
> >> ??? 2014 	Conference Recording Use Cases and Requirements to
> IESG as
> >> Informational RFC
> >> ??? 2014 	Conference Recording Architecture to IESG as
> Informational
> >> RFC
> >> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
> >> Proposed Standard RFC
> >> ??? 2014 	Protocol and metadata for capturing the content (RFC
> 4796)
> >> of the media stream.
> >>
> >>
> >>
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Paul
> >> Kyzivat
> >>> Sent: 21 November 2013 18:44
> >>> To: siprec@ietf.org
> >>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
> >> kyzivat-
> >>> siprec-conference-use-cases-00
> >>>
> >>> I still haven't seen anything on this subject.
> >>> I *thought* there were multiple people in the siprec session in
> >>> Vancouver that seemed to have other use cases related to media.
> >>>
> >>> If so, better speak up, or IIUC we are going to treat the use cases
> >> we
> >>> have as bounding the new scope.
> >>>
> >>> 	Thanks,
> >>> 	Paul
> >>>
> >>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
> >>>> One of the action items from the meeting last week was:
> >>>>
> >>>>> chairs: use cases to the list in the next couple of weeks.  After
> >>> that,
> >>>>> we will decide if we need charter language.  If your use case is
> >> not
> >>>>> contributed, it will not be considered in the milestones.
> >>>>
> >>>> The above is a little vague about the timing. Two weeks from the
> >> end
> >>> of
> >>>> the meeting would be Friday, November 23. (Hopefully the chairs
> >> will
> >>>> clarify this.)
> >>>>
> >>>> This is important because there was some desire to tighten up the
> >>> scope
> >>>> of the rechartering to encompass only the mentioned use cases.
> >>>>
> >>>> I'll be happy to incorporate additional popular use cases even
> >> before
> >>>> this draft becomes a wg draft. (But please send text.)
> >>>>
> >>>> While the name of the draft is about conferences, the use cases
> >>> include
> >>>> additional media support. (Maybe we should rename the draft.) And
> >> it
> >>>> seemed that much of the interest was about additional media.
> >>>>
> >>>>       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 nobody Thu Mar 20 02:19:10 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F10841A06E8 for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 02:19:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vmEqWRY9ch_j for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 02:19:08 -0700 (PDT)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id CCCEF1A06AB for <siprec@ietf.org>; Thu, 20 Mar 2014 02:19:07 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx11.unify.com (Server) with ESMTP id 35A341EB85E8; Thu, 20 Mar 2014 10:18:58 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.208]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0174.001; Thu, 20 Mar 2014 10:18:58 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] adoption of conf drafts
Thread-Index: AQHPQi8/xyHElNoCDUSlL6eJEH0LiZrptVhA
Date: Thu, 20 Mar 2014 09:18:56 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17D3C3A8@MCHP04MSX.global-ad.net>
References: <53277565.9040506@alum.mit.edu>
In-Reply-To: <53277565.9040506@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/BpPJsTo2fvqeBcCCLyjbrz0hwX0
Subject: Re: [siprec] adoption of conf drafts
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 20 Mar 2014 09:19:09 -0000

On: 17 March 2014 22:21 Paul Kyzivat Wrote:
>=20
> In any case, I ask for people to review and comment on both of these
> drafts.
>

We definitely need some review and list discussion on these two documents t=
o get an idea of the level of support for them and whether they are what th=
e group wants to adopt.

So please have a look at these and send comments.

- draft-kyzivat-siprec-conference-use-cases-01
- draft-yan-siprec-msrp-recording-00


Andy
=20


From nobody Thu Mar 20 07:59:20 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEBEB1A03FE for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 07:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iG-L37lxN_UH for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 07:59:16 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id E16E51A046A for <siprec@ietf.org>; Thu, 20 Mar 2014 07:59:15 -0700 (PDT)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta02.westchester.pa.mail.comcast.net with comcast id foRP1n0010mv7h051qz6rD; Thu, 20 Mar 2014 14:59:06 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta11.westchester.pa.mail.comcast.net with comcast id fqz61n00d3ZTu2S3Xqz6EH; Thu, 20 Mar 2014 14:59:06 +0000
Message-ID: <532B023A.9060203@alum.mit.edu>
Date: Thu, 20 Mar 2014 10:59:06 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Hutton, Andrew" <andrew.hutton@unify.com>
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net> <532313E8.2070904@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395327546; bh=QvlqKByOrPZ3ajIbQICzAGnKqUo2OtFJ4e66pfdvlRg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=g7gmbKl4Fb4hBvnSzgXN9RtXGbBlVY9aIpmLYehDi+x1+A+ADSqbo6/1Pn8Sy2h9W yvp47d9jYWSouO6xYnYvuZ9i43wns6LQ6vZjt/D2UAxVjrDdh9ZOhYJPIlklqYhiEQ BklZeNjwwupQ+tb/zurgz4r6QljL8jPSil69HpSxtdq+uip2MGEx6kRxgfg1t5tgKZ SN89YC6MKwGqax2bw2oWn9aqwbxtK0nmtsIKTg744HXIvCYoaLsjFDxRyu3BmCTovD AiKYmMpjVKU27WmGe7u+j908V6C1KJg4F+7HNj3MCGK26mHW2r2jhg5YvzQjNGb4HA h8tOjOxcjOLDQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/FGO8iZ7rKxVwgMkNVXA3QkMoJ5E
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 20 Mar 2014 14:59:19 -0000

On 3/20/14 5:13 AM, Hutton, Andrew wrote:
> Paul,
>
> The feedback we had during the IETF88 (Vancouver) meeting was that we could not extend SIPREC to generically cover "document & application" sharing as there is no standard to base this on.
>
> Can you suggest a milestone that is more precise that we can get consensus on?

OK. I will think on it and come back with a new proposal.

	Thanks,
	Paul

> Andy
>
>
>
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>> Sent: 14 March 2014 14:36
>> To: Hutton, Andrew; siprec@ietf.org
>> Subject: Re: SIPREC Milestone Update.
>>
>> Andy,
>>
>> On 3/13/14 2:49 PM, Hutton, Andrew wrote:
>>> During the IETF89 SIPREC meeting a discrepancy was identified between
>> my slides showing the proposed new milestones and Paul's slides.
>>>
>>> The chairs slides stated the following milestone:
>>>
>>> "??? 2014 	Protocol and metadata for capturing the content (RFC
>> 4796) of the media stream".
>>>
>>> Whilst Paul's conference recording slides stated
>>>
>>> "Dec 2014	Protocol and metadata for recording of document &
>> application sharing to IESG as Proposed Standard RFC"
>>>
>>> I posted this suggested change to the list as can be seen in the
>> message below and received no comments. The rational for the suggestion
>> is also given in the text below but is basically that we did not have
>> consensus for recording of document and application sharing just for
>> video with reference to the content.
>>>
>>> Please give feedback as to whether the milestone with reference to
>> RFC 4796 makes sense.
>>
>> IMO limiting this to RFC 4796 is too narrow for the milestone. It may
>> turn out that 4796 is *part* of the mechanism, but I certainly don't
>> want to be limited to that. While it needs discussion, I have in mind
>> to
>> capture additional metadata, such as:
>> - the distinction between document, application, and screen sharing
>> - the name of the document or application
>>
>> These won't always be available, but if they are they would be useful
>> to
>> record.
>>
>> Also, while the intent is to capture presentations using video (and
>> perhaps audio) media streams, we *may* also want to say something about
>> *how* this is done.
>>
>> And, if the presentation media includes audio as well as video, and the
>> audio is distinct from the "room audio", we may want metadata to tie
>> the
>> audio and video together.
>>
>> Note that I've phrased the above as *may* because IMO this stuff is all
>> subject to debate. But I would like it to be within the scope of the
>> milestone.
>>
>> That is why I phrased the milestone the way I did.
>>
>> The date for the milestone is another question. The December date is
>> probably a little optimistic, but I'd rather do that than have it be
>> pessimistic and just dawdle. But in the end the milestone dates are
>> really up to the chairs and ADs.
>>
>> 	Thanks,
>> 	Paul
>>
>>> Regards
>>> Andy
>>>
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
>>>> Andrew
>>>> Sent: 23 December 2013 15:24
>>>> To: Paul Kyzivat; siprec@ietf.org
>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
>> kyzivat-
>>>> siprec-conference-use-cases-00
>>>>
>>>> Hi All,
>>>>
>>>> Since nobody posted any new uses cases I went back to our discussion
>> in
>>>> Vancouver and tried to see what we appeared to have consensus on in
>> the
>>>> meeting.
>>>>
>>>>   From that I have formed a proposal for a charter update which is
>> given
>>>> below and also attached (with changes highlighted).
>>>>
>>>> It seems everybody agreed that we need to clarify that SIPREC is
>>>> limited to SIP based systems and that MSRP recording needs to be
>> added.
>>>>
>>>> It also seemed to me that there was no consensus on adding the
>> generic
>>>> case of document/application sharing but if this was limited to
>> being a
>>>> video session in which the content type (RFC 4796) formed part of
>> the
>>>> metadata then probably we would have consensus.  So I included a
>>>> suggested reference to this as a milestone please comment on whether
>>>> this makes sense.
>>>>
>>>> There was a lot of discussion in the Vancouver meeting about
>> defining a
>>>> generic mechanism to record media without the need to come back to
>>>> SIPREC every time new media types or metadata needs to be recorded.
>>>> There has been no use cases submitted or discussion on possible
>>>> mechanism since the meeting so I see no way to progress this at
>>>> present.
>>>>
>>>>
>>>> Please can provide comments and Paul and others who stated they
>> would
>>>> contribute can you confirm that you still intend to do so and that
>> this
>>>> charter proposal is acceptable to you.
>>>>
>>>> Regards
>>>> Andy
>>>>
>>>>
>>>>
>>>> =====================================
>>>> SUGGESTED CHARTER - UPDATE
>>>> =====================================
>>>>
>>>> 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, business analytics, or consumer protection.
>> Recording
>>>> is typically done by sending a copy of the media to the recording
>>>> devices. The working group will determine requirements and produce a
>>>> specification for a protocol that will manage delivery of media, in
>> SIP
>>>> based systems (including audio, video, MSRP instant message
>> sessions)
>>>> from an end-point that originates media, or that has access to it,
>> to a
>>>> recording device. PBX and recording vendors today implement
>>>> proprietary, incompatible mechanisms to facilitate recording. A
>>>> standard protocol will reduce the complexity and cost of providing
>> such
>>>> recording services.
>>>>
>>>> The group will define these issues and rationalize with IETF
>> standards
>>>> and practices. This includes encryption, NAT traversal, operations
>> and
>>>> manageability, SIP-enabled firewalls, authorization, and security.
>>>> The scope explicitly does not include recording any of the extended
>>>> session attributes being defined by the CLUE WG. (These may be
>>>> addressed by a subsequent effort.)
>>>>
>>>> The group will produce:
>>>>
>>>> * Updated Requirements, Use Cases, Architecture draft
>>>>
>>>> * Specification for Session Recording Protocol and Metadata
>>>>
>>>> Milestones
>>>>
>>>> DONE   	Use Cases and Requirements to IESG as Informational RFC
>>>> MAR 2014 	Submit Architecture to IESG as Informational RFC
>>>> JUN 2014 	Submit protocol draft to IESG as Proposed Standard
>> RFC
>>>> AUG 2014 	Submit Metadata model and format to IESG as Proposed
>>>> Standard RFC
>>>> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an
>> informational
>>>> RFC
>>>> ??? 2014 	Conference Recording Use Cases and Requirements to
>> IESG as
>>>> Informational RFC
>>>> ??? 2014 	Conference Recording Architecture to IESG as
>> Informational
>>>> RFC
>>>> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
>>>> Proposed Standard RFC
>>>> ??? 2014 	Protocol and metadata for capturing the content (RFC
>> 4796)
>>>> of the media stream.
>>>>
>>>>
>>>>
>> =======================================================================
>>>> =====================
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Paul
>>>> Kyzivat
>>>>> Sent: 21 November 2013 18:44
>>>>> To: siprec@ietf.org
>>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
>>>> kyzivat-
>>>>> siprec-conference-use-cases-00
>>>>>
>>>>> I still haven't seen anything on this subject.
>>>>> I *thought* there were multiple people in the siprec session in
>>>>> Vancouver that seemed to have other use cases related to media.
>>>>>
>>>>> If so, better speak up, or IIUC we are going to treat the use cases
>>>> we
>>>>> have as bounding the new scope.
>>>>>
>>>>> 	Thanks,
>>>>> 	Paul
>>>>>
>>>>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
>>>>>> One of the action items from the meeting last week was:
>>>>>>
>>>>>>> chairs: use cases to the list in the next couple of weeks.  After
>>>>> that,
>>>>>>> we will decide if we need charter language.  If your use case is
>>>> not
>>>>>>> contributed, it will not be considered in the milestones.
>>>>>>
>>>>>> The above is a little vague about the timing. Two weeks from the
>>>> end
>>>>> of
>>>>>> the meeting would be Friday, November 23. (Hopefully the chairs
>>>> will
>>>>>> clarify this.)
>>>>>>
>>>>>> This is important because there was some desire to tighten up the
>>>>> scope
>>>>>> of the rechartering to encompass only the mentioned use cases.
>>>>>>
>>>>>> I'll be happy to incorporate additional popular use cases even
>>>> before
>>>>>> this draft becomes a wg draft. (But please send text.)
>>>>>>
>>>>>> While the name of the draft is about conferences, the use cases
>>>>> include
>>>>>> additional media support. (Maybe we should rename the draft.) And
>>>> it
>>>>>> seemed that much of the interest was about additional media.
>>>>>>
>>>>>>        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 nobody Thu Mar 20 08:12:37 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55CB31A03FD for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 08:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CZbQSl7Sx3n8 for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 08:12:28 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id 25D1B1A03EF for <siprec@ietf.org>; Thu, 20 Mar 2014 08:12:28 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta08.westchester.pa.mail.comcast.net with comcast id fqWK1n0071uE5Es58rCKsA; Thu, 20 Mar 2014 15:12:19 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta16.westchester.pa.mail.comcast.net with comcast id frCJ1n0143ZTu2S3crCJab; Thu, 20 Mar 2014 15:12:19 +0000
Message-ID: <532B0552.2090907@alum.mit.edu>
Date: Thu, 20 Mar 2014 11:12:18 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Hutton, Andrew" <andrew.hutton@unify.com>
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net> <532313E8.2070904@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395328339; bh=YuWRj8BmPlKX2e0zGBkUKAucz+f6Josb66owecz4f6w=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ZTO/v3TsmC9RjXLM/5F4CXCBn28Sz26kM/YIkKn6SnhwbuGkMMmKavUDzGrQYzgVB HC2W6nccMVSYtCzetv+V0RucRqH9Kx8cXYCNOAl+MZXoLE72e+8aNnQmf4bWYRykdz soyfWRXSiLBhF7iBazWuUMzX6uccXSO26ZsQoYi7cwfIdRRuZM6fIhFTaJz3siJVvL Uh0sngoi/QuqWipnh5lurD1DqRJhyFwdUwomLs16HVw4nG9YY3G4mXi/MBx3jMpDII n4Jjo4ZL1+FXT/lmopixCYhQeaGLy0ZE+Hqsq2uVIVcYJs+ydgV3NR8z8/lpCOcI3O JrYd+bAWG4Oqw==
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/vLoK1POGCdsm1xU-Go_NuIcXu3k
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 20 Mar 2014 15:12:30 -0000

On 3/20/14 5:13 AM, Hutton, Andrew wrote:
> Paul,
>
> The feedback we had during the IETF88 (Vancouver) meeting was that we could not extend SIPREC to generically cover "document & application" sharing as there is no standard to base this on.
>
> Can you suggest a milestone that is more precise that we can get consensus on?

Does the following work for you?

   Protocol and metadata for using RTP media to record the sharing
   of applications, documents and screens.

	Thanks,
	Paul

> Andy
>
>
>
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>> Sent: 14 March 2014 14:36
>> To: Hutton, Andrew; siprec@ietf.org
>> Subject: Re: SIPREC Milestone Update.
>>
>> Andy,
>>
>> On 3/13/14 2:49 PM, Hutton, Andrew wrote:
>>> During the IETF89 SIPREC meeting a discrepancy was identified between
>> my slides showing the proposed new milestones and Paul's slides.
>>>
>>> The chairs slides stated the following milestone:
>>>
>>> "??? 2014 	Protocol and metadata for capturing the content (RFC
>> 4796) of the media stream".
>>>
>>> Whilst Paul's conference recording slides stated
>>>
>>> "Dec 2014	Protocol and metadata for recording of document &
>> application sharing to IESG as Proposed Standard RFC"
>>>
>>> I posted this suggested change to the list as can be seen in the
>> message below and received no comments. The rational for the suggestion
>> is also given in the text below but is basically that we did not have
>> consensus for recording of document and application sharing just for
>> video with reference to the content.
>>>
>>> Please give feedback as to whether the milestone with reference to
>> RFC 4796 makes sense.
>>
>> IMO limiting this to RFC 4796 is too narrow for the milestone. It may
>> turn out that 4796 is *part* of the mechanism, but I certainly don't
>> want to be limited to that. While it needs discussion, I have in mind
>> to
>> capture additional metadata, such as:
>> - the distinction between document, application, and screen sharing
>> - the name of the document or application
>>
>> These won't always be available, but if they are they would be useful
>> to
>> record.
>>
>> Also, while the intent is to capture presentations using video (and
>> perhaps audio) media streams, we *may* also want to say something about
>> *how* this is done.
>>
>> And, if the presentation media includes audio as well as video, and the
>> audio is distinct from the "room audio", we may want metadata to tie
>> the
>> audio and video together.
>>
>> Note that I've phrased the above as *may* because IMO this stuff is all
>> subject to debate. But I would like it to be within the scope of the
>> milestone.
>>
>> That is why I phrased the milestone the way I did.
>>
>> The date for the milestone is another question. The December date is
>> probably a little optimistic, but I'd rather do that than have it be
>> pessimistic and just dawdle. But in the end the milestone dates are
>> really up to the chairs and ADs.
>>
>> 	Thanks,
>> 	Paul
>>
>>> Regards
>>> Andy
>>>
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
>>>> Andrew
>>>> Sent: 23 December 2013 15:24
>>>> To: Paul Kyzivat; siprec@ietf.org
>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
>> kyzivat-
>>>> siprec-conference-use-cases-00
>>>>
>>>> Hi All,
>>>>
>>>> Since nobody posted any new uses cases I went back to our discussion
>> in
>>>> Vancouver and tried to see what we appeared to have consensus on in
>> the
>>>> meeting.
>>>>
>>>>   From that I have formed a proposal for a charter update which is
>> given
>>>> below and also attached (with changes highlighted).
>>>>
>>>> It seems everybody agreed that we need to clarify that SIPREC is
>>>> limited to SIP based systems and that MSRP recording needs to be
>> added.
>>>>
>>>> It also seemed to me that there was no consensus on adding the
>> generic
>>>> case of document/application sharing but if this was limited to
>> being a
>>>> video session in which the content type (RFC 4796) formed part of
>> the
>>>> metadata then probably we would have consensus.  So I included a
>>>> suggested reference to this as a milestone please comment on whether
>>>> this makes sense.
>>>>
>>>> There was a lot of discussion in the Vancouver meeting about
>> defining a
>>>> generic mechanism to record media without the need to come back to
>>>> SIPREC every time new media types or metadata needs to be recorded.
>>>> There has been no use cases submitted or discussion on possible
>>>> mechanism since the meeting so I see no way to progress this at
>>>> present.
>>>>
>>>>
>>>> Please can provide comments and Paul and others who stated they
>> would
>>>> contribute can you confirm that you still intend to do so and that
>> this
>>>> charter proposal is acceptable to you.
>>>>
>>>> Regards
>>>> Andy
>>>>
>>>>
>>>>
>>>> =====================================
>>>> SUGGESTED CHARTER - UPDATE
>>>> =====================================
>>>>
>>>> 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, business analytics, or consumer protection.
>> Recording
>>>> is typically done by sending a copy of the media to the recording
>>>> devices. The working group will determine requirements and produce a
>>>> specification for a protocol that will manage delivery of media, in
>> SIP
>>>> based systems (including audio, video, MSRP instant message
>> sessions)
>>>> from an end-point that originates media, or that has access to it,
>> to a
>>>> recording device. PBX and recording vendors today implement
>>>> proprietary, incompatible mechanisms to facilitate recording. A
>>>> standard protocol will reduce the complexity and cost of providing
>> such
>>>> recording services.
>>>>
>>>> The group will define these issues and rationalize with IETF
>> standards
>>>> and practices. This includes encryption, NAT traversal, operations
>> and
>>>> manageability, SIP-enabled firewalls, authorization, and security.
>>>> The scope explicitly does not include recording any of the extended
>>>> session attributes being defined by the CLUE WG. (These may be
>>>> addressed by a subsequent effort.)
>>>>
>>>> The group will produce:
>>>>
>>>> * Updated Requirements, Use Cases, Architecture draft
>>>>
>>>> * Specification for Session Recording Protocol and Metadata
>>>>
>>>> Milestones
>>>>
>>>> DONE   	Use Cases and Requirements to IESG as Informational RFC
>>>> MAR 2014 	Submit Architecture to IESG as Informational RFC
>>>> JUN 2014 	Submit protocol draft to IESG as Proposed Standard
>> RFC
>>>> AUG 2014 	Submit Metadata model and format to IESG as Proposed
>>>> Standard RFC
>>>> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an
>> informational
>>>> RFC
>>>> ??? 2014 	Conference Recording Use Cases and Requirements to
>> IESG as
>>>> Informational RFC
>>>> ??? 2014 	Conference Recording Architecture to IESG as
>> Informational
>>>> RFC
>>>> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
>>>> Proposed Standard RFC
>>>> ??? 2014 	Protocol and metadata for capturing the content (RFC
>> 4796)
>>>> of the media stream.
>>>>
>>>>
>>>>
>> =======================================================================
>>>> =====================
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Paul
>>>> Kyzivat
>>>>> Sent: 21 November 2013 18:44
>>>>> To: siprec@ietf.org
>>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
>>>> kyzivat-
>>>>> siprec-conference-use-cases-00
>>>>>
>>>>> I still haven't seen anything on this subject.
>>>>> I *thought* there were multiple people in the siprec session in
>>>>> Vancouver that seemed to have other use cases related to media.
>>>>>
>>>>> If so, better speak up, or IIUC we are going to treat the use cases
>>>> we
>>>>> have as bounding the new scope.
>>>>>
>>>>> 	Thanks,
>>>>> 	Paul
>>>>>
>>>>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
>>>>>> One of the action items from the meeting last week was:
>>>>>>
>>>>>>> chairs: use cases to the list in the next couple of weeks.  After
>>>>> that,
>>>>>>> we will decide if we need charter language.  If your use case is
>>>> not
>>>>>>> contributed, it will not be considered in the milestones.
>>>>>>
>>>>>> The above is a little vague about the timing. Two weeks from the
>>>> end
>>>>> of
>>>>>> the meeting would be Friday, November 23. (Hopefully the chairs
>>>> will
>>>>>> clarify this.)
>>>>>>
>>>>>> This is important because there was some desire to tighten up the
>>>>> scope
>>>>>> of the rechartering to encompass only the mentioned use cases.
>>>>>>
>>>>>> I'll be happy to incorporate additional popular use cases even
>>>> before
>>>>>> this draft becomes a wg draft. (But please send text.)
>>>>>>
>>>>>> While the name of the draft is about conferences, the use cases
>>>>> include
>>>>>> additional media support. (Maybe we should rename the draft.) And
>>>> it
>>>>>> seemed that much of the interest was about additional media.
>>>>>>
>>>>>>        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 nobody Thu Mar 20 10:39:05 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3B5E1A07F6 for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 10:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ulHb8nGp0O2f for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 10:38:59 -0700 (PDT)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id A95251A090E for <siprec@ietf.org>; Thu, 20 Mar 2014 10:38:58 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id 0F8C61EB8430; Thu, 20 Mar 2014 18:38:49 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.208]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0174.001; Thu, 20 Mar 2014 18:38:48 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: SIPREC Milestone Update.
Thread-Index: AQHPPuzxMCDLaWKnsESlQX1WYgfyVprglu4AgAki16CAAFUuAIAAOKIA
Date: Thu, 20 Mar 2014 17:38:48 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17D3D460@MCHP04MSX.global-ad.net>
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net> <532313E8.2070904@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net> <532B0552.2090907@alum.mit.edu>
In-Reply-To: <532B0552.2090907@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/wI8k3W7PCIZ_AoTBxg00f-MSwsc
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 20 Mar 2014 17:39:03 -0000

I would like to hear what others in the WG think.

Andy

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> Sent: 20 March 2014 15:12
> To: Hutton, Andrew
> Cc: siprec@ietf.org
> Subject: Re: SIPREC Milestone Update.
>=20
> On 3/20/14 5:13 AM, Hutton, Andrew wrote:
> > Paul,
> >
> > The feedback we had during the IETF88 (Vancouver) meeting was that we
> could not extend SIPREC to generically cover "document & application"
> sharing as there is no standard to base this on.
> >
> > Can you suggest a milestone that is more precise that we can get
> consensus on?
>=20
> Does the following work for you?
>=20
>    Protocol and metadata for using RTP media to record the sharing
>    of applications, documents and screens.
>=20
> 	Thanks,
> 	Paul
>=20
> > Andy
> >
> >
> >
> >> -----Original Message-----
> >> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> >> Sent: 14 March 2014 14:36
> >> To: Hutton, Andrew; siprec@ietf.org
> >> Subject: Re: SIPREC Milestone Update.
> >>
> >> Andy,
> >>
> >> On 3/13/14 2:49 PM, Hutton, Andrew wrote:
> >>> During the IETF89 SIPREC meeting a discrepancy was identified
> between
> >> my slides showing the proposed new milestones and Paul's slides.
> >>>
> >>> The chairs slides stated the following milestone:
> >>>
> >>> "??? 2014 	Protocol and metadata for capturing the content (RFC
> >> 4796) of the media stream".
> >>>
> >>> Whilst Paul's conference recording slides stated
> >>>
> >>> "Dec 2014	Protocol and metadata for recording of document &
> >> application sharing to IESG as Proposed Standard RFC"
> >>>
> >>> I posted this suggested change to the list as can be seen in the
> >> message below and received no comments. The rational for the
> suggestion
> >> is also given in the text below but is basically that we did not
> have
> >> consensus for recording of document and application sharing just for
> >> video with reference to the content.
> >>>
> >>> Please give feedback as to whether the milestone with reference to
> >> RFC 4796 makes sense.
> >>
> >> IMO limiting this to RFC 4796 is too narrow for the milestone. It
> may
> >> turn out that 4796 is *part* of the mechanism, but I certainly don't
> >> want to be limited to that. While it needs discussion, I have in
> mind
> >> to
> >> capture additional metadata, such as:
> >> - the distinction between document, application, and screen sharing
> >> - the name of the document or application
> >>
> >> These won't always be available, but if they are they would be
> useful
> >> to
> >> record.
> >>
> >> Also, while the intent is to capture presentations using video (and
> >> perhaps audio) media streams, we *may* also want to say something
> about
> >> *how* this is done.
> >>
> >> And, if the presentation media includes audio as well as video, and
> the
> >> audio is distinct from the "room audio", we may want metadata to tie
> >> the
> >> audio and video together.
> >>
> >> Note that I've phrased the above as *may* because IMO this stuff is
> all
> >> subject to debate. But I would like it to be within the scope of the
> >> milestone.
> >>
> >> That is why I phrased the milestone the way I did.
> >>
> >> The date for the milestone is another question. The December date is
> >> probably a little optimistic, but I'd rather do that than have it be
> >> pessimistic and just dawdle. But in the end the milestone dates are
> >> really up to the chairs and ADs.
> >>
> >> 	Thanks,
> >> 	Paul
> >>
> >>> Regards
> >>> Andy
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
> >>>> Andrew
> >>>> Sent: 23 December 2013 15:24
> >>>> To: Paul Kyzivat; siprec@ietf.org
> >>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
> >> kyzivat-
> >>>> siprec-conference-use-cases-00
> >>>>
> >>>> Hi All,
> >>>>
> >>>> Since nobody posted any new uses cases I went back to our
> discussion
> >> in
> >>>> Vancouver and tried to see what we appeared to have consensus on
> in
> >> the
> >>>> meeting.
> >>>>
> >>>>   From that I have formed a proposal for a charter update which is
> >> given
> >>>> below and also attached (with changes highlighted).
> >>>>
> >>>> It seems everybody agreed that we need to clarify that SIPREC is
> >>>> limited to SIP based systems and that MSRP recording needs to be
> >> added.
> >>>>
> >>>> It also seemed to me that there was no consensus on adding the
> >> generic
> >>>> case of document/application sharing but if this was limited to
> >> being a
> >>>> video session in which the content type (RFC 4796) formed part of
> >> the
> >>>> metadata then probably we would have consensus.  So I included a
> >>>> suggested reference to this as a milestone please comment on
> whether
> >>>> this makes sense.
> >>>>
> >>>> There was a lot of discussion in the Vancouver meeting about
> >> defining a
> >>>> generic mechanism to record media without the need to come back to
> >>>> SIPREC every time new media types or metadata needs to be
> recorded.
> >>>> There has been no use cases submitted or discussion on possible
> >>>> mechanism since the meeting so I see no way to progress this at
> >>>> present.
> >>>>
> >>>>
> >>>> Please can provide comments and Paul and others who stated they
> >> would
> >>>> contribute can you confirm that you still intend to do so and that
> >> this
> >>>> charter proposal is acceptable to you.
> >>>>
> >>>> Regards
> >>>> Andy
> >>>>
> >>>>
> >>>>
> >>>> =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
> >>>> SUGGESTED CHARTER - UPDATE
> >>>> =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
> >>>>
> >>>> 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, business analytics, or consumer protection.
> >> Recording
> >>>> is typically done by sending a copy of the media to the recording
> >>>> devices. The working group will determine requirements and produce
> a
> >>>> specification for a protocol that will manage delivery of media,
> in
> >> SIP
> >>>> based systems (including audio, video, MSRP instant message
> >> sessions)
> >>>> from an end-point that originates media, or that has access to it,
> >> to a
> >>>> recording device. PBX and recording vendors today implement
> >>>> proprietary, incompatible mechanisms to facilitate recording. A
> >>>> standard protocol will reduce the complexity and cost of providing
> >> such
> >>>> recording services.
> >>>>
> >>>> The group will define these issues and rationalize with IETF
> >> standards
> >>>> and practices. This includes encryption, NAT traversal, operations
> >> and
> >>>> manageability, SIP-enabled firewalls, authorization, and security.
> >>>> The scope explicitly does not include recording any of the
> extended
> >>>> session attributes being defined by the CLUE WG. (These may be
> >>>> addressed by a subsequent effort.)
> >>>>
> >>>> The group will produce:
> >>>>
> >>>> * Updated Requirements, Use Cases, Architecture draft
> >>>>
> >>>> * Specification for Session Recording Protocol and Metadata
> >>>>
> >>>> Milestones
> >>>>
> >>>> DONE   	Use Cases and Requirements to IESG as Informational
> RFC
> >>>> MAR 2014 	Submit Architecture to IESG as Informational RFC
> >>>> JUN 2014 	Submit protocol draft to IESG as Proposed Standard
> >> RFC
> >>>> AUG 2014 	Submit Metadata model and format to IESG as Proposed
> >>>> Standard RFC
> >>>> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an
> >> informational
> >>>> RFC
> >>>> ??? 2014 	Conference Recording Use Cases and Requirements to
> >> IESG as
> >>>> Informational RFC
> >>>> ??? 2014 	Conference Recording Architecture to IESG as
> >> Informational
> >>>> RFC
> >>>> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
> >>>> Proposed Standard RFC
> >>>> ??? 2014 	Protocol and metadata for capturing the content (RFC
> >> 4796)
> >>>> of the media stream.
> >>>>
> >>>>
> >>>>
> >>
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>>>
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Paul
> >>>> Kyzivat
> >>>>> Sent: 21 November 2013 18:44
> >>>>> To: siprec@ietf.org
> >>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
> >>>> kyzivat-
> >>>>> siprec-conference-use-cases-00
> >>>>>
> >>>>> I still haven't seen anything on this subject.
> >>>>> I *thought* there were multiple people in the siprec session in
> >>>>> Vancouver that seemed to have other use cases related to media.
> >>>>>
> >>>>> If so, better speak up, or IIUC we are going to treat the use
> cases
> >>>> we
> >>>>> have as bounding the new scope.
> >>>>>
> >>>>> 	Thanks,
> >>>>> 	Paul
> >>>>>
> >>>>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
> >>>>>> One of the action items from the meeting last week was:
> >>>>>>
> >>>>>>> chairs: use cases to the list in the next couple of weeks.
> After
> >>>>> that,
> >>>>>>> we will decide if we need charter language.  If your use case
> is
> >>>> not
> >>>>>>> contributed, it will not be considered in the milestones.
> >>>>>>
> >>>>>> The above is a little vague about the timing. Two weeks from the
> >>>> end
> >>>>> of
> >>>>>> the meeting would be Friday, November 23. (Hopefully the chairs
> >>>> will
> >>>>>> clarify this.)
> >>>>>>
> >>>>>> This is important because there was some desire to tighten up
> the
> >>>>> scope
> >>>>>> of the rechartering to encompass only the mentioned use cases.
> >>>>>>
> >>>>>> I'll be happy to incorporate additional popular use cases even
> >>>> before
> >>>>>> this draft becomes a wg draft. (But please send text.)
> >>>>>>
> >>>>>> While the name of the draft is about conferences, the use cases
> >>>>> include
> >>>>>> additional media support. (Maybe we should rename the draft.)
> And
> >>>> it
> >>>>>> seemed that much of the interest was about additional media.
> >>>>>>
> >>>>>>        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 nobody Thu Mar 20 13:49:47 2014
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64A951A07F8 for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 13:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e0sXlwBQOtZA for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 13:49:44 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 890F11A07EF for <siprec@ietf.org>; Thu, 20 Mar 2014 13:49:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2868; q=dns/txt; s=iport; t=1395348575; x=1396558175; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=VvhCPpm7MWWaBMgJi9MNaknGw6BzVpQdWc0twe/Ddn0=; b=ejmrKWhSSFaCy5/FqMWelTJUhCwVbBppZsUOpr2BTlf0bcAlhb789Gn/ WrMlqErLh22MFfJOhTRpLH225sYfSHxlAZ3EK25qG6M+y8DEKgWgltSST EjXYMmi51zLi6+a4ocQkdMmXXq/XIYlQ54GnJevD+0E0IgpXqxa4/IZtd E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao4FAKVTK1OtJXG9/2dsb2JhbABZgwY7UQa7HYZhUYEaFnSCJgEBBAEBATc0GwIBCDYQJwslAgQTCYdvAQgFz1wXjhEDAQFRBYQ4BJhHgTKQfoMtgXI5
X-IronPort-AV: E=Sophos;i="4.97,697,1389744000"; d="scan'208";a="29098993"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-6.cisco.com with ESMTP; 20 Mar 2014 20:49:34 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id s2KKnYxi010728 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <siprec@ietf.org>; Thu, 20 Mar 2014 20:49:34 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.148]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0123.003; Thu, 20 Mar 2014 15:49:34 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] I-D Action: draft-ietf-siprec-protocol-12.txt
Thread-Index: AQHPKdQYgU/jKVfo0E+K4BQVWXtFX5q1NLsAgDVR4IA=
Date: Thu, 20 Mar 2014 20:49:33 +0000
Message-ID: <CF50A1EA.233D4%eckelcu@cisco.com>
References: <20140214222751.19319.38020.idtracker@ietfa.amsl.com> <CF23D8D0.1F03A%eckelcu@cisco.com>
In-Reply-To: <CF23D8D0.1F03A%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [171.68.20.16]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E3D8892FFC42BB41BEEB232B4E7FACED@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/snC8y-4nuhCNJkZesTqLexg6dGs
Subject: Re: [siprec] I-D Action: draft-ietf-siprec-protocol-12.txt
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 20 Mar 2014 20:49:46 -0000

Following up on our session in London, while comments on the entire draft
are encourage, the biggest changes were to the metadata section:
http://tools.ietf.org/html/draft-ietf-siprec-protocol-12#section-9


If nothing else, comments on this specific section would be greatly
appreciated.

Cheers,
Charles


On 2/14/14, 2:34 PM, "Charles Eckel (eckelcu)" <eckelcu@cisco.com> wrote:

>This update to the protocol draft incorporate the changes captured in the
>following two threads:
>
>IETF 88 comments:
>http://www.ietf.org/mail-archive/web/siprec/current/msg03829.html
>
>Metadata sending frequency:
>http://www.ietf.org/mail-archive/web/siprec/current/msg03910.html
>
>There are a couple other threads that have not yet reached a conclusion
>that I felt comfortable capturing in the draft.
>
>Please review and share your comments.
>
>Cheers,
>Charles
>
>On 2/14/14 2:27 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>wrote:
>
>>
>>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           : Session Recording Protocol
>>        Authors         : Leon Portman
>>                          Henry Lum
>>                          Charles Eckel
>>                          Alan Johnston
>>                          Andrew Hutton
>>	Filename        : draft-ietf-siprec-protocol-12.txt
>>	Pages           : 43
>>	Date            : 2014-02-14
>>
>>Abstract:
>>   This document specifies the use of the Session Initiation Protocol
>>   (SIP), the Session Description Protocol (SDP), and the Real Time
>>   Protocol (RTP) for delivering real-time media and metadata from a
>>   Communication Session (CS) to a recording device.  The Session
>>   Recording Protocol specifies the use of SIP, SDP, and RTP to
>>   establish a Recording Session (RS) between the Session Recording
>>   Client (SRC), which is on the path of the CS, and a Session Recording
>>   Server (SRS) at the recording device.
>>
>>
>>The IETF datatracker status page for this draft is:
>>https://datatracker.ietf.org/doc/draft-ietf-siprec-protocol/
>>
>>There's also a htmlized version available at:
>>http://tools.ietf.org/html/draft-ietf-siprec-protocol-12
>>
>>A diff from the previous version is available at:
>>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-siprec-protocol-12
>>
>>
>>Please note that it may take a couple of minutes from the time of
>>submission
>>until the htmlized version and diff are available at tools.ietf.org.
>>
>>Internet-Drafts are also available by anonymous FTP at:
>>ftp://ftp.ietf.org/internet-drafts/
>>
>>_______________________________________________
>>siprec mailing list
>>siprec@ietf.org
>>https://www.ietf.org/mailman/listinfo/siprec
>


From nobody Thu Mar 20 14:04:38 2014
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A8651A0753 for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 14:04:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XVD9yXC2AS7 for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 14:04:33 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id E7F2D1A042C for <siprec@ietf.org>; Thu, 20 Mar 2014 14:04:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1922; q=dns/txt; s=iport; t=1395349464; x=1396559064; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=CcUeF5zaU8fnh+EwKg5jnJddwuoMjIbv3Vc3lX9JxZ0=; b=UFRbL7pIc2rJdpduLOWQpJAgvF5ER2CGpYWQ/cZdhuMV4mTIwbs2NrzQ 0FP/FOd6AHaCZMDmOWAjG1r6IZaYxN9qvLs99qW/eaeY6NeozhkDiq1/p xotjXYGIKMNAWZvwzhtBOh6VINWevzJV5qz6sGzw/a8Q/BdPS9lRaZQB+ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsFACJXK1OtJV2Y/2dsb2JhbABZgwY7V8F+UYEaFnSCLIELAYEAJwQch28BDZ15sWcXjhEDAQFRhD0EiRqPLYEyiTWHSYMtgXI5
X-IronPort-AV: E=Sophos;i="4.97,697,1389744000"; d="scan'208";a="29102365"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-6.cisco.com with ESMTP; 20 Mar 2014 21:04:23 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s2KL4NDY032583 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <siprec@ietf.org>; Thu, 20 Mar 2014 21:04:23 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.148]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Thu, 20 Mar 2014 16:04:23 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: FIR vs. SIP INFO
Thread-Index: AQHPRH/3ygx87Q2NFUiIJ4Cd64NY0w==
Date: Thu, 20 Mar 2014 21:04:22 +0000
Message-ID: <CF50A5E6.2341C%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [171.68.20.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <9FA6C8DD63AF8945938AA0BCEF363C5E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/jQgwX__v1124Q6EIDWjedi5cP0M
Subject: [siprec] FIR vs. SIP INFO
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 20 Mar 2014 21:04:35 -0000

To the best of my knowledge, this is the last open item in the protocol
draft. Here is the info from the slide presented at IETF 89 in London:

FIR and SIP INFO requirements in SRC and/or SRS
------------------------
Section 8.1.7.1.1 SIP INFO for FIR
=A8"XML Schema for Media Control=B2 [RFC5168
<http://tools.ietf.org/html/rfc5168>] defines an Extensible Markup
Language (XML) Schema for video fast update. Implementations are
discouraged from using the method described except for backward
compatibility purposes. Implementations SHOULD use FIR messages instead.

NENA ICE-8 event feedback, do we need to say more? Options:
1.SRC MUST support both and provide interworking to what SRS supports (and
an UA that does not support both MUST NOT use SIPREC?)
2.SRS MUST support both (and allow SRC to support both simultaneously? And
how do you negotiation that ?)
3.Provide recommendations and leave as quality of implementation decision
(and live with interoperability issues?)
-----------------------------

Discussion in room (from minutes:
http://www.ietf.org/mail-archive/web/siprec/current/msg03934.html)
- Paul K - no brainer, SRS is the powerful box - that is the place to put
requirements - 2 is preferable to 1 - 2 vs. 3, I'm not sure, kind of
inclined for 2 but not sure
- Chair: definitive is best for implementation
- Charles: option 3 is my suggestion (as the draft is), but could live
with option 2 - would appreciate some help with the text - need to think
about use cases - if a UA is capable of dealing with both, it can simplify
for the SRS, but depends on capabilities of the SRC and SRS - if we can do
better that is great
- Chair: let's have more list discussion because missing people - but in
favour of documenting one and generally in favour of having the server do
the work - tentatively think going in the direction of option 2

Thoughts?

Cheers,
Charles


From nobody Thu Mar 20 15:50:44 2014
Return-Path: <partha@parthasarathi.co.in>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB1BC1A092E for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 15:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bh4hPYKR5aFK for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 15:50:38 -0700 (PDT)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.29]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6111A0938 for <siprec@ietf.org>; Thu, 20 Mar 2014 15:50:36 -0700 (PDT)
Received: from userPC (unknown [122.167.81.185]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id 9A57614E81B7; Thu, 20 Mar 2014 22:50:23 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1395355827; bh=a2qfsA3n73OFeslzsBMBNV7gbuwnCCjyHnsf4Y5jy50=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=RnpyTu9MoTm10BLK4xjc43niXyGEBrjpeMe2rjn0GWnPPisp4Z2x71gSz3DCO5UT9 lenFxWJYBe96jUbYpHXZAg/zdMy6BiYrORli4Wznct9BZB6eANOdrtGqqYXdkqxX0G 7bbuh59svIeWTbCy9L63HfPiP9P9nxsXKuS+8fQY=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Hutton, Andrew'" <andrew.hutton@unify.com>, "'Paul Kyzivat'" <pkyzivat@alum.mit.edu>, <siprec@ietf.org>
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net> <532313E8.2070904@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net> <532B0552.2090907@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3D460@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17D3D460@MCHP04MSX.global-ad.net>
Date: Fri, 21 Mar 2014 04:19:55 +0530
Message-ID: <00f401cf448e$bb0203f0$31060bd0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHPPuzxMCDLaWKnsESlQX1WYgfyVprglu4AgAki16CAAFUuAIAAOKIAgABKCwA=
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020209.532B70B3.005D, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 172.18.214.93
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/cJR1pLwYxbTIa0USCOxGGL72RBw
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 20 Mar 2014 22:50:42 -0000

Hi Paul & all,

I understand that screen sharing shall be considered as a video stream. I'm
interested in knowing how RTP media is used for application and document
sharing.

Also, I'm interested in knowing whether RFC 5547 (A Session Description
Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer) will be
covered within MSRP recording deliverable or not.  

Thanks
Partha

> -----Original Message-----
> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
> Andrew
> Sent: Thursday, March 20, 2014 11:09 PM
> To: Paul Kyzivat; siprec@ietf.org
> Subject: Re: [siprec] SIPREC Milestone Update.
> 
> I would like to hear what others in the WG think.
> 
> Andy
> 
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> > Sent: 20 March 2014 15:12
> > To: Hutton, Andrew
> > Cc: siprec@ietf.org
> > Subject: Re: SIPREC Milestone Update.
> >
> > On 3/20/14 5:13 AM, Hutton, Andrew wrote:
> > > Paul,
> > >
> > > The feedback we had during the IETF88 (Vancouver) meeting was that
> we
> > could not extend SIPREC to generically cover "document & application"
> > sharing as there is no standard to base this on.
> > >
> > > Can you suggest a milestone that is more precise that we can get
> > consensus on?
> >
> > Does the following work for you?
> >
> >    Protocol and metadata for using RTP media to record the sharing
> >    of applications, documents and screens.
> >
> > 	Thanks,
> > 	Paul
> >
> > > Andy
> > >
> > >
> > >
> > >> -----Original Message-----
> > >> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> > >> Sent: 14 March 2014 14:36
> > >> To: Hutton, Andrew; siprec@ietf.org
> > >> Subject: Re: SIPREC Milestone Update.
> > >>
> > >> Andy,
> > >>
> > >> On 3/13/14 2:49 PM, Hutton, Andrew wrote:
> > >>> During the IETF89 SIPREC meeting a discrepancy was identified
> > between
> > >> my slides showing the proposed new milestones and Paul's slides.
> > >>>
> > >>> The chairs slides stated the following milestone:
> > >>>
> > >>> "??? 2014 	Protocol and metadata for capturing the content (RFC
> > >> 4796) of the media stream".
> > >>>
> > >>> Whilst Paul's conference recording slides stated
> > >>>
> > >>> "Dec 2014	Protocol and metadata for recording of document &
> > >> application sharing to IESG as Proposed Standard RFC"
> > >>>
> > >>> I posted this suggested change to the list as can be seen in the
> > >> message below and received no comments. The rational for the
> > suggestion
> > >> is also given in the text below but is basically that we did not
> > have
> > >> consensus for recording of document and application sharing just
> for
> > >> video with reference to the content.
> > >>>
> > >>> Please give feedback as to whether the milestone with reference
> to
> > >> RFC 4796 makes sense.
> > >>
> > >> IMO limiting this to RFC 4796 is too narrow for the milestone. It
> > may
> > >> turn out that 4796 is *part* of the mechanism, but I certainly
> don't
> > >> want to be limited to that. While it needs discussion, I have in
> > mind
> > >> to
> > >> capture additional metadata, such as:
> > >> - the distinction between document, application, and screen
> sharing
> > >> - the name of the document or application
> > >>
> > >> These won't always be available, but if they are they would be
> > useful
> > >> to
> > >> record.
> > >>
> > >> Also, while the intent is to capture presentations using video
> (and
> > >> perhaps audio) media streams, we *may* also want to say something
> > about
> > >> *how* this is done.
> > >>
> > >> And, if the presentation media includes audio as well as video,
> and
> > the
> > >> audio is distinct from the "room audio", we may want metadata to
> tie
> > >> the
> > >> audio and video together.
> > >>
> > >> Note that I've phrased the above as *may* because IMO this stuff
> is
> > all
> > >> subject to debate. But I would like it to be within the scope of
> the
> > >> milestone.
> > >>
> > >> That is why I phrased the milestone the way I did.
> > >>
> > >> The date for the milestone is another question. The December date
> is
> > >> probably a little optimistic, but I'd rather do that than have it
> be
> > >> pessimistic and just dawdle. But in the end the milestone dates
> are
> > >> really up to the chairs and ADs.
> > >>
> > >> 	Thanks,
> > >> 	Paul
> > >>
> > >>> Regards
> > >>> Andy
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of
> Hutton,
> > >>>> Andrew
> > >>>> Sent: 23 December 2013 15:24
> > >>>> To: Paul Kyzivat; siprec@ietf.org
> > >>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
> > >> kyzivat-
> > >>>> siprec-conference-use-cases-00
> > >>>>
> > >>>> Hi All,
> > >>>>
> > >>>> Since nobody posted any new uses cases I went back to our
> > discussion
> > >> in
> > >>>> Vancouver and tried to see what we appeared to have consensus on
> > in
> > >> the
> > >>>> meeting.
> > >>>>
> > >>>>   From that I have formed a proposal for a charter update which
> is
> > >> given
> > >>>> below and also attached (with changes highlighted).
> > >>>>
> > >>>> It seems everybody agreed that we need to clarify that SIPREC is
> > >>>> limited to SIP based systems and that MSRP recording needs to be
> > >> added.
> > >>>>
> > >>>> It also seemed to me that there was no consensus on adding the
> > >> generic
> > >>>> case of document/application sharing but if this was limited to
> > >> being a
> > >>>> video session in which the content type (RFC 4796) formed part
> of
> > >> the
> > >>>> metadata then probably we would have consensus.  So I included a
> > >>>> suggested reference to this as a milestone please comment on
> > whether
> > >>>> this makes sense.
> > >>>>
> > >>>> There was a lot of discussion in the Vancouver meeting about
> > >> defining a
> > >>>> generic mechanism to record media without the need to come back
> to
> > >>>> SIPREC every time new media types or metadata needs to be
> > recorded.
> > >>>> There has been no use cases submitted or discussion on possible
> > >>>> mechanism since the meeting so I see no way to progress this at
> > >>>> present.
> > >>>>
> > >>>>
> > >>>> Please can provide comments and Paul and others who stated they
> > >> would
> > >>>> contribute can you confirm that you still intend to do so and
> that
> > >> this
> > >>>> charter proposal is acceptable to you.
> > >>>>
> > >>>> Regards
> > >>>> Andy
> > >>>>
> > >>>>
> > >>>>
> > >>>> =====================================
> > >>>> SUGGESTED CHARTER - UPDATE
> > >>>> =====================================
> > >>>>
> > >>>> 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, business analytics, or consumer protection.
> > >> Recording
> > >>>> is typically done by sending a copy of the media to the
> recording
> > >>>> devices. The working group will determine requirements and
> produce
> > a
> > >>>> specification for a protocol that will manage delivery of media,
> > in
> > >> SIP
> > >>>> based systems (including audio, video, MSRP instant message
> > >> sessions)
> > >>>> from an end-point that originates media, or that has access to
> it,
> > >> to a
> > >>>> recording device. PBX and recording vendors today implement
> > >>>> proprietary, incompatible mechanisms to facilitate recording. A
> > >>>> standard protocol will reduce the complexity and cost of
> providing
> > >> such
> > >>>> recording services.
> > >>>>
> > >>>> The group will define these issues and rationalize with IETF
> > >> standards
> > >>>> and practices. This includes encryption, NAT traversal,
> operations
> > >> and
> > >>>> manageability, SIP-enabled firewalls, authorization, and
> security.
> > >>>> The scope explicitly does not include recording any of the
> > extended
> > >>>> session attributes being defined by the CLUE WG. (These may be
> > >>>> addressed by a subsequent effort.)
> > >>>>
> > >>>> The group will produce:
> > >>>>
> > >>>> * Updated Requirements, Use Cases, Architecture draft
> > >>>>
> > >>>> * Specification for Session Recording Protocol and Metadata
> > >>>>
> > >>>> Milestones
> > >>>>
> > >>>> DONE   	Use Cases and Requirements to IESG as Informational
> > RFC
> > >>>> MAR 2014 	Submit Architecture to IESG as Informational RFC
> > >>>> JUN 2014 	Submit protocol draft to IESG as Proposed Standard
> > >> RFC
> > >>>> AUG 2014 	Submit Metadata model and format to IESG as Proposed
> > >>>> Standard RFC
> > >>>> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an
> > >> informational
> > >>>> RFC
> > >>>> ??? 2014 	Conference Recording Use Cases and Requirements to
> > >> IESG as
> > >>>> Informational RFC
> > >>>> ??? 2014 	Conference Recording Architecture to IESG as
> > >> Informational
> > >>>> RFC
> > >>>> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
> > >>>> Proposed Standard RFC
> > >>>> ??? 2014 	Protocol and metadata for capturing the content (RFC
> > >> 4796)
> > >>>> of the media stream.
> > >>>>
> > >>>>
> > >>>>
> > >>
> >
> =======================================================================
> > >>>> =====================
> > >>>>
> > >>>>
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Paul
> > >>>> Kyzivat
> > >>>>> Sent: 21 November 2013 18:44
> > >>>>> To: siprec@ietf.org
> > >>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
> > >>>> kyzivat-
> > >>>>> siprec-conference-use-cases-00
> > >>>>>
> > >>>>> I still haven't seen anything on this subject.
> > >>>>> I *thought* there were multiple people in the siprec session in
> > >>>>> Vancouver that seemed to have other use cases related to media.
> > >>>>>
> > >>>>> If so, better speak up, or IIUC we are going to treat the use
> > cases
> > >>>> we
> > >>>>> have as bounding the new scope.
> > >>>>>
> > >>>>> 	Thanks,
> > >>>>> 	Paul
> > >>>>>
> > >>>>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
> > >>>>>> One of the action items from the meeting last week was:
> > >>>>>>
> > >>>>>>> chairs: use cases to the list in the next couple of weeks.
> > After
> > >>>>> that,
> > >>>>>>> we will decide if we need charter language.  If your use case
> > is
> > >>>> not
> > >>>>>>> contributed, it will not be considered in the milestones.
> > >>>>>>
> > >>>>>> The above is a little vague about the timing. Two weeks from
> the
> > >>>> end
> > >>>>> of
> > >>>>>> the meeting would be Friday, November 23. (Hopefully the
> chairs
> > >>>> will
> > >>>>>> clarify this.)
> > >>>>>>
> > >>>>>> This is important because there was some desire to tighten up
> > the
> > >>>>> scope
> > >>>>>> of the rechartering to encompass only the mentioned use cases.
> > >>>>>>
> > >>>>>> I'll be happy to incorporate additional popular use cases even
> > >>>> before
> > >>>>>> this draft becomes a wg draft. (But please send text.)
> > >>>>>>
> > >>>>>> While the name of the draft is about conferences, the use
> cases
> > >>>>> include
> > >>>>>> additional media support. (Maybe we should rename the draft.)
> > And
> > >>>> it
> > >>>>>> seemed that much of the interest was about additional media.
> > >>>>>>
> > >>>>>>        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
> > >>>
> > >
> > >
> 
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From nobody Thu Mar 20 20:03:56 2014
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0C941A08D6 for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 20:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.448
X-Spam-Level: 
X-Spam-Status: No, score=-9.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_32=0.6, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8BGM2zkj9bT for <siprec@ietfa.amsl.com>; Thu, 20 Mar 2014 20:03:49 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 4D9391A0883 for <siprec@ietf.org>; Thu, 20 Mar 2014 20:03:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4414; q=dns/txt; s=iport; t=1395371020; x=1396580620; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=NcfzVXzUvK4VFg7VCmDdV4HaxmbTinyf8xVpN35K8kQ=; b=CHAxWoLs05lQ6IkdKtR2ccsYuJlTmWufLKj3R3e/4jrYJKf6Kgw4Bu0d Kl2ngW2ZWOwZ97f6B6Q4ZoTTK8AsPNFUpoAZw3qyNnakGYjqMk5Zxn1OX Nc8Y77P48Phe9UY4dFEJKsl5K/Yf8OnDg7UE+ccG8+mBPkUXKpzhBYfv5 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAKSrK1OtJXHA/2dsb2JhbABZgwY7V4MHuBWGY1EZfBZ0giUBAQEEAQEBMToXBgEIEQMBAgUoBCULHQoEARIJh3ANkQKcDwaiYheBI4xuAwEBXIJjgU8EmEmBMok1h0qDLYFyOQ
X-IronPort-AV: E=Sophos;i="4.97,700,1389744000"; d="scan'208";a="29193827"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by alln-iport-6.cisco.com with ESMTP; 21 Mar 2014 03:03:38 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s2L33c8i014632 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <siprec@ietf.org>; Fri, 21 Mar 2014 03:03:38 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.78]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Thu, 20 Mar 2014 22:03:38 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] FIR vs. SIP INFO
Thread-Index: AQHPRLInie4MPj/tQEKPU85/ePxHyg==
Date: Fri, 21 Mar 2014 03:03:38 +0000
Message-ID: <CF51A68B.84EF2%rmohanr@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [72.163.212.114]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <9605300C959A7F4F93504E3960D118F0@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/xNHTnPAx2eath17lAtJxM-oBqRM
Subject: Re: [siprec] FIR vs. SIP INFO
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 21 Mar 2014 03:03:52 -0000

SSBwcmVmZXIgb3B0aW9uIDIgYXMgbWFuZGF0b3J5IHNpbmNlIFNSUyBpcyB0aGUgb25lIHRoYXQg
ZXZlbnR1YWxseSBsb29rcw0KYXQgdGhlIG1lZGlhIGJlaW5nIHJlY29yZGVkKFJUUCkgYW5kIGlz
IHRoZSBiZXN0IG9uZSB0byBkZWNpZGUgb24gd2hldGhlcg0KdG8gZ2VuZXJhdGUgYSBGSVIgb3Ig
U0lQIElORk8uICBIb3dldmVyIHdlIG1heSBhbHNvIGFsbG93IGEgU1JDIHRvDQpnZW5lcmF0ZSBh
IEZJUi9TSVAgSU5GTy4gU28gSSBwcmVmZXIgdGhhdCB3ZSBjYW4ga2VlcCBNVVNUIGZvciBvcHRp
b24gMg0KYW5kIE1BWSBmb3Igb3B0aW9uIDEuDQoNCkkgaGF2ZSBhIHNsaWdodGx5IGRpZmZlcmVu
dCBxdWVzdGlvbiBvbiB0aGlzIC0NCkRvIHdlIHdhbnQgU1JTKG9yIFNSQykgdG8gYWx3YXlzIGdl
bmVyYXRlIGJvdGggRklSIGFuZCBTSVAgSU5GTyA/IFRoZXJlDQptYXkgYmUgY2FzZXMgd2hlcmUg
ZW5kcG9pbnQgKFVBKSBtYXkgc3VwcG9ydCBvbmUgb3IgYm90aCBvZiB0aGVtLiBJZiBhIFVBDQpz
dXBwb3J0cyBib3RoIG9mIHRoZW0gaXQgbWF5IHJlc3VsdCBpbiBhIGNhc2Ugd2hlcmUgVUEgbWF5
IHJlLXRyYW5zbWl0IElEUg0KZnJhbWUgdHdpY2UgKG9uZSBvbiByZWNlaXB0IG9mIEZJUiBhbmQg
b3RoZXIgb24gb24gcmVjZWlwdCBvZiBTSVAgSU5GTykuDQpUaGlzIGlzIG9rIGluIHByaW5jaXBs
ZSBidXQgbWF5IGxlYWQgdG8gbW9yZSBuZXR3b3JrIGNvbmdlc3Rpb24gZHVlIHRvDQpidXJzdHkg
dHJhZmZpYy4gSXMgdGhpcyBzb21lIHRoaW5nIHdlIHNob3VsZCB3b3JyeSBhYm91dCA/DQoNClBl
cmhhcHMgaWYgdGhlcmUgaXMgYSB3YXkgU1JTL1NSQyBjYW4gZmluZCB3aGF0IG1ldGhvZCB0aGUg
VUEgcHJlZmVycyAoRklSDQpvciBTSVAgSU5GTykgaXQgY2FuIG9ubHkgZ2VuZXJhdGUgdGhhdC4N
Cg0KUmFtDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206ICJDaGFybGVzIEVj
a2VsICAgKGVja2VsY3UpIiA8ZWNrZWxjdUBjaXNjby5jb20+DQpEYXRlOiBGcmlkYXksIDIxIE1h
cmNoIDIwMTQgMjozNCBhbQ0KVG86ICJzaXByZWNAaWV0Zi5vcmciIDxzaXByZWNAaWV0Zi5vcmc+
DQpTdWJqZWN0OiBbc2lwcmVjXSBGSVIgdnMuIFNJUCBJTkZPDQoNCj5UbyB0aGUgYmVzdCBvZiBt
eSBrbm93bGVkZ2UsIHRoaXMgaXMgdGhlIGxhc3Qgb3BlbiBpdGVtIGluIHRoZSBwcm90b2NvbA0K
PmRyYWZ0LiBIZXJlIGlzIHRoZSBpbmZvIGZyb20gdGhlIHNsaWRlIHByZXNlbnRlZCBhdCBJRVRG
IDg5IGluIExvbmRvbjoNCj4NCj5GSVIgYW5kIFNJUCBJTkZPIHJlcXVpcmVtZW50cyBpbiBTUkMg
YW5kL29yIFNSUw0KPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPlNlY3Rpb24gOC4xLjcuMS4x
IFNJUCBJTkZPIGZvciBGSVINCj6hpyJYTUwgU2NoZW1hIGZvciBNZWRpYSBDb250cm9sqfcgW1JG
QzUxNjgNCj48aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNTE2OD5dIGRlZmluZXMgYW4g
RXh0ZW5zaWJsZSBNYXJrdXANCj5MYW5ndWFnZSAoWE1MKSBTY2hlbWEgZm9yIHZpZGVvIGZhc3Qg
dXBkYXRlLiBJbXBsZW1lbnRhdGlvbnMgYXJlDQo+ZGlzY291cmFnZWQgZnJvbSB1c2luZyB0aGUg
bWV0aG9kIGRlc2NyaWJlZCBleGNlcHQgZm9yIGJhY2t3YXJkDQo+Y29tcGF0aWJpbGl0eSBwdXJw
b3Nlcy4gSW1wbGVtZW50YXRpb25zIFNIT1VMRCB1c2UgRklSIG1lc3NhZ2VzIGluc3RlYWQuDQo+
DQo+TkVOQSBJQ0UtOCBldmVudCBmZWVkYmFjaywgZG8gd2UgbmVlZCB0byBzYXkgbW9yZT8gT3B0
aW9uczoNCj4xLlNSQyBNVVNUIHN1cHBvcnQgYm90aCBhbmQgcHJvdmlkZSBpbnRlcndvcmtpbmcg
dG8gd2hhdCBTUlMgc3VwcG9ydHMgKGFuZA0KPmFuIFVBIHRoYXQgZG9lcyBub3Qgc3VwcG9ydCBi
b3RoIE1VU1QgTk9UIHVzZSBTSVBSRUM/KQ0KPjIuU1JTIE1VU1Qgc3VwcG9ydCBib3RoIChhbmQg
YWxsb3cgU1JDIHRvIHN1cHBvcnQgYm90aCBzaW11bHRhbmVvdXNseT8gQW5kDQo+aG93IGRvIHlv
dSBuZWdvdGlhdGlvbiB0aGF0ID8pDQo+My5Qcm92aWRlIHJlY29tbWVuZGF0aW9ucyBhbmQgbGVh
dmUgYXMgcXVhbGl0eSBvZiBpbXBsZW1lbnRhdGlvbiBkZWNpc2lvbg0KPihhbmQgbGl2ZSB3aXRo
IGludGVyb3BlcmFiaWxpdHkgaXNzdWVzPykNCj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LQ0KPg0KPkRpc2N1c3Npb24gaW4gcm9vbSAoZnJvbSBtaW51dGVzOg0KPmh0dHA6Ly93d3cuaWV0
Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9zaXByZWMvY3VycmVudC9tc2cwMzkzNC5odG1sKQ0KPi0g
UGF1bCBLIC0gbm8gYnJhaW5lciwgU1JTIGlzIHRoZSBwb3dlcmZ1bCBib3ggLSB0aGF0IGlzIHRo
ZSBwbGFjZSB0byBwdXQNCj5yZXF1aXJlbWVudHMgLSAyIGlzIHByZWZlcmFibGUgdG8gMSAtIDIg
dnMuIDMsIEknbSBub3Qgc3VyZSwga2luZCBvZg0KPmluY2xpbmVkIGZvciAyIGJ1dCBub3Qgc3Vy
ZQ0KPi0gQ2hhaXI6IGRlZmluaXRpdmUgaXMgYmVzdCBmb3IgaW1wbGVtZW50YXRpb24NCj4tIENo
YXJsZXM6IG9wdGlvbiAzIGlzIG15IHN1Z2dlc3Rpb24gKGFzIHRoZSBkcmFmdCBpcyksIGJ1dCBj
b3VsZCBsaXZlDQo+d2l0aCBvcHRpb24gMiAtIHdvdWxkIGFwcHJlY2lhdGUgc29tZSBoZWxwIHdp
dGggdGhlIHRleHQgLSBuZWVkIHRvIHRoaW5rDQo+YWJvdXQgdXNlIGNhc2VzIC0gaWYgYSBVQSBp
cyBjYXBhYmxlIG9mIGRlYWxpbmcgd2l0aCBib3RoLCBpdCBjYW4gc2ltcGxpZnkNCj5mb3IgdGhl
IFNSUywgYnV0IGRlcGVuZHMgb24gY2FwYWJpbGl0aWVzIG9mIHRoZSBTUkMgYW5kIFNSUyAtIGlm
IHdlIGNhbiBkbw0KPmJldHRlciB0aGF0IGlzIGdyZWF0DQo+LSBDaGFpcjogbGV0J3MgaGF2ZSBt
b3JlIGxpc3QgZGlzY3Vzc2lvbiBiZWNhdXNlIG1pc3NpbmcgcGVvcGxlIC0gYnV0IGluDQo+ZmF2
b3VyIG9mIGRvY3VtZW50aW5nIG9uZSBhbmQgZ2VuZXJhbGx5IGluIGZhdm91ciBvZiBoYXZpbmcg
dGhlIHNlcnZlciBkbw0KPnRoZSB3b3JrIC0gdGVudGF0aXZlbHkgdGhpbmsgZ29pbmcgaW4gdGhl
IGRpcmVjdGlvbiBvZiBvcHRpb24gMg0KPg0KPlRob3VnaHRzPw0KPg0KPkNoZWVycywNCj5DaGFy
bGVzDQo+DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj5zaXByZWMgbWFpbGluZyBsaXN0DQo+c2lwcmVjQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXByZWMNCg0K


From nobody Fri Mar 21 07:42:47 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D4931A0973 for <siprec@ietfa.amsl.com>; Fri, 21 Mar 2014 07:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dEbGCWXQCCiR for <siprec@ietfa.amsl.com>; Fri, 21 Mar 2014 07:42:42 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 799AE1A09AA for <siprec@ietf.org>; Fri, 21 Mar 2014 07:42:42 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by QMTA11.westchester.pa.mail.comcast.net with comcast id gCra1n00327AodY5BEiZDS; Fri, 21 Mar 2014 14:42:33 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta19.westchester.pa.mail.comcast.net with comcast id gEiY1n00y3ZTu2S3fEiYf6; Fri, 21 Mar 2014 14:42:33 +0000
Message-ID: <532C4FD8.7030007@alum.mit.edu>
Date: Fri, 21 Mar 2014 10:42:32 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Parthasarathi R <partha@parthasarathi.co.in>,  "'Hutton, Andrew'" <andrew.hutton@unify.com>, siprec@ietf.org
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net> <532313E8.2070904@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net> <532B0552.2090907@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3D460@MCHP04MSX.global-ad.net> <00f401cf448e$bb0203f0$31060bd0$@co.in>
In-Reply-To: <00f401cf448e$bb0203f0$31060bd0$@co.in>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395412953; bh=RfYmu0h++AmmSAKxGiUZFq7WHyK6NsRhOP/133JRQRE=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=oBSTldRlRG3Cdq22CMjqXRiXpCq0LVaw7aZZXguqhAvq5WIJV9kX0DNsWkJ7nG7Sa NH+R1b5S0avWfRF0dv4WqnGm6b8yx3qVVUO1cDJbnIbzIlpAXuHTeC6bNxjeuy61sv dMdplSioTrzju3ZKACBmpN1tve14anqVxNGU4AaMzxCvO24T/ulkPm2SmewlgaRsXQ r3wnXNNlXvW1Oj8L7EQccHPJaeMs70B/UykII5UV2hsMBbBXFZSws2h8dgI4FwkZTA g8evmbZKSj+/InRMIuJp9kganQPJeolOZ+Ha77rUQF5lAUkNqY//KwXpB/PcTIMnkb gkNW61iGSvNsA==
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/29Q4xq1R74Q4qJuwImHyKWL-xhQ
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 21 Mar 2014 14:42:45 -0000

On 3/20/14 6:49 PM, Parthasarathi R wrote:
> Hi Paul & all,
>
> I understand that screen sharing shall be considered as a video stream. I'm
> interested in knowing how RTP media is used for application and document
> sharing.

My intent is to treat them exactly the same. And while the focus is on 
video, the sharing can also extend to audio and RTT.

> Also, I'm interested in knowing whether RFC 5547 (A Session Description
> Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer) will be
> covered within MSRP recording deliverable or not.

I'd like to have discussion of that.

I think it makes sense to include it. The way that works, I think the 
SRS would have the option to accept or reject each file transfer, and 
might decide to refuse some or all of them. Also, in general for MSRP 
the SRS will have the option to select which content types it accepts. 
So I think the SRS has reasonable control to accept what it is prepared 
to record and reject things that are irrelevant or too costly to record.

	Thanks,
	Paul

> Thanks
> Partha
>
>> -----Original Message-----
>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
>> Andrew
>> Sent: Thursday, March 20, 2014 11:09 PM
>> To: Paul Kyzivat; siprec@ietf.org
>> Subject: Re: [siprec] SIPREC Milestone Update.
>>
>> I would like to hear what others in the WG think.
>>
>> Andy
>>
>>> -----Original Message-----
>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>> Sent: 20 March 2014 15:12
>>> To: Hutton, Andrew
>>> Cc: siprec@ietf.org
>>> Subject: Re: SIPREC Milestone Update.
>>>
>>> On 3/20/14 5:13 AM, Hutton, Andrew wrote:
>>>> Paul,
>>>>
>>>> The feedback we had during the IETF88 (Vancouver) meeting was that
>> we
>>> could not extend SIPREC to generically cover "document & application"
>>> sharing as there is no standard to base this on.
>>>>
>>>> Can you suggest a milestone that is more precise that we can get
>>> consensus on?
>>>
>>> Does the following work for you?
>>>
>>>     Protocol and metadata for using RTP media to record the sharing
>>>     of applications, documents and screens.
>>>
>>> 	Thanks,
>>> 	Paul
>>>
>>>> Andy
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>>>> Sent: 14 March 2014 14:36
>>>>> To: Hutton, Andrew; siprec@ietf.org
>>>>> Subject: Re: SIPREC Milestone Update.
>>>>>
>>>>> Andy,
>>>>>
>>>>> On 3/13/14 2:49 PM, Hutton, Andrew wrote:
>>>>>> During the IETF89 SIPREC meeting a discrepancy was identified
>>> between
>>>>> my slides showing the proposed new milestones and Paul's slides.
>>>>>>
>>>>>> The chairs slides stated the following milestone:
>>>>>>
>>>>>> "??? 2014 	Protocol and metadata for capturing the content (RFC
>>>>> 4796) of the media stream".
>>>>>>
>>>>>> Whilst Paul's conference recording slides stated
>>>>>>
>>>>>> "Dec 2014	Protocol and metadata for recording of document &
>>>>> application sharing to IESG as Proposed Standard RFC"
>>>>>>
>>>>>> I posted this suggested change to the list as can be seen in the
>>>>> message below and received no comments. The rational for the
>>> suggestion
>>>>> is also given in the text below but is basically that we did not
>>> have
>>>>> consensus for recording of document and application sharing just
>> for
>>>>> video with reference to the content.
>>>>>>
>>>>>> Please give feedback as to whether the milestone with reference
>> to
>>>>> RFC 4796 makes sense.
>>>>>
>>>>> IMO limiting this to RFC 4796 is too narrow for the milestone. It
>>> may
>>>>> turn out that 4796 is *part* of the mechanism, but I certainly
>> don't
>>>>> want to be limited to that. While it needs discussion, I have in
>>> mind
>>>>> to
>>>>> capture additional metadata, such as:
>>>>> - the distinction between document, application, and screen
>> sharing
>>>>> - the name of the document or application
>>>>>
>>>>> These won't always be available, but if they are they would be
>>> useful
>>>>> to
>>>>> record.
>>>>>
>>>>> Also, while the intent is to capture presentations using video
>> (and
>>>>> perhaps audio) media streams, we *may* also want to say something
>>> about
>>>>> *how* this is done.
>>>>>
>>>>> And, if the presentation media includes audio as well as video,
>> and
>>> the
>>>>> audio is distinct from the "room audio", we may want metadata to
>> tie
>>>>> the
>>>>> audio and video together.
>>>>>
>>>>> Note that I've phrased the above as *may* because IMO this stuff
>> is
>>> all
>>>>> subject to debate. But I would like it to be within the scope of
>> the
>>>>> milestone.
>>>>>
>>>>> That is why I phrased the milestone the way I did.
>>>>>
>>>>> The date for the milestone is another question. The December date
>> is
>>>>> probably a little optimistic, but I'd rather do that than have it
>> be
>>>>> pessimistic and just dawdle. But in the end the milestone dates
>> are
>>>>> really up to the chairs and ADs.
>>>>>
>>>>> 	Thanks,
>>>>> 	Paul
>>>>>
>>>>>> Regards
>>>>>> Andy
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of
>> Hutton,
>>>>>>> Andrew
>>>>>>> Sent: 23 December 2013 15:24
>>>>>>> To: Paul Kyzivat; siprec@ietf.org
>>>>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
>>>>> kyzivat-
>>>>>>> siprec-conference-use-cases-00
>>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Since nobody posted any new uses cases I went back to our
>>> discussion
>>>>> in
>>>>>>> Vancouver and tried to see what we appeared to have consensus on
>>> in
>>>>> the
>>>>>>> meeting.
>>>>>>>
>>>>>>>    From that I have formed a proposal for a charter update which
>> is
>>>>> given
>>>>>>> below and also attached (with changes highlighted).
>>>>>>>
>>>>>>> It seems everybody agreed that we need to clarify that SIPREC is
>>>>>>> limited to SIP based systems and that MSRP recording needs to be
>>>>> added.
>>>>>>>
>>>>>>> It also seemed to me that there was no consensus on adding the
>>>>> generic
>>>>>>> case of document/application sharing but if this was limited to
>>>>> being a
>>>>>>> video session in which the content type (RFC 4796) formed part
>> of
>>>>> the
>>>>>>> metadata then probably we would have consensus.  So I included a
>>>>>>> suggested reference to this as a milestone please comment on
>>> whether
>>>>>>> this makes sense.
>>>>>>>
>>>>>>> There was a lot of discussion in the Vancouver meeting about
>>>>> defining a
>>>>>>> generic mechanism to record media without the need to come back
>> to
>>>>>>> SIPREC every time new media types or metadata needs to be
>>> recorded.
>>>>>>> There has been no use cases submitted or discussion on possible
>>>>>>> mechanism since the meeting so I see no way to progress this at
>>>>>>> present.
>>>>>>>
>>>>>>>
>>>>>>> Please can provide comments and Paul and others who stated they
>>>>> would
>>>>>>> contribute can you confirm that you still intend to do so and
>> that
>>>>> this
>>>>>>> charter proposal is acceptable to you.
>>>>>>>
>>>>>>> Regards
>>>>>>> Andy
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> =====================================
>>>>>>> SUGGESTED CHARTER - UPDATE
>>>>>>> =====================================
>>>>>>>
>>>>>>> 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, business analytics, or consumer protection.
>>>>> Recording
>>>>>>> is typically done by sending a copy of the media to the
>> recording
>>>>>>> devices. The working group will determine requirements and
>> produce
>>> a
>>>>>>> specification for a protocol that will manage delivery of media,
>>> in
>>>>> SIP
>>>>>>> based systems (including audio, video, MSRP instant message
>>>>> sessions)
>>>>>>> from an end-point that originates media, or that has access to
>> it,
>>>>> to a
>>>>>>> recording device. PBX and recording vendors today implement
>>>>>>> proprietary, incompatible mechanisms to facilitate recording. A
>>>>>>> standard protocol will reduce the complexity and cost of
>> providing
>>>>> such
>>>>>>> recording services.
>>>>>>>
>>>>>>> The group will define these issues and rationalize with IETF
>>>>> standards
>>>>>>> and practices. This includes encryption, NAT traversal,
>> operations
>>>>> and
>>>>>>> manageability, SIP-enabled firewalls, authorization, and
>> security.
>>>>>>> The scope explicitly does not include recording any of the
>>> extended
>>>>>>> session attributes being defined by the CLUE WG. (These may be
>>>>>>> addressed by a subsequent effort.)
>>>>>>>
>>>>>>> The group will produce:
>>>>>>>
>>>>>>> * Updated Requirements, Use Cases, Architecture draft
>>>>>>>
>>>>>>> * Specification for Session Recording Protocol and Metadata
>>>>>>>
>>>>>>> Milestones
>>>>>>>
>>>>>>> DONE   	Use Cases and Requirements to IESG as Informational
>>> RFC
>>>>>>> MAR 2014 	Submit Architecture to IESG as Informational RFC
>>>>>>> JUN 2014 	Submit protocol draft to IESG as Proposed Standard
>>>>> RFC
>>>>>>> AUG 2014 	Submit Metadata model and format to IESG as Proposed
>>>>>>> Standard RFC
>>>>>>> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an
>>>>> informational
>>>>>>> RFC
>>>>>>> ??? 2014 	Conference Recording Use Cases and Requirements to
>>>>> IESG as
>>>>>>> Informational RFC
>>>>>>> ??? 2014 	Conference Recording Architecture to IESG as
>>>>> Informational
>>>>>>> RFC
>>>>>>> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
>>>>>>> Proposed Standard RFC
>>>>>>> ??? 2014 	Protocol and metadata for capturing the content (RFC
>>>>> 4796)
>>>>>>> of the media stream.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>
>> =======================================================================
>>>>>>> =====================
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Paul
>>>>>>> Kyzivat
>>>>>>>> Sent: 21 November 2013 18:44
>>>>>>>> To: siprec@ietf.org
>>>>>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
>>>>>>> kyzivat-
>>>>>>>> siprec-conference-use-cases-00
>>>>>>>>
>>>>>>>> I still haven't seen anything on this subject.
>>>>>>>> I *thought* there were multiple people in the siprec session in
>>>>>>>> Vancouver that seemed to have other use cases related to media.
>>>>>>>>
>>>>>>>> If so, better speak up, or IIUC we are going to treat the use
>>> cases
>>>>>>> we
>>>>>>>> have as bounding the new scope.
>>>>>>>>
>>>>>>>> 	Thanks,
>>>>>>>> 	Paul
>>>>>>>>
>>>>>>>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
>>>>>>>>> One of the action items from the meeting last week was:
>>>>>>>>>
>>>>>>>>>> chairs: use cases to the list in the next couple of weeks.
>>> After
>>>>>>>> that,
>>>>>>>>>> we will decide if we need charter language.  If your use case
>>> is
>>>>>>> not
>>>>>>>>>> contributed, it will not be considered in the milestones.
>>>>>>>>>
>>>>>>>>> The above is a little vague about the timing. Two weeks from
>> the
>>>>>>> end
>>>>>>>> of
>>>>>>>>> the meeting would be Friday, November 23. (Hopefully the
>> chairs
>>>>>>> will
>>>>>>>>> clarify this.)
>>>>>>>>>
>>>>>>>>> This is important because there was some desire to tighten up
>>> the
>>>>>>>> scope
>>>>>>>>> of the rechartering to encompass only the mentioned use cases.
>>>>>>>>>
>>>>>>>>> I'll be happy to incorporate additional popular use cases even
>>>>>>> before
>>>>>>>>> this draft becomes a wg draft. (But please send text.)
>>>>>>>>>
>>>>>>>>> While the name of the draft is about conferences, the use
>> cases
>>>>>>>> include
>>>>>>>>> additional media support. (Maybe we should rename the draft.)
>>> And
>>>>>>> it
>>>>>>>>> seemed that much of the interest was about additional media.
>>>>>>>>>
>>>>>>>>>         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
>>>>>>
>>>>
>>>>
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>
>


From nobody Sun Mar 23 03:41:45 2014
Return-Path: <partha@parthasarathi.co.in>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 308681A6EF7 for <siprec@ietfa.amsl.com>; Sun, 23 Mar 2014 03:41:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.699
X-Spam-Level: 
X-Spam-Status: No, score=0.699 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JmXVeiX7FUgm for <siprec@ietfa.amsl.com>; Sun, 23 Mar 2014 03:41:38 -0700 (PDT)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.29]) by ietfa.amsl.com (Postfix) with ESMTP id 70DDD1A098B for <siprec@ietf.org>; Sun, 23 Mar 2014 03:41:38 -0700 (PDT)
Received: from userPC (unknown [122.167.205.77]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id F2B7A86904E; Sun, 23 Mar 2014 10:41:33 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1395571298; bh=6/iJOjb9MEmfFWJAyeCk0k40CKNwCZpYzDoN0gvri4U=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=CQs3YgIAWM6m9XIhH1XwYaQlGsuFwcuJ4TgTlpZ4Z+MZGN20+oSyqmUr/YaUDVdPS i0C4wpRdrtpBCPDcSpOcLoNUpQoNAGwudVoK9vQxhkCOkbQE9kMqzUOWpPJDxOackt G+ZNxfVn2pi1NqPkLnPU/CxIsA0mC7rvGFG5BpAE=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Paul Kyzivat'" <pkyzivat@alum.mit.edu>, "'Hutton, Andrew'" <andrew.hutton@unify.com>, <siprec@ietf.org>
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net> <532313E8.2070904@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net> <532B0552.2090907@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3D460@MCHP04MSX.global-ad.net> <00f401cf448e$bb0203f0$31060bd0$@co.in> <532C4FD8.7030007@alum.mit.edu>
In-Reply-To: <532C4FD8.7030007@alum.mit.edu>
Date: Sun, 23 Mar 2014 16:11:23 +0530
Message-ID: <00c701cf4684$774e6ed0$65eb4c70$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac9FE86bbuuvcKvSSD2f5Q1Dpa5s8ABbz6+w
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020203.532EBA61.00E9, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 172.18.214.93
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/hD2KZimem968LS5zTXFMAXkTvM8
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 23 Mar 2014 10:41:42 -0000

Hi Paul,

Please read inline.

Thanks
Partha

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> Sent: Friday, March 21, 2014 8:13 PM
> To: Parthasarathi R; 'Hutton, Andrew'; siprec@ietf.org
> Subject: Re: [siprec] SIPREC Milestone Update.
> 
> On 3/20/14 6:49 PM, Parthasarathi R wrote:
> > Hi Paul & all,
> >
> > I understand that screen sharing shall be considered as a video
> stream. I'm
> > interested in knowing how RTP media is used for application and
> document
> > sharing.
> 
> My intent is to treat them exactly the same. And while the focus is on
> video, the sharing can also extend to audio and RTT.
> 
<Partha> Agreed as it applies to some of the usecases wherein sharing is the
focus. But we need to consider the usecase wherein screen sharing as video
stream whereas the audio & RTT as the regular communication session, this
helps for debugging sort of scenario </Partha> 

> > Also, I'm interested in knowing whether RFC 5547 (A Session
> Description
> > Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer) will
> be
> > covered within MSRP recording deliverable or not.
> 
> I'd like to have discussion of that.
> 
> I think it makes sense to include it. The way that works, I think the
> SRS would have the option to accept or reject each file transfer, and
> might decide to refuse some or all of them. Also, in general for MSRP
> the SRS will have the option to select which content types it accepts.
> So I think the SRS has reasonable control to accept what it is prepared
> to record and reject things that are irrelevant or too costly to
> record.
> 
<Partha> Thanks for the clarification about your point of view. I agree with
you that there should be option to select or reject in SRS. Please include
the initial text in your MSRP draft (draft-yan-siprec-msrp-recording) for
more discussion. </Partha>

> 	Thanks,
> 	Paul
> 
> > Thanks
> > Partha
> >
> >> -----Original Message-----
> >> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
> >> Andrew
> >> Sent: Thursday, March 20, 2014 11:09 PM
> >> To: Paul Kyzivat; siprec@ietf.org
> >> Subject: Re: [siprec] SIPREC Milestone Update.
> >>
> >> I would like to hear what others in the WG think.
> >>
> >> Andy
> >>
> >>> -----Original Message-----
> >>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> >>> Sent: 20 March 2014 15:12
> >>> To: Hutton, Andrew
> >>> Cc: siprec@ietf.org
> >>> Subject: Re: SIPREC Milestone Update.
> >>>
> >>> On 3/20/14 5:13 AM, Hutton, Andrew wrote:
> >>>> Paul,
> >>>>
> >>>> The feedback we had during the IETF88 (Vancouver) meeting was that
> >> we
> >>> could not extend SIPREC to generically cover "document &
> application"
> >>> sharing as there is no standard to base this on.
> >>>>
> >>>> Can you suggest a milestone that is more precise that we can get
> >>> consensus on?
> >>>
> >>> Does the following work for you?
> >>>
> >>>     Protocol and metadata for using RTP media to record the sharing
> >>>     of applications, documents and screens.
> >>>
> >>> 	Thanks,
> >>> 	Paul
> >>>
> >>>> Andy
> >>>>
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> >>>>> Sent: 14 March 2014 14:36
> >>>>> To: Hutton, Andrew; siprec@ietf.org
> >>>>> Subject: Re: SIPREC Milestone Update.
> >>>>>
> >>>>> Andy,
> >>>>>
> >>>>> On 3/13/14 2:49 PM, Hutton, Andrew wrote:
> >>>>>> During the IETF89 SIPREC meeting a discrepancy was identified
> >>> between
> >>>>> my slides showing the proposed new milestones and Paul's slides.
> >>>>>>
> >>>>>> The chairs slides stated the following milestone:
> >>>>>>
> >>>>>> "??? 2014 	Protocol and metadata for capturing the content (RFC
> >>>>> 4796) of the media stream".
> >>>>>>
> >>>>>> Whilst Paul's conference recording slides stated
> >>>>>>
> >>>>>> "Dec 2014	Protocol and metadata for recording of document &
> >>>>> application sharing to IESG as Proposed Standard RFC"
> >>>>>>
> >>>>>> I posted this suggested change to the list as can be seen in the
> >>>>> message below and received no comments. The rational for the
> >>> suggestion
> >>>>> is also given in the text below but is basically that we did not
> >>> have
> >>>>> consensus for recording of document and application sharing just
> >> for
> >>>>> video with reference to the content.
> >>>>>>
> >>>>>> Please give feedback as to whether the milestone with reference
> >> to
> >>>>> RFC 4796 makes sense.
> >>>>>
> >>>>> IMO limiting this to RFC 4796 is too narrow for the milestone. It
> >>> may
> >>>>> turn out that 4796 is *part* of the mechanism, but I certainly
> >> don't
> >>>>> want to be limited to that. While it needs discussion, I have in
> >>> mind
> >>>>> to
> >>>>> capture additional metadata, such as:
> >>>>> - the distinction between document, application, and screen
> >> sharing
> >>>>> - the name of the document or application
> >>>>>
> >>>>> These won't always be available, but if they are they would be
> >>> useful
> >>>>> to
> >>>>> record.
> >>>>>
> >>>>> Also, while the intent is to capture presentations using video
> >> (and
> >>>>> perhaps audio) media streams, we *may* also want to say something
> >>> about
> >>>>> *how* this is done.
> >>>>>
> >>>>> And, if the presentation media includes audio as well as video,
> >> and
> >>> the
> >>>>> audio is distinct from the "room audio", we may want metadata to
> >> tie
> >>>>> the
> >>>>> audio and video together.
> >>>>>
> >>>>> Note that I've phrased the above as *may* because IMO this stuff
> >> is
> >>> all
> >>>>> subject to debate. But I would like it to be within the scope of
> >> the
> >>>>> milestone.
> >>>>>
> >>>>> That is why I phrased the milestone the way I did.
> >>>>>
> >>>>> The date for the milestone is another question. The December date
> >> is
> >>>>> probably a little optimistic, but I'd rather do that than have it
> >> be
> >>>>> pessimistic and just dawdle. But in the end the milestone dates
> >> are
> >>>>> really up to the chairs and ADs.
> >>>>>
> >>>>> 	Thanks,
> >>>>> 	Paul
> >>>>>
> >>>>>> Regards
> >>>>>> Andy
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of
> >> Hutton,
> >>>>>>> Andrew
> >>>>>>> Sent: 23 December 2013 15:24
> >>>>>>> To: Paul Kyzivat; siprec@ietf.org
> >>>>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
> >>>>> kyzivat-
> >>>>>>> siprec-conference-use-cases-00
> >>>>>>>
> >>>>>>> Hi All,
> >>>>>>>
> >>>>>>> Since nobody posted any new uses cases I went back to our
> >>> discussion
> >>>>> in
> >>>>>>> Vancouver and tried to see what we appeared to have consensus
> on
> >>> in
> >>>>> the
> >>>>>>> meeting.
> >>>>>>>
> >>>>>>>    From that I have formed a proposal for a charter update
> which
> >> is
> >>>>> given
> >>>>>>> below and also attached (with changes highlighted).
> >>>>>>>
> >>>>>>> It seems everybody agreed that we need to clarify that SIPREC
> is
> >>>>>>> limited to SIP based systems and that MSRP recording needs to
> be
> >>>>> added.
> >>>>>>>
> >>>>>>> It also seemed to me that there was no consensus on adding the
> >>>>> generic
> >>>>>>> case of document/application sharing but if this was limited to
> >>>>> being a
> >>>>>>> video session in which the content type (RFC 4796) formed part
> >> of
> >>>>> the
> >>>>>>> metadata then probably we would have consensus.  So I included
> a
> >>>>>>> suggested reference to this as a milestone please comment on
> >>> whether
> >>>>>>> this makes sense.
> >>>>>>>
> >>>>>>> There was a lot of discussion in the Vancouver meeting about
> >>>>> defining a
> >>>>>>> generic mechanism to record media without the need to come back
> >> to
> >>>>>>> SIPREC every time new media types or metadata needs to be
> >>> recorded.
> >>>>>>> There has been no use cases submitted or discussion on possible
> >>>>>>> mechanism since the meeting so I see no way to progress this at
> >>>>>>> present.
> >>>>>>>
> >>>>>>>
> >>>>>>> Please can provide comments and Paul and others who stated they
> >>>>> would
> >>>>>>> contribute can you confirm that you still intend to do so and
> >> that
> >>>>> this
> >>>>>>> charter proposal is acceptable to you.
> >>>>>>>
> >>>>>>> Regards
> >>>>>>> Andy
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> =====================================
> >>>>>>> SUGGESTED CHARTER - UPDATE
> >>>>>>> =====================================
> >>>>>>>
> >>>>>>> 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, business analytics, or consumer protection.
> >>>>> Recording
> >>>>>>> is typically done by sending a copy of the media to the
> >> recording
> >>>>>>> devices. The working group will determine requirements and
> >> produce
> >>> a
> >>>>>>> specification for a protocol that will manage delivery of
> media,
> >>> in
> >>>>> SIP
> >>>>>>> based systems (including audio, video, MSRP instant message
> >>>>> sessions)
> >>>>>>> from an end-point that originates media, or that has access to
> >> it,
> >>>>> to a
> >>>>>>> recording device. PBX and recording vendors today implement
> >>>>>>> proprietary, incompatible mechanisms to facilitate recording. A
> >>>>>>> standard protocol will reduce the complexity and cost of
> >> providing
> >>>>> such
> >>>>>>> recording services.
> >>>>>>>
> >>>>>>> The group will define these issues and rationalize with IETF
> >>>>> standards
> >>>>>>> and practices. This includes encryption, NAT traversal,
> >> operations
> >>>>> and
> >>>>>>> manageability, SIP-enabled firewalls, authorization, and
> >> security.
> >>>>>>> The scope explicitly does not include recording any of the
> >>> extended
> >>>>>>> session attributes being defined by the CLUE WG. (These may be
> >>>>>>> addressed by a subsequent effort.)
> >>>>>>>
> >>>>>>> The group will produce:
> >>>>>>>
> >>>>>>> * Updated Requirements, Use Cases, Architecture draft
> >>>>>>>
> >>>>>>> * Specification for Session Recording Protocol and Metadata
> >>>>>>>
> >>>>>>> Milestones
> >>>>>>>
> >>>>>>> DONE   	Use Cases and Requirements to IESG as Informational
> >>> RFC
> >>>>>>> MAR 2014 	Submit Architecture to IESG as Informational RFC
> >>>>>>> JUN 2014 	Submit protocol draft to IESG as Proposed Standard
> >>>>> RFC
> >>>>>>> AUG 2014 	Submit Metadata model and format to IESG as Proposed
> >>>>>>> Standard RFC
> >>>>>>> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an
> >>>>> informational
> >>>>>>> RFC
> >>>>>>> ??? 2014 	Conference Recording Use Cases and Requirements to
> >>>>> IESG as
> >>>>>>> Informational RFC
> >>>>>>> ??? 2014 	Conference Recording Architecture to IESG as
> >>>>> Informational
> >>>>>>> RFC
> >>>>>>> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
> >>>>>>> Proposed Standard RFC
> >>>>>>> ??? 2014 	Protocol and metadata for capturing the content (RFC
> >>>>> 4796)
> >>>>>>> of the media stream.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>
> >>
> =======================================================================
> >>>>>>> =====================
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of
> Paul
> >>>>>>> Kyzivat
> >>>>>>>> Sent: 21 November 2013 18:44
> >>>>>>>> To: siprec@ietf.org
> >>>>>>>> Subject: Re: [siprec] Reminder: Additional use cases for
> draft-
> >>>>>>> kyzivat-
> >>>>>>>> siprec-conference-use-cases-00
> >>>>>>>>
> >>>>>>>> I still haven't seen anything on this subject.
> >>>>>>>> I *thought* there were multiple people in the siprec session
> in
> >>>>>>>> Vancouver that seemed to have other use cases related to
> media.
> >>>>>>>>
> >>>>>>>> If so, better speak up, or IIUC we are going to treat the use
> >>> cases
> >>>>>>> we
> >>>>>>>> have as bounding the new scope.
> >>>>>>>>
> >>>>>>>> 	Thanks,
> >>>>>>>> 	Paul
> >>>>>>>>
> >>>>>>>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
> >>>>>>>>> One of the action items from the meeting last week was:
> >>>>>>>>>
> >>>>>>>>>> chairs: use cases to the list in the next couple of weeks.
> >>> After
> >>>>>>>> that,
> >>>>>>>>>> we will decide if we need charter language.  If your use
> case
> >>> is
> >>>>>>> not
> >>>>>>>>>> contributed, it will not be considered in the milestones.
> >>>>>>>>>
> >>>>>>>>> The above is a little vague about the timing. Two weeks from
> >> the
> >>>>>>> end
> >>>>>>>> of
> >>>>>>>>> the meeting would be Friday, November 23. (Hopefully the
> >> chairs
> >>>>>>> will
> >>>>>>>>> clarify this.)
> >>>>>>>>>
> >>>>>>>>> This is important because there was some desire to tighten up
> >>> the
> >>>>>>>> scope
> >>>>>>>>> of the rechartering to encompass only the mentioned use
> cases.
> >>>>>>>>>
> >>>>>>>>> I'll be happy to incorporate additional popular use cases
> even
> >>>>>>> before
> >>>>>>>>> this draft becomes a wg draft. (But please send text.)
> >>>>>>>>>
> >>>>>>>>> While the name of the draft is about conferences, the use
> >> cases
> >>>>>>>> include
> >>>>>>>>> additional media support. (Maybe we should rename the draft.)
> >>> And
> >>>>>>> it
> >>>>>>>>> seemed that much of the interest was about additional media.
> >>>>>>>>>
> >>>>>>>>>         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
> >>>>>>
> >>>>
> >>>>
> >>
> >> _______________________________________________
> >> siprec mailing list
> >> siprec@ietf.org
> >> https://www.ietf.org/mailman/listinfo/siprec
> >
> >


From nobody Sun Mar 23 10:51:06 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A202B1A6FFA for <siprec@ietfa.amsl.com>; Sun, 23 Mar 2014 10:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOSBa3aMyq9z for <siprec@ietfa.amsl.com>; Sun, 23 Mar 2014 10:51:00 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id B2B3E1A6FF4 for <siprec@ietf.org>; Sun, 23 Mar 2014 10:50:59 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta12.westchester.pa.mail.comcast.net with comcast id h5kY1n00417dt5G5C5qzkt; Sun, 23 Mar 2014 17:50:59 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta13.westchester.pa.mail.comcast.net with comcast id h5qy1n00X3ZTu2S3Z5qyR8; Sun, 23 Mar 2014 17:50:59 +0000
Message-ID: <532F1F02.4010500@alum.mit.edu>
Date: Sun, 23 Mar 2014 13:50:58 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Parthasarathi R <partha@parthasarathi.co.in>,  "'Hutton, Andrew'" <andrew.hutton@unify.com>, siprec@ietf.org
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net> <532313E8.2070904@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net> <532B0552.2090907@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3D460@MCHP04MSX.global-ad.net> <00f401cf448e$bb0203f0$31060bd0$@co.in> <532C4FD8.7030007@alum.mit.edu> <00c701cf4684$774e6ed0$65eb4c70$@co.in>
In-Reply-To: <00c701cf4684$774e6ed0$65eb4c70$@co.in>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395597059; bh=LfSQXODf/wAfB62zWpPm9krBxSkzgdLWtTxlqx1CCqQ=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=g92QNrBvfuFaWY51SumC7T57pOXVQgJRzLmwXmECWnlSjUL6IUVkucoGs/WW8/3mY zQ/c2qQe65aQ1WCnq43OLvBi+kU/AH4NDFP9FYPW4uekJVWG/BdO4gs5/NaqNLpHs3 Cx4vv7si0fE7V3g2zpg1lwcsJ7cAi3HiiBb/3eqAd39h+T/Umebnrp09Z1Y7Z3Pu9v kQzFd9FEl9tYvvUg/730b2fYeY+U8YI/P4zmOCmnhNzICVoR0OUSZJTDGW/skHl3Or JR+Txp8aeXts4/gkjN5T61yMiRCyuH1lInlNuvFg+7jPnIOKv8HWFMpWjWnfGnrTUL MXQ3jXZpxOxmg==
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/xOo1Ffyb140PwOzbe-IefxeEWKk
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 23 Mar 2014 17:51:02 -0000

On 3/23/14 6:41 AM, Parthasarathi R wrote:
> Hi Paul,
>
> Please read inline.
>
> Thanks
> Partha
>
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>> Sent: Friday, March 21, 2014 8:13 PM
>> To: Parthasarathi R; 'Hutton, Andrew'; siprec@ietf.org
>> Subject: Re: [siprec] SIPREC Milestone Update.
>>
>> On 3/20/14 6:49 PM, Parthasarathi R wrote:
>>> Hi Paul & all,
>>>
>>> I understand that screen sharing shall be considered as a video
>> stream. I'm
>>> interested in knowing how RTP media is used for application and
>> document
>>> sharing.
>>
>> My intent is to treat them exactly the same. And while the focus is on
>> video, the sharing can also extend to audio and RTT.
>>
> <Partha> Agreed as it applies to some of the usecases wherein sharing is the
> focus. But we need to consider the usecase wherein screen sharing as video
> stream whereas the audio & RTT as the regular communication session, this
> helps for debugging sort of scenario </Partha>

Certainly. Each media stream may be for doc/app/screen sharing, or for 
normal interactive communications. There could be streams of any type 
for each in any given CS. It will be the task of metadata to distinguish 
the intent of each stream.

>>> Also, I'm interested in knowing whether RFC 5547 (A Session
>> Description
>>> Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer) will
>> be
>>> covered within MSRP recording deliverable or not.
>>
>> I'd like to have discussion of that.
>>
>> I think it makes sense to include it. The way that works, I think the
>> SRS would have the option to accept or reject each file transfer, and
>> might decide to refuse some or all of them. Also, in general for MSRP
>> the SRS will have the option to select which content types it accepts.
>> So I think the SRS has reasonable control to accept what it is prepared
>> to record and reject things that are irrelevant or too costly to
>> record.
>>
> <Partha> Thanks for the clarification about your point of view. I agree with
> you that there should be option to select or reject in SRS. Please include
> the initial text in your MSRP draft (draft-yan-siprec-msrp-recording) for
> more discussion. </Partha>

OK. In next version.

Note that the SRS is already free to select or reject any given media 
for recording - either be refusing to receive it, or by receiving it by 
not recording it. What we get here are more tools for selecting what to 
receive.

	Thanks,
	Paul

>> 	Thanks,
>> 	Paul
>>
>>> Thanks
>>> Partha
>>>
>>>> -----Original Message-----
>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
>>>> Andrew
>>>> Sent: Thursday, March 20, 2014 11:09 PM
>>>> To: Paul Kyzivat; siprec@ietf.org
>>>> Subject: Re: [siprec] SIPREC Milestone Update.
>>>>
>>>> I would like to hear what others in the WG think.
>>>>
>>>> Andy
>>>>
>>>>> -----Original Message-----
>>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>>>> Sent: 20 March 2014 15:12
>>>>> To: Hutton, Andrew
>>>>> Cc: siprec@ietf.org
>>>>> Subject: Re: SIPREC Milestone Update.
>>>>>
>>>>> On 3/20/14 5:13 AM, Hutton, Andrew wrote:
>>>>>> Paul,
>>>>>>
>>>>>> The feedback we had during the IETF88 (Vancouver) meeting was that
>>>> we
>>>>> could not extend SIPREC to generically cover "document &
>> application"
>>>>> sharing as there is no standard to base this on.
>>>>>>
>>>>>> Can you suggest a milestone that is more precise that we can get
>>>>> consensus on?
>>>>>
>>>>> Does the following work for you?
>>>>>
>>>>>      Protocol and metadata for using RTP media to record the sharing
>>>>>      of applications, documents and screens.
>>>>>
>>>>> 	Thanks,
>>>>> 	Paul
>>>>>
>>>>>> Andy
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>>>>>> Sent: 14 March 2014 14:36
>>>>>>> To: Hutton, Andrew; siprec@ietf.org
>>>>>>> Subject: Re: SIPREC Milestone Update.
>>>>>>>
>>>>>>> Andy,
>>>>>>>
>>>>>>> On 3/13/14 2:49 PM, Hutton, Andrew wrote:
>>>>>>>> During the IETF89 SIPREC meeting a discrepancy was identified
>>>>> between
>>>>>>> my slides showing the proposed new milestones and Paul's slides.
>>>>>>>>
>>>>>>>> The chairs slides stated the following milestone:
>>>>>>>>
>>>>>>>> "??? 2014 	Protocol and metadata for capturing the content (RFC
>>>>>>> 4796) of the media stream".
>>>>>>>>
>>>>>>>> Whilst Paul's conference recording slides stated
>>>>>>>>
>>>>>>>> "Dec 2014	Protocol and metadata for recording of document &
>>>>>>> application sharing to IESG as Proposed Standard RFC"
>>>>>>>>
>>>>>>>> I posted this suggested change to the list as can be seen in the
>>>>>>> message below and received no comments. The rational for the
>>>>> suggestion
>>>>>>> is also given in the text below but is basically that we did not
>>>>> have
>>>>>>> consensus for recording of document and application sharing just
>>>> for
>>>>>>> video with reference to the content.
>>>>>>>>
>>>>>>>> Please give feedback as to whether the milestone with reference
>>>> to
>>>>>>> RFC 4796 makes sense.
>>>>>>>
>>>>>>> IMO limiting this to RFC 4796 is too narrow for the milestone. It
>>>>> may
>>>>>>> turn out that 4796 is *part* of the mechanism, but I certainly
>>>> don't
>>>>>>> want to be limited to that. While it needs discussion, I have in
>>>>> mind
>>>>>>> to
>>>>>>> capture additional metadata, such as:
>>>>>>> - the distinction between document, application, and screen
>>>> sharing
>>>>>>> - the name of the document or application
>>>>>>>
>>>>>>> These won't always be available, but if they are they would be
>>>>> useful
>>>>>>> to
>>>>>>> record.
>>>>>>>
>>>>>>> Also, while the intent is to capture presentations using video
>>>> (and
>>>>>>> perhaps audio) media streams, we *may* also want to say something
>>>>> about
>>>>>>> *how* this is done.
>>>>>>>
>>>>>>> And, if the presentation media includes audio as well as video,
>>>> and
>>>>> the
>>>>>>> audio is distinct from the "room audio", we may want metadata to
>>>> tie
>>>>>>> the
>>>>>>> audio and video together.
>>>>>>>
>>>>>>> Note that I've phrased the above as *may* because IMO this stuff
>>>> is
>>>>> all
>>>>>>> subject to debate. But I would like it to be within the scope of
>>>> the
>>>>>>> milestone.
>>>>>>>
>>>>>>> That is why I phrased the milestone the way I did.
>>>>>>>
>>>>>>> The date for the milestone is another question. The December date
>>>> is
>>>>>>> probably a little optimistic, but I'd rather do that than have it
>>>> be
>>>>>>> pessimistic and just dawdle. But in the end the milestone dates
>>>> are
>>>>>>> really up to the chairs and ADs.
>>>>>>>
>>>>>>> 	Thanks,
>>>>>>> 	Paul
>>>>>>>
>>>>>>>> Regards
>>>>>>>> Andy
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of
>>>> Hutton,
>>>>>>>>> Andrew
>>>>>>>>> Sent: 23 December 2013 15:24
>>>>>>>>> To: Paul Kyzivat; siprec@ietf.org
>>>>>>>>> Subject: Re: [siprec] Reminder: Additional use cases for draft-
>>>>>>> kyzivat-
>>>>>>>>> siprec-conference-use-cases-00
>>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>>
>>>>>>>>> Since nobody posted any new uses cases I went back to our
>>>>> discussion
>>>>>>> in
>>>>>>>>> Vancouver and tried to see what we appeared to have consensus
>> on
>>>>> in
>>>>>>> the
>>>>>>>>> meeting.
>>>>>>>>>
>>>>>>>>>     From that I have formed a proposal for a charter update
>> which
>>>> is
>>>>>>> given
>>>>>>>>> below and also attached (with changes highlighted).
>>>>>>>>>
>>>>>>>>> It seems everybody agreed that we need to clarify that SIPREC
>> is
>>>>>>>>> limited to SIP based systems and that MSRP recording needs to
>> be
>>>>>>> added.
>>>>>>>>>
>>>>>>>>> It also seemed to me that there was no consensus on adding the
>>>>>>> generic
>>>>>>>>> case of document/application sharing but if this was limited to
>>>>>>> being a
>>>>>>>>> video session in which the content type (RFC 4796) formed part
>>>> of
>>>>>>> the
>>>>>>>>> metadata then probably we would have consensus.  So I included
>> a
>>>>>>>>> suggested reference to this as a milestone please comment on
>>>>> whether
>>>>>>>>> this makes sense.
>>>>>>>>>
>>>>>>>>> There was a lot of discussion in the Vancouver meeting about
>>>>>>> defining a
>>>>>>>>> generic mechanism to record media without the need to come back
>>>> to
>>>>>>>>> SIPREC every time new media types or metadata needs to be
>>>>> recorded.
>>>>>>>>> There has been no use cases submitted or discussion on possible
>>>>>>>>> mechanism since the meeting so I see no way to progress this at
>>>>>>>>> present.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Please can provide comments and Paul and others who stated they
>>>>>>> would
>>>>>>>>> contribute can you confirm that you still intend to do so and
>>>> that
>>>>>>> this
>>>>>>>>> charter proposal is acceptable to you.
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> Andy
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> =====================================
>>>>>>>>> SUGGESTED CHARTER - UPDATE
>>>>>>>>> =====================================
>>>>>>>>>
>>>>>>>>> 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, business analytics, or consumer protection.
>>>>>>> Recording
>>>>>>>>> is typically done by sending a copy of the media to the
>>>> recording
>>>>>>>>> devices. The working group will determine requirements and
>>>> produce
>>>>> a
>>>>>>>>> specification for a protocol that will manage delivery of
>> media,
>>>>> in
>>>>>>> SIP
>>>>>>>>> based systems (including audio, video, MSRP instant message
>>>>>>> sessions)
>>>>>>>>> from an end-point that originates media, or that has access to
>>>> it,
>>>>>>> to a
>>>>>>>>> recording device. PBX and recording vendors today implement
>>>>>>>>> proprietary, incompatible mechanisms to facilitate recording. A
>>>>>>>>> standard protocol will reduce the complexity and cost of
>>>> providing
>>>>>>> such
>>>>>>>>> recording services.
>>>>>>>>>
>>>>>>>>> The group will define these issues and rationalize with IETF
>>>>>>> standards
>>>>>>>>> and practices. This includes encryption, NAT traversal,
>>>> operations
>>>>>>> and
>>>>>>>>> manageability, SIP-enabled firewalls, authorization, and
>>>> security.
>>>>>>>>> The scope explicitly does not include recording any of the
>>>>> extended
>>>>>>>>> session attributes being defined by the CLUE WG. (These may be
>>>>>>>>> addressed by a subsequent effort.)
>>>>>>>>>
>>>>>>>>> The group will produce:
>>>>>>>>>
>>>>>>>>> * Updated Requirements, Use Cases, Architecture draft
>>>>>>>>>
>>>>>>>>> * Specification for Session Recording Protocol and Metadata
>>>>>>>>>
>>>>>>>>> Milestones
>>>>>>>>>
>>>>>>>>> DONE   	Use Cases and Requirements to IESG as Informational
>>>>> RFC
>>>>>>>>> MAR 2014 	Submit Architecture to IESG as Informational RFC
>>>>>>>>> JUN 2014 	Submit protocol draft to IESG as Proposed Standard
>>>>>>> RFC
>>>>>>>>> AUG 2014 	Submit Metadata model and format to IESG as Proposed
>>>>>>>>> Standard RFC
>>>>>>>>> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an
>>>>>>> informational
>>>>>>>>> RFC
>>>>>>>>> ??? 2014 	Conference Recording Use Cases and Requirements to
>>>>>>> IESG as
>>>>>>>>> Informational RFC
>>>>>>>>> ??? 2014 	Conference Recording Architecture to IESG as
>>>>>>> Informational
>>>>>>>>> RFC
>>>>>>>>> ??? 2014 	Protocol and metadata for MSRP recording to IESG as
>>>>>>>>> Proposed Standard RFC
>>>>>>>>> ??? 2014 	Protocol and metadata for capturing the content (RFC
>>>>>>> 4796)
>>>>>>>>> of the media stream.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>
>>>>
>> =======================================================================
>>>>>>>>> =====================
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of
>> Paul
>>>>>>>>> Kyzivat
>>>>>>>>>> Sent: 21 November 2013 18:44
>>>>>>>>>> To: siprec@ietf.org
>>>>>>>>>> Subject: Re: [siprec] Reminder: Additional use cases for
>> draft-
>>>>>>>>> kyzivat-
>>>>>>>>>> siprec-conference-use-cases-00
>>>>>>>>>>
>>>>>>>>>> I still haven't seen anything on this subject.
>>>>>>>>>> I *thought* there were multiple people in the siprec session
>> in
>>>>>>>>>> Vancouver that seemed to have other use cases related to
>> media.
>>>>>>>>>>
>>>>>>>>>> If so, better speak up, or IIUC we are going to treat the use
>>>>> cases
>>>>>>>>> we
>>>>>>>>>> have as bounding the new scope.
>>>>>>>>>>
>>>>>>>>>> 	Thanks,
>>>>>>>>>> 	Paul
>>>>>>>>>>
>>>>>>>>>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
>>>>>>>>>>> One of the action items from the meeting last week was:
>>>>>>>>>>>
>>>>>>>>>>>> chairs: use cases to the list in the next couple of weeks.
>>>>> After
>>>>>>>>>> that,
>>>>>>>>>>>> we will decide if we need charter language.  If your use
>> case
>>>>> is
>>>>>>>>> not
>>>>>>>>>>>> contributed, it will not be considered in the milestones.
>>>>>>>>>>>
>>>>>>>>>>> The above is a little vague about the timing. Two weeks from
>>>> the
>>>>>>>>> end
>>>>>>>>>> of
>>>>>>>>>>> the meeting would be Friday, November 23. (Hopefully the
>>>> chairs
>>>>>>>>> will
>>>>>>>>>>> clarify this.)
>>>>>>>>>>>
>>>>>>>>>>> This is important because there was some desire to tighten up
>>>>> the
>>>>>>>>>> scope
>>>>>>>>>>> of the rechartering to encompass only the mentioned use
>> cases.
>>>>>>>>>>>
>>>>>>>>>>> I'll be happy to incorporate additional popular use cases
>> even
>>>>>>>>> before
>>>>>>>>>>> this draft becomes a wg draft. (But please send text.)
>>>>>>>>>>>
>>>>>>>>>>> While the name of the draft is about conferences, the use
>>>> cases
>>>>>>>>>> include
>>>>>>>>>>> additional media support. (Maybe we should rename the draft.)
>>>>> And
>>>>>>>>> it
>>>>>>>>>>> seemed that much of the interest was about additional media.
>>>>>>>>>>>
>>>>>>>>>>>          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
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>
>>>
>
>


From nobody Sun Mar 23 17:52:12 2014
Return-Path: <partha@parthasarathi.co.in>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 945F11A006E for <siprec@ietfa.amsl.com>; Sun, 23 Mar 2014 17:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XyU6bT3cFfew for <siprec@ietfa.amsl.com>; Sun, 23 Mar 2014 17:52:05 -0700 (PDT)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.25]) by ietfa.amsl.com (Postfix) with ESMTP id 99DB71A006B for <siprec@ietf.org>; Sun, 23 Mar 2014 17:52:05 -0700 (PDT)
Received: from userPC (unknown [122.167.205.77]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id D3A3E16C803D; Mon, 24 Mar 2014 00:52:00 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1395622325; bh=ZVGQeB/CH3Lflj5SXGi9W4u61NgUZJUBnxAfvLMSwD0=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=K3KNKtgwQlvs063XobdCXpg/y3X2VgcWSapr4VG37NikPmR6u+Wrl1NmKzWatqrAM f1QiqydX2rTHWtoD9AbHTKD+RqnWb4DNFNQ851mI/iJDVIWA5yV2WI+wQN90Sduzln KUxv6LO4nLBYQHLYV/5mCrELZiyE0VfYxxvCKXc0=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Paul Kyzivat'" <pkyzivat@alum.mit.edu>, "'Hutton, Andrew'" <andrew.hutton@unify.com>, <siprec@ietf.org>
References: <52865A68.4070000@alum.mit.edu> <528E545C.2090804@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C883A5@MCHP04MSX.global-ad.net> <9F33F40F6F2CD847824537F3C4E37DDF17D35623@MCHP04MSX.global-ad.net> <532313E8.2070904@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3C367@MCHP04MSX.global-ad.net> <532B0552.2090907@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17D3D460@MCHP04MSX.global-ad.net> <00f401cf448e$bb0203f0$31060bd0$@co.in> <532C4FD8.7030007@alum.mit.edu> <00c701cf4684$774e6ed0$65eb4c70$@co.in> <532F1F02.4010500@alum.mit.edu>
In-Reply-To: <532F1F02.4010500@alum.mit.edu>
Date: Mon, 24 Mar 2014 06:21:55 +0530
Message-ID: <000d01cf46fb$44eea5a0$cecbf0e0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac9GwHZV2lkOLEUaRoqY00sv64ZuKAAOh9Hw
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020201.532F81B4.0072, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 172.18.214.93
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/c8xjZb_WHJSsnhHZw5Jt3YtXJrw
Subject: Re: [siprec] SIPREC Milestone Update.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 24 Mar 2014 00:52:10 -0000

Hi Paul,

We are in the same page w.r.t RTP based doc/app/screen sharing and also, RFC
5547 usage within MSRP.

Thanks
Partha

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> Sent: Sunday, March 23, 2014 11:21 PM
> To: Parthasarathi R; 'Hutton, Andrew'; siprec@ietf.org
> Subject: Re: [siprec] SIPREC Milestone Update.
> 
> On 3/23/14 6:41 AM, Parthasarathi R wrote:
> > Hi Paul,
> >
> > Please read inline.
> >
> > Thanks
> > Partha
> >
> >> -----Original Message-----
> >> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> >> Sent: Friday, March 21, 2014 8:13 PM
> >> To: Parthasarathi R; 'Hutton, Andrew'; siprec@ietf.org
> >> Subject: Re: [siprec] SIPREC Milestone Update.
> >>
> >> On 3/20/14 6:49 PM, Parthasarathi R wrote:
> >>> Hi Paul & all,
> >>>
> >>> I understand that screen sharing shall be considered as a video
> >> stream. I'm
> >>> interested in knowing how RTP media is used for application and
> >> document
> >>> sharing.
> >>
> >> My intent is to treat them exactly the same. And while the focus is
> on
> >> video, the sharing can also extend to audio and RTT.
> >>
> > <Partha> Agreed as it applies to some of the usecases wherein sharing
> is the
> > focus. But we need to consider the usecase wherein screen sharing as
> video
> > stream whereas the audio & RTT as the regular communication session,
> this
> > helps for debugging sort of scenario </Partha>
> 
> Certainly. Each media stream may be for doc/app/screen sharing, or for
> normal interactive communications. There could be streams of any type
> for each in any given CS. It will be the task of metadata to
> distinguish
> the intent of each stream.
> 
> >>> Also, I'm interested in knowing whether RFC 5547 (A Session
> >> Description
> >>> Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer) will
> >> be
> >>> covered within MSRP recording deliverable or not.
> >>
> >> I'd like to have discussion of that.
> >>
> >> I think it makes sense to include it. The way that works, I think
> the
> >> SRS would have the option to accept or reject each file transfer,
> and
> >> might decide to refuse some or all of them. Also, in general for
> MSRP
> >> the SRS will have the option to select which content types it
> accepts.
> >> So I think the SRS has reasonable control to accept what it is
> prepared
> >> to record and reject things that are irrelevant or too costly to
> >> record.
> >>
> > <Partha> Thanks for the clarification about your point of view. I
> agree with
> > you that there should be option to select or reject in SRS. Please
> include
> > the initial text in your MSRP draft (draft-yan-siprec-msrp-recording)
> for
> > more discussion. </Partha>
> 
> OK. In next version.
> 
> Note that the SRS is already free to select or reject any given media
> for recording - either be refusing to receive it, or by receiving it by
> not recording it. What we get here are more tools for selecting what to
> receive.
> 
> 	Thanks,
> 	Paul
> 
> >> 	Thanks,
> >> 	Paul
> >>
> >>> Thanks
> >>> Partha
> >>>
> >>>> -----Original Message-----
> >>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Hutton,
> >>>> Andrew
> >>>> Sent: Thursday, March 20, 2014 11:09 PM
> >>>> To: Paul Kyzivat; siprec@ietf.org
> >>>> Subject: Re: [siprec] SIPREC Milestone Update.
> >>>>
> >>>> I would like to hear what others in the WG think.
> >>>>
> >>>> Andy
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> >>>>> Sent: 20 March 2014 15:12
> >>>>> To: Hutton, Andrew
> >>>>> Cc: siprec@ietf.org
> >>>>> Subject: Re: SIPREC Milestone Update.
> >>>>>
> >>>>> On 3/20/14 5:13 AM, Hutton, Andrew wrote:
> >>>>>> Paul,
> >>>>>>
> >>>>>> The feedback we had during the IETF88 (Vancouver) meeting was
> that
> >>>> we
> >>>>> could not extend SIPREC to generically cover "document &
> >> application"
> >>>>> sharing as there is no standard to base this on.
> >>>>>>
> >>>>>> Can you suggest a milestone that is more precise that we can get
> >>>>> consensus on?
> >>>>>
> >>>>> Does the following work for you?
> >>>>>
> >>>>>      Protocol and metadata for using RTP media to record the
> sharing
> >>>>>      of applications, documents and screens.
> >>>>>
> >>>>> 	Thanks,
> >>>>> 	Paul
> >>>>>
> >>>>>> Andy
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> >>>>>>> Sent: 14 March 2014 14:36
> >>>>>>> To: Hutton, Andrew; siprec@ietf.org
> >>>>>>> Subject: Re: SIPREC Milestone Update.
> >>>>>>>
> >>>>>>> Andy,
> >>>>>>>
> >>>>>>> On 3/13/14 2:49 PM, Hutton, Andrew wrote:
> >>>>>>>> During the IETF89 SIPREC meeting a discrepancy was identified
> >>>>> between
> >>>>>>> my slides showing the proposed new milestones and Paul's
> slides.
> >>>>>>>>
> >>>>>>>> The chairs slides stated the following milestone:
> >>>>>>>>
> >>>>>>>> "??? 2014 	Protocol and metadata for capturing the content
> (RFC
> >>>>>>> 4796) of the media stream".
> >>>>>>>>
> >>>>>>>> Whilst Paul's conference recording slides stated
> >>>>>>>>
> >>>>>>>> "Dec 2014	Protocol and metadata for recording of document
> &
> >>>>>>> application sharing to IESG as Proposed Standard RFC"
> >>>>>>>>
> >>>>>>>> I posted this suggested change to the list as can be seen in
> the
> >>>>>>> message below and received no comments. The rational for the
> >>>>> suggestion
> >>>>>>> is also given in the text below but is basically that we did
> not
> >>>>> have
> >>>>>>> consensus for recording of document and application sharing
> just
> >>>> for
> >>>>>>> video with reference to the content.
> >>>>>>>>
> >>>>>>>> Please give feedback as to whether the milestone with
> reference
> >>>> to
> >>>>>>> RFC 4796 makes sense.
> >>>>>>>
> >>>>>>> IMO limiting this to RFC 4796 is too narrow for the milestone.
> It
> >>>>> may
> >>>>>>> turn out that 4796 is *part* of the mechanism, but I certainly
> >>>> don't
> >>>>>>> want to be limited to that. While it needs discussion, I have
> in
> >>>>> mind
> >>>>>>> to
> >>>>>>> capture additional metadata, such as:
> >>>>>>> - the distinction between document, application, and screen
> >>>> sharing
> >>>>>>> - the name of the document or application
> >>>>>>>
> >>>>>>> These won't always be available, but if they are they would be
> >>>>> useful
> >>>>>>> to
> >>>>>>> record.
> >>>>>>>
> >>>>>>> Also, while the intent is to capture presentations using video
> >>>> (and
> >>>>>>> perhaps audio) media streams, we *may* also want to say
> something
> >>>>> about
> >>>>>>> *how* this is done.
> >>>>>>>
> >>>>>>> And, if the presentation media includes audio as well as video,
> >>>> and
> >>>>> the
> >>>>>>> audio is distinct from the "room audio", we may want metadata
> to
> >>>> tie
> >>>>>>> the
> >>>>>>> audio and video together.
> >>>>>>>
> >>>>>>> Note that I've phrased the above as *may* because IMO this
> stuff
> >>>> is
> >>>>> all
> >>>>>>> subject to debate. But I would like it to be within the scope
> of
> >>>> the
> >>>>>>> milestone.
> >>>>>>>
> >>>>>>> That is why I phrased the milestone the way I did.
> >>>>>>>
> >>>>>>> The date for the milestone is another question. The December
> date
> >>>> is
> >>>>>>> probably a little optimistic, but I'd rather do that than have
> it
> >>>> be
> >>>>>>> pessimistic and just dawdle. But in the end the milestone dates
> >>>> are
> >>>>>>> really up to the chairs and ADs.
> >>>>>>>
> >>>>>>> 	Thanks,
> >>>>>>> 	Paul
> >>>>>>>
> >>>>>>>> Regards
> >>>>>>>> Andy
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of
> >>>> Hutton,
> >>>>>>>>> Andrew
> >>>>>>>>> Sent: 23 December 2013 15:24
> >>>>>>>>> To: Paul Kyzivat; siprec@ietf.org
> >>>>>>>>> Subject: Re: [siprec] Reminder: Additional use cases for
> draft-
> >>>>>>> kyzivat-
> >>>>>>>>> siprec-conference-use-cases-00
> >>>>>>>>>
> >>>>>>>>> Hi All,
> >>>>>>>>>
> >>>>>>>>> Since nobody posted any new uses cases I went back to our
> >>>>> discussion
> >>>>>>> in
> >>>>>>>>> Vancouver and tried to see what we appeared to have consensus
> >> on
> >>>>> in
> >>>>>>> the
> >>>>>>>>> meeting.
> >>>>>>>>>
> >>>>>>>>>     From that I have formed a proposal for a charter update
> >> which
> >>>> is
> >>>>>>> given
> >>>>>>>>> below and also attached (with changes highlighted).
> >>>>>>>>>
> >>>>>>>>> It seems everybody agreed that we need to clarify that SIPREC
> >> is
> >>>>>>>>> limited to SIP based systems and that MSRP recording needs to
> >> be
> >>>>>>> added.
> >>>>>>>>>
> >>>>>>>>> It also seemed to me that there was no consensus on adding
> the
> >>>>>>> generic
> >>>>>>>>> case of document/application sharing but if this was limited
> to
> >>>>>>> being a
> >>>>>>>>> video session in which the content type (RFC 4796) formed
> part
> >>>> of
> >>>>>>> the
> >>>>>>>>> metadata then probably we would have consensus.  So I
> included
> >> a
> >>>>>>>>> suggested reference to this as a milestone please comment on
> >>>>> whether
> >>>>>>>>> this makes sense.
> >>>>>>>>>
> >>>>>>>>> There was a lot of discussion in the Vancouver meeting about
> >>>>>>> defining a
> >>>>>>>>> generic mechanism to record media without the need to come
> back
> >>>> to
> >>>>>>>>> SIPREC every time new media types or metadata needs to be
> >>>>> recorded.
> >>>>>>>>> There has been no use cases submitted or discussion on
> possible
> >>>>>>>>> mechanism since the meeting so I see no way to progress this
> at
> >>>>>>>>> present.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Please can provide comments and Paul and others who stated
> they
> >>>>>>> would
> >>>>>>>>> contribute can you confirm that you still intend to do so and
> >>>> that
> >>>>>>> this
> >>>>>>>>> charter proposal is acceptable to you.
> >>>>>>>>>
> >>>>>>>>> Regards
> >>>>>>>>> Andy
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> =====================================
> >>>>>>>>> SUGGESTED CHARTER - UPDATE
> >>>>>>>>> =====================================
> >>>>>>>>>
> >>>>>>>>> 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, business analytics, or consumer protection.
> >>>>>>> Recording
> >>>>>>>>> is typically done by sending a copy of the media to the
> >>>> recording
> >>>>>>>>> devices. The working group will determine requirements and
> >>>> produce
> >>>>> a
> >>>>>>>>> specification for a protocol that will manage delivery of
> >> media,
> >>>>> in
> >>>>>>> SIP
> >>>>>>>>> based systems (including audio, video, MSRP instant message
> >>>>>>> sessions)
> >>>>>>>>> from an end-point that originates media, or that has access
> to
> >>>> it,
> >>>>>>> to a
> >>>>>>>>> recording device. PBX and recording vendors today implement
> >>>>>>>>> proprietary, incompatible mechanisms to facilitate recording.
> A
> >>>>>>>>> standard protocol will reduce the complexity and cost of
> >>>> providing
> >>>>>>> such
> >>>>>>>>> recording services.
> >>>>>>>>>
> >>>>>>>>> The group will define these issues and rationalize with IETF
> >>>>>>> standards
> >>>>>>>>> and practices. This includes encryption, NAT traversal,
> >>>> operations
> >>>>>>> and
> >>>>>>>>> manageability, SIP-enabled firewalls, authorization, and
> >>>> security.
> >>>>>>>>> The scope explicitly does not include recording any of the
> >>>>> extended
> >>>>>>>>> session attributes being defined by the CLUE WG. (These may
> be
> >>>>>>>>> addressed by a subsequent effort.)
> >>>>>>>>>
> >>>>>>>>> The group will produce:
> >>>>>>>>>
> >>>>>>>>> * Updated Requirements, Use Cases, Architecture draft
> >>>>>>>>>
> >>>>>>>>> * Specification for Session Recording Protocol and Metadata
> >>>>>>>>>
> >>>>>>>>> Milestones
> >>>>>>>>>
> >>>>>>>>> DONE   	Use Cases and Requirements to IESG as Informational
> >>>>> RFC
> >>>>>>>>> MAR 2014 	Submit Architecture to IESG as Informational
> RFC
> >>>>>>>>> JUN 2014 	Submit protocol draft to IESG as Proposed
> Standard
> >>>>>>> RFC
> >>>>>>>>> AUG 2014 	Submit Metadata model and format to IESG as
> Proposed
> >>>>>>>>> Standard RFC
> >>>>>>>>> AUG 2014 	Submit SIPREC Call Flows draft to IESG as an
> >>>>>>> informational
> >>>>>>>>> RFC
> >>>>>>>>> ??? 2014 	Conference Recording Use Cases and Requirements
> to
> >>>>>>> IESG as
> >>>>>>>>> Informational RFC
> >>>>>>>>> ??? 2014 	Conference Recording Architecture to IESG as
> >>>>>>> Informational
> >>>>>>>>> RFC
> >>>>>>>>> ??? 2014 	Protocol and metadata for MSRP recording to
> IESG as
> >>>>>>>>> Proposed Standard RFC
> >>>>>>>>> ??? 2014 	Protocol and metadata for capturing the content
> (RFC
> >>>>>>> 4796)
> >>>>>>>>> of the media stream.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>>>
> >>
> =======================================================================
> >>>>>>>>> =====================
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> -----Original Message-----
> >>>>>>>>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of
> >> Paul
> >>>>>>>>> Kyzivat
> >>>>>>>>>> Sent: 21 November 2013 18:44
> >>>>>>>>>> To: siprec@ietf.org
> >>>>>>>>>> Subject: Re: [siprec] Reminder: Additional use cases for
> >> draft-
> >>>>>>>>> kyzivat-
> >>>>>>>>>> siprec-conference-use-cases-00
> >>>>>>>>>>
> >>>>>>>>>> I still haven't seen anything on this subject.
> >>>>>>>>>> I *thought* there were multiple people in the siprec session
> >> in
> >>>>>>>>>> Vancouver that seemed to have other use cases related to
> >> media.
> >>>>>>>>>>
> >>>>>>>>>> If so, better speak up, or IIUC we are going to treat the
> use
> >>>>> cases
> >>>>>>>>> we
> >>>>>>>>>> have as bounding the new scope.
> >>>>>>>>>>
> >>>>>>>>>> 	Thanks,
> >>>>>>>>>> 	Paul
> >>>>>>>>>>
> >>>>>>>>>> On 11/15/13 9:31 AM, Paul Kyzivat wrote:
> >>>>>>>>>>> One of the action items from the meeting last week was:
> >>>>>>>>>>>
> >>>>>>>>>>>> chairs: use cases to the list in the next couple of weeks.
> >>>>> After
> >>>>>>>>>> that,
> >>>>>>>>>>>> we will decide if we need charter language.  If your use
> >> case
> >>>>> is
> >>>>>>>>> not
> >>>>>>>>>>>> contributed, it will not be considered in the milestones.
> >>>>>>>>>>>
> >>>>>>>>>>> The above is a little vague about the timing. Two weeks
> from
> >>>> the
> >>>>>>>>> end
> >>>>>>>>>> of
> >>>>>>>>>>> the meeting would be Friday, November 23. (Hopefully the
> >>>> chairs
> >>>>>>>>> will
> >>>>>>>>>>> clarify this.)
> >>>>>>>>>>>
> >>>>>>>>>>> This is important because there was some desire to tighten
> up
> >>>>> the
> >>>>>>>>>> scope
> >>>>>>>>>>> of the rechartering to encompass only the mentioned use
> >> cases.
> >>>>>>>>>>>
> >>>>>>>>>>> I'll be happy to incorporate additional popular use cases
> >> even
> >>>>>>>>> before
> >>>>>>>>>>> this draft becomes a wg draft. (But please send text.)
> >>>>>>>>>>>
> >>>>>>>>>>> While the name of the draft is about conferences, the use
> >>>> cases
> >>>>>>>>>> include
> >>>>>>>>>>> additional media support. (Maybe we should rename the
> draft.)
> >>>>> And
> >>>>>>>>> it
> >>>>>>>>>>> seemed that much of the interest was about additional
> media.
> >>>>>>>>>>>
> >>>>>>>>>>>          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
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>> _______________________________________________
> >>>> siprec mailing list
> >>>> siprec@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/siprec
> >>>
> >>>
> >
> >

