Re: [GNAP] Trimmed Features

Justin Richer <jricher@mit.edu> Mon, 28 June 2021 20:00 UTC

Return-Path: <jricher@mit.edu>
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 7BCB23A0D4A for <txauth@ietfa.amsl.com>; Mon, 28 Jun 2021 13:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 T3axn_ngzLdN for <txauth@ietfa.amsl.com>; Mon, 28 Jun 2021 13:00:41 -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 1547C3A0D38 for <txauth@ietf.org>; Mon, 28 Jun 2021 13:00:40 -0700 (PDT)
Received: from [192.168.1.49] (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 15SK0cIT008092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <txauth@ietf.org>; Mon, 28 Jun 2021 16:00:39 -0400
From: Justin Richer <jricher@mit.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_38720C92-AAA3-4DF5-AE98-8980519C55FA"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Mon, 28 Jun 2021 16:00:38 -0400
References: <9490FCC5-44EF-493F-9D19-05B577C044CA@mit.edu>
To: GNAP Mailing List <txauth@ietf.org>
In-Reply-To: <9490FCC5-44EF-493F-9D19-05B577C044CA@mit.edu>
Message-Id: <D7DF0540-49B5-4E72-BB10-EE37377CF72A@mit.edu>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/JLkY9VSNGIIoPBSVeZSTDm58Gxo>
Subject: Re: [GNAP] Trimmed Features
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: Mon, 28 Jun 2021 20:00:46 -0000

I just pushed another commit to this PR that removes the separate “instance_id” field from the client request. Previously it was possible to send this both as a field within a restricted object as well as a separate string value on its own. Now, only the latter remains as an option, and this change would close https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/45 <https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/45> in the process.

 — Justin

> On Jun 25, 2021, at 4:30 PM, Justin Richer <jricher@mit.edu> wrote:
> 
> In the past, we’ve discussed the need to trim down some of the advanced features included in GNAP core. After a discussion this week, the editors have targeted two features for removal and have pushed a PR to take these out of the spec.
> 
> Namely, these are:
> 
>  - the “capabilities” array, which was intended to be a holding place for extension identifiers and additional functionality. However, no extensions have shown up that needed this field, and so the editors are recommending that we remove it.
>  - the “existing_grant” field, which was a way to allow a client to reference an existing grant request and create a new request based on it. This was born out of a few early use cases, but now that there’s no longer an explicit identifier for the grant itself, there is less to hold on to here. Additionally, the continuation “update” function might be able to fit most of the identified use cases. 
> 
> The PR that removes these is here:
> 
> https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/270 <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/270>
> 
> If you have a compelling reason to keep either of these in the core document, please start that discussion now and help us understand why they should stay. Keep in mind that either or both of these could be added back in by a separate extension document, given GNAP core’s highly extensible nature.
> 
> — Justin
> -- 
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth