Re: [Sip] Resource Priority Header namespaces
Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Sun, 04 November 2007 16:13 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 1Ioi6O-000165-Nd; Sun, 04 Nov 2007 11:13:33 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Ioi6N-00015n-PH for sip-confirm+ok@megatron.ietf.org; Sun, 04 Nov 2007 11:13:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ioi6N-00015f-Fh for sip@ietf.org; Sun, 04 Nov 2007 11:13:31 -0500
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ioi6L-00028k-Ut for sip@ietf.org; Sun, 04 Nov 2007 11:13:31 -0500
Received: (qmail invoked by alias); 04 Nov 2007 16:13:28 -0000
Received: from p549869EC.dip.t-dialin.net (EHLO [192.168.1.5]) [84.152.105.236] by mail.gmx.net (mp018) with SMTP; 04 Nov 2007 17:13:28 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+Fu0AYp/mFu8DOxnfbpM8aN2TPoMjHbs+/VmUwdI gB9MmT4msY+dY2
Message-ID: <472DEFAE.2080107@gmx.net>
Date: Sun, 04 Nov 2007 17:13:34 +0100
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
Subject: Re: [Sip] Resource Priority Header namespaces
References: <20071101182313.6B6597DA8@bender.tigertech.net> <5D1A7985295922448D5550C94DE2918001886BD9@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE2918001886BD9@DEEXC1U01.de.lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: sip@ietf.org, "Joel M. Halpern" <jmh@joelhalpern.com>
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
This document seems to have its origin in a single or a small number of customers. From the text in the draft it seems the priority values for each namespace are used totally independently. I wonder whether someone has actually thought what this means for a real system when priority values of 50+ namespaces are used together. Does anyone know how the use cases are going to look like? Ciao Hannes DRAGE, Keith (Keith) wrote: > I will leave James to respond to this as it impacts the draft, but > assuming we reach that stage, I will remember this point for the PROTO > writeup. > > Regards > > Keith > > >> -----Original Message----- >> From: Joel M. Halpern [mailto:jmh@joelhalpern.com] >> Sent: Thursday, November 01, 2007 6:23 PM >> To: sip@ietf.org >> Subject: [Sip] Resource Priority Header namespaces >> >> 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 >> >> > > > _______________________________________________ > 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 > _______________________________________________ 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
- [Sip] Resource Priority Header namespaces Joel M. Halpern
- RE: [Sip] Resource Priority Header namespaces DRAGE, Keith (Keith)
- Re: [Sip] Resource Priority Header namespaces Hannes Tschofenig