Re: [apps-discuss] FW: I-D Action: draft-jones-appsawg-webfinger-06.txt
elf Pavlik <perpetual-tripper@wwelves.org> Mon, 18 June 2012 16:05 UTC
Return-Path: <perpetual-tripper@wwelves.org>
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 CDD5A21F86DF for <apps-discuss@ietfa.amsl.com>; Mon, 18 Jun 2012 09:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wagsciBQcPYS for <apps-discuss@ietfa.amsl.com>; Mon, 18 Jun 2012 09:05:06 -0700 (PDT)
Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by ietfa.amsl.com (Postfix) with ESMTP id B153221F86F7 for <apps-discuss@ietf.org>; Mon, 18 Jun 2012 09:05:05 -0700 (PDT)
X-Originating-IP: 217.70.178.133
Received: from mfilter3-d.gandi.net (mfilter3-d.gandi.net [217.70.178.133]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id A9CA5172090; Mon, 18 Jun 2012 18:04:51 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter3-d.gandi.net
Received: from relay4-d.mail.gandi.net ([217.70.183.196]) by mfilter3-d.gandi.net (mfilter3-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id QFe7Y3Z-fy2P; Mon, 18 Jun 2012 18:04:50 +0200 (CEST)
X-Originating-IP: 217.11.53.243
Received: from localhost (243.53.11.217.in-addr.arpa.manitu.net [217.11.53.243]) (Authenticated sender: perpetual-tripper@wwelves.org) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 20A3E1720A5; Mon, 18 Jun 2012 18:04:49 +0200 (CEST)
Content-Type: text/plain; charset="UTF-8"
From: elf Pavlik <perpetual-tripper@wwelves.org>
To: "Paul E. Jones" <paulej@packetizer.com>
In-reply-to: <01e301cd4d64$f948d260$ebda7720$@packetizer.com>
References: <20120618050925.30416.34929.idtracker@ietfa.amsl.com> <016a01cd4d13$3b1b1380$b1513a80$@packetizer.com> <1340005251-sup-8958@heahdk.net> <01e301cd4d64$f948d260$ebda7720$@packetizer.com>
Date: Mon, 18 Jun 2012 16:04:48 +0000
Message-Id: <1340035392-sup-1090@heahdk.net>
User-Agent: Sup/0.12.1
Content-Transfer-Encoding: quoted-printable
Cc: apps-discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] FW: I-D Action: draft-jones-appsawg-webfinger-06.txt
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: Mon, 18 Jun 2012 16:05:07 -0000
Hi Paul, Excerpts from Paul E. Jones's message of 2012-06-18 15:13:53 +0000: > Elf, > > The intent is that the "acct" link relation would be a means of allowing one account to incorporate link relations from a different account URI. So, let's suppose I have an account acct:paulej@packetizer.com and I also have an account that holds pictures on flickr.com. Within my packetizer.com account, I could include a reference to my flickr.com account, like this: > <Link rel="acct" href="acct:paulej@flickr.com"/> > > I could include the particular link relations that Flickr might advertise from within my packetizer.com account. However, that requires me to ensure I keep those references up-to-date. A reference like the above helps simplify my life. > > I added two new paragraphs following the first paragraph in that section to make it clearer in the -07 draft: > > === > 7.1. Purpose for the “acct” Link Relation > > Users of some services might have an “acct” URI that looks significantly different from his or her email address, perhaps using an entirely different domain name. It is also possible for a user have multiple accounts that a user wants to advertise and that a WebFinger client may want to query. To address both of these needs, this specification defines the “acct” link relation. > > The "acct" link relation allows a WebFinger server to reference one or more other user account URIs from within a user account. The "acct" link relation is intended to allow a client to incorporate additional link relations by reference to produce a complete set of link relations for a user. Any newly discovered link relations found by querying the referenced account should be merged into the resource descriptor document at the point where the "acct" link relation was inserted. > > Note that the "acct" link relation does not replace the use of standard HTTP 3xx response codes to indicate the new temporary or permanent location of a user account. If a user account is moved to a different location, then a 3xx response code SHOULD be used. > > ... > === > > Do those additional paragraphs help? That helped me with clarifying it, thank you! :) ~ elf Pavlik ~
- [apps-discuss] I-D Action: draft-jones-appsawg-we… internet-drafts
- [apps-discuss] FW: I-D Action: draft-jones-appsaw… Paul E. Jones
- Re: [apps-discuss] FW: I-D Action: draft-jones-ap… Bjoern Hoehrmann
- Re: [apps-discuss] FW: I-D Action: draft-jones-ap… elf Pavlik
- Re: [apps-discuss] FW: I-D Action: draft-jones-ap… Paul E. Jones
- Re: [apps-discuss] FW: I-D Action: draft-jones-ap… elf Pavlik