Re: [webfinger] FW: [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt

Kingsley Idehen <kidehen@openlinksw.com> Fri, 21 December 2012 21:09 UTC

Return-Path: <kidehen@openlinksw.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 78CD621F8472 for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 13:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.17
X-Spam-Level:
X-Spam-Status: No, score=-1.17 tagged_above=-999 required=5 tests=[AWL=1.429, 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 M8T46lQJc81a for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 13:09:13 -0800 (PST)
Received: from mail.openlinksw.com (mail.openlinksw.com [63.119.36.38]) by ietfa.amsl.com (Postfix) with ESMTP id 7FED821F845D for <webfinger@ietf.org>; Fri, 21 Dec 2012 13:09:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=openlinksw.com; s=x; h=Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=Kdv3D9KA9xoL9uqmucXNx68USI6uFjZKMidgHdYfJrI=; b=A7Ous29u5ThlPq8m0o8f0ZTN0qU4USxYmWK9n55NlybzabRTtZRfY27mBxVwTqqqrvBuAiKM45oMMFzHnqBNqzV1LPedYSc5czLmMpc3qYqZCjGX/2fCm+trCxGFR92B;
Received: from kidehen.vpn ([10.100.2.3] helo=Macintosh-96.local) by mail.openlinksw.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.74) (envelope-from <kidehen@openlinksw.com>) id 1Tm9q5-0001Yd-GN; Fri, 21 Dec 2012 16:09:05 -0500
Message-ID: <50D4CFEF.9030701@openlinksw.com>
Date: Fri, 21 Dec 2012 16:09:03 -0500
From: Kingsley Idehen <kidehen@openlinksw.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Paul E. Jones" <paulej@packetizer.com>
References: <20121221172032.28253.90788.idtracker@ietfa.amsl.com> <065701cddfa1$fa73bc70$ef5b3550$@packetizer.com>
In-Reply-To: <065701cddfa1$fa73bc70$ef5b3550$@packetizer.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms070705050205080202060008"
Cc: webfinger@ietf.org, webfinger@googlegroups.com
Subject: Re: [webfinger] FW: [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt
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: Fri, 21 Dec 2012 21:09:14 -0000

On 12/21/12 12:38 PM, Paul E. Jones wrote:
> Folks,
>
> I just posted a revised version of the WebFinger text.  Highlights include:
>   * Change all queries to require HTTPS only
>   * Forbid server redirection to HTTP URIs
>   * Merged the "Introduction" and "Overview" sections
>   * Moved some references to the informative references section
>   * Removed instructions for the server to return specific
>     status codes (Tim successfully argued it was not needed)
>      * Retained one statement, though, in section 4.2 that
>        requires a server to return a 400.  However, the
>        text was changed to refer to behavior in RFC 2616.
>        Same end result, though.
>   * Moved section the "rel" parameter section before the
>     JRD section.
>   * Made edits to the JRD section as discussed on the list
>   * Various editorial changes
>
> Please have a look at this text and suggest any changes we should make.
>
> Paul
>
>> -----Original Message-----
>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>> bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
>> Sent: Friday, December 21, 2012 12:21 PM
>> To: i-d-announce@ietf.org
>> Cc: apps-discuss@ietf.org
>> Subject: [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>   This draft is a work item of the Applications Area Working Group
>> Working Group of the IETF.
>>
>> 	Title           : WebFinger
>> 	Author(s)       : Paul E. Jones
>>                            Gonzalo Salgueiro
>>                            Joseph Smarr
>> 	Filename        : draft-ietf-appsawg-webfinger-08.txt
>> 	Pages           : 20
>> 	Date            : 2012-12-21
>>
>> Abstract:
>>     This specification defines the WebFinger protocol, which can be used
>>     to discover information about people or other entities on the
>>     Internet using standard HTTP methods.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-appsawg-webfinger
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-08
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-webfinger-08
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
> _______________________________________________
> webfinger mailing list
> webfinger@ietf.org
> https://www.ietf.org/mailman/listinfo/webfinger
>
Paul,

Could this:

  WebFinger is used to discover information about people or other
    entities on the Internet that are identified by a URI [6] or IRI [7]
    using standard Hypertext Transfer Protocol (HTTP) [2] methods over a
    secure transport [14].

become:

  WebFinger is used to discover information about people or other
    entities on the Internet that are *denoted* by a URI [6] or IRI [7]. 
Actual information retrieval uses
    standard Hypertext Transfer Protocol (HTTP) [2] methods over a
    secure transport [14].

-- 

Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen