Re: [Teep] Review of draft-ietf-teep-usecase-for-cc-in-network-00

[[e-mail]]

Hi Hannes

Yes, that's what I mean. If you are using a command line to configure CC 
environment manually, you don't have to use TEEP protocol. Instead, you 
need some commands provided by the CC environment. Like in occlum 
https://occlum.io/, you could use occlum new/build/run to create a CC 
environment.

BR
Penglin


On 9/21/2022 3:14 PM, Hannes Tschofenig wrote:
>
> Hi Penglin,
>
> I think there is a need to explain in the document what “network 
> protocol usecase of TEEP” means.
>
> My understanding, from your text below, is that this means that there 
> is a protocol used to provision the confidential computing device, 
> such as the TEEP protocol, rather than having a human configure the 
> device via the command line.
>
> Ciao
> Hannes
>
> *From:* [e-mail] <[e-mail]>
> *Sent:* Wednesday, September 21, 2022 3:51 AM
> *To:* Hannes Tschofenig <[e-mail]>; [e-mail]
> *Subject:* Re: [Teep] Review of 
> draft-ietf-teep-usecase-for-cc-in-network-00
>
> Hi Hannes,
>
> About the title of this document, I used to think different options 
> such as "in remote", "in cloud " or "in network". But in the end I 
> think "in network" is a better or precise term. The reason is as follow:
>
> 1，This document is about the network protocol usecase of TEEP, no 
> matter where the confidential computing device is, we should use this 
> network protocol usecase to provision the CC environment. For example, 
> the CC device could be in a public cloud where you want to rent for 
> your personal computing, or in a local area where you could provision 
> by LAN.
>
> 2，There are other methods like provision the CC environment by shell 
> or by system administrator directly. I think there scenarios are not 
> in this document's scope. So I prefer to keep "in network" in this 
> document.
>
> Sure, the github link is here https://github.com/ietf-teep/teep-in-cc, 
> you could make comments and create PRs.
>
> Thanks for the very detailed PDF, I think there is no major questions 
> about the comments, I will update the document before 115 meeting.
>
> BR
> Penglin
>
> On 9/20/2022 6:17 PM, Hannes Tschofenig wrote:
>
>     Hi Penglin,
>
>     Thanks for the quick response. Good to hear that you had a broad
>     scope in mind.
>
>     In this case I would suggest to remove the “in network” phrase to
>     avoid confusion. In fact, “in network” isn’t mentioned too often
>     in the text of the draft anyway.
>
>     Let me know if you have any questions about my handwritten
>     comments in the PDF.
>
>     If the document gets added to the working group Github repo, I can
>     also create PRs.
>
>     Ciao
>
>     Hannes
>
>     *From:* [e-mail] <[e-mail]>
>     <mailto:[e-mail]>
>     *Sent:* Tuesday, September 20, 2022 3:51 AM
>     *To:* Hannes Tschofenig <[e-mail]>
>     <mailto:[e-mail]>; [e-mail]
>     *Subject:* Re: [Teep] Review of
>     draft-ietf-teep-usecase-for-cc-in-network-00
>
>     Hi Hannes,
>
>     Thanks for your review. The scope of this document is not only for
>     edge computing like you mentioned in the pdf. In fact, the scope
>     is for any confidential computing environment which need to be
>     configured by network, like cloud computing, private preserve
>     computing, MEC, etc.
>
>     BR
>     Penglin
>
>     On 9/19/2022 7:26 PM, Hannes Tschofenig wrote:
>
>         Hi all,
>
>         I have reviewed the confidential computing use case document.
>         In the attached PDF there are a few comments.
>
>         The document describes a use case of confidential computing
>         for edge devices (although it calls it differently).
>
>         That’s indeed one of the confidential computing use cases.
>
>         I wonder whether the scope should be extended or is there a
>         specific reason to focus on this use case?
>
>         Ciao
>
>         Hannes
>
>         IMPORTANT NOTICE: The contents of this email and any
>         attachments are confidential and may also be privileged. If
>         you are not the intended recipient, please notify the sender
>         immediately and do not disclose the contents to any other
>         person, use it for any purpose, or store or copy the
>         information in any medium. Thank you.
>
>     IMPORTANT NOTICE: The contents of this email and any attachments
>     are confidential and may also be privileged. If you are not the
>     intended recipient, please notify the sender immediately and do
>     not disclose the contents to any other person, use it for any
>     purpose, or store or copy the information in any medium. Thank you.
>
> IMPORTANT NOTICE: The contents of this email and any attachments are 
> confidential and may also be privileged. If you are not the intended 
> recipient, please notify the sender immediately and do not disclose 
> the contents to any other person, use it for any purpose, or store or 
> copy the information in any medium. Thank you.