Subject: Re: updated MIC computation example text

From: Luke Howard <[email-masked]>
Date: Wed, 8 Dec 2004 11:48:35 +1100

>A.3  MechListMIC Computation Example
>    The following is an example to illustrate how the MechListMIC field
>    would be computed.
>
>    The NegTokenInit sequence is constructed as follows:

Just so we're clear that this is an example, perhaps you could add
something like:

In this example, the mechTypes field contains a single OID,
{ 1 2 840 113554 1 2 2 }. The NegTokenInit sequence is constructed
as follows:

>    If a mechlistMIC needs to be generated (according to the rules in
>    section 5), it is computed by using the DER encoding of the type
>    MechTypeList field from the initiator's NegTokenInit token as input
>    to the gss_GetMIC function.  In this case, the MIC would be computed
>    over the following bytes:
>
>       Contents of constructed [0] + contents of SEQUENCE:
>       30 nn 06 09 2A 86 48 86 F7 12 01 02 02 ...

Something like "Contents of field mechTypes" would make more sense to me
given that the [0] type and length octets are not included. But perhaps 
this is just me.

-- Luke

--

_______________________________________________
Kitten mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/kitten