Re: [OAUTH-WG] Dynamic Client Registration Management Protocol: Next Steps?

Hannes Tschofenig <hannes.tschofenig@gmx.net> Thu, 11 September 2014 21:23 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 2C1041A0295 for <oauth@ietfa.amsl.com>; Thu, 11 Sep 2014 14:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.552
X-Spam-Level:
X-Spam-Status: No, score=-3.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652, 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 1tKP1e8Oi2Ml for <oauth@ietfa.amsl.com>; Thu, 11 Sep 2014 14:23:26 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AFAE1A02EC for <oauth@ietf.org>; Thu, 11 Sep 2014 14:22:36 -0700 (PDT)
Received: from [192.168.10.163] ([167.220.25.81]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MUILK-1Xs8hm2CcE-00Qxy2; Thu, 11 Sep 2014 23:22:33 +0200
Message-ID: <54121291.8010106@gmx.net>
Date: Thu, 11 Sep 2014 23:22:25 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: "Richer, Justin P." <jricher@mitre.org>, John Bradley <ve7jtb@ve7jtb.com>
References: <5410E3AF.3030806@gmx.net> <d9523ba290534a9493fc805980f4365d@BLUPR03MB309.namprd03.prod.outlook.com> <9E856DCC-79F4-421B-A6EB-1438115843CB@mitre.org> <AA4C1102-5092-4660-8BF8-51E53B0CD26D@oracle.com> <3AD141D9-5673-4945-9DC9-E95D7D35EF33@ve7jtb.com> <AB44CD57-D088-4FEC-B927-BA9D1D78B52D@mitre.org>
In-Reply-To: <AB44CD57-D088-4FEC-B927-BA9D1D78B52D@mitre.org>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="nnFD7JnfbVFO6sviQiPqtojdi8uiVnfvL"
X-Provags-ID: V03:K0:BoxJfpXhZXz8bY4fbVnPW4InHBzIka6ww5MzMDLbex1n3pKhxIX rSp1ZmX0VPHnwpqCcBoQS21GPnuwb38mDuUi6QxLOK4Tth5s+74n0GekfMGdX00a4EJ2FC5 veFuqNrOXBbZbVpnhjd/TAz4mHgnDXgbmy8MIx9xGZlY3qZkckcY7W1o7pCBOrH7lBHV6zg 0JBmCt7O7Gt3T+E5duDBA==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/Kj-2eqQzEG8fmvav7eFs6Tl7hSQ
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Dynamic Client Registration Management Protocol: Next Steps?
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, 11 Sep 2014 21:23:28 -0000

I also looked at
https://www.ietf.org/iesg/informational-vs-experimental.html and I got
the impression that an Experimental RFC would be the right category.

Ciao
Hannes

On 09/11/2014 06:03 PM, Richer, Justin P. wrote:
> +1 
> 
> That was the key line that I took from the guidelines as well and this was my understanding of the discussion in Toronto.
> 
>  -- Justin
> 
> On Sep 11, 2014, at 12:02 PM, John Bradley <ve7jtb@ve7jtb.com> wrote:
> 
>> I think this fits.
>>
>> 	• If the IETF may publish something based on this on the standards track once we know how well this one works, it's Experimental. This is the typical case of not being able to decide which protocol is "better" before we have experience of dealing with them from a stable specification. Case in point: "PGM Reliable Transport Protocol Specification" (RFC 3208)
>>
>> If we publish something it may or may not look like the current spec but getting some experience with the current spec will inform that decision. 
>>
>> John B.
>> On Sep 11, 2014, at 12:55 PM, Phil Hunt <phil.hunt@oracle.com> wrote:
>>
>>> Interesting. The definitions in that don't correspond with what ADs and other groups are doing. 
>>>
>>> I heard httpbis using experimental as a placeholder for a draft that didn't have full consensus to bring back later. 
>>>
>>> That was the feel I had in Toronto-that we weren't done but it was time to publish something. 
>>>
>>> Reading the actual definition i would say neither fits. Ugh. 
>>>
>>> Phil
>>>
>>>> On Sep 11, 2014, at 8:01, "Richer, Justin P." <jricher@mitre.org> wrote:
>>>>
>>>> According to the guidelines here:
>>>>
>>>> https://www.ietf.org/iesg/informational-vs-experimental.html
>>>>
>>>> And the discussion in Toronto, it's clearly experimental.
>>>>
>>>> -- Justin
>>>>
>>>>> On Sep 11, 2014, at 10:36 AM, Anthony Nadalin <tonynad@microsoft.com> wrote:
>>>>>
>>>>> Is "experimental" the correct classification? Maybe "informational" is more appropriate as both of these were discussed. 
>>>>>
>>>>> -----Original Message-----
>>>>> From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Hannes Tschofenig
>>>>> Sent: Wednesday, September 10, 2014 4:50 PM
>>>>> To: oauth@ietf.org
>>>>> Subject: [OAUTH-WG] Dynamic Client Registration Management Protocol: Next Steps?
>>>>>
>>>>> Hi all,
>>>>>
>>>>> in response to the discussions at the last IETF meeting the authors of the "Dynamic Client Registration Management Protocol"
>>>>> http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-management-05 have changed the document type to "Experimental".
>>>>>
>>>>> We need to make a decision about the next steps for the document and we see the following options:
>>>>>
>>>>> a) Publish it as an experimental RFC
>>>>>
>>>>> b) Remove it from the working group and ask an AD to shepherd it
>>>>>
>>>>> c) Remove it from the working group and let the authors publish it via the independent submission track.
>>>>>
>>>>> In any case it would be nice to let folks play around with it and then, after some time, come back to determine whether there is enough interest to produce a standard.
>>>>>
>>>>> Please let us know what you think!
>>>>>
>>>>> Ciao
>>>>> Hannes & Derek
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>> _______________________________________________
>>> 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
>