%% You should probably cite draft-ietf-rats-architecture instead of this I-D.
@techreport{birkholz-rats-architecture-00,
    number =    {draft-birkholz-rats-architecture-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-birkholz-rats-architecture/00/},
    author =    {Henk Birkholz and Monty Wiseman and Hannes Tschofenig and Ned Smith},
    title =     {{Architecture and Reference Terminology for Remote Attestation Procedures}},
    pagetotal = 25,
    year =      2018,
    month =     oct,
    day =       23,
    abstract =  {Remote ATtestation ProcedureS (RATS), such as Remote Integrity VERification (RIVER), the creation of Entity Attestation Tokens (EAT), software integrity Measurement And ATtestation (MAAT), or the attestation of device characteristics, in general, are based on specific operations and qualities provided by hardware and software. The RATS architecture maps corresponding functions and operation capabilities to specific RATS roles. The goal is to enable an appropriate conveyance of believable evidence about device health or trusted claims about device capabilities via network protocols. The flows of data between these roles depend on the composition of RATS roles and their location with respect to devices or services. The RATS architecture provides these roles as building blocks to enable suitable composition, while remaining hardware-agnostic. This flexibility is intended to address a significant majority of use cases or usage scenarios in the domain of RATS. Examples include, but are not limited to: financial transactions, voting machines, critical safety systems, network equipment health, or trustworthy end-user device management.},
}