gh-103268: Add IPv4-IPv6 Translation#103270
Open
malvidin wants to merge 6 commits intopython:mainfrom
Open
Conversation
This does not handle translation with a Network-Specific Prefix, which must be known beforehand when embedding IPv4 addresses with RFC 6052. https://www.rfc-editor.org/rfc/rfc6052.html#section-2.2
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Member
|
Test case should be added in |
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Remove trailing spaces to appease Lint bot
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
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.
This does not handle translation with a Network-Specific Prefix, which must be known beforehand when embedding IPv4 addresses with RFC 6052.
https://www.rfc-editor.org/rfc/rfc6052.html#section-2.2
See #103268