Re: SASL and KITTEN-WG Merger

Nicolas Williams <Nicolas.Williams@oracle.com> Thu, 06 May 2010 16:48 UTC

Return-Path: <Nicolas.Williams@oracle.com>
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 93B3E3A6917; Thu, 6 May 2010 09:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level:
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[AWL=-0.862, BAYES_20=-0.74, UNPARSEABLE_RELAY=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 G1qhuRxosFUl; Thu, 6 May 2010 09:48:04 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id AF6223A6921; Thu, 6 May 2010 09:48:04 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o46GlnrI010610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 May 2010 16:47:51 GMT
Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o465rq7P013811; Thu, 6 May 2010 16:47:47 GMT
Received: from abhmt013.oracle.com by acsmt355.oracle.com with ESMTP id 220127231273164393; Thu, 06 May 2010 09:46:33 -0700
Received: from oracle.com (/129.153.128.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 06 May 2010 09:46:33 -0700
Date: Thu, 6 May 2010 11:46:31 -0500
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: Shawn Emery <shawn.emery@oracle.com>
Subject: Re: SASL and KITTEN-WG Merger
Message-ID: <20100506164630.GU9429@oracle.com>
References: <4BE1E547.5030103@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BE1E547.5030103@oracle.com>
User-Agent: Mutt/1.5.20 (2010-03-02)
X-Auth-Type: Internal IP
X-Source-IP: acsinet15.oracle.com [141.146.126.227]
X-CT-RefId: str=0001.0A090204.4BE2F2B7.0172:SCFMA922111,ss=1,fgs=0
Cc: kitten@ietf.org, sasl@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/mail-archive/web/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>
X-List-Received-Date: Thu, 06 May 2010 16:48:05 -0000

On Wed, May 05, 2010 at 03:38:15PM -0600, Shawn Emery wrote:
> Sorry for any cross-posting, but this is unavoidable given the subject line.

:)

> During IETF 77, the security ADs suggested that we merge the KITTEN
> and SASL WGs.  This has some potential benefits:
> 
> 1. ensure efforts of any new work items/extensions
> 2. both WGs have expertise in security interface design
> 3. analyze proposed security mechanisms for both set of interfaces

Note that KITTEN never had mechanism standardization as a
responsibility.  Now its successor will?  This means that the new WG's
charter can't just be a union of the KITTEN and SASL charters.

> Please respond to both lists if you have any objections to such a
> merger.  The time-out for objections is two weeks from this posting.

No objections here.

I would like to see the proposed charter, of course.

I'm also curious as to the name of the new WG.  I'd be fine with keeping
either of KITTEN or SASL as the name for the new WG.  I'd also be happy
with a new name.

Nico
--