Re: [saag] Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 15 May 2012 16:41 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E67521F8745 for <saag@ietfa.amsl.com>; Tue, 15 May 2012 09:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level:
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Cy5hwzyG-vkS for <saag@ietfa.amsl.com>; Tue, 15 May 2012 09:41:32 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 89BE421F8731 for <saag@ietf.org>; Tue, 15 May 2012 09:41:32 -0700 (PDT)
Received: from [10.20.30.102] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q4FGfThJ003481 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 15 May 2012 09:41:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAK3OfOgUJCzeCJpHW_B8ieq657aLeibRJyVpHmjrfYsExJ1+rA@mail.gmail.com>
Date: Tue, 15 May 2012 09:41:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <410AB643-F18B-47F1-926E-9D34A1EE24DD@vpnc.org>
References: <14A09626-8397-4656-A042-FEFDDD017C9F@mnot.net> <4DAC6FBC-3E6D-4CD1-9B5C-0CA5986169A5@mnot.net> <A4D25A70-C9BA-4E0D-A271-F3E6C5E01465@vpnc.org> <CAK3OfOjN=1T3kzxJ3Gcx500=23Y8xcrt=c2XCOnAo8HBB4TUpQ@mail.gmail.com> <F656F4BC-A9BA-4BEB-A1CE-1C603A8ACEBD@vpnc.org> <CAK3OfOgUJCzeCJpHW_B8ieq657aLeibRJyVpHmjrfYsExJ1+rA@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF Security Area Advisory Group <saag@ietf.org>
Subject: Re: [saag] Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 16:41:33 -0000

On May 15, 2012, at 9:33 AM, Nico Williams wrote:

> On Tue, May 15, 2012 at 11:16 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>> I'm pretty sure that a pointer to draft-williams-rest-gss-00 (or any other expired draft in this area) is all the httpbis WG needs; they don't need an up-to-date draft.
> 
> Good point.  But working on the classification document is making me
> think of possible enhancements to my proposal anyways :)
> 
>> Having said that, I bet that they would very much like to see a classification / analysis document to help them!
> 
> Right.  Assuming they get lots of proposals it will be necessary to
> figure out how to analyze them.  Even if they get no proposals it'd be
> useful to have such a document to guide any design team.

At this point they have zero proposals, but I'm hoping to change that by nudging here (not by writing a proposal myself).

> Personally I continue to believe that there will not be a single
> authentication mechanism that satisfies all users' needs, so I will
> continue to argue for pluggable frameworks.  However, I'm less
> interested in this than I am in the analysis at this point.

We already have a pluggable framework; if it needs changes, letting the httpbis WG know that early would be important.

> As for the dearth of proposals...  I suspect part of it is not knowing
> what HTTP 2.0 will look like, and part of it is weariness: web auth
> has been a resisting solutions for many years now.  Perhaps no one
> really expects HTTPbis WG to be able to crack that nut?


The IESG expects them to not only crack the nut, but to show that the inside is edible. This was made very clear in the rechartering discussion (well, without the food analogy).

--Paul Hoffman