From kitten-bounces@ietf.org  Tue May 13 14:42:35 2008
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 BE6E23A6923;
	Tue, 13 May 2008 14:42:35 -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 3EFBA3A67B1;
	Tue, 13 May 2008 14:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.204
X-Spam-Level: 
X-Spam-Status: No, score=-17.204 tagged_above=-999 required=5
	tests=[AWL=-0.205, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
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 zOm5lZjd9-EJ; Tue, 13 May 2008 14:42:29 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id 181BA3A6877;
	Tue, 13 May 2008 14:41:58 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id DE7C912A879; Tue, 13 May 2008 14:38:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5179 on Generic Security Service Application Program Interface
	(GSS-API) Domain-Based Service Names Mapping for the Kerberos V
	GSS Mechanism
From: rfc-editor@rfc-editor.org
Message-Id: <20080513213839.DE7C912A879@bosco.isi.edu>
Date: Tue, 13 May 2008 14:38:39 -0700 (PDT)
Cc: kitten@ietf.org, rfc-editor@rfc-editor.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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: kitten-bounces@ietf.org
Errors-To: kitten-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5179

        Title:      Generic Security Service Application Program 
                    Interface (GSS-API) Domain-Based Service Names Mapping 
                    for the Kerberos V GSS Mechanism 
        Author:     N. Williams
        Status:     Standards Track
        Date:       May 2008
        Mailbox:    Nicolas.Williams@sun.com
        Pages:      5
        Characters: 8017
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5179.txt

This document describes the mapping of Generic Security Service
Application Program Interface (GSS-API) domain-name-based service
principal names onto Kerberos V principal names.  [STANDARDS TRACK]

This document is a product of the Kitten (GSS-API Next Generation) Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
Kitten mailing list
Kitten@ietf.org
https://www.ietf.org/mailman/listinfo/kitten


From kitten-bounces@ietf.org  Tue May 13 14:43:22 2008
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 2679A28B797;
	Tue, 13 May 2008 14:43:22 -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 7CFFD3A6853;
	Tue, 13 May 2008 14:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.192
X-Spam-Level: 
X-Spam-Status: No, score=-17.192 tagged_above=-999 required=5
	tests=[AWL=-0.193, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
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 ibWVgufvFXqd; Tue, 13 May 2008 14:43:17 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id F2E5E3A67E2;
	Tue, 13 May 2008 14:43:14 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 984B912A875; Tue, 13 May 2008 14:38:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5178 on Generic Security Service Application Program Interface
	(GSS-API) Internationalization and Domain-Based Service Names
	and Name Type
From: rfc-editor@rfc-editor.org
Message-Id: <20080513213835.984B912A875@bosco.isi.edu>
Date: Tue, 13 May 2008 14:38:35 -0700 (PDT)
Cc: kitten@ietf.org, rfc-editor@rfc-editor.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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: kitten-bounces@ietf.org
Errors-To: kitten-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5178

        Title:      Generic Security Service Application Program 
                    Interface (GSS-API) Internationalization and
                    Domain-Based Service 
                    Names and Name Type 
        Author:     N. Williams, A. Melnikov
        Status:     Standards Track
        Date:       May 2008
        Mailbox:    Nicolas.Williams@sun.com, 
                    Alexey.Melnikov@isode.com
        Pages:      9
        Characters: 17262
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-kitten-gssapi-domain-based-names-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5178.txt

This document describes domain-name-based service principal names and
the corresponding name type for the Generic Security Service
Application Programming Interface (GSS-API).  Internationalization of
the GSS-API is also covered.

Domain-based service names are similar to host-based service names,
but using a domain name (not necessarily an Internet domain name) in
addition to a hostname.  The primary purpose of domain-based names is
to provide a measure of protection to applications that utilize
insecure service discovery protocols.  This is achieved by providing
a way to name clustered services after the "domain" which they
service, thereby allowing their clients to authorize the service's
servers based on authentication of their service names.  
[STANDARDS TRACK]

This document is a product of the Kitten (GSS-API Next Generation) Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
Kitten mailing list
Kitten@ietf.org
https://www.ietf.org/mailman/listinfo/kitten


From kitten-bounces@ietf.org  Fri May 16 23:02:40 2008
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 D36CF3A69E9;
	Fri, 16 May 2008 23:02:40 -0700 (PDT)
X-Original-To: kitten@ietf.org
Delivered-To: kitten@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 65534)
	id 684773A69E9; Fri, 16 May 2008 23:02:38 -0700 (PDT)
X-Original-To: kitten@core3.amsl.com
Old-Delivered-To: kitten@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2944528C2B3
	for <kitten@core3.amsl.com>; Fri, 16 May 2008 17:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.764
X-Spam-Level: *
X-Spam-Status: No, score=1.764 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MISSING_SUBJECT=1.762]
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 DGKhVyHuTrMZ for <kitten@core3.amsl.com>;
	Fri, 16 May 2008 17:15:46 -0700 (PDT)
Received: from bay0-omc3-s17.bay0.hotmail.com (bay0-omc3-s17.bay0.hotmail.com
	[65.54.246.217])
	by core3.amsl.com (Postfix) with ESMTP id 73DC728C2BE
	for <kitten@ietf.org>; Fri, 16 May 2008 17:15:46 -0700 (PDT)
Received: from BAY107-W30 ([64.4.51.130]) by bay0-omc3-s17.bay0.hotmail.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 16 May 2008 17:15:38 -0700
Message-ID: <BAY107-W30939FBFB8CB865F629FABF4CB0@phx.gbl>
X-Originating-IP: [136.182.158.153]
From: Ken Li <ken_li76@hotmail.com>
To: <kitten@ietf.org>
Subject: 
Date: Fri, 16 May 2008 19:15:37 -0500
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 17 May 2008 00:15:38.0241 (UTC)
	FILETIME=[224AB710:01C8B7B3]
X-TMDA-Confirmed: Fri, 16 May 2008 23:02:38 -0700
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: multipart/mixed; boundary="===============0185024598=="
Sender: kitten-bounces@ietf.org
Errors-To: kitten-bounces@ietf.org

--===============0185024598==
Content-Type: multipart/alternative;
	boundary="_fe52957c-cc09-4c03-93f7-d0b607005981_"

--_fe52957c-cc09-4c03-93f7-d0b607005981_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


Hi,
=20
I just joined this mailing list, in hope of getting simple answers regardin=
g the current status of the next generation GSSAPI (v3). Is the work half c=
ompleted, three-quarters, etc.? When can one expect the "full" specificatio=
n to be out? I work for an IT organization that is waiting to upgrade to th=
e next generation GSSAPI.
=20
Thanks in advance,
=20
Ken
_________________________________________________________________
Make every e-mail and IM count. Join the i=92m Initiative from Microsoft.
http://im.live.com/Messenger/IM/Join/Default.aspx?source=3DEML_WL_ MakeCoun=
t=

--_fe52957c-cc09-4c03-93f7-d0b607005981_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class=3D'hmmessage'>
Hi,<BR>
&nbsp;<BR>
I just joined this mailing list, in hope of getting simple answers regardin=
g the current status of the next generation GSSAPI (v3). Is the work half c=
ompleted, three-quarters, etc.? When can one expect the "full" specificatio=
n to be out? I work for an IT organization that is waiting to upgrade to th=
e next generation GSSAPI.<BR>
&nbsp;<BR>
Thanks in advance,<BR>
&nbsp;<BR>
Ken<BR><br /><hr />Make every e-mail and IM count. <a href=3D'http://im.liv=
e.com/Messenger/IM/Join/Default.aspx?source=3DEML_WL_ MakeCount' target=3D'=
_new'>Join the i=92m Initiative from Microsoft.</a></body>
</html>=

--_fe52957c-cc09-4c03-93f7-d0b607005981_--

--===============0185024598==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kitten mailing list
Kitten@ietf.org
https://www.ietf.org/mailman/listinfo/kitten

--===============0185024598==--


From kitten-bounces@ietf.org  Sun May 18 22:14:35 2008
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 5F7D83A6AC6;
	Sun, 18 May 2008 22:14:35 -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 BE1BF3A69A6
	for <kitten@core3.amsl.com>; Sun, 18 May 2008 22:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.549
X-Spam-Level: *
X-Spam-Status: No, score=1.549 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_3=0.001]
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 1cYKDjXeleNu for <kitten@core3.amsl.com>;
	Sun, 18 May 2008 22:14:32 -0700 (PDT)
Received: from bay0-omc3-s31.bay0.hotmail.com (bay0-omc3-s31.bay0.hotmail.com
	[65.54.246.231])
	by core3.amsl.com (Postfix) with ESMTP id D5A393A6AC6
	for <kitten@ietf.org>; Sun, 18 May 2008 22:14:32 -0700 (PDT)
Received: from BAY107-W15 ([64.4.51.115]) by bay0-omc3-s31.bay0.hotmail.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Sun, 18 May 2008 22:14:33 -0700
Message-ID: <BAY107-W1502B1AC1A661B481C3402F4C50@phx.gbl>
X-Originating-IP: [68.58.70.142]
From: Ken Li <ken_li76@hotmail.com>
To: <kitten@ietf.org>
Subject: GSSAPIv3 status?
Date: Mon, 19 May 2008 00:14:33 -0500
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 19 May 2008 05:14:33.0792 (UTC)
	FILETIME=[398A1C00:01C8B96F]
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: multipart/mixed; boundary="===============0896608114=="
Sender: kitten-bounces@ietf.org
Errors-To: kitten-bounces@ietf.org

--===============0896608114==
Content-Type: multipart/alternative;
	boundary="_aeeb5e04-6918-4e06-81e8-5c165bc3221b_"

--_aeeb5e04-6918-4e06-81e8-5c165bc3221b_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable








Security scan upon download
  ATT00001 (0.1 KB)=20

Hi, I just joined this mailing list, in hope of getting simple answers rega=
rding the current status of the next generation GSSAPI (v3). Is the work ha=
lf completed, three-quarters, etc.? When can one expect the "full" specific=
ation to be out? I work for an IT organization that is waiting to upgrade t=
o the next generation GSSAPI. Thanks in advance, Ken
_________________________________________________________________
Give to a good cause with every e-mail. Join the i=92m Initiative from Micr=
osoft.
http://im.live.com/Messenger/IM/Join/Default.aspx?souce=3DEML_WL_ GoodCause=

--_aeeb5e04-6918-4e06-81e8-5c165bc3221b_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class=3D'hmmessage'>
<DIV class=3DAttachmentContainer>
<DIV class=3DAttachmentRow>
<DIV class=3DFloatRight>
<TABLE cellSpacing=3D0 cellPadding=3D0>
<TBODY>
<TR>
<TD class=3DSecondaryTextColor>Security scan upon download</TD>
<TD><A href=3D"http://www.trendmicro.com/" target=3D_blank><IMG height=3D19=
 alt=3D"Trend Micro =AE logo" src=3D"http://gfx2.hotmail.com/mail/w2/ltr/i_=
trend_small.gif" width=3D53> </A></TD></TR></TBODY></TABLE></DIV><IMG alt=
=3D"Attachments: " src=3D"http://gfx2.hotmail.com/mail/w2/ltr/i_attach.gif"=
> <SPAN class=3DNonThemedLinkContainer><A onclick=3D"" href=3D"http://by107=
w.bay107.mail.live.com/mail/ReadMessageLight.aspx?Action=3DScanAttachment&a=
mp;AllowUnsafeContentOverride=3DFalse&amp;AttachmentIndex=3D0&amp;Attachmen=
tDepth=3D0&amp;FolderID=3D00000000-0000-0000-0000-000000000001&amp;InboxSor=
tAscending=3DFalse&amp;InboxSortBy=3DDate&amp;IsMessageSafe=3DTrue&amp;Mess=
ageCodePage=3D1252&amp;ReadMessageId=3Dc7fa8494-5638-4612-aefc-85507e57816b=
&amp;n=3D1436312422">ATT00001 (0.1 KB)</A> </SPAN></DIV></DIV>
<DIV class=3D"ReadMsgBody BorderTop">
<DIV class=3DExternalClass id=3DMsgContainer>Hi,<BR>&nbsp;<BR>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, thr=
ee-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 genera=
tion GSSAPI.<BR>&nbsp;<BR>Thanks in advance,<BR>&nbsp;<BR>Ken<BR></DIV></DI=
V><br /><hr />Give to a good cause with every e-mail. <a href=3D'http://im.=
live.com/Messenger/IM/Join/Default.aspx?souce=3DEML_WL_ GoodCause' target=
=3D'_new'>Join the i=92m Initiative from Microsoft.</a></body>
</html>=

--_aeeb5e04-6918-4e06-81e8-5c165bc3221b_--

--===============0896608114==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kitten mailing list
Kitten@ietf.org
https://www.ietf.org/mailman/listinfo/kitten

--===============0896608114==--


From kitten-bounces@ietf.org  Sun May 18 22:22:55 2008
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


From kitten-bounces@ietf.org  Mon May 19 07:37:20 2008
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 111FE3A6ABE;
	Mon, 19 May 2008 07:37:20 -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 C02E53A6ABE
	for <kitten@core3.amsl.com>; Mon, 19 May 2008 07:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.557
X-Spam-Level: 
X-Spam-Status: No, score=-1.557 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11, 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 aBKGyXbR8v9w for <kitten@core3.amsl.com>;
	Mon, 19 May 2008 07:37:18 -0700 (PDT)
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
	by core3.amsl.com (Postfix) with ESMTP id 01E7F28C1A1
	for <kitten@ietf.org>; Mon, 19 May 2008 07:37:17 -0700 (PDT)
Received: from dm-central-02.central.sun.com ([129.147.62.5])
	by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	m4JEbIVL001926 for <kitten@ietf.org>; Mon, 19 May 2008 14:37:18 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104])
	by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,
	v2.2) with ESMTP id m4JEbIkx050221
	for <kitten@ietf.org>; Mon, 19 May 2008 08:37:18 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id
	m4JEbIh7001625; Mon, 19 May 2008 09:37:18 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m4JEbHJb001624; 
	Mon, 19 May 2008 09:37:17 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to
	Nicolas.Williams@sun.com using -f
Date: Mon, 19 May 2008 09:37:17 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Shawn M Emery <Shawn.Emery@sun.com>
Subject: Re: GSS-APIv3 status?
Message-ID: <20080519143717.GC26388@Sun.COM>
Mail-Followup-To: Shawn M Emery <Shawn.Emery@Sun.COM>,
	Ken Li <ken_li76@hotmail.com>, kitten@ietf.org
References: <BAY107-W30939FBFB8CB865F629FABF4CB0@phx.gbl>
	<48310EF6.2030400@sun.com>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <48310EF6.2030400@sun.com>
User-Agent: Mutt/1.5.7i
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

On Sun, May 18, 2008 at 11:24:06PM -0600, Shawn M Emery wrote:
> 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.

Interesting.  I didn't know anyone was waiting for this work.

What operating systems do you run?  What particular features are you
interested in?  You may want to speak to your OS vendors/communities.

> There are a number of work items that are at various stages:
> 
> Recently published RFCs:
> RFC 5178
> RFC 5179

That's domain-based naming.

> [...]

Nico
-- 
_______________________________________________
Kitten mailing list
Kitten@ietf.org
https://www.ietf.org/mailman/listinfo/kitten


