Re: [webfinger] Question about device info discovery example.

nov matake <matake@gmail.com> Sat, 22 December 2012 05:10 UTC

Return-Path: <matake@gmail.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 5F22121E8042 for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 21:10:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 A7-cLXI2e77K for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 21:10:30 -0800 (PST)
Received: from mail-da0-f53.google.com (mail-da0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id 91B5121F84C9 for <webfinger@ietf.org>; Fri, 21 Dec 2012 21:10:30 -0800 (PST)
Received: by mail-da0-f53.google.com with SMTP id x6so2387165dac.12 for <webfinger@ietf.org>; Fri, 21 Dec 2012 21:10:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:message-id:references:to:x-mailer; bh=wyqmSS5uT+3jLYz8t6TqDBNcgqYJmkwTSnxQAbIi8kQ=; b=RBi16VdXC7mL/tOZW9q+9tCfXJg3bDxNH0KtajyA3Jh0dWyuyuNE/JOQn5SJ2hhfln 9AS9WyHHnWwNYJzAqbmp310va2+jJuqDBEvuUf2GQdrJc/FFIeNRFl3K0mqIUqHMeeAg SA5x4+9B2ZMlInBxrt6IFqdNH9ItzXQjwzAaahRHiB5a1RrAzOFHnV8fAHPDhmAaDbyv eXhqHP5eATwOCPHlPraQ1dgV5S0fIawODteg3sihPLUVdLO2Hlg7eIT0Z+9+6blui9wP TxlziCt0psgkeeaXPiB1nuEpsUK9mEnDaaCDE6FKef48u8mmTh77NfCgOUPTBE+T8MZB jXyw==
X-Received: by 10.66.82.35 with SMTP id f3mr42743346pay.49.1356153030283; Fri, 21 Dec 2012 21:10:30 -0800 (PST)
Received: from [192.168.1.6] (z195031.dynamic.ppp.asahi-net.or.jp. [110.4.195.31]) by mx.google.com with ESMTPS id d9sm8609226paw.33.2012.12.21.21.10.26 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 21 Dec 2012 21:10:28 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B6AAC6F1-B7A0-4DCE-83AC-62E898436AB7"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: nov matake <matake@gmail.com>
In-Reply-To: <075b01cde000$d283d790$778b86b0$@packetizer.com>
Date: Sat, 22 Dec 2012 14:10:27 +0900
Message-Id: <1B7C31D3-E41E-4DF2-910F-AC43340C62D6@gmail.com>
References: <D6A97D9D-9431-4C0F-9428-397677C179D1@gmail.com> <075b01cde000$d283d790$778b86b0$@packetizer.com>
To: "Paul E. Jones" <paulej@packetizer.com>
X-Mailer: Apple Mail (2.1499)
Cc: webfinger@ietf.org
Subject: Re: [webfinger] Question about device info discovery example.
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: Sat, 22 Dec 2012 05:10:36 -0000

OK,

Then basically webfinger clients MUST use the host of resource parameter (at least when using acct, mailto, http and https schema),
but extension spec MAY define another rule and in that case, client MUST follow the extension's rule.

Is it right?

Or webfinger itself doesn't specify anything for host usage?
(It just define path "/.well-known/webfinger" and schema "https", but not host?)

On 2012/12/22, at 13:57, Paul E. Jones <paulej@packetizer.com> wrote:

> Nov,
>  
> Keep in mind that this is an entirely fictional example.  There isn’t even a URI scheme called “device”.
>  
> The answer to your question would come from a document (if it existed, but does not) that describes the “device” URI and how to use it within the context of WebFinger.
>  
> My thinking when I wrote this is that there are named devices on the network and one would query the parent domain to learn about the device.  The parent in this case beingexample.com.  It might be that there is a designated host that serves as the device info server called “devices.example.com” to which all queries are directed.  In any case, this is completely unspecified and the example is there only to illustrate the range of use for WebFinger.  It should not be viewed in any way as proper usage, though.
>  
> Paul
>  
> From: webfinger-bounces@ietf.org [mailto:webfinger-bounces@ietf.org] On Behalf Of nov matake
> Sent: Friday, December 21, 2012 11:40 PM
> To: webfinger@ietf.org
> Subject: [webfinger] Question about device info discovery example.
>  
> Hi all,
> 
> I'm new to this ML.
> 
> I'm writing a ruby webfinger library.
> https://rubygems.org/gems/webfinger
> 
> After reading usecases in section 3, I have a question.
> 
> In the device info discovery example in section 3.4, resource is "device:p1.example.com" but the host of discovery endpoint is "example.com", not "p1.example.com".
> Is there any reason why these hosts are different?
> How did the client decide the host of the discovery endpoint from resource URI?
> 
> Thanks
> 
> Nov Matake