[Sip] Resource Priority Header namespaces

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 01 November 2007 18:23 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Inehe-0001HF-2r; Thu, 01 Nov 2007 14:23:38 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Inehd-0001Gv-GI for sip-confirm+ok@megatron.ietf.org; Thu, 01 Nov 2007 14:23:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Inehd-0001Gn-6h for sip@ietf.org; Thu, 01 Nov 2007 14:23:37 -0400
Received: from bender-mail.tigertech.net ([64.62.209.30]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1InehX-0004Ft-19 for sip@ietf.org; Thu, 01 Nov 2007 14:23:37 -0400
Received: from localhost (localhost [127.0.0.1]) by bender.tigertech.net (Postfix) with ESMTP id 4ECEC7DEA for <sip@ietf.org>; Thu, 1 Nov 2007 11:23:15 -0700 (PDT)
Received: from JMHLap3.joelhalpern.com (pool-162-83-78-52.culp.east.verizon.net [162.83.78.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bender.tigertech.net (Postfix) with ESMTP id 6B6597DA8 for <sip@ietf.org>; Thu, 1 Nov 2007 11:23:13 -0700 (PDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 01 Nov 2007 14:23:09 -0400
To: sip@ietf.org
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-Id: <20071101182313.6B6597DA8@bender.tigertech.net>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on bender.tigertech.net
X-Spam-Status: No, hits=4.3 tagged_above=-999.0 required=7.0 tests=MSGID_FROM_MTA_ID, RCVD_IN_SORBS_DUL, SPF_NEUTRAL
X-Spam-Level: ****
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [Sip] Resource Priority Header namespaces
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

I read over the draft in last call requesting new RPH namespace assignments.
In and of itself it looks non-objectionable.  While I don't 
understand the need for that many name spaces, or those specific 
values, my first reaction is to say "okay" anyway.

However, I went and looked at RFC4412, which defines the header 
namespace registration.
That RFC calls for a standard track RFC for defining namespaces.
And the text is quite explicit that one should not create a 
multiplicity of namespaces, but should try to use existing spaces first.

So, unless we want to check RFC4412, it seems that the request for 32 
namespaces in
	draft-ietf-sip-rph-new-namespaces-00.txt
really needs more explanation / justification.

Yours,
Joel M. Halpern



_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip