IETF Logo Mail Archive

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

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

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ES679-00062z-F0; Wed, 19 Oct 2005 01:03:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ES676-00060M-L9 for sipping@megatron.ietf.org; Wed, 19 Oct 2005 01:03:44 -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 BAA20984 for <sipping@ietf.org>; Wed, 19 Oct 2005 01:03:35 -0400 (EDT)
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ES6Il-0006wP-FK for sipping@ietf.org; Wed, 19 Oct 2005 01:15:48 -0400
Received: from rcdn-vpn-cluster-2-23.cisco.com ([12.5.186.26]) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id j9J58fKg007368 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 19 Oct 2005 00:08:42 -0500
Subject: RE: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt
From: Dean Willis <dean.willis@softarmor.com>
To: Francois Audet <audet@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF04CE9A10@zrc2hxm0.corp.nortel.com>
References: <1ECE0EB50388174790F9694F77522CCF04CE9A10@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain
Date: Wed, 19 Oct 2005 00:02:12 -0500
Message-Id: <1129698132.22142.311.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Cc: "Elwell, John" <john.elwell@siemens.com>, Paul Kyzivat <pkyzivat@cisco.com>, sipping <sipping@ietf.org>, "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 Tue, 2005-10-18 at 16:22 -0500, Francois Audet wrote:

> My issue is when the endpoint is "faking" the 486 because there was
> never any 
> 486 received. I think a GW (or B2BUA or SIP phone) sending a 302 with an
> embedded
> fake 486 just to make the other end believe (through History-Info or
> not) that
> it was Call Forward Busy is an abuse of the protocol.
> 
> If there is a 486 Reason in there, it should be because there was a 486
> received.

Well, if I send you a 302 because I would have sent you a 486 if I
hadn't had an alternative (i.e. a call-forward because I was busy here)
is that faking? 


Can't I legimately file a "History-Info" saying I redirected you for a
reason? If so, what other reason would you suggest I use?

What if the 302 were being generated bya B2BUA instead of a terminal UA?

Or is History-Info just sort of broken when generated by a UA?

--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

v2.26.15 | Report a Bug | By Email | System Status