IETF Logo Mail Archive

Re: [Geopriv] Document listing standardized Geopriv rules?

"James M. Polk" <jmpolk@cisco.com> Fri, 19 January 2007 21:15 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H814u-0006aX-Uq; Fri, 19 Jan 2007 16:15:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H814t-0006Zt-PT for geopriv@ietf.org; Fri, 19 Jan 2007 16:15:15 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H814r-0003l1-Ff for geopriv@ietf.org; Fri, 19 Jan 2007 16:15:15 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 19 Jan 2007 13:15:03 -0800
X-IronPort-AV: i="4.13,212,1167638400"; d="scan'208"; a="51183957:sNHT1351955010"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l0JLF3h2025028; Fri, 19 Jan 2007 16:15:03 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l0JLF3VT016585; Fri, 19 Jan 2007 16:15:03 -0500 (EST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 19 Jan 2007 16:15:02 -0500
Received: from jmpolk-wxp.cisco.com ([10.89.20.45]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 19 Jan 2007 16:15:02 -0500
Message-Id: <4.3.2.7.2.20070119150552.02a65e68@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 19 Jan 2007 15:15:01 -0600
To: Matt Lepinski <mlepinski@bbn.com>, geopriv@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Geopriv] Document listing standardized Geopriv rules?
In-Reply-To: <45B12DD0.50508@bbn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-OriginalArrivalTime: 19 Jan 2007 21:15:02.0995 (UTC) FILETIME=[E2762230:01C73C0E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1222; t=1169241303; x=1170105303; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com> |Subject:=20Re=3A=20[Geopriv]=20Document=20listing=20standardized=20Geopr iv=20rules? |Sender:=20 |To:=20Matt=20Lepinski=20<mlepinski@bbn.com>,=20geopriv@ietf.org; bh=63i+1d4YtswWr25RYRXWukJxR8SD6jFqA4tOlsQfLZ8=; b=UkW1YwSrUvKuvdmQUYPYwtJ70O18X+DxDHFzLoy/REmZaKD8egj1eluej2jvbhQ011bOvXCq bTtt+WjOh2ncLrqpIx1OWIRGD8fjSXYV2ByOuY2bnbADq912KimpI5GF;
Authentication-Results: rtp-dkim-1; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc:
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
Errors-To: geopriv-bounces@ietf.org

Matt

Common rules for both Geopriv and SIMPLE (combined) are in
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-common-policy-11.txt

Geopriv Rules unique to Geopriv (meaning not SIMPLE) are in
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-policy-10.txt

SIMPLE has its own unique rules doc like the one above.

Neither discuss (I do not believe) the rule you mention, but this was 
discussed at the last IETF meeting and on the lists (Geopriv, ECRIT and SIP).

The table in Conveyance-06, section 5.3, is unique to the Conveyance doc, I 
believe.

At 03:45 PM 1/19/2007 -0500, Matt Lepinski wrote:
>I was reading the latest draft of the SIP conveyance draft (-06) which 
>references the particular rule: routing-query-allowed  (in Section 5.3 of 
>the document)
> From context, it seems that this must be a Geopriv rule regarding the use 
> of Location Information.
>
>Is there a document somewhere that lists standardized Geopriv rules (such 
>as routing-query-allowed) and their meanings?
>
>Thanks a lot,
>- Matt Lepinski :->
>
>
>_______________________________________________
>Geopriv mailing list
>Geopriv@ietf.org
>https://www1.ietf.org/mailman/listinfo/geopriv

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv

v2.23.0 | Report a Bug | By Email