Re: [caldav] [VCARDDAV] new webdav sync draft

Julian Reschke <julian.reschke@gmx.de> Fri, 20 November 2009 17:38 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F39E3A6875 for <caldav@core3.amsl.com>; Fri, 20 Nov 2009 09:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.535
X-Spam-Level:
X-Spam-Status: No, score=-4.535 tagged_above=-999 required=5 tests=[AWL=-1.936, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lZr89RPGPxMe for <caldav@core3.amsl.com>; Fri, 20 Nov 2009 09:38:13 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id DFF643A6A38 for <caldav@ietf.org>; Fri, 20 Nov 2009 09:38:12 -0800 (PST)
Received: (qmail invoked by alias); 20 Nov 2009 17:38:08 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.105]) [217.91.35.233] by mail.gmx.net (mp025) with SMTP; 20 Nov 2009 18:38:08 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+IxgRo3wuIOqRHXKwXql3/erUI0GzxqGrKCX7qgT ntWn0NQk092nwL
Message-ID: <4B06D3FA.8050904@gmx.de>
Date: Fri, 20 Nov 2009 18:38:02 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <4B057E6B.7040808@sun.com> (sfid-20091120_062140_570344_FA568882) <1258668093.15545.555.camel@happy.home.mcmillan.net.nz> <4B064079.50404@gmx.de> <351598D1DDF378AF6AF4C3E4@caldav.corp.apple.com> <4B06A836.7010007@gmx.de> <4B06D073.5080107@isode.com>
In-Reply-To: <4B06D073.5080107@isode.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.57
Cc: Arnaud Quillaud <Arnaud.Quillaud@Sun.COM>, caldav@ietf.org, w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] [VCARDDAV] new webdav sync draft
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2009 17:38:14 -0000

Alexey Melnikov wrote:
> ...
>> <http://greenbytes.de/tech/webdav/rfc4918.html#rfc.section.21.1>:
>>
>> "Creation of identifiers in the "DAV:" namespace is controlled by the 
>> IETF."
>>
>> So it's not relevant whether something is generic. What's important is 
>> that there's IETF consensus to add new names to the namespace.
>>
>> I'm not saying this can't be the case here, but I think the proper way 
>> would be to start with a proposal in a custom namespace, and then 
>> switch to the DAV: namespace once it's clear that consensus has been 
>> achieved.
> 
> This sounds like a question to bring during IETF LC. If the document 
> fails to reach IETF consensus, then the prefix can be changed.
> Unless you are concerned about early implementations of the draft.
> ...

Not sure.

What you say makes it sound as if any document published by the IETF can 
use the DAV: namespace; I think the intent of RFC 4918 was something 
else (but I may be misinterpreting it): the default extension point for 
WebDAV (both in RFC 4918 and 2518) is to put extensions into a 
*different* namespace.

So far we have made exceptions in cases where the specs actually started 
as WG deliverables (redirect, search, or bind), were proposed by another 
WG (MKCOL extension), or were a *really* minor extension to an existing 
WebDAV spec (WebDAV Current Principal Extension).

The concern about early implementations is there as well, of course.

Best regards, Julian