%% You should probably cite draft-chen-rats-tee-identification-03 instead of this revision.
@techreport{chen-rats-tee-identification-00,
    number =    {draft-chen-rats-tee-identification-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-chen-rats-tee-identification/00/},
    author =    {Penglin Yang and Meiling Chen and Li Su},
    title =     {{Use TEE Identification in EAP-TLS}},
    pagetotal = 10,
    year =      2021,
    month =     may,
    day =       28,
    abstract =  {In security considerations, identity of a device should be protected and cannot be exposed in public. Based on this purpose, this document specifies the architecture of TEE(Trust Execution Environment) identification based on EAP-TLS. In this architecture, TEE is in charge of protecting the certificate and generating handshake keys which will be used for EAP-TLS authentication. REE(Rich Execution Environment) is in charge of building communication with EAP-TLS Server. A middle layer is introduced to communicate with separate parts of EAP-TLS in TEE and REE to implement its original functionality. This architecture could be used in data link layer and also application layer to implement identity authentication under the protection of TEE and EAP-TLS.},
}