[Ace] Re: [IANA #1367581] expert review for draft-ietf-ace-revoked-token-notification (core-parameters - Custom Problem Detail Keys)
Carsten Bormann <cabo@tzi.org> Thu, 11 July 2024 04:09 UTC
Return-Path: <cabo@tzi.org>
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 3539FC1516E1 for <ace@ietfa.amsl.com>; Wed, 10 Jul 2024 21:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S8bKhgHFoXvM for <ace@ietfa.amsl.com>; Wed, 10 Jul 2024 21:08:54 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28C7CC15155F for <ace@ietf.org>; Wed, 10 Jul 2024 21:08:53 -0700 (PDT)
Received: from smtpclient.apple (p5089ae14.dip0.t-ipconnect.de [80.137.174.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4WKLnY6SBPzDCcS; Thu, 11 Jul 2024 06:08:49 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <rt-5.0.3-717310-1720644697-873.1367581-9-0@icann.org>
Date: Thu, 11 Jul 2024 06:08:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC2CFE1A-2AA3-4F94-B889-377D87A08D9D@tzi.org>
References: <RT-Ticket-1367581@icann.org> <rt-5.0.3-945252-1719972220-755.1367581-9-0@icann.org> <rt-5.0.3-953546-1719972621-44.1367581-9-0@icann.org> <rt-5.0.3-477670-1720490107-143.1367581-9-0@icann.org> <rt-5.0.3-717310-1720644697-873.1367581-9-0@icann.org>
To: Sabrina Tanamal via RT <drafts-expert-review-comment@iana.org>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: JCBYY5A5B43JTTHQDYK5CK7PPJLHRMBX
X-Message-ID-Hash: JCBYY5A5B43JTTHQDYK5CK7PPJLHRMBX
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ace.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ace@ietf.org, Thomas.Fossati@arm.com
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Ace] Re: [IANA #1367581] expert review for draft-ietf-ace-revoked-token-notification (core-parameters - Custom Problem Detail Keys)
List-Id: "Authentication and Authorization for Constrained Environments (ace)" <ace.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/0taLYJOCRH_yZu8K1pRbNa4FShQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Owner: <mailto:ace-owner@ietf.org>
List-Post: <mailto:ace@ietf.org>
List-Subscribe: <mailto:ace-join@ietf.org>
List-Unsubscribe: <mailto:ace-leave@ietf.org>
Hi Amanda, I approve the registration. I have an editorial comment on Section 5.1 (which supplies the specification that the IANA considerations reference). This has a rather terse definition of the “cursor” field, with no indication on where to continue reading (there is an example that gives a hunch of at least one intended usage). There are 135 occurrences of the word “cursor”, so it would be rather tedious to find the places where the use of the field in problem details is actually defined. Could a reference from Section 5.1 to that text be added? Grüße, Carsten > On 10. Jul 2024, at 22:51, Amanda Baber via RT <drafts-expert-review-comment@iana.org> wrote: > > Hi Thomas, Carsten, > > We had to submit our ballot response to the IESG today, so we marked it "IANA NOT OK." Can one of you get to this one before the telechat (1400 UTC tomorrow)? > > thanks, > Amanda > > On Tue Jul 09 01:55:07 2024, amanda.baber wrote: >> Hi Thomas, Carsten, >> >> Sending a reminder for this review request. Can you get to this one >> before Thursday? >> >> thanks, >> Amanda >> >> On Wed Jul 03 02:10:21 2024, amanda.baber wrote: >>> Hi Thomas and Carsten (cc: ace WG) >>> >>> Can you review the new Custom Problem Detail Key registration in this >>> document by Wednesday, July 10th? >>> >>> https://datatracker.ietf.org/doc/html/draft-ietf-ace-revoked-token- >>> notification-08 >>> >>> This document is on the July 11th IESG telechat agenda. The >>> registration was added after IETF Last Call, so we just now caught >>> it. >>> >>> Unless you ask us to wait for both experts, we'll consider the review >>> complete after we receive the first response. >>> >>> thanks, >>> >>> Amanda Baber >>> IANA Operations Manager >
- [Ace] [IANA #1367581] expert review for draft-iet… Amanda Baber via RT
- [Ace] Re: [IANA #1367581] expert review for draft… Carsten Bormann