Re: [webfinger] Possibly speeding up the RFC process

"Paul E. Jones" <paulej@packetizer.com> Thu, 20 December 2012 18:10 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: webfinger@ietfa.amsl.com
Delivered-To: webfinger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3AEF21F8A99 for <webfinger@ietfa.amsl.com>; Thu, 20 Dec 2012 10:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level:
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599]
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 y-7akhpYbPni for <webfinger@ietfa.amsl.com>; Thu, 20 Dec 2012 10:10:54 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 72B4A21F8419 for <webfinger@ietf.org>; Thu, 20 Dec 2012 10:10:53 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id qBKIAj0V004414 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Dec 2012 13:10:45 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1356027045; bh=TSA9lshMS0uRnym2gVeaPYhcIw9w+Mx5+M2SDry4MkI=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=Y3T3tDUCDbyhIBmZZ7/9pujE/a15tMbmYdkpbKgdxewYe+pgI9iTMNnIIDb0QQN0N fW/v5QigUrvR4+ru/Bm2i00ga3NGqJRJclHGCYs1Ir7PG/jWZDXdE0zmagV4N8kvlm ZVbUJqN+oFM+yaXmcRSKMaBDSeg7KTvWVYy7NwAk=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'Goix Laurent Walter' <laurentwalter.goix@telecomitalia.it>
References: <CAKaEYhJRxVZHMxvSiAupMiW=9KonKNssaFRmC+HwbnZ7y+toVQ@mail.gmail.com> <004201cddbcb$3a003ab0$ae00b010$@packetizer.com> <CAKaEYhLOKpBSh3LT5OHb5MKGiV_fgA0RK-CT5thCUPg+n-6ATQ@mail.gmail.com> <008a01cddbd4$17834140$4689c3c0$@packetizer.com> <CAKaEYhL_TuEwkMzXtkMAVr6tdwkaoLwnCsVRd6n_yT+rxPGxaQ@mail.gmail.com> <00c801cddbda$72cc7d90$586578b0$@packetizer.com> <CAJL4Wta2i_gtgwC_RtyRZRuKa-pH64xDC+BzQpbi1ZyWLsGt6g@mail.gmail.com> <02a501cddc95$6a740a80$3f5c1f80$@packetizer.com> <CAJL4WtbFbx-CvDZ=5GkX=mCM6HDUsg=DEFW3PoXPU1miBdfSSg@mail.gmail.com> <A09A9E0A4B9C654E8672D1DC003633AE53A5DDCD08@GRFMBX704BA020.griffon.local> <CAJL4WtYDkrFyoxK+6aPQH6xoPfw2pWWEekvOnwOVnAFymRR-Bg@mail.gmail.com> <047601cdded6$594c9090$0be5b1b0$@packetizer.com> <0C783CC2-F8C5-4520-9E9A-061B373A7CFA@telecomitalia.it> <04b001cddedb$5d36d0d0$17a47270$@packetizer.com> <D98E8200-433B-4B72-AE52-6DC831B2AFA3@telecomitalia.it>
In-Reply-To: <D98E8200-433B-4B72-AE52-6DC831B2AFA3@telecomitalia.it>
Date: Thu, 20 Dec 2012 13:10:53 -0500
Message-ID: <04d401cddedd$5a15a8c0$0e40fa40$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFXXsdYIDFkRYF/cKUyX9w1YoKrkAICVkdlAm5m3hAB68knVQGk1LrlAZwlmmgCS5qz2AKIYVhrAUWuRZABCyCqMQHH/q7wAodvYjICqq12zwNxb+Q3AdUTiK+YJuTBwA==
Content-Language: en-us
Cc: webfinger@ietf.org, 'Nick Jennings' <nick@silverbucket.net>, webfinger@googlegroups.com, 'Melvin Carvalho' <melvincarvalho@gmail.com>
Subject: Re: [webfinger] Possibly speeding up the RFC process
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <webfinger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webfinger>, <mailto:webfinger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webfinger>
List-Post: <mailto:webfinger@ietf.org>
List-Help: <mailto:webfinger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webfinger>, <mailto:webfinger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 18:10:55 -0000

Walter,

> > So, as a way forward, we have a couple of options:
> >    1) Allow the assumption to be made that the account for
> >       the above address is "acct:"
> >    2) Don't allow the assumption and require a query to
> >       "mailto" and discover the "acct" URI
> 
> I am not sure we have to standardize that specific behaviour. It would
> be impossible to do for all use cases with a normative language. That
> said it could be clearly mentioned in the examples to guide implementors.
> My preferred option for the example would be with mailto: (optionally
> mentioning that the answer could provide a proof of existence of the
> equivalent acct: uri through an acct rel.

My preference is that we leave the examples we have in the text as they are and encourage use of the "acct" URI if a query relates to a user's account.  Concrete recommendations might also come about through a little more real-world experience.  I suspect the first major service provider to support WF will dictate how it works.

Paul