IETF Logo Mail Archive

Re: [Ace] Update of access rights

Jim Schaad <ietf@augustcellars.com> Mon, 18 May 2020 13:13 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FC633A0B46 for <ace@ietfa.amsl.com>; Mon, 18 May 2020 06:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-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 2InNdN3GsPHu for <ace@ietfa.amsl.com>; Mon, 18 May 2020 06:13:46 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A20F3A0ABE for <ace@ietf.org>; Mon, 18 May 2020 06:13:45 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 18 May 2020 06:13:20 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Olaf Bergmann' <bergmann@tzi.org>
CC: 'Francesca Palombini' <francesca.palombini@ericsson.com>, 'Ace Wg' <ace@ietf.org>
References: <8063D003-2C48-4157-B80E-B7AF3D2099FC@ericsson.com> <20680.1588694462@localhost> <CB1396B3-5D52-422A-AFC4-0FB362C2C0F5@ericsson.com> <29287.1588780702@localhost> <006401d62cc3$70d795f0$5286c1d0$@augustcellars.com> <87eerhkb2i.fsf@wangari>
In-Reply-To: <87eerhkb2i.fsf@wangari>
Date: Mon, 18 May 2020 06:13:18 -0700
Message-ID: <008a01d62d16$1a934d80$4fb9e880$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQHYz/rnI4HjFcemc1imkKmWhr9LqwIHn/F4Acb/RDkDYpVdMQHR58enAwOeLE+oSFVQgA==
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/K_pNeiQw4c-UryWXoWLGlLS2Ivs>
Subject: Re: [Ace] Update of access rights
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2020 13:13:48 -0000

As I said, I have not fully thought it out.  A better way to state this might be - this token uses the same key as rather than implying overriding.

-----Original Message-----
From: Olaf Bergmann <bergmann@tzi.org> 
Sent: Sunday, May 17, 2020 11:32 PM
To: Jim Schaad <ietf@augustcellars.com>
Cc: 'Francesca Palombini' <francesca.palombini@ericsson.com>; 'Ace Wg' <ace@ietf.org>
Subject: Re: [Ace] Update of access rights

Hi Jim,

Jim Schaad <ietf@augustcellars.com> writes:

> define a new claim which says - This token supersedes the token(s) 
> with CWTID values of "x", "y" and "z".

Isn't this the same as token revocation with all its implications?  I would prefer strict token ordering combined with a sound revocation mechanism. In both scenarios, you would still have the issue that the client forwards the superseding token/revocation message if it has a benefit from doing so.

Grüße
Olaf

v2.23.0 | Report a Bug | By Email