Intro and high level architecture #3
Conversation
| TODO Introduction | ||
| This document defines authentication and authorization in the context of interaction between two workloads. | ||
| This is the core component of the WIMSE architecture {{?I-D.ietf-wimse-arch}}. | ||
| Assume that Service A needs to call Service B. For simplicity, this document focuses on REST services, |
There was a problem hiding this comment.
I think we should stick to one term - either workload or service. Using these two interchangeably may confuse readers.
There was a problem hiding this comment.
Agreed. Note that this includes the document's title. Sigh.
There was a problem hiding this comment.
On second thoughts, even in the group charter we called it "service to service". I will let others chime in.
There was a problem hiding this comment.
I'm in favor of switching to workload to workload vs service. I feel that the workload term is more generic and its what we are using elsewhere. I believe the way we are using the they are synonymous.
draft-sheffer-wimse-s2s-protocol.md
Outdated
| * The other commonly deployed architecture has a mutual-TLS connection between each pair of services. This setup | ||
| can be addressed by a simpler solution ({{mutual-tls}}). | ||
|
|
||
| It is an explicit goal of this protocol that a service deployment, and in fact a single call chain, |
There was a problem hiding this comment.
| It is an explicit goal of this protocol that a service deployment, and in fact a single call chain, | |
| It is an explicit goal of this protocol that a service deployment can include both architectures across a multi chain call. |
or do you indeed mean mTLS + TLS terminating middlebox? If that's the case I propose to rephrase the example to something like "TLS terminating middlebox + mTLS"
There was a problem hiding this comment.
I meant it exactly like you wrote it: a single multi chain call including both architectures. (Except that maybe the word "architecture" is a bit off here.)
No description provided.