Re: [apps-discuss] Looking at Webfinger

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Thu, 05 July 2012 00:48 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 664E521F8539 for <apps-discuss@ietfa.amsl.com>; Wed, 4 Jul 2012 17:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.546
X-Spam-Level:
X-Spam-Status: No, score=-99.546 tagged_above=-999 required=5 tests=[AWL=0.244, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, 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 gb6x+Mt6jAG4 for <apps-discuss@ietfa.amsl.com>; Wed, 4 Jul 2012 17:48:58 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id D3C6121F8534 for <apps-discuss@ietf.org>; Wed, 4 Jul 2012 17:48:56 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q650mvfW012251 for <apps-discuss@ietf.org>; Thu, 5 Jul 2012 09:48:58 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 141e_776b_3432e894_c63b_11e1_a781_001d096c5782; Thu, 05 Jul 2012 09:48:57 +0900
Received: from [IPv6:::1] ([133.2.210.1]:39372) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15DCAB5> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Thu, 5 Jul 2012 09:49:01 +0900
Message-ID: <4FF4E474.6080608@it.aoyama.ac.jp>
Date: Thu, 05 Jul 2012 09:48:52 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Melvin Carvalho <melvincarvalho@gmail.com>
References: <F80C8C9C-7AB8-4B7E-BFD2-4D69499D21A1@mnot.net> <4E1F6AAD24975D4BA5B168042967394366574F93@TK5EX14MBXC283.redmond.corp.microsoft.com> <EEF96DE8-6BEC-40D0-BC77-932E1B8591F9@mnot.net> <1A87B9DE-ECEC-4F07-8734-131D4BB564EB@ve7jtb.com> <CAC4RtVAatJPnOMw3VZZhTxHuG5PdzcoNPMeqH-mhfsA0i47JLg@mail.gmail.com> <911C1091-6D88-4937-BF4C-0FCB264B6AEF@ve7jtb.com> <CAL0qLwZP++ggNOadubb4OsuNw+zqeinQ2V8ACnVu8T0zg05m9w@mail.gmail.com> <CAKaEYhKiL0cuSXEg5z2jNwfzkwF-q1DOa-4txGP0K3xiFbuRDg@mail.gmail.com>
In-Reply-To: <CAKaEYhKiL0cuSXEg5z2jNwfzkwF-q1DOa-4txGP0K3xiFbuRDg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, Barry Leiba <barryleiba@computer.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Looking at Webfinger
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: Thu, 05 Jul 2012 00:48:59 -0000

On 2012/07/05 4:05, Melvin Carvalho wrote:

> One question I've been thinking about.  Does the acct: scheme also apply to
> subdomains too, or just the parent domain, or only where an email exists?
>
> For example, are the following four, equivalent ways to describe an account?
>
> acct:bob@facebook.com
> acct:bob@www.facebook.com
> acct:bob@graph.facebook.com
> https://graph.facebook.com/bob

In general, no. If you know a lot about facebook, and you trust them 
that they won't change things, you might be able to infer that the 
account or person behind these URIs is one and the same, but that would 
be at your own risk, and may depend on what exactly you are trying to do.

Regards,   Martin.