Re: [sieve] I-D Action:draft-ietf-sieve-external-lists-07.txt

Barry Leiba <barryleiba@computer.org> Fri, 06 May 2011 20:33 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: sieve@ietfa.amsl.com
Delivered-To: sieve@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2B75E07D6 for <sieve@ietfa.amsl.com>; Fri, 6 May 2011 13:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.246
X-Spam-Level:
X-Spam-Status: No, score=-103.246 tagged_above=-999 required=5 tests=[AWL=-0.269, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uv3APBVExHyf for <sieve@ietfa.amsl.com>; Fri, 6 May 2011 13:33:08 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0910AE07DB for <sieve@ietf.org>; Fri, 6 May 2011 13:33:07 -0700 (PDT)
Received: by ywi6 with SMTP id 6so1617342ywi.31 for <sieve@ietf.org>; Fri, 06 May 2011 13:33:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=SivTM/I7S+g764Fx/7hcUKXKZAXw2CABxvFJnOB50Ec=; b=hI9YF+iWYFO2nSi+17jKlJJrQbxHwwc66OhPNCYWViqY/AIX2wnK1LGdjl6c6283fn 95dzC4hxjY8fb1YKb+Gi3Y9iBkCbE1/sV06/VKR2LqZWXJbkRVp0tn/OAJPTj7nFEvpn NsHduv+ffuXi0i+HY8foSfL0ncpguSlNlWRO0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=EtIvhua4R9NxOcKmzA6Rx4pj7d441zRCLVpS2ZWToIP2ronmJS/XpitP3GxFWr3yUX f/EOSa2Rg3WrLHmChCIyCO7+uIRtR0h0BtFC0i7vpY1t9zGHgq3ZqTtZFAjqKkt08nuD 8TfjaK7m7DNb3n1DBvZ/I7jiy3c2H/t2b2nAo=
MIME-Version: 1.0
Received: by 10.150.73.41 with SMTP id v41mr4001948yba.106.1304713985589; Fri, 06 May 2011 13:33:05 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.137.13 with HTTP; Fri, 6 May 2011 13:33:05 -0700 (PDT)
In-Reply-To: <BANLkTimSPgifh9KRoGAc73J6TKb3ZMV-AQ@mail.gmail.com>
References: <20110421144501.29652.47331.idtracker@ietfc.amsl.com> <BANLkTindZim5y5yPtpSbFLAwEV7bhjXWMg@mail.gmail.com> <BANLkTimSPgifh9KRoGAc73J6TKb3ZMV-AQ@mail.gmail.com>
Date: Fri, 06 May 2011 16:33:05 -0400
X-Google-Sender-Auth: s7zS_t4A40JrwjtyNZRmzjyvEr0
Message-ID: <BANLkTik=Cy3T7dFZHxtwMS6TN29vw2_QuQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Sieve mailing list <sieve@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [sieve] I-D Action:draft-ietf-sieve-external-lists-07.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 06 May 2011 20:33:08 -0000

> In response to review on the uri-review list, I have changed the URI
> schema name from "ab" to "addrbook".

In further discussion on the uri-review list, Graham, who will be the
expert reviewer we'll have to convince when we get to that point, has
pushed back on our defining an "addrbook" URI scheme for this.  At the
moment, he's not speaker as the expert reviewer, but this tells us
where we'll stand when he does.  It's still possible for us to
convince him, but for now, he's not convinced.

He suggests that we we use the "urn" scheme, either coming in as part
of the existing IETF parameter namespace:
   urn:ietf:param:sieve:addrbook:default
...or defining and registering our own new namespace:
   urn:addrbook:default

We're concerned that the former generates too-long and too-ugly URIs
for our purposes.  The second is possible, but I actually think it's a
*worse* idea to define a URN namespace for "addrbook" than it is to
make a URI scheme for it.

For those who want to see the discussions, here are the three most
significant posts from Graham:
   http://www.ietf.org/mail-archive/web/uri-review/current/msg01408.html
   http://www.ietf.org/mail-archive/web/uri-review/current/msg01416.html
   http://www.ietf.org/mail-archive/web/uri-review/current/msg01424.html

...and you can look at the other, related messages.

I spoke with Pete Resnick, who suggested using something related to
CardDAV to handle this.  I've asked Cyrus whether there's anything we
can do in that regard, and I'm waiting for his response.  Pete is not
inclined to go against Graham's recommendation, and also is concerned
about the scope here.

At this point, I don't know what to do, so I'm taking it back to the
working group.  Alexey thinks grabbing a URN namespace is acceptable,
even if we have to hold our noses a bit.  Ned, what do you think?
Others?

Barry