[17248] in Kerberos_V5_Development
Re: GSS memory allocation initial cut for review
daemon@ATHENA.MIT.EDU (Nico Williams)
Wed Oct 5 00:22:13 2011
MIME-Version: 1.0
In-Reply-To: <CAK3OfOgxX-2x23+hAjX4ygQ=DSoPZ-aJb4b6YxDE8MouQWvVnA@mail.gmail.com>
Date: Tue, 4 Oct 2011 23:22:07 -0500
Message-ID: <CAK3OfOgb8HHN__pWJstefm9vmWGzMe-KZPFsNrMky5crqn3caw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Sam Hartman <hartmans@painless-security.com>
Cc: kevin.wasserman@painless-security.com, krbdev@mit.edu
Content-Type: text/plain; charset="utf-8"
Errors-To: krbdev-bounces@mit.edu
Content-Transfer-Encoding: 8bit
On Mon, Oct 3, 2011 at 1:54 PM, Nico Williams <nico@cryptonector.com> wrote:> At first glance I'm tempted to conclude that the problem is that one> mechglue cannot impose these sorts of requirements on other mechglues.> It seems like a matter of principle.
I should say: it is a matter of principle. I suppose that we couldreach agreement on a proposal like yours modified as I proposed.However, I do believe that Jeff is right to suggest that the correctforum for this is KITTEN WG (not necessarily that we should publishRFC, and certainly not as a prerequisite, but, rather, that we shouldreach consensus there).
If there's a simple resolution to the *technical* issues with yourproposal (I do think there is, though I'd like to hear from theWindows experts among us and at KITTEN), I suspect that the variousGSS C bindings implementors could quickly reach agreement on it. Isuggest, if you're in a hurry, that post on kitten@ietf.org soonerrather than later.
Nico--
_______________________________________________krbdev mailing list krbdev@mit.eduhttps://mailman.mit.edu/mailman/listinfo/krbdev
