SNMS4@vaxb.acs.unt.edu ("Kevin W. Mullet, Univ. of N. Tx") (12/10/90)
A couple of weeks ago, I was prompted by an offhanded comment by our VAX
manager that IP routing was probably over my head to try and find as many
sources for IP routing information as I could and live/eat/breathe IP routing
for a time, indignantly I might add. :)
After posting a query to a number of newsgroups and mailing lists, I've got a
good start on this path and have once again affirmed my belief that nothing is
over anyone's head as long as you can reduce it to an appropriate metaphor.
Below is a representative sample of the replies I got. These documents should
be available to anyone who gets this note. Internet folks can FTP directly,
BITNET folks will have to use BITFTP. Thanks to all who replied. I appreciate
each of the replies I got, even the one that sent me the entire RFC Index as an
attachment. (Gads!) :)
======= cut here =====================================================
From: IN%"rlg@desktalkdesktalk.com" 26-NOV-1990 22:14:22.66
Hi Kevin,
Got your note from tcp-ip@nic.ddn.mil (along with a billion others from the
same place), and thought this might help. Here is a copy of the RFC index.
Check it out for RFCs on Routing Information Protocol (1058 I think),
Open Shortest Path First (OSPF), End System-Intermediate System (ES-IS).
From: IN%"MH@NIC.DDN.MIL" "Mark Hamamoto" 28-NOV-1990 13:31:59.55
Network Working Group J. Mogul (Stanford)
Request for Comments: 950 J. Postel (ISI)
August 1985
Internet Standard Subnetting Procedure
[RFC followed . . . ]
From: IN%"root@rainbow.cse.nau.edu" 29-NOV-1990 09:46:08.08
There's a good document describing RIP routing, which is what the
"routed" daemon uses. RIP is too simple / small to use on the Internet,
but many sites still use it within their local network. Other routing
protocols you should look at include IGRP, invented by cisco Systems,
and used in some areas on the Internet, if I understand correctly.
You can ftp a copy of "rip.txt" document from spot.colorado.edu,
in the "pub" directory. It's good information, and easier to read
than RFCs.
-- paul