Re: [Id-event] RFC 9493 on Subject Identifiers for Security Event Tokens
Atul Tulshibagwale <atul@sgnl.ai> Mon, 11 December 2023 19:54 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 11F15C14CE45 for <id-event@ietfa.amsl.com>; Mon, 11 Dec 2023 11:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 zn4YFPiLbNJ6 for <id-event@ietfa.amsl.com>; Mon, 11 Dec 2023 11:54:34 -0800 (PST)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 C3F22C14F747 for <id-event@ietf.org>; Mon, 11 Dec 2023 11:54:34 -0800 (PST)
Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-286b45c5a8dso5086064a91.1 for <id-event@ietf.org>; Mon, 11 Dec 2023 11:54:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sgnl-ai.20230601.gappssmtp.com; s=20230601; t=1702324473; x=1702929273; 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=zlUWI4yz/3MUW0/z75zXu14Lu24m30pbgNJ4ZEt0wwk=; b=wlaPlO9BxHGp/cGBbvd3uxD4gaNBKPG6E2/qp9P89/ZguFcc/IUhDxSJeaJH984RMl YvBGvcvEKuYCsJ8alojy5bgomUTHMjah3paazbgEBasWTGuu3QPhUy6LEUG9Mm/Vaaxx krC12/+1sAJnz6kje1tDfhF85deLB3efbDh6YdlNfFt3BJEkslFTlf4nM3YOAS2ikaKY QpEM3YXDLRAIpl5/hbv+21/FMqaiXxDnEA2+sxVh94YxFI5Vc/T3tbzWEtbxMwgSWWm+ Mz+lXiiRCT0N9NVnDDP85giQXYGsDP4cm9BqS1gJiPjFXEI3hBMNxVw2yTMfJre5JHrk igyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702324473; x=1702929273; 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=zlUWI4yz/3MUW0/z75zXu14Lu24m30pbgNJ4ZEt0wwk=; b=p6zaUdzoHUq672RYtFmT6Xqvv4E6GygkEDxqnpvJPKgKQvF0xQL5W1rqc6A92XQeM4 8i8pOcRutnRHP6pqXP+E0gRA8sPYi8JIrrWw74pZNT2x8m5/6panRb0WLfM5G2c4OQo3 TXwu45b/DFxi8jlErBrNg0N2dvG3qbpiJyw6rhK2u38Nx06V5vBtivrshoEf/vZUG0ux n7jXcNgQOlY5heDS0sjKnraY6t4wxUV0Eq8SjlJd+IGT68UapwtdAWrvlAhfTTHoMnoZ kiXA3mA3BriF/MfEiocr4P97BhE2ChFATfTSJdI3fudamvwBJoAq/C3tgT71Mt8OPcoY xbDQ==
X-Gm-Message-State: AOJu0YxS4yNPgLEyu5g1qVZXxAjcGjFvdPumQIsYsOM6eG2nd8gP/eNe yo3GpM50i49gV1oCJ9j6fWdsCTMANNmYAXH5ZEOVsQ==
X-Google-Smtp-Source: AGHT+IF8lA8F3yVLVYJ0YUEB5vtcVzEMSQzkCBhxG2yovqXPWLNSMjSjRXCqWUb4XoALroXwLRYKRouA11LnFlUvjqg=
X-Received: by 2002:a17:90a:ee8d:b0:28a:3562:7d71 with SMTP id i13-20020a17090aee8d00b0028a35627d71mr3401840pjz.35.1702324473429; Mon, 11 Dec 2023 11:54:33 -0800 (PST)
MIME-Version: 1.0
References: <20231207010618.7B21719073C5@rfcpa.amsl.com> <D41A05EF-7402-456B-8190-7C8EA65575A8@gmail.com> <CAA1-vB3fVQEu=eQbPYFk6DcQqvU3b8mzBYGJzOR9yzFw7WGAbQ@mail.gmail.com>
In-Reply-To: <CAA1-vB3fVQEu=eQbPYFk6DcQqvU3b8mzBYGJzOR9yzFw7WGAbQ@mail.gmail.com>
From: Atul Tulshibagwale <atul@sgnl.ai>
Date: Mon, 11 Dec 2023 11:54:17 -0800
Message-ID: <CANtBS9dvRAyXXUjCHKQtC3nyP+tXhYKmZ=Fb98qgX53er6Z5JQ@mail.gmail.com>
To: Prachi Jain <prachi.jain1288@gmail.com>
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, id-event@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008813f1060c414d01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/UDrw8LsdP5Wciu62IbAyCoLNr78>
Subject: Re: [Id-event] RFC 9493 on Subject Identifiers for Security Event Tokens
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 19:54:39 -0000
Thanks Yaron, I think I discovered an issue with the spec, just as I was trying to refer to it: Section 8.1 is named "Security Event Identifier Formats Registry". Should it be named "Subject Identifier Formats Registry"? There are a few more changes that will flow from there, if this is considered to be an error. Atul On Thu, Dec 7, 2023 at 3:51 AM Prachi Jain <prachi.jain1288@gmail.com> wrote: > Thanks Yaron. Truly appreciate the guidance and support in getting this > past the finish line. > > On Thu, Dec 7, 2023 at 5:04 AM Yaron Sheffer <yaronf.ietf@gmail.com> > wrote: > >> Congratulations on this last deliverable of the Security Events working >> group. Thanks to Annabelle and Prachi who drove this document to completion! >> >> Yaron >> >> On 07/12/2023, 3:06, "id-event-bounces@ietf.org <mailto: >> id-event-bounces@ietf.org> on behalf of rfc-editor@rfc-editor.org >> <mailto:rfc-editor@rfc-editor.org>" <id-event-bounces@ietf.org <mailto: >> id-event-bounces@ietf.org> on behalf of rfc-editor@rfc-editor.org >> <mailto:rfc-editor@rfc-editor.org>> wrote: >> >> >> A new Request for Comments is now available in online RFC libraries. >> >> >> >> >> RFC 9493 >> >> >> Title: Subject Identifiers for Security Event Tokens >> Author: A. Backman, Ed., >> M. Scurtescu, >> P. Jain >> Status: Standards Track >> Stream: IETF >> Date: December 2023 >> Mailbox: richanna@amazon.com <mailto:richanna@amazon.com>, >> marius.scurtescu@coinbase.com <mailto:marius.scurtescu@coinbase.com>, >> prachi.jain1288@gmail.com <mailto:prachi.jain1288@gmail.com> >> Pages: 18 >> Updates/Obsoletes/SeeAlso: None >> >> >> I-D Tag: draft-ietf-secevent-subject-identifiers-18.txt >> >> >> URL: https://www.rfc-editor.org/info/rfc9493 < >> https://www.rfc-editor.org/info/rfc9493> >> >> >> DOI: 10.17487/RFC9493 >> >> >> Security events communicated within Security Event Tokens may support >> a variety of identifiers to identify subjects related to the event. >> This specification formalizes the notion of Subject Identifiers as >> structured information that describes a subject and named formats >> that define the syntax and semantics for encoding Subject Identifiers >> as JSON objects. It also establishes a registry for defining and >> allocating names for such formats as well as the JSON Web Token (JWT) >> "sub_id" Claim. >> >> >> This document is a product of the Security Events Working Group of the >> IETF. >> >> >> This is now a Proposed Standard. >> >> >> STANDARDS TRACK: This document specifies an Internet Standards Track >> protocol for the Internet community, and requests discussion and >> suggestions >> for improvements. Please refer to the current edition of the Official >> Internet Protocol Standards (https://www.rfc-editor.org/standards < >> https://www.rfc-editor.org/standards>) for the >> standardization state and status of this protocol. Distribution of this >> memo is unlimited. >> >> >> This announcement is sent to the IETF-Announce and rfc-dist lists. >> To subscribe or unsubscribe, see >> https://www.ietf.org/mailman/listinfo/ietf-announce < >> https://www.ietf.org/mailman/listinfo/ietf-announce> >> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist < >> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist> >> >> >> For searching the RFC series, see https://www.rfc-editor.org/search < >> https://www.rfc-editor.org/search> >> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk < >> https://www.rfc-editor.org/retrieve/bulk> >> >> >> Requests for special distribution should be addressed to either the >> author of the RFC in question, or to rfc-editor@rfc-editor.org <mailto: >> rfc-editor@rfc-editor.org>. Unless >> specifically noted otherwise on the RFC itself, all RFCs are for >> unlimited distribution. >> >> >> >> >> The RFC Editor Team >> Association Management Solutions, LLC >> >> >> _______________________________________________ >> Id-event mailing list >> Id-event@ietf.org <mailto:Id-event@ietf.org> >> https://www.ietf.org/mailman/listinfo/id-event < >> https://www.ietf.org/mailman/listinfo/id-event> >> >> >> >> >> _______________________________________________ >> Id-event mailing list >> Id-event@ietf.org >> https://www.ietf.org/mailman/listinfo/id-event >> > _______________________________________________ > Id-event mailing list > Id-event@ietf.org > https://www.ietf.org/mailman/listinfo/id-event >
- [Id-event] RFC 9493 on Subject Identifiers for Se… rfc-editor
- Re: [Id-event] RFC 9493 on Subject Identifiers fo… Prachi Jain
- Re: [Id-event] RFC 9493 on Subject Identifiers fo… Yaron Sheffer
- Re: [Id-event] RFC 9493 on Subject Identifiers fo… Atul Tulshibagwale
- Re: [Id-event] RFC 9493 on Subject Identifiers fo… Yaron Sheffer
- Re: [Id-event] RFC 9493 on Subject Identifiers fo… Atul Tulshibagwale
- Re: [Id-event] RFC 9493 on Subject Identifiers fo… Brian Campbell
- Re: [Id-event] RFC 9493 on Subject Identifiers fo… Yaron Sheffer
- Re: [Id-event] RFC 9493 on Subject Identifiers fo… Atul Tulshibagwale
- Re: [Id-event] RFC 9493 on Subject Identifiers fo… Prachi Jain