Jim, RFC 4121 tokens are for message protection services only. (at least fast reauth notwithstanding)
OID awaits assignment, we use one in PADL's arc now. Luke Sent from my iPhone On 09/10/2011, at 12:44, "Jim Schaad" <[email protected]> wrote: > Sam, > > I am trying to construct the first token to be returned from the call to > GSS_Init_sec_context and I am having a couple of problems. > > 1. I don't know the value of the OID as it is not in the document (minor I > can always fudge this value) > > 2. Next item in the field is a token ID (note that this is capitalized as > iD in the current draft which is probably a typo). This should contain > either the value of <06 01> according to section 5 of this document. > However it would be <00 01> if it was using the tokens defined in RFC 4121. > It is not clear to me if you are re-using the same values from section 4.1 > in that document or defining new values in which case this needs to be > reflected in section 8.1 of this document. > > 3. Next item in the field is an inner token type - this is a 32-bit number > -- oh wait, I just figured this out. It would be clearer if you used the > following terms: > First subtoken type > First subtoken length > First subtoken body > Second subtoken type. > > I would be happy if you were consistent on the use of either inner token or > subtoken but mixing them got me confused. > > Jim > > > _______________________________________________ > abfab mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/abfab _______________________________________________ abfab mailing list [email protected] https://www.ietf.org/mailman/listinfo/abfab
