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

Nat Sakimura <sakimura@gmail.com> Tue, 27 September 2016 14:02 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 62DF212B1DE for <oauth@ietfa.amsl.com>; Tue, 27 Sep 2016 07:02:48 -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 3mfCsCykpDwa for <oauth@ietfa.amsl.com>; Tue, 27 Sep 2016 07:02:44 -0700 (PDT)
Received: from mail-ua0-x235.google.com (mail-ua0-x235.google.com [IPv6:2607:f8b0:400c:c08::235]) (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 159DF12B1D6 for <oauth@ietf.org>; Tue, 27 Sep 2016 07:02:44 -0700 (PDT)
Received: by mail-ua0-x235.google.com with SMTP id n13so11431577uaa.3 for <oauth@ietf.org>; Tue, 27 Sep 2016 07:02:44 -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=oTRQ2igThRiZOLMEOLKXPIE/VleVY/Fiyw8GJIunt1s=; b=Nl6L0YaM8vJD5EcUG6LbkT8VtvEMbWrLwodDtGSNp+HQyifS97HbG2IUWX35IQZCJA wTFGgabeYaHbS4pVk3jlhC5mnDaJcRFt6zlZNY1OEC0nw8qq59hsxwG0HGUhinEJ/NYK n15C47Qn5nLZeTIkO4fvSMJ94RY+0lDwDPR15716I8tZgacxBv+1B1hms0s+I98bVpdi UJ8PNE0/rS8z4a1hvKlbmAIIWR2jYmDklRpVP4Ja4FEbh+B4VCkZzGIzdDaJDOJnbtXr 25Fsn29oTRMAiAedZeMBJZNYsc926fOR8YjuIN4sEFrfExcr2NtO0m+xEsNY00ZKgxJR ZvdA==
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=oTRQ2igThRiZOLMEOLKXPIE/VleVY/Fiyw8GJIunt1s=; b=hXGEFX1dXbeqo0gCaes9/lrkUUYeZe27vKF1d6rzY7yYNd378ipRj0A55lcbuI9apX 6jqOgziXEvzXfLQmt3WnnlQJ/IvrZz94fdjObKRB2F+/Epao9waau0oc9c5XhVJWrw23 S9Q8Ch42PB5fhVaI7wyqzINLdXDOpLY3bDIDo8e4MI+kCF5iEJhQm8iR8EZQSaWtkoa3 yb45LvGLVUlLChlAMDo51k+M1KVz/PvQdo1BFX85iZ4ID0MFt2JGqGrqpKZY3s5m8Y/N KyaXzmdw8ydGd1A5it5/VnRWBhi4gAj7ONZVp78klcme9LmTeCtdNgsWizoB7KN4Cp4o 9efA==
X-Gm-Message-State: AA6/9RmJ+ijfZl9eloKcij/81g1qzSD9E14MI44RnKi8eE8VBrdK7h5k+O+R9WX4hrmGB5WrodFZOeH2lDq5tg==
X-Received: by 10.176.82.109 with SMTP id j42mr2437459uaa.170.1474984963148; Tue, 27 Sep 2016 07:02:43 -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>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A4774AA@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
From: Nat Sakimura <sakimura@gmail.com>
Date: Tue, 27 Sep 2016 14:02:32 +0000
Message-ID: <CABzCy2BT36zmZZmPmv1FFyqRegtgFbJDRDy5nr89pMbuz4dy2A@mail.gmail.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, Justin Richer <jricher@mit.edu>, "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c190200c7111c053d7db268"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/irE-8m1ZWKofooSE3y1kre8ZNFE>
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:02:48 -0000

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