IETF Logo Mail Archive

Re: [OAUTH-WG] Stephen Farrell's Discuss on draft-ietf-oauth-dyn-reg-28: (with DISCUSS and COMMENT)

Mike Jones <Michael.Jones@microsoft.com> Fri, 24 April 2015 22:25 UTC

Return-Path: <Michael.Jones@microsoft.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 D4C331AD358; Fri, 24 Apr 2015 15:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 Zet7-NLoH6sT; Fri, 24 Apr 2015 15:25:29 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0120.outbound.protection.outlook.com [207.46.100.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03D2C1AD0CC; Fri, 24 Apr 2015 15:25:28 -0700 (PDT)
Received: from BY2PR03MB442.namprd03.prod.outlook.com (10.141.141.145) by BY2PR03MB441.namprd03.prod.outlook.com (10.141.141.142) with Microsoft SMTP Server (TLS) id 15.1.148.15; Fri, 24 Apr 2015 22:25:27 +0000
Received: from BY2PR03MB442.namprd03.prod.outlook.com ([10.141.141.145]) by BY2PR03MB442.namprd03.prod.outlook.com ([10.141.141.145]) with mapi id 15.01.0148.008; Fri, 24 Apr 2015 22:25:28 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Thread-Topic: [OAUTH-WG] Stephen Farrell's Discuss on draft-ietf-oauth-dyn-reg-28: (with DISCUSS and COMMENT)
Thread-Index: AQHQfoUalSOc/4LV0kOyMMcWs5xAgZ1cEhCAgAAC7gCAAAESAIAAAdEAgAACFYCAAJQPgIAAATgAgAAISICAAAaSrw==
Date: Fri, 24 Apr 2015 22:25:27 +0000
Message-ID: <BY2PR03MB44233B10FB71EAA0DA6A620F5EC0@BY2PR03MB442.namprd03.prod.outlook.com>
References: <20150424115205.3265.73381.idtracker@ietfa.amsl.com> <553A3289.2000401@cs.tcd.ie> <553A34FE.8@mit.edu> <553A35E4.1000904@cs.tcd.ie> <553A376A.1070806@mit.edu> <553A3929.3000002@cs.tcd.ie> <AB914C1E-1D45-4597-A6CC-90B5C3C10945@mit.edu> <553AB662.7010303@cs.tcd.ie>, <CAHbuEH6AS=N_pX+bByjGJ3d-Kr0xcwKJ+sUDxFDsuPMpjG8wXQ@mail.gmail.com>
In-Reply-To: <CAHbuEH6AS=N_pX+bByjGJ3d-Kr0xcwKJ+sUDxFDsuPMpjG8wXQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-originating-ip: [166.171.251.144]
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR03MB441;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(164054003)(51704005)(377454003)(24454002)(479174004)(2656002)(93886004)(50986999)(40100003)(19580405001)(86362001)(122556002)(230783001)(87936001)(46102003)(74316001)(106116001)(76176999)(33656002)(16236675004)(5001770100001)(77096005)(76576001)(102836002)(2950100001)(62966003)(99286002)(66066001)(86612001)(54356999)(77156002)(92566002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR03MB441; H:BY2PR03MB442.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-microsoft-antispam-prvs: <BY2PR03MB441E751F44DA6B228666D3EF5EC0@BY2PR03MB441.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006)(3002001); SRVR:BY2PR03MB441; BCL:0; PCL:0; RULEID:; SRVR:BY2PR03MB441;
x-forefront-prvs: 05568D1FF7
Content-Type: multipart/alternative; boundary="_000_BY2PR03MB44233B10FB71EAA0DA6A620F5EC0BY2PR03MB442namprd_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Apr 2015 22:25:27.8286 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR03MB441
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/e8VmCCiXDerGgsXj-dpZFftuEi0>
Cc: "draft-ietf-oauth-dyn-reg@ietf.org" <draft-ietf-oauth-dyn-reg@ietf.org>, The IESG <iesg@ietf.org>, "oauth-chairs@ietf.org" <oauth-chairs@ietf.org>, "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Stephen Farrell's Discuss on draft-ietf-oauth-dyn-reg-28: (with DISCUSS and COMMENT)
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: Fri, 24 Apr 2015 22:25:31 -0000

Thanks all. Justin, please add a comma after the OpenID.Discovery reference.
________________________________
From: Kathleen Moriarty<mailto:kathleen.moriarty.ietf@gmail.com>
Sent: ‎4/‎24/‎2015 3:02 PM
To: Stephen Farrell<mailto:stephen.farrell@cs.tcd.ie>
Cc: Justin Richer<mailto:jricher@mit.edu>; draft-ietf-oauth-dyn-reg@ietf.org<mailto:draft-ietf-oauth-dyn-reg@ietf.org>; oauth-chairs@ietf.org<mailto:oauth-chairs@ietf.org>; <oauth@ietf.org><mailto:oauth@ietf.org>; The IESG<mailto:iesg@ietf.org>
Subject: Re: [OAUTH-WG] Stephen Farrell's Discuss on draft-ietf-oauth-dyn-reg-28: (with DISCUSS and COMMENT)

Thank you, both!

On Fri, Apr 24, 2015 at 5:32 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie<mailto:stephen.farrell@cs.tcd.ie>> wrote:


On 24/04/15 22:27, Justin Richer wrote:
> Stephen, I’ve worked on this this afternoon and this is my proposed text:
>
>           The response to such a
>            situation is out of scope for this specification but could include
>            filing a report with the application developer or authorization
>           server provider, attempted re-registration with different metadata
>           values, or various other methods. For instance, if the server also
>           supports a registration management mechanism such as that defined in
>           <xref target="OAuth.Registration.Management"/>, the client or
>           developer could attempt to update the registration with different
>           metadata values. This process could also be aided by a service
>           discovery protocol such as <xref target="OpenID.Discovery"/> which
>           can list a server's capabilities, allowing a client to make a more
>           informed registration request. The use of any such management or
>           discovery system is OPTIONAL and outside the scope of this
>           specification.
>
> Does this text work for you?

It does, nicely.

Thanks,
S.


>
>  — Justin
>
>> On Apr 24, 2015, at 8:38 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie<mailto:stephen.farrell@cs.tcd.ie>> wrote:
>>
>>
>>
>> On 24/04/15 13:30, Justin Richer wrote:
>>>>
>>>
>>> OK, so are you asking for something like:
>>>
>>> "If the server supports an update mechanism such as [Dyn-Reg-Management]
>>> and a discovery mechanism such as [OIDC-Discovery], then a smart client
>>> could use these components to renegotiate undesirable metadata values."
>>>
>>> With both of these being informative references? I'm not opposed to it.
>>
>> That'd work for me, yes, thanks.
>>
>> S.
>




--

Best regards,
Kathleen

v2.23.0 | Report a Bug | By Email