RE: Implementation of 4.5.2 and 4.5.3 of RFC 2251

["Cabrera Borges, J.P." <J.P.CabreraBorges@research.kpn.com>]

> > So on my opinion, It should exit an attribute in the administrative area
> > (in a sub-entry), like the general referral, that in case that a user do
> a
> > query with a "scope=subtree", the response message, if it is the case,
> > indicates that this
> > sub-tree continues in another or others servers without having to put a
> > referral on all
> > the leaves entries of the tree (like collective attribute in X.500).
> 
> I haven't seen any attribute like the one you describe. The closest is
> the "ref" attribute which has yet to be published in an RFC or ITU
> recommendation (although there is finally a draft that contains it).
> The only other way that I have seen to get a SearchResultReference is
> when dereferencing aliases.
> 
	The attribute I describe "non-specific subordinate reference" is the
same that has been 
	already described on draft-ietf-ldapext-referral-00.txt section 5.3.
Thank you for the point.

	But, On this draft I don't understand the DN:

	dn: ref=ldap://hostB/o=abc,c=us

      Is this a valid DN? Formally speaking, it is valid but I think it has
gone out of all schemata.
      What parts of the DIT are affected by this entry?
      The draft says that "is similar to non-specific sub-ordinate reference
concept found in X.500"
so then it affects to all the leafes entries...
How does this entry affects to the search operations?

Probably the conversation is getting out of topic so I suugest, If everybody
is agree, to change 
to the conversation to the ietf mailing list "ldap-ext@netscape.com" or
other suugested mail-list. 
I'll wait for a confirmation.

Regards,
Juan Pablo