Re: [secdir] additional mechanisms on top of the auth framework, was: SECDIR review of draft-ietf-httpbis-p7-auth-24

Bjoern Hoehrmann <derhoermi@gmx.net> Thu, 31 October 2013 14:44 UTC

Return-Path: <derhoermi@gmx.net>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2D821F9EE5 for <secdir@ietfa.amsl.com>; Thu, 31 Oct 2013 07:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level:
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id elrgoEbv-apd for <secdir@ietfa.amsl.com>; Thu, 31 Oct 2013 07:44:25 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id A54A711E8125 for <secdir@ietf.org>; Thu, 31 Oct 2013 07:44:24 -0700 (PDT)
Received: from netb.Speedport_W_700V ([84.180.225.225]) by mail.gmx.com (mrgmx101) with ESMTPA (Nemesis) id 0M3NEK-1VtYpB1QxM-00r2UR for <secdir@ietf.org>; Thu, 31 Oct 2013 15:44:24 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Julian Reschke <julian.reschke@greenbytes.de>
Date: Thu, 31 Oct 2013 15:44:24 +0100
Message-ID: <omq479p5tt306gress6en7thrh06lr1ge6@hive.bjoern.hoehrmann.de>
References: <52700DE4.8020208@bbn.com> <52726125.1000802@greenbytes.de>
In-Reply-To: <52726125.1000802@greenbytes.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:3NxLwSYNBDU1cFQhmmVB+cIvCn4YtGBbyq08uzht4GfCkFMmnP1 /GYvwrMHyLSiEA12E3FueSOqaqlwpXQhVLrrGN/tHyLw19VNJxwAWm1ZPMH8XjjSccqR3oj f/AKz+r8U/5B1EI55fOYFSqL9ZSCo8Z1w9q1+OWHkK4XipL6RpywzIiWosOvSjLZSLnqWXC J/fxiWXcY94O4er45nhSw==
X-Mailman-Approved-At: Thu, 31 Oct 2013 08:15:22 -0700
Cc: secdir <secdir@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, "Mankin, Allison" <amankin@verisign.com>, HTTP Working Group <ietf-http-wg@w3.org>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [secdir] additional mechanisms on top of the auth framework, was: SECDIR review of draft-ietf-httpbis-p7-auth-24
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2013 14:44:29 -0000

* Julian Reschke wrote:
>On 2013-10-29 20:35, Stephen Kent wrote:
> > ...
> > Later on page 6 the text says:
>>
>> The HTTP protocol does not restrict applications to this simple
>> challenge-response framework for access authentication.Additional
>> mechanisms MAY be used, such as encryption at the transport level or
>> via message encapsulation, and with additional header fields
>> specifying authentication information.However, such additional
>> mechanisms are not defined by this specification.
>>
>> Encryption is not, per se, an authentication mechanism. Please revise
>> this text.
>> ...
>
>OK. Maybe:
>
>"HTTP does not restrict applications to this simple challenge-response 
>framework. Additional mechanisms can be used, such as additional header 
>fields carrying authentication information, or encryption on the 
>transport layer in order to provide confidentiality. However, such 
>additional mechanisms are not defined by this specification."
>
>?

I think doing s/encryption/authentication/ instead would be better.
There is no reason to discuss confidentiality here. Encryption and other
cryptographic techniques are used in many authentication schemes, like
with client certificates; that may have been the idea behind the text.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/