Re: Determining a token's mechanism

Marc Horowitz <marc@cam.ov.com> Tue, 25 April 1995 15:20 UTC

Message-Id: <199504251445.KAA26226@dun-dun-noodles.cam.ov.com>
To: John Linn <linn@cam.ov.com>
Cc: cat-ietf@mit.edu
Subject: Re: Determining a token's mechanism
In-Reply-To: Your message of "Tue, 25 Apr 1995 08:43:02 EDT." <199504251243.IAA07352@winkl.cam.ov.com>
Date: Tue, 25 Apr 1995 10:45:38 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Marc Horowitz <marc@cam.ov.com>

In message <199504251243.IAA07352@winkl.cam.ov.com>, John Linn <linn@cam.ov.com> writes:

>> The following replies were received on this point:
>> 
>> Marc Horowitz, 7 April:
>> 
>> >The gss_parse_token() routine would be easy to implement, and it would
>> >do the right thing for all krb5 tokens.

For the record, I was replying to John's question of April 7, which
was:

    (2) Referring to the SPKM_Parse_token() routine as described in
    draft-ietf-cat-spkmgss-02.txt, we would like to consider the
    feasibility of incorporating an equivalent routine within GSS-V2.
    Question to implementors: please review the definition of this routine
    and consider whether its functionality is implementable within your
    mechanism and code base.

My answer to this technical question is still the same, I believe.
However, and this was not part of my original response, I don't
believe that SPKM_Parse_token() is a useful function in light of its
inherent nonportability, and I'd rather not see it included in the
spec.

		Marc

Re: Determining a token's mechanism Dennis Glatting
Re: Determining a token's mechanism Marc Horowitz
Re: Determining a token's mechanism John Linn
Re: Determining a token's mechanism Dennis Glatting
Determining a token's mechanism John Linn
Re: Determining a token's mechanism Doug Rosenthal
Re: Determining a token's mechanism Dan Nessett