Re: [siprec] I-D Action: draft-ietf-siprec-metadata-21.txt

Alissa Cooper <alissa@cooperw.in> Sat, 19 March 2016 11:50 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 512F412D781 for <siprec@ietfa.amsl.com>; Sat, 19 Mar 2016 04:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=VqSZgSnw; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=cHSl/mJE
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 Ofq59LKN-Qn1 for <siprec@ietfa.amsl.com>; Sat, 19 Mar 2016 04:50:47 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6529612D51C for <siprec@ietf.org>; Sat, 19 Mar 2016 04:50:47 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 91F10202DD for <siprec@ietf.org>; Sat, 19 Mar 2016 07:41:44 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 19 Mar 2016 07:41:44 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=K0nab gqbsZfKobmQFzPXrQnRI+k=; b=VqSZgSnwjtVZOLEdejviP4t/XgTA9yXNOrZPq kwX9BPAru+xdOodpJcAHkMuQQOCnzwxVolOP6vvsC9CYHDuzLEosRZjLKgJuQ/EM GMsIBsW4CHCbF9NC4auBm5s9bzULsdsTzPSKcPJByBV8Yc2wqJUFtR/YuerqdXkn Wur+HA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=K0nabgqbsZfKobmQFzPXrQnRI+k=; b=cHSl/ mJECzai+E+IbpeVA/G8QW48b7a93OZ9e2LRjDjaMlneTLP0hzuZrCFu+54Ppfh9K ILeqd1A3Stt5luKN0yR4Gke19vDhYJ6Sp+VlCBsl5ovzg/yCgSLIdXvCi+s3yhg5 DU+UkuztL0FzeOl/FrKSlsnlVIbM/krgVBxcBk=
X-Sasl-enc: CeI4CSN5SbvM5OyUBSdapg4maTEqylPKCYLwV8PSp87L 1458387704
Received: from sjc-alcoop-8813.cisco.com (unknown [128.107.241.190]) by mail.messagingengine.com (Postfix) with ESMTPA id 2207CC00012 for <siprec@ietf.org>; Sat, 19 Mar 2016 07:41:43 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3181D527-9EE1-40E5-B7AB-56CD94F2CC23"
Message-Id: <A38B158A-969E-46DF-8D4E-B8B549FFDF5D@cooperw.in>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Date: Sat, 19 Mar 2016 04:41:49 -0700
References: <20160319055243.18124.6668.idtracker@ietfa.amsl.com>
To: siprec@ietf.org
In-Reply-To: <20160319055243.18124.6668.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/dyKSOOQvK84xasruAzgIDZiypYw>
Subject: Re: [siprec] I-D Action: draft-ietf-siprec-metadata-21.txt
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: Sat, 19 Mar 2016 11:50:49 -0000

One suggestion, I think there is a word missing here:

OLD
And the policy of the SRS might not
   require all the metadata it receives.

NEW
And the policy of the SRS might not
   require recording all the metadata it receives.

If this is the only remaining change I can put it in an RFC Editor’s note. But I assume you’d like to hear from Ben before I approve this document?

Thanks,
Alissa


> On Mar 18, 2016, at 10:52 PM, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the SIP Recording of the IETF.
> 
>        Title           : Session Initiation Protocol (SIP) Recording Metadata
>        Authors         : Ram Mohan Ravindranath
>                          Parthasarathi Ravindran
>                          Paul Kyzivat
> 	Filename        : draft-ietf-siprec-metadata-21.txt
> 	Pages           : 32
> 	Date            : 2016-03-18
> 
> 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:
> https://tools.ietf.org/html/draft-ietf-siprec-metadata-21
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-siprec-metadata-21
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec