On 19-Jan-06, at 2:16 PM, Dick Hardt wrote:
Temporary certificate
This is to satisfy the minimality requirement. User has cert
including
date of birth, say, and wants to prove he's over 21. So, he (or his
agent) shows the cert to some CA that produces a temporary cert
for him
saying he's over 21, which he or his agent then shows to the
relying party.
Note that this only half gets you unlinkability if the certs are
anything conventional because the CA can link the permanent and
temporary certs.
The CA is, of course, a fourth party in the transaction.
I understand this one.
I think of that as two transactions. One to acquire the claim, the other
to present the claim, even if the claim if thrown away after it's
presented.
But I can see why my wording appears to exclude that.
Proxy
Not sure exactly what to say about this, except that a proxy could
sit
between any of these parties, and the language above assumes that
it can
do so both transparently and securely. Which may not be so (that
is, it
may have to be non-transparent to remain secure) if it adds
functionality, like caching, or anonymising.
I understand what you are saying here as well (proxy has a number
of meanings)
Yeah... I just assumed that was part of the infrastructure that the
protocol
ran over... so I should call that out.
Authentication Elsewhere
It may turn out that for whatever reason I have to use multiple
agents,
so I'd like to authenticate them via my meta-agent. Unlinkably.
I would say that the meta-agent is your agent.
Yeah.
John
_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix
