public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Seth David Schoen <schoen@loyalty.org>
To: linux-man <linux-man@vger.kernel.org>
Subject: ip.7 update on treatment of reserved addresses?
Date: Wed, 12 Apr 2023 16:06:49 -0700	[thread overview]
Message-ID: <20230412230649.GA2462622@demorgan> (raw)

Hi,

I've submitted a patch a couple of times that adds more detailed
information in ip.7 about how the Linux kernel treats reserved IPv4
addresses.  (There is some discussion already there, but it's not
entirely comprehensive and up-to-date with respect to the current
behavior.)  I'm paying attention to this because I've been actively
involved in efforts to get the kernel to treat these addresses more
permissively than historical standards suggest -- which it indeed
does.

I haven't gotten any feedback on my patch on the occasions when I've
submitted it, so I thought I'd ask directly whether anyone is
interested in reviewing it or discussing it, or whether there would
be any interest in expanding the documentation on this point under any
circumstances.

Thanks!


(specifically, Linux now permits you to assign the lowest, or "network",
address on a segment as a unicast address; it has for several years
permitted you to assign addresses from within 0/8; it has for many
years permitted you to assign addresses from within 240/4; and all of
these are also accepted as valid unicast destinations -- none of which
users would assume just from reading RFCs!)

             reply	other threads:[~2023-04-12 23:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 23:06 Seth David Schoen [this message]
2023-04-13  0:37 ` ip.7 update on treatment of reserved addresses? Alejandro Colomar

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=20230412230649.GA2462622@demorgan \
    --to=schoen@loyalty.org \
    --cc=linux-man@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