Re: [sasl] Mechanism Negotiation and Channel Binding with SCRAM

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 02 March 2010 12:28 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 CD5643A8676 for <sasl@core3.amsl.com>; Tue, 2 Mar 2010 04:28:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 MBh+82hnFoWU for <sasl@core3.amsl.com>; Tue, 2 Mar 2010 04:28:06 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id D3F5D3A8191 for <sasl@ietf.org>; Tue, 2 Mar 2010 04:28:05 -0800 (PST)
Received: from [172.16.2.121] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <S40EUwAu7gSM@rufus.isode.com>; Tue, 2 Mar 2010 12:28:05 +0000
Message-ID: <4B8D043E.6070804@isode.com>
Date: Tue, 02 Mar 2010 12:27:42 +0000
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: Simon Josefsson <simon@josefsson.org>
References: <18CD98AA-6737-41FF-B838-2F3C872F016B@googlemail.com> <87k4tww57r.fsf@mocca.josefsson.org> <20100301173017.GF1061@Sun.COM> <87k4tvk7ew.fsf@mocca.josefsson.org> <20100301224424.GN1061@Sun.COM> <87d3znr62u.fsf@mocca.josefsson.org> <20100301231900.GO1061@Sun.COM> <87fx4jng8y.fsf@mocca.josefsson.org>
In-Reply-To: <87fx4jng8y.fsf@mocca.josefsson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: sasl@ietf.org
Subject: Re: [sasl] Mechanism Negotiation and Channel Binding with SCRAM
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: Tue, 02 Mar 2010 12:28:06 -0000

Simon Josefsson wrote:

>Nicolas Williams <Nicolas.Williams@sun.com> writes:
>  
>
>>On Tue, Mar 02, 2010 at 12:10:49AM +0100, Simon Josefsson wrote:
>>    
>>
>>>Nicolas Williams <Nicolas.Williams@sun.com> writes:
>>>      
>>>
>>>>I see no real change.  I think we want to s/MUST select/selects/ to go
>>>>from normative to declarative language.
>>>>        
>>>>
>>>That seems simpler.
>>>      
>>>
>>>>[...]
>>>>        
>>>>
>>>Seems good to me, although it needs to be adapted to GS2 as well.
>>>
>>>The question remains if we want to make this change now or not.  Both
>>>SCRAM and GS2 needs to be updated.  Your proposed change wouldn't be the
>>>most minimal fix, but maybe clarity is better served by rewriting these
>>>paragraphs.
>>>      
>>>
>>Does anyone else have an opinion on this?  I'd be happy doing: a)
>>nothing, b) changing a couple of normative MUSTs into declaratives, c)
>>re-writing some of these as I proposed.
>>    
>>
>I kind of prefer b) and the main reason is to minimize the amount of
>changes we do at this late time.
>
>I believe that if we don't change this now, clients without channel
>binding support will violate the first MUST in practice.  This will
>likely cause problems when moving SCRAM from Proposed to Draft (if that
>happens...).
>
I can be easily confused by declarative language, so I would prefer c). 
But I can live with b).