CSIV2 — Format of GSSUP GSS exported name object undefined

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

Format of GSSUP GSS mechanism-independent exported name object, a
special form of "flat" name as described below, is not defined.

Description:

>From RFC 2473 section 1.1.5 Naming

> Different classes of name representations are used in conjunction
> with different GSS-API parameters:
>
> - Internal form (denoted in this document by INTERNAL NAME),
> opaque to callers and defined by individual GSS-API
> implementations. GSS-API implementations supporting multiple
> namespace types must maintain internal tags to disambiguate the
> interpretation of particular names. A Mechanism Name (MN) is a
> special case of INTERNAL NAME, guaranteed to contain elements
> corresponding to one and only one mechanism; calls which are
> guaranteed to emit MNs or which require MNs as input are so
> identified within this specification.
>
> - Contiguous string ("flat") form (denoted in this document by
> OCTET STRING); accompanied by OID tags identifying the namespace
> to which they correspond. Depending on tag value, flat names may
> or may not be printable strings for direct acceptance from and
> presentation to users. Tagging of flat names allows GSS-API
> callers and underlying GSS-API mechanisms to disambiguate name
> types and to determine whether an associated name's type is one
> which they are capable of processing, avoiding aliasing problems
> which could result from misinterpreting a name of one type as a
> name of another type.
>
> - The GSS-API Exported Name Object, a special case of flat name
> designated by a reserved OID value, carries a canonicalized form
> of a name suitable for binary comparisons.

No Data Available