[Ietf-not43] #6 inetDnsDomain objects and 2251 referrals

[Andrew Newton]

Eric A. Hall wrote:
1  > A referral entry:
2  >
3  >     cn=www.example.com,cn=...
4  >       cn: www.example.com
5  >       objectClass: top
6  >       objectClass: inetResources
7  >       objectClass: inetDnsDomain
8  >       objectClass: referral
9  >       ref: ldap:///cn=host1.example.net,cn=inetResources,dc=...
10 >
11 >       [No other attributes allowed.]

I think the confusion is over lines 7 & 8.  How could it be either-or 
when your text says "also"?  Anyway, I believe I understand what you are 
saying.

I believe this comes down to a difference between 2251 style referrals 
and the named subordinate references in 3296.  After reading 3296, it 
would seem my original point is still somewhat valid because your draft 
does not mention the use of the manageDsaIT control.  You should add 
text requiring the recognition of it by the server and the use of it by 
the client.  Otherwise, all those domain variants you mentioned will 
fill up the result set before any valid response.

I also do not see where the thin registry model referral/reference is 
defined. But that should be a simple addition, correct?

-andy