All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Seth David Schoen <schoen@loyalty.org>
Cc: linux-man@vger.kernel.org, gnu@toad.com
Subject: Re: [PATCH 1/1] ip.7: Add "special and reserved addresses" section
Date: Wed, 24 Mar 2021 09:26:03 +0100	[thread overview]
Message-ID: <87blb9q7ok.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20210322175815.GX10062@frotz.zork.net> (Seth David Schoen's message of "Mon, 22 Mar 2021 10:58:15 -0700")

* Seth David Schoen:

> Both things you noted are true: you can change broadcast addresses with
> ifconfig or ip (e.g. ip addr add x/y broadcast z dev d), and /31 subnets
> indeed don't have them.  This is defined at

There is also the questions of netmask that aren't in the CIDR style
(so 255.255.0.255 instead of 255.255.255.0).  Are they still
supported?

> I'm not familiar with a way in which it depends on the network device
> other than the /31 issue.  At least, this particular logic isn't
> affected by other aspects of the network device type.

Are there network devices that are neither point-to-point, nor do they
have broadcast support?

> Could you suggest a way that these details could usefully be described
> here?  The ability to change the broadcast address is very little-used,
> so I'm not sure many readers would benefit from details about it here,
> but I also wouldn't want to mislead them about that.  Maybe just
> changing it to "are both designated, by default, as broadcast
> addresses"?

My main concern is that the language should not imply that something
cannot happen if it actually can.  Otherwise programmers will end up
using this guidance and create software that won't work in such
configurations.

  parent reply	other threads:[~2021-03-24  8:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20  0:20 [PATCH 1/1] ip.7: Add "special and reserved addresses" section Seth David Schoen
2021-03-20 19:49 ` Florian Weimer
2021-03-22 17:58   ` Seth David Schoen
2021-03-22 21:29     ` Seth David Schoen
2021-03-24  7:07       ` John Gilmore
2021-03-24  8:26     ` Florian Weimer [this message]
2021-03-24 19:18       ` Seth David Schoen
2021-03-26 22:53         ` Seth David Schoen
2021-03-26 23:45           ` John Gilmore
2021-03-27  0:22             ` Seth David Schoen
2021-03-30  3:21           ` [PATCH v2] " Seth David Schoen
2021-05-06  2:37             ` [RESEND PATCH " Seth David Schoen

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=87blb9q7ok.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=gnu@toad.com \
    --cc=linux-man@vger.kernel.org \
    --cc=schoen@loyalty.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.