[OAUTH-WG] OAuth Dynamic Registration Management API: Our Lunch Chat Today

Hannes Tschofenig <hannes.tschofenig@gmx.net> Thu, 06 March 2014 14:15 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 24CF61A036B for <oauth@ietfa.amsl.com>; Thu, 6 Mar 2014 06:15:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.547, 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 TSmRhrVebhc7 for <oauth@ietfa.amsl.com>; Thu, 6 Mar 2014 06:15:03 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 196051A0361 for <oauth@ietf.org>; Thu, 6 Mar 2014 06:15:03 -0800 (PST)
Received: from [192.168.10.136] ([31.133.156.1]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0M1VlJ-1XANPX1StF-00tWpu for <oauth@ietf.org>; Thu, 06 Mar 2014 15:14:58 +0100
Message-ID: <531882E0.7010809@gmx.net>
Date: Thu, 06 Mar 2014 15:14:56 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: oauth@ietf.org
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="JWpJLRSftPpvDcQbvI68O5rvs1CN8KV7H"
X-Provags-ID: V03:K0:fLVu/rL+Xfy5n/yF/MdTAFc8QeE6V8/4JdQzizLUrfODvcLujIR WzUL2ca1xHMvsx33oqvywfoc/lStLibZfcRYY8xe0NVisAFvTklIDVAercna05FWxUEgNOG wKaaI54Wh6407cceo6i0+uKu63/xrerlqSg20jeVxyQnkFzumel2Bb4j9OMUZu6ZiuqrQG5 8zqtUJ0j6O/iQwEhi44VQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/MnSFP3XmqA3Nn1pDilGKaZbJDTw
Subject: [OAUTH-WG] OAuth Dynamic Registration Management API: Our Lunch Chat Today
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: Thu, 06 Mar 2014 14:15:05 -0000

Hi all,

several OAuth folks met today to talk about the next steps regarding the
OAuth dynamic client registration management API.

At the end of our short lunch chat I asked each participant individually
what they think should be done next. Here are the notes I took.

Phil: We need to document what events does the client want to notify the
server. Phil, volunteered to write a slide deck.

Justin: Document the deployment characteristics (for the different
client types). He also suggested to publish the current document as an
experimental draft and let people play around with it.

Tony: The work on the management API is not mature enough for
standardization

Mat: Decide what is in scope and what is out-of-scope.

Morteza: Investigate use cases further

Brian: Document use cases and assumptions

Mike: Focus on the dynamic registration and the meta-data work for now.
The management API is not mature enough.

John: We first need to figure out what we need the management API for.

Bill: Document what problem we are solving.

Kaoru: Document use cases and better understand the relationship with
the other specs.

As you can see the views are all over the map. It does, however, seem to
be useful to get a better understanding of the deployment and the use cases.

Ciao
Hannes