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

[Yuxuan Song <[e-mail]>]

Hi all, 

I support its adoption. I attended the side meeting once and I think the topic fits well and worths to be explored further in RATS WG. 

I am also willing to review the document throughout its development. 

BR, 
Yuxuan. 

> De: "Paul Howard" <[e-mail]>
> À: "Ned Smith" <[e-mail]>, "rats" <[e-mail]>,
> "rats-chairs" <[e-mail]>,
> [e-mail]
> Cc: "nd" <[e-mail]>
> Envoyé: Mercredi 22 Avril 2026 17:30:11
> Objet: [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. [phone]

> arm.com

> On 17/04/2026, 15:32, "Ned Smith via Datatracker" <[e-mail]> 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/ |
> https://datatracker.ietf.org/doc/bcp78/ ]
> [2] [ https://datatracker.ietf.org/doc/bcp79/ |
> https://datatracker.ietf.org/doc/bcp79/ ]
> [3] [ https://datatracker.ietf.org/doc/rfc6701/ |
> 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/ |
> 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 |
> 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
> |
> https://author-tools.ietf.org/iddiff?url2=draft-deshpande-rats-multi-verifier-04
> ]

> _______________________________________________
> RATS mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

> _______________________________________________
> RATS mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]