Re: [Teep] New Version Notification for draft-yang-teep-usecase-for-cc-in-network-01.txt

"yangpenglin@chinamobile.com" <yangpenglin@chinamobile.com> Wed, 03 August 2022 03:11 UTC

Return-Path: <yangpenglin@chinamobile.com>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3189DC131956 for <teep@ietfa.amsl.com>; Tue, 2 Aug 2022 20:11:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v8hXmNmpQTi4 for <teep@ietfa.amsl.com>; Tue, 2 Aug 2022 20:11:47 -0700 (PDT)
Received: from cmccmta2.chinamobile.com (cmccmta2.chinamobile.com [221.176.66.80]) by ietfa.amsl.com (Postfix) with ESMTP id 9B321C14F744 for <teep@ietf.org>; Tue, 2 Aug 2022 20:11:46 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.81]) by rmmx-syy-dmz-app05-12005 (RichMail) with SMTP id 2ee562e9e770ad0-f83d6; Wed, 03 Aug 2022 11:11:44 +0800 (CST)
X-RM-TRANSID: 2ee562e9e770ad0-f83d6
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[223.104.40.104]) by rmsmtp-syy-appsvrnew01-12030 (RichMail) with SMTP id 2efe62e9e76d917-2d685; Wed, 03 Aug 2022 11:11:43 +0800 (CST)
X-RM-TRANSID: 2efe62e9e76d917-2d685
Date: Wed, 03 Aug 2022 11:11:45 +0800
From: "yangpenglin@chinamobile.com" <yangpenglin@chinamobile.com>
To: teep <teep@ietf.org>
Cc: Su <suli@chinamobile.com>, chenmeiling <chenmeiling@chinamobile.com>, Pang <pangting@huawei.com>
References: <165949348041.65516.5050903399195805921@ietfa.amsl.com>
X-Priority: 3
X-GUID: 950F65F8-28C5-4067-BB65-69A3FC5A706F
X-Has-Attach: no
X-Mailer: Foxmail 7.2.24.88[en]
Mime-Version: 1.0
Message-ID: <2022080311114426212412@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart453747340035_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/Fgr_XzZAyON6bh_HFIHtvJo81Iw>
Subject: Re: [Teep] New Version Notification for draft-yang-teep-usecase-for-cc-in-network-01.txt
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2022 03:11:52 -0000

Hi all,

Based on the meeting, I changed the draft as the information draft. Thank you for your support and comments. Hope the Chairs could adpot this as a WG draft.
The follwoing link is the source text of this draft in Github (https://github.com/PenglinYang/teep-usecase-for-cc-in-network), right now three issues are opened.
1,cloud scenario should be included
2,security of confidential container should to be clarified
3,specify or refer to secure channel in other document

Thanks for your comments in GitHub or mailing list.

BR.
Penglin


yangpenglin@chinamobile.com
 
From: internet-drafts
Date: 2022-08-03 10:24
To: Li Su; Meiling Chen; Penglin Yang; Ting Pang; chenmeiling
Subject: New Version Notification for draft-yang-teep-usecase-for-cc-in-network-01.txt
 
A new version of I-D, draft-yang-teep-usecase-for-cc-in-network-01.txt
has been successfully submitted by Penglin Yang and posted to the
IETF repository.
 
Name: draft-yang-teep-usecase-for-cc-in-network
Revision: 01
Title: TEEP Usecase for Confidential Computing in Network
Document date: 2022-08-03
Group: Individual Submission
Pages: 12
URL:            https://www.ietf.org/archive/id/draft-yang-teep-usecase-for-cc-in-network-01.txt
Status:         https://datatracker.ietf.org/doc/draft-yang-teep-usecase-for-cc-in-network/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-yang-teep-usecase-for-cc-in-network
Diff:           https://www.ietf.org/rfcdiff?url2=draft-yang-teep-usecase-for-cc-in-network-01
 
Abstract:
   Confidential computing is the protection of data in use by performing
   computation in a hardware-based Trusted Execution Environment.
   Confidential computing could provide integrity and confidentiality
   for users who want to run application and process data in that
   environment.  When confidential computing is used in network like MEC
   and CAN which provide computing resource to network users, TEEP
   protocol could be used to provision network user's data and
   application in TEE environment in confidential computing resource.
   This document focuses on using TEEP to provision network user's data
   and application in confidential computing in such network.  This
   document is a use case and extension of TEEP and could provide
   guidance for MEC, CAN and other scenarios to use confidential
   computing.
 
                                                                                  
 
 
The IETF Secretariat