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

NSE Composition: Translation client for the passthrough NSE #879

Closed
Bolodya1997 opened this issue Apr 27, 2021 · 2 comments
Closed

NSE Composition: Translation client for the passthrough NSE #879

Bolodya1997 opened this issue Apr 27, 2021 · 2 comments
Assignees
Labels
blocked Something is blocking this

Comments

@Bolodya1997
Copy link

Overview

Translation client for the passthrough NSE should set new ConnectionContext as it is done for { Mechanism, MechanismPreferences } in mechanismtranslation.

References

Tests

  1. Unit tests for the new client.
  2. (?) Sandbox tests.
@edwarnicke
Copy link
Member

I'm a little confused here... why is this needed? Current behavior simply passes through the ConnectionContext, which is the correct behavior for NSMgr, Forwarder, and PassThrough NSEs...

@Bolodya1997
Copy link
Author

@edwarnicke
I suppose that for the simple IP forwarder passthrough NSE we will have one of these schemes:
image
image
Where yellow highlight means IP context specific for NSC -> NSE-1 IP connection and green highlight means IP context specific for NSE-1 -> NSE-2 IP connection.
So we have different src/dst IP, different src/dst Routes for these connections and it probably should mean that we want to switch ConnectionContext when we are switching the connection on NSE-1.

@denis-tingaikin denis-tingaikin added the blocked Something is blocking this label May 6, 2021
@denis-tingaikin denis-tingaikin moved this from In progress to Open questions in Issue/PR tracking May 6, 2021
Issue/PR tracking automation moved this from Open questions to Done May 11, 2021
@denis-tingaikin denis-tingaikin removed this from Done in Issue/PR tracking May 31, 2021
@denis-tingaikin denis-tingaikin removed the Planning The issue that related to current SOW label May 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Something is blocking this
Projects
None yet
Development

No branches or pull requests

4 participants