Re: [sipcore] Location-conveyance, option tags and URI scheme support

"Thomson, Martin" <Martin.Thomson@andrew.com> Wed, 10 November 2010 03:50 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 78C373A6407 for <sipcore@core3.amsl.com>; Tue, 9 Nov 2010 19:50:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level:
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[AWL=-0.549, 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 d9cdTkJsZLYn for <sipcore@core3.amsl.com>; Tue, 9 Nov 2010 19:50:52 -0800 (PST)
Received: from csmailgw2.commscope.com (csmailgw2.commscope.com [198.135.207.242]) by core3.amsl.com (Postfix) with ESMTP id EA4C03A67B1 for <sipcore@ietf.org>; Tue, 9 Nov 2010 19:50:51 -0800 (PST)
Received: from [10.86.20.103] ([10.86.20.103]:17049 "EHLO ACDCE7HC2.commscope.com") by csmailgw2.commscope.com with ESMTP id S488567Ab0KJDvR (ORCPT <rfc822; sipcore@ietf.org>); Tue, 9 Nov 2010 21:51:17 -0600
Received: from SISPE7HC2.commscope.com (10.97.4.13) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Tue, 9 Nov 2010 21:50:54 -0600
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC2.commscope.com ([fe80::58c3:2447:f977:57c3%10]) with mapi; Wed, 10 Nov 2010 11:50:50 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Peterson, Jon" <jon.peterson@neustar.biz>, "sipcore@ietf.org" <sipcore@ietf.org>
Date: Wed, 10 Nov 2010 11:50:47 +0800
Thread-Topic: [sipcore] Location-conveyance, option tags and URI scheme support
Thread-Index: AcuAe6GOF4JGUmD4TEKI1iKWD+xc3AAA+EWgAAGMM9AAAQptYA==
Message-ID: <8B0A9FCBB9832F43971E38010638454F03F33652F2@SISPE7MB1.commscope.com>
References: <C9001EB7.480D2%jon.peterson@neustar.biz> <8B0A9FCBB9832F43971E38010638454F03F33652DB@SISPE7MB1.commscope.com> <A444A0F8084434499206E78C106220CA023587F13A@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA023587F13A@MCHP058A.global-ad.net>
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 csmailgw2.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Subject: Re: [sipcore] Location-conveyance, option tags and URI scheme support
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: Wed, 10 Nov 2010 03:50:54 -0000

On 2010-11-10 at 11:24:10, Elwell, John wrote:
> > I see little reason to separately identify HELD.  HELD
> > dereference works with HTTP GET well enough and a
> > HELD-capable client can recognize a HELD-capable server if
> > they care about using HELD (for quality of service
> > constraints and so on).
> [JRE] But the point of supporting HELD is that you expect a PIDF-LO in
> the response. Just supporting HTTP does not necessarily mean you are
> able to handle PIDF-LO in a response?

The point of supporting Geolocation-http is that you support acquisition of a PIDF-LO using HTTP (and maybe HELD).  It's a continuum of support that doesn't require discrete steps (in my opinion).

--Martin