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

"jmh.direct" <jmh.direct@joelhalpern.com> Fri, 27 January 2017 23:01 UTC

Return-Path: <jmh.direct@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 7DCED129A89; Fri, 27 Jan 2017 15:01:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 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_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 YoKIxf5QUmZE; Fri, 27 Jan 2017 15:01:10 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 AD7EA129989; Fri, 27 Jan 2017 15:01:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 5C2255C1706; Fri, 27 Jan 2017 15:01:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1485558070; bh=YdeywLLisBIpyciUoZNKpf1BVgMdG2tgM+I7PE24ksg=; h=Date:Subject:From:To:Cc:From; b=c2icAdOwTFbdkVe3X5GrMqgQKcLiNjcDaTtUBzoUDtPcDcb2dUbpKOm9pOzaPa8VF puafUFdswy651sXbx7Ll9VnKTvVQmDS+g9kmC8IRlaf0kjHR0OslEbLXzd2cphuQCT p7H5a8ls7krO9XqkWA7A+YxKmCTggf2umJ2U2O1s=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.38.157.105] (unknown [166.175.185.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 7A4C51C0487; Fri, 27 Jan 2017 15:01:09 -0800 (PST)
Date: Fri, 27 Jan 2017 17:01:05 -0600
Subject: Re: Review of draft-mohali-dispatch-cause-for-service-number-12
Message-ID: <gayq4rno45534tb465mg9d0g.1485558065488@email.android.com>
Importance: normal
From: "jmh.direct" <jmh.direct@joelhalpern.com>
To: Ben Campbell <ben@nostrum.com>, marianne.mohali@orange.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_2249831801890"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8jiKatLNkysD-D4saus5YKRRh7M>
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-mohali-dispatch-cause-for-service-number.all@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, 27 Jan 2017 23:01:12 -0000

Thank you.That seems a reasonable compromise among the constraints. 
Ypyrs,Joel


Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone
-------- Original message --------From: Ben Campbell <ben@nostrum.com> Date: 1/27/17  14:17  (GMT-06:00) To: marianne.mohali@orange.com Cc: Joel Halpern <jmh@joelhalpern.com>om>, gen-art@ietf.org, ietf@ietf.org, draft-mohali-dispatch-cause-for-service-number.all@ietf.org, dispatch@ietf.org Subject: Re: Review of draft-mohali-dispatch-cause-for-service-number-12 
On 27 Jan 2017, at 11:15, marianne.mohali@orange.com wrote:

> Hi Joel,
>
> I have submitted a new version (v-13) of the draft.
> I have addressed your comment for IPv6 addresses format in the 
> example.
> Concerning your major comment, the discussion is leaded by Ben.

To that point: Please note that version 13 adds a comment to the end of 
the introduction to make it clear that this draft documents something 
that another group (3GPP) does. It is not an IETF standard.

Thanks!

Ben.

>
> I hope I have correctly address your comment.
> https://datatracker.ietf.org/doc/draft-mohali-dispatch-cause-for-service-number/
>
> Best regards,
> Marianne
>
>> -----Message d'origine-----
>> De : Joel Halpern [mailto:jmh@joelhalpern.com]
>> Envoyé : vendredi 16 décembre 2016 04:57
>> À : gen-art@ietf.org
>> Cc : ietf@ietf.org; draft-mohali-dispatch-cause-for-service-
>> number.all@ietf.org; dispatch@ietf.org
>> Objet : Review of draft-mohali-dispatch-cause-for-service-number-12
>>
>> 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.)
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez 
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les 
> messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, 
> deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or 
> privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and 
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have 
> been modified, changed or falsified.
> Thank you.