RFC 9783 on Arm's Platform Security Architecture (PSA) Attestation Token

rfc-editor@rfc-editor.org Fri, 13 June 2025 17:47 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D1EAB34B00D4; Fri, 13 Jun 2025 10:47:10 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id A5729265CF2; Fri, 13 Jun 2025 10:47:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9783 on Arm's Platform Security Architecture (PSA) Attestation Token
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250613174710.A5729265CF2@rfcpa.rfc-editor.org>
Date: Fri, 13 Jun 2025 10:47:10 -0700
Message-ID-Hash: 22JQRYI4ZILUK6ANYOR2XTSE5AB6PHHQ
X-Message-ID-Hash: 22JQRYI4ZILUK6ANYOR2XTSE5AB6PHHQ
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/GJ1V8VgxjUJVpq30EZbUn7t79vk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9783

        Title:      Arm's Platform Security Architecture (PSA) 
                    Attestation Token 
        Author:     H. Tschofenig,
                    S. Frost,
                    M. Brossard,
                    A. Shaw,
                    T. Fossati
        Status:     Informational
        Stream:     Independent
        Date:       June 2025 
        Mailbox:    Hannes.Tschofenig@gmx.net,
                    simon.frost@arm.com,
                    mathias.brossard@arm.com,
                    adrianlshaw@acm.org,
                    thomas.fossati@linaro.org
        Pages:      36
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-tschofenig-rats-psa-token-24.txt

        URL:        https://www.rfc-editor.org/info/rfc9783

        DOI:        10.17487/RFC9783

Arm's Platform Security Architecture (PSA) is a family of hardware
and firmware security specifications, along with open-source
reference implementations, aimed at helping device makers and chip
manufacturers integrate best-practice security into their products.
Devices that comply with PSA can generate attestation tokens as
described in this document, which serve as the foundation for various
protocols, including secure provisioning and network access control.
This document specifies the structure and semantics of the PSA
attestation token.

The PSA attestation token is a profile of the Entity Attestation
Token (EAT). This specification describes the claims used in an
attestation token generated by PSA-compliant systems, how these
claims are serialized for transmission, and how they are
cryptographically protected.

This Informational document is published as an Independent Submission
to improve interoperability with Arm's architecture. It is not a
standard nor a product of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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