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

"Richer, Justin P." <jricher@mitre.org> Thu, 11 September 2014 16:03 UTC

Return-Path: <jricher@mitre.org>
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 10BF51A6FDD for <oauth@ietfa.amsl.com>; Thu, 11 Sep 2014 09:03:39 -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, RP_MATCHES_RCVD=-1.652] 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 HhRUoMD864om for <oauth@ietfa.amsl.com>; Thu, 11 Sep 2014 09:03:37 -0700 (PDT)
Received: from smtptsrv1.mitre.org (smtptsrv1.mitre.org [192.52.194.77]) by ietfa.amsl.com (Postfix) with ESMTP id F0F9C1A0410 for <oauth@ietf.org>; Thu, 11 Sep 2014 09:03:36 -0700 (PDT)
Received: from smtptsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 816DCC506BC; Thu, 11 Sep 2014 12:03:36 -0400 (EDT)
Received: from IMCCAS02.MITRE.ORG (imccas02.mitre.org [129.83.29.79]) by smtptsrv1.mitre.org (Postfix) with ESMTP id 5FB55C50923; Thu, 11 Sep 2014 12:03:36 -0400 (EDT)
Received: from IMCMBX01.MITRE.ORG ([169.254.1.225]) by IMCCAS02.MITRE.ORG ([129.83.29.69]) with mapi id 14.03.0174.001; Thu, 11 Sep 2014 12:03:36 -0400
From: "Richer, Justin P." <jricher@mitre.org>
To: John Bradley <ve7jtb@ve7jtb.com>
Thread-Topic: [OAUTH-WG] Dynamic Client Registration Management Protocol: Next Steps?
Thread-Index: AQHPzc2/q7TBpPSJVUaj/5AAy9WFo5v8SeEAgAAPK4CAAAHgAIAAAGcA
Date: Thu, 11 Sep 2014 16:03:35 +0000
Message-ID: <AB44CD57-D088-4FEC-B927-BA9D1D78B52D@mitre.org>
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>
In-Reply-To: <3AD141D9-5673-4945-9DC9-E95D7D35EF33@ve7jtb.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.146.15.23]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <09E8F1923C8587489D8C33B1AC01ADC8@imc.mitre.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/UJcG0yqfzI1zA2U_wlxAQHlEntk
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 16:03:39 -0000

+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
>