Off Topic Request: I need some help!

Hey all,

I was hoping someone could give me the RFC for non routable addresses
(10.0.0.0). I did a couple of searchs for it, but I did not find what I
was looking for. So if anyone knows ( and I know you do) could you please
help me out.

Thank you,

Dan Bustillos
Datalink Computer Services
(530) 897-6400
(888) 328-4638

I was hoping someone could give me the RFC for non routable addresses

1918

Hi,

I was hoping someone could give me the RFC for non routable addresses
(10.0.0.0). I did a couple of searchs for it, but I did not find what I
was looking for. So if anyone knows ( and I know you do) could you please
help me out.

That's RFC 1918. Check out <ftp://ftp.isi.edu/in-notes/rfc1918.txt>...

    "Error, No Keyboard - Press F1 to continue"
Only on a PC would you see this error. Never on my mac.

Wow, how profound!

You want /all/ of the RFCs, right?

RFC1166 -- Internet Numbers
           Covers addressing for Class D/E (multicast/experimental) traffic;
           shouldn't be used as source addresses.
RFC1700 -- Assigned Numbers
           Covers fun networks like 0/8 and 255.255.255.255/32,
           which aren't nice for source addresses (or destination addresses
           outside of your network, depending on your viewpoint).
RFC1918 -- Address Allocation for Private Internets
           Covers the 'private' address space definitions.

draft-ietf-dhc-ipv4-autoconfig-04.txt -- Auto-IP configuration in ad-hoc
           networks: 169.254/16

Then there is the IANA test network, 192.0.2/24. (Anyone have an official
reference to this one?)

Then there is the unallocated IP address space, as determined by the IANA
and the regional registries.

And then there are a few other IANA-reserved networks.

All of these address classes should be invalid as source addresses (except
where negotiated in advance), and very few should be permitted as destination
addresses (Multicast for example, should be permitted as a desination, just
not as a source).

[great list deleted]

For reference, apart from reading rfc-index.txt, has anyone taken the
time to build a categorised (probably web based) RFC tree ? With a
search engine ? Public ?

Would save me much time - as my memory for most RFC numbers is bad.

Regards,