IETF Logo Mail Archive

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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 27 September 2016 14:23 UTC

Return-Path: <shollenbeck@verisign.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 A636212B134 for <oauth@ietfa.amsl.com>; Tue, 27 Sep 2016 07:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign-com.20150623.gappssmtp.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 CfQBhYtLOGgW for <oauth@ietfa.amsl.com>; Tue, 27 Sep 2016 07:22:58 -0700 (PDT)
Received: from mail-qt0-x264.google.com (mail-qt0-x264.google.com [IPv6:2607:f8b0:400d:c0d::264]) (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 B797712B209 for <oauth@ietf.org>; Tue, 27 Sep 2016 07:22:57 -0700 (PDT)
Received: by mail-qt0-x264.google.com with SMTP id z36so52987qtc.0 for <oauth@ietf.org>; Tue, 27 Sep 2016 07:22:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=6chGJ8JVCxfWLjUly/Ijt4GO7w/IE7eegwec4ItkPMY=; b=UKrfkCT3zNCPcnp9ewAqfbRV6P0jFvGN9XnEsKDLmKPl95GfwCbstYlEZ9K32Oiq/D SEfdwPST255qywhP6Y2s/xcg8+u3+hsOahA4oOZjb3Av+8n1MJz7yf1JG6OA+Nmk5/VX H2Brhj8CwfbpIYqFadWjnhQKxr2/xpr7X0rsvHob3m98glr+XFT9sO1t2PfoGSSg7NLW ypeL5x5MJAAmnI0DCu6cwj1Na3xVAw/sKq/Qy4PhRZSFRLRELXg+AMrB8vJkcicwPLE9 LKtt+PNmGUD6s9ee8gQucwId0C/cR8+NF+uWrZxnaozlPtKaAmPcln3n+789meQ3cWi4 Dwqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :mime-version; bh=6chGJ8JVCxfWLjUly/Ijt4GO7w/IE7eegwec4ItkPMY=; b=JReHKN0UDlD9fjFzOHdMmXgdXduN+RaVpo1C3kOz4ywAy1rXbeKM+3dGQf8Qgd6Boz MXvfiQdrllR3n3KSx0A/NMky7DNYYz1gI+uZHWe75YHUDSGh3B4ZuQC9ZAenldnMSFRf cXpfNLsXEvz/MI7e9km9tCgcPFbqIz+GuBKym8kyLXKEIU484UEfM91AOJe02f6iPZEo d8cQTaWIGLTYhdAFfMyl8ohiTwb1niTno/RPWIpmuXDndzdsDb4zicq1E6zWyfk2KwpF flW8PgvXBOVVfWuTlg8Mh4GsXZEdHL5UMWwHv0ZVFF3aw+ET+zHNbpno/11l/VMnx7Jr iihQ==
X-Gm-Message-State: AA6/9Rlgo6rYqBNpWQLt0qiDoZC7BJXRGUqc/+p20Evl1NJ/IXu7O8wOT9ft8b3NTeDXrCRVbHvnwbYHOGu/ID9OiWCeZYZm
X-Received: by 10.55.147.66 with SMTP id v63mr26346578qkd.298.1474986176764; Tue, 27 Sep 2016 07:22:56 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id v198sm209452qka.6.2016.09.27.07.22.56 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 27 Sep 2016 07:22:56 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id u8REMuCa022363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Sep 2016 10:22:56 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0301.000; Tue, 27 Sep 2016 10:22:54 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Nat Sakimura <sakimura@gmail.com>, Justin Richer <jricher@mit.edu>, "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] Identity Provider Interop Testing?
Thread-Index: AQHSGMfSzF+fhohsvkmm3EWb3tckSaCNY5fw
Date: Tue, 27 Sep 2016 14:22:53 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A48B1AA@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <831693C2CDA2E849A7D7A712B24E257F4A4773F3@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <1cae674a-853d-84ae-b7d2-ae63c0eff425@mit.edu> <831693C2CDA2E849A7D7A712B24E257F4A4774AA@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <CABzCy2BT36zmZZmPmv1FFyqRegtgFbJDRDy5nr89pMbuz4dy2A@mail.gmail.com>
In-Reply-To: <CABzCy2BT36zmZZmPmv1FFyqRegtgFbJDRDy5nr89pMbuz4dy2A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F4A48B1AABRN1WNEXMBX01vc_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/F985huqZmrnDNDmyfpQCOV8xC8U>
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:23:02 -0000

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<mailto:shollenbeck@verisign.com>> wrote:
> -----Original Message-----
> From: OAuth [mailto:oauth-bounces@ietf.org<mailto:oauth-bounces@ietf.org>] On Behalf Of Justin Richer
> Sent: Monday, September 19, 2016 9:35 AM
> To: oauth@ietf.org<mailto: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<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth
--

Nat Sakimura

Chairman of the Board, OpenID Foundation

v2.23.0 | Report a Bug | By Email