On Mon, 2015-04-20 at 21:15 -0400, Dianne Skoll wrote: > On Mon, 20 Apr 2015 17:02:09 -0700 (PDT) > John Hardin <jhar...@impsec.org> wrote: > > > I suggest that this rule should treat 0/8 as equivalent to 127/8. > > That's essentially what it's reserved for, just "local to the LAN" > > vs. "local to the host". > > Does 0/8 really mean that? On at least one OS (Linux), the TCP stack > treats it specially: > The situation seems to be confused at best. Many of the lists of reserved IP ranges don't even mention 0/8.
- the Wikipedia reserved IP page says its for multicasting on the LAN and quotes RFC1700 page 4, where there's no mention of it that I could see but its private address page doesn't mention 0/8 at all, but a shed-load of other special addresses are also listed. - The IANA IPv4 Address Space Registry says 0/8 for 'IANA - Local Identification' - RFC 1918 defines the 10/8, 172.16/12 and 192.168/16 as private address ranges but leaves it at that. - Microsoft adds 169.254/16 as something called APIPA in addition to RFC 1918. RFC 3927 describes it as link-local. Is this reserved for asking a DHCP server for an address? At this point I gave up the search and decided that 'confused' is a fair description. I hope this helps, but suspect it doesn't. Martin
