This PR addresses #47 and #55 by explicitly stating a common aspect of all entities (in the scope of this document): They play a role related to path-aware networking for a particular path and flow.
It then illustrates these roles based on the clarified "data plane" and "control plane".
Not sure if "what may be called [data|control] plane" is the right phrasing yet, but I didn't want to imply that one has to use these terms, or that the entity's role always has to align with any possible definition of these terms.
I like the changes and I think its good to keep it as general as possible.
I changed a few things:
Change "control aspects" -> "influence aspects" since the actual path control may be done by the endpoint not the control plane (although the name control plane seems to imply control so we can also keep "control aspects" ;D )
Change node definition to be an on-path entity because we want to actually use the abstract entity definitions (#47).
Also, I changed some occurrences of node to entity in the security considerations since it seems to be more general.
This PR addresses #47 and #55 by explicitly stating a common aspect of all entities (in the scope of this document): They play a role related to path-aware networking for a particular path and flow. It then illustrates these roles based on the clarified "data plane" and "control plane".
Not sure if "what may be called [data|control] plane" is the right phrasing yet, but I didn't want to imply that one has to use these terms, or that the entity's role always has to align with any possible definition of these terms.
Please let me know what you think.