9. Use the global name space
Some people, for instance when using Novell 4 servers, have decided that they will use X.500 or X.500-like services as an internal naming mechanism, without coordinating with an outside source.
This suffers from many of the same problems as private IP addresses, only more so: your data may need significant restructuring once you decide to expose them to the outer world.
A globally accessible X.500 service requires a globally connected X.500 name space. See [3] and [4] for recommendations on how create a local part of the global name space.
Though the standard is not very clear about this and the most recent version (93) appears not to support it, in practice the X.500 name space is only manageable if there is a single root context operated under a cooperative agreement. However, one can be sure that there will be turf battles over it's control.
If those turf battles aren't decided outside the actual running service, the effect on the service quality will be ruinous.
This document appeals to all players in the field to let existing practice alone until a better system is agreed and is ready to go into place; at the moment, the root context of the day is operated by the Dante NameFLOW-Paradise service.
More information on the Dante NameFLOW-Paradise service is found at the URL