- From: Eric Sedlar <eric.sedlar@oracle.com>
- Date: Wed, 18 Sep 2002 11:09:56 -0700
- To: "Julian Reschke" <julian.reschke@gmx.de>, "Lisa Dusseault" <lisa@xythos.com>, "'Ilya Kirnos'" <ilya.kirnos@oracle.com>
- Cc: "'Webdav WG'" <w3c-dist-auth@w3c.org>
Authentication is explicitly out of the scope of the ACL spec. Authentication is assumed to be handled at the HTTP level, and there are already plenty of schemes for this. --Eric ----- Original Message ----- From: "Julian Reschke" <julian.reschke@gmx.de> To: "Lisa Dusseault" <lisa@xythos.com>; "'Ilya Kirnos'" <ilya.kirnos@oracle.com> Cc: "'Webdav WG'" <w3c-dist-auth@w3c.org> Sent: Wednesday, September 18, 2002 1:37 AM Subject: RE: Interop issue: how can clients force authentication? .. > makes it clear that we need some more time to precisely describe what the > actual problem is. It's an interesting problem, and I suppose it needs to be > discussed in relation to the ACL spec. However I don't think there's any > reason to declare it an interop problem just to rush a quick workaround into > RFC2518bis. >
Received on Wednesday, 18 September 2002 14:13:57 UTC