Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucselx!ucsd!hub.ucsb.edu!spectrum.CMC.COM!lars From: lars@spectrum.CMC.COM (Lars Poulsen) Newsgroups: comp.protocols.tcp-ip Subject: Re: SLIP documents Message-ID: <1991Feb13.231653.20211@spectrum.CMC.COM> Date: 13 Feb 91 23:16:53 GMT References: <1991Feb6.172144.12605@nmt.edu> Organization: Rockwell CMC Lines: 26 In article <1991Feb6.172144.12605@nmt.edu> Ruth Milner (NRAO Array Operations Center) writes: >Where can I get some good documentation on SLIP? I have RFC1055, but it does >not state which of the actual protocols it uses (presumably because it can use >more than one). Now, I thought it used UDP in most implementations, and I'm >trying to convince someone that he's not getting much, if any, error correction >on his SLIP connections, but he wants actual written proof. He thinks it's >using TCP (as in "TCP/IP"), the same as Internet connections on Ethernet links. >I can't remember where I read (ages ago) that SLIP (generally) uses UDP; is >there such a beast? SLIP sits *UNDER* IP, and will carry any and all IP traffic that the router sends to the SLIP interface. The user executes the FTP client program. The FTP specification (RFC-959) will tell you that FTP uses two simultaneous TCP connections to do the work. It is possible to use a UDP based protocol to transfer files. Two examples of UDP based file transfer protocols are TFTP (RFC-783) and NFS. Be aware, however, that the error detection capabilites of SLIP are somewhat weaker than those of Ethernet (or HDLC). -- / Lars Poulsen, SMTS Software Engineer CMC Rockwell lars@CMC.COM