IETF Logo Mail Archive

[Acme] 回复: Re: Call for adoption: draft-liu-acme-rats-02 (Ends 2025-12-10)

"Xialiang(Frank, IP Security Standard)" <frank.xialiang@huawei.com> Mon, 08 December 2025 05:46 UTC

Return-Path: <frank.xialiang@huawei.com>
X-Original-To: acme@mail2.ietf.org
Delivered-To: acme@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B3D609736F9C; Sun, 7 Dec 2025 21:46:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.935
X-Spam-Level:
X-Spam-Status: No, score=-3.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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 2GbaM_qXUV-6; Sun, 7 Dec 2025 21:46:29 -0800 (PST)
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 579879736F95; Sun, 7 Dec 2025 21:46:29 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.224.150]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4dPrZM2D88zHnH7N; Mon, 8 Dec 2025 13:46:19 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id 0EF164048B; Mon, 8 Dec 2025 13:46:26 +0800 (CST)
Received: from kwepemf500016.china.huawei.com (7.202.181.3) 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; Mon, 8 Dec 2025 13:46:24 +0800
Received: from kwepemf100017.china.huawei.com (7.202.181.16) by kwepemf500016.china.huawei.com (7.202.181.3) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Mon, 8 Dec 2025 13:46:24 +0800
Received: from kwepemf100017.china.huawei.com ([7.202.181.16]) by kwepemf100017.china.huawei.com ([7.202.181.16]) with mapi id 15.02.1544.036; Mon, 8 Dec 2025 13:46:24 +0800
From: "Xialiang(Frank, IP Security Standard)" <frank.xialiang@huawei.com>
To: Mike Ounsworth <mike@ounsworth.ca>
Thread-Topic: [Acme] Re: Call for adoption: draft-liu-acme-rats-02 (Ends 2025-12-10)
Thread-Index: AQHcaAJIQs3wWBFH/UyEGRltxwKZsbUXO9lw
Date: Mon, 08 Dec 2025 05:46:24 +0000
Message-ID: <8dc8fe7d29f74d88b3e1d7bf8c13939e@huawei.com>
References: <176420392326.2804200.15166188813286514520@dt-datatracker-5bd94c585b-wk4l4> <CAB=Y13fHDx-z2guN_++4iMw0nij8PgAinDxTa2e4xXa8ApTN9A@mail.gmail.com>
In-Reply-To: <CAB=Y13fHDx-z2guN_++4iMw0nij8PgAinDxTa2e4xXa8ApTN9A@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.164.29.104]
Content-Type: multipart/alternative; boundary="_000_8dc8fe7d29f74d88b3e1d7bf8c13939ehuaweicom_"
MIME-Version: 1.0
Message-ID-Hash: YRMY247PJJDYHWONG6464UGRSEVPXWVW
X-Message-ID-Hash: YRMY247PJJDYHWONG6464UGRSEVPXWVW
X-MailFrom: frank.xialiang@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-acme.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "acme-chairs@ietf.org" <acme-chairs@ietf.org>, IETF ACME <acme@ietf.org>, "draft-liu-acme-rats@ietf.org" <draft-liu-acme-rats@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Acme] 回复: Re: Call for adoption: draft-liu-acme-rats-02 (Ends 2025-12-10)
List-Id: Automated Certificate Management Environment <acme.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/BGKoa1aDReFaa8GV7bL7BezK7cY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Owner: <mailto:acme-owner@ietf.org>
List-Post: <mailto:acme@ietf.org>
List-Subscribe: <mailto:acme-join@ietf.org>
List-Unsubscribe: <mailto:acme-leave@ietf.org>

+1

发件人: 吴攀雨 <wupanyuuu@gmail.com>
发送时间: 2025年12月8日 13:19
收件人: Mike Ounsworth <mike@ounsworth.ca>
抄送: acme-chairs@ietf.org; IETF ACME <acme@ietf.org>; draft-liu-acme-rats@ietf.org
主题: [Acme] Re: Call for adoption: draft-liu-acme-rats-02 (Ends 2025-12-10)

Hi,
I support adoption.
Introducing Remote Attestation into the ACME process enables certificate issuance to not only “prove you control the domain/hostname” but also “verify that the device you're using is itself trustworthy/secure.” This capability is crucial for enterprise security, Zero-Trust architectures, and device management scenarios such as BYOD and IoT.

Best regards.
Grace

Mike Ounsworth via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>> 于2025年11月27日周四 08:39写道：

Subject: Call for adoption: draft-liu-acme-rats-02  (Ends 2025-12-10)

This message starts a 2-week Call for Adoption for this document.

Abstract:
   This document describes an approach where an ACME Server can
   challenge an ACME Client to provide a Remote Attestation Evidence or
   Remote Attestation Result in any format supported by the Conceptual
   Message Wrapper.

   The ACME Server can optionally challenge the Client for specific
   claims that it wishes attestation for.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-liu-acme-rats/

Please reply to this message keeping acme@ietf.org<mailto:acme@ietf.org> in copy by indicating
whether you support or not the adoption of this draft as a WG document.
Comments to motivate your preference are highly appreciated.

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/



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

v2.46.0 | Report a Bug | By Email | System Status