[Rats] Fw: New Version Notification for draft-chen-rats-tee-identification-00.txt

Meiling Chen <chenmeiling@chinamobile.com> Fri, 28 May 2021 09:15 UTC

Return-Path: <chenmeiling@chinamobile.com>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60AAA3A217E for <rats@ietfa.amsl.com>; Fri, 28 May 2021 02:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level:
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wjH-XZXDeHRY for <rats@ietfa.amsl.com>; Fri, 28 May 2021 02:15:06 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 50CF83A217B for <rats@ietf.org>; Fri, 28 May 2021 02:15:04 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.3]) by rmmx-syy-dmz-app10-12010 (RichMail) with SMTP id 2eea60b0b48b699-28881; Fri, 28 May 2021 17:14:51 +0800 (CST)
X-RM-TRANSID: 2eea60b0b48b699-28881
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[10.2.50.233]) by rmsmtp-syy-appsvr02-12002 (RichMail) with SMTP id 2ee260b0b48aca4-e3c27; Fri, 28 May 2021 17:14:51 +0800 (CST)
X-RM-TRANSID: 2ee260b0b48aca4-e3c27
Date: Fri, 28 May 2021 17:15:23 +0800
From: Meiling Chen <chenmeiling@chinamobile.com>
To: "rats@ietf.org" <rats@ietf.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.9.115[cn]
Mime-Version: 1.0
Message-ID: <202105281715229094864@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart006480272824_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/FtX16GVSMZcJzgkLQeV7W_j5r4g>
Subject: [Rats] Fw: New Version Notification for draft-chen-rats-tee-identification-00.txt
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote ATtestation procedureS <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2021 09:15:10 -0000

Hi all,
A new draft, it  is about how to use trusted identities in interactions.

More disscussion and comments are welcome.
URL: https://www.ietf.org/archive/id/draft-chen-rats-tee-identification-00.txt

Best Regards,
Meiling

From: internet-drafts
Date: 2021-05-28 17:07
To: Li Su; Meiling Chen; Penglin Yang; chenmeiling
Subject: New Version Notification for draft-chen-rats-tee-identification-00.txt
 
A new version of I-D, draft-chen-rats-tee-identification-00.txt
has been successfully submitted by Meiling Chen and posted to the
IETF repository.
 
Name: draft-chen-rats-tee-identification
Revision: 00
Title: Use TEE Identification in EAP-TLS
Document date: 2021-05-28
Group: Individual Submission
Pages: 10
URL:            https://www.ietf.org/archive/id/draft-chen-rats-tee-identification-00.txt
Status:         https://datatracker.ietf.org/doc/draft-chen-rats-tee-identification/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-chen-rats-tee-identification
 
 
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.
 
                                                                                  
 
 
The IETF Secretariat