Daniel Pluta writes:
cite: "... this means longer dn's (i.e. more specific dn's) will be found first when searching..."
But, longer DNs do not neccessarily are more specific:
ou=openldap,o=rockz,c=it dc=abcdefghijklmnopqrstuvwxyz,dc=com (even longer but not more specific)
It's just the comment which is unclear. It should be saying that sorting normalized DNs by reverse length ensures that a DN is stored after any of its subordinate DNs.
I'll fix that and a few other comments and close this ITS, since you've clarified issue here in ITS#6076.