GSS-API misalignment

"John Linn. LKG1-2/A19. {" (508)"-486 or DTN 226}-7384. 02-Oct-1992 1534" <linn@albeit.enet.dec.com> Fri, 02 October 1992 19:42 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa09060; 2 Oct 92 15:42 EDT
Received: from NRI.RESTON.VA.US by IETF.NRI.Reston.VA.US id aa09054; 2 Oct 92 15:42 EDT
Received: from BITSY.MIT.EDU by NRI.Reston.VA.US id aa17788; 2 Oct 92 15:47 EDT
Received: by bitsy.MIT.EDU id AA26494; Fri, 2 Oct 92 15:34:24 EDT
Received: from MIT.MIT.EDU by bitsy.MIT.EDU with SMTP id AA26488; Fri, 2 Oct 92 15:34:22 EDT
Received: from inet-gw-2.pa.dec.com by MIT.EDU with SMTP id AA01969; Fri, 2 Oct 92 15:34:16 EDT
Received: by inet-gw-2.pa.dec.com; id AA10467; Fri, 2 Oct 92 12:34:09 -0700
Received: by us1rmc.bb.dec.com; id AA00137; Fri, 2 Oct 92 15:31:34 -0400
Message-Id: <9210021931.AA00137@us1rmc.bb.dec.com>
Received: from albeit.enet; by us1rmc.enet; Fri, 2 Oct 92 15:31:36 EDT
Date: Fri, 02 Oct 1992 15:31:36 -0400
Sender: ietf-archive-request@IETF.NRI.Reston.VA.US
From: "John Linn. LKG1-2/A19. { -486 or DTN 226}-7384. 02-Oct-1992 1534" <linn@albeit.enet.dec.com>
To: cat-ietf@mit.edu
Cc: linn@albeit.enet.dec.com
Apparently-To: cat-ietf@mit.edu
Subject: GSS-API misalignment

There's a small misalignment between draft-ietf-cat-genericsec-02 and
draft-ietf-cat-secservice-01.  The latter (bindings) spec's definition
for GSS_Acquire_cred() includes an actual_mechs output parameter,
indicating the set of mechanisms for which the received credentials may
be used, but the former (high-level) spec includes no such return value,
implicitly making it necessary to call GSS_Inquire_cred() to determine
this information.  I think that it's a good idea for GSS_Acquire_cred()
to return the mechanism set data directly, and propose to treat its
omission from the high-level spec as an erratum to be fixed when the
spec is next updated, but not to issue a new Internet-Draft at this time
in order to rectify this single point.  Does anyone object to this
proposal?

--jl