Re: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt

Dean Willis <dean.willis@softarmor.com> Wed, 19 October 2005 15:13 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESFci-0004KV-Bl; Wed, 19 Oct 2005 11:13:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESFcf-0004KG-Sd for sipping@megatron.ietf.org; Wed, 19 Oct 2005 11:12:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22394 for <sipping@ietf.org>; Wed, 19 Oct 2005 11:12:49 -0400 (EDT)
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESFoQ-0006OM-1V for sipping@ietf.org; Wed, 19 Oct 2005 11:25:07 -0400
Received: from rcdn-vpn-cluster-2-59.cisco.com ([12.5.186.26]) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id j9JFHvKx013023 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 19 Oct 2005 10:17:57 -0500
Subject: Re: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt
From: Dean Willis <dean.willis@softarmor.com>
To: David R Oran <oran@cisco.com>
In-Reply-To: <968B784F-106E-494E-AE37-8E2EEEEA1BCA@cisco.com>
References: <1ECE0EB50388174790F9694F77522CCF04CE9A10@zrc2hxm0.corp.nortel.com> <1129698132.22142.311.camel@localhost> <968B784F-106E-494E-AE37-8E2EEEEA1BCA@cisco.com>
Content-Type: text/plain
Date: Wed, 19 Oct 2005 10:11:26 -0500
Message-Id: <1129734686.23926.17.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>, Francois Audet <audet@nortel.com>, "Elwell, John" <john.elwell@siemens.com>, Paul Kyzivat <pkyzivat@cisco.com>, "Michael Hammer (mhammer)" <mhammer@cisco.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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

On Wed, 2005-10-19 at 09:22 -0400, David R Oran wrote:

> What we don't have a way of saying is "I'm busy, go try this other  
> place".
. . .
> A third way is to in fact invent a new 3xx which means exactly "Try  
> this other place because I'm busy" (as opposed to moved temporarily).
> 
> Why don't we just do the last of these? It's completely  
> straightforward to me.

At first glance, it sounds fine. But then people are going to want to
say "I'm busy to you because you're on my warn list, please try this
other contact " and "I'm busy because my QoS is saturated, please try
this other destination" and "I'm busy because I'm in a meeting, but I
could do text messaging too" and a million other things. We can't just
add a new response code for every one of these.

There are some fundamental problems with intertwingling applications
that use SIP with the SIP protocol itself, and I think that the path
you're suggesting leads to continuances of this layer violation model.

Of course, we could just accept that the application-protocol layer is
completely violated in the SIP model, and just make the best of what we
have. I suppose that is an alternative.

--
Dean



_______________________________________________
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