Skip to content
New issue

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

Flags draft - Loopback mode issues #138

Open
barakgafni opened this issue Nov 4, 2019 · 0 comments
Open

Flags draft - Loopback mode issues #138

barakgafni opened this issue Nov 4, 2019 · 0 comments

Comments

@barakgafni
Copy link
Collaborator

barakgafni commented Nov 4, 2019

Hi,
I would like to discuss more on the behavior of the loopback mode:
I think that there is no real need to collect data on the way back from the duplication node to the source. This can simplify and increase performance of the network as well as the duplicator and the source node. The above includes solving a question: what is being done on the edge of the IOAM, and beyond the edge, assume the source is out of this network.
In addition, there is a question regarding the relation between source and encapsulator, and whether source might be the only one allowed to encapsulate with loopback. One option to protect the source is to force decapsulators to prevent loopback packets from going out of the IOAM domain. This may simplify the the majority of the attack vectors on the source by potential malicious encapsulators.

If agreed, let's fix this draft.

Thanks,
Barak

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant