Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: =?utf-8?Q?Erik_Wahlstr=C3=B6m?= <erik@wahlstromstekniska.se>
In-Reply-To: <06B31DE0-ACD3-4E20-B4F3-A165931F6D8A@oracle.com>
Date: Thu, 5 Nov 2015 10:22:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2FBC9C7B-110E-462C-B399-CEBEDF202053@wahlstromstekniska.se>
References: <329E288C-A6CB-47A5-8F6E-AD4B9B05D16B@mit.edu>
 <06B31DE0-ACD3-4E20-B4F3-A165931F6D8A@oracle.com>
To: Phil Hunt <phil.hunt@oracle.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/LqXB30y6MtzD9cpQn2v-e2G3GgI>
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] UMA Resource Set Registration
Precedence: list

The concepts on resource registration is also very important when it =
comes to IoT so I think we will get there soon enough.
/ Erik

> On 05 Nov 2015, at 09:35, Phil Hunt <phil.hunt@oracle.com> wrote:
>=20
> I am thinking that the api management perspective might be very =
different than UMAs. Eg we want to automatically register resource =
servers to be managed and negotiate token format and introspection.=20
>=20
> Today this is all done manually both when installing and when =
packaging software for distribution in the form of multiple SKUs =
targeted at each major cloud provider and each enterprise oauth server.=20=

>=20
> In order to have a benefit we have to have interest to support it. =
Judging by the level of interest in the meeting I am not sure the =
pain/opportunity threshold to drive a spec is there yet.=20
>=20
> Phil
>=20
>> On Nov 5, 2015, at 17:21, Justin Richer <jricher@MIT.EDU> wrote:
>>=20
>> As brought up in the F2F today in Yokohama, the UMA Resource Set =
Registration document is here:
>>=20
>> https://docs.kantarainitiative.org/uma/draft-oauth-resource-reg.html
>>=20
>> The ID has expired and is out of sync with the Kantara document.
>>=20
>> =E2=80=94 Justin
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>=20
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth