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

Bob Wyman <bob@wyman.us> Wed, 23 May 2012 15:06 UTC

Return-Path: <bobwyman@gmail.com>
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 0CC1521F8713 for <apps-discuss@ietfa.amsl.com>; Wed, 23 May 2012 08:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 3mmJlmrc2AFm for <apps-discuss@ietfa.amsl.com>; Wed, 23 May 2012 08:06:21 -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 154FE21F8703 for <apps-discuss@ietf.org>; Wed, 23 May 2012 08:06:21 -0700 (PDT)
Received: by yhq56 with SMTP id 56so7888636yhq.31 for <apps-discuss@ietf.org>; Wed, 23 May 2012 08:06:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=394oMSuCxC99uI70VYZJSm+3fbRWEeJ4kYmFBhypN8c=; b=zMVdz/yq88s5iOQHPIAh8td+nlwELRnvoAheZ0G5urhoxNB1MkOV5YQBHNhC6P44Hj KBPKqvau3kZCvnS/DdJIOp705qH4oujvvdsFtZcC9/yQOwl2YXoJ12pa8Dx4DPiAD3wu JQ9CdYNiNn8TEdKV9ixMc1Rv7FHN9YfSl4gdG+Tu69VMyyZ1zpFkKhIfxQL4b4mNyRxG jY6TSwupFT4jrpiI2XMtVY8jtd+JxNcTKTYtviZ+Yw4V03UFBrz5ahML/auqM8ldteXg 1S7mUF+HI2rhB+8fqbHkGD6b0o3lJWShnlKfyIuCncFQKO6iVgaVkExR9JKJMt+eyn2c SJBA==
MIME-Version: 1.0
Received: by 10.236.190.99 with SMTP id d63mr19735885yhn.125.1337785580607; Wed, 23 May 2012 08:06:20 -0700 (PDT)
Sender: bobwyman@gmail.com
Received: by 10.101.99.6 with HTTP; Wed, 23 May 2012 08:06:20 -0700 (PDT)
In-Reply-To: <f5baa0z16jt.fsf@calexico.inf.ed.ac.uk>
References: <9452079D1A51524AA5749AD23E00392812B6B6@exch-mbx901.corp.cloudmark.com> <4E1F6AAD24975D4BA5B1680429673943665131A7@TK5EX14MBXC284.redmond.corp.microsoft.com> <7BCF42BF-127F-478B-A922-1E84D087A0F3@ve7jtb.com> <f5baa0z16jt.fsf@calexico.inf.ed.ac.uk>
Date: Wed, 23 May 2012 11:06:20 -0400
X-Google-Sender-Auth: enAGCX0uCwTiF-OS1g7QWnYukUs
Message-ID: <CAA1s49VxqhjyE=0M9pKQ5hx-NfXtt2K6coEAPB=-WQonZj4rng@mail.gmail.com>
From: Bob Wyman <bob@wyman.us>
To: "Henry S. Thompson" <ht@inf.ed.ac.uk>
Content-Type: multipart/alternative; boundary="20cf305e25a55159d404c0b57a3a"
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
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: Wed, 23 May 2012 15:06:22 -0000

acct: is NOT "a relatively minor part of a larger project." acct:
identifies a fundamental class of resource on the network that we've
traditionally ignored due to the inappropriate assumption that there was a
binding between accounts and email addresses. However, as we increase the
richness of services available on the network, we see more and more that
such a binding is inappropriate. Not all services that offer accounts do or
should provide email support as well.

Would people be happier with acct: if there were other protocols that used
it? For instance, if we had an "Account Creation and Management Protocol"
that used acct:? (Such a thing and its utility would not be that hard to
imagine....) if so, then for goodness sake, let acct: be created now and
then we can be sure that someone will eventually submit the Internet Draft
to define the full-fledged acct: protocol. But, today, we only need this
one aspect of acct: to be defined. Let it be.

bob wyman

On Wed, May 23, 2012 at 7:27 AM, Henry S. Thompson <ht@inf.ed.ac.uk> wrote:

> John Bradley writes:
>
> > As another poster pointed out schemes have particular semantics and
> > trigger specific browser behaviours.  The scheme needs to answer
> > questions around expected browser behaviour.
>
> Precisely.  I have no detailed interest in webfinger as such, but new
> URI schemes are not something to be created casually.  We have
> guidelines for these things, in the form of RFC 4395 [1], which says,
> _inter alia_,
>
>  "The use and deployment of new URI schemes in the Internet
>   infrastructure is costly; . . . For these reasons, the unbounded
>   registration of new schemes is harmful.  New URI schemes SHOULD
>   have clear utility to the broad Internet community, beyond that
>   available with already registered URI schemes."
>
> Pushing through a new scheme because it's a relatively minor part of a
> larger project which people are keen to get finished doesn't seem like
> the best way to get the necessary careful review that a new scheme
> requires.
>
> ht
>
> [1] http://tools.ietf.org/html/rfc4395
> --
>       Henry S. Thompson, School of Informatics, University of Edinburgh
>      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
>                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
>                       URL: http://www.ltg.ed.ac.uk/~ht/
>  [mail from me _always_ has a .sig like this -- mail without it is forged
> spam]
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>