Re: Review of draft-mohali-dispatch-cause-for-service-number-12

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 16 December 2016 04:35 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9957F12953B; Thu, 15 Dec 2016 20:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level:
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 1jpheVUCvDyL; Thu, 15 Dec 2016 20:35:35 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 4A274129522; Thu, 15 Dec 2016 20:35:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 364312464C8; Thu, 15 Dec 2016 20:35:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1481862935; bh=6vXV2rr/B3UwgrS0xbTS4N2j0NwrC8S+WT4aJ6HSYzM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=TKyct95vbs8amrnYnJLmYGBk9/W7JcR2CUeqIDPe2Jn0318I2oiO/C+FQQedbY6P/ L4AXHDgJatqCQJMy3BWs1QuwBqXbh70Heg+NIHQ7TXRKJgfoA5q+RS0HPkVexQtYoR iTTF40ZyJR16dR3woox4eicXYssA7+acUwG2k3c4=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 70812240F4B; Thu, 15 Dec 2016 20:35:34 -0800 (PST)
Subject: Re: Review of draft-mohali-dispatch-cause-for-service-number-12
To: Ben Campbell <ben@nostrum.com>, Joel Halpern <jmh@joelhalpern.com>
References: <148186064804.24550.3460112022117949321.idtracker@ietfa.amsl.com> <9E288F8F-BD52-49D0-83B2-472F1B223127@nostrum.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <f0e5f66a-a7be-8d4e-a865-2ba4a27d6a3a@joelhalpern.com>
Date: Thu, 15 Dec 2016 23:35:33 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <9E288F8F-BD52-49D0-83B2-472F1B223127@nostrum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6rUWb35ak5m6qDwNWqhlkPPbCfI>
Cc: gen-art@ietf.org, dispatch@ietf.org, ietf@ietf.org, draft-mohali-dispatch-cause-for-service-number.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2016 04:35:36 -0000

I see your point about this adding a value to the entry created by RFC 4458.
Is there a reason this can not simply be PS?  The fact that 4458 is 
Informational does not, as far as I can tell, justify continuing the 
error.  While this is for a 3GPP usage, it appears to have been reviewed 
by the Dispatch WG sufficiently to justify PS.
One could argue that there is a down-ref issue, but the fact that the 
field is in a standards-track required registry would seem to make that 
a moot point.

Yours,
Joel

PS: It would seem that WG discussion of that sort is something we would 
like to see in Shepherd writeups.

On 12/15/16 11:28 PM, Ben Campbell wrote:
> Hi Joel,
>
> Thanks for the comments. There has been a fair amount of discussion
> about the status of the draft. The situation is clearly not optimal, and
> I welcome input on how to straighten it out.
>
> The rational so far has been that this draft updates RFC 4588, which is
> informational. It adds some additional values and related semantics for
> the "cause" parameter from 4588. It does not register new parameters;
> rather it adds itself as a reference in the existing "cause"
> registration. This is mainly a courtesy to readers. (There is no
> sub-registry for "cause" parameter values.) We might could get by
> without that change, since in a perfect world people following the IANA
> reference to 4588 would notice the "Updated by..." tag.
>
> The gotcha is that RFC 4588 would not be possible as an informational
> today; it would not have standing to register the "cause" parameter. But
> at the time it was published, there was a lack of clarity around the
> "standards action" policy for the SIP URI parameters registry. Making
> the new values from _this_ draft standards track, when the parameter
> itself is not, doesn't seem appropriate. We had some discussion about
> whether we should promote 4588 to PS, but there was not consensus to do
> so when it was published, and I don't see reason to expect that to have
> changed.
>
> This draft is primarily intended to meet a need in 3GPP, where I
> understand they are effectively already doing this. Would it help to
> more tightly scope this as "Here's something 3GPP is doing..." rather
> than as a general mechanism?
>
> Thanks!
>
> Ben.
>
> On 15 Dec 2016, at 21:57, Joel Halpern wrote:
>
>> Reviewer: Joel Halpern
>> Review result: Ready with Issues
>>
>> Major:
>>     This document defines a new code for use in SIP, and specifies new
>> behavior both for the code itself and for its use in history-info.  I
>> am thus confused as to how this can be an informational RFC.  It looks
>> like it either Proposed Standard or experimental.  Yes, I see that RFC
>> 4458, which this updates is Informational.  But just because we did it
>> wrong before does not make that behavior correct now.  In addition to
>> my understanding of the roles of different RFCs, I note that RFC 3969
>> and the IANA registry both state that this assignment must be made by
>> a standards track RFC.
>>
>> Minor:
>>    Given our emphasis on IPv6 over IPv4, would it not make sense for
>> the examples to use IPv6 addresses?  (Inspired by the Id-Nits alert.)