Re: [webfinger] [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt
Dick Hardt <dick.hardt@gmail.com> Fri, 21 December 2012 23:19 UTC
Return-Path: <dick.hardt@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 E0CC421F8A40 for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 15:19:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 pD884aX713ch for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 15:19:09 -0800 (PST)
Received: from mail-pb0-f43.google.com (mail-pb0-f43.google.com [209.85.160.43]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA5E21F8997 for <webfinger@ietf.org>; Fri, 21 Dec 2012 15:19:09 -0800 (PST)
Received: by mail-pb0-f43.google.com with SMTP id um15so3002056pbc.16 for <webfinger@ietf.org>; Fri, 21 Dec 2012 15:19:08 -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:content-transfer-encoding:message-id:references:to:x-mailer; bh=AFBNBuTbtRPjnWXVWn6WlW8qVl5nuiOhtQIUu9F1jbU=; b=t+h+7bwmPKDKMf/A+fQGTaD1OS5ZJbKXO1M74r6Z4lZIPQnPxE0ci9CHbtPbRy82rq HUpk6Zyeo2nTQiPH9eid3CgpUdBOcGGkBA5w6kYMgN1MtscIO2bntkKqLkuME8sL7eTw FuE1dcvlM7Hie1XqoM38VSlqn/dxUuF47UZOJqyulutsyL7MgDd5XH/TWGoQpA4NiiQw YPTSek2Nr+G5wYajTyVm+pgunADemSIVsQS+Py5Po91rQDL2c6YaARUT5AmLeDMFziPY WvR3YpHgfSll+oHJZ0Z4ouPSdjgcZWe0izrf7O6ioAeA8awv57h/JGHRcV7bfnsjvwIP I6ug==
X-Received: by 10.66.89.42 with SMTP id bl10mr41276193pab.2.1356131948666; Fri, 21 Dec 2012 15:19:08 -0800 (PST)
Received: from [10.0.0.4] (c-24-5-69-173.hsd1.ca.comcast.net. [24.5.69.173]) by mx.google.com with ESMTPS id bh9sm8134411pab.12.2012.12.21.15.19.00 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 21 Dec 2012 15:19:04 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <065701cddfa1$fa73bc70$ef5b3550$@packetizer.com>
Date: Fri, 21 Dec 2012 15:18:59 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1612DB1-5F7D-42DF-8981-00CA8A66971F@gmail.com>
References: <20121221172032.28253.90788.idtracker@ietfa.amsl.com> <065701cddfa1$fa73bc70$ef5b3550$@packetizer.com>
To: webfinger@googlegroups.com
X-Mailer: Apple Mail (2.1499)
Cc: webfinger@ietf.org
Subject: Re: [webfinger] [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 23:19:10 -0000
Paul First off, thanks for all the effort in pulling this together -- it is much simpler and tighter than it was in the past. One aspect that jumped out at me as a client implementor is that I am not sure what URI am supposed to query when I have an email address for a user. In 3.1 acct: is used, but then later there are mailto: and http: URIs that seem equivalent. i.e.: 1) acct:bob@example.com is used in 3.1, 3.2 2) mailto:bob@example.com is used in 3.3 3) http://www.example.com/~bob/ in 3.1 As a mail client I can see that (3) may be a separate URI that has slightly different meaning that (1) or (2) As a server implementor, would I need to support both (1) and (2)? As a client, can I query either (1) or (2)? Is (2) only for email configuration per 3.3? Did I miss a reference somewhere that would clarify? -- Dick On Dec 21, 2012, at 9:38 AM, Paul E. Jones <paulej@packetizer.com> 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 >
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Tim Bray
- [webfinger] FW: [apps-discuss] I-D Action: draft-… Paul E. Jones
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Kingsley Idehen
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Tim Bray
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… John Bradley
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Kingsley Idehen
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Kingsley Idehen
- Re: [webfinger] [apps-discuss] I-D Action: draft-… Dick Hardt
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Melvin Carvalho
- Re: [webfinger] [apps-discuss] I-D Action: draft-… Paul E. Jones
- Re: [webfinger] [apps-discuss] I-D Action: draft-… Dick Hardt
- Re: [webfinger] [apps-discuss] I-D Action: draft-… Paul E. Jones
- Re: [webfinger] [apps-discuss] I-D Action: draft-… Dick Hardt
- Re: [webfinger] [apps-discuss] I-D Action: draft-… Paul E. Jones
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Melvin Carvalho
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Melvin Carvalho
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Tim Bray
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Kingsley Idehen
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Kingsley Idehen
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… Paul E. Jones
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… chris.dent
- Re: [webfinger] FW: [apps-discuss] I-D Action: dr… James M Snell