From: Dave Taht <dave.taht@gmail.com>
To: netdev@vger.kernel.org
Cc: Dave Taht <dave.taht@gmail.com>
Subject: [net-next 0/1] Allow 0.0.0.0/8 as a valid address range
Date: Sat, 22 Jun 2019 10:07:33 -0700 [thread overview]
Message-ID: <1561223254-13589-1-git-send-email-dave.taht@gmail.com> (raw)
My talk's slides and video at netdev 0x13 about
"Potential IPv4 Unicast expansions" is up, here:
https://netdevconf.org/0x13/session.html?talk-ipv4-unicast-expansions
There are roughly 419 million IPv4 addresses that are unallocated and
unused in the 0, localhost, reserved future multicast, and 240/4
spaces.
Linux already supports 240/4 fully. SDN's such as AWS already support
the entire IPv4 address space as a unicast playground.
This first patch for 0/8 was intended primarily as a conversation
starter - arguably we should rename the function across 22 fairly
"hot" files - but:
Should Linux treat these ranges as policy, and no longer enforce via
mechanism?
A full patchset for adding 225-232, and 127 address spaces is on github:
https://github.com/dtaht/unicast-extensions
with the very few needed patches for routing daemons and BSD also
available there.
Dave Taht (1):
Allow 0.0.0.0/8 as a valid address range
include/linux/in.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2019-06-22 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 17:07 Dave Taht [this message]
2019-06-22 17:07 ` [PATCH net-next 1/1] Allow 0.0.0.0/8 as a valid address range Dave Taht
2019-06-26 20:20 ` David Miller
2019-07-14 3:57 ` Paul Marks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1561223254-13589-1-git-send-email-dave.taht@gmail.com \
--to=dave.taht@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).