So even though I withdrew my suggestion of adding a parameter to device flow,
that was only because my own direct reason was addressed, and I support adding
it back in for all the reasons that Annabelle and Dick and John and others
brought up in conversation.
— Justin
> On Jul 21, 2017, at 8
Hi
This version hopefully have addressed all the comments that I received during
IESG review.
I also added RFC8141 as the reference to URN.
The main difference from -12 that was posted in March are:
1) Now, all the parameters to be used MUST reside within the request object.
(It is still
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Web Authorization Protocol WG of the IETF.
Title : The OAuth 2.0 Authorization Framework: JWT Secured
Authorization Request (JAR)
Authors : Nat Sakim
OAuth Working Group Meeting at IETF 99 21-Jul-17
William Denniss presented on the Device Flow
Justin Richer discussed a suggestion to add another parameter that he'd made on
the list
William Denniss clarified that the client constructs the URL - not the server
Justin withdrew his suggestion
Just
Thanks Alexey, and sorry for taking this long.
I will fix the nits about URN ASAP.
Best,
Nat
--
このメールは、本来の宛先の方のみに限定された機密情報が含まれてい
る場合がございます。お心あたりのない場合は、送信者にご連絡のうえ、
このメールを削除して下さいますようお願い申し上げます。
PLEASE READ :This e-mail is confidential and intended for the
named recipient only. If you are not an
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-jwsreq-14: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to h
