Re: [GNAP] I-D Action: draft-ietf-gnap-core-protocol-01.txt

This version adds Aaron and Fabien as authors (welcome, folks!), and also incorporates some small editorial changes to fix typos, update examples, and clean up the document itself. The one normative change is the “updated_at” field for subject information is now an ISO 8601 date string instead of an integer timestamp, which was suggested as part of Yaron’s review and was a very simple change to capture — and didn’t have any detractors to the suggested change on the list. If this change is a problem, please raise an issue with the document.

Other suggested changes have not been incorporated into the document itself (either as comments or substantive changes) as the working group is defining and adopting a new change management process for the document to ensure transparency, clarity, and consensus. I’ll let the chairs speak to the details on this as we all figure it out as a group.

Thank you,
 — Justin

> On Nov 2, 2020, at 10:56 AM, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Grant Negotiation and Authorization Protocol WG of the IETF.
> 
>        Title           : Grant Negotiation and Authorization Protocol
>        Authors         : Justin Richer
>                          Aaron Parecki
>                          Fabien Imbault
> 	Filename        : draft-ietf-gnap-core-protocol-01.txt
> 	Pages           : 119
> 	Date            : 2020-11-02
> 
> Abstract:
>   This document defines a mechanism for delegating authorization to a
>   piece of software, and conveying that delegation to the software.
>   This delegation can include access to a set of APIs as well as
>   information passed directly to the software.
> 
>   This document has been prepared by the GNAP working group design team
>   of Kathleen Moriarty, Fabien Imbault, Dick Hardt, Mike Jones, and
>   Justin Richer.  This document is intended as a starting point for the
>   working group and includes decision points for discussion and
>   agreement.  Many of the features in this proposed protocol can be
>   accomplished in a number of ways.  Where possible, the editor has
>   included notes and discussion from the design team regarding the
>   options as understood.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-gnap-core-protocol/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-gnap-core-protocol-01.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-gnap-core-protocol-01
> 
> 
> 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/
> 
> 
> -- 
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth