Re: [Id-event] RFC 9493 on Subject Identifiers for Security Event Tokens

Yaron Sheffer <yaronf.ietf@gmail.com> Thu, 07 December 2023 11:04 UTC

Return-Path: <yaronf.ietf@gmail.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 58002C14F75F for <id-event@ietfa.amsl.com>; Thu, 7 Dec 2023 03:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.084
X-Spam-Level:
X-Spam-Status: No, score=-1.084 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, 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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 a1YxH321iWkN for <id-event@ietfa.amsl.com>; Thu, 7 Dec 2023 03:04:06 -0800 (PST)
Received: from mail-oo1-xc32.google.com (mail-oo1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (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 BA417C14F5E8 for <id-event@ietf.org>; Thu, 7 Dec 2023 03:04:06 -0800 (PST)
Received: by mail-oo1-xc32.google.com with SMTP id 006d021491bc7-59067ccb090so277083eaf.1 for <id-event@ietf.org>; Thu, 07 Dec 2023 03:04:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701947046; x=1702551846; darn=ietf.org; h=content-transfer-encoding:mime-version:in-reply-to:references :thread-topic:message-id:cc:from:subject:date:user-agent:from:to:cc :subject:date:message-id:reply-to; bh=nYD9wy+YSCkzcWL97y2afw2LaeUt8o27F0vRaUKrHWw=; b=hIkHVNsIKe69LWKtxVCqGJUYbRsLq1YKQtPP7kjIIwUC6hD/37xK2isDBaqyxn3QFZ 1CPRGadjyHBNerVMdkGCXb7yFvXAIEkXlMUiThS++V9NAqbCqlMqRM9IgOkMce8vswjT y+BQm8CrCYFlpy4njazg4FNKXLbEM43I21KZFm5xoL5r5Afp/ECqL2HEfmCRCBXMGyMN 4/wKR4688CMBNKbBxGEbXSUWpw1VXbZ9mnzBh6LCWQ5vP2haxCK7p+KaOLNNSorHNhJ0 afaAGdoYMazmtGUapmvvvZ8sA6ZFVrskcgci3jy2aHIHoOu/bIWMa4niNZ1vYMHStO4e CdSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701947046; x=1702551846; h=content-transfer-encoding:mime-version:in-reply-to:references :thread-topic:message-id:cc:from:subject:date:user-agent :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nYD9wy+YSCkzcWL97y2afw2LaeUt8o27F0vRaUKrHWw=; b=gXLwFfbtoDHP2ZwLr+MF+tk3iLAsNRVoYdprSaa3q14366JU4rD/HdnjM7jXMvINmE cbgOAPJWAj/cm8f+fKS5ngEelifomgxOtULKYirHP3GOooM+cazIXPUUctGmWMrWPd5d HCmBvoxOlXFjGkfqQDvVa11UFK1lOB7BXNn7iVGQBJTdvrhAnyKdhh5FJTrB+HY6piJb DJ/08M8vFryRcmUBDgeHj34hZgq73G+KCjPwhNqtXvDlMgZ+ZQSx9yh2owCC4UMnM+qt ayPnIN1R4zIPdBZButmvUleeBYS9nwSM1QlLs1hiV+QQ2VOLrydf7ds7ZCyCEZ5RtzZX r4jg==
X-Gm-Message-State: AOJu0Yz9MBQ+knxYg09UTt0wFrQ6ofQmAkLBbpKyZms5wLOz4URI7XZo TI9KYn4xG3b20zLWKJoDR+GSupQDYUI=
X-Google-Smtp-Source: AGHT+IHGU0n/3E4pyaJNfChSs44GIgRlQqeb2AY+itg3LSRMpwy2GQEZ6asMg2ZmenjsoJg5FVRl/Q==
X-Received: by 2002:a05:6359:459a:b0:170:7e3f:c25c with SMTP id no26-20020a056359459a00b001707e3fc25cmr621259rwb.61.1701947045598; Thu, 07 Dec 2023 03:04:05 -0800 (PST)
Received: from [192.168.68.101] (IGLD-84-229-146-155.inter.net.il. [84.229.146.155]) by smtp.gmail.com with ESMTPSA id i6-20020ad44ba6000000b0067c4b7ca239sm399597qvw.22.2023.12.07.03.04.04 for <id-event@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Dec 2023 03:04:05 -0800 (PST)
User-Agent: Microsoft-MacOutlook/16.79.23111718
Date: Thu, 07 Dec 2023 13:04:02 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
CC: id-event@ietf.org
Message-ID: <D41A05EF-7402-456B-8190-7C8EA65575A8@gmail.com>
Thread-Topic: [Id-event] RFC 9493 on Subject Identifiers for Security Event Tokens
References: <20231207010618.7B21719073C5@rfcpa.amsl.com>
In-Reply-To: <20231207010618.7B21719073C5@rfcpa.amsl.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/_jtGQCBimm_8YiiC9kObFBHCIlA>
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: Thu, 07 Dec 2023 11:04:11 -0000

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>