Re: [Uri-review] Request for review of "ab:" URI scheme

Barry Leiba <barryleiba@computer.org> Thu, 28 April 2011 20:25 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9ACE069A for <uri-review@ietfa.amsl.com>; Thu, 28 Apr 2011 13:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.058
X-Spam-Level:
X-Spam-Status: No, score=-103.058 tagged_above=-999 required=5 tests=[AWL=-0.081, 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 ULUiHl1tJgQg for <uri-review@ietfa.amsl.com>; Thu, 28 Apr 2011 13:25:18 -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 11758E0679 for <uri-review@ietf.org>; Thu, 28 Apr 2011 13:25:17 -0700 (PDT)
Received: by ywi6 with SMTP id 6so1350550ywi.31 for <uri-review@ietf.org>; Thu, 28 Apr 2011 13:25:17 -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:cc:content-type :content-transfer-encoding; bh=phM7EClj+9MfnIJtxUgjKFVomV5cI8aAH4JVK7LrDnM=; b=Zc1YTMXoInnnJa4XUeRtqn62gBDZkmPClLq0ANXfYfqtepk1oLdHy0t4ufzJQne77t 79lLfxgZs+ZCU1PJDocXILvSCQBRQgwl+4WwoJigeC7sRaBzFith1CYQxxN/UWz4sVjM YETP3Ur7xfNPwKrpqH15K3iiOn4S/QZtUnb+A=
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:cc:content-type :content-transfer-encoding; b=IOrSm8GRtQLOxOlEJPpYtSHHZd1LBWfsIqLmr9DcaZpAhmrX+6Dn+4LaShMo0UM3ub M6nPAZnuf17cqMDIz+bxem0EFKHmomsfTs4HDXznAQYxfLRLiA4trdAE7jUtnuwMfBMa LtWwT0DinNQPJuaMbyW7T2PpesBLx4PEA56hM=
MIME-Version: 1.0
Received: by 10.236.110.202 with SMTP id u50mr4809081yhg.464.1304022317509; Thu, 28 Apr 2011 13:25:17 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.111.1 with HTTP; Thu, 28 Apr 2011 13:25:17 -0700 (PDT)
In-Reply-To: <4DB70FFC.2000508@ninebynine.org>
References: <BANLkTim8eWcWwKfyERghK2tuSP1rK0SdsA@mail.gmail.com> <4DB1D685.4090706@ninebynine.org> <4DB5D6EE.4080503@isode.com> <4DB6B9B6.8040306@ninebynine.org> <BANLkTinMm0OyBqUNTU_-Er_4w1TK7kW-Eg@mail.gmail.com> <4DB6D2C8.4090806@ninebynine.org> <BANLkTimBP3zHOEn4F_S8-LhqK6+9AkXm6Q@mail.gmail.com> <0E82FA0E66DC3ABE22989712@17.101.34.182> <4DB70FFC.2000508@ninebynine.org>
Date: Thu, 28 Apr 2011 16:25:17 -0400
X-Google-Sender-Auth: 8msldBkJ6dkEKDSNqfbdX7QvqXk
Message-ID: <BANLkTim9cLa2=y1EthczaVPGnHOx5h581Q@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Graham Klyne <GK-lists@ninebynine.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Cyrus Daboo <cyrus@daboo.name>, uri-review@ietf.org, draft-ietf-sieve-external-lists.all@tools.ietf.org
Subject: Re: [Uri-review] Request for review of "ab:" URI scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 20:25:19 -0000

> So, reinvention aside, I think what Barry sketches above is prima facie a
> reasonable approach.  If there's any real advantage to an addrbook: scheme,
> I think it is in part that it can abstract away from a particular protocol
> or mechanism and leave just the essential capabilities exposed.

Graham, where are we on this?  Should we proceed with the Sieve
document as it is, with the addrbook URI?  Or do we still need more
discussion?  We're otherwise ready to send the document to the IESG.

Barry