[Id-event] [Errata Held for Document Update] RFC9493 (7727)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 05 April 2024 13:25 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F4212C14F70F; Fri, 5 Apr 2024 06:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.649
X-Spam-Level:
X-Spam-Status: No, score=-6.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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 IxdcBWo6XwrF; Fri, 5 Apr 2024 06:25:54 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (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 B4DC4C15106A; Fri, 5 Apr 2024 06:25:54 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 770AE192F799; Fri, 5 Apr 2024 06:25:54 -0700 (PDT)
To: atul@sgnl.ai, richanna@amazon.com, marius.scurtescu@coinbase.com, prachi.jain1288@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: paul.wouters@aiven.io, iesg@ietf.org, id-event@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240405132554.770AE192F799@rfcpa.amsl.com>
Date: Fri, 05 Apr 2024 06:25:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/baxlNnN5JRa2jwAd0tgWqiBUFGQ>
Subject: [Id-event] [Errata Held for Document Update] RFC9493 (7727)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2024 13:25:59 -0000

The following errata report has been held for document update 
for RFC9493, "Subject Identifiers for Security Event Tokens". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7727

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Atul Tulshibagwale <atul@sgnl.ai>
Date Reported: 2023-12-11
Held by: Paul Wouters (IESG)

Section: GLOBAL

Original Text
-------------
Security Event Identifier Formats

Corrected Text
--------------
Subject Identifier Formats

Notes
-----
The identifiers described in the RFC are relating to subject fields in Security Event Tokens, and not to the Security Event Tokens as a whole. This is clearly stated in the first sentence of Section 1 (Introduction) and the first sentence of the second paragraph of Section 1 (Introduction).

Therefore, the registry defined in Section 8.1 should be named "Subject Identifier Formats", and not "Security Event Identifier Formats".

Paul Wouters(AD): See https://mailarchive.ietf.org/arch/msg/id-event/-S-MsO2W6PeFF_O5kjP8om-7QNM/

--------------------------------------
RFC9493 (draft-ietf-secevent-subject-identifiers-18)
--------------------------------------
Title               : Subject Identifiers for Security Event Tokens
Publication Date    : December 2023
Author(s)           : A. Backman, Ed., M. Scurtescu, P. Jain
Category            : PROPOSED STANDARD
Source              : Security Events
Stream              : IETF
Verifying Party     : IESG