Status of draft-ietf-ipsec-isakmp-gss-auth-06.txt

Jason R Thorpe <thorpej@zembu.com> Sat, 27 January 2001 02:17 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id SAA26880; Fri, 26 Jan 2001 18:17:13 -0800 (PST)
Received: by lists.tislabs.com (8.9.1/8.9.1) id TAA17292 Fri, 26 Jan 2001 19:56:22 -0500 (EST)
Date: Fri, 26 Jan 2001 16:58:33 -0800
From: Jason R Thorpe <thorpej@zembu.com>
To: ipsec@lists.tislabs.com
Subject: Status of draft-ietf-ipsec-isakmp-gss-auth-06.txt
Message-ID: <20010126165833.M473@dr-evil.shagadelic.org>
Reply-To: thorpej@zembu.com
Mail-Followup-To: Jason R Thorpe <thorpej@zembu.com>, ipsec@lists.tislabs.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Organization: Zembu Labs, Inc.
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

What's the current status of the aforementioned draft (GSS-API
Authentication Method for IKE)?  I haven't seen any discussion
of it since IETF-49, and the draft itself hasn't changed since
July, 2000.

I ask because the draft is now basically expired, and as far as I
know, none of the temorarily-assigned constants in the draft were
set into stone with official assignments.

Yes, I know that there is now another proposed Kerberos-based IPsec
key exchange mechanism on the table, but there are now multiple
implementations of GSS-API for IKE out there (KAME, plus presumably
a Microsoft implementation for Windows 2000, at least), so it might
be nice for some forward movement on the draft to happen (make an
informational RFC out of it to document existing practice?).

-- 
        -- Jason R. Thorpe <thorpej@zembu.com>

Status of draft-ietf-ipsec-isakmp-gss-auth-06.txt Jason R Thorpe