Re: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-metadata-20: (with DISCUSS and COMMENT)
Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 21 March 2016 17:04 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 E38FA12D850 for <siprec@ietfa.amsl.com>; Mon, 21 Mar 2016 10:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 mdE50RxCPZxy for <siprec@ietfa.amsl.com>; Mon, 21 Mar 2016 10:04:42 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8FBB12D931 for <siprec@ietf.org>; Mon, 21 Mar 2016 10:04:30 -0700 (PDT)
Received: from resomta-ch2-11v.sys.comcast.net ([69.252.207.107]) by comcast with SMTP id i3E4aC6rxBGW6i3FmaF3qu; Mon, 21 Mar 2016 17:04:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1458579870; bh=m4io0qUDdj6RrfoknepXU1WlxETQBk+JrYLiw6cvWjU=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=nMiCuYdV6PeOBaUePhfWKDaxBax2lMFuFG3kkMCAtztNMzzm0mDyyPtVKDmCta9t8 L0ZtLhsM90e+54yNA9Tmz/gJCS3br49Q8O+hl2F5AUwYEGZDBcubzfYw2U4Okp3BOp e+Wvc6hR8/f4MB6m/1O9r/QQuaZp7oqAY2ZSIzy0nqPXa+NgPfns4AeKjbP6AuBH4w znIU6Rp6K3JhgRar9q80nqJ2XQBInWqsnyPF+j+Dz3Z2amZ8XGIFXm7bz3vISKculx 5Ch0uG8swl4gcOzIog+1/xVmS1o+HD4PoIDVgDK3zvMCZVcHdmNFoVa+/Agw4xMtDm j9V6qFW8TvM0Q==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-11v.sys.comcast.net with comcast id Yh4V1s00D3KdFy101h4VqT; Mon, 21 Mar 2016 17:04:30 +0000
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
References: <20160302110853.23213.23639.idtracker@ietfa.amsl.com> <D2FD2694.5326B%rmohanr@cisco.com> <56D9989F.1010103@cs.tcd.ie> <D303791D.53A11%rmohanr@cisco.com> <D312E982.5567D%rmohanr@cisco.com> <56EEDFF2.4000604@alum.mit.edu> <D3160C24.5591E%rmohanr@cisco.com> <56F01407.5000606@alum.mit.edu> <D3161B0F.55972%rmohanr@cisco.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <56F0299D.9060105@alum.mit.edu>
Date: Mon, 21 Mar 2016 13:04:29 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <D3161B0F.55972%rmohanr@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/Pd6lONko9zxqJkxpM8owONRvghs>
Subject: Re: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-metadata-20: (with DISCUSS and COMMENT)
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/siprec/>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2016 17:04:44 -0000
That is better. Thanks, Paul On 3/21/16 12:10 PM, Ram Mohan R (rmohanr) wrote: > Paul, > > Please see inline > > -----Original Message----- > From: Paul Kyzivat <pkyzivat@alum.mit.edu> > Date: Monday, 21 March 2016 at 9:02 PM > To: Cisco Employee <rmohanr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org> > Subject: Re: [siprec] Stephen Farrell's Discuss on > draft-ietf-siprec-metadata-20: (with DISCUSS and COMMENT) > >> On 3/21/16 10:59 AM, Ram Mohan R (rmohanr) wrote: >>> Paul, >>> >>> One comment please see inline >>> >>> -----Original Message----- >>> From: siprec <siprec-bounces@ietf.org> on behalf of Paul Kyzivat >>> <pkyzivat@alum.mit.edu> >>> Date: Sunday, 20 March 2016 at 11:07 PM >>> To: "siprec@ietf.org" <siprec@ietf.org> >>> Subject: Re: [siprec] Stephen Farrell's Discuss on >>> draft-ietf-siprec-metadata-20: (with DISCUSS and COMMENT) >>> >>>> Hi Ram, >>>> >>>> This looks good. I saw a couple of nits while reviewing the changes: >>>> >>>> * Section 6.1.2: >>>> >>>> CSs and CS-Groups are optional to accommodate persistent recording, >>>> where there may sometimes be none. ... >>>> >>>> That statement is correct WRT CS-Groups, but not CSs. CSs have much >>>> more >>>> relevance, and aren't optional for recording. So I would simply omit >>>> "CSs and " from the above. >>> >>> Above statement is for persistent recording case where the RS may be >>> setup >>> between SRC (say endpoint like voip phone) and SRS even before any CS is >>> setup. >>> Once CS is setup, the persistent RS dialog will be used to record the RS >>> rather than setting up another RS. This statement is to indicate the >>> same. >> >> My point was that CSs are not optional in the same way that CSGs are. >> >> They are optional in the sense that you can send a <recording> element >> that has none > > That¹s correct. I was trying to convey this information through the above > statement. Perhaps it is not clear. > How about re-wording the sentence to some thing like this: > > EXISTING: > CS and CS-Groups are optional to accommodate persistent recording, > Where there may sometimes be none.A persistent RS is a SIP dialog > that is setup between SRC to SRS even before any CS is setupŠ....... > > > NEW: > Zero instances of CS and CS-Group in a recording element is allowed to > accommodate persistent recording scenarios. > A persistent RS is a SIP dialog that is setup between SRC to SRS even > before any CS is setupŠ....... > > > Does this look better ? > > Regards, > Ram > >> . But ultimately it is CSs that are the primary thing being >> recorded. >> And of course communication sessions can exist without recordings. >> >> So maybe this just needs a few more words. >> >> But this isn't a big deal. I won't be bothered if you leave it as-is. >> >> Thanks, >> Paul >> > >
- [siprec] Stephen Farrell's Discuss on draft-ietf-… Stephen Farrell
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Paul Kyzivat
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Paul Kyzivat
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Paul Kyzivat
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Paul Kyzivat
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Paul Kyzivat
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Ram Mohan R (rmohanr)
- Re: [siprec] Stephen Farrell's Discuss on draft-i… Paul Kyzivat