-
Notifications
You must be signed in to change notification settings - Fork 16
Ipv6 srh no tlv #445
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
Merged
Merged
Ipv6 srh no tlv #445
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
apratimmukherjee
approved these changes
Sep 23, 2025
Contributor
apratimmukherjee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good , some comments on descriptions.
SuryyaKrJana
approved these changes
Sep 24, 2025
Contributor
SuryyaKrJana
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks ok now.
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.
IPv6 Segment Routing Header Support
Redocly view of proposed model
Proposal is for IPv6 segment routing (Type 4) header, This is the first of the IPv6 routing extension header support in OTG model. This current PR is an abridged version of the original PR and does not have the SR TLVs.
The model is made generic to accommodate other IPv6 extension header types, hop-by-hop or fragment. Currently we will support routing extensions only. In routing also we will currently support Type 4 which is segment routing.
Note: The IPv6 next_header if set to AUTO, will be updated to reflect the correct next header type, which is 43 for IPv6 route.
RFC for reference