From nobody Sun Jun  6 01:31:42 2021
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 6C9693A107E
 for <txauth@ietfa.amsl.com>; Sun,  6 Jun 2021 01:31:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level: 
X-Spam-Status: No, score=-2.797 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_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001,
 RCVD_IN_MSPIKE_WL=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=Zolc+dyf;
 dkim=pass (2048-bit key)
 header.d=messagingengine.com header.b=F7bGVPmH
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 pULpVdNGGN5H for <txauth@ietfa.amsl.com>;
 Sun,  6 Jun 2021 01:31:34 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com
 [64.147.123.24])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 3B9493A1079
 for <txauth@ietf.org>; Sun,  6 Jun 2021 01:31:34 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46])
 by mailout.west.internal (Postfix) with ESMTP id F1A0418A5
 for <txauth@ietf.org>; Sun,  6 Jun 2021 04:20:17 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
 by compute6.internal (MEProxy); Sun, 06 Jun 2021 04:20:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=
 content-type:mime-version:from:to:subject; s=fm2; bh=uwdlUVlc4vC
 oRtdNNPH3N03oAVbw0EEmymnAaIWR+ps=; b=Zolc+dyfNRqMMZUVXAaYFDCAvsO
 pj8TWl1wriMlQu8wT10BuQycv2HsmmrTUQulgPCa/7X8GIhGN4YLR8rGPPbMnPQ9
 Z21y1epCQNSKIHWnxLDwRY3XFHX9YM/Zua3hSydagmoVcVczxvVhyJZYcA+zsVKk
 qUdKm9Y6souSWu2yRT3IRyKGAZW+BrPMcrVpf3WwbmKAgSotJIowePOK5k49jOzW
 XDL5dPecSz4ngIpmlbdXsSYC4ikt9jhGgY/HdCRuprcbBMel8nRB6vj6zB84TQO6
 bYJUIrFgVhLrA/5gsraylcma4GodMNC0wy72Nl2OSt+qaERZJWX+AeMhf0Q==
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=uwdlUVlc4vCoRtdNNPH3N03oAVbw0EEmymnAaIWR+ps=; b=F7bGVPmH
 WEvpUvGwe2LQCsVECaibIgy0EYeUjl/4T9iZF+t+9tLkFlhX4uZU6K4m6aBcThSg
 vHoSY9Yj8RJJkUhG2XvmlvFXUu9L9XRZoF/CyXNpWvX/Ux4SEODY4rtPZyA+W9sq
 eAzPC2Or4thfn/k7GzyLSDScZZ01IsTdgLIHfo5gVI3Znc+XzNEzAPFSG/EABKmy
 CzmT0Hy8fo3H1lnNb8BTcycpT9a+37yqGd49lJIpPLH7oqgPRZR8A4XKSm0k1lGD
 jXMkS5gOfvhGha8DWpjSQfDc1ZFfT8WDzMkhBxl+zv8C0X0QUdZoemBqAoRkjgcC
 x1C13iL4hQWXYw==
X-ME-Sender: <xms:QYW8YKwZj_YCp8PBYTfEAd4Tz9zFYLKAxppCInocHei_ChQRbSw2Pw>
 <xme:QYW8YGSShKZtLQKXA0XiI8nkg5Bgd-Yf1x1aoaeOVwBE9FhvH-Ukza-zCBo5Gxgar
 Gj4_-1tRAPtlu54Kw>
X-ME-Received: <xmr:QYW8YMWEiKUFd5cpHJAik2I0sUoM6BPe4wWqKW2-U9B1j5t7sRo7njqsf6_bny05F1YRFeaDRq0COO0EnCOcBR5tWRrde1U7kHbx4LzpaRjn6ZL7QWf51n7cSzmUb_S-MnSSMg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedthedgtdefucetufdoteggodetrfdotf
 fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
 uceurghilhhouhhtmecufedttdenucfpohcuuggrthgvuchfihgvlhguucdlgeelmdenuc
 fjughrpegtggfhvffusegrtddtredttdejnecuhfhrohhmpeftvghpohhsihhtohhrhicu
 tegtthhivhhithihucfuuhhmmhgrrhihuceuohhtuceoughopghnohhtpghrvghplhihse
 hmnhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepkeefvdduteejvdefkeehieevuefg
 fefhteetveegffekffefteffvdelheduieetnecuffhomhgrihhnpehgihhthhhusgdrtg
 homhenucevlhhushhtvghrufhiiigvpedvnecurfgrrhgrmhepmhgrihhlfhhrohhmpegu
 ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:QYW8YAjy6KJh40lyudhkkjjC8lA0Kw48-hp7VCvEwg9aA-_ewqSsDg>
 <xmx:QYW8YMABRvJGf3NT4KjFAFa9zvajwlp-EwLbQ2eBRG4ZtLVfm1dTbQ>
 <xmx:QYW8YBLbR6uo6NelUVMeqYHCXG87c5MpEPGkS7E6Vx0ShhbZbNz6og>
 <xmx:QYW8YPOGp_Ox_0ndApXowh1LdLhJi2eZzDrr4ul0a-iNna0dkXM70g>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for
 <txauth@ietf.org>; Sun, 6 Jun 2021 04:20:17 -0400 (EDT)
Content-Type: multipart/alternative;
 boundary="===============0762553474261754699=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: txauth@ietf.org
Message-Id: <20210606083134.3B9493A1079@ietfa.amsl.com>
Date: Sun,  6 Jun 2021 01:31:34 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/pFtRSi5NlK0JTsUR_p-Vs09oMEU>
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, 06 Jun 2021 08:31:41 -0000

--===============0762553474261754699==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"

Issues
------
* ietf-wg-gnap/core-protocol (+0/-3/=F0=9F=92=AC3)
  3 issues received 3 new comments:
  - #265 What kind of control may a client have about the content of a retu=
rned access token ? (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/265=20
  - #263 Negotiation of the token format by the client should be mentioned =
in section 1.4 (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/263=20
  - #262 Should the reader understand that a RS can only be protected by a =
single AS ? (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/262=20

  3 issues closed:
  - What kind of control may a client have about the content of a returned =
access token ? https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/26=
5=20
  - Should the reader understand that a RS can only be protected by a singl=
e AS ? https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/262=20
  - Negotiation of the token format by the client should be mentioned in se=
ction 1.4 https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/263=20

* ietf-wg-gnap/gnap-resource-servers (+1/-3/=F0=9F=92=AC6)
  1 issues created:
  - The access token verifications to be perfomed by the RS should be descr=
ibed  (by Denisthemalice)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/30=20

  3 issues received 6 new comments:
  - #30 The access token verifications to be perfomed by the RS should be d=
escribed  (4 by Denisthemalice, jricher)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/30=20
  - #28 Examples about Macaroons and Biscuits are currently inappropriate  =
(1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/28=20
  - #27 Access Token Formats Negotiation (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/27=20

  3 issues closed:
  - The access token verifications to be perfomed by the RS should be descr=
ibed  https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/30=20
  - Examples about Macaroons and Biscuits are currently inappropriate  http=
s://github.com/ietf-wg-gnap/gnap-resource-servers/issues/28=20
  - Access Token Formats Negotiation https://github.com/ietf-wg-gnap/gnap-r=
esource-servers/issues/27=20




Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-gnap/core-protocol
* https://github.com/ietf-wg-gnap/gnap-resource-servers

--===============0762553474261754699==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (GNAP Weekly GitHub Activity Summary)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
</style>
</head>

<body>
<h1>Sunday June 06, 2021</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>ietf-wg-gnap/core-protocol (+0/-3/=F0=9F=92=AC3)</h3>

  <p>3 issues received 3 new comments:</p>
  <ul>
  <li>#265 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/265">What kind of control may a client have about the content of a ret=
urned access token ?</a> (1 by jricher) </li>
 =20
  <li>#263 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/263">Negotiation of the token format by the client should be mentioned=
 in section 1.4</a> (1 by jricher) </li>
 =20
  <li>#262 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/262">Should the reader understand that a RS can only be protected by a=
 single AS ?</a> (1 by jricher) </li>
  </ul>

  <p>3 issues closed:</p>
  <ul>
  <li>#265 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/265">What kind of control may a client have about the content of a ret=
urned access token ?</a> </li>
 =20
  <li>#262 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/262">Should the reader understand that a RS can only be protected by a=
 single AS ?</a> </li>
 =20
  <li>#263 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/263">Negotiation of the token format by the client should be mentioned=
 in section 1.4</a> </li>
  </ul>

<h3>ietf-wg-gnap/gnap-resource-servers (+1/-3/=F0=9F=92=AC6)</h3>
  <p class=3D"new">1 issues created:</p>
  <ul>
  <li>#30 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/30">The access token verifications to be perfomed by the RS should b=
e described </a> (by Denisthemalice) </li>
  </ul>

  <p>3 issues received 6 new comments:</p>
  <ul>
  <li>#30 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/30">The access token verifications to be perfomed by the RS should b=
e described </a> (4 by Denisthemalice, jricher) </li>
 =20
  <li>#28 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/28">Examples about Macaroons and Biscuits are currently inappropriat=
e </a> (1 by jricher) </li>
 =20
  <li>#27 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/27">Access Token Formats Negotiation</a> (1 by jricher) </li>
  </ul>

  <p>3 issues closed:</p>
  <ul>
  <li>#30 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/30">The access token verifications to be perfomed by the RS should b=
e described </a> </li>
 =20
  <li>#28 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/28">Examples about Macaroons and Biscuits are currently inappropriat=
e </a> </li>
 =20
  <li>#27 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/27">Access Token Formats Negotiation</a> </li>
  </ul>




<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/ietf-wg-gnap/core-protocol">https://git=
hub.com/ietf-wg-gnap/core-protocol</a></li>
  <li><a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers">htt=
ps://github.com/ietf-wg-gnap/gnap-resource-servers</a></li>
  </ul>
</body>
</html>

--===============0762553474261754699==--

