[Sip] History-Info: UA loose route versus Target header

"Mary Barnes" <mary.barnes@nortel.com> Thu, 13 March 2008 15:39 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: ietfarch-sip-archive@core3.amsl.com
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DB6A3A6E92; Thu, 13 Mar 2008 08:39:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.24
X-Spam-Level:
X-Spam-Status: No, score=-101.24 tagged_above=-999 required=5 tests=[AWL=-0.804, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SBpDyqFreU5I; Thu, 13 Mar 2008 08:39:18 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 083543A6C83; Thu, 13 Mar 2008 08:39:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C4FA3A6E70 for <sip@core3.amsl.com>; Thu, 13 Mar 2008 08:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w5UlbAFufnqe for <sip@core3.amsl.com>; Thu, 13 Mar 2008 08:39:15 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 70F2E3A6C43 for <sip@ietf.org>; Thu, 13 Mar 2008 08:39:15 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id m2DFWVc11207 for <sip@ietf.org>; Thu, 13 Mar 2008 15:32:31 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 13 Mar 2008 10:34:13 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE02640F48@zrc2hxm1.corp.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: History-Info: UA loose route versus Target header
Thread-Index: AciFH7Dyq9TdpeR0RBun7/oZCM2XWw==
From: Mary Barnes <mary.barnes@nortel.com>
To: sip@ietf.org
Subject: [Sip] History-Info: UA loose route versus Target header
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0437546595=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Per my comments at the microphone, here's my assessment of the
difference between the two documents as they apply to History-Info as a
potential solution.

draft-rosenberg-sip-ua-loose-route-02 clearly states that History-Info
functionally can be used to solve the problem described in that
document.  However, Jonathan's objective is to solve a fundamental
problem of not distinguishing routing versus re-targeting (read section
5).  This document would actually change the content of the History-Info
headers for the same requests, just as it's already identified in RFC
4244 that if you have loose routing in general, that the information is
different in History-Info. 

The document  draft-holmberg-sip-target-uri-delivery-01.txt  doesn't do
anything to change fundamental SIP processing. It just adds another
header that contains information that would already be contained in
History-Info. History-info provides a complete history of the processing
of a request, with the indexing provided by the entries and the reasons,
you know exactly why a request was either "retargetted" or "re-routed".
The examples in the appendix would apply to the use cases you are
attempting to solve as described in Jonathan's document. 

Mary. 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip