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

RFC6598 addresses not recognized as private #68

Open
gkuenning opened this issue Mar 6, 2024 · 0 comments
Open

RFC6598 addresses not recognized as private #68

gkuenning opened this issue Mar 6, 2024 · 0 comments

Comments

@gkuenning
Copy link

The private? function doesn't recognize the RFC6598 "shared address space", which is basically a new(ish) version of the well known 192.168/16, 172.16/12, and 10./8 spaces. The new space is 100.64.0.0/10.

A complete list of reserved address spaces can be found in the special-purpose address registries at https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml and https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml

I believe that in those two tables, any address marked with "True" in the Source and Destination columns, and "False" in the "Globally Reachable" column, should be considered private. However I'll leave that decision to others.

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

No branches or pull requests

1 participant