We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.2. TEEP Broker Implementation Consideration
[...]
Model: A B C ... TEE TEE TEE +----------------+ | | | | TEEP | Agent | | | Agent | implementation | | | | +----------------+ v | | | | | +----------------+ ^ | | | TEEP/HTTP | Broker | | | | implementation | | | | +----------------+ | v | | | | +----------------+ | ^ | | HTTP | | | | | implementation | | | | +----------------+ | | v | | | +----------------+ | | ^ | TCP or QUIC | | | | Broker | implementation | | | | +----------------+ | | | REE REE REE Figure 5: TEEP Broker Models
I am wondering if TLS could be included into the TEE. It is correct that I do not envision TCP being in the TEE.
[Hannes] This can be done and is done regularly. I think we should update the figure to include this option since it is very common.
The text was updated successfully, but these errors were encountered:
It's model C. Simplest change would be to change "HTTP" to "HTTP(S)". Also keep in mind that these are just examples.
Sorry, something went wrong.
Fixed in draft -15
tireddy2
No branches or pull requests
6.2. TEEP Broker Implementation Consideration
[...]
I am wondering if TLS could be included
into the TEE. It is correct that I do
not envision TCP being in the TEE.
[Hannes] This can be done and is done regularly. I think we should update the figure to include this option since it is very common.
The text was updated successfully, but these errors were encountered: