Review of draft-mohali-dispatch-cause-for-service-number-12
Joel Halpern <jmh@joelhalpern.com> Fri, 16 December 2016 03:57 UTC
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E8C129480; Thu, 15 Dec 2016 19:57:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: gen-art@ietf.org
Subject: Review of draft-mohali-dispatch-cause-for-service-number-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148186064804.24550.3460112022117949321.idtracker@ietfa.amsl.com>
Date: Thu, 15 Dec 2016 19:57:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xvKSnIi6Ymwe-dtG63ayfqvf5Ow>
Cc: 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
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 03:57:28 -0000
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.)
- Review of draft-mohali-dispatch-cause-for-service… Joel Halpern
- Re: Review of draft-mohali-dispatch-cause-for-ser… Ben Campbell
- Re: Review of draft-mohali-dispatch-cause-for-ser… Joel M. Halpern
- Re: Review of draft-mohali-dispatch-cause-for-ser… Ben Campbell
- Re: Review of draft-mohali-dispatch-cause-for-ser… Joel M. Halpern
- Re: Review of draft-mohali-dispatch-cause-for-ser… Cullen Jennings
- RE: Review of draft-mohali-dispatch-cause-for-ser… marianne.mohali
- Re: Review of draft-mohali-dispatch-cause-for-ser… Mary Barnes
- Re: Review of draft-mohali-dispatch-cause-for-ser… Ben Campbell
- Re: Review of draft-mohali-dispatch-cause-for-ser… Ben Campbell
- Re: [dispatch] Review of draft-mohali-dispatch-ca… Adam Roach
- Re: [dispatch] Review of draft-mohali-dispatch-ca… Ben Campbell
- Re: [dispatch] Review of draft-mohali-dispatch-ca… Robert Sparks
- Re: [dispatch] Review of draft-mohali-dispatch-ca… Ben Campbell
- Re: [dispatch] Review of draft-mohali-dispatch-ca… Cullen Jennings (fluffy)
- RE: Review of draft-mohali-dispatch-cause-for-ser… marianne.mohali
- Re: Review of draft-mohali-dispatch-cause-for-ser… Ben Campbell