CSIV2 — inconsistent definition of target_name field

Document: orbos/2000-08-04 CSIv2 Final Submission
Issue:

target_name(s) field of struct AS_ContextSec is defined and described
inconsistently in various places in the submission.

Description:

In section 6.1.4.1 this field is defined as

sequence <Security::GSS_NT_exportedName> target_names;

and defined as a list of target names.

In the IDL in section B.7 this field is defined as

sequence <Security::GSS_NT_exportedName> target_name;

There are other places in the document where the singular form of this
field name is used, including in the examples of the scenarios chapter.

Proposed Solution:

The change of this field to a list was not necessary, as it is difficult
to make a case for requiring multiple target names within a single
mechanism (as there is a multiple mechanism workaround).

We should at least fix the inconsitencies in the document. If we keep
the
ability to express multiple targets, then we should also say something
about the semantics of position in the list.

The prefered solution would be to revert back to the singular form.

Security::GSS_NT_exportedName target_name;

and fix all references to this field accordingly.

Make it singular. Close issue with revised text.