[sipcore] 4244bis: How does History-Info account for Route?
"Worley, Dale R (Dale)" <dworley@avaya.com> Tue, 05 July 2011 19:13 UTC
Return-Path: <dworley@avaya.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9293521F887C for <sipcore@ietfa.amsl.com>; Tue, 5 Jul 2011 12:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.474
X-Spam-Level:
X-Spam-Status: No, score=-103.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j9NF3fQp7Gho for <sipcore@ietfa.amsl.com>; Tue, 5 Jul 2011 12:13:52 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 0868121F857F for <sipcore@ietf.org>; Tue, 5 Jul 2011 12:13:51 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtgGAKthE06HCzI1/2dsb2JhbABTqApwB6wng3UCmy6DNIMCBJdLiz0
X-IronPort-AV: E=Sophos;i="4.65,481,1304308800"; d="scan'208";a="254982822"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 05 Jul 2011 15:13:50 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 05 Jul 2011 15:07:03 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 5 Jul 2011 15:13:49 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Tue, 05 Jul 2011 15:10:49 -0400
Thread-Topic: 4244bis: How does History-Info account for Route?
Thread-Index: AQHMO0ernbOrqXUQ2U2Mi4/0UjWpfg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5732@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [sipcore] 4244bis: How does History-Info account for Route?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 19:13:54 -0000
How does the History-Info reflect the actions due to Route headers? As written, while the request is being routed due to the Route URIs, the request-URI does not change, and so many History-Info entries show the request-URI (and give no information about where the request was being sent). Oddly, I ran into this while I was considering a practical use for H-I: It allows the upstream proxies to determine if a fork reached a particular downstream proxy, and so helps with the "redundant paths" routing issue. Dale
- [sipcore] 4244bis: How does History-Info account … Worley, Dale R (Dale)
- Re: [sipcore] 4244bis: How does History-Info acco… Shida Schubert