Re: [sipcore] composition or just indirection
"James M. Polk" <jmpolk@cisco.com> Sun, 25 July 2010 13:33 UTC
Return-Path: <jmpolk@cisco.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 DC2C33A6998 for <sipcore@core3.amsl.com>; Sun, 25 Jul 2010 06:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.527
X-Spam-Level:
X-Spam-Status: No, score=-10.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 Psz8mBZAFWgj for <sipcore@core3.amsl.com>; Sun, 25 Jul 2010 06:33:21 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id EB7293A6988 for <sipcore@ietf.org>; Sun, 25 Jul 2010 06:33:20 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.55,257,1278288000"; d="scan'208";a="138860677"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 25 Jul 2010 13:33:41 +0000
Received: from jmpolk-wxp01.cisco.com (ams3-vpn-dhcp5712.cisco.com [10.61.86.79]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o6PDXUS9019180; Sun, 25 Jul 2010 13:33:40 GMT
Message-Id: <201007251333.o6PDXUS9019180@rtp-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 25 Jul 2010 07:04:54 -0500
To: "Thomson, Martin" <Martin.Thomson@andrew.com>, Paul Kyzivat <pkyzivat@cisco.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F03EB773153@SISPE7MB1.comms cope.com>
References: <8B0A9FCBB9832F43971E38010638454F03EB772EBB@SISPE7MB1.commscope.com> <C86A11BF.41D5D%jon.peterson@neustar.biz> <8B0A9FCBB9832F43971E38010638454F03EB7730BA@SISPE7MB1.commscope.com> <4C459BD7.9050007@cisco.com> <8B0A9FCBB9832F43971E38010638454F03EB773153@SISPE7MB1.commscope.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
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: Sun, 25 Jul 2010 13:33:23 -0000
At 06:50 PM 7/20/2010, Thomson, Martin wrote: > > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]: > > Thomson, Martin wrote: > > > The Geolocation header identifies a PIDF document by value or > > > reference. A Geolocation header indicates that a) this particular > > > PIDF > > > document contains location information and b) that this location > > > information in particular may be relevant to the processing of the > > > SIP request. > > > > IMO this is *too* vague. > > > > For instance, I might want request that a call be routed *to* the phone > > closest to some geolocation. That location is also relevant to the > > processing of the request, but in an entirely different way. > >Damn. You would have to point out my big blind >spot. I've been concentrating on the >routing-based-on-caller-location use case too long. > >If we also consider that the location needs to >be attributed to a particular entity, you can >either add syntax that attempts to identify the >entity that you are talking about (a "from" or >"to" parameter might do this), or you can make >the entity constant. In the interest of >simplicity, the latter seems more fashionable: > >" >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. >" I'm reading this believing someone here believes part of -03 needs to replace text with the above, but I'm not sure which text needs replacing from this discussion. Can someone point to the paragraph in question? James >This is almost the "bold" interpretation that >says that this Targetâs location should be >considered the source of the request. It does >not imply that the Target and source are the >same identity. Nor does it expressly state that >the source is actually located anywhere in >particular, though we're walking a fairly fine line there. > >--Martin
- [sipcore] location-conveyance-03 just submitted James M. Polk
- Re: [sipcore] location-conveyance-03 just submitt… Thomson, Martin
- Re: [sipcore] location-conveyance-03 just submitt… James M. Polk
- Re: [sipcore] location-conveyance-03 just submitt… Winterbottom, James
- Re: [sipcore] location-conveyance-03 just submitt… Thomson, Martin
- Re: [sipcore] location-conveyance-03 just submitt… James M. Polk
- Re: [sipcore] location-conveyance-03 just submitt… Francois Menard
- Re: [sipcore] location-conveyance-03 just submitt… Thomson, Martin
- Re: [sipcore] location-conveyance-03 just submitt… Peterson, Jon
- Re: [sipcore] location-conveyance-03 just submitt… Thomson, Martin
- Re: [sipcore] location-conveyance-03 just submitt… Francois Menard
- Re: [sipcore] location-conveyance-03 just submitt… Roger Marshall
- Re: [sipcore] location-conveyance-03 just submitt… Winterbottom, James
- Re: [sipcore] location-conveyance-03 just submitt… Peterson, Jon
- [sipcore] composition or just indirection (was: l… Thomson, Martin
- Re: [sipcore] composition or just indirection (wa… Peterson, Jon
- Re: [sipcore] composition or just indirection (wa… Richard L. Barnes
- Re: [sipcore] composition or just indirection (wa… Peterson, Jon
- Re: [sipcore] composition or just indirection (wa… Richard L. Barnes
- Re: [sipcore] composition or just indirection (wa… James M. Polk
- Re: [sipcore] composition or just indirection (wa… James M. Polk
- Re: [sipcore] composition or just indirection (wa… Peterson, Jon
- Re: [sipcore] composition or just indirection (wa… Thomson, Martin
- Re: [sipcore] composition or just indirection (wa… Thomson, Martin
- Re: [sipcore] composition or just indirection (wa… Hannes Tschofenig
- Re: [sipcore] location-conveyance-03 just submitt… Elwell, John
- Re: [sipcore] composition or just indirection Paul Kyzivat
- Re: [sipcore] composition or just indirection Thomson, Martin
- Re: [sipcore] composition or just indirection (wa… Thomson, Martin
- Re: [sipcore] composition or just indirection Paul Kyzivat
- Re: [sipcore] location-conveyance-03 just submitt… James M. Polk
- Re: [sipcore] location-conveyance-03 just submitt… James M. Polk
- Re: [sipcore] location-conveyance-03 just submitt… James M. Polk
- Re: [sipcore] location-conveyance-03 just submitt… James M. Polk
- Re: [sipcore] location-conveyance-03 just submitt… James M. Polk
- Re: [sipcore] location-conveyance-03 just submitt… James M. Polk
- Re: [sipcore] composition or just indirection James M. Polk
- Re: [sipcore] location-conveyance-03 just submitt… Elwell, John
- Re: [sipcore] location-conveyance-03 just submitt… Thomson, Martin
- Re: [sipcore] location-conveyance-03 just submitt… Thomson, Martin
- Re: [sipcore] composition or just indirection Thomson, Martin
- Re: [sipcore] location-conveyance-03 just submitt… Brian Rosen
- Re: [sipcore] location-conveyance-03 just submitt… Richard L. Barnes
- Re: [sipcore] composition or just indirection Thomson, Martin