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

Repository Activity Summary Bot <do_not_reply@mnot.net> Sun, 10 October 2021 08:36 UTC

Return-Path: <do_not_reply@mnot.net>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F88A3A083D for <txauth@ietfa.amsl.com>; Sun, 10 Oct 2021 01:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=E3RggOmN; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JPaRYEtI
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXMp7cvf6TDP for <txauth@ietfa.amsl.com>; Sun, 10 Oct 2021 01:35:55 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A59733A083E for <txauth@ietf.org>; Sun, 10 Oct 2021 01:35:55 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6EB5F5C0108 for <txauth@ietf.org>; Sun, 10 Oct 2021 03:38:58 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 10 Oct 2021 03:38:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject; s=fm3; bh=cfeXXJJWpFC AlXKgCgc1bV77zs/5gaMqMht5rDIUDvY=; b=E3RggOmNGyfszjGwONqc2GLCuD2 shnwHAE6CI9x7LdTrL02wW3EVzHnN7sEKI7bVo5WGLhh06qowBkpl1hRfThm6zi1 xPollgjzOclLd0Q7L85u6e2gJLt8fBURLsYxQauPfoZvJrXUY8xIMnk18/DdrZtb ByXWmBBT6TJrSoAUH1v5/o9H8Po25VDRaVFhq1SnUMSAdt01gsirEGtwmwcISn3c buh5+EQOXu0W3sscHSeGDkMsHmsShnOI5rqn/kwdela90G9STRk8bn5fYd1tG68E 5cfNYXOSPAi0d7DbiTLio0AFmE6xN/zA6z2Kd7FtF/TIz4d8sACuZDi+IbQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:from:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=cfeXXJJWpFCAlXKgCgc1bV77zs/5gaMqMht5rDIUDvY=; b=JPaRYEtI doB4cglfZ/Mfv5kZqpFqaNs4PC1vCJFLME7rj+WOmRY3kcXxOnrDrtQen5V+frs/ oHjn4tT/VC3zGJNYmiKGka+PH5DWn+tuxWGr85JPHm2hD70VraER5PXJu36I24fC K5QuS2SRPO3prJDDTVtji3Vx92BGhj6uljdZDUhbgNrX+7o/OkhpkN08tfm3IAMP UuzrxFFBAEF0bFPt982ZXyFZ70PLg7esiUhtVZ2milOzcKrEZ1QQgR9RvN0SnlJX AvCWlf4dAXK01IFBzOK8pr2sJ+sZcFPTEjdO4S05n5qKkA8pl1yG5y1pASv9zen9 plAENsaDu5C+Aw==
X-ME-Sender: <xms:kphiYR2PtdbPydOm9n_u5a7q1FDksObYS7SJ7Eiei2drg_tzJGuP2w> <xme:kphiYYEZlOagfabKJ9q7dTBfuAk4-Z6Mk_lGDmNxXEmGer1-Xn7yxJAORyyHg3Mwy kFq3O6WaaKu1_R_Dg>
X-ME-Received: <xmr:kphiYR4aRZS3syR3_ZJ-fvpmbtMSkBCNXIC5rD8gB5XYuEV_fiHRU8g_NIaH8iqDo_8gJlkLAbbwSoTK72fpO0xiPkyn5L4385gW1drRSScNlnNQEWcirXa5Z_ZvD-Y8eYA7Zg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvddtfedguddulecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecupfhoucgurghtvgcufhhivghlugculdegledmne cujfgurheptggghffvufesrgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhih ucettghtihhvihhthicuufhumhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhi esmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeu gfefhfetteevgeffkefffeetffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrd gtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:kphiYe1-bpOh1xNHutScn-1xy1wNxOR1Z49YvBCCkqZZYGJggHroJg> <xmx:kphiYUG91NA65H0WvQVA61WD2K1qQL06pHDCSnLtalVRalrAjlYgKw> <xmx:kphiYf-Wb2MqjYaA97ftdu1lJpLsp1nVBFD6zrMbspJsmUxtsac4Ow> <xmx:kphiYZTRJ4Nq-JUVxIQzlc9I81pJdT-Qx2nuEP5WYki5o81B-RkBCw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <txauth@ietf.org>; Sun, 10 Oct 2021 03:38:58 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============0450297206782767888=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: txauth@ietf.org
Message-Id: <20211010083555.A59733A083E@ietfa.amsl.com>
Date: Sun, 10 Oct 2021 01:35:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/Fp21oURVhs_9dDW_ne7gccAwPAE>
Subject: [GNAP] Weekly github digest (GNAP Weekly GitHub Activity Summary)
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: GNAP <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Oct 2021 08:36:01 -0000



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