Skip to content

240.0.0.0/4 may become available for public use #9

@daenney

Description

@daenney

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    rfcUpdates related to IETF RFCs

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions