IETF Logo Mail Archive

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

Dean Willis <dean.willis@softarmor.com> Tue, 18 October 2005 20:01 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERxeS-0001T0-Rn; Tue, 18 Oct 2005 16:01:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERxeP-0001S4-UQ for sipping@megatron.ietf.org; Tue, 18 Oct 2005 16:01:34 -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 QAA26097 for <sipping@ietf.org>; Tue, 18 Oct 2005 16:01:26 -0400 (EDT)
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERxpx-0000rH-B8 for sipping@ietf.org; Tue, 18 Oct 2005 16:13:32 -0400
Received: from [64.101.149.214] (dhcp-64-101-149-214.cisco.com [64.101.149.214] (may be forged)) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id j9IK6M4w004948 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 18 Oct 2005 15:06:23 -0500
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF04C4DB64@zrc2hxm0.corp.nortel.com>
References: <1ECE0EB50388174790F9694F77522CCF04C4DB64@zrc2hxm0.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <EAB5D538-0562-4801-A018-A1CEE75C892F@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt
Date: Tue, 18 Oct 2005 15:01:17 -0500
To: Francois Audet <audet@nortel.com>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens.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 Oct 17, 2005, at 5:47 PM, Francois Audet wrote:

> You mean adding a Reason of 486 inside 302????
>
> That seems highly confusing to me.

That's more or less what I think I proposed, except I buried it in a  
History-Info header field.

One of the things that puzzles me about H-I is that while the RFC  
allows use of H-I in 302 responses, it doesn't talk about it in any  
great detail.

It would be very nice to have an H-I use-cases draft with some good  
examples.

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