[NOT TO BE MERGED] Check SVC resolution only happens with one-hop path #4790
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR adds a beacon extension to include control and discovery service addresses along with beacons. This will help to reduce the number of SVC resolution requests we need. With this information we can simply use the provided addresses instead of doing SVC resolution when communicating upstream. Contributes scionproto#4388
jiceathome
reviewed
Jun 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR intention is to check that only one-hop path traffic is using the SVC resolution mechanism, which includes two additional round trips. In fact this reduces the traffic to beaconing.
#4789 contains the actual contribution.
This PR will be closed without merging after passing all the integration test and merging #4789