IETF Logo Mail Archive

Re: [Id-event] [Technical Errata Reported] RFC9493 (7727)

Rebecca VanRheenen <rvanrheenen@amsl.com> Tue, 12 December 2023 17:05 UTC

Return-Path: <rvanrheenen@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 972CAC14CEFD for <id-event@ietfa.amsl.com>; Tue, 12 Dec 2023 09:05:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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=unavailable 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 5rnyWj2Phewc for <id-event@ietfa.amsl.com>; Tue, 12 Dec 2023 09:05:46 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 976EBC14F5E9 for <id-event@ietf.org>; Tue, 12 Dec 2023 09:05:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 8923D424CD01; Tue, 12 Dec 2023 09:05:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ob7zlaQg4A4B; Tue, 12 Dec 2023 09:05:46 -0800 (PST)
Received: from [IPv6:2601:641:300:5fb0:ed0c:7f19:a672:1612] (unknown [IPv6:2601:641:300:5fb0:ed0c:7f19:a672:1612]) by c8a.amsl.com (Postfix) with ESMTPSA id 5A3A3424B432; Tue, 12 Dec 2023 09:05:46 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Rebecca VanRheenen <rvanrheenen@amsl.com>
In-Reply-To: <20231211222538.DD97476345@rfcpa.amsl.com>
Date: Tue, 12 Dec 2023 09:05:45 -0800
Cc: atul@sgnl.ai, id-event@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E074A573-E537-4785-8573-4F940CA384B1@amsl.com>
References: <20231211222538.DD97476345@rfcpa.amsl.com>
To: richanna@amazon.com, marius.scurtescu@coinbase.com, prachi.jain1288@gmail.com, Roman Danyliw <rdd@cert.org>, Paul Wouters <paul.wouters@aiven.io>, dick.hardt@gmail.com, yaronf.ietf@gmail.com
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/8KP3ZNSyndsHGhQ0si-ojm-BVLs>
Subject: Re: [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: Tue, 12 Dec 2023 17:05:51 -0000

Greetings,

This errata reports a possible issue in Section 8.1. However, we note that the name of the registry appears several times in the document, not just in Section 8.1. We thus updated “Section 8.1” to “GLOBAL”. Please let us know any concerns. 

Thank you,
RFC Editor/rv


> On Dec 11, 2023, at 2:25 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> 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
>

v2.23.0 | Report a Bug | By Email