1994-08-09 - Re: Problem in draft FIPS `CRYPTOGRAPHIC SERVICE CALLS’

Header Data

From: “Perry E. Metzger” <perry@imsi.com>
To: p.v.mcmahon.rea0803@oasis.icl.co.uk
Message Hash: a10bf6a3cda22eabba8b827610757b718d6c1301ddfc95b33097a9af9b50ca87
Message ID: <9408091701.AA23510@snark.imsi.com>
Reply To: <9408091650.AA17029@getafix.oasis.icl.co.uk>
UTC Datetime: 1994-08-09 17:02:17 UTC
Raw Date: Tue, 9 Aug 94 10:02:17 PDT

Raw message

From: "Perry E. Metzger" <perry@imsi.com>
Date: Tue, 9 Aug 94 10:02:17 PDT
To: p.v.mcmahon.rea0803@oasis.icl.co.uk
Subject: Re: Problem in draft FIPS `CRYPTOGRAPHIC SERVICE CALLS'
In-Reply-To: <9408091650.AA17029@getafix.oasis.icl.co.uk>
Message-ID: <9408091701.AA23510@snark.imsi.com>
MIME-Version: 1.0
Content-Type: text/plain



p.v.mcmahon.rea0803@oasis.icl.co.uk says:
> My interest in this is that I am chair of the X/Open security working group
> defining a industry consensus specification for which the draft FIPS is one
> of the inputs, along with other inputs from RSADSI (via Sun), IBM, HP,
> Olivetti, SESAME etc. 

Have you been following the IETF's GSS-API work?

.pm





Thread