From discuss-bounces@apps.ietf.org Mon Nov 07 13:13:02 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EZBUM-0004rw-9L; Mon, 07 Nov 2005 13:13:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EZBUL-0004ra-5l
	for discuss@megatron.ietf.org; Mon, 07 Nov 2005 13:13:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26702
	for <discuss@apps.ietf.org>; Mon, 7 Nov 2005 13:12:34 -0500 (EST)
Received: from mxout3.cac.washington.edu ([140.142.32.166])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZBjx-0003P1-7o
	for discuss@apps.ietf.org; Mon, 07 Nov 2005 13:29:11 -0500
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP
	id jA7ICuOa002061
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <discuss@apps.ietf.org>; Mon, 7 Nov 2005 10:12:56 -0800
X-Auth-Received: from pp106-152.bctel.ca (pp106-152.bctel.ca [209.52.106.152])
	(authenticated authid=rlmorgan)
	by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id
	jA7ICtdr020070
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <discuss@apps.ietf.org>; Mon, 7 Nov 2005 10:12:56 -0800
Date: Mon, 7 Nov 2005 10:13:13 -0800 (PST)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@perf.cac.washington.edu
To: discuss@apps.ietf.org
Subject: [HTTP authentication discussion]
Message-ID: <Pine.LNX.4.63.0511071006160.9315@perf.cac.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0,
	__HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0,
	__SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols
	<discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>,
	<mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>,
	<mailto:discuss-request@apps.ietf.org?subject=subscribe>
Sender: discuss-bounces@apps.ietf.org
Errors-To: discuss-bounces@apps.ietf.org


In the spirit of "letting people know about new things", let me point out 
the activity below to the discuss@apps list.

We'll be having a dinner BoF tonight (Monday Nov 7); if you're interested 
in attending let me know.

  - RL "Bob"

---------- Forwarded message ----------
Date: Thu, 29 Sep 2005 13:07:54 -0700
From: Lisa Dusseault <lisa@osafoundation.org>
To: HTTP working group <ietf-http-wg@w3.org>,
     CalDAV DevList <ietf-caldav@osafoundation.org>,
     WebDav WG <w3c-dist-auth@w3.org>
Cc: RL 'Bob' Morgan <rlmorgan@washington.edu>, Scott Lawrence <scott@skrb.org>,
     Cyrus Daboo <daboo@isamet.com>, Paul B.Hill <pbh@MIT.EDU>,
     Mike Shaver <shaver@mozilla.org>,
     Alexey Melnikov <alexey.melnikov@isode.com>, Sam Hartman <hartmans@mit.edu>
Subject: HTTP authentication


Talking with various potential CalDAV deployers lately, there's a 
perceived need for better HTTP authentication mechanisms: ones which can 
deal with federated identity and single sign-on.  I've also heard people 
respond "what's the problem? Put an authentication proxy in the proxy 
path" or suggest HTTP-SASL or a number of other possible solutions to 
possible problems.

So, we probably need first to discuss whether there is a problem, and if 
so, what to do about it.  There's been a suggestion to hold a BOF in 
Vancouver (if it's not too late to plan one) to see who the interested 
parties are and start defining (or defining away) the problem.  Another 
idea is to hold a workshop at some point after we've identified the 
interested parties.

Anyway, I've started a separate discussion list for this topic-- I didn't 
want to spam the general HTTP list or make people who weren't interested 
in general HTTP issues (but only in authentication for CalDAV/WebDAV) join 
that list. Please join and chime in any time about what you perceive the 
problem or lack of problem to be or leap straight to what ought to be 
done.

http://lists.osafoundation.org/cgi-bin/mailman/listinfo/ietf-http-auth

Lisa





