Re: [webfinger] Looking for JRDs

Tim Bray <tbray@textuality.com> Mon, 22 July 2013 18:37 UTC

Return-Path: <tbray@textuality.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 4DED821F8717 for <webfinger@ietfa.amsl.com>; Mon, 22 Jul 2013 11:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 KsP1KjweTPr8 for <webfinger@ietfa.amsl.com>; Mon, 22 Jul 2013 11:37:07 -0700 (PDT)
Received: from mail-ve0-f170.google.com (mail-ve0-f170.google.com [209.85.128.170]) by ietfa.amsl.com (Postfix) with ESMTP id C8B9911E80D2 for <webfinger@ietf.org>; Mon, 22 Jul 2013 11:37:04 -0700 (PDT)
Received: by mail-ve0-f170.google.com with SMTP id 14so5350834vea.15 for <webfinger@ietf.org>; Mon, 22 Jul 2013 11:37:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=KlB9HF6a9a07YwOGDer8UMH6IhdSGnnl5WH/uNR+lvg=; b=JVrh1LOMtB7e/bhAqSqFfW1kNibA2WvMfqZ6Xk4esGX2pX0H0Z75Sm6tMc4P65LrNQ eiKhhskHfRWJ0SPx5ChTB/lBawk84m4ialCVsYd9jTVuzORQ2XP7+I9LKWfyTljUn5KY VUXF+HGzxoz1pJmCLEjU561mFSkslarrjPibpj2waKjZyX2LQsQtLX/iouIZuQHpAFGu bWjhy2HntbX/pXlS0WQqB67Xh64UUNNzNR4tbZwW3fWKALZLugNhpuy3F16xoudhsJzm dO2klVTZJSeCYvZRSolXO8/qeggC6nPkk06uUAqrBnArrhsFxacgnbr+MIrLFljZ5Vge eXfQ==
MIME-Version: 1.0
X-Received: by 10.221.36.4 with SMTP id sy4mr9886499vcb.11.1374518224109; Mon, 22 Jul 2013 11:37:04 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Mon, 22 Jul 2013 11:37:04 -0700 (PDT)
X-Originating-IP: [96.49.81.176]
In-Reply-To: <03b801ce8708$cd5a2c10$680e8430$@packetizer.com>
References: <CAHBU6ivuHwToVHEyDuU3AKnd-nD-5ee20is_8U+fOkA1uszbzA@mail.gmail.com> <00d301ce80ff$fffd76e0$fff864a0$@packetizer.com> <CAHBU6itqxCfAgQSVOMKhbcBLe4afNW7QF5C4tMsHC1EKGBt+Gg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436B6F7E7A@TK5EX14MBXC284.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B16804296739436B6F81E7@TK5EX14MBXC284.redmond.corp.microsoft.com> <1374516883.73070.YahooMailNeo@web184401.mail.bf1.yahoo.com> <03b801ce8708$cd5a2c10$680e8430$@packetizer.com>
Date: Mon, 22 Jul 2013 11:37:04 -0700
Message-ID: <CAHBU6ivKr14qwfeof=g6eSw+2GgO-6=dHouobLoPZ7sVNAdLdA@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: multipart/alternative; boundary=001a11339f387c55a104e21df6ab
X-Gm-Message-State: ALoCoQmJfWJSl/mWxPJdXIkGaMQIxhNM/++zwGlIdHJIoyd+b/bdxy9CJ+uMSm9e551fwX/+rC2S
Cc: "webfinger@ietf.org" <webfinger@ietf.org>, openid-connect-interop@googlegroups.com, Edmund Jay <ejay@mgi1.com>
Subject: Re: [webfinger] Looking for JRDs
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: Mon, 22 Jul 2013 18:37:13 -0000

Hm?  You mean the HTTP Expires header?  Why should recipients act in a
non-HTTP-standard way?  I don’t think we’re allowed to rewrite HTTP rules.
-T


On Mon, Jul 22, 2013 at 11:25 AM, Paul E. Jones <paulej@packetizer.com>wrote;wrote:

> Edmund,****
>
> ** **
>
> Note that we removed the “expires” header from the current WebFinger
> spec.  It’s OK to have it there, but it should be ignored by recipients.**
> **
>
> ** **
>
> Paul****
>
> ** **
>
> *From:* Edmund Jay [mailto:ejay@mgi1.com]
> *Sent:* Monday, July 22, 2013 2:15 PM
> *To:* openid-connect-interop@googlegroups.com; Tim Bray; Paul E. Jones
> *Cc:* webfinger@ietf.org
>
> *Subject:* Re: [webfinger] Looking for JRDs****
>
> ** **
>
> The following can be used : ****
>
>  ****
>
> alice@connect.openid4.us or****
>
> bob@connect.openid4.us****
>
> ** **
>
> -- Edmund****
> ------------------------------
>
> *From:* Mike Jones <Michael.Jones@microsoft.com>
> *To:* "openid-connect-interop@googlegroups.com" <
> openid-connect-interop@googlegroups.com>gt;; Tim Bray <tbray@textuality.com>om>;
> Paul E. Jones <paulej@packetizer.com>
> *Cc:* "webfinger@ietf.org" <webfinger@ietf.org>
> *Sent:* Saturday, July 20, 2013 10:51 PM
> *Subject:* RE: [webfinger] Looking for JRDs****
>
> ** **
>
> Could those of you with OpenID OPs that support discovery please post
> specific identifiers using e-mail address syntax that Tim could use for
> testing e-mail based discovery using WebFinger?****
>
>  ****
>
>                                                             Thanks all,***
> *
>
>                                                             -- Mike****
>
>  ****
>
> *From:* openid-connect-interop@googlegroups.com [
> mailto:openid-connect-interop@googlegroups.com<openid-connect-interop@googlegroups.com>]
> *On Behalf Of *Mike Jones
> *Sent:* Saturday, July 20, 2013 4:34 PM
> *To:* Tim Bray; Paul E. Jones
> *Cc:* webfinger@ietf.org; openid-connect-interop@googlegroups.com
> *Subject:* RE: [webfinger] Looking for JRDs****
>
>  ****
>
> See http://osis.idcommons.net/wiki/Category:OC5_OP for a list of OpenID
> providers, most of which implement Discovery, including WebFinger.****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> *From:* webfinger-bounces@ietf.org [mailto:webfinger-bounces@ietf.org<webfinger-bounces@ietf.org>]
> *On Behalf Of *Tim Bray
> *Sent:* Friday, July 19, 2013 9:34 PM
> *To:* Paul E. Jones
> *Cc:* webfinger@ietf.org
> *Subject:* Re: [webfinger] Looking for JRDs****
>
>  ****
>
> Got an OpenID Connect provider? rel=
> http://openid.net/specs/connect/1.0/issuer****
>
>  ****
>
> On Sun, Jul 14, 2013 at 7:07 PM, Paul E. Jones <paulej@packetizer.com>
> wrote:****
>
> Tim,****
>
>  ****
>
> You’re welcome to test my addresses, including mailto: / acct: / xmpp: ***
> *
>
>  ****
>
> Most of what is returned is just test data (though some is valid), but it
> should be properly formatted.****
>
>  ****
>
> I have aliases, properties, titles, and non-ASCII characters in the acct:
> reply.  I’m happy to throw something in if you want to check a particular
> response.****
>
>  ****
>
> Paul****
>
>  ****
>
> *From:* webfinger-bounces@ietf.org [mailto:webfinger-bounces@ietf.org] *On
> Behalf Of *Tim Bray
> *Sent:* Sunday, July 14, 2013 5:54 PM
> *To:* webfinger@ietf.org
> *Subject:* [webfinger] Looking for JRDs****
>
>  ****
>
> Working on some WF code... looking for some candidate addresses/domains to
> test JRD wrangling.  Suggestions? -T****
>
>  ****
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenID Connect Interop" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openid-connect-interop+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>  ****
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenID Connect Interop" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openid-connect-interop+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>  ****
>
> ** **
>