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

Atul Tulshibagwale <atul@sgnl.ai> Tue, 12 December 2023 17:06 UTC

Return-Path: <atul@sgnl.ai>
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 1718AC14CF09 for <id-event@ietfa.amsl.com>; Tue, 12 Dec 2023 09:06:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sgnl-ai.20230601.gappssmtp.com
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 yGNwDr75MoLu for <id-event@ietfa.amsl.com>; Tue, 12 Dec 2023 09:06:53 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 3B8AEC14CF05 for <id-event@ietf.org>; Tue, 12 Dec 2023 09:06:52 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id 41be03b00d2f7-5ca29c131ebso1303389a12.0 for <id-event@ietf.org>; Tue, 12 Dec 2023 09:06:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sgnl-ai.20230601.gappssmtp.com; s=20230601; t=1702400812; x=1703005612; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6Aw5D6D9p8UF+u6OS1RHw0wcCrE3Rd+byQboWOZc6b4=; b=QMzHExJmnBgDIstvSqEhI/pIHM0Oj1R2VkxmK6nBT6gX6g2jc8rM3jd1klaYhwj5zv gpI63VIfjjdoYzENL83bmSqXGrM/NLsan6KcJHTPm3f57AjvCyueJ7zWKLxdH1eU/Ui2 nhYpPNsR+0FytSyJd0MK56QC7DDE0nIf2KL944h11GW2drFq8+B8a6WYfTGBZxJfs9a9 JJkTjdNKzwvn3DJHpmR8MmhvY+bd5gnw00Uxxo0JhvWsh7ooJNoKqu39QM2Kes9vmNlO 9PBO/JKYYrUFxuLLZAxo7ogqZp4rUrytTZks3Togc0lI2hfxKI4OZNDHhbZkMIuF5cU7 8YfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702400812; x=1703005612; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=6Aw5D6D9p8UF+u6OS1RHw0wcCrE3Rd+byQboWOZc6b4=; b=nLKj+lxUhSajBmWq5Qj8Elc9w1NobT+3tCwujMJxs4pAstJXTSnWCTJRpmSR/rFKC/ xZ0LVRELpmpFEi1lMefgvbHx4lmB5RS10imy/P+35b82NZsk4qcyCZ4zFYZ59RuP/xZn QOmmaholTP7hswjVWrFcIVI7ybfuOY2hthf3mlCSjoWb1ekJhp1mq/C1ekcfQXLDBHcr kgtR16rsePrxubmLMQ2DEvaFe5NJz/XPD48MiqBsZ2n6yFRjy5FeUvikVY2g9LdqXURp BhPohPnEHgCAUMBuTqpnzXD2gdR2wZQfexylmZzkb0DDarIuHGcWhdNTnh6jVQQgvaqb L6OQ==
X-Gm-Message-State: AOJu0YzjTiWP+cyKvsioB5eJiAm5zeL3bw8aaN86MoI6A4CIsHaSuIJu a8AN17IFn5Pc9YVQGtkUmnk5uP9DuVZ5eUnfUmPrvhxB+WziGg5l
X-Google-Smtp-Source: AGHT+IGXSkZJoYHRVCmQy+tf1ByptOAVvXJpekmjjgqCgIvkRuZ7EHPgwAgnX87vmN5tUyHemUcbc2+a3uyAHX4i0Rg=
X-Received: by 2002:a17:90b:f10:b0:28a:c5e5:98da with SMTP id br16-20020a17090b0f1000b0028ac5e598damr969622pjb.54.1702400812107; Tue, 12 Dec 2023 09:06:52 -0800 (PST)
MIME-Version: 1.0
References: <20231211222538.DD97476345@rfcpa.amsl.com> <E074A573-E537-4785-8573-4F940CA384B1@amsl.com>
In-Reply-To: <E074A573-E537-4785-8573-4F940CA384B1@amsl.com>
From: Atul Tulshibagwale <atul@sgnl.ai>
Date: Tue, 12 Dec 2023 09:06:36 -0800
Message-ID: <CANtBS9epN4WwMJm5CiArSX1eK=EPW2b7xerCyvzAL__EhuNbWQ@mail.gmail.com>
To: Rebecca VanRheenen <rvanrheenen@amsl.com>
Cc: 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, id-event@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary="000000000000abdd33060c5313bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/ojcLiiQ1sfOzyOETgnEiKMtJMOo>
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:06:57 -0000

Thanks, no concerns from my side.

Atul

On Tue, Dec 12, 2023 at 9:05 AM Rebecca VanRheenen <rvanrheenen@amsl.com>
wrote:

> 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
> >
>
>