On 19/04/2011, at 6:32 PM, Cantor, Scott E. wrote:
> On 4/19/11 12:25 PM, "Luke Howard" <[log in to unmask]> wrote:
>> What about what I mentioned yesterday, i.e. allowing composite names to
>> be imported with GSS_C_NT_EXPORT_NAME? (Sam is best positioned to answer
>> this.)
>
> Yeah, I didn't respond because I didn't understand the suggestion. You're
> saying that the mechanism would just be able to internally recognize that
> its exported name format was a composite? That doesn't seem irrational to
> me...
Indicating that the exported name is a composite name both in its encoding and in the associated name type is somewhat redundant. Redundancy may be irrational. :-)
Regardless, that is what the spec says: tokens MUST start with a two-octet token ID, hex 04 02... and the OID is GSS_C_NT_COMPOSITE_EXPORT (TBD).
-- Luke
|