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

From: Repository Activity Summary Bot <[email-masked]>
Date: Sun, 10 Oct 2021 01:35:55 -0700 (PDT)

Events without label "editorial"

Issues
------
* ietf-wg-gnap/core-protocol (+1/-19/💬23)
  1 issues created:
  - Short term and long term RS user accounts (by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/322 

  19 issues received 23 new comments:
  - #322 Short term and long term RS user accounts (3 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/322 
  - #298 Untrusted security-critical information from the Client (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/298 
  - #292 Does a client instance really need to be identified by a unique key ? (3 by Denisthemalice, aaronpk, fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/292 
  - #290 Checks needed to defeat user collaborative attacks are unfortunately out of the scope of the document (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/290 
  - #289 Bearer tokens should not be supported or be deprecated (1 by aaronpk)
    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 (1 by fimbault)
    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 
  - #285 The diagram of the exchanges is mandating a pre-configuration between each pair of AS/RS (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/285 
  - #253 Discuss MTLS deployment differences (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/253 
  - #249 Privacy Considerations for Subject Identifiers (1 by aaronpk)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/249 
  - #221 DID as identifier (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/221 [Needs Text] 
  - #215 User choice and consent, and user notice (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/215 
  - #214 Trust relationships (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/214 
  - #175 GNAP for Custodial SSI Wallets (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/175 
  - #169 User-to-user delegation (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/169 
  - #168 message based interaction / DIDComm (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/168 
  - #154 Common means to dereference key references (1 by aaronpk)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/154 
  - #149 Special label for access token used for continuation (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/149 
  - #133 Privacy considerations (1 by aaronpk)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/133 

  19 issues closed:
  - Terminology: definition for "key proof" https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/159 [Design] 
  - Define which "resources" fields are optional https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/167 
  - message based interaction / DIDComm https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/168 
  - User-to-user delegation https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/169 
  - GNAP for Custodial SSI Wallets https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/175 
  - Trust relationships https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/214 
  - User choice and consent, and user notice https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/215 
  - DID as identifier https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/221 [Needs Text] 
  - Privacy considerations https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/133 
  - Privacy Considerations for Subject Identifiers https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/249 
  - Discuss MTLS deployment differences https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/253 
  - How can an AS determine "what is needed" to fulfill the request ? https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/264 
  - The diagram of the exchanges is mandating a pre-configuration between each pair of AS/RS https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/285 
  - About the locations field https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/287 
  - Since both rights and resource locations must be disclosed to the AS, the AS can act as Big Brother https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/288 
  - Bearer tokens should not be supported or be deprecated https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/289 
  - Checks needed to defeat user collaborative attacks are unfortunately out of the scope of the document https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/290 
  - Does a client instance really need to be identified by a unique key ? https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/292 
  - Token Management functions are over-engineering https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/293 

* ietf-wg-gnap/gnap-resource-servers (+0/-4/💬1)
  1 issues received 1 new comments:
  - #2 The Abstract and the Introduction should be aligned (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/2 [Editorial] 

  4 issues closed:
  - RS Token derivation https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/23 
  - The Abstract and the Introduction should be aligned https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/2 [Editorial] 
  - “RS-Facing API” versus “AS-Facing API” https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/39 [Pending Close] 
  - Trust relationships between a RS and an AS https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/7 

Pull requests
-------------
* ietf-wg-gnap/core-protocol (+9/-3/💬22)
  9 pull requests submitted:
  - Replace remaining occurrences of "callback" (by pq2)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/321 
  - Add contributor (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/320 
  - inline definition of "key proof" (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/319 
  - Add link to authorization processing section in diagram. (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/318 
  - Add security considerations for message-level signatures (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/317 
  - Replace "split field" with "split flag" (by pq2)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/316 
  - Fix description of interaction start modes (by pq2)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/315 
  - Remove 'bearer' (by pq2)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/314 
  - Replace 'push' with 'finish' (by pq2)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/313 

  11 pull requests received 22 new comments:
  - #321 Replace remaining occurrences of "callback" (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/321 
  - #320 Add contributor (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/320 [Editorial] 
  - #319 inline definition of "key proof" (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/319 [Editorial] 
  - #318 Add link to authorization processing section in diagram. (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/318 [Editorial] 
  - #317 Add security considerations for message-level signatures (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/317 
  - #316 Replace "split field" with "split flag" (3 by jricher, netlify, pq2)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/316 [Editorial] 
  - #315 Fix description of interaction start modes (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/315 
  - #314 Remove 'bearer' (2 by jricher, netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/314 [Editorial] 
  - #313 Replace 'push' with 'finish' (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/313 
  - #306 initial draft of trust relationships (9 by Denisthemalice, agropper, fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/306 [Pending Merge] 
  - #304 Security Considerations (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/304 [Pending Merge] 

  3 pull requests merged:
  - inline definition of "key proof"
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/319 [Editorial] 
  - Add link to authorization processing section in diagram.
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/318 [Editorial] 
  - Add security considerations for message-level signatures
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/317 

* ietf-wg-gnap/gnap-resource-servers (+1/-0/💬1)
  1 pull requests submitted:
  - Change apostrophes to backticks (by pq2)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/44 

  1 pull requests received 1 new comments:
  - #44 Change apostrophes to backticks (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/44 

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