Re: [webfinger] Question about device info discovery example.
"Paul E. Jones" <paulej@packetizer.com> Sat, 22 December 2012 04:57 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 B7D1421F8920 for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 20:57:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level:
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 NMIrix-YMi9Z for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 20:57:20 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED2621F882D for <webfinger@ietf.org>; Fri, 21 Dec 2012 20:57:20 -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 qBM4vGHu002994 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Dec 2012 23:57:16 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1356152237; bh=ZtEpJXECfp5zXYd9+enZaJTP/4h7cpB6k2eO+Yt8sls=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=oadiKDUEF4dCucEadQonLwMYb2/ACBzBI8ljUErWkFZvPc58vEZ0D7tGFxn5FIvX9 +5gh0f6UkksocSmT4oEPTx2JUm+qRwDMsawjDbMfzYZqRbpNb+hshKpkXBVhoVPHyh gqA2AhPxZfTvrptd/eSD0MXmuwqYLKO7qE/WE44Q=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'nov matake' <matake@gmail.com>, webfinger@ietf.org
References: <D6A97D9D-9431-4C0F-9428-397677C179D1@gmail.com>
In-Reply-To: <D6A97D9D-9431-4C0F-9428-397677C179D1@gmail.com>
Date: Fri, 21 Dec 2012 23:57:19 -0500
Message-ID: <075b01cde000$d283d790$778b86b0$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_075C_01CDDFD6.E9AE6BD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIeIapXe7gOJ5OOW00neyp/e43xx5eDvK1g
Content-Language: en-us
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 04:57:21 -0000
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 being example.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 <http://example.com/> " but the host of discovery endpoint is "example.com <http://example.com/> ", not "p1.example.com <http://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
- [webfinger] Question about device info discovery … nov matake
- Re: [webfinger] Question about device info discov… Paul E. Jones
- Re: [webfinger] Question about device info discov… nov matake
- Re: [webfinger] Question about device info discov… Paul E. Jones
- Re: [webfinger] Question about device info discov… Paul E. Jones
- Re: [webfinger] Question about device info discov… nov matake
- Re: [webfinger] Question about device info discov… Paul E. Jones
- Re: [webfinger] Question about device info discov… nov matake