IETF Logo Mail Archive

Re: [sipcore] composition or just indirection

"Thomson, Martin" <Martin.Thomson@andrew.com> Mon, 26 July 2010 11:55 UTC

Return-Path: <Martin.Thomson@andrew.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 D5FCB3A680A for <sipcore@core3.amsl.com>; Mon, 26 Jul 2010 04:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level:
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599]
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 Xk+4U09B49sc for <sipcore@core3.amsl.com>; Mon, 26 Jul 2010 04:55:14 -0700 (PDT)
Received: from csmailgw1.commscope.com (csmailgw1.commscope.com [198.135.207.244]) by core3.amsl.com (Postfix) with ESMTP id EE4E33A686E for <sipcore@ietf.org>; Mon, 26 Jul 2010 04:55:13 -0700 (PDT)
Received: from [10.86.20.102] ([10.86.20.102]:4164 "EHLO ACDCE7HC1.commscope.com") by csmailgw1.commscope.com with ESMTP id S28661517Ab0GZLze (ORCPT <rfc822; sipcore@ietf.org>); Mon, 26 Jul 2010 06:55:34 -0500
Received: from SISPE7HC2.commscope.com (10.97.4.13) by ACDCE7HC1.commscope.com (10.86.20.102) with Microsoft SMTP Server (TLS) id 8.1.436.0; Mon, 26 Jul 2010 06:43:54 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC2.commscope.com ([fe80::58c3:2447:f977:57c3%10]) with mapi; Mon, 26 Jul 2010 19:43:52 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: "Thomson, Martin" <Martin.Thomson@andrew.com>, "James M. Polk" <jmpolk@cisco.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Mon, 26 Jul 2010 19:43:51 +0800
Thread-Topic: [sipcore] composition or just indirection
Thread-Index: Acsr/f+IF10+DI+ZSEm+KNE7/3XQhAABbmxAACxyrhA=
Message-ID: <8B0A9FCBB9832F43971E38010638454F03EB773642@SISPE7MB1.commscope.com>
References: <8B0A9FCBB9832F43971E38010638454F03EB772EBB@SISPE7MB1.commscope.com> <C86A11BF.41D5D%jon.peterson@neustar.biz> <8B0A9FCBB9832F43971E38010638454F03EB7730BA@SISPE7MB1.commscope.com> <4C459BD7.9050007@cisco.com> <8B0A9FCBB9832F43971E38010638454F03EB773153@SISPE7MB1.commscope.com> <201007251333.o6PDXUS9019180@rtp-core-1.cisco.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw1.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Cc: Roger Marshall <RMarshall@telecomsys.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] composition or just indirection
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: Mon, 26 Jul 2010 11:55:14 -0000

I wrote: 
> > >"
> > >The Geolocation header identifies a source of
> > >location information.  This might be a PIDF-LO
> > >document that is identified by value or
> > >reference, or a geo: URI that includes location information directly.
> > >
> > >A Geolocation header indicates that a) that this
> > >location information is somehow applicable to
> > >the entity that initiated the request and b)
> > >that this location information might be relevant
> > >to the processing of the SIP request.
> > >"

To this, it has been suggested that we expand on this to the following effect:

The subject of a PIDF document is identified in the "entity" attribute of the document element.  If this is identical to the identity provided by the UAC in the From header of the request, then the PIDF-LO describes the location of the UAC.

--Martin

v2.20.0 | Report a Bug | By Email