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

Repository Activity Summary Bot <do_not_reply@mnot.net> Sun, 18 July 2021 08:11 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 A34013A145C for <txauth@ietfa.amsl.com>; Sun, 18 Jul 2021 01:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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=oVMYQ8GR; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=MNMS5SvO
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 sON8dQ51sSlE for <txauth@ietfa.amsl.com>; Sun, 18 Jul 2021 01:11:00 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 221113A145D for <txauth@ietf.org>; Sun, 18 Jul 2021 01:10:59 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id AE95B5C0105 for <txauth@ietf.org>; Sun, 18 Jul 2021 03:34:20 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 18 Jul 2021 03:34:20 -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=8zh799Mx+YT 4SgGlYKLhZFmUv978+ITjaDeSJZq5/5o=; b=oVMYQ8GRX8MKZX7EvkbySzwBkds 9IKNWhMMiyoIgQuaNFqtugzxTwmWapKSjZyZrclf/msR+Lab80A2FO3ALAXvWd9I bsI258RnegwQN5aCxquc7cwpOPssXUgdmzHOiTahlwtWmBzjRkmXBiOULGxUSkMK 3m7R8PDFY97y9W2Uf1FzPDtwCvcQ+R771pBa9gR3tWpkdW4vWz/Q3FFhZTGbM3Ee LmAq0F2zCBjVLEWb0QEkg+3CBd4GH+fhOVpARAYVZPJeQoIMXLnee4Ksi81yh/rC HW2xx3G+9clXhjTaR3h1UHGsvHGUKDUZDiYY7vWGjizzTNs6xSSN+IoHXeA==
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= fm3; bh=8zh799Mx+YT4SgGlYKLhZFmUv978+ITjaDeSJZq5/5o=; b=MNMS5SvO HhGFYtz/KecEFrn9uZXaeq9OvjZnhUEdPWvtiRF3V3/ECNkKp3nKH25UwTiSLp3j JCkJpuLWduhcIpWxlndfrwu5FM16l0a0dALSr59KDjyV0gReILuDFMdPYQTaynPQ cl+68/7pj0GHrzKFDv5lgwYFE2m1javb2UETCIRVba9zGi32IiByroUKAy5ruw3q OCr6JnUFO7bXIsSAwrEFGhxRiKZd5zuLVppuSiO8vnBZXnJHDpylf0hhJXQkH4ui 5jZA545ZGq7CwXrrmolJflWR4AEpxh2h6kWR2yy3QKab+vwKrto3bHt6KJAG9rU7 Kg5wp9Oth6SyAQ==
X-ME-Sender: <xms:fNnzYPSN_Tn-RoiiysVwXCQ40HKEzcgNtPFjRjMbn3zozRX6HCejuw> <xme:fNnzYAzFZDtiwSct24FmZ5NUCBS5Kjbdl-IgQKXDVt4TnW4f18CKz2_9y_1Ph6_Hl yHUJc1r4Rbd1X6CPw>
X-ME-Received: <xmr:fNnzYE0GYdm8MhixO3J4MFnFUSxIFIDL0fbBoDTmvZSlXzHIT6wKf7bOHqx4gQBopWxZ8l3uJrflDeWxMGronK9PawOO9cDy5g4JEvhykEwb-yucNpeKg8UnuqVs5P3pG54aXA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvdejgdduudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecupfhoucgurghtvgcufhhivghlugculdegledmnecujf gurheptggghffvufesrgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhihucet tghtihhvihhthicuufhumhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhiesmh hnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeugfef hfetteevgeffkefffeetffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrdgtoh hmnecuvehluhhsthgvrhfuihiivgepvdenucfrrghrrghmpehmrghilhhfrhhomhepugho pghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:fNnzYPBI2JMGyHvqaZ-l0gKlRUWHN0LBDdWmUuej3irTOSxDX03Tlw> <xmx:fNnzYIhyIt4GZsFtW9fLqn-Y987GbbS2HZxkEYV0oye_bHvfzZUHtA> <xmx:fNnzYDqQ141osj7EOkNPgw9BfvG-Is6WN-lLRia7E4VqAjDGQqOMMQ> <xmx:fNnzYLtIBsrZb3W7LG2nm-gqmS1oYHJ_5bTtSjjoq9HYzzghnxvkAw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <txauth@ietf.org>; Sun, 18 Jul 2021 03:34:20 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============7226397037936638696=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: txauth@ietf.org
Message-Id: <20210718081100.221113A145D@ietfa.amsl.com>
Date: Sun, 18 Jul 2021 01:10:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/VT5ThcDuZhrIbtWdt4RJ3JNawlM>
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, 18 Jul 2021 08:11:06 -0000



Events without label "editorial"

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

  1 issues received 1 new comments:
  - #134 Guidance for Extensions (1 by yaronf)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/134 

  1 issues closed:
  - Mutual exclusivity of instance identifier https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/45 

* ietf-wg-gnap/gnap-resource-servers (+4/-6/💬0)
  4 issues created:
  - Accessing a secondary RS from a primary RS (by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/42 
  - In section 3.4,  "token_format_required" should be changed into"token_formats_supported" (by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/41 
  - Insufficient description of two fields from RS-facing AS Discovery (editorial) (by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/40 
  - “RS-Facing API” versus “AS-Facing API” (by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/39 

  6 issues closed:
  - Ref in Terminology https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/14 [Editorial] 
  - A section describing the structure of the list of token formats is currently missing https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/29 
  - Token Introspection security check https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/20 
  - Token Introspection https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/24 
  - Token Introspection API: level of detail https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/19 
  - RS-registered resource reference handle arity https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/22 



Pull requests
-------------
* ietf-wg-gnap/core-protocol (+2/-7/💬6)
  2 pull requests submitted:
  - pre 06 editorial cleanup (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/275 
  - add did example (by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/274 

  5 pull requests received 6 new comments:
  - #275 pre 06 editorial cleanup (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/275 [Editorial] 
  - #274 add did example (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/274 
  - #272 trim oauthpop (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/272 
  - #271 trim dpop (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/271 
  - #270 Trim features. (2 by jricher, yaronf)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/270 [Pending Merge] 

  7 pull requests merged:
  - pre 06 editorial cleanup
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/275 [Editorial] 
  - add did example
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/274 [Editorial] 
  - refactor token response details to use flags array
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/273 [Pending Merge] 
  - trim oauthpop
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/272 [Pending Merge] 
  - trim dpop
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/271 [Pending Merge] 
  - Trim features.
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/270 [Pending Merge] 
  - split interaction methods discovery value
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/269 [Pending Merge] 

* ietf-wg-gnap/gnap-resource-servers (+2/-7/💬5)
  2 pull requests submitted:
  - Several pretty minor edits after I read through this doc. (by adeinega)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/38 
  - pre 01 editorial cleanup (by jricher)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/37 

  3 pull requests received 5 new comments:
  - #38 Several pretty minor edits after I read through this doc. (3 by adeinega, jricher, netlify)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/38 [Editorial] 
  - #37 pre 01 editorial cleanup (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/37 [Editorial] 
  - #31 gnap terminology ref (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/31 [Editorial] 

  7 pull requests merged:
  - pre 01 editorial cleanup
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/37 [Editorial] 
  - expanded RS authentication discussion, with examples
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/36 [Pending Merge] 
  - added access token format registry
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/35 [Pending Merge] 
  - expanded introspection details
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/34 [Pending Merge] 
  - expanded RS resource set registration protocol
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/33 [Pending Merge] 
  - updated discovery definitions
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/32 [Pending Merge] 
  - gnap terminology ref
    https://github.com/ietf-wg-gnap/gnap-resource-servers/pull/31 [Editorial] 


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