[Id-event] [Technical Errata Reported] RFC9493 (7727)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 11 December 2023 22: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 6B4ACC14F5FB for <id-event@ietfa.amsl.com>; Mon, 11 Dec 2023 14:25:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 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, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 DeK5SZzD7_sw for <id-event@ietfa.amsl.com>; Mon, 11 Dec 2023 14:25:39 -0800 (PST)
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 956AEC14F5EE for <id-event@ietf.org>; Mon, 11 Dec 2023 14:25:39 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id DD97476345; Mon, 11 Dec 2023 14:25:38 -0800 (PST)
To: richanna@amazon.com, marius.scurtescu@coinbase.com, prachi.jain1288@gmail.com, rdd@cert.org, paul.wouters@aiven.io, dick.hardt@gmail.com, yaronf.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: atul@sgnl.ai, id-event@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231211222538.DD97476345@rfcpa.amsl.com>
Date: Mon, 11 Dec 2023 14:25:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/WvuW75DVhmM14nsL1feXi82BRAs>
Subject: [Id-event] [Technical Errata Reported] 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: Mon, 11 Dec 2023 22:25:43 -0000
The following errata report has been submitted for RFC9493, "Subject Identifiers for Security Event Tokens". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7727 -------------------------------------- Type: Technical Reported by: Atul Tulshibagwale <atul@sgnl.ai> Section: 8.1 Original Text ------------- Security Event Identifier Formats Registry Corrected Text -------------- Subject Identifier Formats Registry 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 should be named "Subject Identifier Formats Registry", and not "Security Event Identifier Formats Registry". Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- 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 Area : Security Stream : IETF Verifying Party : IESG
- [Id-event] [Technical Errata Reported] RFC9493 (7… RFC Errata System
- Re: [Id-event] [Technical Errata Reported] RFC949… Rebecca VanRheenen
- Re: [Id-event] [Technical Errata Reported] RFC949… Atul Tulshibagwale