Re: [secdir] proxies and forwarding of credentials, was: SECDIR review of draft-ietf-httpbis-p7-auth-24

Bjoern Hoehrmann <derhoermi@gmx.net> Thu, 31 October 2013 14:30 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 5234011E8149 for <secdir@ietfa.amsl.com>; Thu, 31 Oct 2013 07:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 VsJmjgM0kUW2 for <secdir@ietfa.amsl.com>; Thu, 31 Oct 2013 07:30:25 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id CE98221F9DD5 for <secdir@ietf.org>; Thu, 31 Oct 2013 07:30:24 -0700 (PDT)
Received: from netb.Speedport_W_700V ([84.180.225.225]) by mail.gmx.com (mrgmx102) with ESMTPA (Nemesis) id 0Mcgur-1VKUpx221B-00Hsno for <secdir@ietf.org>; Thu, 31 Oct 2013 15:30:24 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Julian Reschke <julian.reschke@greenbytes.de>
Date: Thu, 31 Oct 2013 15:30:22 +0100
Message-ID: <5op4795b77js1jfi5pqfv9jss3ko77vd4a@hive.bjoern.hoehrmann.de>
References: <52700DE4.8020208@bbn.com> <52725E8E.50106@greenbytes.de>
In-Reply-To: <52725E8E.50106@greenbytes.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:R+c4qbQIQcJmo76fRrccV/pAzxs1PJ/TGTz/iReCHd9LDDKEVni jbjAhWWG1apg6X4cD6ACw8ledb9e81JDBvAovUqhxcbj0N/7G2yvaEtAVODJjxVZgV4uQ5n ma6T5kL47OqjMbhksAHHDw7vbboNMf3FxXWzY2DrGTCx6/F7lHT8OamK+u2Zh1IvXBcIkqb WwNcqGiSlDRvP1KxHz2gw==
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] proxies and forwarding of credentials, 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:30:29 -0000

* Julian Reschke wrote:
>On 2013-10-29 20:35, Stephen Kent wrote:
>> ...
>> In Section 4.3, the text says:
>>
>> A proxy MAY relay
>>
>> the credentials from the client request to the next proxy if that is
>>
>> the mechanism by which the proxies cooperatively authenticate a given
>>
>> request.
>>
>> If, as stated here, a set of proxies cooperatively authenticate a
>> request, then isn’t this a MUST vs. a MAY?
>> ...
>
>Maybe. I have no experience with proxy authentication, and this piece of 
>text was copied from 
><http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.14.34>.
>
>Perhaps this is a case where we should drop the RFC2119 keywords [...]

Ordinarily a proxy is not supposed to forward the `Proxy-Authorization`
header and an implementation that forwards it by accident fails to meet
the requirements of the specification, so use of RFC 2119 keywords seems
appropriate to me. I also see nothing wrong with the proxy offering an
configuration option to, say, relay the credentials for some users, but
not for others, so this cannot be a MUST. I think the text is fine.
-- 
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/