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

"Richard L. Barnes" <> Mon, 26 July 2010 14:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E686F3A6982 for <>; Mon, 26 Jul 2010 07:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.478
X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EnML52MisqQY for <>; Mon, 26 Jul 2010 07:27:19 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A1B003A6948 for <>; Mon, 26 Jul 2010 07:27:19 -0700 (PDT)
Received: from [] (port=51728 by with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <>) id 1OdOea-0000zU-3B; Mon, 26 Jul 2010 10:27:40 -0400
Message-Id: <>
From: "Richard L. Barnes" <>
To: Alexander Mayrhofer <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="Apple-Mail-4--947935964"
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 26 Jul 2010 16:27:38 +0200
References: <> <>
X-Mailer: Apple Mail (2.936)
Cc:, "Thomson, Martin" <>
Subject: Re: [sipcore] geo URI and conveyance: conclusion?
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 26 Jul 2010 14:27:21 -0000

I was afraid that Alex would notice :)

The concern here is about privacy, since the geo URI scheme doesn't  
include GEOPRIV-like rules.  In fact, the privacy part of RFC 5870 has  
the following text:
However, if a 'geo' URI is used in a context where it identifies the  
location of a Target, it becomes part of a Location Object and is  
therefore subject to GEOPRIV rules. Therefore, when 'geo' URIs are put  
into such contexts, the privacy requirements of RFC 3693 MUST be met.

So in order to use a geo URI in SIP, we would need to do something  
about privacy rules.  The only easy approach that occurs to me is to  
specify fixed rules that come along with putting a GEO URI in a  
Geolocation header.  Suggested text:
Including a "geo:" URI in a Geolocation header associates that  
location with the entity that originated the SIP message, making it in  
effect a Location Object in the terms of RFC 3693. In particular,  
there is a need for such location objects to have privacy rules that  
accompany the object.  A "geo:" URI in a Geolocation header is  
assigned a default set of privacy rules, equivalent to the default  
rules in RFC 4119:
   o retransmission-allowed: false
   o retention-expires: 24 hours from time of transmission
   o ruleset-reference: null
   o note-well: null

On Jul 26, 2010, at 4:05 PM, Alexander Mayrhofer wrote:

>> I missed the conclusions regarding geo URI.  I got the bit
>> where we decided that we needed to have _some_ text, but I'm
>> not sure what we decided what the text might look like.
> Adding "geo:" to SIP Location Conveyance was actually one of the first
> applications that came to my mind when i started the draft. I'm more
> than happy to help with the text - i'm in Maastricht for the whole  
> week
> for face to face discussions.
> Alex
> _______________________________________________
> sipcore mailing list