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

bpo-42937: Update ipaddress.py to include additional private range of IPs #26205

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

wjohnston99
Copy link

@wjohnston99 wjohnston99 commented May 18, 2021

…f IPs

There is a lot more IPs in the private address range.   I will create a separate issue for that.  This makes this a very simple request.  I verified the IP and that it is not routeable globally according according to IANA.  This is my first PR for cpython.   Please let me know if bpo or anything like that is not correct.
    
https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
…f IPs

There is a lot more IPs in the private address range.   I will create a separate issue for that.  This makes this a very simple request.  I verified the IP and that it is not routeable globally according according to IANA.  This is my first PR for cpython.   Please let me know if bpo or anything like that is not correct.
    
https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
@the-knights-who-say-ni
Copy link

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

CLA Missing

Our records indicate the following people have not signed the CLA:

@wjohnston99

For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

If you have recently signed the CLA, please wait at least one business day
before our records are updated.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

@wjohnston99
Copy link
Author

I have now signed a CLA.

Copy link
Author

@wjohnston99 wjohnston99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Signed CLA

@mjpieters
Copy link
Contributor

I note that the list is not complete; unless the IANA marks a subset of 192.0.0.0/24 as globally reachable in future, all of that subnet except for 192.0.0.9/32 and 192.0.0.10/32 should be considered private. See my comments on the associated issue.

Copy link

@wjohnston888 wjohnston888 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please review last comment. I am addressing this one IP to address the CR. I am more than willing to update the private and special IPs as declared by IANA and hopefully remove some of the confusion. This is ready to go, pending this approved. This change does specifically address this CR. First time submitting so just want to get used to the process.

@github-actions
Copy link

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Stale PR or inactive for long period of time. label Jun 30, 2021
@wjohnston888
Copy link

wjohnston888 commented Jul 7, 2021 via email

@github-actions github-actions bot removed the stale Stale PR or inactive for long period of time. label Jul 8, 2021
@wjohnston888
Copy link

Is there anyway to move this forward.

Copy link
Contributor

@jstasiak jstasiak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants