Subject: [GNAP] Weekly github digest (GNAP Weekly GitHub Activity Summary)

From: Repository Activity Summary Bot <[email-masked]>
Date: Sun, 25 Jul 2021 00:40:58 -0700 (PDT)

Events without label "editorial"

Issues
------
* ietf-wg-gnap/core-protocol (+2/-12/💬68)
  2 issues created:
  - Re-opening of: In practice, only rights are supported but attributes should also be supported (by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/296 
  -   In practice, only rights are supported but attributes should also be supported (by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/295 

  23 issues received 68 new comments:
  - #296 Re-opening of: In practice, only rights are supported but attributes should also be supported (11 by Denisthemalice, aaronpk, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/296 
  - #295   In practice, only rights are supported but attributes should also be supported (6 by Denisthemalice, jricher, yaronf)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/295 
  - #293 Token Management functions are over-engineering (3 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/293 
  - #292 Does a client instance really need to be identified by a unique key ? (3 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/292 
  - #291 Requesting RO Information or Requesting Subject Information? (2 by Denisthemalice, fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/291 
  - #290 Checks needed to defeat user collaborative attacks are unfortunately out of the scope of the document (14 by Denisthemalice, aaronpk, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/290 
  - #289 Bearer tokens should not be supported or be deprecated (5 by Denisthemalice, aaronpk, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/289 
  - #288 Since both rights and resource locations must be disclosed to the AS, the AS can act as Big Brother (4 by Denisthemalice, agropper, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/288 
  - #287 About the locations field (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/287 
  - #286 In practice, only rights are supported but attributes should also be supported (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/286 
  - #285 The diagram of the exchanges is mandating a pre-configuration between each pair of AS/RS (2 by fimbault, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/285 
  - #284 The document is confusing a Resource Server (RS) with a Protected Resource (2 by aaronpk, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/284 
  - #283 User consent is not supported (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/283 
  - #282 The client has no effective control upon the content of an access token (2 by aaronpk, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/282 
  - #281 The client is unable to know that a RS is associated with more than one AS (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/281 
  - #280 The access token is opaque to the client instance: transparency cannot be achieved (2 by aaronpk, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/280 
  - #279 Trust relationships between ROs and ASs and between ROs and RSs are left undefined (2 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/279 
  - #278 Trust relationships are still undefined (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/278 
  - #277 No access token structure is being defined or referenced (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/277 
  - #276 The document is currently unable to follow the standards track  (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/276 
  - #244 Refactoring the internals of access request (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/244 
  - #215 User choice and consent, and user notice (1 by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/215 
  - #214 Trust relationships (1 by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/214 

  12 issues closed:
  - Refactoring the internals of access request https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/244 
  - Trust relationships between ROs and ASs and between ROs and RSs are left undefined https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/279 
  -   In practice, only rights are supported but attributes should also be supported https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/295 
  - The document is currently unable to follow the standards track  https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/276 
  - No access token structure is being defined or referenced https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/277 
  - Trust relationships are still undefined https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/278 
  - The access token is opaque to the client instance: transparency cannot be achieved https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/280 
  - The client is unable to know that a RS is associated with more than one AS https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/281 
  - The client has no effective control upon the content of an access token https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/282 
  - User consent is not supported https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/283 
  - The document is confusing a Resource Server (RS) with a Protected Resource https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/284 
  - In practice, only rights are supported but attributes should also be supported https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/286 

* ietf-wg-gnap/gnap-resource-servers (+0/-0/💬1)
  1 issues received 1 new comments:
  - #39 “RS-Facing API” versus “AS-Facing API” (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/39 

Pull requests
-------------
* ietf-wg-gnap/core-protocol (+2/-1/💬2)
  2 pull requests submitted:
  - added editorconfig processor (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/297 
  - add editorconfig (by aaronpk)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/294 

  2 pull requests received 2 new comments:
  - #297 added editorconfig processor (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/297 
  - #294 add editorconfig (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/294 

  1 pull requests merged:
  - add editorconfig
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/294 

* ietf-wg-gnap/gnap-resource-servers (+1/-2/💬1)
  1 pull requests submitted:
  - adds .editorconfig and cleans up trailing spaces (by aaronpk)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/43 

  1 pull requests received 1 new comments:
  - #43 adds .editorconfig and cleans up trailing spaces (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/43 

  2 pull requests merged:
  - adds .editorconfig and cleans up trailing spaces
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/43 [Editorial] 
  - Several pretty minor edits after I read through this doc.
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/38 [Editorial] 

Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-gnap/core-protocol
* https://github.com/ietf-wg-gnap/gnap-resource-servers