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

Julian Reschke <julian.reschke@gmx.de> Tue, 10 February 2015 22:03 UTC

Return-Path: <julian.reschke@gmx.de>
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 822AA1A6FF7 for <http-auth@ietfa.amsl.com>; Tue, 10 Feb 2015 14:03:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 bOmN42Fs9-BS for <http-auth@ietfa.amsl.com>; Tue, 10 Feb 2015 14:03:55 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E16B1A870F for <http-auth@ietf.org>; Tue, 10 Feb 2015 14:03:49 -0800 (PST)
Received: from [192.168.2.175] ([93.217.119.132]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LtUHA-1XeNS4013c-010wc4; Tue, 10 Feb 2015 23:03:40 +0100
Message-ID: <54DA8039.3030108@gmx.de>
Date: Tue, 10 Feb 2015 23:03:37 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Benjamin Kaduk <kaduk@MIT.EDU>, draft-ietf-httpauth-basicauth-update@tools.ietf.org
References: <20150205161049.4222.88369.idtracker@ietfa.amsl.com> <alpine.GSO.1.10.1502101635030.3953@multics.mit.edu>
In-Reply-To: <alpine.GSO.1.10.1502101635030.3953@multics.mit.edu>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:m6G8ggEnxuqq4iZuXzZjZtZC2VEqJcl51pHHR9VOF77jZKzJshf IJz7CnY2oN4o8y65f/GjWyJdMNrNsZs67nWTmbClzGVJ6ACn6AVh6jjVEmBe6h5ooLn+fMQ 5EyXjzjKo6822HRb9D452+P4+3YZd0lkXS3/fWYM1ghOCfjWqzSsJnMIzhefj6ylgzxsDUm oRhv851tBpEInkEB5LxAg==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-auth/U0DDaHF1nSXgH-AYxGcZY72W7kk>
Cc: http-auth@ietf.org
Subject: Re: [http-auth] Last Call: <draft-ietf-httpauth-basicauth-update-05.txt> (The 'Basic' HTTP Authentication Scheme) to Proposed Standard
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: <http://www.ietf.org/mail-archive/web/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: Tue, 10 Feb 2015 22:03:56 -0000

On 2015-02-10 22:36, Benjamin Kaduk wrote:
> On Thu, 5 Feb 2015, The IESG wrote:
>
>>
>> The IESG has received a request from the Hypertext Transfer Protocol
>> Authentication WG (httpauth) to consider the following document:
>> - 'The 'Basic' HTTP Authentication Scheme'
>>    <draft-ietf-httpauth-basicauth-update-05.txt> as Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2015-02-19. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     This document defines the "Basic" Hypertext Transfer Protocol (HTTP)
>>     Authentication Scheme, which transmits credentials as userid/password
>>     pairs, obfuscated by the use of Base64 encoding.
>
> I forget if this was already mentioned, but "local-specific encoding" in
> section 2 should probably use "locale" instead of "local".

No, it wasn't. Thanks!