%% You should probably cite draft-tschofenig-rats-psa-token-22 instead of this revision.
@techreport{tschofenig-rats-psa-token-06,
    number =    {draft-tschofenig-rats-psa-token-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-tschofenig-rats-psa-token/06/},
    author =    {Hannes Tschofenig and Simon Frost and Mathias Brossard and Adrian L. Shaw and Thomas Fossati},
    title =     {{Arm's Platform Security Architecture (PSA) Attestation Token}},
    pagetotal = 25,
    year =      2020,
    month =     dec,
    day =       1,
    abstract =  {The Platform Security Architecture (PSA) is a family of hardware and firmware security specifications, as well as open-source reference implementations, to help device makers and chip manufacturers build best-practice security into products. Devices that are PSA compliant are able to produce attestation tokens as described in this memo, which are the basis for a number of different protocols, including secure provisioning and network access control. This document specifies the PSA attestation token structure and semantics. At its core, the CWT (COSE Web Token) format is used and populated with a set of claims in a way similar to EAT (Entity Attestation Token). This specification describes what claims are used by PSA compliant systems.},
}