Re: [Gen-art] Gen-ART LC review of draft-ietf-siprec-protocol-16

Peter Yee <peter@akayla.com> Wed, 17 June 2015 18:25 UTC

Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4550B1B2C9E; Wed, 17 Jun 2015 11:25:43 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] 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 yIkPcJPKQgtS; Wed, 17 Jun 2015 11:25:41 -0700 (PDT)
Received: from p3plsmtpa08-08.prod.phx3.secureserver.net (p3plsmtpa08-08.prod.phx3.secureserver.net [173.201.193.109]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B58041B2C9D; Wed, 17 Jun 2015 11:25:41 -0700 (PDT)
Received: from [10.5.50.234] ([72.164.171.211]) by p3plsmtpa08-08.prod.phx3.secureserver.net with id hWRc1q00P4a0vuo01WRetE; Wed, 17 Jun 2015 11:25:41 -0700
User-Agent: Microsoft-MacOutlook/14.5.1.150515
Date: Wed, 17 Jun 2015 11:25:35 -0700
From: Peter Yee <peter@akayla.com>
To: eckelcu@cisco.com
Message-ID: <D1A70781.11504%peter@akayla.com>
Thread-Topic: Gen-ART LC review of draft-ietf-siprec-protocol-16
References: <D17BB964.10F58%peter@akayla.com> <D1921326.4E786%eckelcu@cisco.com> <02cf01d0a635$ad68d2f0$083a78d0$@akayla.com>
In-Reply-To: <02cf01d0a635$ad68d2f0$083a78d0$@akayla.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/Ts0mJYSTWcqAWEo4Pqdlh4rii2s>
Cc: gen-art@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, draft-ietf-siprec-protocol.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-siprec-protocol-16
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2015 18:25:43 -0000

Charles,

	Looks pretty good to me.  Thanks for considering my suggestions.

		Kind regards,
		-Peter

>-----Original Message-----
>From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
>Sent: Monday, June 01, 2015 4:24 PM
>To: Peter Yee; draft-ietf-siprec-protocol.all@tools.ietf.org
>Cc: gen-art@ietf.org; IETF Discussion Mailing List
>Subject: Re: Gen-ART LC review of draft-ietf-siprec-protocol-16
>
>Hi Peter,
>
>Thanks for your detailed review and great comments. I¹ve added proposed
>resolutions inline.
>
>On 5/16/15, 4:16 AM, "Peter Yee" <peter@akayla.com> wrote:
>
>>I am the assigned Gen-ART reviewer for this draft. For background on
>>Gen-ART, please see the FAQ at
>><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>
>>Please resolve these comments along with any other Last Call comments
>>you may receive.
>>
>>
>>Document: draft-ietf-siprec-protocol-16
>>Reviewer: Peter Yee
>>Review Date: May-15-2015
>>IETF LC End Date: May-15-2015
>>IESG Telechat date: TBD
>>
>>Summary: This draft is almost ready for publication as a proposed
>>standard but has open issues, described in the review. [Ready with
>>issues]
>>
>>The draft specifies entities and a protocol using SIP, SDP, and RTP for
>>recording communication sessions.  It provides the ability to notify
>>UAs that they are being recorded and for UAs to notify the recording
>>system of their recording preference.
>>
>>The document is well written and has no obvious major technical issues.
>>
>>
>>Major issues: None
>>
>>Minor issues:
>>
>>
>>Page 21, section 8.1.4, last sentence: what does “appropriately".
>>Specify where is the appropriate interpretation defined or provide it
>>here.
>
>I propose replacing
>"interpret the CSRC list appropriately when received." with "interpret the
>CSRC list per RFC 3550 when received."

That seems like a helpful clarification.

>>Nits:
>>
>>NB: Anything below marked with an asterisk before the line is a
>>technical change; the rest are purely editorial and of lesser importance.
>
>Lots of good catches here and all suggested changes made with the few
>exceptions noted inline.
>
>>Page 15, section 7.2, 1st paragraph, 3rd sentence: Would this sentence
>>be more correct if rewritten for clarity as: "When the SRS is ready to
>>receive recorded streams, the SRS sends a new SDP offer and sets the
>>a=recvonly attribute in the media streams.²?
>
>I think either construction gets the point across. It left as is in order
>to
>be consistent with the structure of the previous sentence.

Okay.

>>Page 33, last paragraph, 2nd sentence: Why not state this in the
>>affirmative: ³Any subsequent partial updates will only be dependent on
>>the metadata sent in this full metadata snapshot and any intervening
>>partial updates.²
>
>I find the current construction to be simpler.

As you wish. :-)

>Thanks so much,
>Charles