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

Justin Richer <jricher@mit.edu> Fri, 24 April 2015 21:28 UTC

Return-Path: <jricher@mit.edu>
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 1A1501AC437; Fri, 24 Apr 2015 14:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 NbnfiGACf5ga; Fri, 24 Apr 2015 14:28:04 -0700 (PDT)
Received: from dmz-mailsec-scanner-8.mit.edu (dmz-mailsec-scanner-8.mit.edu [18.7.68.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF29F1AC430; Fri, 24 Apr 2015 14:28:03 -0700 (PDT)
X-AuditID: 12074425-f79ca6d000000e5e-e4-553ab562f184
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 36.23.03678.265BA355; Fri, 24 Apr 2015 17:28:02 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id t3OLS0bV032096; Fri, 24 Apr 2015 17:28:01 -0400
Received: from artemisia.richer.local (static-96-237-195-53.bstnma.fios.verizon.net [96.237.195.53]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t3OLRwbw013043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Apr 2015 17:27:59 -0400
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_14263F66-25AE-426B-A9CE-982D48DFD177"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail 2.5b6
From: Justin Richer <jricher@mit.edu>
In-Reply-To: <553A3929.3000002@cs.tcd.ie>
Date: Fri, 24 Apr 2015 17:27:57 -0400
Message-Id: <AB914C1E-1D45-4597-A6CC-90B5C3C10945@mit.edu>
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>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.2070.6)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrEKsWRmVeSWpSXmKPExsUixG6nrpu01SrU4OYLKYtpP1+zWcz4M5HZ 4vbclWwWJ9++YrOYvvcauwOrx9ruq2weS5b8ZApgiuKySUnNySxLLdK3S+DK2Hguo+C/SMXX +UuZGhi/CXQxcnJICJhIXNz+ghHCFpO4cG89WxcjF4eQwGImiVubm1ggnI2MEnMWNjJCOA+Z JFZf3M4G0iIskCMxb+cxJhCbV8BAYu6pL0wgRcwCUxglljdeY4aYKyXR9PoY2A42AVWJ6Wta wBo4BTQl5jQ+B7NZgOLb/r5hhWhuYZS4f2kxM8RUK4kft2HuOM4oMe31bLBJIgL6Ens3n2Pv YuQA2iAv0bMpfQKj4Cwkh8xCdghIgllAW2LZwtdQtqbE/u7lLBC2vMT2t3Og4pYSi2fegIrb StzqW8AEYdtJPJq2iHUBI8cqRtmU3Crd3MTMnOLUZN3i5MS8vNQiXQu93MwSvdSU0k2M4Ohy Ud3BOOGQ0iFGAQ5GJR7eGXMsQ4VYE8uKK3MPMUpyMCmJ8nr3W4UK8SXlp1RmJBZnxBeV5qQW H2JUAdr1aMPqC4xSLHn5ealKIrz8vUB1vCmJlVWpRfkwZdIcLErivJt+8IUICaQnlqRmp6YW pBbBZGU4OJQkeHu3ADUKFqWmp1akZeaUIKSZODgPMUpw8AANDwCp4S0uSMwtzkyHyJ9iVJQS 5y0ASQiAJDJK8+B6YUnxFaM40FvCvNs2A1XxABMqXPcroMFMQINnLrUAGVySiJCSamC8dGPJ +4lX9kqYae5wy088/dd2ziUzg09/t9yb/OV63WfrB284i1bef7A3enXUSgaJXLY5v7O1L+e1 SCuvaX0rZrDlY02fod9R811es0vb/0b03bMK4I407Hn6aPmEA+2vt5rP2DedsXD+rSVrvFc0 5fTey8oKtp3fpxS0R7P2wK6mG22rTdatU2Ipzkg01GIuKk4EACng0nxlAwAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/9UI7kG0PCi5yN1a7n3A4uIxdH9g>
Cc: draft-ietf-oauth-dyn-reg@ietf.org, "<oauth@ietf.org>" <oauth@ietf.org>, The IESG <iesg@ietf.org>, oauth-chairs@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 21:28:09 -0000

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?

 — Justin

> On Apr 24, 2015, at 8:38 AM, Stephen Farrell <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.