RFC 9334 on Remote ATtestation procedureS (RATS) Architecture
rfc-editor@rfc-editor.org Sat, 14 January 2023 00:23 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC1FC15C522; Fri, 13 Jan 2023 16:23:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 8r1unTECEOVt; Fri, 13 Jan 2023 16:22:56 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [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 3B213C1527BC; Fri, 13 Jan 2023 16:22:56 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 0A1F04C292; Fri, 13 Jan 2023 16:22:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9334 on Remote ATtestation procedureS (RATS) Architecture
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rats@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230114002256.0A1F04C292@rfcpa.amsl.com>
Date: Fri, 13 Jan 2023 16:22:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/VYoGNOfro0qcdwC8MAWrvxxRVwg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jan 2023 00:23:00 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9334
Title: Remote ATtestation procedureS (RATS) Architecture
Author: H. Birkholz,
D. Thaler,
M. Richardson,
N. Smith,
W. Pan
Status: Informational
Stream: IETF
Date: January 2023
Mailbox: henk.birkholz@sit.fraunhofer.de,
dthaler@microsoft.com,
mcr+ietf@sandelman.ca,
ned.smith@intel.com,
william.panwei@huawei.com
Pages: 46
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rats-architecture-22.txt
URL: https://www.rfc-editor.org/info/rfc9334
DOI: 10.17487/RFC9334
In network protocol exchanges, it is often useful for one end of a
communication to know whether the other end is in an intended
operating state. This document provides an architectural overview of
the entities involved that make such tests possible through the
process of generating, conveying, and evaluating evidentiary Claims.
It provides a model that is neutral toward processor architectures,
the content of Claims, and protocols.
This document is a product of the Remote ATtestation ProcedureS Working Group 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
Association Management Solutions, LLC