Re: [http-auth] Barry Leiba's Yes on draft-ietf-httpauth-scram-auth-14: (with COMMENT)
Alexey Melnikov <alexey.melnikov@isode.com> Wed, 16 December 2015 14:48 UTC
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6EC71A001D; Wed, 16 Dec 2015 06:48:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 nA4lUtSOqH4Y; Wed, 16 Dec 2015 06:48:08 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 2ECB91A0031; Wed, 16 Dec 2015 06:47:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1450277277; d=isode.com; s=selector; i=@isode.com; bh=KzOyqlF+dadAtlxrXf1LAxLdAp2UPpj2uM6lvKoN1TQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=SCqNKSL8CpWVOSPNfPLFhcbmfMCqsfhBTayXRDPofOATwfYbmAIUN+vtfxFCr+0HPK2IsD hNOkCqH+1rPeNDKdWa+qLJWgEBsokVgLE7KfJep4C+01obO81sNBlCP6WhImLrHG4v66YN HvfnpThoU49C7a8DtnBh4Y0CWZNlyyY=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <VnF5nABBx4FP@statler.isode.com>; Wed, 16 Dec 2015 14:47:57 +0000
To: Barry Leiba <barryleiba@computer.org>, The IESG <iesg@ietf.org>
References: <20151216050031.11217.8507.idtracker@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5671798A.8030005@isode.com>
Date: Wed, 16 Dec 2015 14:47:38 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
In-Reply-To: <20151216050031.11217.8507.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-auth/uelWGWIbmc3hU_UA0kCK2pWFncQ>
Cc: draft-ietf-httpauth-scram-auth@ietf.org, httpauth-chairs@tools.ietf.org, httpauth-chairs@ietf.org, http-auth@ietf.org, draft-ietf-httpauth-scram-auth-all@tools.ietf.org
Subject: Re: [http-auth] Barry Leiba's Yes on draft-ietf-httpauth-scram-auth-14: (with COMMENT)
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: HTTP authentication methods <http-auth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-auth>, <mailto:http-auth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-auth/>
List-Post: <mailto:http-auth@ietf.org>
List-Help: <mailto:http-auth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-auth>, <mailto:http-auth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Dec 2015 14:48:10 -0000
Hi Barry, Thank you for your comments. On 16/12/2015 05:00, Barry Leiba wrote: > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > -- Section 3 -- > > It sends > the username to the server, which retrieves the corresponding > authentication information, i.e. a salt, StoredKey, ServerKey and the > iteration count i. > > As this is written, it's not clear whether the "corresponding > authentication information" is "a salt" alone, or the whole list of > things after. I suggest this: > > NEW > It sends > the username to the server, which retrieves the corresponding > authentication information: a salt, a StoredKey, a ServerKey, > and an iteration count (i). > END Done, thank you. > Why does the paragraph end in a colon ("and sends a ClientProof to the > server:")? > > To begin with, the SCRAM client is in possession of a username and > password (*) (or a ClientKey/ServerKey, or SaltedPassword). > > ...and... > > (*) - Note that both the username and the password MUST be encoded in > UTF-8 [RFC3629]. > > I suggest that splitting these up with a bunch of text in between isn't a > good way to do it. I think this would be better: > > NEW > To begin with, the SCRAM client is in possession of a username and > password, both encoded in UTF-8 [RFC3629] (or a ClientKey/ServerKey, > or SaltedPassword). > END Yes, this is better. > There's no pressing need to use the word "MUST" there. > > Informative Note: Implementors are encouraged to create test cases > that use both username passwords with non-ASCII codepoints. In > particular, it is useful to test codepoints whose "Unicode > Normalization Form C" and "Unicode Normalization Form KC" are > different. > > It would be good to include an informative reference to the Unicode > Normalization Forms document here, so people can easily look up what NFC > and NFKC are. It might also be good to say "Normalization Form Canonical > Composition (NFC)" and "Normalization Form Compatibility Composition > (NFKC)", rather than to use the mixed versions that you have here. Ok > -- Section 4 -- > > from the IANA "Hash Function Textual Names" registry (see > http://www.iana.org) . > > Better, I think, to use the direct URL for the registry (which is fine > with IANA): > http://www.iana.org/assignments/hash-function-text-names/ Ok.
- [http-auth] Barry Leiba's Yes on draft-ietf-httpa… Barry Leiba
- Re: [http-auth] Barry Leiba's Yes on draft-ietf-h… Alexey Melnikov