Re: [OAUTH-WG] Dynamic Client Registration: IPR Confirmation
Maciej Machulak <maciej.machulak@gmail.com> Wed, 16 July 2014 11:51 UTC
Return-Path: <maciej.machulak@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ADF01B2B15 for <oauth@ietfa.amsl.com>; Wed, 16 Jul 2014 04:51:26 -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, SPF_PASS=-0.001] autolearn=ham
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 2PfHDAenvT6V for <oauth@ietfa.amsl.com>; Wed, 16 Jul 2014 04:51:23 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AB2C1B29D3 for <oauth@ietf.org>; Wed, 16 Jul 2014 04:51:22 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id f8so4682874wiw.5 for <oauth@ietf.org>; Wed, 16 Jul 2014 04:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0CqOtewJdu+c3FwrMMY6BGR/T4oyD/DCYFgr92HJ/6I=; b=MFZsfUQ/vjWZcTyo9o4ed2QLAexQVxrhxP69r1xb6ndS4PKCMSWElAL13BS2WtCZPz mQJzTyoQ11+SGNg2OtU7aIzlIguZN5xHzLyox88jxi1CetPAaHM/NRa6tDdsfNPe10Lg l6v+cHd8tSoOos+iW//6/BEBm2VKeFUqjp5gQtBcSnmRreHw3ICXgw8yPqBXFkePkp2Q wDSxRYzSk1wamMMXe2kuNEXTN7kuPFfIe30a1+v0M0oRXThLMZU96nl4z7zwIBj+SdCf CSBnOXf2C/r0jCZAKKDOJjs9ExDPiT69MmOUiJwAl/1COrxP+Lri1cQOuw2K/4dlBt3w huRw==
MIME-Version: 1.0
X-Received: by 10.180.206.144 with SMTP id lo16mr12843480wic.52.1405511477837; Wed, 16 Jul 2014 04:51:17 -0700 (PDT)
Received: by 10.194.18.198 with HTTP; Wed, 16 Jul 2014 04:51:17 -0700 (PDT)
In-Reply-To: <53C665B0.7040708@gmx.net>
References: <53BBDBEE.703@gmx.net> <BE6275F6-27D0-4A7A-ABA2-18B571BFDF18@oracle.com> <4E1F6AAD24975D4BA5B16804296739439ADA02B7@TK5EX14MBXC294.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B16804296739439ADA1766@TK5EX14MBXC294.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B16804296739439ADAB98C@TK5EX14MBXC294.redmond.corp.microsoft.com> <53C65120.4020302@gmx.net> <53C664DC.50907@mit.edu> <53C665B0.7040708@gmx.net>
Date: Wed, 16 Jul 2014 13:51:17 +0200
Message-ID: <CA+c2x_Vuj_1BR7h+kgkNGj=iMZQSWivLF7=de0usze6PEXKaTw@mail.gmail.com>
From: Maciej Machulak <maciej.machulak@gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: multipart/alternative; boundary="001a11c3843a5d4dec04fe4e245c"
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/5jdUqpY-rvqEFjNsjPy9Ke09D4k
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Dynamic Client Registration: IPR Confirmation
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 16 Jul 2014 11:51:26 -0000
Hi, Yes, I agree - I think the note should mention UMA. As Justin proposed, there should be a normative reference to an IETF document. Kind regards, Maciej On 16 July 2014 13:44, Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote: > Interesting background information. Maybe we should then extend the note > Mike provided to also clarify the relationship with the UMA work (both > in terms to IPR, copyright, and attribution-wise). > It would also make sense to state the relationship in the introduction > to highlight the compatibility, which I believe is a big accomplishment. > > Ciao > Hannes > > On 07/16/2014 01:41 PM, Justin Richer wrote: > > I thought I had sent this note already, but I don't see it in the > > archives or in my 'sent' folder: > > > > If we're going to point to OpenID Connect (which I'm fine with), then we > > should clarify that portions were also taken from the UMA specification. > > In fact, draft -00 actually *was* the UMA specification text entirely. > > This is also what the OpenID Connect registration specification was > > (loosely) based on when it was started. > > > > In reality, the relationship between these three documents from three > > different SBO's is more complicated: they all grew up together and > > effectively merged to become wire-compatible with each other. There were > > a number of changes that were discussed here in the IETF that OpenID > > Connect adopted, and a number of changes that were discussed at OIDF > > that were adopted here. OIDC also extends the IETF draft with a set of > > OIDC-specific metadata fields and editorial language that makes it fit > > more closely in the OIDC landscape, but make no mistake: they're the > > same protocol. In the case of UMA, it's a straight normative reference > > to the IETF document now because we were able to incorporate those use > > cases and parameters directly. > > > > The trouble is, I'm not sure how to concisely state that all that in the > > draft text, but it's not as simple as "we copied OpenID", which is what > > the text below seems to say. > > > > -- Justin > > > > On 7/16/2014 6:17 AM, Hannes Tschofenig wrote: > >> Thanks, Mike. > >> > >> This is a useful addition and reflects the relationship between the two > >> efforts. > >> > >> Please add it to the next draft version. > >> > >> Ciao > >> Hannes > >> > >> On 07/15/2014 09:46 PM, Mike Jones wrote: > >>> So that the working group has concrete language to consider, propose > the > >>> following language to the OAuth Dynamic Client Registration > specification: > >>> > >>> > >>> > >>> Portions of this specification are derived from the OpenID Connect > >>> Dynamic Registration [OpenID.Registration] specification. This was > done > >>> so that implementations of this specification and OpenID Connect > Dynamic > >>> Registration can be compatible with one another. > >>> > >>> > >>> > >>> -- Mike > >>> > >>> > >>> > >>> *From:*OAuth [mailto:oauth-bounces@ietf.org] *On Behalf Of *Mike Jones > >>> *Sent:* Tuesday, July 08, 2014 7:15 PM > >>> *To:* Phil Hunt; Hannes Tschofenig > >>> *Cc:* Maciej Machulak; oauth@ietf.org > >>> *Subject:* Re: [OAUTH-WG] Dynamic Client Registration: IPR Confirmation > >>> > >>> > >>> > >>> Thinking about this some more, there is one IPR issue that we need to > >>> address before publication. This specification is a derivative work > >>> from the OpenID Connect Dynamic Registration specification > >>> http://openid.net/specs/openid-connect-registration-1_0.html. Large > >>> portions of the text were copied wholesale from that spec to this one, > >>> so that the two would be compatible. (This is good thing – not a bad > >>> thing.) > >>> > >>> > >>> > >>> This is easy to address from an IPR perspective – simply acknowledge > >>> that this spec is a derivative work and provide proper attribution. > The > >>> OpenID copyright in the spec at > >>> http://openid.net/specs/openid-connect-registration-1_0.html#Notices > >>> allows for this resolution. It says: > >>> > >>> > >>> > >>> Copyright (c) 2014 The OpenID Foundation. > >>> > >>> The OpenID Foundation (OIDF) grants to any Contributor, developer, > >>> implementer, or other interested party a non-exclusive, royalty free, > >>> worldwide copyright license to reproduce, prepare derivative works > from, > >>> distribute, perform and display, this Implementers Draft or Final > >>> Specification solely for the purposes of (i) developing specifications, > >>> and (ii) implementing Implementers Drafts and Final Specifications > based > >>> on such documents, provided that attribution be made to the OIDF as the > >>> source of the material, but that such attribution does not indicate an > >>> endorsement by the OIDF. > >>> > >>> Let’s add the reference and acknowledgment in the next version. > >>> > >>> > >>> > >>> -- Mike > >>> > >>> > >>> > >>> *From:*Mike Jones > >>> *Sent:* Tuesday, July 08, 2014 10:06 AM > >>> *To:* Phil Hunt; Hannes Tschofenig > >>> *Cc:* John Bradley; Justin Richer; Maciej Machulak; oauth@ietf.org > >>> <mailto:oauth@ietf.org> > >>> *Subject:* RE: Dynamic Client Registration: IPR Confirmation > >>> > >>> > >>> > >>> I likewise do not hold any IPR on these specs. > >>> > >>> > ------------------------------------------------------------------------ > >>> > >>> *From: *Phil Hunt <mailto:phil.hunt@oracle.com> > >>> *Sent: *7/8/2014 9:11 AM > >>> *To: *Hannes Tschofenig <mailto:hannes.tschofenig@gmx.net> > >>> *Cc: *Mike Jones <mailto:Michael.Jones@microsoft.com>; John Bradley > >>> <mailto:ve7jtb@ve7jtb.com>; Justin Richer <mailto:jricher@mitre.org>; > >>> Maciej Machulak <mailto:m.p.machulak@ncl.ac.uk>; oauth@ietf.org > >>> <mailto:oauth@ietf.org> > >>> *Subject: *Re: Dynamic Client Registration: IPR Confirmation > >>> > >>> I confirm I have no IPR disclosures on this document. > >>> > >>> Phil > >>> > >>>> On Jul 8, 2014, at 4:54, Hannes Tschofenig <hannes.tschofenig@gmx.net > <mailto:hannes.tschofenig@gmx.net>> wrote: > >>>> > >>>> Hi Phil, John, Maciej, Justin, Mike, > >>>> > >>>> I am working on the shepherd writeup for the dynamic client > registration > >>>> document and one item in the template requires me to indicate whether > >>>> each document author has confirmed that any and all appropriate IPR > >>>> disclosures required for full conformance with the provisions of BCP > 78 > >>>> and BCP 79 have already been filed. > >>>> > >>>> Could you please confirm? > >>>> > >>>> Ciao > >>>> Hannes > >>>> > >>>> > >> > >> > >> _______________________________________________ > >> OAuth mailing list > >> OAuth@ietf.org > >> https://www.ietf.org/mailman/listinfo/oauth > > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > > -- Maciej Machulak email: maciej.machulak@gmail.com mobile: +44 7999 606 767 (UK) mobile: +48 602 45 31 66 (PL)
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Justin Richer
- [OAUTH-WG] Dynamic Client Registration: IPR Confi… Hannes Tschofenig
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… John Bradley
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Phil Hunt
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Mike Jones
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Mike Jones
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… John Bradley
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Mike Jones
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Maciej Machulak
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Hannes Tschofenig
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Justin Richer
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Hannes Tschofenig
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Maciej Machulak
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Justin Richer
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Mike Jones
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Justin Richer
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Mike Jones
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Maciej Machulak
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… Justin Richer
- Re: [OAUTH-WG] Dynamic Client Registration: IPR C… John Bradley