From nobody Fri Apr 2 00:33:45 2021 Return-Path: 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 2FE423A36C7 for ; Fri, 2 Apr 2021 00:33:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 DhqSjzuirq7W for ; Fri, 2 Apr 2021 00:33:41 -0700 (PDT) Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 859A23A36C8 for ; Fri, 2 Apr 2021 00:33:41 -0700 (PDT) Received: by mail-io1-xd2a.google.com with SMTP id k8so2164238iop.12 for ; Fri, 02 Apr 2021 00:33:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xPD1RLpnR8Eob9sqZ1zjmAIKa/ytmtRUS36XdbhUl0A=; b=CCcLQSP0/Qi/ltz6WkRr5ZEcsm83Xm/+oFDQfosT0B1rUS9gqJu3VuwKT3M9t5//EQ LZTE7cL2dMnM74a6yui/H9ClUcjVxXplYhRE72CP81V1jB6+/iin8Xfpqp4XoryCmJZL cKWGMwKERGfqPE5C0HCf8hko19TAG69pel5G0T80J9F5CYKPtfM/2Y+sVA9c94NJZ0fg UzBG8eZqC4YyGZXFOsg+hE+ha3OGVVofpvoUjdDYOijz0JlpbXnX9dPdD2Hd7A35u0uh gmFX/e7K0UHo4bLmkLxE1c1DdW/EAbQt5I/MrOG2/p4zZLuqilVp/OX4YSuTFeW4lchC oC0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xPD1RLpnR8Eob9sqZ1zjmAIKa/ytmtRUS36XdbhUl0A=; b=iRqe3nlJPAuFOru6ba+i6ZZxufm1GF7hau5S+304jXid0I1gzJPW3nz+qA7avvgfMO gz72PP35Xs5IDGnyyahbWRdk/TrIllUqzK3aN6CuFzGBPBVH8puLzRy0NMXRbdup8usf g+UnLakXAFtqilgsen+9HlZ+C5Kf7vHwwtliW62WHWSC7TrN2PoNAD4rJqIoMNWZ/lnK uIXN80lVymKrUo5j2sAa2V5DgvjLbQwLn2YPEPe8vFVxitYiZTG8NIjacPNS0VnvTxBW 7GDVoYeIIbDXBGWPIibLgJ/LJiSeI1YnWHW2Rfrx59lWwVcBU4T9AC9eV6Fs9cgFuELd /SYg== X-Gm-Message-State: AOAM533yq3jYuZcTcuTx69H5mW6ZkXYsz1Mn6C/vI7GKL46umq4+p+EB PNKsf4z2aE0dzRe42OmeLgT/bodA/ZM5BnSgN4BmiF922snDxw== X-Google-Smtp-Source: ABdhPJx8/mbA9O+zGCRzxygJp+5h/kZxTIylpuBoaIIviCdhOHseYaKPkQZEySyFiKUOnCcCY08jhal/x4t/uiNLFS8= X-Received: by 2002:a05:6638:224e:: with SMTP id m14mr12062004jas.8.1617348819854; Fri, 02 Apr 2021 00:33:39 -0700 (PDT) MIME-Version: 1.0 From: Fabien Imbault Date: Fri, 2 Apr 2021 09:33:28 +0200 Message-ID: To: GNAP Mailing List Content-Type: multipart/alternative; boundary="000000000000e2a8ee05bef85dee" Archived-At: Subject: [GNAP] Editorial update X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Apr 2021 07:33:44 -0000 --000000000000e2a8ee05bef85dee Content-Type: text/plain; charset="UTF-8" Hi everyone, Here's the summary of the last editorial review of issues and PRs. As usual, please comment in the coming week. *PRs now pending merge:* - Change subject type to format to comply with secevent draft07 https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/220 - The "typ" parameter for jws and jwsd key proofing mechanisms https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/226 Please note that this PR raised a new issue #231 on the verification side. - Replacing email by opaque in examples https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/228 *PRs pending close:* - Replace parameter "ts" by "iat" for jws and jwsd key proofing mechanisms https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/227 Please note that there's on-going discussion on the name to be used. *Update on issues :* - paramaters x5c and x5t#S256 and GNAP key formats is pending close https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/222 - Definition of a Subject in section 1.3 is pending close https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/198 - DID as identifier is need text https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/221 As an exception, the editors won't apply the one week period on this substantive item. But we would need some contributions to get forward. Cheers Justin, Aaron and Fabien --000000000000e2a8ee05bef85dee Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi everyone,

Here's the summary= of the last editorial review of issues and PRs. As usual, please comment i= n the coming week.=C2=A0

PRs now pending merge:=
- Change subject type to format to comply with secevent draf= t07=C2=A0

-=C2=A0The "typ" parameter for= jws and jwsd key proofing mechanisms
Please note that this PR ra= ised a new issue #231 on the verification side.=C2=A0

<= div>- Replacing email by opaque in examples

PRs= pending close:
-=C2=A0Replace parameter "ts" by &q= uot;iat" for jws and jwsd key proofing mechanisms
Please not= e that there's on-going discussion on the name to be used.
Update on issues :
-=C2=A0=C2=A0paramaters x5= c and x5t#S256 and GNAP key formats is pending close

- Definition of a Subject in section 1.3 is pending close
= =

-=C2=A0DID as identifier is need text
<= a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/221">ht= tps://github.com/ietf-wg-gnap/gnap-core-protocol/issues/221
As an exception, the editors won't apply the one week period on this= substantive item. But we would need some contributions to get forward.

Cheers
Justin, Aaron and Fabien
<= br>
--000000000000e2a8ee05bef85dee-- From nobody Fri Apr 2 10:01:06 2021 Return-Path: X-Original-To: txauth@ietf.org Delivered-To: txauth@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D5D83A1D32; Fri, 2 Apr 2021 10:01:04 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IESG Secretary To: "IETF-Announce" Cc: txauth@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.27.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <161738286447.31292.8790971017092614075@ietfa.amsl.com> Date: Fri, 02 Apr 2021 10:01:04 -0700 Archived-At: Subject: [GNAP] Grant Negotiation and Authorization Protocol (gnap) WG Virtual Meeting: 2021-05-06 X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Apr 2021 17:01:05 -0000 The Grant Negotiation and Authorization Protocol (gnap) WG will hold a virtual interim meeting on 2021-05-06 from 15:00 to 16:00 UTC. Agenda: (No agenda submitted) Information about remote participation: https://intuit.zoom.us/j/91960243935?from=addon From nobody Sun Apr 4 01:01:09 2021 Return-Path: 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 607F83A1BF6 for ; Sun, 4 Apr 2021 01:01:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.216 X-Spam-Level: * X-Spam-Status: No, score=1.216 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=fnJ8dQbh; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=GExVFxL3 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 1g9tBn_oMwDg for ; Sun, 4 Apr 2021 01:00:59 -0700 (PDT) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 141773A1BF5 for ; Sun, 4 Apr 2021 01:00:58 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 77F9B5C00A7 for ; Sun, 4 Apr 2021 03:43:30 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 04 Apr 2021 03:43:30 -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=nNIwHsICxGXjoeSHe/u0yTgooCgO3i5OZfsETKYgAyk=; b=fnJ8dQbh tp1W8htYNb39kSPY+M+5OU+6kM/CJoExvC0NsFfNVyGeogGvoz1cz+rKycp+4zFl QVYPOY6qUqdeGh1/0f3NhZzxfG+Mjo3gLSnA0EtsoiuXMpqm4uhsW+qweNjjZk64 DfGq3EKs03b2QPXWs9QhbZvdm2YnBek6OLXy+Hcxe+94tKWn6wfPhbjmyopa4Kxp 2U9AHAP6JF59Ox1ktQAhtOBEnjAZyDZqdoBCiYFFENIPlOHFpsqDPOyDeoo0UHX2 iZS/gobgUMZNcxiGZkU+42Eg6NL4h6KR7KHGGhC4B2YP6O2w493uOm75Z88dzw5C lwHCyB/j0xu4BQ== 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=nNIwHsICxGXjoeSHe/u0yTgooCgO3 i5OZfsETKYgAyk=; b=GExVFxL3lzmYJW9WOI65/zJzAqDWJEXzpSfus7kgqnGxI 7wPWlfin/p2UAZo5jKHyz0uY8xIg1SCGxDXaJ+2XffzLtnFxg7KsfE2Br9YIUWGc 7TGsj7jq60m3bifhOXY5gAOwpSHqIIBBbqaKIGOW+OpxucRVYx7+O6+jWawOtfr+ hIU/JIfVvkvlcrOMS5GEiVqhGZTE4FJek7l7z5iz6/0+XhMbug8OM7hGkb7V+9PG tUKuSPyQQqf4LtMX+Z/m2IHFN3jMadyZJNCHMIaD3ky1I4BMNoDoejzz91kZcYo4 W+/xWr0sRGjGd4fuvMY6J35VIzCbAmiblteCRmTeg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeiledguddviecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffeetffdvleehudei teenucffohhmrghinhepghhithhhuhgsrdgtohhmnecukfhppeegtddrieehrddvvdehrd efvdenucevlhhushhtvghrufhiiigvpeeinecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght X-ME-Proxy: Received: from fv-az213-537.internal.cloudapp.net (unknown [40.65.225.32]) by mail.messagingengine.com (Postfix) with ESMTPA id 4D2DB24005A for ; Sun, 4 Apr 2021 03:43:30 -0400 (EDT) Content-Type: multipart/alternative; boundary="===============1255627869021459564==" MIME-Version: 1.0 From: Repository Activity Summary Bot To: txauth@ietf.org Message-Id: <20210404074330.4D2DB24005A@mailuser.nyi.internal> Date: Sun, 4 Apr 2021 03:43:30 -0400 (EDT) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Apr 2021 08:01:04 -0000 --===============1255627869021459564== 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 (+12/-3/=F0=9F=92=AC38) 12 issues created: - Unlinkability (by Denisthemalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/241=20 - Scalability and prior relationships between ASs and RSs (by Denisthema= lice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/240=20 - Access token format(s) negotiation (by Denisthemalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/239=20 - Concept of a "service" supported by a set of RSs (by Denisthemalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/238=20 - How can a client identify which ASs are trusted by the RS ? (by Denisth= emalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/237=20 - Common points and main differences with OAuth ? (by Denisthemalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/236=20 - An overview is missing (by Denisthemalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/235=20 - Privacy considerations (by Denisthemalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/234=20 - The case of attributes should be addressed (by Denisthemalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/233=20 - Create verifier text (by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/231=20 - Update "htu" claim name in JOSE methods (by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/230=20 - Explicit typing for jws and jwsd key proofing mechanisms (by adeinega) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/225=20 14 issues received 38 new comments: - #236 Common points and main differences with OAuth ? (1 by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/236=20 - #235 An overview is missing (1 by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/235=20 - #234 Privacy considerations (5 by Denisthemalice, fimbault, jricher, ya= ronf) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/234=20 - #233 The case of attributes should be addressed (3 by aaronpk, fimbault= , jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/233=20 - #230 Update "htu" claim name in JOSE methods (3 by jricher, yaronf) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/230=20 - #223 AS-RO policy delegation (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/223=20 - #222 paramaters x5c and x5t#S256 and GNAP key formats (3 by adeinega, f= imbault, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/222 [Pending = Close]=20 - #221 DID as identifier (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/221 [Needs Te= xt]=20 - #215 User choice and consent, and user notice (2 by Denisthemalice, sma= rtopian) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/215=20 - #214 Trust relationships (1 by Denisthemalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/214=20 - #176 Protocol rationale (1 by yaronf) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/176=20 - #133 Privacy considerations (14 by Denisthemalice, IDmachines, agropper) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/133=20 - #51 User reference as an assertion (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/51=20 - #6 Polymorphism (1 by yaronf) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/6=20 3 issues closed: - An overview is missing https://github.com/ietf-wg-gnap/gnap-core-protoc= ol/issues/235=20 - Common points and main differences with OAuth ? https://github.com/ietf= -wg-gnap/gnap-core-protocol/issues/236=20 - Privacy considerations https://github.com/ietf-wg-gnap/gnap-core-protoc= ol/issues/234=20 Pull requests ------------- * ietf-wg-gnap/core-protocol (+5/-0/=F0=9F=92=AC30) 5 pull requests submitted: - JWK definition (by adeinega) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/232=20 - update subject info definition according to sub_ids (by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/229=20 - replacing email by opaque in examples (by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/228=20 - Replace parameter "ts" by "iat" for jws and jwsd key proofing mechanism= s. (by adeinega) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/227=20 - The "typ" parameter for jws and jwsd key proofing mechanisms. (by adein= ega) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/226=20 6 pull requests received 30 new comments: - #232 JWK definition (3 by adeinega, fimbault, netlify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/232=20 - #229 update subject info definition according to sub_ids (7 by agropper= , fimbault, jricher, netlify, yaronf) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/229=20 - #228 replacing email by opaque in examples (1 by netlify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/228=20 - #227 Replace parameter "ts" by "iat" for jws and jwsd key proofing mech= anisms. (12 by adeinega, fimbault, jricher, netlify, yaronf) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/227 [Pending Cl= ose]=20 - #226 The "typ" parameter for jws and jwsd key proofing mechanisms. (2 b= y fimbault, netlify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/226=20 - #202 Syntax and schema based normalization for URI in the htu claim. (5= by adeinega, fimbault, jricher, yaronf) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/202=20 Repositories tracked by this digest: ----------------------------------- * https://github.com/ietf-wg-gnap/core-protocol --===============1255627869021459564== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Weekly github digest (GNAP Weekly GitHub Activity Summary)

Sunday April 04, 2021

Events without label "editorial"

Issues

ietf-wg-gnap/core-protocol (+12/-3/=F0=9F=92=AC38)

12 issues created:

14 issues received 38 new comments:

3 issues closed:

Pull requests

ietf-wg-gnap/core-protocol (+5/-0/=F0=9F=92=AC30)

5 pull requests submitted:

6 pull requests received 30 new comments:

Repositories tracked by this digest:

--===============1255627869021459564==-- From nobody Fri Apr 9 05:28:20 2021 Return-Path: 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 6250A3A1F86 for ; Fri, 9 Apr 2021 05:28:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, RCVD_DOTEDU_SHORT=1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no 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 CKNl1iDgZJE4 for ; Fri, 9 Apr 2021 05:28:17 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48AF63A1F7E for ; Fri, 9 Apr 2021 05:28:16 -0700 (PDT) Received: from [192.168.1.22] (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 139CSDZP028830 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 9 Apr 2021 08:28:14 -0400 From: Justin Richer Content-Type: multipart/alternative; boundary="Apple-Mail=_A3E36858-F792-46E4-95B3-8E6375D2AD6B" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Message-Id: <40D2CDB6-9EF7-42B1-8926-CDDC3523A5AE@mit.edu> Date: Fri, 9 Apr 2021 08:28:13 -0400 To: GNAP Mailing List X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [GNAP] Gathering Consent and Authorization X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2021 12:28:19 -0000 --Apple-Mail=_A3E36858-F792-46E4-95B3-8E6375D2AD6B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 We=E2=80=99ve recently had a lot of good discussion about the nature and = role of the AS within GNAP, and the editors stated that we would be = working on new text to incorporate this discussion. With that in mind, I = wanted to bring everyone=E2=80=99s attention to a PR that makes some big = changes to the core spec, though mostly in the description of how = components work and less with the normative syntax of the protocol = itself. https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242 = This rewrites the section that is currently =E2=80=9CInteraction at the = AS=E2=80=9D to better describe the wider range of possibilities for the = authorization process. Note that this PR hasn=E2=80=99t been tagged as = =E2=80=9Cpending merge=E2=80=9D by the editors yet, which means = there=E2=80=99s not a review deadline in place yet, but since it=E2=80=99s= such a big change we=E2=80=99d like to get it in somewhat soon. Please = go read through the new text and help improve it! Thank you, =E2=80=94 Justin= --Apple-Mail=_A3E36858-F792-46E4-95B3-8E6375D2AD6B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 We=E2=80=99ve recently had a lot of good discussion about the = nature and role of the AS within GNAP, and the editors stated that we = would be working on new text to incorporate this discussion. With that = in mind, I wanted to bring everyone=E2=80=99s attention to a PR that = makes some big changes to the core spec, though mostly in the = description of how components work and less with the normative syntax of = the protocol itself.

https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242=

This rewrites = the section that is currently =E2=80=9CInteraction at the AS=E2=80=9D to = better describe the wider range of possibilities for the authorization = process. Note that this PR hasn=E2=80=99t been tagged as =E2=80=9Cpending = merge=E2=80=9D by the editors yet, which means there=E2=80=99s not a = review deadline in place yet, but since it=E2=80=99s such a big change = we=E2=80=99d like to get it in somewhat soon. Please go read through the = new text and help improve it!

Thank you,
 =E2= =80=94 Justin
= --Apple-Mail=_A3E36858-F792-46E4-95B3-8E6375D2AD6B-- From nobody Fri Apr 9 08:11:58 2021 Return-Path: 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 3CBBB3A2466 for ; Fri, 9 Apr 2021 08:11:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.626 X-Spam-Level: X-Spam-Status: No, score=0.626 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no 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 2Z6Pb3T4btdn for ; Fri, 9 Apr 2021 08:11:54 -0700 (PDT) Received: from smtp.smtpout.orange.fr (smtp06.smtpout.orange.fr [80.12.242.128]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C7293A2464 for ; Fri, 9 Apr 2021 08:11:54 -0700 (PDT) Received: from [192.168.1.11] ([90.26.9.133]) by mwinf5d86 with ME id qfBq2400B2sDAeJ03fBqkH; Fri, 09 Apr 2021 17:11:51 +0200 X-ME-Helo: [192.168.1.11] X-ME-Auth: ZGVuaXMucGlua2FzQG9yYW5nZS5mcg== X-ME-Date: Fri, 09 Apr 2021 17:11:51 +0200 X-ME-IP: 90.26.9.133 To: Justin Richer , GNAP Mailing List References: <40D2CDB6-9EF7-42B1-8926-CDDC3523A5AE@mit.edu> From: Denis Message-ID: Date: Fri, 9 Apr 2021 17:11:49 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: <40D2CDB6-9EF7-42B1-8926-CDDC3523A5AE@mit.edu> Content-Type: multipart/alternative; boundary="------------970A4ABACA4024EB1D4016D7" Content-Language: en-GB Archived-At: Subject: Re: [GNAP] Gathering Consent and Authorization X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2021 15:11:57 -0000 This is a multi-part message in MIME format. --------------970A4ABACA4024EB1D4016D7 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi  Justin, "Gathering Consent"  is not solely related with a section that would be called “Interaction at the AS”. For authorizing a method on an object, the RS (or more precisely the RO controlling that object) is wishing to obtain some privileges (i.e. attributes types and /or rights ) inside an access token that may be issued by *one AS among several ASs*. The privileges a RS is wishing to obtain should be proportionate to the method that is being requested on the object. This means that in the first access to a RS, the client should advertise both the method and the object on which the method applies and then in its response, the RS should indicate which choices are possible and the reason(s) behind each choice ("User Notice"). In general, it is possible to decompose the end-user choice into three consecutive choices: a) a first choice for selecting the AS, b) a second choice for selecting different privileges *types *(i.e. attributes types and /or rights types) for the selected AS, c) a third choice selecting different privileges *values *for the selected privileges types (i.e. attributes type values and /or rights types values) If a RS is only trusting one AS, the first choice becomes a YES or NO question. The second choice must be based on information provided by the RS, since only the RS is knowing the rational to request some set of privileges. In such a case , the dialogue with the end-user can be done either *directly at the RS* or *locally at the client* using information provided by the RS. The third choice must be done at the AS. If a RS is trusting more than one AS, the first and the second choices must be done before contacting an AS (see above), while the third choice must be done at the AS. Denis PS. I have not yet read through the new text. > We’ve recently had a lot of good discussion about the nature and role > of the AS within GNAP, and the editors stated that we would be working > on new text to incorporate this discussion. With that in mind, I > wanted to bring everyone’s attention to a PR that makes some big > changes to the core spec, though mostly in the description of how > components work and less with the normative syntax of the protocol > itself. > > https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242 > > > This rewrites the section that is currently “Interaction at the AS” to > better describe the wider range of possibilities for the authorization > process. Note that this PR hasn’t been tagged as “pending merge” by > the editors yet, which means there’s not a review deadline in place > yet, but since it’s such a big change we’d like to get it in somewhat > soon. Please go read through the new text and help improve it! > > Thank you, >  — Justin > --------------970A4ABACA4024EB1D4016D7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
Hi  Justin,

"Gathering Consent"  is not solely related with a section that would be called “Interaction at the AS”.

For authorizing a method on an object, the RS (or more precisely the RO controlling that object) is wishing to obtain some privileges
(i.e. attributes types and /or rights ) inside an access token that may be issued by one AS among several ASs.

The privileges a RS is wishing to obtain should be proportionate to the method that is being requested on the object. This means that
in the first access to a RS, the client should advertise both the method and the object on which the method applies and then in its response,
the RS should indicate which choices are possible and the reason(s) behind each choice ("User Notice").

In general, it is possible to decompose the end-user choice into three consecutive choices:
a) a first choice for selecting the AS,
b) a second choice for selecting different privileges types (i.e. attributes types and /or rights types) for the selected AS,
c) a third choice selecting different privileges values for the selected privileges types (i.e. attributes type values and /or rights types values)
If a RS is only trusting one AS, the first choice becomes a YES or NO question. The second choice must be based on information provided by the RS,
since only the RS is knowing the rational to request some set of privileges. In such a case , the dialogue with the end-user can be done either
directly at the RS or locally at the client using information provided by the RS. The third choice must be done at the AS.

If a RS is trusting more than one AS, the first and the second choices must be done before contacting an AS (see above), while the third choice
must be done at the AS.

Denis

PS. I have not yet read through the new text.


We’ve recently had a lot of good discussion about the nature and role of the AS within GNAP, and the editors stated that we would be working on new text to incorporate this discussion. With that in mind, I wanted to bring everyone’s attention to a PR that makes some big changes to the core spec, though mostly in the description of how components work and less with the normative syntax of the protocol itself.


This rewrites the section that is currently “Interaction at the AS” to better describe the wider range of possibilities for the authorization process. Note that this PR hasn’t been tagged as “pending merge” by the editors yet, which means there’s not a review deadline in place yet, but since it’s such a big change we’d like to get it in somewhat soon. Please go read through the new text and help improve it!

Thank you,
 — Justin


--------------970A4ABACA4024EB1D4016D7-- From nobody Fri Apr 9 08:33:35 2021 Return-Path: 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 EEB263A24F1 for ; Fri, 9 Apr 2021 08:33:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=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=gmail.com 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 cWWNx-l6otjg for ; Fri, 9 Apr 2021 08:33:29 -0700 (PDT) Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53B3E3A1A07 for ; Fri, 9 Apr 2021 08:33:29 -0700 (PDT) Received: by mail-il1-x134.google.com with SMTP id w2so5021557ilj.12 for ; Fri, 09 Apr 2021 08:33:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YW9T2WhvkomXNiBJc/4EwKAogQ5gI1MrVAAKUGGWZv8=; b=bfN0QJTqO29aIQ+X1aKaTetAmGcPtu0cO7aunCae+6IvP9IfAU0Gtp8hEQV2PXFUpw wEK0hQQC1tQF1idCUEUVuPgGJvyiIunBwyWcgYHFIetF8Ktxk+U8OXfWELfyKVqIAIvF RyYt2P1bcC4gtVnjnP6+snie/jOZ0BGu4vlii1jUCxMujj0nSZIRwraC580sRYgRnHrZ KpsagCau5QCfX46QeQOsZzvlFazDbvnyaONOIaJjFHo7p0uKKZSBNJv8acL6L7OEKsN3 uAM1dWvp2Nf/T7/4ZYe/yYPmHrtqLYSYxIZFd0UY/FIMx0FJJqi6P3HPyV+JWfsnXfDi q6NQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YW9T2WhvkomXNiBJc/4EwKAogQ5gI1MrVAAKUGGWZv8=; b=MSJGPF3ObuPyCYcLsv04RXrigCDv+D3D8X6eR3rP+jTmGGgu+026Zoal4GHvJ/5qkL UnAnI0luFnt3DI9mKWvIbqEqqyBTKqORKBCUYEL8L4kKRFqtIK+kRllH4Iz1/1ntohu5 zcOdChwzGk1BQ5pbj773dpd/+OZwymtosmqGtzRHn9zuYx/lfI/1qOo7Mnz3fIki8ZcN 8hcvkDsc4VaCozjrloAuU+CjrLiCwoDhe0LsF2NsZq+zqnVJMOmD/KP2MJI/VxrX4ok4 EO+Kmi0yBTodu8tit/bIzprwOVvreIrZPI4LbOjlyWsIFNhpK3UVTi+2wjBA639v5/2u 9Rcw== X-Gm-Message-State: AOAM533XUcdPmByMRPn2SqF/qd76Jz4UfUoOAPNnpi2O7c30L7N+kSgw Qho0WtVanWO2BK+PQCa3V2d0hv0gGOCHxhDe2UA= X-Google-Smtp-Source: ABdhPJwNHvQHPK5aB9myakklhZrtknQDqdFFp5SDUKow3eI2ULjV6WNqeVdXWZ0BTNz7ItwERsZPrBZANcHo+Idu/x4= X-Received: by 2002:a05:6e02:4aa:: with SMTP id e10mr2274297ils.188.1617982407477; Fri, 09 Apr 2021 08:33:27 -0700 (PDT) MIME-Version: 1.0 References: <40D2CDB6-9EF7-42B1-8926-CDDC3523A5AE@mit.edu> In-Reply-To: From: Fabien Imbault Date: Fri, 9 Apr 2021 17:33:16 +0200 Message-ID: To: Denis Cc: Justin Richer , GNAP Mailing List Content-Type: multipart/alternative; boundary="000000000000a68d1a05bf8be2ef" Archived-At: Subject: Re: [GNAP] Gathering Consent and Authorization X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2021 15:33:34 -0000 --000000000000a68d1a05bf8be2ef Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Remember that for convenience, the PR generates an HTML draft, so you should be able to read easily. See https://deploy-preview-242--gnap-core-protocol-editors-draft.netlify.app/ In particular section 4 is now called Determining Authorization and Consent= . Cheers Fabien On Fri, Apr 9, 2021 at 5:12 PM Denis wrote: > Hi Justin, > > "Gathering Consent" is not solely related with a section that would be > called =E2=80=9CInteraction at the AS=E2=80=9D. > > For authorizing a method on an object, the RS (or more precisely the RO > controlling that object) is wishing to obtain some privileges > (i.e. attributes types and /or rights ) inside an access token that may b= e > issued by *one AS among several ASs*. > > The privileges a RS is wishing to obtain should be proportionate to the > method that is being requested on the object. This means that > in the first access to a RS, the client should advertise both the method > and the object on which the method applies and then in its response, > the RS should indicate which choices are possible and the reason(s) behin= d > each choice ("User Notice"). > > In general, it is possible to decompose the end-user choice into three > consecutive choices: > > a) a first choice for selecting the AS, > b) a second choice for selecting different privileges *types *(i.e. > attributes types and /or rights types) for the selected AS, > c) a third choice selecting different privileges *values *for the > selected privileges types (i.e. attributes type values and /or rights typ= es > values) > > If a RS is only trusting one AS, the first choice becomes a YES or NO > question. The second choice must be based on information provided by the = RS, > since only the RS is knowing the rational to request some set of > privileges. In such a case , the dialogue with the end-user can be done > either > *directly at the RS* or *locally at the client* using information > provided by the RS. The third choice must be done at the AS. > > If a RS is trusting more than one AS, the first and the second choices > must be done before contacting an AS (see above), while the third choice > must be done at the AS. > > Denis > > PS. I have not yet read through the new text. > > > We=E2=80=99ve recently had a lot of good discussion about the nature and = role of > the AS within GNAP, and the editors stated that we would be working on ne= w > text to incorporate this discussion. With that in mind, I wanted to bring > everyone=E2=80=99s attention to a PR that makes some big changes to the c= ore spec, > though mostly in the description of how components work and less with the > normative syntax of the protocol itself. > > https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242 > > This rewrites the section that is currently =E2=80=9CInteraction at the A= S=E2=80=9D to > better describe the wider range of possibilities for the authorization > process. Note that this PR hasn=E2=80=99t been tagged as =E2=80=9Cpending= merge=E2=80=9D by the > editors yet, which means there=E2=80=99s not a review deadline in place y= et, but > since it=E2=80=99s such a big change we=E2=80=99d like to get it in somew= hat soon. Please > go read through the new text and help improve it! > > Thank you, > =E2=80=94 Justin > > > -- > TXAuth mailing list > TXAuth@ietf.org > https://www.ietf.org/mailman/listinfo/txauth > --000000000000a68d1a05bf8be2ef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0

Remember that for convenience= , the PR generates an HTML draft, so you should be able to read easily.

In particular sectio= n 4 is now called=C2=A0Determining Authorization and Consent.
Cheers
Fabien

On Fri, Apr 9, 2021 at 5:12 PM Den= is <denis.ietf@free.fr> wro= te:
=20 =20 =20
Hi=C2=A0 Justin,

"Gathering Consent"=C2=A0 is not solely related with a section that would be called =E2=80=9CInteraction at t= he AS=E2=80=9D.

For authorizing a method on an object, the RS (or more precisely the RO controlling that object) is wishing to obtain some privileges
(i.e. attributes types and /or rights ) inside an access token that may be issued by one AS among several ASs.

The privileges a RS is wishing to obtain should be proportionate to the method that is being requested on the object. This means that
in the first access to a RS, the client should advertise both the method and the object on which the method applies and then in its response,
the RS should indicate which choices are possible and the reason(s) behind each choice ("User Notice").

In general, it is possible to decompose the end-user choice into three consecutive choices:
a) a first choice for selecting the AS,
b) a second choice for selecting different privileges types (i.e. attributes types and /or rights types) for the selected AS,
c) a third choice selecting different privileges values for the selected privileges types (i.e. attributes type values and /or rights types values)
If a RS is only trusting one AS, the first choice becomes a YES or NO question. The second choice must be based on information provided by the RS,
since only the RS is knowing the rational to request some set of privileges. In such a case , the dialogue with the end-user can be done either
directly at the RS or locally at the client using information provided by the RS. The third choice must be done at the AS.

If a RS is trusting more than one AS, the first and the second choices must be done before contacting an AS (see above), while the third choice
must be done at the AS.

Denis

PS. I have not yet read through the new text.


We=E2=80=99ve recently had a lot of good discussion about the nature and role of the AS within GNAP, and the editors stated that we would be working on new text to incorporate this discussion. With that in mind, I wanted to bring everyone=E2=80=99s attention to a PR that mak= es some big changes to the core spec, though mostly in the description of how components work and less with the normative syntax of the protocol itself.


This rewrites the section that is currently =E2=80=9CInteraction at the AS=E2=80=9D to better describe the wide= r range of possibilities for the authorization process. Note that this PR hasn=E2=80=99t been tagged as =E2=80=9Cpending merge=E2=80=9D by th= e editors yet, which means there=E2=80=99s not a review deadline in place yet, but since= it=E2=80=99s such a big change we=E2=80=99d like to get it in somewhat soon. Ple= ase go read through the new text and help improve it!

Thank you,
=C2=A0=E2=80=94 Justin


--
TXAuth mailing list
TXAuth@ietf.org https://www.ietf.org/mailman/listinfo/txauth
--000000000000a68d1a05bf8be2ef-- From nobody Sun Apr 11 01:01:08 2021 Return-Path: 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 CF9F03A3181 for ; Sun, 11 Apr 2021 01:01:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.119 X-Spam-Level: X-Spam-Status: No, score=-2.119 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=qvYE5ALW; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=pRba11LT 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 Os7jcGm813gV for ; Sun, 11 Apr 2021 01:00:59 -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 171C93A317F for ; Sun, 11 Apr 2021 01:00:59 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6FA945C00F4 for ; Sun, 11 Apr 2021 03:42:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 11 Apr 2021 03:42:10 -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=9e38Io4BN1ZMcVvWn45RCX43+8E7Av55EwoHpYw2vFI=; b=qvYE5ALW vuJixz7NGniug0pcf5inSkzr5x5Iw78FowbAPjRlVAv0sJDZXjmcau1OkibYxyjQ PevjCN4iBqOZQDMGu4oO3jlI4fwkvUYoV5KT42BcGhjJx3/YtuByrfN3WVFfB4D/ Ws8CmN2UPhNuMhgRXs/bTd/7PXjRACWHtxn5ZrHeEIu6RvsjMlg1n2dkFdee14F9 w/sde3bVMFgN3nq3Cua41EFNOw5h4MkFr51dGZyllo6h7FUt80SCSAdpNqDL5nMN LbbmX0DQPGCRmTwygi/3LHRoJcMG3u5iCqXBlbyGOhffY4PR2xHMMoyYVbbpoF8t bsrlSQf2ePo68g== 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=9e38Io4BN1ZMcVvWn45RCX43+8E7A v55EwoHpYw2vFI=; b=pRba11LTg4l5UdMSgEvAzu94h6SZ522xirqEbW54zrgmZ jcXccjPt2aq4M2j5PgzKZnQmBqlkE3Hdh1xQikp3xObifz22ArfP7MjE3x7MW1Sn VFnpz5gTovP5Q+MB/tiuQOEIHKsdCK4LrUoeZ3uc+eAWlNNQ82MkETkSwmmjr/Bu TA3Kuw+vH5No52Q+z/e0/UWjHStZ5JMSGM7P9/EsD1+H26o/lsRRK0lhJJEHuoUb tajLJrZajiwQGN8qiBIRc3cVHa9mKK9JSenuoWCWhb9ZU/0awidyqABshXozZBmm joeZ/lg+Mt64zLrhf76Qtc4sesAVysFR43nAIdRzA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudekgedguddvfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffeetffdvleehudei teenucffohhmrghinhepghhithhhuhgsrdgtohhmnecukfhppeehvddrudegjedrudejfe drledtnecuvehluhhsthgvrhfuihiivgepjeenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth X-ME-Proxy: Received: from fv-az266-924.internal.cloudapp.net (unknown [52.147.173.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 4437B108005C for ; Sun, 11 Apr 2021 03:42:10 -0400 (EDT) Content-Type: multipart/alternative; boundary="===============2004199226696109332==" MIME-Version: 1.0 From: Repository Activity Summary Bot To: txauth@ietf.org Message-Id: <20210411074210.4437B108005C@mailuser.nyi.internal> Date: Sun, 11 Apr 2021 03:42:10 -0400 (EDT) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2021 08:01:04 -0000 --===============2004199226696109332== 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 (+1/-0/=F0=9F=92=AC18) 1 issues created: - Refactoring the internals of access request (by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/244=20 8 issues received 18 new comments: - #244 Refactoring the internals of access request (11 by adeinega, fimba= ult, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/244=20 - #241 Unlinkability (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/241=20 - #240 Scalability and prior relationships between ASs and RSs (1 by fim= bault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/240=20 - #239 Access token format(s) negotiation (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/239=20 - #238 Concept of a "service" supported by a set of RSs (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/238=20 - #237 How can a client identify which ASs are trusted by the RS ? (1 by = fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/237=20 - #189 Token format (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/189=20 - #6 Polymorphism (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/6=20 Pull requests ------------- * ietf-wg-gnap/core-protocol (+2/-0/=F0=9F=92=AC17) 2 pull requests submitted: - Fix the payload of the introspection request. (by adeinega) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/243=20 - Gathering consent and authorization through interaction and other means= (by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242=20 3 pull requests received 17 new comments: - #243 Fix the payload of the introspection request. (8 by adeinega, fimb= ault, jricher, netlify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/243=20 - #242 Gathering consent and authorization through interaction and other = means (4 by agropper, fimbault, jricher, netlify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242=20 - #232 JWK definition (5 by adeinega, fimbault, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/232=20 Repositories tracked by this digest: ----------------------------------- * https://github.com/ietf-wg-gnap/core-protocol --===============2004199226696109332== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Weekly github digest (GNAP Weekly GitHub Activity Summary)

Sunday April 11, 2021

Events without label "editorial"

Issues

ietf-wg-gnap/core-protocol (+1/-0/=F0=9F=92=AC18)

1 issues created:

8 issues received 18 new comments:

Pull requests

ietf-wg-gnap/core-protocol (+2/-0/=F0=9F=92=AC17)

2 pull requests submitted:

3 pull requests received 17 new comments:

Repositories tracked by this digest:

--===============2004199226696109332==-- From nobody Wed Apr 14 10:42:24 2021 Return-Path: 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 BC7A03A1902 for ; Wed, 14 Apr 2021 10:42:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.498 X-Spam-Level: X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no 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 K8_WutlUTFZT for ; Wed, 14 Apr 2021 10:42:20 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 717273A18FE for ; Wed, 14 Apr 2021 10:42:20 -0700 (PDT) Received: from [192.168.1.22] (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13EHgIVF020993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 14 Apr 2021 13:42:18 -0400 From: Justin Richer Content-Type: multipart/alternative; boundary="Apple-Mail=_1E57019B-BB44-4D56-8251-40BF56E0F498" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Message-Id: <11825BA5-66B8-4370-A971-5535EB4A082A@mit.edu> Date: Wed, 14 Apr 2021 13:42:17 -0400 To: GNAP Mailing List X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [GNAP] Editors' Updates X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2021 17:42:23 -0000 --Apple-Mail=_1E57019B-BB44-4D56-8251-40BF56E0F498 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 The editors met today and have processed a number of issues and pull = requests. The following pull requests have been reviewed by the editors and are = marked Pending Merge: #229: update subject info definition according to sub_ids https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/229 = #232: JWK definition https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/232 = #242: Gathering consent and authorization through interaction and other = means https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242 = #246: Extract RS-focused protocol elements https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246 = #247: Appendix on protocol rationale https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/247 = Several issues will be closed when these pull requests are merged.=20 The following issues have been marked as Pending Close: #185: Protected and Public Resources https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/185 = #189: Token format https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/189 = #190: Tentative proposal for a RS discovery mechanism https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/190 = #191: Validity of an access token https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/191 = #203: Requesting resources with insufficient access https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/203 = #210: =E2=80=9Csub_id=E2=80=9D claims https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/210 = #212: Definition of a Resource Server (RS) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/212 = #213: Definition and roles of a Resource Owner (RO) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/213 = #237: How can a client identify which ASs are trusted by the RS ? https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/237 = #238: Concept of a =E2=80=9Cservice=E2=80=9D supported by a set of RSs https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/238 = #240: Scalability and prior relationships between ASs and RSs https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/240 = #241: Unlinkability https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/241 = Additionally, the editors have gone through the issue tracker and closed = a number of duplicate issues.=20 Unless there is substantive disagreement from the working group, these = actions will be taken in one week from today on April 21. In particular, = please review the pull requests, and feel free to suggest improvements. = However, please keep in mind that the goal of each PR is not to be = perfect and address all known problems but rather to move things forward = from where they are now. As a reminder, we=E2=80=99ve got the next GNAP Interim meeting on May = 6th. The editors are looking to publish the next revision of the spec a = week ahead of that meeting, to give everyone a chance to read the new = draft in its entirety. =E2=80=94 Justin, Aaron, and Fabien= --Apple-Mail=_1E57019B-BB44-4D56-8251-40BF56E0F498 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 The = editors met today and have processed a number of issues and pull = requests.


The following pull requests have been = reviewed by the editors and are marked Pending Merge:

#229: update subject = info definition according to sub_ids
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/229=

#232: JWK = definition
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/232=

#242: = Gathering consent and authorization through interaction and other = means
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242=

#246: Extract = RS-focused protocol elements
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246=

#247: = Appendix on protocol rationale
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/247=

Several = issues will be closed when these pull requests are = merged. 



The following issues have been marked as Pending = Close:

#185: = Protected and Public Resources
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/185

#189: Token = format
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/189

#190: = Tentative proposal for a RS discovery mechanism
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/190

#191: = Validity of an access token
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/191

#203: = Requesting resources with insufficient access
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/203

#210: = =E2=80=9Csub_id=E2=80=9D claims
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/210

#212: = Definition of a Resource Server (RS)
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/212

#213: = Definition and roles of a Resource Owner (RO)
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/213

#237: How = can a client identify which ASs are trusted by the RS ?
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/237

#238: = Concept of a =E2=80=9Cservice=E2=80=9D supported by a set of = RSs
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/238

#240: = Scalability and prior relationships between ASs and RSs
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/240

#241: = Unlinkability
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/241



Additionally, the editors have gone through the issue tracker = and closed a number of duplicate issues. 



Unless there is substantive = disagreement from the working group, these actions will be taken in one = week from today on April 21. In particular, please review the pull = requests, and feel free to suggest improvements. However, please keep in = mind that the goal of each PR is not to be perfect and address all known = problems but rather to move things forward from where they are = now.



As = a reminder, we=E2=80=99ve got the next GNAP Interim meeting on May 6th. = The editors are looking to publish the next revision of the spec a week = ahead of that meeting, to give everyone a chance to read the new draft = in its entirety.

 =E2=80=94 Justin, Aaron, and Fabien
= --Apple-Mail=_1E57019B-BB44-4D56-8251-40BF56E0F498-- From nobody Sun Apr 18 01:21:12 2021 Return-Path: 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 ; 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 ; 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 ; 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 ; 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: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudelkedgvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfhvffusegrtddtredttdejne cuhfhrohhmpeftvghpohhsihhtohhrhicutegtthhivhhithihucfuuhhmmhgrrhihuceu ohhtuceoughopghnohhtpghrvghplhihsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepkeefvdduteejvdefkeehieevuefgfefhteetveegffekffefteffvdelheduieet necuffhomhgrihhnpehgihhthhhusgdrtghomhenucfkphephedvrddufeekrdekhedrle dvnecuvehluhhsthgvrhfuihiivgepjeenucfrrghrrghmpehmrghilhhfrhhomhepugho pghnohhtpghrvghplhihsehmnhhothdrnhgvth X-ME-Proxy: Received: from [10.1.0.164] (unknown [52.138.85.92]) by mail.messagingengine.com (Postfix) with ESMTPA id B54F91080064 for ; Sun, 18 Apr 2021 03:41:49 -0400 (EDT) Content-Type: multipart/alternative; boundary="===============7996708468279517806==" MIME-Version: 1.0 From: Repository Activity Summary Bot To: txauth@ietf.org Message-Id: <20210418074149.B54F91080064@mailuser.nyi.internal> Date: Sun, 18 Apr 2021 03:41:49 -0400 (EDT) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Apr 2021 08:21:08 -0000 --===============7996708468279517806== 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 (+3/-10/=F0=9F=92=AC58) 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=20 - Privacy Considerations for Subject Identifiers (by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/249=20 - Be consistent with OAuth 2.0 (not OAuth 2) (by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/248 [Editoria= l]=20 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=20 - #241 Unlinkability (3 by Denisthemalice, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/241 [Pending = Close]=20 - #240 Scalability and prior relationships between ASs and RSs (3 by Den= isthemalice, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/240 [Pending = Close]=20 - #239 Access token format(s) negotiation (2 by Denisthemalice, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/239=20 - #238 Concept of a "service" supported by a set of RSs (3 by Denisthemal= ice, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/238 [Pending = Close]=20 - #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]=20 - #233 The case of attributes should be addressed (1 by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/233=20 - #225 Explicit typing for jws and jwsd key proofing mechanisms (1 by jri= cher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/225=20 - #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]=20 - #213 Definition and roles of a Resource Owner (RO) (1 by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/213=20 - #212 Definition of a Resource Server (RS) (1 by Denisthemalice) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/212 [Pending = Close]=20 - #210 "sub_id" claims (3 by Denisthemalice, aaronpk, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/210 [Pending = Close]=20 - #203 Requesting resources with insufficient access (4 by Denisthemalice= , aaronpk, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/203 [Pending = Close]=20 - #201 Include body hash in Detached JWS (1 by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/201=20 - #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]=20 - #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=20 - #193 Requesting Resources With Insufficient Access (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/193=20 - #191 Validity of an access token (2 by Denisthemalice, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/191 [Pending = Close]=20 - #190 Tentative proposal for a RS discovery mechanism (2 by Denisthemali= ce, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/190 [Pending = Close]=20 - #189 Token format (2 by Denisthemalice, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/189 [Pending = Close]=20 - #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=20 - #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=20 - #186 User consent and user notice (2 by fimbault, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/186=20 - #185 Protected and Public Resources (2 by Denisthemalice, jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/185 [Pending = Close]=20 - #176 Protocol rationale (1 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/176=20 - #133 Privacy considerations (1 by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/133=20 10 issues closed: - Explicit typing for jws and jwsd key proofing mechanisms https://github= .com/ietf-wg-gnap/gnap-core-protocol/issues/225=20 - Prior relationship or not between a RS and an AS https://github.com/iet= f-wg-gnap/gnap-core-protocol/issues/188=20 - The case of a RS trusting more that one AS https://github.com/ietf-wg-g= nap/gnap-core-protocol/issues/187=20 - Access token format(s) negotiation https://github.com/ietf-wg-gnap/gnap= -core-protocol/issues/239=20 - The case of attributes should be addressed https://github.com/ietf-wg-g= nap/gnap-core-protocol/issues/233=20 - User consent and user notice https://github.com/ietf-wg-gnap/gnap-core-= protocol/issues/186=20 - Requesting Resources With Insufficient Access https://github.com/ietf-w= g-gnap/gnap-core-protocol/issues/193=20 - Definition of a Subject in section 1.3 https://github.com/ietf-wg-gnap/= gnap-core-protocol/issues/198 [Pending Close]=20 - paramaters x5c and x5t#S256 and GNAP key formats https://github.com/iet= f-wg-gnap/gnap-core-protocol/issues/222 [Pending Close]=20 - Use of identifiers as communication channels https://github.com/ietf-wg= -gnap/gnap-core-protocol/issues/42=20 Pull requests ------------- * ietf-wg-gnap/core-protocol (+5/-4/=F0=9F=92=AC18) 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=20 - Cryptographic Key Proofing Updates (by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/250=20 - Appendix on protocol rationale (by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/247=20 - Extract RS-focused protocol elements (by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246=20 - Continuation information was stored on the step (2) not (3) (by romabaz) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/245=20 6 pull requests received 18 new comments: - #251 Not 'push' but 'finish' is used to provide nonce value during inte= ract response (1 by netlify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/251=20 - #250 Cryptographic Key Proofing Updates (3 by jricher, netlify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/250=20 - #247 Appendix on protocol rationale (1 by netlify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/247=20 - #246 Extract RS-focused protocol elements (9 by adeinega, jricher, netl= ify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246=20 - #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=20 - #227 Replace parameter "ts" by "iat" for jws and jwsd key proofing mech= anisms. (2 by fimbault) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/227 [Pending Cl= ose]=20 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]= =20 - replacing email by opaque in examples https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/228 [Pending Me= rge]=20 - The "typ" parameter for jws and jwsd key proofing mechanisms. https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/226 [Pending Me= rge]=20 - change subject type to format to comply with secevent draft07 https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/220 [Pending Me= rge]=20 Repositories tracked by this digest: ----------------------------------- * https://github.com/ietf-wg-gnap/core-protocol --===============7996708468279517806== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Weekly github digest (GNAP Weekly GitHub Activity Summary)

Sunday April 18, 2021

Events without label "editorial"

Issues

ietf-wg-gnap/core-protocol (+3/-10/=F0=9F=92=AC58)

3 issues created:

26 issues received 58 new comments:

10 issues closed:

Pull requests

ietf-wg-gnap/core-protocol (+5/-4/=F0=9F=92=AC18)

5 pull requests submitted:

6 pull requests received 18 new comments:

4 pull requests merged:

Repositories tracked by this digest:

--===============7996708468279517806==-- From nobody Wed Apr 21 06:20:00 2021 Return-Path: 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 140483A2776 for ; Wed, 21 Apr 2021 06:19:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no 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 5-vwoNxWv3m5 for ; Wed, 21 Apr 2021 06:19:54 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2946A3A2774 for ; Wed, 21 Apr 2021 06:19:53 -0700 (PDT) Received: from [192.168.1.22] (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13LDJpNm001074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 21 Apr 2021 09:19:52 -0400 From: Justin Richer Content-Type: multipart/alternative; boundary="Apple-Mail=_867B1DEB-B9B5-4137-8150-09DA2D38E100" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Message-Id: Date: Wed, 21 Apr 2021 09:19:51 -0400 To: GNAP Mailing List X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [GNAP] Cryptographic Updates X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2021 13:19:59 -0000 --Apple-Mail=_867B1DEB-B9B5-4137-8150-09DA2D38E100 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 The editors have prepared a PR addressing a number of issues with the = cryptographic requirements and examples in the draft, and this has been = marked Pending Merge. Please review the changes as they will be = incorporated in 7 days: https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/250 = =E2=80=94 Justin --Apple-Mail=_867B1DEB-B9B5-4137-8150-09DA2D38E100 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 The = editors have prepared a PR addressing a number of issues with the = cryptographic requirements and examples in the draft, and this has been = marked Pending Merge. Please review the changes as they will be = incorporated in 7 days:

https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/250=

 =E2=80=94= Justin

= --Apple-Mail=_867B1DEB-B9B5-4137-8150-09DA2D38E100-- From nobody Wed Apr 21 07:08:11 2021 Return-Path: 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 95BF73A2925 for ; Wed, 21 Apr 2021 07:08:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no 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 l_dzKwbO16PT for ; Wed, 21 Apr 2021 07:08:05 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D87B33A2525 for ; Wed, 21 Apr 2021 07:08:04 -0700 (PDT) Received: from [192.168.1.22] (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13LE82A2024165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 21 Apr 2021 10:08:03 -0400 From: Justin Richer Content-Type: multipart/alternative; boundary="Apple-Mail=_9E9C6EE5-36E3-4CEE-88AA-BA1985E8AB8E" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Message-Id: <5856F391-84AD-44B7-8801-BE96A878C10A@mit.edu> Date: Wed, 21 Apr 2021 10:08:02 -0400 To: GNAP Mailing List X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [GNAP] GNAP-RS Draft X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2021 14:08:10 -0000 --Apple-Mail=_9E9C6EE5-36E3-4CEE-88AA-BA1985E8AB8E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 In recent discussions on the list, tracker, and calls, there has been a = lot of mixing up of requirements for the client vs. the RS vs. the AS = vs. other components, and the relationships between them. The editors = proposed and enacted a solution to focus the core document on the client = -> AS and client -> RS parts of the protocol, allowing the RS <-> AS leg = of the diagram to vary independently, as it does in OAuth. Unlike OAuth, = there is a definite goal and desire in this WG to focus on some forms of = interoperability for the RS <-> AS relationship, but not at the expense = of its independence from the client-facing portions. With the merging of PR #246, we have now factored out the portions of = the document related to AS-RS relationships. These will now be defined = in a separate draft, at: https://github.com/ietf-wg-gnap/gnap-resource-servers = A proposed document is available for review there and will be submitted = as a WG document ahead of the next interim. As a topic at the next = interim, the group will discuss how to best manage issues directed at = one document or the other, in order to help the conversations stay = focused on the appropriate portions of the protocol space.=20 Thank you, =E2=80=94 Justin= --Apple-Mail=_9E9C6EE5-36E3-4CEE-88AA-BA1985E8AB8E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
In recent discussions on the list, tracker, and calls, there = has been a lot of mixing up of requirements for the client vs. the RS = vs. the AS vs. other components, and the relationships between them. The = editors proposed and enacted a solution to focus the core document on = the client -> AS and client -> RS parts of the protocol, allowing = the RS <-> AS leg of the diagram to vary independently, as it does = in OAuth. Unlike OAuth, there is a definite goal and desire in this WG = to focus on some forms of interoperability for the RS <-> AS = relationship, but not at the expense of its independence from the = client-facing portions.

With = the merging of PR #246, we have now factored out the portions of the = document related to AS-RS relationships. These will now be defined in a = separate draft, at:

https://github.com/ietf-wg-gnap/gnap-resource-servers
=

A proposed document = is available for review there and will be submitted as a WG document = ahead of the next interim. As a topic at the next interim, the group = will discuss how to best manage issues directed at one document or the = other, in order to help the conversations stay focused on the = appropriate portions of the protocol space. 
Thank you,
 =E2=80=94 Justin
= --Apple-Mail=_9E9C6EE5-36E3-4CEE-88AA-BA1985E8AB8E-- From nobody Sun Apr 25 00:51:08 2021 Return-Path: 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 4C6363A0CBE for ; Sun, 25 Apr 2021 00:51:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.819 X-Spam-Level: X-Spam-Status: No, score=-2.819 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.01, RCVD_IN_MSPIKE_WL=-0.01, 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=fwbT4X4C; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=EtoZDefY 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 SH6HLteJvmn8 for ; Sun, 25 Apr 2021 00:51:01 -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 811743A0CBD for ; Sun, 25 Apr 2021 00:51:01 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 55B4513EA for ; Sun, 25 Apr 2021 03:43:36 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 25 Apr 2021 03:43:36 -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=kMvmmu8Djl9pm7ZMoUi4Q2+h5HTohpCjHHXbWE+9ra4=; b=fwbT4X4C nelBEwbpNAehWa1GnVrXKl87hshKVm8Ky579QstxvyuHPVFeeFiJIfYJJi5HPTTC dVt/pi1k5OQiw4EsrKYgtnd+VEaIiqzWmzOCrbNFBacRjkEWHItP83nzouVC0R58 FNkV0UEtsu16LVzC4azMPXD71p7DrEeoMqRuW2fG//94KaMEWKiynUMKkfNiAxI2 RIxizROnPkwoVB2YYGb0zGxf7tnHR6Jvqlj0GQNducuSrM0K9tGP1AsACfq/vsWG pZsr7uxrlwNwd6sVVnG3aiWPY+sleFNKEIE4gJhYLJErUNIOuj4Uc6enTxvWmERf kdpo6Jf1y26VUQ== 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=kMvmmu8Djl9pm7ZMoUi4Q2+h5HToh pCjHHXbWE+9ra4=; b=EtoZDefYKjp7mPAB7BZ3pOggwP32b/sYTiKlRxVuvOBbj p8UDcTOXdQsLNBLi1GdXCAOhg82e8b/1HdVhtxF8FKC3/3eFD+QLQ3gM7wZRqJP0 DKfFhyETmgp90rNOWWmzrux4TllhKnBsSPlUJO/LPCipDx/oAoa3GDBU824+pMx9 Qk1WpZdvnEzp8P2joFXX7+lThRdxFcboQcn9f4W8dYpHLvP8F5u/tXVkyOhpFpkE mWLDAmMv6ghrrqRfdYupbI9i7mZfpR1UOCldwO9sEvx6b3eaRDnOMuXb1diWGG3U /xrvIdjyKzmXahCek6Qoaj3SIMPUm+LNm5kYinZGg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdduhedguddujecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffeetffdvleehudei teenucffohhmrghinhepghhithhhuhgsrdgtohhmnecukfhppeehvddrudekfedrjeehrd ehjeenucevlhhushhtvghrufhiiigvpeejnecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght X-ME-Proxy: Received: from fv-az216-331.cj41wgrgafsezefiwwcvtnsr0c.xx.internal.cloudapp.net (unknown [52.183.75.57]) by mail.messagingengine.com (Postfix) with ESMTPA id B54E9108005B for ; Sun, 25 Apr 2021 03:43:35 -0400 (EDT) Content-Type: multipart/alternative; boundary="===============1422249964758611794==" MIME-Version: 1.0 From: Repository Activity Summary Bot To: txauth@ietf.org Message-Id: <20210425074335.B54E9108005B@mailuser.nyi.internal> Date: Sun, 25 Apr 2021 03:43:35 -0400 (EDT) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Apr 2021 07:51:06 -0000 --===============1422249964758611794== 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 (+1/-16/=F0=9F=92=AC2) 1 issues created: - Discuss MTLS deployment differences (by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/253=20 2 issues received 2 new comments: - #253 Discuss MTLS deployment differences (1 by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/253=20 - #105 Rotation of bound client keys (1 by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/105=20 16 issues closed: - Protocol rationale https://github.com/ietf-wg-gnap/gnap-core-protocol/i= ssues/176=20 - Unlinkability https://github.com/ietf-wg-gnap/gnap-core-protocol/issues= /241 [Pending Close]=20 - Scalability and prior relationships between ASs and RSs https://github= .com/ietf-wg-gnap/gnap-core-protocol/issues/240 [Pending Close]=20 - Concept of a "service" supported by a set of RSs https://github.com/iet= f-wg-gnap/gnap-core-protocol/issues/238 [Pending Close]=20 - How can a client identify which ASs are trusted by the RS ? https://git= hub.com/ietf-wg-gnap/gnap-core-protocol/issues/237 [Pending Close]=20 - Definition and roles of a Resource Owner (RO) https://github.com/ietf-w= g-gnap/gnap-core-protocol/issues/213 [Pending Close]=20 - Definition of a Resource Server (RS) https://github.com/ietf-wg-gnap/gn= ap-core-protocol/issues/212 [Pending Close]=20 - "sub_id" claims https://github.com/ietf-wg-gnap/gnap-core-protocol/issu= es/210 [Pending Close]=20 - Requesting resources with insufficient access https://github.com/ietf-w= g-gnap/gnap-core-protocol/issues/203 [Pending Close]=20 - Validity of an access token https://github.com/ietf-wg-gnap/gnap-core-p= rotocol/issues/191 [Pending Close]=20 - Tentative proposal for a RS discovery mechanism https://github.com/ietf= -wg-gnap/gnap-core-protocol/issues/190 [Pending Close]=20 - Token format https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/= 189 [Pending Close]=20 - Protected and Public Resources https://github.com/ietf-wg-gnap/gnap-cor= e-protocol/issues/185 [Pending Close]=20 - Resource Server Section https://github.com/ietf-wg-gnap/gnap-core-proto= col/issues/114=20 - Expand "user interaction" discussion https://github.com/ietf-wg-gnap/gn= ap-core-protocol/issues/224=20 - Scope of subject identifiers https://github.com/ietf-wg-gnap/gnap-core-= protocol/issues/75=20 Pull requests ------------- * ietf-wg-gnap/core-protocol (+1/-6/=F0=9F=92=AC6) 1 pull requests submitted: - clarify scope of spec in introduction (by aaronpk) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/254=20 3 pull requests received 6 new comments: - #254 clarify scope of spec in introduction (1 by netlify) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/254=20 - #250 Cryptographic Key Proofing Updates (1 by jricher) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/250=20 - #246 Extract RS-focused protocol elements (4 by jricher, yaronf) https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246 [Pending Me= rge]=20 6 pull requests merged: - Appendix on protocol rationale https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/247 [Pending Me= rge]=20 - Interact example typo: nonce value must be provided using 'finish'=20 https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/251 [Editorial]= =20 - Extract RS-focused protocol elements https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/246 [Pending Me= rge]=20 - Gathering consent and authorization through interaction and other means https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/242 [Pending Me= rge]=20 - JWK definition https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/232 [Pending Me= rge]=20 - update subject info definition according to sub_ids https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/229 [Pending Me= rge]=20 Repositories tracked by this digest: ----------------------------------- * https://github.com/ietf-wg-gnap/core-protocol --===============1422249964758611794== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Weekly github digest (GNAP Weekly GitHub Activity Summary)

Sunday April 25, 2021

Events without label "editorial"

Issues

ietf-wg-gnap/core-protocol (+1/-16/=F0=9F=92=AC2)

1 issues created:

2 issues received 2 new comments:

16 issues closed:

Pull requests

ietf-wg-gnap/core-protocol (+1/-6/=F0=9F=92=AC6)

1 pull requests submitted:

3 pull requests received 6 new comments:

6 pull requests merged:

Repositories tracked by this digest:

--===============1422249964758611794==-- From nobody Wed Apr 28 13:12:11 2021 Return-Path: X-Original-To: txauth@ietf.org Delivered-To: txauth@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C6D343A1EAF; Wed, 28 Apr 2021 13:11:58 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: txauth@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.28.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: txauth@ietf.org Message-ID: <161964071870.13483.14421507452176789711@ietfa.amsl.com> Date: Wed, 28 Apr 2021 13:11:58 -0700 Archived-At: Subject: [GNAP] I-D Action: draft-ietf-gnap-core-protocol-05.txt X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2021 20:12:05 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Grant Negotiation and Authorization Protocol WG of the IETF. Title : Grant Negotiation and Authorization Protocol Authors : Justin Richer Aaron Parecki Fabien Imbault Filename : draft-ietf-gnap-core-protocol-05.txt Pages : 132 Date : 2021-04-28 Abstract: GNAP defines a mechanism for delegating authorization to a piece of software, and conveying that delegation to the software. This delegation can include access to a set of APIs as well as information passed directly to the software. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-gnap-core-protocol/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-gnap-core-protocol-05.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-gnap-core-protocol-05 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Apr 28 13:36:55 2021 Return-Path: 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 4F3D73A1F5E for ; Wed, 28 Apr 2021 13:36:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 f9yVSTXFIbfq for ; Wed, 28 Apr 2021 13:36:49 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 743513A1F5C for ; Wed, 28 Apr 2021 13:36:49 -0700 (PDT) Received: from [192.168.1.22] (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13SKakQf007842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 28 Apr 2021 16:36:47 -0400 From: Justin Richer Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Wed, 28 Apr 2021 16:36:46 -0400 References: <161964071870.13483.14421507452176789711@ietfa.amsl.com> To: GNAP Mailing List In-Reply-To: <161964071870.13483.14421507452176789711@ietfa.amsl.com> Message-Id: <733855E9-4227-43FF-A92F-8233DC27444B@mit.edu> X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [GNAP] I-D Action: draft-ietf-gnap-core-protocol-05.txt X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2021 20:36:53 -0000 Everyone, The editors have published a new version of the core specification. = Please try to give it a read through in preparation for next week=E2=80=99= s interim meeting. =E2=80=94 Justin > On Apr 28, 2021, at 4:11 PM, internet-drafts@ietf.org wrote: >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Grant Negotiation and Authorization = Protocol WG of the IETF. >=20 > Title : Grant Negotiation and Authorization Protocol > Authors : Justin Richer > Aaron Parecki > Fabien Imbault > Filename : draft-ietf-gnap-core-protocol-05.txt > Pages : 132 > Date : 2021-04-28 >=20 > Abstract: > GNAP defines a mechanism for delegating authorization to a piece of > software, and conveying that delegation to the software. This > delegation can include access to a set of APIs as well as = information > passed directly to the software. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-gnap-core-protocol/ >=20 > There is also an HTML version available at: > https://www.ietf.org/archive/id/draft-ietf-gnap-core-protocol-05.html >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-gnap-core-protocol-05 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 >=20 > --=20 > TXAuth mailing list > TXAuth@ietf.org > https://www.ietf.org/mailman/listinfo/txauth From nobody Wed Apr 28 16:16:37 2021 Return-Path: X-Original-To: txauth@ietf.org Delivered-To: txauth@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C12C33A23B8; Wed, 28 Apr 2021 16:16:31 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: txauth@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.28.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: txauth@ietf.org Message-ID: <161965179164.19528.16718040316850564701@ietfa.amsl.com> Date: Wed, 28 Apr 2021 16:16:31 -0700 Archived-At: Subject: [GNAP] I-D Action: draft-ietf-gnap-resource-servers-00.txt X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2021 23:16:32 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Grant Negotiation and Authorization Protocol WG of the IETF. Title : Grant Negotiation and Authorization Protocol Resource Server Connections Authors : Justin Richer Aaron Parecki Fabien Imbault Filename : draft-ietf-gnap-resource-servers-00.txt Pages : 12 Date : 2021-04-28 Abstract: GNAP defines a mechanism for delegating authorization to a piece of software, and conveying that delegation to the software. This extension defines methods for resource servers (RS) to communicate with authorization servers (AS) in an interoperable fashion. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-gnap-resource-servers/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-gnap-resource-servers-00.html Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Apr 28 17:31:44 2021 Return-Path: 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 6B2AA3A26CA for ; Wed, 28 Apr 2021 17:31:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.497 X-Spam-Level: X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.4, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no 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 jVVG2HWmal9j for ; Wed, 28 Apr 2021 17:31:40 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69B4E3A26C6 for ; Wed, 28 Apr 2021 17:31:40 -0700 (PDT) Received: from [192.168.1.22] (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13T0VbOK006624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 28 Apr 2021 20:31:38 -0400 From: Justin Richer Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Wed, 28 Apr 2021 20:31:37 -0400 References: <161965179164.19528.16718040316850564701@ietfa.amsl.com> To: GNAP Mailing List In-Reply-To: <161965179164.19528.16718040316850564701@ietfa.amsl.com> Message-Id: X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [GNAP] I-D Action: draft-ietf-gnap-resource-servers-00.txt X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2021 00:31:43 -0000 Everyone, As previously discussed, the editors have pulled the RS-AS portions of = the protocol out to a separate document to help focus discussion. We = will be discussing our process of managing both documents, including = issues, PRs, and releases, at the interim next week. =E2=80=94 Justin > On Apr 28, 2021, at 7:16 PM, internet-drafts@ietf.org wrote: >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Grant Negotiation and Authorization = Protocol WG of the IETF. >=20 > Title : Grant Negotiation and Authorization Protocol = Resource Server Connections > Authors : Justin Richer > Aaron Parecki > Fabien Imbault > Filename : draft-ietf-gnap-resource-servers-00.txt > Pages : 12 > Date : 2021-04-28 >=20 > Abstract: > GNAP defines a mechanism for delegating authorization to a piece of > software, and conveying that delegation to the software. This > extension defines methods for resource servers (RS) to communicate > with authorization servers (AS) in an interoperable fashion. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-gnap-resource-servers/ >=20 > There is also an HTML version available at: > = https://www.ietf.org/archive/id/draft-ietf-gnap-resource-servers-00.html >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 >=20 > --=20 > TXAuth mailing list > TXAuth@ietf.org > https://www.ietf.org/mailman/listinfo/txauth From nobody Fri Apr 30 03:21:02 2021 Return-Path: X-Original-To: txauth@ietf.org Delivered-To: txauth@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D743A3A0DCA; Fri, 30 Apr 2021 03:20:59 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: gnap-chairs@ietf.org, rdd@cert.org, txauth@ietf.org, yaronf.ietf@gmail.com X-Test-IDTracker: no X-IETF-IDTracker: 7.28.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <161977805986.14439.11126149382197525113@ietfa.amsl.com> Date: Fri, 30 Apr 2021 03:20:59 -0700 Archived-At: Subject: [GNAP] gnap - New Meeting Session Request for IETF 111 X-BeenThere: txauth@ietf.org X-Mailman-Version: 2.1.29 List-Id: GNAP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Apr 2021 10:21:00 -0000 A new meeting session request has just been submitted by Yaron Sheffer, a Chair of the gnap working group. --------------------------------------------------------- Working Group Name: Grant Negotiation and Authorization Protocol Area Name: Security Area Session Requester: Yaron Sheffer Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 100 Conflicts to Avoid: Chair Conflict: ace acme cose curdle dots emu i2nsf ipsecme kitten lake lamps mls rats sacm secdispatch secevent suit teep tls trans httpbis quic saag uta cfrg Technology Overlap: oauth People who must be present: Yaron Sheffer Roman Danyliw Leif Johansson Resources Requested: Special Requests: ---------------------------------------------------------