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

"Elwell, John" <john.elwell@siemens.com> Wed, 12 October 2005 06:49 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPaQh-0004MD-D7; Wed, 12 Oct 2005 02:49:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPaQf-0004M8-Oc for sipping@megatron.ietf.org; Wed, 12 Oct 2005 02:49:33 -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 CAA00539 for <sipping@ietf.org>; Wed, 12 Oct 2005 02:49:31 -0400 (EDT)
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPaat-00082Z-0u for sipping@ietf.org; Wed, 12 Oct 2005 03:00:10 -0400
Received: from CONVERSION-DAEMON.siemenscomms.co.uk by siemenscomms.co.uk (PMDF V6.0-24 #40642) id <0IO800301ITVNF@siemenscomms.co.uk> for sipping@ietf.org; Wed, 12 Oct 2005 07:46:43 +0100 (BST)
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82]) by siemenscomms.co.uk (PMDF V6.0-24 #40642) with ESMTP id <0IO800JBEITUXA@siemenscomms.co.uk>; Wed, 12 Oct 2005 07:46:42 +0100 (BST)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service (5.5.2657.72) id <TTA71WDL>; Wed, 12 Oct 2005 07:49:10 +0100
Content-return: allowed
Date: Wed, 12 Oct 2005 07:49:09 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt
To: Paul Kyzivat <pkyzivat@cisco.com>, "Dolly, Martin C, ALABS" <mdolly@att.com>
Message-id: <50B1CBA96870A34799A506B2313F266706A2A4D4@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>, GARCIN Sebastien RD-CORE-ISS <sebastien.garcin@francetelecom.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

Paul,

> I don't know how valid an argument this is, but I am finding an 
> "impedence mismatch" between the approaches in the two 
> drafts, that is 
> disconcerting.
> 
> - In H-I, the reason is associated with the uri that
>    was retargetted-from
> 
> - In draft...retargeting... the reason is associated
>    with the uri that was retargetted-to
> 
> When you combine them, you get one entry with a 
> retargetted-from uri and 
> the reason why retargetting from it happened, and then you 
> get another 
> entry for the retargetted-to uri with the reason why 
> retargetting to it 
> happened. If they agree then they are redundant. If they are 
> different, 
> then one has to deal with why they are different.
> 
> I'd be more comfortable if all the reasons for a particular 
> retargetting 
> were gathered up in *one* place.

[JRE] Your observation is correct. The way we (the authors) looked at is was
that the first entry shows why the attempt to send the request to the first
target failed and the second entry shows why the new target was selected
(e.g., forwarding to it because of busy). I agree it is equally valid to
look at the other way round.

John

_______________________________________________
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