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

240.0.0.0/4 may become available for public use #9

Open
daenney opened this issue Dec 2, 2022 · 0 comments
Open

240.0.0.0/4 may become available for public use #9

daenney opened this issue Dec 2, 2022 · 0 comments
Labels
rfc Updates related to IETF RFCs

Comments

@daenney
Copy link
Owner

daenney commented Dec 2, 2022

RFC 1112, Section 4, initially set aside 240.0.0.0/4 (a class E) as "Reserved", meaning it was not available for public allocation/use by RIRs.

Since this range has never seen use before and with the current shortage of IPv4 address, an RFC has been tabled to reclassify this range: https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-240/. Should that happen the range should automatically get removed from the special purpose registry but we should keep an eye out for how that's encoded and if necessary update ssrfgen to handle it.

@daenney daenney added the rfc Updates related to IETF RFCs label Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rfc Updates related to IETF RFCs
Projects
None yet
Development

No branches or pull requests

1 participant