AW: AW: AW: [Geopriv] common policy document

"Tschofenig, Hannes" <hannes.tschofenig@siemens.com> Wed, 13 July 2005 12:53 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dsgjk-0005EX-6D; Wed, 13 Jul 2005 08:53:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dsgjf-00056u-7R for geopriv@megatron.ietf.org; Wed, 13 Jul 2005 08:53:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03374 for <geopriv@ietf.org>; Wed, 13 Jul 2005 08:53:09 -0400 (EDT)
Received: from gecko.sbs.de ([194.138.37.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DshC4-0007Gd-8R for geopriv@ietf.org; Wed, 13 Jul 2005 09:22:32 -0400
Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by gecko.sbs.de (8.12.6/8.12.6) with ESMTP id j6DCqmbF013584; Wed, 13 Jul 2005 14:52:48 +0200
Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net [157.163.133.222]) by mail2.sbs.de (8.12.6/8.12.6) with ESMTP id j6DCqkpl006318; Wed, 13 Jul 2005 14:52:48 +0200
Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.146]) by fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.0); Wed, 13 Jul 2005 14:56:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: AW: AW: AW: [Geopriv] common policy document
Date: Wed, 13 Jul 2005 14:52:45 +0200
Message-ID: <ECDC9C7BC7809340842C0E7FCF48C393421DC5@MCHP7IEA.ww002.siemens.net>
Thread-Topic: AW: AW: [Geopriv] common policy document
Thread-Index: AcWHoZVjNCV6VPToSRKzyBygiogH8gABxedw
From: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
X-OriginalArrivalTime: 13 Jul 2005 12:56:11.0609 (UTC) FILETIME=[3EB3D490:01C587AA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: quoted-printable
Cc: GEOPRIV <geopriv@ietf.org>, aki.niemi@nokia.com
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>
Sender: geopriv-bounces@ietf.org
Errors-To: geopriv-bounces@ietf.org

hi henning, 

the <any-identity> element is a condition element that matches any
authenticated and asserted identity.

as an example, the following two rules (that are shown in ruleset (1))
are equivalent to rule, which uses the <any-identity> element, shown in
ruleset (2) :

1) WITHOUT <any-identity>:

<?xml version="1.0" encoding="UTF-8"?>
<ruleset xmlns="urn:ietf:params:xml:ns:common-policy">

  <rule id="f3g44r2">
    <conditions>
      <identity/>
    </conditions>
  </rule>

  <rule id="f3g44r2">
    <conditions>
      <asserted/>
    </conditions>
  </rule>
</ruleset>

1) WITH <any-identity>:

<?xml version="1.0" encoding="UTF-8"?>
<ruleset xmlns="urn:ietf:params:xml:ns:common-policy">

  <rule id="f3g44r2">
    <conditions>
      <any-identity/>
    </conditions>
  </rule>
</ruleset>

with more complex rules (e.g., <any-identity/> with multiple
<except-domain> elements) it would be necessary to replicate them. 

does this make more sense? 

ciao
hannes

> To help the discussion along, can you summarize the two 
> options or given 
> an example?
> 
> 
> Tschofenig, Hannes wrote:
> > hi jari, 
> > 
> > thanks for your comment. please find a short response below: 
> > 
> > ~snip~snip~
> > 
> > 
> >>I'll have another question about common-pol-05. I don't understand
> >><domain>s in <any-identity>. It seems to me that they break the
> >>consistent model of "anything", why can't you get similar thing with
> >><domain>s in <identity> ?
> > 
> > 
> > this is a very good question. the <any-identity> was proposed as a
> > condition element that matches any authenticated and 
> asserted identity.
> > the <any-identity> is basically a short version of 
> <identity/> combined
> > with <asserted/>. the <any-identity> with the domain 
> element can also be
> > replaced by the respective combination of <identity> and <asserted>.
> > 
> > hence, your comment raises the question whether we can 
> actually omit the
> > <any-identity> element. at the interim meeting there was no comment
> > regarding this issue. what do you think?
> > 
> > ciao
> > hannes
> > 
> >>br,
> >>Jari
> >>
> >>
> > 
> > 
> > _______________________________________________
> > 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
> 

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