[Rats] Re: Call for adoption: draft-deshpande-rats-multi-verifier-04 (Ends 2026-04-24)

"Panwei (William)" <william.panwei@huawei.com> Wed, 22 April 2026 20:51 UTC

Return-Path: <william.panwei@huawei.com>
X-Original-To: rats@mail2.ietf.org
Delivered-To: rats@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 97D42E121568; Wed, 22 Apr 2026 13:51:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776891104; bh=z8uvbZFqktx+u/W/NVMez5tPsWgkGXYu2sQFugZT7Vo=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=Yq83orQDeokWrsie4RpjKpp4CMercX8TBlFXlDeHOgZ5CV+Oi/KU2OcJ1Ha524urq +anYu0wB8koOLCriMlwIVRK1J/Q3CIUfqz/PyRVeEw6mofbSkkAOj5ZcZdukFfzRl8 N5z1UOl1yf9hzACTfJhTOaHcqDKOBOqkt/SGVc14=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.195
X-Spam-Level:
X-Spam-Status: No, score=-4.195 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GU4YCJJ5JuVZ; Wed, 22 Apr 2026 13:51:42 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (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 EB9CFE1213AD; Wed, 22 Apr 2026 13:50:21 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.224.150]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4g1BDY0cGJzHnGcp; Thu, 23 Apr 2026 04:49:49 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id 78D4740570; Thu, 23 Apr 2026 04:50:19 +0800 (CST)
Received: from kwepemh100015.china.huawei.com (7.202.181.101) by kwepemh500011.china.huawei.com (7.202.181.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 23 Apr 2026 04:50:17 +0800
Received: from kwepemh100014.china.huawei.com (7.202.181.99) by kwepemh100015.china.huawei.com (7.202.181.101) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Thu, 23 Apr 2026 04:50:17 +0800
Received: from kwepemh100014.china.huawei.com ([7.202.181.99]) by kwepemh100014.china.huawei.com ([7.202.181.99]) with mapi id 15.02.1544.036; Thu, 23 Apr 2026 04:50:14 +0800
From: "Panwei (William)" <william.panwei@huawei.com>
To: Paul Howard <Paul.Howard@arm.com>, Ned Smith <ned.smith.ietf@outlook.com>, "rats@ietf.org" <rats@ietf.org>, "rats-chairs@ietf.org" <rats-chairs@ietf.org>, "draft-deshpande-rats-multi-verifier@ietf.org" <draft-deshpande-rats-multi-verifier@ietf.org>
Thread-Topic: [Rats] Re: Call for adoption: draft-deshpande-rats-multi-verifier-04 (Ends 2026-04-24)
Thread-Index: AQHc0jsT7WN4RB7EN0SjDPnsjop5MrXrjjrw
Date: Wed, 22 Apr 2026 20:50:14 +0000
Message-ID: <abc5d8a4328c45948c983a5879331e20@huawei.com>
References: <177643631672.70056.16474393035056250188@dt-datatracker-b45949c58-5szpr> <GVXPR08MB78933C5EC68A1D3BA89F761EEA2D2@GVXPR08MB7893.eurprd08.prod.outlook.com>
In-Reply-To: <GVXPR08MB78933C5EC68A1D3BA89F761EEA2D2@GVXPR08MB7893.eurprd08.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.158.53]
Content-Type: multipart/alternative; boundary="_000_abc5d8a4328c45948c983a5879331e20huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: DWNG2VWU6QB56CCIO6MG2EODFDGODK2N
X-Message-ID-Hash: DWNG2VWU6QB56CCIO6MG2EODFDGODK2N
X-MailFrom: william.panwei@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rats.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: nd <nd@arm.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Rats] Re: Call for adoption: draft-deshpande-rats-multi-verifier-04 (Ends 2026-04-24)
List-Id: Remote ATtestation procedureS <rats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/-XYpk_PdID3mnBao-BT5V5OZHlM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Owner: <mailto:rats-owner@ietf.org>
List-Post: <mailto:rats@ietf.org>
List-Subscribe: <mailto:rats-join@ietf.org>
List-Unsubscribe: <mailto:rats-leave@ietf.org>

+1 to Paul’s opinions. I also support the adoption.

Regards & Thanks!
Wei PAN (潘伟)

From: Paul Howard <Paul.Howard@arm.com>
Sent: Wednesday, April 22, 2026 11:30 AM
To: Ned Smith <ned.smith.ietf@outlook.com>; rats@ietf.org; rats-chairs@ietf.org; draft-deshpande-rats-multi-verifier@ietf.org
Cc: nd <nd@arm.com>
Subject: [Rats] Re: Call for adoption: draft-deshpande-rats-multi-verifier-04 (Ends 2026-04-24)

Hi, RATS chairs/all,

I have read this draft and I support adoption. I think it’s healthy to be open-minded about different verifier topologies, and to bring the expertise of this WG to bear on reasoning about how they might be deployed. An adopted draft feels like a good vehicle for doing that.

Cheers,
P.

Paul Howard
Senior Principal Software Architect | Arm
………………………………………………………………..
m. +44 (0)7595 334971<tel:+447595334971>
arm.com

On 17/04/2026, 15:32, "Ned Smith via Datatracker" <noreply@ietf.org<mailto:noreply@ietf.org>> wrote:

This message starts a rats WG Call for Adoption of:
draft-deshpande-rats-multi-verifier-04

This Working Group Call for Adoption ends on 2026-04-24

Abstract:
   IETF RATS Architecture, defines the key role of a Verifier.  In a
   complex system, this role needs to be performed by multiple Verfiers
   coordinating together to assess the full trustworthiness of an
   Attester.  This document focuses on various topological patterns for
   a multiple Verifier system.  It only covers the architectural aspects
   introduced by the Multi Verifier concept, which is neutral with
   regard to specific wire formats, encoding, transport mechanisms, or
   processing details.

Please reply to this message and indicate whether or not you support adoption
of this Internet-Draft by the rats WG. Comments to explain your preference
are greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-deshpande-rats-multi-verifier/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-deshpande-rats-multi-verifier-04.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-deshpande-rats-multi-verifier-04

_______________________________________________
RATS mailing list -- rats@ietf.org<mailto:rats@ietf.org>
To unsubscribe send an email to rats-leave@ietf.org<mailto:rats-leave@ietf.org>