Re: [sieve] Proposed "pab" URI scheme registration for Sieve External Lists

Cyrus Daboo <cyrus@daboo.name> Tue, 30 November 2010 20:13 UTC

Return-Path: <cyrus@daboo.name>
X-Original-To: sieve@core3.amsl.com
Delivered-To: sieve@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90B213A6BDF for <sieve@core3.amsl.com>; Tue, 30 Nov 2010 12:13:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level:
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 WuYUrcrHnqUg for <sieve@core3.amsl.com>; Tue, 30 Nov 2010 12:13:37 -0800 (PST)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 7ACDD3A6C2A for <sieve@ietf.org>; Tue, 30 Nov 2010 12:13:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 180931AD71AEE; Tue, 30 Nov 2010 15:14:49 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zGRl3bzAg8rO; Tue, 30 Nov 2010 15:14:48 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id D9C5F1AD71AE3; Tue, 30 Nov 2010 15:14:47 -0500 (EST)
Date: Tue, 30 Nov 2010 15:14:41 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Sieve WG <sieve@ietf.org>
Message-ID: <57BA898BDCAFFFBEC5607786@caldav.corp.apple.com>
In-Reply-To: <4CF5529B.5010708@isode.com>
References: <4CF5529B.5010708@isode.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1380"
Subject: Re: [sieve] Proposed "pab" URI scheme registration for Sieve External Lists
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Nov 2010 20:13:38 -0000

Hi Alexey,

--On November 30, 2010 7:38:03 PM +0000 Alexey Melnikov 
<alexey.melnikov@isode.com> wrote:

>    This specification requests the IANA to register the
>    "pab" URI scheme as specified in this document and summarized in
>    the following template, per [RFC4395]:
>
>    URI scheme name:  pab

So I am not convinced we should have this URI scheme (though that is not a 
strong objection).

If we do stick with it, then:

1) Since you have broadened the scope to "applications" in general, why 
does this have to remain a "personal" reference? What about shared or 
global address books available to the application. i.e. shouldn't this be 
"ab" rather than "pab"?

2) I wonder if we want to be more generic - not just address books (e.g. I 
could easily imagine a SIEVE system looking at my calendar to determine 
possible vacation times automatically - i.e. it would be nice to just add 
an all-day event to a special "vacation" calendar and have that 
automatically turn on SIEVE vacation for that day). So if we stick with a 
URI, why not target it specifically at sieve, but allow for different 
types, e.g. have a 'sieveid' scheme that can be used to represent any 
external "system" identifier needed in a SIEVE script. The syntax could 
include a type specifier as the first item, e.g.:

sieveid:addressbook:default
sieveid:calendar:vacation


-- 
Cyrus Daboo