Draft: draft-ietf-gnap-core-protocol

Commentary: Adds implementation status section , 
 To edit notification comments on pull requests , go to your . _ 
 Now is a good time to add this information into the draft , per Note that according to RFC 7942 , this section will be removed before the protocol is published as an RFC . 
 Pending feedback from the IETF113 Hackaton , and discussion started here : 
 Maybe this could go in instead of the core spec ( since it is expected to be removed before publication anyway ) Note that I 've created a wiki label so that we can isolate those issues
Mailing list commentary: Hi everyone , Ahead of of the IETF 113 Hackathon , we ’d like to collect a list of tools that implementors can use for building GNAP . These can either be implementations of GNAP itself ( either in whole or some component or subset ) , or libraries that can be used to implement things needed in GNAP , like HTTP Message Signatures or Subject Identifiers or JOSE . I ’ll start off this thread with the tools that I personally know about , and we are asking for everyone else to chime in with their own additions . GNAP : XYZ : A implementation ( based on Spring ) of an AS , RS , and webserver - based client instance . The UX is written in React agains a Spring - based backend API . Supports HTTP Signing and methods . There was a React - based SPA implementation in there as well but it has n’t been kept up to date . HTTP Signatures : Go library ( from ) . Python implementation behind demo site : Rust library ( known to be incomplete — also note this is a branch on a fork ): HTTP Structured Fields ( used with signatures ): Python :  : Subject Identifiers :    : I do n’t think it ’s really worth listing all of the JOSE implementations out there , as there are so many . That said , many that are written as purely JWT libraries do n’t like you to provide your own unencoded ( or pre - encoded ) payload body , which is required with GNAP ’s use of JWS for key proofing . Please submit your additions to the mailing list . We ’ll be collecting this list and making it available to Hackathon participants . The editors also plan to incorporate this information in a future version of the spec as an “ implementation status ” section , as discussed in this issue : — Justin
Paragraph (version B):
implementation by David Skyberg.  https://github.com/dskyberg/gnap
[16].  Prototype implementation of AS and Client in Rust.  MIT
license.
Paragraph (version B):
from Interledger Foundation. https://github.com/interledger/rafiki
[17] Production implementation of AS in JavaScript.  Apache 2.0
license.
Paragraph (version B):
implementation by Aaron Pareckit. https://github.com/aaronpk/gnap-
client-php [18] Prototype implementation of web application client
and CLI client in PHP, with common support library.  CC0 license.
Paragraph (version B):
from SUNET. https://github.com/SUNET/sunet-auth-server [19]
Production implementation of AS in Python.  BSD license.
Paragraph (version B):
from Bespoke Engineering, implementation by Justin Richer.
https://github.com/bspk/oauth.xyz-java [20].  Advanced prototype
implementation of AS, Client, and RS in Java, with common support
library.  Prototype implementation of SPA Client in pure JavaScript.
Apache 2.0 license.