[GNAP] GNAP Editors Update

Justin Richer <jricher@mit.edu> Fri, 11 February 2022 17:16 UTC

Return-Path: <jricher@mit.edu>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B6C833A079F for <txauth@ietfa.amsl.com>; Fri, 11 Feb 2022 09:16:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id CWhqxqvECZ8L for <txauth@ietfa.amsl.com>; Fri, 11 Feb 2022 09:16:04 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu []) (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 4A1B73A079E for <txauth@ietf.org>; Fri, 11 Feb 2022 09:16:03 -0800 (PST)
Received: from smtpclient.apple (static-71-174-62-56.bstnma.fios.verizon.net []) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 21BHG1xB006245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <txauth@ietf.org>; Fri, 11 Feb 2022 12:16:02 -0500
From: Justin Richer <jricher@mit.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D0EB6C75-17F1-41AE-B5DE-C1ADFCCFCF40"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.\))
Message-Id: <9936CC61-65BA-4D4C-B190-99475DA4BE94@mit.edu>
Date: Fri, 11 Feb 2022 12:16:01 -0500
To: GNAP Mailing List <txauth@ietf.org>
X-Mailer: Apple Mail (2.3693.
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/tV_B5XTMZsOur0ewqdD1yFapsfE>
Subject: [GNAP] GNAP Editors Update
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: GNAP <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2022 17:16:07 -0000

The editors met this week and are working on a number of issues ahead of IETF113. The issue tracker will have all of the details, including who’s been assigned to what topic. We’ve tried to add comments on each of these issues to give an idea of which direction we’re planning to go to resolve them. 

There are several issues that have been marked “Pending Close” since it seems that either the issue has been resolved by other work, or it’s no longer relevant due to changes in the spec since the issue was filed. These will be closed without changes after 1 week unless there’s significant push from the WG to do otherwise.

#49: AS Validation of RC-presented assertions
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/49 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/49>

#77: Dynamic RC instance registration
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/77 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/77>

#20: Interaction “Modes”
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/20 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/20>

#43: User information request items
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/43 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/43>

#50: User identification items
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/50 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/50>

#72: Separation of AS into delegation and interaction
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/72 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/72>

Additionally, one additional issue been tagged as “Need Text”. These are items that need clearer direction and input from the working group to warrant a change to the specification text before they can affect anything. As is usually the case, many of these things seem like they might be good ideas, but it’s not clear that there’s a driving use case with enough detail to specify things at this time. These will remain open for now but the editors are not focusing any effort on addressing them at this time, and they may be marked Pending Close in the future if nobody steps up.

#44: Client attestation and posture
https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/44 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/44>

Finally, there are a number of pull requests that have been marked “Pending Merge”. These changes will be merged in one week unless there’s significant push back or cause to do otherwise. Please take a look as these are all concrete changes:

#385: expand error codes
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/385 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/385>

#383: update manage URI section
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/383 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/383>

#382: one time use clarification
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/382 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/382>

#381: reference for safe URL
https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/381 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/381>

Thank you everyone for your attention to all these items, please supply your comments in GitHub on the issues and PRs themselves.

 — Justin