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

pm: subflow: specify the destination IP #51

Merged
merged 2 commits into from
Mar 27, 2025
Merged

Conversation

matttbe
Copy link
Member

@matttbe matttbe commented Mar 18, 2025

The 'subflow' endpoint description might be confusing: is it needed to be specified to create subflows to additional IP announced by the other peer. Mentioning that it is only to create subflows to the other peer's IP address should help clarifying this.

Link: multipath-tcp/mptcp_net-next#554

The 'subflow' endpoint description might be confusing: is it needed to
be specified to create subflows to additional IP announced by the other
peer. Mentioning that it is only to create subflows to the other peer's
IP address should help clarifying this.

Link: multipath-tcp/mptcp_net-next#554
Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
@matttbe matttbe requested a review from mjmartineau March 18, 2025 16:34
It might not be clear what a "subflow" is.

Mentioning that it is another word for 'path' might help.

Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
@matttbe matttbe merged commit 1ed621c into main Mar 27, 2025
@matttbe matttbe deleted the pm-sf-init-dest-addr branch March 27, 2025 10:17
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

Successfully merging this pull request may close these issues.

2 participants