This figure shows a partitioned directory. Server A holds a tree with <font face="Courier New, Courier, mono">dc=com</font> 
at the root, <font face="Courier New, Courier, mono">dc=acme</font> as the root 
of a subtree that includes <font face="Courier New, Courier, mono">c=us</font>, 
<font face="Courier New, Courier, mono">c=uk</font>, and <font face="Courier New, Courier, mono">c=au</font>. 
Server B likewise holds a tree with <font face="Courier New, Courier, mono">dc=com</font> 
at the root, <font face="Courier New, Courier, mono">dc=acme</font> as the root 
of a subtree that includes <font face="Courier New, Courier, mono">c=us</font>, 
<font face="Courier New, Courier, mono">c=uk</font>, and <font face="Courier New, Courier, mono">c=au</font>. 
However, on Server B, only <font face="Courier New, Courier, mono">c=au</font> 
is a replicated naming context. Both <font face="Courier New, Courier, mono">c=us</font> 
and <font face="Courier New, Courier, mono">c=uk</font> are knowledge references 
pointing back to those naming contexts on Server A.