Re: [http-auth] re-call for IETF http-auth BoF
"Harry Halpin" <hhalpin@w3.org> Sun, 05 June 2011 21:32 UTC
Return-Path: <hhalpin@w3.org>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F00AE21F8502; Sun, 5 Jun 2011 14:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4aDtcp3IEv-J; Sun, 5 Jun 2011 14:32:54 -0700 (PDT)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by ietfa.amsl.com (Postfix) with ESMTP id 6296121F8500; Sun, 5 Jun 2011 14:32:53 -0700 (PDT)
Received: from www-data by jay.w3.org with local (Exim 4.69) (envelope-from <hhalpin@w3.org>) id 1QTKw8-0004Ua-Eq; Sun, 05 Jun 2011 17:32:44 -0400
Received: from 87.149.171.109 (SquirrelMail authenticated user hhalpin) by webmail-mit.w3.org with HTTP; Sun, 5 Jun 2011 22:32:44 +0100 (BST)
Message-ID: <6cdda6a1c5901b19823e4e2cf54b7e90.squirrel@webmail-mit.w3.org>
In-Reply-To: <878vtgfbs1.fsf@bluewind.rcis.aist.go.jp>
References: <878vtgfbs1.fsf@bluewind.rcis.aist.go.jp>
Date: Sun, 05 Jun 2011 22:32:44 +0100
From: Harry Halpin <hhalpin@w3.org>
To: http-auth@ietf.org, y.oiwa@aist.go.jp
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: public-identity@w3.org, websec@ietf.org, saag@ietf.org, Sean Turner <turners@ieca.com>
Subject: Re: [http-auth] re-call for IETF http-auth BoF
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 05 Jun 2011 21:32:55 -0000
> Dear all at http-auth mailing list, > (Cc: Peter, Sean, Harry, and related mailing lists subscribers) > > following the discussions in the Prague http-auth Bar-BoF in March, > and the W3C Identity in Browser workshop in the last month, now I > would like to re-call the formation of BoF for http-auth in IETF. The > workshop was really hot and enjoying, and there were so many useful > inputs to both Web community and IETF, I believe. Some materials > presented and discussed there are available at > <http://www.w3.org/2011/identity-ws/>. > > # Harry, are the *output* materials ofn the workshop already available to > public? > The workshop already links to all papers and slides on the website. There will be a final report released in about 2 weeks. The public-identity@w3.org will be list I use to get input to the draft final report, to join email "subscribe" in subject line to public-identity-request@w3.org. From my memory there was interest in MutualAuth, primarily from the financial industry and banks, who really did seem to want it. The browser vendors were of course skeptical of anything in chrome, but other discussions such as Dirk Balfanz's do to auth in the OS layer could provide an alternative. [1] http://www.w3.org/2011/identity-ws/ > Currently I'm preparing a start-up version of problem statement document > and > proposed BoF agenda. However, very unfortunately, the last week I had a > severe fever heat and could not work well (I'm really sorry about that). > I'm going to submit them to the list within two days, and if possible > comments to the last version of the agenda proposal, available at > <http://www.ietf.org/mail-archive/web/http-auth/current/msg00770.html>, > are welcome. I'm currently working based on that. > > Thanks, > > Yutaka > > -- > Yutaka OIWA, Ph.D. Research > Scientist > Research Center for Information Security > (RCIS) > National Institute of Advanced Industrial Science and Technology > (AIST) > Mail addresses: <y.oiwa@aist.go.jp>, > <yutaka@oiwa.jp> > OpenPGP: id[440546B5] fp[7C9F 723A 7559 3246 229D 3139 8677 9BD2 4405 > 46B5] > >
- Re: [http-auth] [saag] re-call for IETF http-auth… Yutaka OIWA
- Re: [http-auth] [saag] re-call for IETF http-auth… Tim
- Re: [http-auth] [saag] re-call for IETF http-auth… Nico Williams
- [http-auth] re-call for IETF http-auth BoF Yutaka OIWA
- Re: [http-auth] re-call for IETF http-auth BoF Harry Halpin
- Re: [http-auth] [saag] re-call for IETF http-auth… Hannes Tschofenig
- Re: [http-auth] [saag] re-call for IETF http-auth… Nico Williams
- Re: [http-auth] [saag] re-call for IETF http-auth… Tim
- Re: [http-auth] [saag] re-call for IETF http-auth… Marsh Ray
- Re: [http-auth] [saag] re-call for IETF http-auth… Nico Williams
- Re: [http-auth] [saag] re-call for IETF http-auth… Nico Williams
- Re: [http-auth] [saag] re-call for IETF http-auth… Stephen Farrell
- Re: [http-auth] [saag] re-call for IETF http-auth… Nico Williams
- Re: [http-auth] [saag] re-call for IETF http-auth… Marsh Ray
- Re: [http-auth] [saag] re-call for IETF http-auth… Nico Williams
- Re: [http-auth] re-call for IETF http-auth BoF Yutaka OIWA
- Re: [http-auth] re-call for IETF http-auth BoF Yutaka OIWA
- Re: [http-auth] re-call for IETF http-auth BoF Julian Reschke
- [http-auth] Fwd: re-call for IETF http-auth BoF Yutaka OIWA
- Re: [http-auth] [websec] re-call for IETF http-au… Phillip Hallam-Baker
- Re: [http-auth] [websec] re-call for IETF http-au… Alexey Melnikov
- Re: [http-auth] [saag] [websec] re-call for IETF … Peter Gutmann
- Re: [http-auth] [saag] [websec] re-call for IETF … Nico Williams
- Re: [http-auth] [websec] [saag] re-call for IETF … Stephen Farrell
- Re: [http-auth] [websec] [saag] re-call for IETF … Nico Williams
- Re: [http-auth] [saag] [websec] re-call for IETF … Yutaka OIWA
- Re: [http-auth] [saag] [websec] re-call for IETF … Nico Williams
- Re: [http-auth] [saag] [websec] re-call for IETF … Yutaka OIWA
- Re: [http-auth] [saag] [websec] re-call for IETF … Nico Williams
- Re: [http-auth] [saag] [websec] re-call for IETF … KIHARA, Boku
- [http-auth] Fwd: [saag] [websec] re-call for IETF… KIHARA, Boku
- Re: [http-auth] [websec] Fwd: [saag] re-call for … Thomas Roessler
- Re: [http-auth] [saag] [websec] re-call for IETF … Nico Williams
- Re: [http-auth] [saag] [websec] re-call for IETF … Yutaka OIWA
- Re: [http-auth] [saag] [websec] re-call for IETF … Yutaka OIWA
- Re: [http-auth] [saag] [websec] re-call for IETF … Nico Williams
- Re: [http-auth] [saag] [websec] re-call for IETF … Peter Gutmann
- Re: [http-auth] [saag] [websec] re-call for IETF … Nico Williams
- Re: [http-auth] [saag] [websec] re-call for IETF … Josh Howlett
- Re: [http-auth] [saag] [websec] Fwd: re-call for … Marc Williams
- Re: [http-auth] [saag] [websec] Fwd: re-call for … SHIMIZU, Kazuki
- Re: [http-auth] [saag] [websec] Fwd: re-call for … GOGWIM, JOEL GODWIN
- Re: [http-auth] [saag] [websec] Fwd: re-call for … Nico Williams
- Re: [http-auth] [saag] [websec] Fwd: re-call for … Henry B. Hotz
- Re: [http-auth] [saag] [websec] Fwd: re-call for … Yutaka OIWA
- Re: [http-auth] [saag] [websec] Fwd: re-call for … Yutaka OIWA
- Re: [http-auth] [saag] [websec] Fwd: re-call for … Yaron Sheffer
- Re: [http-auth] [websec] [saag] Fwd: re-call for … Marsh Ray
- Re: [http-auth] [websec] [saag] Fwd: re-call for … Stephen Farrell
- Re: [http-auth] [saag] [websec] Fwd: re-call for … Nico Williams
- Re: [http-auth] [saag] [websec] re-call for IETF … Phillip Hallam-Baker
- Re: [http-auth] [websec] [saag] re-call for IETF … Thomas Fossati
- Re: [http-auth] [websec] [saag] re-call for IETF … Nico Williams
- Re: [http-auth] [saag] [websec] re-call for IETF … Henry B. Hotz