Re: [cuss] [Gen-art] review: draft-ietf-cuss-sip-uui-10

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 27 January 2014 18:16 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: cuss@ietfa.amsl.com
Delivered-To: cuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B83701A001E; Mon, 27 Jan 2014 10:16:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 GM-epQnU6wHm; Mon, 27 Jan 2014 10:16:25 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 07AFD1A022F; Mon, 27 Jan 2014 10:16:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id D5E3C1004C9; Mon, 27 Jan 2014 10:16:22 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id EBCB11004C7; Mon, 27 Jan 2014 10:16:21 -0800 (PST)
Message-ID: <52E6A274.5020307@joelhalpern.com>
Date: Mon, 27 Jan 2014 13:16:20 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Alan Johnston <alan.b.johnston@gmail.com>
References: <5195550A.3000608@nostrum.com> <519920BA.9040308@joelhalpern.com> <CAKhHsXHpOKaCb5M1j=H=j8z+dDsWtuKXmK_vFE9qsKSKv3mAEQ@mail.gmail.com>
In-Reply-To: <CAKhHsXHpOKaCb5M1j=H=j8z+dDsWtuKXmK_vFE9qsKSKv3mAEQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-cuss-sip-uui-all@tools.ietf.org, "cuss@ietf.org" <cuss@ietf.org>
Subject: Re: [cuss] [Gen-art] review: draft-ietf-cuss-sip-uui-10
X-BeenThere: cuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" <cuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cuss>, <mailto:cuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cuss/>
List-Post: <mailto:cuss@ietf.org>
List-Help: <mailto:cuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cuss>, <mailto:cuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 18:16:26 -0000

Thank you Alan.  Those changes fully address my comments.
Yours,
Joel

On 1/27/14 8:28 AM, Alan Johnston wrote:
> Joel,
>
> Thanks for your review of the document.  We have made the changes you
> suggested in your review in the -12 version.
>
> http://www.ietf.org/id/draft-ietf-cuss-sip-uui-12.txt
>
> Let us know if there are any other issues.
>
> - Alan -
>
>
> On Sun, May 19, 2013 at 1:58 PM, Joel M. Halpern <jmh@joelhalpern.com
> <mailto:jmh@joelhalpern.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
>     <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-cuss-sip-uui-10
>          A Mechanism for Transporting User to User
>              Call Control Information in SIP
>     Reviewer: Joel M. Halpern
>     Review Date: 19-May-2013
>     IETF LC End Date: 29-May-2013
>     IESG Telechat date: N/A
>
>     Summary: This document is nearly ready for publication as a Proposed
>     Standard
>
>     Major issues:
>
>     Minor issues:
>          The requirements discussions for redirection and referral
>     (second paragraph of section 3, in regards REQ-3) includes what
>     appears to be normative requirements on redirecting devices.
>     a) This would seem to belong in section 4 on Normative Definition.
>     b) It would seem that there ought to be some discussion of what
>     happens with redirecting devices that do not understand this new
>     UUI. (I presume things work, but I don't see how.)
>
>     Nits/editorial comments:
>          In section 8.2, given that this is a WG document, should the
>     "the authors believe" actually be "the WG believes"?  Or even, given
>     IETF rough consensus on this document, "the IETF believes"?
>     _________________________________________________
>     cuss mailing list
>     cuss@ietf.org <mailto:cuss@ietf.org>
>     https://www.ietf.org/mailman/__listinfo/cuss
>     <https://www.ietf.org/mailman/listinfo/cuss>
>
>