IETF Logo Mail Archive

Re: [sasl] MOGGIES Proposed Charter

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 19 May 2010 09:01 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: sasl@core3.amsl.com
Delivered-To: sasl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 480EE3A687C; Wed, 19 May 2010 02:01:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.21
X-Spam-Level:
X-Spam-Status: No, score=-2.21 tagged_above=-999 required=5 tests=[AWL=0.389, BAYES_00=-2.599]
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 D8rWJ0CNvxo2; Wed, 19 May 2010 02:01:23 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id BB1A53A6829; Wed, 19 May 2010 02:01:20 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <S=Oo2ABeGUuh@rufus.isode.com>; Wed, 19 May 2010 10:01:12 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4BF3A8D5.8070905@isode.com>
Date: Wed, 19 May 2010 10:01:09 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Jeffrey Hutzelman <jhutz@cmu.edu>
References: <4BF221C1.2090005@oracle.com> <22122_1274210205_o4IJGi7g000698_20100518191521.GL9429@oracle.com> <0653C22222CBEBDD0AD1CCFA@minbar.fac.cs.cmu.edu>
In-Reply-To: <0653C22222CBEBDD0AD1CCFA@minbar.fac.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: kitten@ietf.org, Tim Polk <tim.polk@nist.gov>, sasl@ietf.org
Subject: Re: [sasl] MOGGIES Proposed Charter
X-BeenThere: sasl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SASL Working Group <sasl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sasl>, <mailto:sasl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sasl>
List-Post: <mailto:sasl@ietf.org>
List-Help: <mailto:sasl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sasl>, <mailto:sasl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 09:01:24 -0000

Jeffrey Hutzelman wrote:

> --On Tuesday, May 18, 2010 02:15:22 PM -0500 Nicolas Williams 
> <Nicolas.Williams@oracle.com> wrote:
>
>> On Mon, May 17, 2010 at 11:12:33PM -0600, Shawn Emery wrote:
>
 [...]

>>> This working group will review SASL related submissions as well,
>>> including any new SASL mechanisms proposed.
>>
>> New SASL mechanisms?  Why not new GSS-API mechanisms?  Why not close the
>> WG (and even SASL) to new non-GS2 mechanisms?  Might there be conflicts
>> with EMU?
>
> This WG should review proposals for new SASL and GSS-API mechanisms, 
> and such work should be considered to fall within its general scope, 
> but it should be constrained to actually work only on mechanisms 
> specifically listed in the charter.  If we want to work on a new 
> mechanism, we can amend the charter.

+1.

> It should also be willing to provide advice and review on 
> non-mechanism proposals such as defining use of SASL or GSS-API in a 
> new or existing protocol.  However, actual work on such proposals 
> should be done in the relevant WG for the protocol in question, and 
> _not_ in the new one.

I think I was quite clear on this in my reply, but in case I wasn't: +1.

v2.23.0 | Report a Bug | By Email