IETF Logo Mail Archive

Re: [sasl] SASL and KITTEN-WG Merger

Tony Hansen <tony@att.com> Tue, 11 May 2010 20:29 UTC

Return-Path: <tony@att.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 E821D3A67B5; Tue, 11 May 2010 13:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 55dX-XL-HU4i; Tue, 11 May 2010 13:29:57 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id 9D71F3A69E4; Tue, 11 May 2010 13:28:11 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-9.tower-120.messagelabs.com!1273609679!55845038!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 21369 invoked from network); 11 May 2010 20:28:00 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-9.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 May 2010 20:28:00 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o4BKSC2h027972; Tue, 11 May 2010 16:28:12 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o4BKSBVQ027950; Tue, 11 May 2010 16:28:11 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.3/8.14.3) with ESMTP id o4BKRvaC009722; Tue, 11 May 2010 16:27:57 -0400
Received: from maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.3/8.14.3) with ESMTP id o4BKRrZK009609; Tue, 11 May 2010 16:27:53 -0400
Received: from [135.25.190.148] (njcdtl02ga7127.ugd.att.com[135.25.190.148]) by maillennium.att.com (mailgw1) with ESMTP id <20100511202751gw100b8ilqe> (Authid: tony); Tue, 11 May 2010 20:27:53 +0000
X-Originating-IP: [135.25.190.148]
Message-ID: <4BE9BDC6.7070303@att.com>
Date: Tue, 11 May 2010 16:27:50 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: [sasl] SASL and KITTEN-WG Merger
References: <4BE1E547.5030103@oracle.com> <4BE5518B.7060101@cisco.com> <87ljbtumzm.fsf@mocca.josefsson.org> <20100510145648.GO9429@oracle.com> <11586_1273508712_o4AGPBeI021842_4BE82041.9070507@cisco.com> <176E8F86825AF9BE457A43D2@minbar.fac.cs.cmu.edu>
In-Reply-To: <176E8F86825AF9BE457A43D2@minbar.fac.cs.cmu.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 11 May 2010 13:38:27 -0700
Cc: kitten@ietf.org, Simon Josefsson <simon@josefsson.org>, sasl@ietf.org, Eliot Lear <lear@cisco.com>
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: Tue, 11 May 2010 20:29:59 -0000

what's a good retronym for KABOODLE?

On 5/11/2010 2:12 PM, Jeffrey Hutzelman wrote:
> --On Monday, May 10, 2010 05:03:29 PM +0200 Eliot Lear 
> <lear@cisco.com> wrote:
>
> Also, I'll just point out that this is our
>> opportunity for a new SASSY WG name (KITTEN-KABOODLE?) ;-)
>
> Absolutely not.  Working group acronyms containing dashes are a major 
> pain.
> :-)

v2.23.0 | Report a Bug | By Email