Hi. 

Took much longer than I anticipated but I finally applied the comments I
received during the WGLC. 
When broken down, there were 44 comments that needed to be dealt with. 

I have accepted most of them. There are a few discussion points, and a few
rejects. 

I am now making the list of those, but as I am going into a meeting now, it
will not be available before tomorrow. 

For a preview, you can go and see them in
https://bitbucket.org/Nat/oauth-jwsreq/issues?status=new&status=open. There
are two sets of comments provided by Mike and Brian as of the time of this
writing. They have unresolved comments. I have recorded my dispositions
there so if you are so inclined, please have a look. 

I will pull out those points as separate issues in the tracker so that they
can be individually tracked. 

Cheers, 

Nat Sakimura

--
PLEASE READ :This e-mail is confidential and intended for the
named recipient only. If you are not an intended recipient,
please notify the sender  and delete this e-mail.


-----Original Message-----
From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of
internet-dra...@ietf.org
Sent: Tuesday, January 19, 2016 6:44 PM
To: i-d-annou...@ietf.org
Cc: oauth@ietf.org
Subject: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
 This draft is a work item of the Web Authorization Protocol Working Group
of the IETF.

        Title           : OAuth 2.0 JWT Authorization Request
        Authors         : Nat Sakimura
                          John Bradley
        Filename        : draft-ietf-oauth-jwsreq-07.txt
        Pages           : 16
        Date            : 2016-01-19

Abstract:
   The authorization request in OAuth 2.0 [RFC6749] utilizes query
   parameter serialization, which means that parameters are encoded in
   the URI of the request.  This document introduces the ability to send
   request parameters in form of a JSON Web Token (JWT) instead, which
   allows the request to be signed and encrypted.  using JWT
   serialization.  The request is sent by value or by reference.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-oauth-jwsreq-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-jwsreq-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
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

Reply via email to