webdav@conference.ietf.jabber.com - 2003/03/18


[09:09] %% logger has arrived.
[16:49] %% mrose has arrived.
[17:01] %% rjs3 has arrived.
[17:02] %% leg has arrived.
[17:06] <mrose> meeting is about to begin
[17:10] <mrose> jim: called to order
[17:10] <mrose> lisa: agenda: report on interim wg meeting, rfc2581bis, quota, bindings, ordered collections, acl, dasl
[17:10] <mrose> lisa: any bashing?
[17:11] <mrose> lisa: no here is able to talk about DASL, so we won't discuss that
[17:11] <mrose> lisa: no other bashing
[17:12] <mrose> jim: interop/interim results... 09/2002: 37 people testing 13 clients and 16 servers
[17:12] <mrose> jim: progress underway to develop an improved compliance test suite
[17:14] <mrose> jim: it's called "litmus", hope to see it released soon after some IP issues are addressed
[17:15] <mrose> jim: interim meeting in 01/03
[17:16] <mrose> lisa: issues relating to rfc2518
[17:20] <mrose> lisa: a lock either directly or indirectly locks a resource. adding text about a lock-root and resource creation
[17:26] <mrose> lisa: depth:infinity locks
[17:30] %% gwachob has arrived.
[17:38] %% The Saint has arrived.
[17:40] %% The Saint has left.
[17:41] %% gwachob has left.
[17:52] %% mark.ellison has arrived.
[17:55] <mrose> can someone else physically here scribe for a while, i've got a fire to put out...
[17:58] <leg> lots of talk about how to fix certain problems with 2518 problems. AD advice is to make the documents clarity.
[17:58] <leg> err, make the documents more clear.
[18:01] <leg> now getting more and more philosophical
[18:04] <leg> more on locks: when a resource is locked, what operations must fail without a lock-token?
[18:08] <leg> are all live properties (server semantically aware properties) lockable?
[18:08] <leg> there exist implementations that allow some live properties to be modified even if they are locked and the client doesn't have a lock token.
[18:10] <leg> now discussing birth control pills in the water
[18:13] %% duerst has arrived.
[18:20] <leg> now discussing proposed 207 response code replacement
[18:20] %% duerst has left.
[19:02] %% mark.ellison has left.
[19:05] %% rjs3 has left.
[19:05] %% leg has left.
[19:19] %% leg has arrived.
[19:19] %% leg has left.
[19:26] %% mrose has left.