- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 10 Apr 2006 14:05:15 +0200
- To: werner.donne@re.be
- CC: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>, ietf-dav-versioning@w3.org
Werner Donné wrote: > If new clients should work with older servers there should be > a mechanism for a client to detect the compliance level of the > server. It can then act accordingly. In RFC 2518 the DAV header > seems to be used for this. I don't find such a mechanism in > RFC 3253. Well, the mechanism would be the same. The major question here is whether there's a group of implementors who want that feature. In which case the right thing to do is to define an extension (including the aforementioned discovery mechanism), and publish it in an Internet Draft. If that gets traction, you may be able to get it published as RFC through either the RFC Editor or the IESG. If, at a future date, RFC3253 gets revised, the authors then will certainly consider extensions that have been published since for inclusion into the base protocol. Sounds complicated? Yes. Consider it a way to prevent feature creep :-) Best regards, Julian
Received on Monday, 10 April 2006 12:07:15 UTC