doc/roadmap: Make working 6LBR a goal #20351
Merged
Conversation
This file contains 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
chrysn
added
the
CI: ready for build
miri64
reviewed
Feb 7, 2024
|
A note on Proxy ND: There is another 6LBR implementation that does it. |
maribu
approved these changes
Feb 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Contribution description
This describes goals of the border router example, and lists candidate technologies for achieving them.
ND Proxy is there explicitly because NAT66 was also discussed, which I dislike a lot because it pulls in all the old IPv4 NAT problems all over again. (Plus ND proxying might be doable with O(1) state if the 6LBR distributes 16bit addresses).
Issues/PRs references
Coming out of a discussion on matrix with @benpicco and @miri64.