I would combine these two documents, with no normative changes. This would be
a convenience for implementers. And the metadata values that are currently
optional would remain optional.
I would also add an optional "jwks" metadata member, paralleling this addition
in OpenID Connect Registration. This allows the JWK Set to be passed by value,
rather than by reference. This was discussed in London and people seemed to
agree with this change.
The reference to RFC 4627 should be changed to RFC 7159, which has obsoleted
4627.
Other than that, I believe they're ready to proceed on the next steps towards
becoming an RFC.
-- Mike
-----Original Message-----
From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Hannes Tschofenig
Sent: Friday, April 04, 2014 2:14 AM
To: oauth@ietf.org
Subject: [OAUTH-WG] Working Group Last Call on Dynamic Client Registration
Documents
Hi all,
This is a Last Call for comments on the dynamic client registration
documents:
* OAuth 2.0 Dynamic Client Registration Core Protocol
http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-16
* OAuth 2.0 Dynamic Client Registration Metadata
http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-metadata-00
Since we have to do the last call for these two documents together we are
setting the call for **3 weeks**.
Please have your comments in no later than April 25th.
Ciao
Hannes & Derek
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
