Re: [Geopriv] HELD Context & Common Policy
Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Sun, 13 July 2008 19:51 UTC
Return-Path: <geopriv-bounces@ietf.org>
X-Original-To: geopriv-archive@megatron.ietf.org
Delivered-To: ietfarch-geopriv-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E6AC3A68A7; Sun, 13 Jul 2008 12:51:06 -0700 (PDT)
X-Original-To: geopriv@core3.amsl.com
Delivered-To: geopriv@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B21E3A68A7 for <geopriv@core3.amsl.com>; Sun, 13 Jul 2008 12:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.423
X-Spam-Level:
X-Spam-Status: No, score=-2.423 tagged_above=-999 required=5 tests=[AWL=0.176, 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 MCpR0JnrHViV for <geopriv@core3.amsl.com>; Sun, 13 Jul 2008 12:51:03 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 3164E3A6891 for <geopriv@ietf.org>; Sun, 13 Jul 2008 12:51:02 -0700 (PDT)
Received: (qmail invoked by alias); 13 Jul 2008 19:51:25 -0000
Received: from a91-154-105-144.elisa-laajakaista.fi (EHLO [192.168.255.3]) [91.154.105.144] by mail.gmx.net (mp063) with SMTP; 13 Jul 2008 21:51:25 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/rvZ04gIXriQc4FQ4TBS4kI2ViP7dLUdzqXhe8vd qYJK363Luvi5H/
Message-ID: <487A5CC1.80708@gmx.net>
Date: Sun, 13 Jul 2008 22:51:29 +0300
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>
References: <487909AA.9020203@gmx.net> <487A5562.8000908@bbn.com>
In-Reply-To: <487A5562.8000908@bbn.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.62
Cc: GEOPRIV <geopriv@ietf.org>
Subject: Re: [Geopriv] HELD Context & Common Policy
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: geopriv-bounces@ietf.org
Errors-To: geopriv-bounces@ietf.org
That's certainly possible. Richard Barnes wrote: > It seems a little odd to put the "snapshot" designation in the > "transformations" field. I think of the transformations as modifying > whatever LO the LS started with, whereas, the snapshot flag tells the > LS what LO to start with. > > Would it be appropriate to use the "actions" stanza to describe what > location the LS should use as a base, namely snapshot vs. current? > > <actions> > <co:determine-snapshot time="2008-07-124T8:00:00+01:00"/> > </actions> > > <actions> > <co:determine-current /> > </actions> > > --Richard > > > > Hannes Tschofenig wrote: >> At the interim meeting we had discussions how the authorization >> policies in HELD Context >> http://tools.ietf.org/id/draft-winterbottom-geopriv-held-context-02.txt >> could be expressed using the Common Policy framework. >> >> Here is an example: >> >> <?xml version="1.0" encoding="UTF-8"?> >> <ruleset >> xmlns="urn:ietf:params:xml:ns:common-policy" >> xmlns:gp="urn:ietf:params:xml:ns:geolocation-policy" >> xmlns:lp="urn:ietf:params:xml:ns:basic-location-profiles" >> xmlns:co="urn:ietf:params:xml:ns:held-context"> >> >> <rule id="AA56ia9"> >> <conditions> >> <co:max-use>10</co:max-use> >> <validity> >> <from>2008-07-124T8:00:00+01:00</from> >> <until>2008-07-12T10:00:00+01:00</until> >> </validity> >> </conditions> >> <actions/> >> <transformations> >> <co:snapshot>yes</co:snapshot> >> <gp:provide-location >> profile="civic-transformation"> >> <lp:provide-civic>full</lp:provide-civic> >> </gp:provide-location> >> </transformations> >> </rule> >> </ruleset> >> >> This is more complex than the current encoding scheme in the HELD >> context document. >> >> Ciao >> Hannes >> >> _______________________________________________ >> Geopriv mailing list >> Geopriv@ietf.org >> https://www.ietf.org/mailman/listinfo/geopriv >> _______________________________________________ Geopriv mailing list Geopriv@ietf.org https://www.ietf.org/mailman/listinfo/geopriv
- Re: [Geopriv] HELD Context & Common Policy Richard Barnes
- Re: [Geopriv] HELD Context & Common Policy Hannes Tschofenig
- [Geopriv] HELD Context & Common Policy Hannes Tschofenig
- Re: [Geopriv] HELD Context & Common Policy Thomson, Martin