Re: [apps-discuss] The acct: scheme question

Peter Saint-Andre <stpeter@stpeter.im> Sun, 01 July 2012 03:09 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D473121F855F for <apps-discuss@ietfa.amsl.com>; Sat, 30 Jun 2012 20:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.01
X-Spam-Level:
X-Spam-Status: No, score=-102.01 tagged_above=-999 required=5 tests=[AWL=-0.461, BAYES_00=-2.599, SARE_TOWRITE=1.05, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dzNS5DPS4G3r for <apps-discuss@ietfa.amsl.com>; Sat, 30 Jun 2012 20:09:04 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 24B2D21F84B3 for <apps-discuss@ietf.org>; Sat, 30 Jun 2012 20:09:04 -0700 (PDT)
Received: from [192.168.0.9] (unknown [216.17.179.227]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A36074005A; Sat, 30 Jun 2012 21:27:12 -0600 (MDT)
Message-ID: <4FEFBF51.5000905@stpeter.im>
Date: Sat, 30 Jun 2012 21:09:05 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Graham Klyne <GK@ninebynine.org>
References: <9452079D1A51524AA5749AD23E00392812B6B6@exch-mbx901.corp.cloudmark.com> <CAKaEYhKpeayOw4sN4=NYaoXKJQ2e5P+pP8SqJqnt-=Barb=WqA@mail.gmail.com> <4E1F6AAD24975D4BA5B168042967394366568E4F@TK5EX14MBXC283.redmond.corp.microsoft.com> <1340723227.60315.YahooMailNeo@web31801.mail.mud.yahoo.com> <4E1F6AAD24975D4BA5B168042967394366568FF8@TK5EX14MBXC283.redmond.corp.microsoft.com> <043201cd54a5$79f2e170$6dd8a450$@packetizer.com> <CAKaEYhL0NS=RZXTdyOMBM_q15P7D1KZ9kgUyMYYB06kA9f0w8Q@mail.gmail.com> <4FEC3B4F.80607@ninebynine.org> <4FEC8BF0.6070605@stpeter.im>
In-Reply-To: <4FEC8BF0.6070605@stpeter.im>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: apps-discuss@ietf.org, "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: [apps-discuss] The acct: scheme question
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jul 2012 03:09:05 -0000

On 6/28/12 10:53 AM, Peter Saint-Andre wrote:
> On 6/28/12 5:09 AM, Graham Klyne wrote:
>> On 28/06/2012 08:28, Melvin Carvalho wrote:
>>> Should acct: be rejected, we can simply use mailto: as per SWD. 
>>> Similarly
>>> you could simply use ?acct=user@host as has been suggested.
>>
>> Since my comments with reviewer hat on have been cited, I feel I should
>> summarize my personal feelings about the specification of the acct: scheme.
>>
>> *Reviewer hat OFF*
>>
>> Roughly, I think the acct: scheme does provide a useful, possibly minor,
>> purpose that is not served by other URI schemes, and as such it has
>> reasonable claim to meet the bar for registering a new scheme.  But I
>> think the description of the acct: scheme in the WebFinger document does
>> a poor job of explaining this; i.e. I think there is a document quality
>> issue here around the acct: scheme registration/specification.
>>
>> I've had private exchanges with one of the document editors, but I don't
>> think my suggestions have been reflected in the current draft.  In
>> summary, what I think is not as clear as it should be in the scheme
>> registration includes:
>> * what does an acct URI identify
>> * how are acct URIs allocated; what's the assignment delegation structure?
>> * how should an acct: URI be dereferenced?  (e.g. if one were used as a
>> link in a web page, how should it be handled?).
>>
>> I suspect that most of this information can be inferred if one has a
>> detailed knowledge of WebFinger protocol, but for an average Joe web
>> developer I don't think that's really helpful.
>>
>> I don't think this is a sufficiently important issue for me to engage
>> more actively with the discussion.
> 
> Graham, I think you're right about the fact that these matters are
> underspecified. I hereby offer to propose some text, and will do that in
> the next few days.

I went beyond proposing text and decided to write a standalone I-D:

http://datatracker.ietf.org/doc/draft-saintandre-acct-uri/

Graham, I think that text answers the questions you posed, hopefully in
an accurate way.

Feedback is welcome.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/