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 necessarily the right place for it ...
On Jan 24, 2008, at 12:34, Drummond Reed wrote: > 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 > semantics that the XRI is an abstract identifier for the resource. > So Boeing > wants to establish OIDs for primary-xri (value of the canonical XRI) > and > alt-xri (value of any other XRI synonym). > > OpenID URLs really have the same problem -- yes, they are URLs, but > they are > URLs with the specific property of being OpenID URLs. The LDAP URI > attribute > doesn't have that semantics. > > I don't think Marty's on this list but I'm cc'ing him. > > =Drummond > > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >> Behalf >> Of McGovern, James F (HTSC, IT) >> Sent: Thursday, January 24, 2008 10:12 AM >> To: Johannes Ernst >> Cc: specs@openid.net >> Subject: RE: Integration with Enterprise Directory Services >> >> 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 (HTSC, IT) >> Cc: specs@openid.net >> Subject: Re: Integration with Enterprise Directory Services >> >> 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 (HTSC, IT) wrote: >> >>> 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, James F (HTSC, IT); specs@openid.net >>> Subject: RE: Integration with Enterprise Directory Services >>> >>> James, are you asking about the recommended format for saving an >>> OpenID identifier in an LDAP directory? If so, I know Boeing has >>> done >>> some work in that area -- I can check with their directory guru. >>> >>> =Drummond >>> >>>> -----Original Message----- >>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >>>> Behalf Of McGovern, James F (HTSC, IT) >>>> Sent: Wednesday, January 23, 2008 1:47 PM >>>> To: specs@openid.net >>>> Subject: Integration with Enterprise Directory Services >>>> >>>> What is the standard recommendation for how identifiers get >>>> stored in >> >>>> enterprise directory services (e.g. LDAP)? >>>> >>>> > > > _______________________________________________ > specs mailing list > specs@openid.net > http://openid.net/mailman/listinfo/specs _______________________________________________ specs mailing list specs@openid.net http://openid.net/mailman/listinfo/specs
