IETF Logo Mail Archive

Re: [sipcore] RFC 3261: 305 Use Proxy

worley@ariadne.com (Dale R. Worley) Tue, 10 December 2013 19:16 UTC

Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 740181AE1BC for <sipcore@ietfa.amsl.com>; Tue, 10 Dec 2013 11:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X1BqpQ0DnJGT for <sipcore@ietfa.amsl.com>; Tue, 10 Dec 2013 11:16:20 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id BC99D1AE1BA for <sipcore@ietf.org>; Tue, 10 Dec 2013 11:16:09 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id rBAJFBQD025807 for <sipcore@ietf.org>; Tue, 10 Dec 2013 14:15:13 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id rBAJCR3p571693 for <sipcore@ietf.org>; Tue, 10 Dec 2013 14:12:27 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id rBAJCRAQ571973; Tue, 10 Dec 2013 14:12:27 -0500 (EST)
Date: Tue, 10 Dec 2013 14:12:27 -0500
Message-Id: <201312101912.rBAJCRAQ571973@shell01.TheWorld.com>
From: worley@ariadne.com
Sender: worley@ariadne.com
To: sipcore@ietf.org
In-reply-to: <576A8B541C219D4E9CEB1DF8C19C7B881A06D0EA@MBX08.citservers.local> (brett@broadsoft.com)
References: <576A8B541C219D4E9CEB1DF8C19C7B881A06D0EA@MBX08.citservers.local>
Subject: Re: [sipcore] RFC 3261: 305 Use Proxy
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Dec 2013 19:16:21 -0000

> From: Brett Tate <brett@broadsoft.com>

> What is the expected behavior concerning how to handle a 305's
> Contact: replace Request-URI or utilized as a Route header?  The
> snippet indicates that the unstated assumption is that it populates
> the Request-URI.

That's tricky.  305 is part of the 3xx family, so ideally you want to
handle its Contact header like you'd handle the Contact header for 301
and 302.  In those cases, you put the Contact URI in the request-URI.

But that doesn't seem to match the semantics of 305, which is
specifically to direct the upstream entity to send the request to a
particular proxy.

I suppose you could satisfy both requirements by a trick:  The URI in
the Contact of a 305 would be
<original-request-URI>?Route=<desired-proxy>

That's not satisfying either.

Dale

v2.23.0 | Report a Bug | By Email