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

rfc-editor@rfc-editor.org Thu, 07 December 2023 01:06 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 4BB30C09C23E; Wed, 6 Dec 2023 17:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
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 aB0TmWxPSZqV; Wed, 6 Dec 2023 17:06:18 -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 A1250C18FCC7; Wed, 6 Dec 2023 17:06:18 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7B21719073C5; Wed, 6 Dec 2023 17:06:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, id-event@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231207010618.7B21719073C5@rfcpa.amsl.com>
Date: Wed, 06 Dec 2023 17:06:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/8RaErhFC08bCBenaE7B4BSII4gs>
Subject: [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 01:06:22 -0000

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,
                    marius.scurtescu@coinbase.com,
                    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

        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) 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://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see 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.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC