RFC6598 addresses not recognized as private
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 82
- Forks
- 42
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the private? function in the Ruby ipaddr implementation and review the existing tests for private address handling. Check the RFC6598 100.64.0.0/10 range against the project's chosen definition of private, then verify the test suite demonstrates the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100