For CardSpace, MS and other providers store it in the SeeAlso
attribute. Figured OpenID in the next rev of the spec should talk more
about implementation details.
-Original Message-
From: Drummond Reed [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 23, 2008 11:57 PM
To: McGovern,
This doesn't necessarily belong into the core protocol specs, as many
implementations will store OpenIDs in places other than directories.
However, it would make sense to have a common convention for that ...
perhaps a separate 1-page standard?
On Jan 24, 2008, at 7:02, McGovern, James F
Would even take it to ensuring that directories use a common OID and not
just making up their own attribute. Staying equivalent to Cardspace is a
good thing.
-Original Message-
From: Johannes Ernst [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 24, 2008 1:00 PM
To: McGovern, James F
Yes, Marty Schleiff at Boeing is working on an RFC for how to represent XRIs
in an LDAP directory for that very reason -- to establish standard OIDs for
this attribute. LDAP already has a URI attribute type, but downcasting an
XRI into a URI just to squeeze it into that attribute type loses the
Would you be willing to propose something?
On Jan 24, 2008, at 10:11, McGovern, James F (HTSC, IT) wrote:
Would even take it to ensuring that directories use a common OID and
not
just making up their own attribute. Staying equivalent to Cardspace
is a
good thing.
-Original
Is there a draft available?
BTW, why would that be an RFC, as opposed to, say, an OASIS standard
(XRI) or an OpenID standard? Because of LDAP? As a user-centric
technology, I'm not sure that a preferred close relationship to
corporate directories -- as opposed to other possible places -- is
