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

Remove obsolete limit on path segments in SegReply #3765

Merged
merged 1 commit into from
May 14, 2020

Conversation

matzf
Copy link
Contributor

@matzf matzf commented May 13, 2020

An arbitrary limit to 9 path segments in a SegReply was implemented some time ago as a hack to avoid exceeding MTU. This is no longer necessary as QUIC is now used as transport for these path segment requests.


This change is Reviewable

An arbitrary limit to 9 path segments in a SegReply was implemented some
time ago as a hack to avoid exceeding MTU. This is no longer necessary
as QUIC is now used as transport for these path segment requests.
@matzf
Copy link
Contributor Author

matzf commented May 13, 2020

Note: I noticed this while working on the implementation of #3731; in this context, the code modified here will be removed anyway, but it seemed to make sense to clean this up independently.

Copy link
Collaborator

@lukedirtwalker lukedirtwalker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 1 of 1 files at r1.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved

@lukedirtwalker lukedirtwalker merged commit 541d444 into scionproto:master May 14, 2020
@matzf matzf deleted the segreq-nolimit branch May 14, 2020 10:27
matzf added a commit to matzf/scion that referenced this pull request May 25, 2020
An arbitrary limit to 9 path segments in a SegReply was implemented some
time ago as a hack to avoid exceeding MTU. This is no longer necessary
as QUIC is now used as transport for these path segment requests.
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