Re: [sipcore] #8: It's not clear when a Proxy should/should-not add H-I for "internal" stuff

"Worley, Dale R (Dale)" <dworley@avaya.com> Tue, 31 August 2010 15:53 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24BC03A6846 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 08:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.393
X-Spam-Level:
X-Spam-Status: No, score=-102.393 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, 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 i0fE-psPM+tV for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 08:53:17 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 268DE3A6804 for <sipcore@ietf.org>; Tue, 31 Aug 2010 08:53:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,299,1280721600"; d="scan'208";a="32483851"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 31 Aug 2010 11:53:47 -0400
X-IronPort-AV: E=Sophos;i="4.56,299,1280721600"; d="scan'208";a="504634280"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 31 Aug 2010 11:53:12 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 31 Aug 2010 11:53:12 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: sipcore issue tracker <trac@tools.ietf.org>, "hkaplan@acmepacket.com" <hkaplan@acmepacket.com>
Date: Tue, 31 Aug 2010 11:52:22 -0400
Thread-Topic: [sipcore] #8: It's not clear when a Proxy should/should-not add H-I for "internal" stuff
Thread-Index: ActIb6Rq4hMNrNIkT7KdEmrkk4kNqgAtNtvL
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79BFE@DC-US1MBEX4.global.avaya.com>
References: <064.2fac1c1d9b3ab9e13c8bc32cb433819f@tools.ietf.org>
In-Reply-To: <064.2fac1c1d9b3ab9e13c8bc32cb433819f@tools.ietf.org>
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
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] #8: It's not clear when a Proxy should/should-not add H-I for "internal" stuff
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 31 Aug 2010 15:53:19 -0000

________________________________________
From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of sipcore issue tracker [trac@tools.ietf.org]

 This isn't clear enough.  Let's suppose you have an "alias", like
 john.smith@ssp.com, but your real registered AoR is jsmith@ssp.com.  When
 the proxy receives a request for john.smith@ssp.com, it looks up the
 location service database and ultimately gets a registered contact for
 jsmith@ssp.com.  In some architectures, the proxy would internally go from
 john.smith@ssp.com to jsmith@ssp.com, and then to the registered contact.
 So does it add a H-I for jsmith@ssp.com?
_______________________________________________

If the H-I is to document "How did this request get here?", intermediate targets should be listed.

Dale