
Return-Path: <ietf-http-auth@osafoundation.org>
X-Original-To: ietf-http-auth@osafoundation.org
Delivered-To: ietf-http-auth@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 94E4A7F563 for <ietf-http-auth@osafoundation.org>; Sun,  2 Oct 2005 14:17:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 55AED142285 for <ietf-http-auth@osafoundation.org>; Sun,  2 Oct 2005 14:17:30 -0700 (PDT)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32040-03 for <ietf-http-auth@osafoundation.org>; Sun, 2 Oct 2005 14:17:30 -0700 (PDT)
Received: from chico.rediris.es (chico.rediris.es [130.206.1.3]) by laweleka.osafoundation.org (Postfix) with ESMTP id B04BF142284 for <ietf-http-auth@osafoundation.org>; Sun,  2 Oct 2005 14:17:29 -0700 (PDT)
Received: from [10.8.1.26] (login.rediris.es [130.206.1.21]) by chico.rediris.es (8.12.10/8.9.1) with ESMTP id j92LHRHx024848 for <ietf-http-auth@osafoundation.org>; Sun, 2 Oct 2005 23:17:28 +0200 (CEST)
Message-ID: <43404EB9.3050708@osafoundation.org>
Date: Sun, 02 Oct 2005 23:18:49 +0200
From: "Diego R. Lopez" <ietf-http-auth@osafoundation.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-http-auth@osafoundation.org
Subject: Re: [Ietf-http-auth] Whay is caldav special?
References: <8E017D07811076A41D3358C5@ninevah.cyrusoft.com>	<20050930165929.02BF08A02D@laser.networkresonance.com>	<20050930180952.GB4514@markbaker.ca>	<86br2aqv8n.fsf@raman.networkresonance.com>	<20050930184136.GC4514@markbaker.ca>	<433D91D7.8030204@secure-endpoints.com>	<863bnmqr83.fsf@raman.networkresonance.com> <433D982C.6090705@secure-endpoints.com>
In-Reply-To: <433D982C.6090705@secure-endpoints.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-1.7 tagged_above=-50.0 required=4.0 tests=BAYES_00
X-Spam-Level: 
X-Mailman-Approved-At: Mon, 03 Oct 2005 06:22:28 -0700
X-BeenThere: ietf-http-auth@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-http-auth.osafoundation.org
List-Unsubscribe: <http://lists.osafoundation.org/cgi-bin/mailman/listinfo/ietf-http-auth>, <mailto:ietf-http-auth-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-http-auth>
List-Post: <mailto:ietf-http-auth@osafoundation.org>
List-Help: <mailto:ietf-http-auth-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/cgi-bin/mailman/listinfo/ietf-http-auth>, <mailto:ietf-http-auth-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Oct 2005 21:17:30 -0000

Hi,

Being the first time I write here, let me briefly introduce myself.
My name is Diego Lopez and I work for the Spanish National Research
Network (RedIRIS). I've been working for some time in our own
federated access control system (PAPI, http://papi.rediris.es/),
and I'm leading the group building eduGAIN, the authentication
and authorization infrastructure of the pan-European academic
network, GEANT2.

>>No, I'm just saying that people do that now and we have to
>>> recognize the reasons why that's done and design a solution
>>> that transitions as cleanly as possible from that.
>>> 
>>> -Ekr
> 
> 
> Then let's start a list of the reasons why sites use forms instead
> of HTTP AUTH:

I think the point is not how the authorization state is maintained
across different HTTP requests/responses, but how the initial
rights to invoke a certain operation are established. Once this
initial phase is performed, the state can be maintained either
by encrypyed cookies, HTTP Auth or whatever other similar method:
they reduce to the same general case of (more or less) protected
contents in the HTTP headers.

Of course one could look for a more ellaborated or general way of
dealing with this authorization headers, but I think the real challenge
here is to look for a way of expressing access requirements and rights
in the initial interaction, much like HTTP Auth does now, but with the
richer semantics that what some of you call "forms-and-cookies approach"
allows.

Be goode,
-- 
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez

Red.es - RedIRIS
The Spanish NREN

e-mail: diego.lopez@rediris.es
jid:    drlopez@im.rediris.es
Tel:    +34 955 056 621
Mobile: +34 669 898 094
-----------------------------------------

