Subject: [GNAP] GNAP-RS Draft

From: Justin Richer <[email-masked]>
Date: Wed, 21 Apr 2021 10:08:02 -0400

In recent discussions on the list, tracker, and calls, there has been a lot of mixing up of requirements for the client vs. the RS vs. the AS vs. other components, and the relationships between them. The editors proposed and enacted a solution to focus the core document on the client -> AS and client -> RS parts of the protocol, allowing the RS <-> AS leg of the diagram to vary independently, as it does in OAuth. Unlike OAuth, there is a definite goal and desire in this WG to focus on some forms of interoperability for the RS <-> AS relationship, but not at the expense of its independence from the client-facing portions.

With the merging of PR #246, we have now factored out the portions of the document related to AS-RS relationships. These will now be defined in a separate draft, at:

https://github.com/ietf-wg-gnap/gnap-resource-servers <https://github.com/ietf-wg-gnap/gnap-resource-servers>

A proposed document is available for review there and will be submitted as a WG document ahead of the next interim. As a topic at the next interim, the group will discuss how to best manage issues directed at one document or the other, in order to help the conversations stay focused on the appropriate portions of the protocol space. 

Thank you,
 — Justin