[Geopriv] consensus call: authenticated and asserted identities

"Tschofenig, Hannes" <hannes.tschofenig@siemens.com> Fri, 15 July 2005 14:58 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtRdd-0005HN-JK; Fri, 15 Jul 2005 10:58:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtRdb-0005Gm-Rm for geopriv@megatron.ietf.org; Fri, 15 Jul 2005 10:58:03 -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 KAA13632 for <geopriv@ietf.org>; Fri, 15 Jul 2005 10:58:00 -0400 (EDT)
Received: from lizzard.sbs.de ([194.138.37.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtS6O-0003tH-MX for geopriv@ietf.org; Fri, 15 Jul 2005 11:27:51 -0400
Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by lizzard.sbs.de (8.12.6/8.12.6) with ESMTP id j6FEvpBS026745 for <geopriv@ietf.org>; Fri, 15 Jul 2005 16:57:51 +0200
Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net [157.163.133.222]) by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id j6FEvpin000111 for <geopriv@ietf.org>; Fri, 15 Jul 2005 16:57:51 +0200
Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.146]) by fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.0); Fri, 15 Jul 2005 17:01:16 +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
Date: Fri, 15 Jul 2005 16:57:50 +0200
Message-ID: <ECDC9C7BC7809340842C0E7FCF48C393421E32@MCHP7IEA.ww002.siemens.net>
Thread-Topic: consensus call: authenticated and asserted identities
Thread-Index: AcWIg6NFVFYMy+QKT9GSDk9UBTx0qwAv8n5A
From: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
To: GEOPRIV <geopriv@ietf.org>
X-OriginalArrivalTime: 15 Jul 2005 15:01:16.0625 (UTC) FILETIME=[0CDDE410:01C5894E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: quoted-printable
Subject: [Geopriv] consensus call: authenticated and asserted identities
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 all, 

as raised in a recent discussion about the xml schema of the
common-policy document there might not be a desire to differentiate
between authenticated and asserted identity. 

background:
-----------

we used the term authenticated identity if the policy server PS itself
verified the identity of the watcher/recipient (WR) (typically using
cryptographic means).

we used the term asserted identity if the policy server PS verified that
the WR was authenticated by another party (PS would have to trust the
other party). as an example, the identity enhancements described in RFC
3325 would fit into this category. the PS only gets the assurance that
another party performed the authentication. 

if a rule cannot distinguish between these two concepts then the rule
make implicitly needs to trust the parties trusted by the policy server.


question: 
---------

should we combine the concepts of authenticated and asserted identities
(and therefore avoiding a differentiation between them)?  

ciao
hannes




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