Date: Wed, 14 Nov 2012 10:48:56 +0100 From: Daniel Hartmeier <daniel@benzedrine.cx> To: Sean Chittenden <sean@chittenden.org> Cc: freebsd-net@freebsd.org Subject: Re: 0.0.0.0/8 oddities... Message-ID: <20121114094856.GA19022@insomnia.benzedrine.cx> In-Reply-To: <7BE7E643-FB13-45DE-BA40-257B8ADFAA98@chittenden.org> References: <DC8A0D79-8DF3-472F-9B1A-76BF8577A03C@chittenden.org> <50A20359.9080906@networx.ch> <7C614093-6408-49C6-8515-F6C09183453B@chittenden.org> <50A32FE7.2010206@rewt.org.uk> <7BE7E643-FB13-45DE-BA40-257B8ADFAA98@chittenden.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 13, 2012 at 11:06:04PM -0800, Sean Chittenden wrote:
> Where does it say that it shouldn't be used? Which RFC & ?? There are plenty of RFCs and I haven't exhaustively read things, so I reserve the right to be wrong & corrected, but I haven't seen anything that says, "do not use 0.0.0.0/8." 0.0.0.0/32, yes, that's a reserved and special IP address, but the remainder of the /8? It's a stretch to argue that it can't be used.
RFC1122 Section 3.2.1.3 (which RFC5735 references directly)
(a) { 0, 0 }
This host on this network. MUST NOT be sent, except as
a source address as part of an initialization procedure
by which the host learns its own IP address.
See also Section 3.3.6 for a non-standard use of {0,0}.
(b) { 0, <Host-number> }
Specified host on this network. It MUST NOT be sent,
except as a source address as part of an initialization
procedure by which the host learns its full IP address.
So a sender MUST NOT use 0.0/16 or 0/8 as destination, ever...
Daniel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121114094856.GA19022>