On Tue, Oct 18, 2011 at 9:50 AM, Sam Hartman <[email protected]> wrote: >>>>>> "Jim" == Jim Schaad <[email protected]> writes: > Jim> 3. Next item in the field is an inner token type - this is a > Jim> 32-bit number -- oh wait, I just figured this out. It would be > Jim> clearer if you used the following terms: First subtoken type > Jim> First subtoken length First subtoken body Second subtoken type. > > Jim> I would be happy if you were consistent on the use of either > Jim> inner token or subtoken but mixing them got me confused. > > OK, I'm trying to be consistent with the following. An inner token is a > non-ASN.1 structure carried in the any in the GSSAPI-Token production > defined in RFC 2743. I.E. the context token without the application tag > and OID wrapper.
Well, it could be ASN.1, but the point is it's not defined by RFC2743 -- it's defined by the mechanism. > GSS-EAP inner tokens contain a token ID and a series of subtokens. > Subtokens have types, lengths and values. I believe I've made changes > to the document to be consistent with this terminology. Given that the context token exchange is synchronous, there's no need for any token IDs as such. Or so I would think (sub-token IDs, sure, if there's any sub-tokens that require identification). Nico -- _______________________________________________ abfab mailing list [email protected] https://www.ietf.org/mailman/listinfo/abfab
