HM> Second, two entirely different namespaces may be completely
HM> separate to the extent they have NO zones NAMES in common
HM> except "." for root. -- there is no shadow zone because the
HM> owner of the private namespace does not provide a subset of
HM> any common zones to the other namespace.
HM>
HM> root separte root (separate namespace)
HM> / \ / \
HM> com net local herb
HM> [...]
HM> A private namespace requires a forwarder to resolve names
HM> from another (e.g., THE Public Internet) namespace.

Wrong. In the above scenario there is in fact _one_ namespace seen by
entities within the company, and it looks like this: