39 lines
1.5 KiB
HTML
39 lines
1.5 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
|
|
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>UUCP Low-Level Protocols</TITLE>
|
|
</HEAD>
|
|
<BODY LANG="EN">
|
|
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node181.html">Protocol Overview</A>
|
|
<B>Up:</B> <A HREF="node146.html">Managing Taylor UUCP</A>
|
|
<B> Previous:</B> <A HREF="node179.html">Anonymous UUCP</A>
|
|
<BR> <P>
|
|
<H1><A NAME="SECTION0014600000">UUCP Low-Level Protocols</A></H1>
|
|
<P>
|
|
<A NAME="uucpprotocols"></A>
|
|
<A NAME="6449"></A>
|
|
<P>
|
|
To negotiate session control and file transfers with the remote end,
|
|
uucico uses a set of standardized messages. This is often
|
|
referred to as the high-level protocol. During the initialization phase
|
|
and the hangup phase these are simply sent across as strings. However,
|
|
during the real transfer phase, an additional low-level protocol is
|
|
employed which is mostly transparent to the higher levels. This is to
|
|
make error checks possible when using unreliable lines, for instance.
|
|
<P>
|
|
<BR> <HR>
|
|
<UL>
|
|
<LI> <A HREF="node181.html#SECTION0014610000">Protocol Overview</A>
|
|
<LI> <A HREF="node182.html#SECTION0014620000">Tuning the Transmission Protocol</A>
|
|
<LI> <A HREF="node183.html#SECTION0014630000">Selecting Specific Protocols</A>
|
|
</UL>
|
|
<BR> <HR>
|
|
<P><ADDRESS>
|
|
<I>Andrew Anderson <BR>
|
|
Thu Mar 7 23:22:06 EST 1996</I>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|