IETF Logo Mail Archive

Re: [sipcore] geo URI and conveyance: conclusion?

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Mon, 26 July 2010 15:17 UTC

Return-Path: <alexander.mayrhofer@nic.at>
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 DF0253A6807 for <sipcore@core3.amsl.com>; Mon, 26 Jul 2010 08:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.604
X-Spam-Level:
X-Spam-Status: No, score=-0.604 tagged_above=-999 required=5 tests=[AWL=0.826, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 01aVfPMYH6fq for <sipcore@core3.amsl.com>; Mon, 26 Jul 2010 08:17:23 -0700 (PDT)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) by core3.amsl.com (Postfix) with ESMTP id 66BDE3A686E for <sipcore@ietf.org>; Mon, 26 Jul 2010 08:17:16 -0700 (PDT)
Received: from nics-exch.sbg.nic.at ([10.17.175.3]) by mail.sbg.nic.at over TLS secured channel with XWall v3.45 ; Mon, 26 Jul 2010 17:17:35 +0200
Received: from nics-mail.sbg.nic.at (10.17.175.2) by NICS-EXCH.sbg.nic.at (10.17.175.3) with Microsoft SMTP Server id 14.0.694.0; Mon, 26 Jul 2010 17:17:35 +0200
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 26 Jul 2010 17:17:34 +0200
Message-ID: <8BC845943058D844ABFC73D2220D46650943B128@nics-mail.sbg.nic.at>
In-Reply-To: <201007261510.o6QFAaa3010310@rtp-core-2.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sipcore] geo URI and conveyance: conclusion?
Thread-Index: Acss1LmFCudfXwsZTqezBRaozLkaiAAAC4GQ
References: <8B0A9FCBB9832F43971E38010638454F03EB77364D@SISPE7MB1.commscope.com> <201007261510.o6QFAaa3010310@rtp-core-2.cisco.com>
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: "James M. Polk" <jmpolk@cisco.com>, "Thomson, Martin" <Martin.Thomson@andrew.com>, sipcore@ietf.org
X-XWALL-BCKS: auto
Subject: Re: [sipcore] geo URI and conveyance: conclusion?
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 15:17:24 -0000

> I believe the agreement in the room was to explicitly avoid it (i.e., 
> "MUST NOT appear in the Geolocation header value (i.e., 
> locationValue)"). As it's too close to being a data-URL (per Adam).

I wasn't in the room for the discussion. But i have to disagree that the
geo: URI scheme is "close to being a data-URL". While the data: URI
scheme has opaque semantics by definition, the geo: URI was specifically
developed to have precise and unambigious semantics associated with its
components, and a lot of time was spent on this.

So, if "too close to data-URL" translates into "lack of semantics", than
this is definitely true for the data: scheme, but definitely not for the
geo: scheme.

Alex

v2.23.0 | Report a Bug | By Email