Re: [kitten] [IANA #748877] please review SASL-SCRAM-256
Tony Hansen <tony@att.com> Fri, 11 April 2014 02:59 UTC
Return-Path: <tony@att.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 580091A001D for <kitten@ietfa.amsl.com>; Thu, 10 Apr 2014 19:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.871
X-Spam-Level:
X-Spam-Status: No, score=-2.871 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TxMDplsvU0hV for <kitten@ietfa.amsl.com>; Thu, 10 Apr 2014 19:59:27 -0700 (PDT)
Received: from egssmtp03.att.com (egssmtp03.att.com [144.160.128.152]) by ietfa.amsl.com (Postfix) with ESMTP id A13371A0020 for <kitten@ietf.org>; Thu, 10 Apr 2014 19:59:26 -0700 (PDT)
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by egssmtp03.att.com ( egs 8.14.5/8.14.5) with ESMTP id s3B2xJWd021388 for <kitten@ietf.org>; Thu, 10 Apr 2014 19:59:24 -0700
Received: from vpn-135-70-100-137.vpn.swst.att.com ([135.70.100.137]) by maillennium.att.com (mailgw1) with ESMTP id <20140411025918gw100j0choe>; Fri, 11 Apr 2014 02:59:18 +0000
X-Originating-IP: [135.70.100.137]
Message-ID: <53475A88.3060202@att.com>
Date: Thu, 10 Apr 2014 22:59:20 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: kitten@ietf.org
References: <RT-Ticket-748877@icann.org> <5319DE8B.1030202@att.com> <rt-4.0.8-12541-1394569374-953.748877-9-0@icann.org> <20140312162849.152e924b@latte.josefsson.org> <20140411001759.3d89cfb5@latte.josefsson.org> <CAKHUCzxxbABfJDR8JZ5evHXFHmsBvqVdHTX0QLg4ONsqNKgk5g@mail.gmail.com>
In-Reply-To: <CAKHUCzxxbABfJDR8JZ5evHXFHmsBvqVdHTX0QLg4ONsqNKgk5g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030607050304010800050405"
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/dx1tAHnCi4uPoG4ySvdEyvvkI9M
Subject: Re: [kitten] [IANA #748877] please review SASL-SCRAM-256
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 11 Apr 2014 02:59:35 -0000
On 4/10/14, 7:10 PM, Dave Cridland wrote: > On 10 April 2014 23:17, Simon Josefsson <simon@josefsson.org > <mailto:simon@josefsson.org>> wrote: > > I haven't seen anyone disagree with my interpretation that the > registration policy for new SCRAM-* mechanisms are "IETF Review", > which > requires an RFC. Therefor, I will suggest to IANA that they turn down > the registration request until that has been fulfilled. > > > > Yes, they're IETF Review. > > Although RFC 5802 is generally hash agnostic, a handful of parts of > SCRAM are defined specific to SCRAM-SHA-1[-PLUS], including the > minimum iteration count for example, so an RFC might prove useful anyway. OK, I figured it was worth trying to do it this way. I'll start the RFC process. Dave, a question for you: What do you think a better minimum iteration count should be for SCRAM-SHA-256? Why should it be any different than the value specified for SCRAM-SHA-1 (4096)? One of the items in 5802 that is out of date is the email address to send registrations to, as it specifies sasl@ietf.org which no longer exists. So I think an update to that part of 5802 is needed to point to the kitten list. Thoughts? Are there any other updates needed for 5802? Another question: should an RFC for SCRAM-SHA-256[-PLUS] register any other SCRAM mechanism? Tony Hansen
- Re: [kitten] [IANA #748877] please review SASL-SC… Russ Allbery
- Re: [kitten] [IANA #748877] please review SASL-SC… Tony Hansen
- Re: [kitten] [IANA #748877] please review SASL-SC… Simon Josefsson
- Re: [kitten] [IANA #748877] please review SASL-SC… Simon Josefsson
- Re: [kitten] [IANA #748877] please review SASL-SC… Shawn M Emery
- Re: [kitten] [IANA #748877] please review SASL-SC… Simon Josefsson
- Re: [kitten] [IANA #748877] please review SASL-SC… Simon Josefsson
- Re: [kitten] [IANA #748877] please review SASL-SC… Dave Cridland
- Re: [kitten] [IANA #748877] please review SASL-SC… Tony Hansen
- Re: [kitten] [IANA #748877] please review SASL-SC… Dave Cridland