IETF Logo Mail Archive

Re: [sipcore] #38: How is the mapping of a GRUU into its UA Contact marked?

"Worley, Dale R (Dale)" <dworley@avaya.com> Tue, 07 September 2010 17:33 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 576B63A6858 for <sipcore@core3.amsl.com>; Tue, 7 Sep 2010 10:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.461
X-Spam-Level:
X-Spam-Status: No, score=-102.461 tagged_above=-999 required=5 tests=[AWL=0.138, 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 8XVF1hGI0Lq4 for <sipcore@core3.amsl.com>; Tue, 7 Sep 2010 10:33:51 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 214A03A6822 for <sipcore@ietf.org>; Tue, 7 Sep 2010 10:33:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,329,1280721600"; d="scan'208";a="33472956"
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; 07 Sep 2010 13:34:14 -0400
X-IronPort-AV: E=Sophos;i="4.56,329,1280721600"; d="scan'208";a="508164886"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 Sep 2010 13:33:38 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 7 Sep 2010 13:33:38 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Shida Schubert <shida@ntt-at.com>
Date: Tue, 07 Sep 2010 13:32:41 -0400
Thread-Topic: [sipcore] #38: How is the mapping of a GRUU into its UA Contact marked?
Thread-Index: ActOkElRPYrULL5HTK2xkxsZ1dHkUQAImKnv
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C24@DC-US1MBEX4.global.avaya.com>
References: <061.f3e7a20653cdf403663b0bffba4c43b4@tools.ietf.org>, <DF18BFD3-F136-4BC0-81B1-D16DA4657951@ntt-at.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C09@DC-US1MBEX4.global.avaya.com> <35ECC1DD-6DD6-4103-AC47-A2F9A0D69DAD@ntt-at.com> <4C80EF97.4090703@cisco.com>, <2E92FEF2-DCBD-44A9-869B-CCE2BB98278F@ntt-at.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C19@DC-US1MBEX4.global.avaya.com>, <54579397-D4DC-4043-8D42-7E6F357E5F6F@ntt-at.com>
In-Reply-To: <54579397-D4DC-4043-8D42-7E6F357E5F6F@ntt-at.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
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] #38: How is the mapping of a GRUU into its UA Contact marked?
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, 07 Sep 2010 17:33:52 -0000

________________________________________
From: Shida Schubert [shida@ntt-at.com]

I guess we could but is it really necessary when "gr" tag is present for GRUU?
_______________________________________________

That's a possibility.  But just because the mapped-from URI is a GRUU doesn't mean that the mapped-to URI was done by looking up the GRUU's binding -- there may be some other mapping mechanism that is involved.

Dale

v2.23.0 | Report a Bug | By Email