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

Treat IPv6 Routing Header separately and incorporate diff Routing Types #88

Open
zeeshanlakhani opened this issue Apr 21, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@zeeshanlakhani
Copy link
Member

zeeshanlakhani commented Apr 21, 2020

Background

Currently, we treat the Segment Routing Header (SRH) as the only type of routing header that's possible, with its suggested routing type of 4, as per the spec. However, looking at the RFC for the IPv6 Routing Header, it's possible for more type-specific data and different routing types to exist, of which an SRH would just one kind of type-specific data. We should also accommodate to those who want to add their own specific, custom routing types for example.

Possible Solution

As @drunkirishcoder has shown with the current WIP https://github.com/capsule-rs/capsule/tree/djin/icmp-redux, we can treat different routing types somewhat similarly to how we're handling icmp messages.

@zeeshanlakhani zeeshanlakhani added the enhancement New feature or request label Apr 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant