From partha@parthasarathi.co.in Sun Nov 3 01:22:26 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0161211E81C4 for ; Sun, 3 Nov 2013 01:22:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.8 X-Spam-Level: X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[AWL=-1.135, BAYES_50=0.001, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k7yr+Uuvy8bH for ; Sun, 3 Nov 2013 01:22:21 -0800 (PST) Received: from smtp.mailhostbox.com (outbound-us2.mailhostbox.com [69.93.141.234]) by ietfa.amsl.com (Postfix) with ESMTP id D5C5921E8082 for ; Sun, 3 Nov 2013 01:22:20 -0800 (PST) Received: from userPC (unknown [122.179.43.26]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id DB205638CD9; Sun, 3 Nov 2013 09:22:13 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1383470539; bh=2krs/oSWnJPznBlbUyBhvrrEqifIj/oJpXJWxUWf4q8=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=MiyNM06xUiVQzkVhb+PDF+aKqd5FRgPcMmrMV2iPVPbZ3C5jqgIFuR8ZnYCsEBqT0 FIn2mPae0bzRof0bByap0rIzwC/8PcRikgGqNzdXkHyUtr4jFSCTQrK9ZzCmV5Z+sH V5Xwv9xzJx03YWAp0rkO7VCD1Ky9+mhX4kA6zrbA= From: "Parthasarathi R" To: "'Paul Kyzivat'" , "'Hutton, Andrew'" , "'Michael Smith'" References: <9F33F40F6F2CD847824537F3C4E37DDF17C05C82@MCHP04MSX.global-ad.net> <001501ced3f9$2cec6390$86c52ab0$@co.in> <9F33F40F6F2CD847824537F3C4E37DDF17C20C0F@MCHP04MSX.global-ad.net>, <006401ced404$e7695240$b63bf6c0$@com> <002601ced43c$6a0ce7c0$3e26b740$@co.in> <526FE61B.6090204@alum.mit.edu> In-Reply-To: <526FE61B.6090204@alum.mit.edu> Date: Sun, 3 Nov 2013 14:52:10 +0530 Message-ID: <000701ced876$31d00520$95700f60$@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: Ac7Uxj8+wjcOHSUxQEaCyiwSfQqGRQDr64HA Content-Language: en-us X-CTCH-RefID: str=0001.0A020208.527615CB.0087, ss=1, re=0.100, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.100 X-CTCH-Rules: SUBJECT_NEEDS_ENCODING, 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-Scanned-By: MIMEDefang 2.72 on 70.87.28.142 Cc: siprec@ietf.org Subject: Re: [siprec] IETF 88 - SIPREC Draft Agenda X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Nov 2013 09:22:26 -0000 Paul, Thanks for the clarification. Thanks Partha > -----Original Message----- > From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu] > Sent: Tuesday, October 29, 2013 10:15 PM > To: Parthasarathi R; 'Hutton, Andrew'; 'Michael Smith' > Cc: 'Brian Rosen'; siprec@ietf.org > Subject: Re: [siprec] IETF 88 - SIPREC Draft Agenda > > On 10/28/13 8:18 PM, Parthasarathi R wrote: > > > Also, I hope that the new charter will not impact the metadata draft > > progress and the new usecase will incorporate its metadata > enhancement in > > the respective draft itself. > > It has never been our intent to slow down the existing work. We just > want to prime the pipeline for things to follow that. > > IMO it would be fine for the chairs to do whatever they must to ensure > work is suitably prioritized. > > In my own case, having been involved with the metadata from the > beginning, I view my part as "done" unless reviews by others identify > things that need fixing. > > Thanks, > Paul From andrew.hutton@unify.com Tue Nov 5 08:40:08 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92C4321E81DA for ; Tue, 5 Nov 2013 08:40:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.419 X-Spam-Level: X-Spam-Status: No, score=-2.419 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PFyTSBg3BoBo for ; Tue, 5 Nov 2013 08:40:01 -0800 (PST) Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 2E09721E81D6 for ; Tue, 5 Nov 2013 08:38:44 -0800 (PST) Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx12.unify.com (Server) with ESMTP id E5C8F23F05F5 for ; Tue, 5 Nov 2013 17:38:42 +0100 (CET) Received: from MCHP04MSX.global-ad.net ([169.254.1.69]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 17:38:42 +0100 From: "Hutton, Andrew" To: "siprec@ietf.org" Thread-Topic: SIPREC Dinner or Lunch at IETF88 Thread-Index: Ac7aRXvz0jWwoCHuQBqcT+9plNF28Q== Date: Tue, 5 Nov 2013 16:38:41 +0000 Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17C2F42C@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_9F33F40F6F2CD847824537F3C4E37DDF17C2F42CMCHP04MSXglobal_" MIME-Version: 1.0 Subject: [siprec] SIPREC Dinner or Lunch at IETF88 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 16:40:09 -0000 --_000_9F33F40F6F2CD847824537F3C4E37DDF17C2F42CMCHP04MSXglobal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Anybody want to have some lunch/dinner this week and discuss charter text a= nd the proposed conference recording use cases? If so I would be available tonight or tomorrow. Andy --_000_9F33F40F6F2CD847824537F3C4E37DDF17C2F42CMCHP04MSXglobal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Anybody want to have some lunch/dinner this week and discuss charter t= ext and the proposed conference recording use cases?
 
If so I would be available tonight or tomorrow.
 
Andy
 
 --_000_9F33F40F6F2CD847824537F3C4E37DDF17C2F42CMCHP04MSXglobal_-- From pkyzivat@alum.mit.edu Tue Nov 5 09:31:45 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8CDF11E80D9 for ; Tue, 5 Nov 2013 09:31:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.437 X-Spam-Level: X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4otBq4k211IR for ; Tue, 5 Nov 2013 09:31:39 -0800 (PST) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id BA12811E81A3 for ; Tue, 5 Nov 2013 09:31:35 -0800 (PST) Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta14.westchester.pa.mail.comcast.net with comcast id loph1m0070ldTLk5EtXYG4; Tue, 05 Nov 2013 17:31:32 +0000 Received: from dhcp-a502.meeting.ietf.org ([31.133.165.2]) by omta04.westchester.pa.mail.comcast.net with comcast id ltVP1m00P03RZsX01tVRrR; Tue, 05 Nov 2013 17:29:30 +0000 Message-ID: <52792AF6.1010201@alum.mit.edu> Date: Tue, 05 Nov 2013 09:29:26 -0800 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: siprec@ietf.org References: <9F33F40F6F2CD847824537F3C4E37DDF17C2F42C@MCHP04MSX.global-ad.net> In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17C2F42C@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=1383672692; bh=62Mdwfc1RAelXDbXVoST5oN+eDLCGi2at3C54jrIBL4=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Y6Xj1KQ93QLARuHkP+8fBFWP3PovLkysv7MSvhqB2BmjdCDkaxgEcy1IoTGZvjC4G wQDVMw7au2vnc7sZxwFBU1AjRGgW9ebqeOuUYVw8kcFoYjJhKsjq5q7gMud8sDdhk2 zWz38TZcHKnHh3DIjsqZXfOqsFYTFe12AE3qUVVgqotvG0U4j+Y6Peb5Fq8qz1Es8I zQnzFtjR3ihZyEGKwe/06wPdUmqny6mkLJeSb8jDqbvx/VmZzqplCRMzhMiQrdoGcS 60xbku9cHs7M7lGKHgD2w4Goom+WQVugwGDlx2C5FWgItHdkQK5IZoBrzfusd3RawE A1SkLjtXpIeXg== Subject: Re: [siprec] SIPREC Dinner or Lunch at IETF88 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 17:31:45 -0000 Sure, that would be great. I'm available for dinner W-F and lunch on Th. Thanks, Paul On 11/5/13 8:38 AM, Hutton, Andrew wrote: > Anybody want to have some lunch/dinner this week and discuss charter > text and the proposed conference recording use cases? > If so I would be available tonight or tomorrow. > Andy > > > _______________________________________________ > siprec mailing list > siprec@ietf.org > https://www.ietf.org/mailman/listinfo/siprec > From br@brianrosen.net Tue Nov 5 09:54:45 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 254BF21F9E40 for ; Tue, 5 Nov 2013 09:54:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.491 X-Spam-Level: X-Spam-Status: No, score=-103.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJFS5LzCccnm for ; Tue, 5 Nov 2013 09:54:39 -0800 (PST) Received: from mail-qe0-f41.google.com (mail-qe0-f41.google.com [209.85.128.41]) by ietfa.amsl.com (Postfix) with ESMTP id AB10E21E8137 for ; Tue, 5 Nov 2013 09:54:08 -0800 (PST) Received: by mail-qe0-f41.google.com with SMTP id x7so5237056qeu.0 for ; Tue, 05 Nov 2013 09:54:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=YAvXbcY/JeJ9B2VeEu8hQWlswXSYm6moQE3ftirXFNQ=; b=j7SxC/dxPAS8cHlTEUOaauadf58CO0rohen3XwJtHd23tN6GHgtO2QJKPHL6oT2fJ7 uMqv+GoS86kCzv4/UuwfbPq9jvaewuk5NKe204EQKwNVeoGXITQ+xD/+oLgjcMYux0aX S6Sc4U+QkeDE7SDjgDgRZE6sIFEFiNHfCggysoc+GefPpxxNOsxfqHWq5r5/HRRulSEc y9bPevgX6eK8zKEsmQO4ufDMnmN637LdCGMGE3cMC1fEvZRHxil/QKRd7tU19r8eYu1f WuJ/To+kP2/uTk2HQEjZTIUamEPal/HWS956cx+savZ5KUXBB/t33gWExfzYiPw9ded0 YYNA== X-Gm-Message-State: ALoCoQn+dZZIyvL+WEHWbKwWuWAF5V0vHzjhzZnahRxqiGBXjvnVXLJhhU75uJjTo4Bwwslwy83d X-Received: by 10.49.24.74 with SMTP id s10mr31593594qef.24.1383674047980; Tue, 05 Nov 2013 09:54:07 -0800 (PST) Received: from [192.168.128.255] (neustargw.va.neustar.com. [209.173.53.233]) by mx.google.com with ESMTPSA id h9sm69477323qaq.9.2013.11.05.09.54.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Nov 2013 09:54:07 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) From: Brian Rosen In-Reply-To: <52792AF6.1010201@alum.mit.edu> Date: Tue, 5 Nov 2013 09:53:58 -0800 Content-Transfer-Encoding: 7bit Message-Id: <9E5FAE41-6273-403F-9B01-3943392EF3B9@brianrosen.net> References: <9F33F40F6F2CD847824537F3C4E37DDF17C2F42C@MCHP04MSX.global-ad.net> <52792AF6.1010201@alum.mit.edu> To: Paul Kyzivat X-Mailer: Apple Mail (2.1816) Cc: siprec@ietf.org Subject: Re: [siprec] SIPREC Dinner or Lunch at IETF88 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 17:54:45 -0000 Wed Dinner perhaps? Brian On Nov 5, 2013, at 9:29 AM, Paul Kyzivat wrote: > Sure, that would be great. I'm available for dinner W-F and lunch on Th. > > Thanks, > Paul > > On 11/5/13 8:38 AM, Hutton, Andrew wrote: >> Anybody want to have some lunch/dinner this week and discuss charter >> text and the proposed conference recording use cases? >> If so I would be available tonight or tomorrow. >> Andy >> >> >> _______________________________________________ >> siprec mailing list >> siprec@ietf.org >> https://www.ietf.org/mailman/listinfo/siprec >> > > _______________________________________________ > siprec mailing list > siprec@ietf.org > https://www.ietf.org/mailman/listinfo/siprec From pkyzivat@alum.mit.edu Tue Nov 5 10:10:03 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC5F421E8195 for ; Tue, 5 Nov 2013 10:10:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.437 X-Spam-Level: X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xTSD1Vf1rt-J for ; Tue, 5 Nov 2013 10:09:48 -0800 (PST) Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 9C36D21E808A for ; Tue, 5 Nov 2013 10:09:44 -0800 (PST) Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta03.westchester.pa.mail.comcast.net with comcast id lpr11m0081HzFnQ53u9kyD; Tue, 05 Nov 2013 18:09:44 +0000 Received: from dhcp-a502.meeting.ietf.org ([31.133.165.2]) by omta14.westchester.pa.mail.comcast.net with comcast id lu7Z1m00W03RZsX3au7brm; Tue, 05 Nov 2013 18:07:42 +0000 Message-ID: <527933E8.4080905@alum.mit.edu> Date: Tue, 05 Nov 2013 10:07:36 -0800 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Brian Rosen References: <9F33F40F6F2CD847824537F3C4E37DDF17C2F42C@MCHP04MSX.global-ad.net> <52792AF6.1010201@alum.mit.edu> <9E5FAE41-6273-403F-9B01-3943392EF3B9@brianrosen.net> In-Reply-To: <9E5FAE41-6273-403F-9B01-3943392EF3B9@brianrosen.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=1383674984; bh=LfWBRJmZH9AlCT/l7ki5sVLM97cQDzpy691G5Z8bBug=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=PKed5O7mapC6p6uic10OUUjaxwFBUn96cknfOmbGyd/a3PHzrS22fMm0LhAHzKpmH dGxBKJ/WsKDxyR3vR/73ijVp0/saOYl60JgeO9Ty+njb6H+NhOZwxSl7SpPn4zstGh b5AIae27oOFGqfZkEOooOOmHtoTcb5cu6BPFCLUuoTB7iFAn3foFGHhNfGg2Fv/5Tz qAYZWZ2Q1ZN7j0a4SDDts+bUeXrzjw4ODfNPzHLbXO0Ne39j6dDomqMJ4MgXtrJhcp e8FYjHeDnONrEVKbHEHYsrUOsbuiwvKxT6fn/jYNs+Ufn6kndndkG5m8bL5YiT/c63 s9HJfH6JaZOrw== Cc: siprec@ietf.org Subject: Re: [siprec] SIPREC Dinner or Lunch at IETF88 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 18:10:03 -0000 On 11/5/13 9:53 AM, Brian Rosen wrote: > Wed Dinner perhaps? WFM. I'm temporarily holding that time pending a firm decision. Thanks, Paul > Brian > > On Nov 5, 2013, at 9:29 AM, Paul Kyzivat wrote: > >> Sure, that would be great. I'm available for dinner W-F and lunch on Th. >> >> Thanks, >> Paul >> >> On 11/5/13 8:38 AM, Hutton, Andrew wrote: >>> Anybody want to have some lunch/dinner this week and discuss charter >>> text and the proposed conference recording use cases? >>> If so I would be available tonight or tomorrow. >>> Andy >>> >>> >>> _______________________________________________ >>> siprec mailing list >>> siprec@ietf.org >>> https://www.ietf.org/mailman/listinfo/siprec >>> >> >> _______________________________________________ >> siprec mailing list >> siprec@ietf.org >> https://www.ietf.org/mailman/listinfo/siprec > > From andrew.hutton@unify.com Tue Nov 5 13:36:25 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 770D421E8099 for ; Tue, 5 Nov 2013 13:36:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.441 X-Spam-Level: X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[AWL=0.158, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ZVDqHEjshDx for ; Tue, 5 Nov 2013 13:36:04 -0800 (PST) Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 911E811E80E3 for ; Tue, 5 Nov 2013 13:36:03 -0800 (PST) Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx11.unify.com (Server) with ESMTP id AE16E1EB862E; Tue, 5 Nov 2013 22:36:02 +0100 (CET) Received: from MCHP04MSX.global-ad.net ([169.254.1.69]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 22:36:02 +0100 From: "Hutton, Andrew" To: Paul Kyzivat , Brian Rosen Thread-Topic: [siprec] SIPREC Dinner or Lunch at IETF88 Thread-Index: AQHO2lJYSGJzoeKxEE2LcoYDg9re9ZoXJ1Kg Date: Tue, 5 Nov 2013 21:36:01 +0000 Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17C30007@MCHP04MSX.global-ad.net> References: <9F33F40F6F2CD847824537F3C4E37DDF17C2F42C@MCHP04MSX.global-ad.net> <52792AF6.1010201@alum.mit.edu> <9E5FAE41-6273-403F-9B01-3943392EF3B9@brianrosen.net> <527933E8.4080905@alum.mit.edu> In-Reply-To: <527933E8.4080905@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 Cc: "siprec@ietf.org" Subject: Re: [siprec] SIPREC Dinner or Lunch at IETF88 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 21:36:26 -0000 Ok with me let's make it Wednesday lunch meet at the registration desk. Others are welcome. Andy > -----Original Message----- > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On > Behalf Of Paul Kyzivat > Sent: 05 November 2013 10:08 > To: Brian Rosen > Cc: siprec@ietf.org > Subject: Re: [siprec] SIPREC Dinner or Lunch at IETF88 >=20 > On 11/5/13 9:53 AM, Brian Rosen wrote: > > Wed Dinner perhaps? >=20 > WFM. I'm temporarily holding that time pending a firm decision. >=20 > Thanks, > Paul >=20 > > Brian > > > > On Nov 5, 2013, at 9:29 AM, Paul Kyzivat > wrote: > > > >> Sure, that would be great. I'm available for dinner W-F and lunch on > Th. > >> > >> Thanks, > >> Paul > >> > >> On 11/5/13 8:38 AM, Hutton, Andrew wrote: > >>> Anybody want to have some lunch/dinner this week and discuss > charter > >>> text and the proposed conference recording use cases? > >>> If so I would be available tonight or tomorrow. > >>> Andy > >>> > >>> > >>> _______________________________________________ > >>> siprec mailing list > >>> siprec@ietf.org > >>> https://www.ietf.org/mailman/listinfo/siprec > >>> > >> > >> _______________________________________________ > >> siprec mailing list > >> siprec@ietf.org > >> https://www.ietf.org/mailman/listinfo/siprec > > > > >=20 > _______________________________________________ > siprec mailing list > siprec@ietf.org > https://www.ietf.org/mailman/listinfo/siprec From br@brianrosen.net Tue Nov 5 14:19:20 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E317921E80AA for ; Tue, 5 Nov 2013 14:19:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.494 X-Spam-Level: X-Spam-Status: No, score=-103.494 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZdC+cK7ubIUf for ; Tue, 5 Nov 2013 14:19:15 -0800 (PST) Received: from mail-qe0-f41.google.com (mail-qe0-f41.google.com [209.85.128.41]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1DF21E80CE for ; Tue, 5 Nov 2013 14:19:12 -0800 (PST) Received: by mail-qe0-f41.google.com with SMTP id x7so5524810qeu.14 for ; Tue, 05 Nov 2013 14:19:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=ZpFG+bQBMtel7COy9op51zzX7Z+Py+vNwYJay4y7h6w=; b=TSDVi3sEqhGmnwIoJINIqeMBFNU3h3mAjYcYcUV6WTmnDAVH1eLGFK3D+xehx0yaT3 rXEEyNV8RLsa6t99QH56hvuNVYQ/B3lpAKs3eEtY198/cgiCAlgb6eK+ZoAKqVL+0vL8 e9QmmRBZWjp7KlYcfyph8B4TTC5nFtAkXfJ65/E13iYop1QtGi+QGpTxtxX1C5G7dszg qAT0DQ9OBKxP0CkHW8DLOj8q3XcOKRVJA8RYUX6exlIURJ41kR2qs6Eo3qbhAjiDVbW0 //GylCLJ9TEpmnMHRjVxd7SXSQYpdxY9kzjVl8GWNtAGHk5UgwwLtMCny2ma2OkLtaqs GbEg== X-Gm-Message-State: ALoCoQnlI1wvHBcwdS6OfxlPjgR1YOGmH/+2/oGW+QEZz3Upx9x6LCsminr0DCpg2nwqdFs3loR5 X-Received: by 10.224.121.198 with SMTP id i6mr1224952qar.52.1383689951875; Tue, 05 Nov 2013 14:19:11 -0800 (PST) Received: from [192.168.128.255] (neustargw.va.neustar.com. [209.173.53.233]) by mx.google.com with ESMTPSA id h9sm71973611qaq.9.2013.11.05.14.19.09 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Nov 2013 14:19:10 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) From: Brian Rosen In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17C30007@MCHP04MSX.global-ad.net> Date: Tue, 5 Nov 2013 14:19:07 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <8C1E3105-205D-412F-A804-A4B5F1618222@brianrosen.net> References: <9F33F40F6F2CD847824537F3C4E37DDF17C2F42C@MCHP04MSX.global-ad.net> <52792AF6.1010201@alum.mit.edu> <9E5FAE41-6273-403F-9B01-3943392EF3B9@brianrosen.net> <527933E8.4080905@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C30007@MCHP04MSX.global-ad.net> To: "Hutton, Andrew" X-Mailer: Apple Mail (2.1816) Cc: "siprec@ietf.org" Subject: Re: [siprec] SIPREC Dinner or Lunch at IETF88 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 22:19:21 -0000 Can=92t do Wednesday lunch. Wed dinner I could do. Brian On Nov 5, 2013, at 1:36 PM, Hutton, Andrew = wrote: > Ok with me let's make it Wednesday lunch meet at the registration = desk. >=20 > Others are welcome. >=20 > Andy >=20 >> -----Original Message----- >> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On >> Behalf Of Paul Kyzivat >> Sent: 05 November 2013 10:08 >> To: Brian Rosen >> Cc: siprec@ietf.org >> Subject: Re: [siprec] SIPREC Dinner or Lunch at IETF88 >>=20 >> On 11/5/13 9:53 AM, Brian Rosen wrote: >>> Wed Dinner perhaps? >>=20 >> WFM. I'm temporarily holding that time pending a firm decision. >>=20 >> Thanks, >> Paul >>=20 >>> Brian >>>=20 >>> On Nov 5, 2013, at 9:29 AM, Paul Kyzivat >> wrote: >>>=20 >>>> Sure, that would be great. I'm available for dinner W-F and lunch = on >> Th. >>>>=20 >>>> Thanks, >>>> Paul >>>>=20 >>>> On 11/5/13 8:38 AM, Hutton, Andrew wrote: >>>>> Anybody want to have some lunch/dinner this week and discuss >> charter >>>>> text and the proposed conference recording use cases? >>>>> If so I would be available tonight or tomorrow. >>>>> Andy >>>>>=20 >>>>>=20 >>>>> _______________________________________________ >>>>> siprec mailing list >>>>> siprec@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/siprec >>>>>=20 >>>>=20 >>>> _______________________________________________ >>>> siprec mailing list >>>> siprec@ietf.org >>>> https://www.ietf.org/mailman/listinfo/siprec >>>=20 >>>=20 >>=20 >> _______________________________________________ >> siprec mailing list >> siprec@ietf.org >> https://www.ietf.org/mailman/listinfo/siprec From andrew.hutton@unify.com Tue Nov 5 14:37:11 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F5221E80BA for ; Tue, 5 Nov 2013 14:37:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.45 X-Spam-Level: X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N90dChvYWdTf for ; Tue, 5 Nov 2013 14:37:05 -0800 (PST) Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 7DCC611E8125 for ; Tue, 5 Nov 2013 14:36:52 -0800 (PST) Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id 16C6123F049C; Tue, 5 Nov 2013 23:36:46 +0100 (CET) Received: from MCHP04MSX.global-ad.net ([169.254.1.69]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 23:36:45 +0100 From: "Hutton, Andrew" To: Brian Rosen , Barnes Mary Thread-Topic: [siprec] SIPREC Dinner or Lunch at IETF88 Thread-Index: AQHO2lJYSGJzoeKxEE2LcoYDg9re9ZoXJ1Kg///9W4CAABWwwg== Date: Tue, 5 Nov 2013 22:36:44 +0000 Message-ID: References: <9F33F40F6F2CD847824537F3C4E37DDF17C2F42C@MCHP04MSX.global-ad.net> <52792AF6.1010201@alum.mit.edu> <9E5FAE41-6273-403F-9B01-3943392EF3B9@brianrosen.net> <527933E8.4080905@alum.mit.edu> <9F33F40F6F2CD847824537F3C4E37DDF17C30007@MCHP04MSX.global-ad.net>, <8C1E3105-205D-412F-A804-A4B5F1618222@brianrosen.net> In-Reply-To: <8C1E3105-205D-412F-A804-A4B5F1618222@brianrosen.net> Accept-Language: en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "siprec@ietf.org" Subject: Re: [siprec] SIPREC Dinner or Lunch at IETF88 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 22:37:12 -0000 Sorry I messed up lets move to Dinner then. On 5 Nov 2013, at 14:19, "Brian Rosen" wrote: > Can=92t do Wednesday lunch. Wed dinner I could do. >=20 > Brian >=20 > On Nov 5, 2013, at 1:36 PM, Hutton, Andrew wrot= e: >=20 >> Ok with me let's make it Wednesday lunch meet at the registration desk. >>=20 >> Others are welcome. >>=20 >> Andy >>=20 >>> -----Original Message----- >>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On >>> Behalf Of Paul Kyzivat >>> Sent: 05 November 2013 10:08 >>> To: Brian Rosen >>> Cc: siprec@ietf.org >>> Subject: Re: [siprec] SIPREC Dinner or Lunch at IETF88 >>>=20 >>> On 11/5/13 9:53 AM, Brian Rosen wrote: >>>> Wed Dinner perhaps? >>>=20 >>> WFM. I'm temporarily holding that time pending a firm decision. >>>=20 >>> Thanks, >>> Paul >>>=20 >>>> Brian >>>>=20 >>>> On Nov 5, 2013, at 9:29 AM, Paul Kyzivat >>> wrote: >>>>=20 >>>>> Sure, that would be great. I'm available for dinner W-F and lunch on >>> Th. >>>>>=20 >>>>> Thanks, >>>>> Paul >>>>>=20 >>>>> On 11/5/13 8:38 AM, Hutton, Andrew wrote: >>>>>> Anybody want to have some lunch/dinner this week and discuss >>> charter >>>>>> text and the proposed conference recording use cases? >>>>>> If so I would be available tonight or tomorrow. >>>>>> Andy >>>>>>=20 >>>>>>=20 >>>>>> _______________________________________________ >>>>>> siprec mailing list >>>>>> siprec@ietf.org >>>>>> https://www.ietf.org/mailman/listinfo/siprec >>>>>=20 >>>>> _______________________________________________ >>>>> siprec mailing list >>>>> siprec@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/siprec >>>=20 >>> _______________________________________________ >>> siprec mailing list >>> siprec@ietf.org >>> https://www.ietf.org/mailman/listinfo/siprec >=20 From brian.rosen@neustar.biz Tue Nov 12 11:28:47 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE12111E8140 for ; Tue, 12 Nov 2013 11:28:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.22 X-Spam-Level: X-Spam-Status: No, score=-6.22 tagged_above=-999 required=5 tests=[AWL=0.379, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5zWSeJevNW6I for ; Tue, 12 Nov 2013 11:28:43 -0800 (PST) Received: from neustar.com (smartmail.neustar.com [156.154.17.104]) by ietfa.amsl.com (Postfix) with ESMTP id 501BE21E80C3 for ; Tue, 12 Nov 2013 11:28:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1384285116; x=1699644404; q=dns/txt; h=From:Subject:Date:Message-ID:Content-Language: Content-Type:Content-ID:Content-Transfer-Encoding; bh=llE2HpOUwf q/nx17dFAlslI9aJcXZDOGzvadBmhDptQ=; b=o06wgzzkd8YnutAA3SqTAcakHl n0WsGKZYQEB6JmH1QfGwH2MsIGmBUEiEd+z9zyGk0UFphRReH6Nvrly5rHWQ== Received: from ([10.31.58.69]) by stihiron1.va.neustar.com with ESMTP with TLS id J041124052.35477654; Tue, 12 Nov 2013 14:38:35 -0500 Received: from STNTEXMB10.cis.neustar.com ([169.254.5.5]) by stntexhc10.cis.neustar.com ([169.254.4.132]) with mapi id 14.02.0342.003; Tue, 12 Nov 2013 14:28:25 -0500 From: "Rosen, Brian" To: "siprec@ietf.org" Thread-Topic: Preliminary Minutes Thread-Index: AQHO391aIzq4BXAqNkOPMhPYqEmpEw== Date: Tue, 12 Nov 2013 19:28:24 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.33.193.19] x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: YhODVRfVMp8lBJnNE1EP+Q== Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [siprec] Preliminary Minutes X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2013 19:28:48 -0000 Please send corrections SIPREC IETF 88 minutes by Brian Rosen Working Group Status architecture draft almost done Protocol WGLC completed, comments being resolved Metatdata. Looking for implementation experience, NENA ICE8 happening this = week Protool Charles Eckel WGLC Complete, comments received from Paul, most dealt with on the list, in= V11. Mary: suggest early genart and security review Charis: agree Recording Preferences in SRC The must was dropped when adding the ability to announce recording in curre= nt or subsequent offer/answer Brian: did we drop MUST inadvertantly Paul: don't recall exactly, but make sure we don't have to send announcemen= t when we already have Charles: will discuss on list Paul: whenever you change state, you announce it SRS procedures with SDP and metadata requests Paul: don't expect SRS to send INVITES Charles: if we only use UPDATE, it's simpler Chairs: some clarification is needed, take to list Next Steps, Conference Recording - Paul Kyzviat Proposed to include document sharing Brian: Whe you say doc share, we have no standards Mary: yeah, that's a problem take it out of the=20 Jonathan: it's video, marked as doc share Dan: this shouldn't be the only way to record multimedia Chairs: Suggest charter language Mary: Too broad , MSRP may be too much Brian: NENA needs MSRP Keith: tell me exactly media you want to add in the charter Jonathan: is BFCP in? Paul: it's hard Dan: doesn't say SIP or SIP based Simon: agree with Dan Hadrie: don't need this (media) sentence in the charter Chairs: do we have consensus on getting rid of the list and add sip? Mary: like the list, example, is BFCP in or out? Audio, video and MSRP is enough Paul: really, this is just a metadata discussion Keith: need the list to know when you are done If you don't say, then work isn't done until BFCP is done Hadriel: what is needed, for example for MSRP? Brian: metadata and how to record non RTP media Paul: explicitly dnot want to include clue now Mary: look at use cases first, then look at charter Dan: yes Keith: still need to know when we are done Need to add sip, define conferencing Use Cases Brian: need a way to record any new RTP media without a new version of meta= data. ??? Lots of use cases with mixed sessions which we need to record Brian: if they are separate apps, can't correlate them in one session Hadriel: yeah, lots of different apps used here. Yeah need a generic way t= o record new media. Maybe even generic TCP recording for MSRP Mary: yeah or some proprietary stream, something generic is needed Hadriel: if we limit to SIP based stuff! it's easier Paul: as long as the SRC can reformat to something the SRS can handle, we c= an record it Brian: if we had a generic RTP extension mechanism and a generic container = mechanism for non RTP streams, with ways of marking in metadata, that might work Mary: are ADs aware? Chairs: yes Keith: and perhaps Dispatch chairs. And don't forget file transfer is some= times file transfer and sometimes a URI that leads to the file Mary: need use cases. =20 Mary: re deliverables, are these new docs or bis docs? Need to be very cle= ar. Chairs: this to conclude in the next few weeks. =20 Keith: need to decide if you are going specific or generic and reflect in t= he charter 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 contribut= ed, it will not be considered in the milestones.= From pkyzivat@alum.mit.edu Fri Nov 15 09:31:28 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 122E521F9D7D for ; Fri, 15 Nov 2013 09:31:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.137 X-Spam-Level: X-Spam-Status: No, score=-0.137 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QlD7D6ydeWlm for ; Fri, 15 Nov 2013 09:31:22 -0800 (PST) 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 E4E6411E812D for ; Fri, 15 Nov 2013 09:31:21 -0800 (PST) Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta02.westchester.pa.mail.comcast.net with comcast id poe91m0071HzFnQ51tXLr4; Fri, 15 Nov 2013 17:31:20 +0000 Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta14.westchester.pa.mail.comcast.net with comcast id ptXL1m00A3ZTu2S3atXL03; Fri, 15 Nov 2013 17:31:20 +0000 Message-ID: <52865A68.4070000@alum.mit.edu> Date: Fri, 15 Nov 2013 09:31:20 -0800 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "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=q20121106; t=1384536680; bh=mFwlIcRqbnxTR6sf4ezJ/Js9K5g8kP0RcuozT1Q4pxY=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=PAvhVd59LttyVveGWUD8jjWtopFj3UWUzP50jwPopj4RnyodTpEOHHriIOWFStp+N Bf07FQTQXjhhdsBhoLBmTLAE2TdH9WcMMppFJ/wdknKZ73SiD6X0PnzMZRCwmjOFjs JUlzicL7O5Y9D8ILK2c4X0Ey0T9RLA7soO825x5qJrghe++Jc1sYPLh+DbiBMFB1X2 nHIJitS9XMfuCupC49s0NJnpmCaoGCGQ9tndJO30qDHD4JftBaROo1ne6Xh18Ey4NA spUks7qs44oE7zz6f92Emns0csRGxZf4U4wtZgsrB+y71WO812jRo/DdSWI/iRs+wP YnW4Hsh1FXhiw== Subject: [siprec] Reminder: Additional use cases for draft-kyzivat-siprec-conference-use-cases-00 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 17:31:28 -0000 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 From eckelcu@cisco.com Sat Nov 16 19:07:05 2013 Return-Path: X-Original-To: siprec@ietfa.amsl.com Delivered-To: siprec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0183911E8125 for ; Sat, 16 Nov 2013 19:07:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.999 X-Spam-Level: X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGvQZoHO5cLJ for ; Sat, 16 Nov 2013 19:06:52 -0800 (PST) Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id BA75911E80E9 for ; Sat, 16 Nov 2013 19:06:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2744; q=dns/txt; s=iport; t=1384657600; x=1385867200; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=JRDpxr/yoXJhg4NSWPUK4EKRMWopJB8iWnNudUU+eMo=; b=ZH7GKL9JwatT7thVxEpKF117x1LFOugkj90xzTIbfRTQ8hmznBPgN4bn Nf+4WuPVnf4eLMzr8OTRU6+Bemt9V6fFQ6Q7IQ7z+rbIwKPy0FDrljmC4 jUrjaDG4tfDmUSxnQDibpRkcXNZAzPelNYS2ciNpR2LPs0CS7+XOn8YVe w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ak4FALkxiFKtJV2Z/2dsb2JhbABZgweBC8BFFm0Hgiw6UQE+QicEiBSgLKB4lCEDmBCSDYMogio X-IronPort-AV: E=Sophos;i="4.93,715,1378857600"; d="scan'208";a="285629028" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP; 17 Nov 2013 03:06:30 +0000 Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rAH36TGE003340 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Sun, 17 Nov 2013 03:06:29 GMT Received: from xmb-aln-x08.cisco.com ([169.254.3.191]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0123.003; Sat, 16 Nov 2013 21:06:29 -0600 From: "Charles Eckel (eckelcu)" To: "siprec@ietf.org" Thread-Topic: proposed changes to draft-ietf-siprec-protocol-11 Thread-Index: AQHO40ICY6xsT2zuzkmv998Y7mobng== Date: Sun, 17 Nov 2013 03:06:28 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.3.120616 x-originating-ip: [10.21.150.35] Content-Type: text/plain; charset="us-ascii" Content-ID: <70ADCF19100FE44CBBF6E1FE7F168A56@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [siprec] proposed changes to draft-ietf-siprec-protocol-11 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Nov 2013 03:07:05 -0000 While presenting the changes from draft-ietf-siprec-protocol-10 to draft-ietf-siprec-protocol-11 at IETF 88, we discussed a small set of additional changes. I promised to summarize and provide suggested text. Here it is. Section 7.1.3. Recording Preference In CS The MUST was dropped in the previous change. The proposal is to add it back and edit slightly. OLD (version 10) Whether or not the SRC honors the recording preference, the SRC MUST update the a=3Drecord attribute to indicate the current state of the recording (on/off/paused). CURRENT (version 11) If the SRC makes a change in recording state, then the SRC reports the recording state in the a=3Drecord attribute in the SDP answer or in a subsequent SDP offer/answer. PROPOSED (for version 12) If the SRC makes a change in recording state, the SRC MUST report the new recording state in the a=3Drecord attribute in the SDP answer or in a subsequent SDP offer. 7.3.1. Recording indication CURRENT (version 11) It is possible that more than one SRC can be in the call path recording the same CS, but the recording indication attribute does not provide any hint as to which SRC is actually performing the recording. This means that an endpoint only knows that the call is being recorded through the recording indicator. This attribute is also not used as an indication to negotiate which SRC in the call path will perform recording and is not used as a request to start/ stop recording if there are multiple SRCs in the call path. PROPOSED (for version 12) It is possible that more than one SRC is in the call path of the same CS, but the recording indication attribute does not provide any hint as to which SRC or how many SRCs are recording. An endpoint only knows that the call is being recorded. Furthermore, this attribute is not used as a request for a specific SRC to start/ stop recording. 9.2. Procedures at the SRS CURRENT (version 11) The SRS MAY explicitly request a full metadata snapshot by sending an UPDATE request. This request MUST contain a body with a content disposition type "recording-session", and MUST NOT contain an SDP body part. Note that the SRS MAY generate an INVITE request without an SDP offer but this MUST NOT include a metadata snapshot request. PROPOSED (for version 12) The SRS MAY explicitly request a full metadata snapshot by sending an UPDATE request. This request MUST contain a body with a content disposition type "recording-session", and MUST NOT contain an SDP body part. The SRS MUST NOT request a full metadata snapshot in an UPDATE response or in any other SIP transaction. Comments are welcome. Silence is not :) Cheers, Charles From pkyzivat@alum.mit.edu Thu Nov 21 10:43:48 2013 Return-Path: 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 DF6E71AE1B9 for ; Thu, 21 Nov 2013 10:43:48 -0800 (PST) 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 85W8KSmnyIWC for ; Thu, 21 Nov 2013 10:43:47 -0800 (PST) Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id 745B51AE088 for ; Thu, 21 Nov 2013 10:43:47 -0800 (PST) Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta01.westchester.pa.mail.comcast.net with comcast id sCZP1m0041ap0As51Jjgwl; Thu, 21 Nov 2013 18:43:40 +0000 Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta22.westchester.pa.mail.comcast.net with comcast id sJjg1m00S3ZTu2S3iJjgYt; Thu, 21 Nov 2013 18:43:40 +0000 Message-ID: <528E545C.2090804@alum.mit.edu> Date: Thu, 21 Nov 2013 10:43:40 -0800 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: "siprec@ietf.org" References: <52865A68.4070000@alum.mit.edu> In-Reply-To: <52865A68.4070000@alum.mit.edu> 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=1385059420; bh=ENE8/T9tdlkmKvfq3xbiazJalxqpoih9N8pnvZ7spGU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=KLFW1QfN2NxVOOM0OPtGD/+XHjzdxNYUr164lcmWKHq/JMFaS0v7Ruwxd4mrSssr7 BNu+Czwlg3oMeiZdrQ3OAepdsEUkh+jLGo3v3Nk389ku0hMnikRk9odzT2pCVts2YM LKSM64F0MdOcbHrBWwUH4MVmwZvC0ILFM00VsHC4/dcW+TbRKyI4RByLKgwIYB85A9 c49xw+2JPz/EJOjbfN9JzrdMqpaohm9Sg2Cc2rxxZU2REq3WZXqYTdLzY6d7fyX1Tm QZ7oZ5rcGi9A3kNe4WW9a13cKOE144xwHJ3zlj0lsJalktzz5gH2g8or9+Mjm2JHaR B/8oC97XoqY1A== Subject: Re: [siprec] Reminder: Additional use cases for draft-kyzivat-siprec-conference-use-cases-00 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Nov 2013 18:43:49 -0000 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 > From internet-drafts@ietf.org Sun Nov 24 07:58:10 2013 Return-Path: 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 15BC51AE304; Sun, 24 Nov 2013 07:58:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 ySPftu99_EVq; Sun, 24 Nov 2013 07:58:08 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 67F781AE282; Sun, 24 Nov 2013 07:58:08 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131124155808.16880.35977.idtracker@ietfa.amsl.com> Date: Sun, 24 Nov 2013 07:58:08 -0800 Cc: siprec@ietf.org Subject: [siprec] I-D Action: draft-ietf-siprec-metadata-13.txt X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.15 List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2013 15:58:10 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the SIP Recording Working Group of the IETF. Title : Session Initiation Protocol (SIP) Recording Metadata Author(s) : Ram Mohan Ravindranath Parthasarathi Ravindran Paul Kyzivat Filename : draft-ietf-siprec-metadata-13.txt Pages : 29 Date : 2013-11-24 Abstract: Session recording is a critical requirement in many communications environments such as call centers and financial trading. In some of these environments, all calls must be recorded for regulatory, compliance, and consumer protection reasons. Recording of a session is typically performed by sending a copy of a media stream to a recording device. This document describes the metadata model as viewed by Session Recording Server(SRS) and the Recording metadata format. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-siprec-metadata There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-siprec-metadata-13 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-siprec-metadata-13 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/ From henry.lum@genesyslab.com Mon Nov 25 06:30:54 2013 Return-Path: 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 CDE581ADDD1 for ; Mon, 25 Nov 2013 06:30:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 qzrFzh2hVfBQ for ; Mon, 25 Nov 2013 06:30:52 -0800 (PST) Received: from service107-us.mimecast.com (service107-us.mimecast.com [207.211.31.84]) by ietfa.amsl.com (Postfix) with ESMTP id A2BC41ADDBF for ; Mon, 25 Nov 2013 06:30:52 -0800 (PST) Received: from webmail-us.genesyslab.com (168.75.250.4 [168.75.250.4]) (Using TLS) by service107-us.mimecast.com; Mon, 25 Nov 2013 09:30:51 -0500 Received: from GENSJZMBX02.msg.int.genesyslab.com ([fe80::64cd:bb44:81d2:5bca]) by GENSJZFE02.msg.int.genesyslab.com ([::1]) with mapi id 14.02.0318.004; Mon, 25 Nov 2013 06:30:50 -0800 From: Henry Lum To: "Charles Eckel (eckelcu)" , "siprec@ietf.org" Thread-Topic: proposed changes to draft-ietf-siprec-protocol-11 Thread-Index: AQHO40ICY6xsT2zuzkmv998Y7mobnpo2DzxA Date: Mon, 25 Nov 2013 14:30:49 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.17.178.19] MIME-Version: 1.0 X-MC-Unique: 113112509305200301 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [siprec] proposed changes to draft-ietf-siprec-protocol-11 X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 14:30:55 -0000 The updated revisions look good to me. Thanks Henry -----Original Message----- From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of= Charles Eckel (eckelcu) Sent: November-16-13 10:06 PM To: siprec@ietf.org Subject: [siprec] proposed changes to draft-ietf-siprec-protocol-11 While presenting the changes from draft-ietf-siprec-protocol-10 to draft-ietf-siprec-protocol-11 at IETF 88, we discussed a small set of additional changes. I promised to summarize and provide suggested text. Here it is. Section 7.1.3. Recording Preference In CS The MUST was dropped in the previous change. The proposal is to add it back and edit slightly. OLD (version 10) Whether or not the SRC honors the recording preference, the SRC MUST update the a=3Drecord attribute to indicate the current state of the recording (on/off/paused). CURRENT (version 11) If the SRC makes a change in recording state, then the SRC reports the recording state in the a=3Drecord attribute in the SDP answer or in a subsequent SDP offer/answer. PROPOSED (for version 12) If the SRC makes a change in recording state, the SRC MUST report the new recording state in the a=3Drecord attribute in the SDP answer or in a subsequent SDP offer. 7.3.1. Recording indication CURRENT (version 11) It is possible that more than one SRC can be in the call path recording the same CS, but the recording indication attribute does not provide any hint as to which SRC is actually performing the recording. This means that an endpoint only knows that the call is being recorded through the recording indicator. This attribute is also not used as an indication to negotiate which SRC in the call path will perform recording and is not used as a request to start/ stop recording if there are multiple SRCs in the call path. PROPOSED (for version 12) It is possible that more than one SRC is in the call path of the same CS, but the recording indication attribute does not provide any hint as to which SRC or how many SRCs are recording. An endpoint only knows that the call is being recorded. Furthermore, this attribute is not used as a request for a specific SRC to start/ stop recording. 9.2. Procedures at the SRS CURRENT (version 11) The SRS MAY explicitly request a full metadata snapshot by sending an UPDATE request. This request MUST contain a body with a content disposition type "recording-session", and MUST NOT contain an SDP body part. Note that the SRS MAY generate an INVITE request without an SDP offer but this MUST NOT include a metadata snapshot request. PROPOSED (for version 12) The SRS MAY explicitly request a full metadata snapshot by sending an UPDATE request. This request MUST contain a body with a content disposition type "recording-session", and MUST NOT contain an SDP body part. The SRS MUST NOT request a full metadata snapshot in an UPDATE response or in any other SIP transaction. Comments are welcome. Silence is not :) Cheers, Charles _______________________________________________ siprec mailing list siprec@ietf.org https://www.ietf.org/mailman/listinfo/siprec From michael.yan@huawei.com Tue Nov 26 23:50:43 2013 Return-Path: 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 267831AE245 for ; Tue, 26 Nov 2013 23:50:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.202 X-Spam-Level: X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 Lt3HR_9T4r8E for ; Tue, 26 Nov 2013 23:50:36 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 73A191AE19B for ; Tue, 26 Nov 2013 23:50:32 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYJ03262; Wed, 27 Nov 2013 07:50:31 +0000 (GMT) Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 27 Nov 2013 07:50:00 +0000 Received: from SZXEMA406-HUB.china.huawei.com (10.82.72.38) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 27 Nov 2013 07:50:30 +0000 Received: from SZXEMA508-MBS.china.huawei.com ([169.254.8.12]) by SZXEMA406-HUB.china.huawei.com ([10.82.72.38]) with mapi id 14.03.0158.001; Wed, 27 Nov 2013 15:50:25 +0800 From: "Yanqiang (Michael)" To: "siprec@ietf.org" Thread-Topic: One question about draft-ietf-siprec-architecture Thread-Index: Ac7rRVPcCgfGMPlDRs+Fpcd8rzxKJw== Date: Wed, 27 Nov 2013 07:50:24 +0000 Message-ID: <21794EB0EE82B0458A524942A141542B31D9C99D@szxema508-mbs.china.huawei.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.166.98.122] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: [siprec] One question about draft-ietf-siprec-architecture X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2013 07:50:44 -0000 SGkgQWxsLA0KDQoJSW4gZHJhZnQtaWV0Zi1zaXByZWMtYXJjaGl0ZWN0dXJlLTA5LCAzLjEuNCBJ bnRlcmFjdGlvbiB3aXRoIE1FRElBQ1RSTCwgdGFsa2luZyBhYm91dCB0aGUgZmlndXJlIDQsIHNo b3VsZCB3ZSB1c2UgdGhlICdzb3VyY2UnIGluc3RlYWQgb2YgJ3NpbmsnIHdoZW4gQVMgcHJvdmlk ZXMgbWV0YWRhdGEgdG8gU1JTPyANCg0KT3JpZ2luYWwgdGV4dDoNCglBcyBzaG93biBpbiBmaWd1 cmUgNCwgd2hlbiB0aGUgU1JDIGlzIGFyY2hpdGVjdGVkIGFjY29yZGluZyB0byBbUkZDNTU2N10g dGhlIE1TIGFjdHMgYXMgYSBzb3VyY2Ugb2YgcmVjb3JkaW5nIG1lZGlhIGFuZCB0aGUgQVMgYWN0 cyBhcyBhIHNpbmsgb2YgdGhlIG1ldGFkYXRhIGFuZCB0aGUgdGVybWluYXRpb24gcG9pbnQgZm9y IFJTIFNJUCBzaWduYWxpbmcuDQoNClByb3Bvc2UgdG8gY2hhbmdlIGFzOg0KCUFzIHNob3duIGlu IGZpZ3VyZSA0LCB3aGVuIHRoZSBTUkMgaXMgYXJjaGl0ZWN0ZWQgYWNjb3JkaW5nIHRvIFtSRkM1 NTY3XSB0aGUgTVMgYWN0cyBhcyBhIHNvdXJjZSBvZiByZWNvcmRpbmcgbWVkaWEgYW5kIHRoZSBB UyBhY3RzIGFzIGEgc291cmNlIG9mIHRoZSBtZXRhZGF0YSBhbmQgdGhlIHRlcm1pbmF0aW9uIHBv aW50IGZvciBSUyBTSVAgc2lnbmFsaW5nLg0KDQpUaGFua3MsDQpNaWNoYWVsDQo= From andrew.hutton@unify.com Wed Nov 27 09:57:21 2013 Return-Path: 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 A10A11AD6D2 for ; Wed, 27 Nov 2013 09:57:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 6jLEB2Jq2xxv for ; Wed, 27 Nov 2013 09:57:19 -0800 (PST) Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id D338F1ACCDE for ; Wed, 27 Nov 2013 09:57:13 -0800 (PST) Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id B90531EB8616; Wed, 27 Nov 2013 18:57:10 +0100 (CET) Received: from MCHP04MSX.global-ad.net ([169.254.1.69]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Wed, 27 Nov 2013 18:57:10 +0100 From: "Hutton, Andrew" To: Michael Smith Thread-Topic: [siprec] IETF 88 - SIPREC Draft Agenda Thread-Index: Ac7QBfK35f3xBYKDRfqfYdPjGeXjUpoKSq3AmgJSZJC0BKG+kOfaFsqg Date: Wed, 27 Nov 2013 17:57:09 +0000 Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17C588FB@MCHP04MSX.global-ad.net> References: <9F33F40F6F2CD847824537F3C4E37DDF17C05C82@MCHP04MSX.global-ad.net> <001501ced3f9$2cec6390$86c52ab0$@co.in> <9F33F40F6F2CD847824537F3C4E37DDF17C20C0F@MCHP04MSX.global-ad.net> <006401ced404$e7695240$b63bf6c0$@com> In-Reply-To: <006401ced404$e7695240$b63bf6c0$@com> 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 Cc: "siprec@ietf.org" Subject: Re: [siprec] IETF 88 - SIPREC Draft Agenda X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2013 17:57:21 -0000 Hi Michael, Do you have any information on the ICE 8 event relevant to SIPREC that you = could provide us? Regards Andy > -----Original Message----- > From: Michael Smith [mailto:msmith@dss-corp.com] > Sent: 28 October 2013 17:41 > To: Hutton, Andrew; 'Parthasarathi R'; 'Brian Rosen' > Cc: siprec@ietf.org > Subject: RE: [siprec] IETF 88 - SIPREC Draft Agenda >=20 > About the NENA interop event (ICE 8) - it is indeed next week. We have > about > 17 companies that have implemented siprec (either SRC or SRS > functionality). > We are testing metadata too. I think that those of us who are also on > this > list will be more than happy to provide feedback based on our own > experiences with the drafts. >=20 > I think we're all swamped right now getting ready for the event, so > bear > with us, and I'm sure we'll have some comments once the smoke has > cleared. >=20 > - Michael Smith, ICE 8 Planning Committee chair >=20 > Michael Smith > Chief Technologist, DSS Corp. > Ph: 606.877.2788 | Mobile: 606.231.0243 >=20 > -----Original Message----- > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On > Behalf Of > Hutton, Andrew > Sent: Monday, October 28, 2013 1:28 PM > To: Parthasarathi R; 'Brian Rosen' > Cc: siprec@ietf.org > Subject: Re: [siprec] IETF 88 - SIPREC Draft Agenda >=20 > Hi Partha, >=20 > I understand and share your concern on the lack of progress regarding > the > metadata draft. >=20 > However the following is taken from the minutes of the last IETF > meeting in > Berlin. >=20 > >Metadata draft needs more review there is no presentation during this > meeting on metadata. > >Companies implementing SIPREC for NENA are expected to be at an > interop > event for NG911 implementations scheduled for fall (Nov.?>). 3-4 > Implementations expected to be there. Brian will ask the implementers > for a > review. An experienced IETF reviewer is also >needed. Biggest concern > is if > all necessary semantic are defined. > >Targeting interop events to look for reviewers. > >- Brian Rosen: NENA (Next Generation 911) > >- Charles Eckel: IMTC SIP Parity groups > >ACTION: Need to find reviewers for metadata draft. >=20 > The NENA interop event appears to be planned for next week (Same week > as > IETF88) maybe Brian can update us this. >=20 > The IMTC event will not take place until next May and might not test > SIPREC > stuff so probably we should not wait for that. >=20 > I would really like to encourage those that have implemented the > metadata > draft to provide feedback on the SIPREC mailing list. >=20 > Regards > Andy (SIPREC Co-Chair). >=20 >=20 >=20 > > -----Original Message----- > > From: Parthasarathi R [mailto:partha@parthasarathi.co.in] > > Sent: 28 October 2013 16:17 > > To: Hutton, Andrew; 'Brian Rosen' > > Cc: 'Ram Mohan R (rmohanr)'; siprec@ietf.org > > Subject: RE: [siprec] IETF 88 - SIPREC Draft Agenda > > > > Hi Andy/Brian, > > > > I had raised my concern regarding Metadata draft status > > (http://www.ietf.org/mail-archive/web/siprec/current/msg03771.html) > > as there is no much progress for 1 years 3 months (from last > Vancouver > > meeting) > > without any changes. The multiple SIPREC implementation exists from > > different vendors namely ACME, NICE, AudioCodec, ORCx, HP, Broadsoft > > (http://www.linkedin.com/groups/Who-is-using-SIPREC- > > 4263898.S.176535181) > > already. The comments from ACME & NICE are already incorporated in > the > > latest draft. This clearly indicates that the metadata draft is > > matured enough to implement. AFAIK, each implementation would have > > gone through the draft carefully before implementing and it shall be > > considered as the review. Could you please let us know when is the > > plan to start WGLC for the metadata drafts or any other blocking > draft > > for this draft. > > > > I'm also interested in knowing whether the new charter will have the > > impact in metadata draft. IMO, the new use case has to be considered > > as an extension to the metadata drafts. > > > > Thanks > > Partha > > > > > -----Original Message----- > > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On > > > Behalf Of Ram Mohan R (rmohanr) > > > Sent: Wednesday, October 23, 2013 9:26 PM > > > To: Hutton, Andrew; siprec@ietf.org > > > Subject: Re: [siprec] IETF 88 - SIPREC Draft Agenda > > > > > > The agenda looks great. One thing I would like to hear is - > > > > > > Discuss on how to progress these two WG drafts: > > > http://tools.ietf.org/wg/siprec/draft-ietf-siprec-metadata/ > > > http://tools.ietf.org/wg/siprec/draft-ietf-siprec-callflows/ > > > > > > We have not had much progress on either of these drafts for quite > > some > > > time now due to lack of reviews. Can we get some help here ? > > > > > > Regards, > > > Ram > > > > > > -----Original Message----- > > > From: , Andrew > > > Date: Wednesday, 23 October 2013 9:08 PM > > > To: "siprec@ietf.org" > > > Subject: [siprec] IETF 88 - SIPREC Draft Agenda > > > > > > >Hi All, > > > > > > > >I posted a draft agenda which can be found at: > > > >https://datatracker.ietf.org/meeting/88/agenda/siprec/. > > > > > > > >Please let me have any requests for changes/additions by Sunday > > > >27th > > > of > > > >October. > > > > > > > >Regards > > > >Andy > > > >_______________________________________________ > > > >siprec mailing list > > > >siprec@ietf.org > > > >https://www.ietf.org/mailman/listinfo/siprec > > > > > > _______________________________________________ > > > siprec mailing list > > > siprec@ietf.org > > > https://www.ietf.org/mailman/listinfo/siprec >=20 > _______________________________________________ > siprec mailing list > siprec@ietf.org > https://www.ietf.org/mailman/listinfo/siprec From andrew.hutton@unify.com Wed Nov 27 10:02:00 2013 Return-Path: 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 750751ADF59 for ; Wed, 27 Nov 2013 10:02:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 X3Jhcz6hkjDW for ; Wed, 27 Nov 2013 10:01:59 -0800 (PST) Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 0E1211ADF0E for ; Wed, 27 Nov 2013 10:01:59 -0800 (PST) Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id 9CCA523F062B; Wed, 27 Nov 2013 19:01:57 +0100 (CET) Received: from MCHP04MSX.global-ad.net ([169.254.1.69]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0123.003; Wed, 27 Nov 2013 19:01:57 +0100 From: "Hutton, Andrew" To: "Yanqiang (Michael)" , "siprec@ietf.org" Thread-Topic: One question about draft-ietf-siprec-architecture Thread-Index: Ac7rRVPcCgfGMPlDRs+Fpcd8rzxKJwAVT1ZA Date: Wed, 27 Nov 2013 18:01:56 +0000 Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17C5893D@MCHP04MSX.global-ad.net> References: <21794EB0EE82B0458A524942A141542B31D9C99D@szxema508-mbs.china.huawei.com> In-Reply-To: <21794EB0EE82B0458A524942A141542B31D9C99D@szxema508-mbs.china.huawei.com> 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 Subject: Re: [siprec] One question about draft-ietf-siprec-architecture X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2013 18:02:00 -0000 Hi Michael, I believe you are correct and as I am about to submit a version 10 I will m= ake the change. Thanks for reporting this. Regards Andy > -----Original Message----- > From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Yanqiang > (Michael) > Sent: 27 November 2013 07:50 > To: siprec@ietf.org > Subject: [siprec] One question about draft-ietf-siprec-architecture >=20 > Hi All, >=20 > In draft-ietf-siprec-architecture-09, 3.1.4 Interaction with > MEDIACTRL, talking about the figure 4, should we use the 'source' > instead of 'sink' when AS provides metadata to SRS? >=20 > Original text: > As shown in figure 4, when the SRC is architected according to > [RFC5567] the MS acts as a source of recording media and the AS acts as > a sink of the metadata and the termination point for RS SIP signaling. >=20 > Propose to change as: > As shown in figure 4, when the SRC is architected according to > [RFC5567] the MS acts as a source of recording media and the AS acts as > a source of the metadata and the termination point for RS SIP > signaling. >=20 > Thanks, > Michael > _______________________________________________ > siprec mailing list > siprec@ietf.org > https://www.ietf.org/mailman/listinfo/siprec From msmith@dss-corp.com Wed Nov 27 14:14:13 2013 Return-Path: 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 5B29B1AE16B for ; Wed, 27 Nov 2013 14:14:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 2EqagJ90PK1k for ; Wed, 27 Nov 2013 14:14:10 -0800 (PST) Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7ED1ADF7A for ; Wed, 27 Nov 2013 14:14:10 -0800 (PST) Received: by mail-ie0-f170.google.com with SMTP id qd12so13143583ieb.1 for ; Wed, 27 Nov 2013 14:14:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:thread-index:content-language; bh=CztNrQGDUGnTZurLLhmP0hcuJ9QHxg+MV5Q/OsY1eEg=; b=ZkVMtepxCzTpg25ju5OJnqdzdMuv1GSGFlhmxSRXOUve1kWEjGM9cC80CnMxUFpRxb TwUUH1wI1PqSvLFrvm290/OXh2c9y6h9wZaymG55zhnmqHoQgiSQjDLWwryILptoRgh1 aiOAfpYt0oi4Fh/qMomg6OWSlDxAJ73ewGrkJ4S+LgnpKb1lo5/FDGh9GhAVeamKkNlO Vlph5TUx9NmZ9VJLVKDvspwZjqXiPs+5nyN/54VKbQjHP1Jzt1zJ6GWxaicZZ66ghxSB VYKCH/6WoUGvvayg0ME449yZdYQz7G9Mp/S2Wc0c3pXldFxPzEYHbu+RXo5U+9vX8ZDH 00OQ== X-Gm-Message-State: ALoCoQn1pKx7rkIB5tO/ihs4FqZlmYTzGynmFl1plF8Bj3CjlUu68JuOWZrB3MHPg5VqpOjXb1QH X-Received: by 10.50.73.74 with SMTP id j10mr104038igv.50.1385590449444; Wed, 27 Nov 2013 14:14:09 -0800 (PST) Received: from mlsAW ([65.24.145.64]) by mx.google.com with ESMTPSA id da14sm1142347igc.1.2013.11.27.14.14.07 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 27 Nov 2013 14:14:08 -0800 (PST) From: "Michael Smith" To: "'Hutton, Andrew'" References: <9F33F40F6F2CD847824537F3C4E37DDF17C05C82@MCHP04MSX.global-ad.net> <001501ced3f9$2cec6390$86c52ab0$@co.in> <9F33F40F6F2CD847824537F3C4E37DDF17C20C0F@MCHP04MSX.global-ad.net> <006401ced404$e7695240$b63bf6c0$@com> <9F33F40F6F2CD847824537F3C4E37DDF17C588FB@MCHP04MSX.global-ad.net> In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17C588FB@MCHP04MSX.global-ad.net> Date: Wed, 27 Nov 2013 17:13:55 -0500 Message-ID: <003301ceebbd$f79ed150$e6dc73f0$@com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0034_01CEEB94.0EC8C950" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac7QBfK35f3xBYKDRfqfYdPjGeXjUpoKSq3AmgJSZJC0BKG+kOfaFsqgz7PprzA= Content-Language: en-us Cc: siprec@ietf.org Subject: Re: [siprec] IETF 88 - SIPREC Draft Agenda X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2013 22:14:13 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0034_01CEEB94.0EC8C950 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I've only gotten one written comment (attached, from Matt Daughtrey of Eventide). This may be because of the Thanksgiving holiday - others made verbal comments, and I'll keep prodding them. Matt's comments reference metadata-13. Perhaps that's a typo - we tested against metadata-12. His point is about whether the drafts are clear on whether multiple CS could be recorded in one RS. The Call and Incident IDs he talks about are NENA specific, and carried in call-info headers, in case you wonder about that. One other comment I heard from many was that the language of the metadata drafts was hard to follow, due to usage and grammar issues - but that generally you could understand the intent. Cleaning up the language without changing the intent is doable, and would help. I don't recall anyone saying they had issues with the protocol draft. I'll ping the ICE 8 group again next week to provide written feedback ASAP. Michael Smith Chief Technologist, DSS Corp. Ph: 606.877.2788 | Mobile: 606.231.0243 -----Original Message----- From: Hutton, Andrew [mailto:andrew.hutton@unify.com] Sent: Wednesday, November 27, 2013 12:57 PM To: Michael Smith Cc: siprec@ietf.org; 'Parthasarathi R'; 'Brian Rosen' Subject: RE: [siprec] IETF 88 - SIPREC Draft Agenda Hi Michael, Do you have any information on the ICE 8 event relevant to SIPREC that you could provide us? Regards Andy > -----Original Message----- > From: Michael Smith [mailto:msmith@dss-corp.com] > Sent: 28 October 2013 17:41 > To: Hutton, Andrew; 'Parthasarathi R'; 'Brian Rosen' > Cc: siprec@ietf.org > Subject: RE: [siprec] IETF 88 - SIPREC Draft Agenda > > About the NENA interop event (ICE 8) - it is indeed next week. We have > about > 17 companies that have implemented siprec (either SRC or SRS > functionality). > We are testing metadata too. I think that those of us who are also on > this list will be more than happy to provide feedback based on our own > experiences with the drafts. > > I think we're all swamped right now getting ready for the event, so > bear with us, and I'm sure we'll have some comments once the smoke has > cleared. > > - Michael Smith, ICE 8 Planning Committee chair > > Michael Smith > Chief Technologist, DSS Corp. > Ph: 606.877.2788 | Mobile: 606.231.0243 > > -----Original Message----- > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On > Behalf Of Hutton, Andrew > Sent: Monday, October 28, 2013 1:28 PM > To: Parthasarathi R; 'Brian Rosen' > Cc: siprec@ietf.org > Subject: Re: [siprec] IETF 88 - SIPREC Draft Agenda > > Hi Partha, > > I understand and share your concern on the lack of progress regarding > the metadata draft. > > However the following is taken from the minutes of the last IETF > meeting in Berlin. > > >Metadata draft needs more review there is no presentation during this > meeting on metadata. > >Companies implementing SIPREC for NENA are expected to be at an > interop > event for NG911 implementations scheduled for fall (Nov.?>). 3-4 > Implementations expected to be there. Brian will ask the implementers > for a review. An experienced IETF reviewer is also >needed. Biggest > concern is if all necessary semantic are defined. > >Targeting interop events to look for reviewers. > >- Brian Rosen: NENA (Next Generation 911) > >- Charles Eckel: IMTC SIP Parity groups > >ACTION: Need to find reviewers for metadata draft. > > The NENA interop event appears to be planned for next week (Same week > as > IETF88) maybe Brian can update us this. > > The IMTC event will not take place until next May and might not test > SIPREC stuff so probably we should not wait for that. > > I would really like to encourage those that have implemented the > metadata draft to provide feedback on the SIPREC mailing list. > > Regards > Andy (SIPREC Co-Chair). > > > > > -----Original Message----- > > From: Parthasarathi R [mailto:partha@parthasarathi.co.in] > > Sent: 28 October 2013 16:17 > > To: Hutton, Andrew; 'Brian Rosen' > > Cc: 'Ram Mohan R (rmohanr)'; siprec@ietf.org > > Subject: RE: [siprec] IETF 88 - SIPREC Draft Agenda > > > > Hi Andy/Brian, > > > > I had raised my concern regarding Metadata draft status > > (http://www.ietf.org/mail-archive/web/siprec/current/msg03771.html) > > as there is no much progress for 1 years 3 months (from last > Vancouver > > meeting) > > without any changes. The multiple SIPREC implementation exists from > > different vendors namely ACME, NICE, AudioCodec, ORCx, HP, Broadsoft > > (http://www.linkedin.com/groups/Who-is-using-SIPREC- > > 4263898.S.176535181) > > already. The comments from ACME & NICE are already incorporated in > the > > latest draft. This clearly indicates that the metadata draft is > > matured enough to implement. AFAIK, each implementation would have > > gone through the draft carefully before implementing and it shall be > > considered as the review. Could you please let us know when is the > > plan to start WGLC for the metadata drafts or any other blocking > draft > > for this draft. > > > > I'm also interested in knowing whether the new charter will have the > > impact in metadata draft. IMO, the new use case has to be considered > > as an extension to the metadata drafts. > > > > Thanks > > Partha > > > > > -----Original Message----- > > > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On > > > Behalf Of Ram Mohan R (rmohanr) > > > Sent: Wednesday, October 23, 2013 9:26 PM > > > To: Hutton, Andrew; siprec@ietf.org > > > Subject: Re: [siprec] IETF 88 - SIPREC Draft Agenda > > > > > > The agenda looks great. One thing I would like to hear is - > > > > > > Discuss on how to progress these two WG drafts: > > > http://tools.ietf.org/wg/siprec/draft-ietf-siprec-metadata/ > > > http://tools.ietf.org/wg/siprec/draft-ietf-siprec-callflows/ > > > > > > We have not had much progress on either of these drafts for quite > > some > > > time now due to lack of reviews. Can we get some help here ? > > > > > > Regards, > > > Ram > > > > > > -----Original Message----- > > > From: , Andrew > > > Date: Wednesday, 23 October 2013 9:08 PM > > > To: "siprec@ietf.org" > > > Subject: [siprec] IETF 88 - SIPREC Draft Agenda > > > > > > >Hi All, > > > > > > > >I posted a draft agenda which can be found at: > > > >https://datatracker.ietf.org/meeting/88/agenda/siprec/. > > > > > > > >Please let me have any requests for changes/additions by Sunday > > > >27th > > > of > > > >October. > > > > > > > >Regards > > > >Andy > > > >_______________________________________________ > > > >siprec mailing list > > > >siprec@ietf.org > > > >https://www.ietf.org/mailman/listinfo/siprec > > > > > > _______________________________________________ > > > siprec mailing list > > > siprec@ietf.org > > > https://www.ietf.org/mailman/listinfo/siprec > > _______________________________________________ > siprec mailing list > siprec@ietf.org > https://www.ietf.org/mailman/listinfo/siprec ------=_NextPart_000_0034_01CEEB94.0EC8C950 Content-Type: application/msword; name="Comments on SIPREC.rtf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Comments on SIPREC.rtf" {\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset0 = Calibri;}} {\*\generator Msftedit = 5.41.21.2510;}\viewkind4\uc1\pard\sa200\sl276\slmult1\lang9\b\f0\fs22 = Comments on SIPREC\b0\par The draft-ietf-siprec-metadata-13 document (hereafter, the "draft = document") describes the concept of a Recording Session (RS) containing = one or more Communication Sessions (CSs). The idea as described in = sections \b 6.1 Recording Session \b0 is that the RS corresponds to a = SIPREC session between the FE and the SRS and is persistent across = multiple CSs (\b Section 6.1.2. Linkages\b0 ), each of which correspond = to a subscriber call (\b Section 6.3.2. Linkages\b0 ) . Each CS consists = of a call structure which is described in the rs-metadata. \par In practice this seems to describe a situation where a SIPREC session = (ie, RS) is created to the SRS which may be prior to any actual calls, = and within that session multiple subscriber calls are processed. The RS = spans multiple calls and, at least in theory, may never disconnect. \par The facility to uniquely identify a call (analogous to the SIP call ID) = is embodied in the CSs Communication Identifier (\b Section 6.3.1. = Attributes\b0 ).\par In short, the traditional role of the SIP call is now taken on by the CS = under SIPREC, and the SIPREC session (as an RS) becomes a 'container' of = sorts. The relationship between the SIPREC session and the CS is = decoupled.\par \par \b Comments on NG911 Implementation of SIPREC\b0\par We've added two new headers to the SIPREC INVITE message: the NENA Call = ID and the NENA Incident ID. The call ID is unique to each SIPREC = session, and the incident ID may occur across multiple sessions. In = adding these headers we return to the idea of a SIPREC session for each = subscriber call, force a 1-to-1 relationship between an RS and a call, = and a 1-to-1 relationship between the RS and CS. The decoupling between = SIPREC session and CS is undone.\par \b Comments on the Previous Comments\par \b0 Our experience is that every SRC has implemented one SIPREC session = per subscriber call. Each session contains one RS and one CS, with = accompanying metadata. The SIPREC session persists for the duration of = the call and is then terminated. UPDATEs and reINVITEs occur as the call = structure changes and this is reflected in the rs-metadata. We return to = the traditional idea of one SIPREC session corresponding to one call. = One RS contains one CS.\par This, to my mind, is the simplest and most sensible approach. Recorders = are already set up to handle many SIP/SIPREC sessions at once and we've = all written the code to handle loss of a SIP/SIPREc session. Handling = multiple CSs in an RS would require shifting that call handling logic to = the CS level, which is simply unnecessary.\par Our implemention of SIPREC does not violate the draft, since an RS may = have zero or more CSs (\b Section 6.1.2. Linkages\b0 )\par \par \b Draft Document Ambiguity\par \b0 There is an ambiguity in the draft document: Section 6.1 Recording = Session states that \par \i Each instance of a Recording Session class (namely the Recording = Session Object) represents a SIP session created between an SRC and SRS = for the purpose of recording \b a\b0 Communication Session\par \i0 (note the singular CS) but Section 6.1.2. Linkages states that each = instance of a Recording Session has:\line\line\i o Zero or more = instances of Communication Session objects\par \par \i0\par } =00 ------=_NextPart_000_0034_01CEEB94.0EC8C950-- From michael.yan@huawei.com Thu Nov 28 01:04:17 2013 Return-Path: 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 CCAC61AC421 for ; Thu, 28 Nov 2013 01:04:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.202 X-Spam-Level: X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 8ARfwUc5Kh5T for ; Thu, 28 Nov 2013 01:04:15 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 778F41AC7F2 for ; Thu, 28 Nov 2013 01:04:14 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAU37930; Thu, 28 Nov 2013 09:04:12 +0000 (GMT) Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 28 Nov 2013 09:03:38 +0000 Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 28 Nov 2013 09:04:11 +0000 Received: from SZXEMA508-MBS.china.huawei.com ([169.254.8.12]) by SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001; Thu, 28 Nov 2013 17:04:03 +0800 From: "Yanqiang (Michael)" To: "Hutton, Andrew" , "siprec@ietf.org" Thread-Topic: One question about draft-ietf-siprec-architecture Thread-Index: Ac7rRVPcCgfGMPlDRs+Fpcd8rzxKJwAVT1ZAAB9poCA= Date: Thu, 28 Nov 2013 09:04:02 +0000 Message-ID: <21794EB0EE82B0458A524942A141542B31D9CCE6@szxema508-mbs.china.huawei.com> References: <21794EB0EE82B0458A524942A141542B31D9C99D@szxema508-mbs.china.huawei.com> <9F33F40F6F2CD847824537F3C4E37DDF17C5893D@MCHP04MSX.global-ad.net> In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17C5893D@MCHP04MSX.global-ad.net> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.166.98.122] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: Re: [siprec] One question about draft-ietf-siprec-architecture X-BeenThere: siprec@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Recording Working Group Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2013 09:04:18 -0000 SGkgQW5keSwNCg0KSSBnb3QgdGhyZWUgbW9yZSBxdWVzdGlvbnMgYWJvdXQgMDkgdmVyc2lvbi4N Cg0KMS4gV2h5IHJlbW92ZSB0aGUgd29yZCBiZWxvdyAnIFBvc3NpYmxlIG1lY2hhbmlzbXMgZm9y IHRoaXMgaW5jbHVkZSB1c2luZyB0aGUgUmVxdWlyZSBoZWFkZXIgb3IgYSBtZWRpYSBmZWF0dXJl IHRhZyBhcyBkZWZpbmVkIGluIFtSRkMzODQwXScgZm9yIHRoZSAzcmQgYWN0aW9uIGluIDMuMi4x PyBJdCB3YXMgcmVtb3ZlZCBpbiAwOSB2ZXJzaW9uIGFuZCB0aGUgY29tcGFyaXNvbiBmaWxlIG9m IDA4LzA5LCB3aGlsZSBpdCBleGlzdGVkIGluIDA4IHZlcnNpb24gYW5kIHZlcnNpb25zIGJlZm9y ZS4NCg0KMi4gU2hvdWxkIHdlIGNoYW5nZSAnU1JDJyB0byAnU1JTJyBpbiB0aGUgd29yZCBiZWxv dyAnIElmIHRoZSBSZWNvcmRpbmcgU2Vzc2lvbiBpcyB0byBiZSBzdGFydGVkIGltbWVkaWF0ZWx5 IHRoZW4gdGhlIFNSQyB3aWxsIGluY2x1ZGUgYW4gU0RQIGF0dHJpYnV0ZSBvZiAiYT1yZWN2b25s eSIgZm9yIGVhY2ggbWVkaWEgbGluZSBvciAiYT1pbmFjdGl2ZSIgaWYgaXQgaXMgbm90IHJlYWR5 IHRvIHJlY2VpdmUgdGhlIG1lZGlhJyBpbiAzLjIuMiBsYXN0IGFjdGlvbj8NCg0KMy4gSWYgdXNl IFNSUyB0byByZXBsYWNlIGFsbCAnU2Vzc2lvbiBSZWNvcmRpbmcgU2VydmVyJyBpbiAwOSB2ZXJz aW9uLCB3aHkgbm90IGNoYW5nZSBhbGwgJ1Nlc3Npb24gUmVjb3JkaW5nIENsaWVudCcgdG8gU1JD IGFzIHdlbGwuIEFueXdheSwgc2hvdWxkIHByb3RvY29sIGRvY3VtZW50IGFuZCBvdGhlcnMgdXNl IFNSQy9TUlMgaW5zdGVhZCBvZiAnU2Vzc2lvbiBSZWNvcmRpbmcgU2VydmVyJy8nU2Vzc2lvbiBS ZWNvcmRpbmcgQ2xpZW50Jz8NCg0KVGhhbmtzLA0KTWljaGFlbA0KDQo+IC0tLS0tT3JpZ2luYWwg TWVzc2FnZS0tLS0tDQo+IEZyb206IEh1dHRvbiwgQW5kcmV3IFttYWlsdG86YW5kcmV3Lmh1dHRv bkB1bmlmeS5jb21dDQo+IFNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAyOCwgMjAxMyAyOjAyIEFN DQo+IFRvOiBZYW5xaWFuZyAoTWljaGFlbCk7IHNpcHJlY0BpZXRmLm9yZw0KPiBTdWJqZWN0OiBS RTogT25lIHF1ZXN0aW9uIGFib3V0IGRyYWZ0LWlldGYtc2lwcmVjLWFyY2hpdGVjdHVyZQ0KPiAN Cj4gSGkgTWljaGFlbCwNCj4gDQo+IEkgYmVsaWV2ZSB5b3UgYXJlIGNvcnJlY3QgYW5kIGFzIEkg YW0gYWJvdXQgdG8gc3VibWl0IGEgdmVyc2lvbiAxMCBJIHdpbGwgbWFrZSB0aGUNCj4gY2hhbmdl Lg0KPiANCj4gVGhhbmtzIGZvciByZXBvcnRpbmcgdGhpcy4NCj4gDQo+IFJlZ2FyZHMNCj4gQW5k eQ0KPiANCj4gDQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBzaXBy ZWMgW21haWx0bzpzaXByZWMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFlhbnFpYW5n DQo+ID4gKE1pY2hhZWwpDQo+ID4gU2VudDogMjcgTm92ZW1iZXIgMjAxMyAwNzo1MA0KPiA+IFRv OiBzaXByZWNAaWV0Zi5vcmcNCj4gPiBTdWJqZWN0OiBbc2lwcmVjXSBPbmUgcXVlc3Rpb24gYWJv dXQgZHJhZnQtaWV0Zi1zaXByZWMtYXJjaGl0ZWN0dXJlDQo+ID4NCj4gPiBIaSBBbGwsDQo+ID4N Cj4gPiAJSW4gZHJhZnQtaWV0Zi1zaXByZWMtYXJjaGl0ZWN0dXJlLTA5LCAzLjEuNCBJbnRlcmFj dGlvbiB3aXRoDQo+ID4gTUVESUFDVFJMLCB0YWxraW5nIGFib3V0IHRoZSBmaWd1cmUgNCwgc2hv dWxkIHdlIHVzZSB0aGUgJ3NvdXJjZScNCj4gPiBpbnN0ZWFkIG9mICdzaW5rJyB3aGVuIEFTIHBy b3ZpZGVzIG1ldGFkYXRhIHRvIFNSUz8NCj4gPg0KPiA+IE9yaWdpbmFsIHRleHQ6DQo+ID4gCUFz IHNob3duIGluIGZpZ3VyZSA0LCB3aGVuIHRoZSBTUkMgaXMgYXJjaGl0ZWN0ZWQgYWNjb3JkaW5n IHRvDQo+ID4gW1JGQzU1NjddIHRoZSBNUyBhY3RzIGFzIGEgc291cmNlIG9mIHJlY29yZGluZyBt ZWRpYSBhbmQgdGhlIEFTIGFjdHMgYXMNCj4gPiBhIHNpbmsgb2YgdGhlIG1ldGFkYXRhIGFuZCB0 aGUgdGVybWluYXRpb24gcG9pbnQgZm9yIFJTIFNJUCBzaWduYWxpbmcuDQo+ID4NCj4gPiBQcm9w b3NlIHRvIGNoYW5nZSBhczoNCj4gPiAJQXMgc2hvd24gaW4gZmlndXJlIDQsIHdoZW4gdGhlIFNS QyBpcyBhcmNoaXRlY3RlZCBhY2NvcmRpbmcgdG8NCj4gPiBbUkZDNTU2N10gdGhlIE1TIGFjdHMg YXMgYSBzb3VyY2Ugb2YgcmVjb3JkaW5nIG1lZGlhIGFuZCB0aGUgQVMgYWN0cyBhcw0KPiA+IGEg c291cmNlIG9mIHRoZSBtZXRhZGF0YSBhbmQgdGhlIHRlcm1pbmF0aW9uIHBvaW50IGZvciBSUyBT SVANCj4gPiBzaWduYWxpbmcuDQo+ID4NCj4gPiBUaGFua3MsDQo+ID4gTWljaGFlbA0KPiA+IF9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gc2lwcmVj IG1haWxpbmcgbGlzdA0KPiA+IHNpcHJlY0BpZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3LmlldGYu b3JnL21haWxtYW4vbGlzdGluZm8vc2lwcmVjDQo=