> > 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 sq
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
2008 3:34 PM
> To: McGovern, James F (HTSC, IT)
> Cc:
> Subject: Re: Integration with Enterprise Directory Services
>
> James,
>
> It appears you possess a good amount of knowledge on this topic.
>
> I believe that if you were to come up with some preliminary
> imp
James,
It appears you possess a good amount of knowledge on this topic.
I believe that if you were to come up with some preliminary
implementation guidelines (and presented them here for review), you
would not be stepping on anyone's toes.
Thank you,
John Ehn
On Jan 25, 2008, at 3:59 PM, "
Reed
Subject: RE: Integration with Enterprise Directory Services
The process to get an OID issued under the directory OID includes doing
an RFC.
The old draft (haven't touched it for about a year) can be seen at
various URLs. Here's one:
http://opends.org/source/xref/trunk/
.
>
> 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, 20
t;
> -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 necessari
, 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 attri
(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
ED]
> 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 s
, 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
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 Be
12 matches
Mail list logo
