Re: [http-auth] Last Call: <draft-ietf-httpauth-basicauth-update-05.txt> (The 'Basic' HTTP Authentication Scheme) to Proposed Standard

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 06 February 2015 15:24 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8EE11A1B24; Fri, 6 Feb 2015 07:24:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 6BIHRV7_g4bu; Fri, 6 Feb 2015 07:23:59 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 23A451A1B49; Fri, 6 Feb 2015 07:23:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1423236238; d=isode.com; s=selector; i=@isode.com; bh=ERu9BNvC7HpB0NGmvsKvh6gQa/rBDawS2YTLQj6CkHY=; 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=oTi7L9+Kx6mF7LWxkyXvqS7DNBDKbTZ7v3LGldnzV+1HGp/Rfsjv9eVUW6c7ouEo9GLJIV AGskwUXEbOXpVsDI1XNB7xrJck6K0583N5FRhThumtickVrYthtJL7cwJSkCDYSb1yw8VQ mq3/hKa++HdeZnvBsnk9Rc9mvqO7lm4=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <VNTcjQAKaH3N@waldorf.isode.com>; Fri, 6 Feb 2015 15:23:58 +0000
Message-ID: <54D4DC68.3030507@isode.com>
Date: Fri, 06 Feb 2015 15:23:20 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org
Subject: Re: [http-auth] Last Call: <draft-ietf-httpauth-basicauth-update-05.txt> (The 'Basic' HTTP Authentication Scheme) to Proposed Standard
References: <20150205161049.4222.88369.idtracker@ietfa.amsl.com> <kdr7da51k6t581cdppljqvdnf6401cjb4o@hive.bjoern.hoehrmann.de>
In-Reply-To: <kdr7da51k6t581cdppljqvdnf6401cjb4o@hive.bjoern.hoehrmann.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WeALBSaSTAF-j13SLYpp9JfTVXQ>
Cc: http-auth@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 15:24:02 -0000

Hi Bjoern,

On 05/02/2015 22:49, Bjoern Hoehrmann wrote:
  [snip]
>     The realm value is an opaque string
>     which can only be compared for equality with other realms on that
>     server.
>
> RFC 7235 says "The realm value is a string, generally assigned by the
> origin server, that can have additional semantics specific to the
> authentication scheme." This seems contradictory (perhaps the intent is
> to say that for the particular case of Basic, the realm value is opaque
> in contrast to other schemes where it might not be opaque, but that is
> not clear from the text) and misleading (users make decisions based on
> the string, which often contains human readable text, so it's not really
> opaque to them).
I think it is opaque to clients and servers, so they shouldn't try to 
parse it.
>     The original definition of this authentication scheme failed to
>     specify the character encoding scheme used to convert the user-pass
>     into an octet sequence.
>
> I think it would be more appropriate to say that it did not do so. That
> wasn't a particular "failure", sending unlabeled 8bit (and 7bit) content
> was normal at the time, in part because other system parts also did not
> know or care about character encodings.
I think the current text as specified is accurate, but I don't have a 
strong opinion.
> There should be an example for "no other authentication parameters are
> defined -- unknown parameters MUST be ignored by recipients", otherwise
> such extension points are too easily missed by implementers.