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

Repository Activity Summary Bot <do_not_reply@mnot.net> Sun, 18 April 2021 08:21 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 21E9B3A11CA for <txauth@ietfa.amsl.com>; Sun, 18 Apr 2021 01:21:08 -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=NYpR+1Aa; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=NVyWNLmA
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 v3GchBBTLzpy for <txauth@ietfa.amsl.com>; Sun, 18 Apr 2021 01:21:01 -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 AE6263A11CB for <txauth@ietf.org>; Sun, 18 Apr 2021 01:21:01 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EDD885C06A5 for <txauth@ietf.org>; Sun, 18 Apr 2021 03:41:49 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 18 Apr 2021 03:41:49 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm2; bh=Tju4aHwe1fJBd1oHxl2/5s0O/VnMImmluJcBiMcRE9w=; b=NYpR+1Aa mY6D2YsnPJGoZi8s4yYFvLHxj4Wx0ZT9GqO62UcXG3rs2L2Xm1JQTxcdzbiO6CUp 7PaiGNVFM4IO8eSJNi3st1ZwYMaosoLKxnUpGXofNwgNqxGQr6MYyBb9PPcJIpDF DtvctSQN3uMxL+it7J8xGkdINQljAloHPotz8beOptY/upfp/vk5IbEiy18+YfSq gn5OJRd+3OkKJoKHgfmkk+GrgLQZqqJBXMRXIr7GUXdAekk0oLOd0Y9RIbFi+YlM jNG0dNUP+OUcha5niraRw0r3vGHVWUIdD8mlJQJNWxP1tZ482Kq8AiybAXkMTQtU cDTJE44hOMWk1g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Tju4aHwe1fJBd1oHxl2/5s0O/VnMI mmluJcBiMcRE9w=; b=NVyWNLmA0IAA0kImcyoX/YnqPFantZnFVEZvCyxSaxO46 DVyQm08S6ZVwMn1gsNWJVFImeJRUb+WN5akeMtSjOSdLqumVdCImNAsSpoXPB65Z firFBVr25rOXzmYC4Kl2qnZ7prCRFpPWMYMJZP3G3JTaNiplU5P660H9ajeQRmlq sIaeimXPIglcbsZd3P+6trb4VLArgly91c+f2lm7q1vKdsw+cUGsBR+9Wg7b99UJ WtqVibwl/Otw8xF0YKVxMVQQ7VPddRfZP7WC5R/E7snlo7K7ZOn4Xb6wdy9xbPsK YmhHP00bw8KAHUnisIloCH6LaSBDtfy0BUt8++1zA==
X-ME-Sender: <xms:veJ7YBcwJ4cb9fYwWrpLZHjJV3zLqFO6xlbKAA0KsvTF_3BaYnbExQ> <xme:veJ7YPM_DlDyNL41tWw_lnjyVWoMkCP_IWr9iWHczeu8G17vM3iP0HSq5wK79Pv5p rDzKJNg0jLL4iTH6A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudelkedgvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfhvffusegrtddtredttdejne cuhfhrohhmpeftvghpohhsihhtohhrhicutegtthhivhhithihucfuuhhmmhgrrhihuceu ohhtuceoughopghnohhtpghrvghplhihsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepkeefvdduteejvdefkeehieevuefgfefhteetveegffekffefteffvdelheduieet necuffhomhgrihhnpehgihhthhhusgdrtghomhenucfkphephedvrddufeekrdekhedrle dvnecuvehluhhsthgvrhfuihiivgepjeenucfrrghrrghmpehmrghilhhfrhhomhepugho pghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:veJ7YKjk6Yii6hnVWAdgzg1JnX-1fABsjdmWL534s_6G6sLo9jpbyQ> <xmx:veJ7YK-3yC6qak-i6a99V8OnIyi5WAaWYXWaxXpGyuaLNEPfHUwZwA> <xmx:veJ7YNszFZTX4GSaK7HUBV6F8LALjJRUusACrV6K4I6OAIeWDPZKiQ> <xmx:veJ7YOVplwrZedpUh4wVZYd6FOmQFyRJrMqSmB5RJ2AF6Ge19GJ2FQ>
Received: from [10.1.0.164] (unknown [52.138.85.92]) by mail.messagingengine.com (Postfix) with ESMTPA id B54F91080064 for <txauth@ietf.org>; Sun, 18 Apr 2021 03:41:49 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============7996708468279517806=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: txauth@ietf.org
Message-Id: <20210418074149.B54F91080064@mailuser.nyi.internal>
Date: Sun, 18 Apr 2021 03:41:49 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/YF8pGDSz7Yguu1VeAJVUH3eXFTw>
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 Apr 2021 08:21:08 -0000



Events without label "editorial"

Issues
------
* ietf-wg-gnap/core-protocol (+3/-10/💬58)
  3 issues created:
  - Interaction (1) between the Client Instance and the RS as described in the first figure (by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/252 
  - Privacy Considerations for Subject Identifiers (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/249 
  - Be consistent with OAuth 2.0 (not OAuth 2) (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/248 [Editorial] 

  26 issues received 58 new comments:
  - #244 Refactoring the internals of access request (13 by Denisthemalice, agropper, fimbault, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/244 
  - #241 Unlinkability (3 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/241 [Pending Close] 
  - #240 Scalability and prior relationships between ASs and RSs  (3 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/240 [Pending Close] 
  - #239 Access token format(s) negotiation (2 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/239 
  - #238 Concept of a "service" supported by a set of RSs (3 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/238 [Pending Close] 
  - #237 How can a client identify which ASs are trusted by the RS ? (4 by Denisthemalice, agropper, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/237 [Pending Close] 
  - #233 The case of attributes should be addressed (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/233 
  - #225 Explicit typing for jws and jwsd key proofing mechanisms (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/225 
  - #222 paramaters x5c and x5t#S256 and GNAP key formats (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/222 [Pending Close] 
  - #213 Definition and roles of a Resource Owner (RO) (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/213 
  - #212 Definition of a Resource Server (RS) (1 by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/212 [Pending Close] 
  - #210 "sub_id" claims (3 by Denisthemalice, aaronpk, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/210 [Pending Close] 
  - #203 Requesting resources with insufficient access (4 by Denisthemalice, aaronpk, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/203 [Pending Close] 
  - #201 Include body hash in Detached JWS (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/201 
  - #198 Definition of a Subject in section 1.3 (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/198 [Pending Close] 
  - #196 Proving Possession of a Key for the AS and RS (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/196 
  - #193 Requesting Resources With Insufficient Access (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/193 
  - #191 Validity of an access token (2 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/191 [Pending Close] 
  - #190 Tentative proposal for a RS discovery mechanism (2 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/190 [Pending Close] 
  - #189 Token format (2 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/189 [Pending Close] 
  - #188 Prior relationship or not between a RS and an AS (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/188 
  - #187 The case of a RS trusting more that one AS (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/187 
  - #186 User consent and user notice (2 by fimbault, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/186 
  - #185 Protected and Public Resources (2 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/185 [Pending Close] 
  - #176 Protocol rationale (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/176 
  - #133 Privacy considerations (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/133 

  10 issues closed:
  - Explicit typing for jws and jwsd key proofing mechanisms https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/225 
  - Prior relationship or not between a RS and an AS https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/188 
  - The case of a RS trusting more that one AS https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/187 
  - Access token format(s) negotiation https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/239 
  - The case of attributes should be addressed https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/233 
  - User consent and user notice https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/186 
  - Requesting Resources With Insufficient Access https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/193 
  - Definition of a Subject in section 1.3 https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/198 [Pending Close] 
  - paramaters x5c and x5t#S256 and GNAP key formats https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/222 [Pending Close] 
  - Use of identifiers as communication channels https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/42 



Pull requests
-------------
* ietf-wg-gnap/core-protocol (+5/-4/💬18)
  5 pull requests submitted:
  - Not 'push' but 'finish' is used to provide nonce value during interact response (by romabaz)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/251 
  - Cryptographic Key Proofing Updates (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/250 
  - Appendix on protocol rationale (by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/247 
  - Extract RS-focused protocol elements (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246 
  - Continuation information was stored on the step (2) not (3) (by romabaz)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/245 

  6 pull requests received 18 new comments:
  - #251 Not 'push' but 'finish' is used to provide nonce value during interact response (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/251 
  - #250 Cryptographic Key Proofing Updates (3 by jricher, netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/250 
  - #247 Appendix on protocol rationale (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/247 
  - #246 Extract RS-focused protocol elements (9 by adeinega, jricher, netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246 
  - #245 Continuation information was stored on the step (2) not (3) (2 by fimbault, netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/245 
  - #227 Replace parameter "ts" by "iat" for jws and jwsd key proofing mechanisms. (2 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/227 [Pending Close] 

  4 pull requests merged:
  - Continuation information was stored on the step (2) not (3)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/245 [Editorial] 
  - replacing email by opaque in examples
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/228 [Pending Merge] 
  - The "typ" parameter for jws and jwsd key proofing mechanisms.
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/226 [Pending Merge] 
  - change subject type to format to comply with secevent draft07
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/220 [Pending Merge] 


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