Re:
Shawn M Emery <Shawn.Emery@Sun.COM> Mon, 19 May 2008 05:22 UTC
Return-Path: <kitten-bounces@ietf.org>
X-Original-To: kitten-archive@megatron.ietf.org
Delivered-To: ietfarch-kitten-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3D823A6A55; Sun, 18 May 2008 22:22:54 -0700 (PDT)
X-Original-To: kitten@core3.amsl.com
Delivered-To: kitten@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 822EB3A6A55 for <kitten@core3.amsl.com>; Sun, 18 May 2008 22:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.632
X-Spam-Level:
X-Spam-Status: No, score=-0.632 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eWYc8QTQ-wUf for <kitten@core3.amsl.com>; Sun, 18 May 2008 22:22:52 -0700 (PDT)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by core3.amsl.com (Postfix) with ESMTP id A79813A6839 for <kitten@ietf.org>; Sun, 18 May 2008 22:22:52 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4J5Mq2N018210 for <kitten@ietf.org>; Mon, 19 May 2008 05:22:52 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K1300M01O5T2E00@mail-amer.sun.com> (original mail from Shawn.Emery@Sun.COM) for kitten@ietf.org; Sun, 18 May 2008 23:22:52 -0600 (MDT)
Received: from [10.0.0.5] ([206.124.7.73]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K13004L7OA2M870@mail-amer.sun.com>; Sun, 18 May 2008 23:22:51 -0600 (MDT)
Date: Sun, 18 May 2008 23:24:06 -0600
From: Shawn M Emery <Shawn.Emery@Sun.COM>
Subject: Re:
In-reply-to: <BAY107-W30939FBFB8CB865F629FABF4CB0@phx.gbl>
To: Ken Li <ken_li76@hotmail.com>
Message-id: <48310EF6.2030400@sun.com>
MIME-version: 1.0
References: <BAY107-W30939FBFB8CB865F629FABF4CB0@phx.gbl>
User-Agent: Thunderbird 2.0.0.12 (X11/20080228)
Cc: kitten@ietf.org
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: kitten-bounces@ietf.org
Errors-To: kitten-bounces@ietf.org
Ken Li wrote: > Hi, > > I just joined this mailing list, in hope of getting simple answers > regarding the current status of the next generation GSSAPI (v3). Is > the work half completed, three-quarters, etc.? When can one expect the > "full" specification to be out? I work for an IT organization that is > waiting to upgrade to the next generation GSSAPI. There are a number of work items that are at various stages: Recently published RFCs: RFC 5178 RFC 5179 WGLC: draft-ietf-kitten-gssapi-channel-bindings Ready for WGLC: draft-ietf-kitten-rfc2853bis Work in progress: draft-ietf-kitten-extended-mech-inquiry draft-ietf-kitten-gssapi-extensions-iana draft-ietf-kitten-gssapi-store-cred What properties are you looking for in GSS? Shawn. Kitten wg co-chair -- _______________________________________________ Kitten mailing list Kitten@ietf.org https://www.ietf.org/mailman/listinfo/kitten
- Ken Li
- Re: Shawn M Emery
- Re: GSS-APIv3 status? Nicolas Williams