NAM — Unclear requirements for support of textual object keys

The core changes introduced by the adoption of the INS specification
have provided the means for a client to fabricate an object reference
with a key containing arbitrary octets, and designating any server
address.

This is the first time that an OMG specification has violated the rule
that object keys are opaque, formatted at the discretion of the server
orb. This rule is violated because, at a minimum, the changes seem to
require that a key containing the characters "NameService" must be a
valid key in some server in order to support the INS specification.

It seems that CORBA is now requiring that a conforming orb must natively
support at least some range of text-like keys, either in all servers or
in at least one specially constructed server.

If this is indeed a requirement, then there is a need to spell out
clearly the extent of this requirement:

The INS specification is not specifying server side behavior.