## Equality test, SourceDN/DestDN

There are many condition tokens that can use equality tests of 7
different types.

Case Sensitive
Case Insensitive
Regular Expression
Numeric
Binary
Source Dn
Destination DN

The first 5 are sort of self explanatory. But the last two, Source DN
and Destination DN are less clear. The docs suggest they use DN
matching semantics.

Well that was less than helpful. (I suspect this is basically a request
to Shon, unless someone else knows...)

What does DN matching mean?

One simple example, using eDir syntax.

\TREE\O-name\OU-name\CN and O-name\OU-name\CN are the same (note the
you do not specify the tree name).

But is that included in this test?

How about implied case insensitivity? Is it really?

What else?

And how would this differ with the various defined DN types (as seen in

Source DN
Destination DN
dot
qualified dot
slash
qualified slash
LDAP
custom

(Custom is WAY cool, see
http://www.novell.com/communities/no...imiter-example

SourceDN/DestDN formats are technically specified by the shim, which
defines what its native DN format structure is. So they of course
depend on the channel, the direction, and the driver. But they should
be one of the other formats.