[GNAP] Editors' Updates

[Justin Richer <[e-mail]>]

The editors met today and have processed a number of issues and pull requests.


The following pull requests have been reviewed by the editors and are marked Pending Merge:

#229: update subject info definition according to sub_ids
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/229 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/229>

#232: JWK definition
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/232 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/232>

#242: Gathering consent and authorization through interaction and other means
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242>

#246: Extract RS-focused protocol elements
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246>

#247: Appendix on protocol rationale
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/247 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/247>

Several issues will be closed when these pull requests are merged. 



The following issues have been marked as Pending Close:

#185: Protected and Public Resources
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/185 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/185>

#189: Token format
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/189 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/189>

#190: Tentative proposal for a RS discovery mechanism
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/190 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/190>

#191: Validity of an access token
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/191 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/191>

#203: Requesting resources with insufficient access
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/203 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/203>

#210: “sub_id” claims
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/210 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/210>

#212: Definition of a Resource Server (RS)
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/212 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/212>

#213: Definition and roles of a Resource Owner (RO)
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/213 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/213>

#237: How can a client identify which ASs are trusted by the RS ?
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/237 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/237>

#238: Concept of a “service” supported by a set of RSs
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/238 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/238>

#240: Scalability and prior relationships between ASs and RSs
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/240 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/240>

#241: Unlinkability
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/241 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/241>



Additionally, the editors have gone through the issue tracker and closed a number of duplicate issues. 



Unless there is substantive disagreement from the working group, these actions will be taken in one week from today on April 21. In particular, please review the pull requests, and feel free to suggest improvements. However, please keep in mind that the goal of each PR is not to be perfect and address all known problems but rather to move things forward from where they are now.



As a reminder, we’ve got the next GNAP Interim meeting on May 6th. The editors are looking to publish the next revision of the spec a week ahead of that meeting, to give everyone a chance to read the new draft in its entirety.

 — Justin, Aaron, and Fabien