Re: [Sipping] Method for URI-List servers to refuse the handling of a URI-List
Jonathan Rosenberg <jdrosen@cisco.com> Wed, 01 November 2006 22:12 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfOJZ-0008JH-VL; Wed, 01 Nov 2006 17:12:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfOJY-0008JA-3J for sipping@ietf.org; Wed, 01 Nov 2006 17:12:04 -0500
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.43) id 1GfOJV-0006hW-Nw for sipping@ietf.org; Wed, 01 Nov 2006 17:12:04 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 01 Nov 2006 14:12:01 -0800
X-IronPort-AV: i="4.09,379,1157353200"; d="scan'208"; a="753592999:sNHT49983092"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA1MC1Si025367; Wed, 1 Nov 2006 14:12:01 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kA1MC0Ao005234; Wed, 1 Nov 2006 14:12:00 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 1 Nov 2006 14:12:00 -0800
Received: from [10.32.241.148] ([10.32.241.148]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 1 Nov 2006 14:12:00 -0800
Message-ID: <45491BAF.5000703@cisco.com>
Date: Wed, 01 Nov 2006 17:11:59 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Jani Hautakorpi (JO/LMF)" <jani.hautakorpi@ericsson.com>
Subject: Re: [Sipping] Method for URI-List servers to refuse the handling of a URI-List
References: <44A9009E.3070906@ericsson.com>
In-Reply-To: <44A9009E.3070906@ericsson.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Nov 2006 22:12:00.0539 (UTC) FILETIME=[C0D7B6B0:01C6FE02]
DKIM-Signature: a=rsa-sha1; q=dns; l=1481; t=1162419121; x=1163283121; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:Re=3A=20[Sipping]=20Method=20for=20URI-List=20servers=20to=20refuse=20th e=20handling=0A=20of=20a=09URI-List; X=v=3Dcisco.com=3B=20h=3D4mCP91ItWOiUFfVv2vM/+hDntwc=3D; b=k6drrkJqsDT9o0xXOxfOfuklUqliNxPhrYWaZWmcHsRlGie/R4BoiBEHgJ1nHZ5eUGMd+TJm 8hgYpwcLt/v3NaPKLV7vxtObi7G40Vx4srnYbmSPIjd47LKUCY7SFwnT;
Authentication-Results: sj-dkim-4.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: sipping@ietf.org, gonzalo.camarillo@ericsson.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org
I don't really understand the motivation for this draft. There are countless reasons why a server might not want to process a request. Why is it important in this case to communicate the reason back to the UA? Why not just send a 400 and be done with it? Is it commonly expected that a server will refuse to fan out a request? What remediation to you expect the client to take? -Jonathan R. Jani Hautakorpi (JO/LMF) wrote: > Hi all, > > We have written a draft describing a method for URI-list servers to > refuse the handling of a URI-List. You can find the draft from: > > http://www.ietf.org/internet-drafts/draft-hautakorpi-sipping-uri-list-handling-refused-00.txt > > > The motivation for writing this draft is that currently URI-List servers > don't have any explicit method for denying the handling of incoming > request. This draft describes just that in a form of a new response > code, 495 (URI-List Handling Refused). > > I would be very interested in hearing any comments/ideas/thoughts that > you might have about this draft. So, please send your input to me > (jani.hautakorpi@ericsson.com). > > -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Cisco Fellow Parsippany, NJ 07054-2711 Cisco Systems jdrosen@cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] Method for URI-List servers to refuse t… Jani Hautakorpi (JO/LMF)
- Re: [Sipping] Method for URI-List servers to refu… Jonathan Rosenberg
- Re: [Sipping] Method for URI-List servers to refu… Gonzalo Camarillo