[Gen-art] Gen-ART review of draft-ietf-sip-rph-new-namespaces-03.txt

Suresh Krishnan <suresh.krishnan@ericsson.com> Fri, 10 October 2008 20:43 UTC

Return-Path: <gen-art-bounces@ietf.org>
X-Original-To: gen-art-archive@optimus.ietf.org
Delivered-To: ietfarch-gen-art-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9F893A680B; Fri, 10 Oct 2008 13:43:09 -0700 (PDT)
X-Original-To: gen-art@core3.amsl.com
Delivered-To: gen-art@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DAB53A6889 for <gen-art@core3.amsl.com>; Fri, 10 Oct 2008 13:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.492
X-Spam-Level:
X-Spam-Status: No, score=-6.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17gM+fbibDjg for <gen-art@core3.amsl.com>; Fri, 10 Oct 2008 13:43:07 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 9503F3A680B for <gen-art@ietf.org>; Fri, 10 Oct 2008 13:43:07 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id m9AKiKJm030651; Fri, 10 Oct 2008 15:44:21 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 10 Oct 2008 15:43:32 -0500
Received: from [142.133.10.113] ([142.133.10.113]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 10 Oct 2008 15:43:32 -0500
Message-ID: <48EFBECB.9070801@ericsson.com>
Date: Fri, 10 Oct 2008 16:44:59 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, draft-ietf-sip-rph-new-namespaces@tools.ietf.org
X-OriginalArrivalTime: 10 Oct 2008 20:43:32.0107 (UTC) FILETIME=[DBA605B0:01C92B18]
Cc: sip-ads@tools.ietf.org, sip-chairs@tools.ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-sip-rph-new-namespaces-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

I am the assigned Gen-ART reviewer for
draft-ietf-sip-rph-new-namespaces-03.txt

For background on Gen-ART, please see the FAQ at
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.

Please resolve these comments along with any other Last Call comments
you may receive.

Summary: Almost ready for publication but I have a few comments.

Major
=====

* The draft assumes some kind of ordering requirement between 
namespaces. From my reading of RFC4412, this is not the case.

"Thus, a message (or a call) with the following Resource-Priority
  header value:

  dsn-000001.8

  for example, MUST NOT ever receive preferential treatment over a
  message, for example, with this Resource-Priority header value:

  dsn-000010.0

  because they are two difference namespaces"

e.g.

Consider an RP actor that supports both the namespaces, dsn-000001 and 
dsn-000010. It could maintain an ordered list which contains

dsn-000001.9
dsn-000001.8
dsn-000010.9
...
dsn-000010.0

and this is a valid priority order according to section 8.2 of RFC4412. 
Given this, why would this be considered invalid behavior if 
dsn-000001.8 DID receive preferential treatment over dsn-000010.0? This 
might be a major misunderstanding on my part. If so please correct me.

Editorial
=========

* Introduction

Replace
"Each will be preemption in nature"
with
"Each will be preemptive in nature"

Nits
====

* Form feed characters missing between Pages

Opinion(feel free to ignore)
============================

* Why so many 0's in the name of the namespace? It is really easy for 
someone to miss a 0 or two.

* Maybe you have been asked this question million times before, but are 
these many namespaces really necessary?

 From RFC4412

"Jurisdictions SHOULD
  attempt to reuse existing IANA registered namespaces where possible,
  as a goal of this document is not to have unique namespaces per
  jurisdiction serving the same purpose, with the same usage of
  priority levels."


Cheers
Suresh







_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art