isValidIdentifier() doesn't conform to rfc6286 #489
Merged
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
BarbarossaTM
requested changes
Mar 20, 2025
There was a problem hiding this comment.
Thanks for your issue and PR!
To fully implement RFC6286 this seems to need some more changes to check the identifier collision for iBGP peers and, ideally, the collision handling as of section 2.3.
I'd prefer to have at least the first part conforming to RFC6286, ideally both. Do you want to take a shot at updating the PR to fully support RFC6286? :-)
BarbarossaTM
approved these changes
Mar 23, 2025
|
Thank you. Do you have a timeline for this to reach a release? |
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.
Fixes #488