Re: [Sip] -resource-priority-05.txt: Comments and Recommendations (2)

David R Oran <oran@cisco.com> Sat, 13 November 2004 16:24 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15509 for <sip-web-archive@ietf.org>; Sat, 13 Nov 2004 11:24:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CT0id-00072t-BB for sip-web-archive@ietf.org; Sat, 13 Nov 2004 11:25:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CT0a2-0004Rq-1e; Sat, 13 Nov 2004 11:16:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CT0Tg-0003V9-R6 for sip@megatron.ietf.org; Sat, 13 Nov 2004 11:10:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14778 for <sip@ietf.org>; Sat, 13 Nov 2004 11:10:15 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CT0VI-0006T3-O6 for sip@ietf.org; Sat, 13 Nov 2004 11:11:57 -0500
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-1.cisco.com with ESMTP; 13 Nov 2004 08:24:12 -0800
X-BrightmailFiltered: true
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iADG9hKU018458; Sat, 13 Nov 2004 08:09:43 -0800 (PST)
Received: from [10.32.245.156] (stealth-10-32-245-156.cisco.com [10.32.245.156]) by imail.cisco.com (8.12.11/8.12.10) with SMTP id iADGAFaZ022976; Sat, 13 Nov 2004 08:10:16 -0800
In-Reply-To: <19d.2bd091f1.2ec6afb7@aol.com>
References: <19d.2bd091f1.2ec6afb7@aol.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Message-Id: <6A965F36-358E-11D9-97C5-000A95C73842@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: David R Oran <oran@cisco.com>
Subject: Re: [Sip] -resource-priority-05.txt: Comments and Recommendations (2)
Date: Sat, 13 Nov 2004 11:09:37 -0500
To: Mpierce1@aol.com
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs"; t:"1100362216.643056"; x:"432200"; a:"rsa-sha1"; b:"nofws:2164"; e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw" "eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU" "tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc="; s:"qCkUOjXsuVolwwWRA987ZTFE3qQA/txGHRg21HxtJYhXnutXvzkgt96XYT/3A" "W2ljsvKMsPGYxYZpqYnk5zmdSEhgdH6WGG4CuRBNZWf1VjufXnjbkCi2AQH4v" "hY3nBiNhzcUnWkPer7YAypO7T1cghIPXWfGU+mjUHp/cIYbq8="; c:"From: David R Oran <oran@cisco.com>"; c:"Subject: Re: [Sip] -resource-priority-05.txt: Comments and Recommendat" "ions (2)"; c:"Date: Sat, 13 Nov 2004 11:09:37 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com"; c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: quoted-printable
Cc: sip@ietf.org
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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable

On Nov 12, 2004, at 7:30 PM, Mpierce1@aol.com wrote:

> In a message dated 11/11/2004 6:12:39 PM Eastern Standard Time, 
> coreya@nortelnetworks.com writes:
>
>
> 2. Is it wise or valid to explicitly allow a proxy to "upgrade" or
>  "downgrade" the  n-p values in a message?
> ---- I'm coming at this from the DSN perspective, but wps and/or ets 
> may
>  allow this kind of thing.  While the DSN/DSRN/(Q735) would not, that
>  does not invalidate the concept.
>
>
>
> If one understands the "proxy" to be the entity which provides call 
> processing logic and which validates the calling party's authority to 
> use the priority level which they signaled in the INVITE (see 
> draft-pierce-tsvwg-assured-service-arch-01), then it should be valid 
> for that proxy to "downgrade" the signaled value to the level allowed 
> for that user before forwarding the INVITE rather than blocking the 
> call. This behavior should not be disallowed by the R-P header draft 
> for any namespace.
>
As long as you have the concept of namespaces, with different policies 
for different namespaces, it follows logically to allow such policies. 
If someone wants a namespace that has a "reject call rather than 
downgrade" as its policy, why prohibit it? Or are you arguing that the 
R-P draft should be silent on upgrade/downgrade/reject other than to 
point out that the allowed behaviors are part of the namespace policy 
definition? If that's what you're saying, I'm ok with that.

Dave.


> I can't think of any "upgrading" case, but there is not reason for the 
> R-P header draft to disallow it.
>
> Mike Pierce
> Artel_______________________________________________
> 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
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com


_______________________________________________
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