Re: [OAUTH-WG] Identity Provider Interop Testing?

Nat Sakimura <sakimura@gmail.com> Tue, 27 September 2016 14:28 UTC

Return-Path: <sakimura@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5302C12B1EE for <oauth@ietfa.amsl.com>; Tue, 27 Sep 2016 07:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bH1Vj66WOyPn for <oauth@ietfa.amsl.com>; Tue, 27 Sep 2016 07:28:21 -0700 (PDT)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EB7212B1E5 for <oauth@ietf.org>; Tue, 27 Sep 2016 07:28:20 -0700 (PDT)
Received: by mail-ua0-x22b.google.com with SMTP id n13so12160004uaa.3 for <oauth@ietf.org>; Tue, 27 Sep 2016 07:28:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=j+JljVz/ymhedCeQntl6UEX7aShJgVCTwnKyv3TOweM=; b=WsuN5/oV1StBXM3C6KzqhYItZtTcKtzf6qZWbuclioh8quon5UTUDhU7BzrPAKobs+ UWNr0H08RJKrxwJAhirPnyuPLbaihT60BHTjrmGZDHhpUlsCCo2uhyWdQi1zBqa9FiRw RG9Vyn+QDmmUPUjsCEL2Y6+wXDWd3bN0Z3hc7JlJ06jrUkcivUJUh5SaXlvEyCRJtToE wWLZYHXQAjdMSItLJOA6JtGfjkjplFvQoyGAylz+ALfa+0AU86TcU7k6Ki4+k3ZbiAmO DNuNZ2BxNuo++XHKi57wRIg3vZW3YU/ifZWV3FkEHOk1I3dKQcdVqi3ixuGL/clS7IuB 2s8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=j+JljVz/ymhedCeQntl6UEX7aShJgVCTwnKyv3TOweM=; b=BMKLiLHKQBKI8K6rnSqa02lGaEl++5bYpbwUpZ10YZY6xFFeDsAjlSPoSAJE52YhVl /X+1EYu78EsGNDnprnHS4IYVY2MbzEaVIEG6uDw8NiOqbgwS6l4iX/+49vT16ee+8G9r 9BB30JAWPMZAHsS4X1ctg9bgGeSde2VVOZWNKku1wZ/4XwTDDoD9ANOU2W/KAiIsxKQY pJ/dta0lcUB21TGiTJZC3ET9u4AgLfklhMpWUmNoLjiipZrJg0BmotXPDn0Fzcpt20Li tsXSYbemjppUN/BevazLdVcx2ReDlkv8AXUn+hy2zHS9Mo+t+vWABkG7g+OwnffTp29K AZnQ==
X-Gm-Message-State: AA6/9Rn+BKG5tf97pZvCEN6oruOqsG4jWAjZNYKZSUCrBpS3Sh8W1Y+Wls55hC1df+kmMqQg5P9/jknzdBU+5w==
X-Received: by 10.176.82.109 with SMTP id j42mr2582043uaa.170.1474986498920; Tue, 27 Sep 2016 07:28:18 -0700 (PDT)
MIME-Version: 1.0
References: <831693C2CDA2E849A7D7A712B24E257F4A4773F3@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <1cae674a-853d-84ae-b7d2-ae63c0eff425@mit.edu> <831693C2CDA2E849A7D7A712B24E257F4A4774AA@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <CABzCy2BT36zmZZmPmv1FFyqRegtgFbJDRDy5nr89pMbuz4dy2A@mail.gmail.com> <831693C2CDA2E849A7D7A712B24E257F4A48B1AA@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A48B1AA@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
From: Nat Sakimura <sakimura@gmail.com>
Date: Tue, 27 Sep 2016 14:28:07 +0000
Message-ID: <CABzCy2BrUKxQ8u_EOOvPmWYUHckxfAshGD_W9czj9pxXLXehFQ@mail.gmail.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, Justin Richer <jricher@mit.edu>, "oauth@ietf.org" <oauth@ietf.org>, Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary="94eb2c190200515223053d7e0e4f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/2SWbDb9op1tcpsI5ywEM0A6qy1M>
Subject: Re: [OAUTH-WG] Identity Provider Interop Testing?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2016 14:28:23 -0000

Just as a side note: we are constructing the RP testing suite right now.
Perhaps you might want to become a beta tester as well. For more info,
please contact Mike Jones, who is CC'ed, for the detail.

Best,

Nat

On Tue, Sep 27, 2016 at 11:22 PM Hollenbeck, Scott <shollenbeck@verisign.com>
wrote:

> Thanks, Nat.
>
>
>
> Scott
>
>
>
> *From:* Nat Sakimura [mailto:sakimura@gmail.com]
> *Sent:* Tuesday, September 27, 2016 10:03 AM
> *To:* Hollenbeck, Scott; Justin Richer; oauth@ietf.org
>
>
> *Subject:* Re: [OAUTH-WG] Identity Provider Interop Testing?
>
>
>
> There is an interop list which does not have IPR requirement.
>
> The IPR Contribution Agreement is there to prevent a party to embed patent
> encumbered claims into the specification to collect license fees at a later
> date. There is no need for such in just working with the interops.
>
>
>
> OpenID Connect Interop Group:
> https://groups.google.com/forum/#!forum/openid-connect-interop
>
>
>
> Cheers,
>
>
>
> Nat
>
>
>
> On Mon, Sep 19, 2016 at 11:37 PM Hollenbeck, Scott <
> shollenbeck@verisign.com> wrote:
>
> > -----Original Message-----
> > From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Justin Richer
> > Sent: Monday, September 19, 2016 9:35 AM
> > To: oauth@ietf.org
> > Subject: Re: [OAUTH-WG] Identity Provider Interop Testing?
> >
> > You're better off contacting the OpenID Connect working group and the
> > interoperability list there.
> >
> > http://openid.net/wg/connect/
> >
> > While there's a lot of overlap in the communities, OAuth and OIDC are
> > different protocols and the discussion you want is better held there.
>
> Understood, but there's this little detail:
>
> > Please note that while anyone can join the mailing list as a read-only
> > recipient, posting to the mailing list or actively contributing to the
> > specification itself requires the submission of an IPR Agreement.
>
> Sorry for the off-topic post, but I thought that a note sent to this list
> might just find the right people without having to deal with the overhead
> of getting an IPR Agreement in place to gain posting privileges.
>
> Scott
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
> --
>
> Nat Sakimura
>
> Chairman of the Board, OpenID Foundation
>
-- 

Nat Sakimura

Chairman of the Board, OpenID Foundation