<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" docName="draft-labiod-rats-attester-groups-00" category="info" ipr="trust200902" obsoletes="" updates="" xml:lang="en" symRefs="true" sortRefs="true" tocInclude="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.21.0 -->
  <!-- Generated by id2xml 1.5.2 on 2024-07-03T03:16:16Z -->
	<front>
    <title>Attester Groups for Remote Attestation</title>
    <seriesInfo name="Internet-Draft" value="draft-labiod-rats-attester-groups-00"/>
    <author initials="H." surname="Labiod" fullname="Houda Labiod">
      <organization abbrev="Huawei Technologies">Huawei Technologies France, France</organization>
      <address/>
    </author>
    <author initials="A." surname="Lamouchi" fullname="Amine Lamouchi">
      <organization abbrev="Huawei Technologies">Huawei Technologies France, France</organization>
      <address/>
    </author>
    <author initials="J." surname="Zhang" fullname="Jun Zhang">
      <organization abbrev="Huawei Technologies">Huawei Technologies France, France</organization>
      <address/>
    </author>
    <author initials="A." surname="Duda" fullname="Andrzej Duda">
      <organization abbrev="Grenoble INP">Grenoble INP - Ensimag, LIG Lab, France</organization>
      <address/>
    </author>
    <author initials="H." surname="Birkholz" fullname="Henk Birkholz">
      <organization>Fraunhofer SIT</organization>
      <address/>
    </author>
    <date year="2024" month="July" day="3"/>
    <workgroup>RATS Working Group</workgroup>
    <abstract>
      <t>
   This document proposes an extension to the Remote Attestation
   Procedures architecture as defined in <xref target="RFC9334" format="default"/> by introducing
   the concept of Attester Groups. This extension aims to reduce
   computational and communication overhead by enabling collective
   attestation of devices with similar characteristics,
   thereby improving the scalability of attestation processes.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="sect-1" numbered="true" toc="default">
      <name>Introduction</name>
      <t>
   <xref target="RFC9334" format="default"/> defines Attesters as entities comprising at least one
   Attesting Environment and one Target Environment. It also introduces
   configurations, such as Composite Devices and Layered Attesters.
   However, mechanisms for efficiently managing multiple, independent
   Attesters are missing. Assessing the trustworthiness of large numbers
   of independent devices individually can result in high conveyance and
   processing overhead. This comes into effect particularly when these
   devices share identical hardware or firmware components, which can
   lead to redundancy between all individual remote attestation
   procedures. One example would be a smart factory scenario where
   numerous sensors of the same model monitor different parts of the
   manufacturing process. These sensors share identical hardware and
   firmware configurations. This document proposes a model by which
   these separate sensors devices can be grouped into a single Attester
   Group and a shared remote attestation procedure can appraise their
   authenticity collectively rather than individually. Direct Anonymous
   Attestation (DAA) <xref target="I-D.ietf-rats-daa" format="default"/> has a similar concept of using one
   unique ID for one group of attesters, but its goal is to mitigate
   the issue of uniquely (re-)identifiable Attesting Environments,
   while the scalability is the major concern in this document.</t>
    </section>
    <section anchor="sect-2" numbered="true" toc="default">
      <name>Terminology</name>
      <t>
   The following terms are imported from <xref target="RFC9334" format="default"/>: Attester, Composite
   Device, Evidence, Layered Attester, Verifier. Newly defined terms for
   this document: Attester Group: A role performed by a group of
   Attesters whose Evidence must be appraised in order to infer the
   extent to which the individual Attesters comprising the group are
   considered trustworthy.</t>
      <t>
   group-id: A new Attester Identity type (see <xref target="I-D.ietf-rats-ar4si" format="default"/>
   section 2.2.1.). It is a unique identifier assigned to each Attester
   Group, allowing the group to dynamically adjust its membership
   without redefining its fundamental identity.</t>
    </section>
    <section anchor="sect-3" numbered="true" toc="default">
      <name>Attester Group and Comparison to Composite Devices</name>
      <t>
   An Attester Group is inherently a dynamic entity. Attesters can join
   or leave the group, in contrast to Composite Devices that have a
   static composition with a pre-defined set of Attesting Environments
   and fixed parameters. The dynamic nature of an Attester Group allows
   for the flexibility to tailor group parameters, such as the number
   of Lead Attesters in the group (if any), the range of devices
   included in the group, and which or how much Evidence is expected to
   be produced by each groups. This kind of flexibility facilitates the
   implementation of various group aggregation schemes that can optimize
   the resources required to conduct remote attestation procedures for
   large device groups. The table below summarizes the key differences
   between the Group Attester concept and the Composite Device concept.</t>
      <artwork name="" type="" align="left" alt=""><![CDATA[
| Feature      | Composite Device | Attester Group          |
|--------------|------------------|-------------------------|
| Evidence     | One evidence     | More granular, e.g.,    |
| Submission   |per composite     | one evidence            |
|              |device            | per two members         |
|-----------------------------------------------------------|
| Lead Attester| One lead attester|Multiple or no           |
|              | communicates     |lead attesters (i.e.     |
|              | with Verifier    |distributed collection)  |
|-----------------------------------------------------------|
| Identity     | Identifiable by  | Identified by unique    |
|              |its lead attester | group-id, independent   |
|              |                  | of lead attester        |
|-----------------------------------------------------------|
| Flexibility  | Static, with     | Dynamic, members can    |
| & Dynamics   | predefined       | join or leave           |
|              | members and roles|                         |
]]></artwork>
    </section>
    <section anchor="sect-4" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>
   This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <reference anchor="RFC9334" target="https://www.rfc-editor.org/info/rfc9334" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9334.xml">
        <front>
          <title>Remote ATtestation procedureS (RATS) Architecture</title>
          <author fullname="H. Birkholz" initials="H." surname="Birkholz"/>
          <author fullname="D. Thaler" initials="D." surname="Thaler"/>
          <author fullname="M. Richardson" initials="M." surname="Richardson"/>
          <author fullname="N. Smith" initials="N." surname="Smith"/>
          <author fullname="W. Pan" initials="W." surname="Pan"/>
          <date month="January" year="2023"/>
          <abstract>
            <t>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.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9334"/>
        <seriesInfo name="DOI" value="10.17487/RFC9334"/>
      </reference>
      <reference anchor="I-D.ietf-rats-ar4si" target="https://datatracker.ietf.org/doc/html/draft-ietf-rats-ar4si-06" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-rats-ar4si.xml">
        <front>
          <title>Attestation Results for Secure Interactions</title>
          <author fullname="Eric Voit" initials="E." surname="Voit">
            <organization>Cisco Systems</organization>
          </author>
          <author fullname="Henk Birkholz" initials="H." surname="Birkholz">
            <organization>Fraunhofer SIT</organization>
          </author>
          <author fullname="Thomas Hardjono" initials="T." surname="Hardjono">
            <organization>MIT</organization>
          </author>
          <author fullname="Thomas Fossati" initials="T." surname="Fossati">
            <organization>Linaro</organization>
          </author>
          <author fullname="Vincent Scarlata" initials="V." surname="Scarlata">
            <organization>Intel</organization>
          </author>
          <date day="4" month="March" year="2024"/>
          <abstract>
            <t>This document defines reusable Attestation Result information elements. When these elements are offered to Relying Parties as Evidence, different aspects of Attester trustworthiness can be evaluated. Additionally, where the Relying Party is interfacing with a heterogeneous mix of Attesting Environment and Verifier types, consistent policies can be applied to subsequent information exchange between each Attester and the Relying Party.</t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-ietf-rats-ar4si-06"/>
      </reference>
      <reference anchor="I-D.ietf-rats-daa" target="https://datatracker.ietf.org/doc/html/draft-ietf-rats-daa-05" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-rats-daa.xml">
        <front>
          <title>Direct Anonymous Attestation for the Remote Attestation Procedures Architecture</title>
          <author fullname="Henk Birkholz" initials="H." surname="Birkholz">
            <organization>Fraunhofer SIT</organization>
          </author>
          <author fullname="Christopher Newton" initials="C." surname="Newton">
            <organization>University of Surrey</organization>
          </author>
          <author fullname="Liqun Chen" initials="L." surname="Chen">
            <organization>University of Surrey</organization>
          </author>
          <author fullname="Dave Thaler" initials="D." surname="Thaler">
            <organization>Microsoft</organization>
          </author>
          <date day="4" month="March" year="2024"/>
          <abstract>
            <t>This document maps the concept of Direct Anonymous Attestation (DAA) to the Remote Attestation Procedures (RATS) Architecture. The protocol entity DAA Issuer is introduced and its mapping with existing RATS roles in DAA protocol steps is specified.</t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-ietf-rats-daa-05"/>
      </reference>
    </references>
    <section anchor="sect-appendix" numbered="true" toc="default">
      <name>Implementation Considerations</name>
      <t>
   Details on creating and maintaining Attester Groups, choosing the
   number of Lead Attesters, and methods for evidence collection and
   signing are left to the implementer's discretion, allowing for
   tailored security measures.</t>
    </section>
  </back>
</rfc>
