bbs/deb-mbse
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixed HTML codes in Fidonet documents

Browse Source
This commit is contained in:
Michiel Broek 2002-02-16 21:38:40 +00:00
parent 1fb610f935
commit 0aa608b565
42 changed files with 18330 additions and 18508 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
html/ftsc/fsc-0035.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Transparant Gateways to and from FidoNet.</TITLE>
</HEAD>
@ -72,7 +73,7 @@ FidoNet is a trademark of Tom Jennings and Fido Software, to whom we all owe
much thanks for the origin and spirit of FidoNet.
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fsc-0039.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>A Type-2 Packet Extension Proposal.</TITLE>
</HEAD>
@ -355,7 +356,7 @@ Date: 29-Sep-90
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

1
html/ftsc/fsc-0046.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>A Product Identiefier for FidoNet Message Handlers.</TITLE>
</HEAD>

15
html/ftsc/fsc-0048.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>A Proposed Type-2 Packet Extension.</TITLE>
</HEAD>
@ -299,11 +300,11 @@ Date: 21-Oct-90
==========================
Do we have a CW Does CW indicate
stored for dest? YES ----> higher packets YES ---> Generate higher
stored for dest? YES ----&gt; higher packets YES ---&gt; Generate higher
NO we support? packet
| NO
\|/ |
+-----<----------------------+
+-----&lt;----------------------+
|
Fill header with all info
|
@ -316,7 +317,7 @@ Date: 21-Oct-90
| set AuxNet = OrigNet
\|/ set OrigNet = -1
| |
+-----<----------------------------------------+
+-----&lt;----------------------------------------+
|
Add Messages
|
@ -329,11 +330,11 @@ Date: 21-Oct-90
Receive Packet
|
Packettype = 2 NO -------------> Process Type-Other
Packettype = 2 NO -------------&gt; Process Type-Other
YES
|
|
CWcopies match NO --------+------> Treat as normal Stone-Age packet
CWcopies match NO --------+------&gt; Treat as normal Stone-Age packet
YES | |
| | |
Store CW /|\ |
@ -351,7 +352,7 @@ Date: 21-Oct-90
| \|/
! \|/ Set OrigNet is AuxNet
| |
+------<-----------------------------------+
+------&lt;-----------------------------------+
|
Process using added info
@ -410,7 +411,7 @@ Date: 21-Oct-90
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fsc-0049.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>A Proposal for Passing Domain Information During an FST-0006 Session.</TITLE>
</HEAD>
@ -96,7 +97,7 @@ with the current uses of all FTS-0006 fields, and should not affect operation
of any mailer that has used reserved bytes in the Hello packet.
</PRE>
<A HREF="./"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="./"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

7
html/ftsc/fsc-0050.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>A Character Set Identifier For FidoNet Message Editors.</TITLE>
</HEAD>
@ -38,7 +39,7 @@ Status of this document:
Fido and FidoNet are registered marks of Tom Jennings and Fido
Software.
Purpose
This document should serve as a guide for the character set
@ -60,7 +61,7 @@ Status of this document:
Format
^aCHARSET: <Character set identifier>
^aCHARSET: &lt;Character set identifier&gt;
Sample
@ -91,7 +92,7 @@ Status of this document:
AMIGA AMIGA complete character set
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

5
html/ftsc/fsc-0053.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Specifications for the ^aFLAGS field.</TITLE>
</HEAD>
@ -68,7 +69,7 @@ Status of this document:
Flags
The FLAGS string should be placed somewhere near the beginning of
the message text, and is preceeded by a <SOH> (^a) character. There
the message text, and is preceeded by a &lt;SOH&gt; (^a) character. There
is no need to support all or any of the below mentioned flags.
If flags are stripped when a message passes through a system, all
@ -179,7 +180,7 @@ Status of this document:
specified on the title page. Please send feedback via netmail.
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

33
html/ftsc/fsc-0056.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>EMSI/IEMSI Protocol Definitions.</TITLE>
</HEAD>
@ -218,7 +219,7 @@ Date: 03-May-1991
Calling system Answering system
+-+-------------------------------+----------------------------------+
:1: Send <CR> until ANY character : Send EMSI_REQ and possible :
:1: Send &lt;CR&gt; until ANY character : Send EMSI_REQ and possible :
: : is received. : banner, etc. :
+-+-------------------------------+----------------------------------+
:2: Receive banner, etc. Monitor : Monitor line for the EMSI_INQ :
@ -232,7 +233,7 @@ Date: 03-May-1991
: : by possible other protocol : characters and if received, :
: : start characters. : attempt to handshake immediately.:
: : : :
: : Transmit <CR> : Go to step 3. :
: : Transmit &lt;CR&gt; : Go to step 3. :
+-+-------------------------------+----------------------------------+
:4: If EMSI_REQ sequence received,:
: : send EMSI_INQ and attempt to :
@ -241,26 +242,26 @@ Date: 03-May-1991
+-+-------------------------------+
In steps 1 and 2, both the Calling and Answering system terminate all
sequences with <CR>. In step 3, the Calling system does not terminate
sequences with <CR> as it is explicitly transmitted after possible
sequences with &lt;CR&gt;. In step 3, the Calling system does not terminate
sequences with &lt;CR&gt; as it is explicitly transmitted after possible
protocol start characters. In step 4, the Calling system once again
terminate all sequences with a <CR>.
terminate all sequences with a &lt;CR&gt;.
STEP 2A, RECEIVE EMSI HANDSHAKE
At this point, all sequences are terminated with a <CR>.
At this point, all sequences are terminated with a &lt;CR&gt;.
+-+------------------------------------------------------------------+
:1: Tries=0, T1=20 seconds, T2=60 seconds :
+-+------------------------------------------------------------------+
:2: Increment Tries :
: : :
: : Tries>6? Terminate, and report failure. :
: : Tries&gt;6? Terminate, and report failure. :
: +------------------------------------------------------------------+
: : Are we answering system? Transmit EMSI_REQ, go to step 3. :
: +------------------------------------------------------------------+
: : Tries>1? Transmit EMSI_NAK, go to step 3. :
: : Tries&gt;1? Transmit EMSI_NAK, go to step 3. :
: +------------------------------------------------------------------+
: : Go to step 4. :
+-+------------------------------------------------------------------+
@ -301,7 +302,7 @@ Date: 03-May-1991
STEP 2B, TRANSMIT EMSI HANDSHAKE
At this point, all sequences are terminated with a <CR>.
At this point, all sequences are terminated with a &lt;CR&gt;.
+-+------------------------------------------------------------------+
:1: Tries=0, T1=60 seconds :
@ -309,7 +310,7 @@ Date: 03-May-1991
:2: Transmit EMSI_DAT packet and increment Tries :
: : :
: +------------------------------------------------------------------+
: : Tries>6? Terminate, and report failure. :
: : Tries&gt;6? Terminate, and report failure. :
: +------------------------------------------------------------------+
: : Go to step 3. :
+-+------------------------------------------------------------------+
@ -808,7 +809,7 @@ Date: 03-May-1991
and capabilities.
=====================================================================
EMSI ISM **EMSI_ISM<len><data><crc32><CR>
EMSI ISM **EMSI_ISM&lt;len&gt;&lt;data&gt;&lt;lt;crc32&gt;&lt;lt;CR&gt;
---------------------------------------------------------------------
The ISM packet is used to transfer ASCII images from the Server to
the Client. These images can then be recalled by the Client when
@ -816,7 +817,7 @@ Date: 03-May-1991
be further described in future revisions of this document.
=====================================================================
EMSI CHT **EMSI_CHT<crc16><CR>
EMSI CHT **EMSI_CHT&lt;crc16&gt;&lt;CR&gt;
---------------------------------------------------------------------
The CHT sequence is used by the Server to instruct the Client
software to enter its full-screen conversation mode function (CHAT).
@ -833,7 +834,7 @@ Date: 03-May-1991
characters back to the Client.
=====================================================================
EMSI TCH **EMSI_TCH<crc16><CR>
EMSI TCH **EMSI_TCH&lt;crc16&gt;&lt;CR&gt;
---------------------------------------------------------------------
The TCH sequence is used by the Server to instruct the Client
software to terminate its full-screen conversation mode function
@ -974,7 +975,7 @@ Date: 03-May-1991
HUSH Do not disturb.
MORE Page pausing, often referred to as "More".
FSED* Full-screen editor.
XPRS <reserved>.
XPRS &lt;reserved&gt;.
(*) Note that this allows the Client to request use of a full-screen
editor without requiring that it also supports a full-screen terminal
@ -1055,7 +1056,7 @@ Date: 03-May-1991
Wait
---------------------------------------------------------------------
A single character used by the Server to indicate that the user
has to press the <Enter> key to resume operation. This is used in
has to press the &lt;Enter&gt; key to resume operation. This is used in
conjunction with ASCII Image Downloads (see ISM packet).
=====================================================================
@ -1071,7 +1072,7 @@ Date: 03-May-1991
designed by Joaquim H. Homrighausen and Andrew Milner.
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

37
html/ftsc/fsc-0057.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Conference Managaers - Specifications for Requests.</TITLE>
</HEAD>
@ -73,7 +74,7 @@ Date: 07-Dec-92
Optional information is enclosed with square brackets, while
variable information is enclosed with angle brackets. For example:
+CONF [,R=<n>]
+CONF [,R=&lt;n&gt;]
indicates that the section within square brackets is optional, and
if supplied, requires a parameter after the equals sign.
@ -166,7 +167,7 @@ Date: 07-Dec-92
Rescans of a single area, newly linked, could be requested as
follows:
+CONFNAME, R[=<n>]
+CONFNAME, R[=&lt;n&gt;]
where 'n' is the number of messages in that area to be rescanned.
(The space following the comma is optional, but allowed.)
@ -183,9 +184,9 @@ Date: 07-Dec-92
The proposed kludge is:
^ARESCANNED <addr>
^ARESCANNED &lt;addr&gt;
where <addr> is the network address, including domain, of the
where &lt;addr&gt; is the network address, including domain, of the
system from which the mail was rescanned.
In alternative to a rescan, a sysop might request a "sample",
@ -194,7 +195,7 @@ Date: 07-Dec-92
ASCII text file, and send it along with the reply, to the requesting
system. A "sample" request would be made as follows:
+CONFNAME, S[=<n>]
+CONFNAME, S[=&lt;n&gt;]
where 'n' indicates how many messages should be sampled.
@ -206,7 +207,7 @@ Date: 07-Dec-92
The format of this command is:
=CONFNAME, <param>[=<n>]
=CONFNAME, &lt;param&gt;[=&lt;n&gt;]
Thus a rescan request for the most recent 50 messages would be
specified as:
@ -273,7 +274,7 @@ Date: 07-Dec-92
via remote, this could be done by including a line such as the
following in the message text:
&CONFNAME
&amp;CONFNAME
In order to remote delete an area, the requesting sysop should
include a line like this in the body of the message text:
@ -321,9 +322,9 @@ Date: 07-Dec-92
mail bound for his system. This could be done with the following
command in the message to a ConfMgr:
%COMPRESS <method>
%COMPRESS &lt;method&gt;
where <method> is one of the compression programs supported by
where &lt;method&gt; is one of the compression programs supported by
the system. Of course, the remote system should also be able to
determine which compression methods are available; this could be
done with
@ -345,7 +346,7 @@ Date: 07-Dec-92
other system's sysop. This could easily be done if the
conference manager implemented the following command:
%PWD <new_password>
%PWD &lt;new_password&gt;
The new password (case insensitive) would replace the current
one as of the next request.
@ -398,7 +399,7 @@ Date: 07-Dec-92
information:
struct bcl_header {
char FingerPrint[4]; /* BCL<NUL> */
char FingerPrint[4]; /* BCL&lt;NUL&gt; */
char ConfMgrName[31]; /* Name of "ConfMgr" */
char Origin[51]; /* Originating network addr */
long CreationTime; /* UNIX-timestamp when created */
@ -463,7 +464,7 @@ Date: 07-Dec-92
sent to another system, perhaps a co-sysop or a sysop point
node. This could be done with the command:
%RECEIPT <name>,<address>
%RECEIPT &lt;name&gt;,&lt;address&gt;
embedded in the request message. For example:
@ -495,7 +496,7 @@ Date: 07-Dec-92
+CONFNAME[,R|S] Request to link to CONFNAME
-CONFNAME Request to unlink from CONFNAME
=CONFNAME,R|S Rescan or "sample" linked conference
&CONFNAME Request to create CONFNAME
&amp;CONFNAME Request to create CONFNAME
~CONFNAME Request to delete CONFNAME
#OLD NEW Name change request
@ -503,13 +504,13 @@ Date: 07-Dec-92
%QUERY Only list linked areas
%UNLINKED List available but unlinked areas
%HELP Send help text
%FROM <addr> Simulate request from another system
%FROM &lt;addr&gt; Simulate request from another system
%RESCAN Rescan conferences linked in current request
%COMPRESS <method> Change compression method
%PWD <new_pwd> Change ConfMgr password
%COMPRESS &lt;method&gt; Change compression method
%PWD &lt;new_pwd&gt; Change ConfMgr password
%PAUSE Suspend link
%RESUME Resume link
%RECEIPT <name>,<addr> Send copy of receipt to another system
%RECEIPT &lt;name&gt;,&lt;addr&gt; Send copy of receipt to another system
%NOTE Introduces comment to the sysop
@ -526,7 +527,7 @@ Date: 07-Dec-92
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

97
html/ftsc/fsc-0059.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Newsgroup Interchange within FidoNet.</TITLE>
</HEAD>
@ -43,7 +44,7 @@ Introduction:
This document defines the standard format for the interchange of USENET
news messages among FidoNet nodes. It incorporates by reference the
document RFC-1036, "Standard for Interchange of USENET Messages" by M.
Horton of AT&T Bell Laboratories and R. Adams of the Center for Seismic
Horton of AT&amp;T Bell Laboratories and R. Adams of the Center for Seismic
Studies. A copy of RFC-1036 should be included in the distribution
archive of this standard. However, RFC-1036 is NOT applicable in its
entirety to FidoNet. Therefore, unless specifically referenced
@ -488,7 +489,7 @@ limit on UseNet messages. If a FidoNet node passes newsgroup messages
to, or on behalf of other FidoNet nodes, it is NOT permissible to
discard or truncate messages that exceed a preset length limit. Note
that in a batched newsgroup file, each message is preceded by a header
of the form "#! rnews <length in bytes>". Since the message text
of the form "#! rnews &lt;length in bytes&gt;". Since the message text
length is never changed in processing, it is possible to determine the
length of a message after processing by reading in all the header
lines, calculating the combined length of the header lines prior to
@ -605,7 +606,7 @@ STATUS OF THIS MEMO
Horton & Adams [Page 1]
Horton &amp; Adams [Page 1]
RFC 1036 Standard for USENET Messages December 1987
@ -623,11 +624,11 @@ RFC 1036 Standard for USENET Messages December 1987
Path: cbosgd!mhuxj!mhuxt!eagle!jerry
Newsgroups: news.announce
Subject: Usenet Etiquette -- Please Read
Message-ID: <642@eagle.ATT.COM>
Message-ID: &lt;642@eagle.ATT.COM&gt;
Date: Fri, 19 Nov 82 16:14:55 GMT
Followup-To: news.misc
Expires: Sat, 1 Jan 83 00:00:00 -0500
Organization: AT&T Bell Laboratories, Murray Hill
Organization: AT&amp;T Bell Laboratories, Murray Hill
The body of the message comes here, after a blank line.
@ -661,7 +662,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 2]
Horton &amp; Adams [Page 2]
RFC 1036 Standard for USENET Messages December 1987
@ -717,19 +718,19 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 3]
Horton &amp; Adams [Page 3]
RFC 1036 Standard for USENET Messages December 1987
From: mark@cbosgd.ATT.COM
From: mark@cbosgd.ATT.COM (Mark Horton)
From: Mark Horton <mark@cbosgd.ATT.COM>
From: Mark Horton &lt;mark@cbosgd.ATT.COM&gt;
Full names may contain any printing ASCII characters from space
through tilde, except that they may not contain "(" (left
parenthesis), ")" (right parenthesis), "<" (left angle bracket), or
">" (right angle bracket). Additional restrictions may be placed on
parenthesis), ")" (right parenthesis), "&lt;" (left angle bracket), or
"&gt;" (right angle bracket). Additional restrictions may be placed on
full names by the mail standard, in particular, the characters ","
(comma), ":" (colon), "@" (at), "!" (bang), "/" (slash), "="
(equal), and ";" (semicolon) are inadvisable in full names.
@ -773,7 +774,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 4]
Horton &amp; Adams [Page 4]
RFC 1036 Standard for USENET Messages December 1987
@ -816,20 +817,20 @@ RFC 1036 Standard for USENET Messages December 1987
Message-ID be reused for at least two years.) Message-ID's have the
syntax:
<string not containing blank or ">">
&lt;string not containing blank or "&gt;"&gt;
In order to conform to RFC-822, the Message-ID must have the format:
<unique@full_domain_name>
&lt;unique@full_domain_name&gt;
where full_domain_name is the full name of the host at which the
message entered the network, including a domain that host is in, and
unique is any string of printing ASCII characters, not including "<"
(left angle bracket), ">" (right angle bracket), or "@" (at sign).
unique is any string of printing ASCII characters, not including "&lt;"
(left angle bracket), "&gt;" (right angle bracket), or "@" (at sign).
Horton & Adams [Page 5]
Horton &amp; Adams [Page 5]
RFC 1036 Standard for USENET Messages December 1987
@ -838,7 +839,7 @@ RFC 1036 Standard for USENET Messages December 1987
sequence number for messages submitted to the network, or a short
string derived from the date and time the message was created. For
example, a valid Message-ID for a message submitted from host ucbvax
in domain "Berkeley.EDU" would be "<4123@ucbvax.Berkeley.EDU>".
in domain "Berkeley.EDU" would be "&lt;4123@ucbvax.Berkeley.EDU&gt;".
Programmers are urged not to make assumptions about the content of
Message-ID fields from other hosts, but to treat them as unknown
character strings. It is not safe, for example, to assume that a
@ -885,7 +886,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 6]
Horton &amp; Adams [Page 6]
RFC 1036 Standard for USENET Messages December 1987
@ -941,7 +942,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 7]
Horton &amp; Adams [Page 7]
RFC 1036 Standard for USENET Messages December 1987
@ -997,7 +998,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 8]
Horton &amp; Adams [Page 8]
RFC 1036 Standard for USENET Messages December 1987
@ -1053,7 +1054,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 9]
Horton &amp; Adams [Page 9]
RFC 1036 Standard for USENET Messages December 1987
@ -1109,7 +1110,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 10]
Horton &amp; Adams [Page 10]
RFC 1036 Standard for USENET Messages December 1987
@ -1143,7 +1144,7 @@ RFC 1036 Standard for USENET Messages December 1987
From: reid@decwrl.DEC.COM (Brian Reid)
Newsgroups: news.lists,news.groups
Subject: USENET READERSHIP SUMMARY REPORT FOR SEP 86
Message-ID: <5658@decwrl.DEC.COM>
Message-ID: &lt;5658@decwrl.DEC.COM&gt;
Date: 1 Oct 86 11:26:15 GMT
Organization: DEC Western Research Laboratory
Lines: 441
@ -1165,7 +1166,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 11]
Horton &amp; Adams [Page 11]
RFC 1036 Standard for USENET Messages December 1987
@ -1184,7 +1185,7 @@ RFC 1036 Standard for USENET Messages December 1987
3.1. Cancel
cancel <Message-ID>
cancel &lt;Message-ID&gt;
If a message with the given Message-ID is present on the local
@ -1205,23 +1206,23 @@ RFC 1036 Standard for USENET Messages December 1987
3.2. Ihave/Sendme
ihave <Message-ID list> [<remotesys>]
sendme <Message-ID list> [<remotesys>]
ihave &lt;Message-ID list&gt; [&lt;remotesys&gt;]
sendme &lt;Message-ID list&gt; [&lt;remotesys&gt;]
This message is part of the ihave/sendme protocol, which allows one
host (say A) to tell another host (B) that a particular message has
been received on A. Suppose that host A receives message
"<1234@ucbvax.Berkeley.edu>", and wishes to transmit the message to
"&lt;1234@ucbvax.Berkeley.edu&gt;", and wishes to transmit the message to
host B.
A sends the control message "ihave <1234@ucbvax.Berkeley.edu> A" to
A sends the control message "ihave &lt;1234@ucbvax.Berkeley.edu&gt; A" to
host B (by posting it to newsgroup to.B). B responds with the
control message "sendme <1234@ucbvax.Berkeley.edu> B" (on newsgroup
control message "sendme &lt;1234@ucbvax.Berkeley.edu&gt; B" (on newsgroup
to.A), if it has not already received the message. Upon receiving
Horton & Adams [Page 12]
Horton &amp; Adams [Page 12]
RFC 1036 Standard for USENET Messages December 1987
@ -1242,7 +1243,7 @@ RFC 1036 Standard for USENET Messages December 1987
3.3. Newgroup
newgroup <groupname> [moderated]
newgroup &lt;groupname&gt; [moderated]
This control message creates a new newsgroup with the given name.
Since no messages may be posted or forwarded until a newsgroup is
@ -1257,7 +1258,7 @@ RFC 1036 Standard for USENET Messages December 1987
3.4. Rmgroup
rmgroup <groupname>
rmgroup &lt;groupname&gt;
This message removes a newsgroup with the given name. Since the
newsgroup is removed from every host on the network, this command
@ -1277,7 +1278,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 13]
Horton &amp; Adams [Page 13]
RFC 1036 Standard for USENET Messages December 1987
@ -1333,7 +1334,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 14]
Horton &amp; Adams [Page 14]
RFC 1036 Standard for USENET Messages December 1987
@ -1356,7 +1357,7 @@ RFC 1036 Standard for USENET Messages December 1987
one system to the other, and once on the receiving system, processed
by the netnews software on that system. (On UNIX systems, this
usually means the rnews program being run with the message on the
standard input. <1>)
standard input. &lt;1&gt;)
It is not a requirement that USENET hosts have mail systems capable
of understanding the Internet mail syntax, but it is strongly
@ -1389,7 +1390,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 15]
Horton &amp; Adams [Page 15]
RFC 1036 Standard for USENET Messages December 1987
@ -1445,7 +1446,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 16]
Horton &amp; Adams [Page 16]
RFC 1036 Standard for USENET Messages December 1987
@ -1459,7 +1460,7 @@ RFC 1036 Standard for USENET Messages December 1987
NFrom: derek@sask.UUCP (Derek Andrew)
NNewsgroups: misc.test
NSubject: necessary test
NMessage-ID: <176@sask.UUCP>
NMessage-ID: &lt;176@sask.UUCP&gt;
NDate: Mon, 3 Jan 83 00:59:15 MST
N
NThis really is a test. If anyone out there more than 6
@ -1492,8 +1493,8 @@ RFC 1036 Standard for USENET Messages December 1987
where 1234 is the length of the message in bytes. Each such line is
followed by a message containing the given number of bytes. (The
newline at the end of each line of the message is counted as one
byte, for purposes of this count, even if it is stored as <CARRIAGE
RETURN><LINE FEED>.) For example, a batch of message might look
byte, for purposes of this count, even if it is stored as &lt;CARRIAGE
RETURN&gt;&lt;LINE FEED&gt;.) For example, a batch of message might look
like this:
@ -1501,7 +1502,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 17]
Horton &amp; Adams [Page 17]
RFC 1036 Standard for USENET Messages December 1987
@ -1511,7 +1512,7 @@ RFC 1036 Standard for USENET Messages December 1987
Path: cbosgd!mhuxj!mhuxt!eagle!jerry
Newsgroups: news.announce
Subject: Usenet Etiquette -- Please Read
Message-ID: <642@eagle.ATT.COM>
Message-ID: &lt;642@eagle.ATT.COM&gt;
Date: Fri, 19 Nov 82 16:14:55 EST
Approved: mark@cbosgd.ATT.COM
@ -1521,7 +1522,7 @@ RFC 1036 Standard for USENET Messages December 1987
Path: cbosgd!mhuxj!mhuxt!eagle!jerry
Newsgroups: news.announce
Subject: Notes on Etiquette message
Message-ID: <643@eagle.ATT.COM>
Message-ID: &lt;643@eagle.ATT.COM&gt;
Date: Fri, 19 Nov 82 17:24:12 EST
Approved: mark@cbosgd.ATT.COM
@ -1557,7 +1558,7 @@ RFC 1036 Standard for USENET Messages December 1987
Horton & Adams [Page 18]
Horton &amp; Adams [Page 18]
RFC 1036 Standard for USENET Messages December 1987
@ -1607,15 +1608,15 @@ RFC 1036 Standard for USENET Messages December 1987
Notes
<1> UNIX is a registered trademark of AT&T.
<1> UNIX is a registered trademark of AT&amp;T.
Horton & Adams [Page 19]
Horton &amp; Adams [Page 19]
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

21
html/ftsc/fsc-0062.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>A Proposed Nodelist flag indicating Online Times of a Node.</TITLE>
</HEAD>
@ -243,7 +244,7 @@ Status of this document:
/* TIMEFLAG.C
Calculates FSC-0062 time flag requirement from user input */
#include <stdio.h>
#include &lt;stdio.h&gt;
char *onlineflag(char *on, char *off, int utc_diff);
@ -258,7 +259,7 @@ void main()
printf("\nSpecify the difference between your local time zone in winter\n"
"time and UTC (e.g. if your time zone is 6 hours behind UTC,\n"
"enter 6): ");
scanf("%d", &utc_diff);
scanf("%d", &amp;utc_diff);
printf("\nYour online time flag is %s\n\n",
onlineflag(on, off, utc_diff));
}
@ -268,10 +269,10 @@ char *onlineflag(char *ontime, char *offtime, int utcdiff)
int onhour, onmin, offhour, offmin;
static char flag[4]="T ";
sscanf(ontime, "%d:%d", &onhour, &onmin);
sscanf(offtime, "%d:%d", &offhour, &offmin);
sscanf(ontime, "%d:%d", &amp;onhour, &amp;onmin);
sscanf(offtime, "%d:%d", &amp;offhour, &amp;offmin);
if(onmin>30) ++onhour;
if(onmin&gt;30) ++onhour;
--offhour; /* to correct for daylight saving time */
onhour = (onhour+24+utcdiff) % 24;
offhour = (offhour+24+utcdiff) % 24;
@ -279,8 +280,8 @@ char *onlineflag(char *ontime, char *offtime, int utcdiff)
flag[1]='A'+onhour;
flag[2]='A'+offhour;
if(onmin>0 && onmin<31) flag[1] += 'a'-'A';
if(offmin>29) flag[2] += 'a'-'A';
if(onmin&gt;0 &amp;&amp; onmin&lt;31) flag[1] += 'a'-'A';
if(offmin&gt;29) flag[2] += 'a'-'A';
return flag;
}
@ -313,12 +314,12 @@ struct TIMES *interpret_flag(char *timeflag)
times.off_min=0;
times.on_hour=timeflag[1]-'A';
if(times.on_hour>23) {
if(times.on_hour&gt;23) {
times.on_hour -= 'a'-'A';
times.on_min=30;
}
times.off_hour=timeflag[2]-'A';
if(times.off_hour>23) {
if(times.off_hour&gt;23) {
times.off_hour -= 'a'-'A';
times.off_min=30;
}
@ -356,7 +357,7 @@ struct TIMES *interpret_flag(char *timeflag)
End of document.
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

17
html/ftsc/fsc-0070.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Improving FidoNet/UseNet gating and Dupe Checking.</TITLE>
</HEAD>
@ -42,7 +43,7 @@ Revision: 002
both worlds, so that we can improve the reliability of Usenet/Fidonet
gateways.
In this document "^" means <control-A> (character 01h).
In this document "^" means &lt;control-A&gt; (character 01h).
History
@ -66,11 +67,11 @@ Revision: 002
in Fidonet messages. Of course, the use of the RFCID kludge doesn't replace
the standard fts-0009 Message-ID:.
(Usenet) Message-ID: <92_feb_10_19192012901@prep.ai.mit.edu>
(Usenet) Message-ID: &lt;92_feb_10_19192012901@prep.ai.mit.edu&gt;
to (Fido) ^MSGID: 2:300/400.5 6789fedc
^RFCID: 92_feb_10_19192012901@prep.ai.mit.edu
Note ^RFCID does not include the Message-ID enclosing "<" and ">".
Note ^RFCID does not include the Message-ID enclosing "&lt;" and "&gt;".
Then if a gateway finds a ^RFCID line in a Fido message, it will use it in
the Usenet message ID, instead of converting the ^MSGID.
@ -101,21 +102,21 @@ Revision: 002
Some examples:
(Fido) ^MSGID: 2:300/400 12345AbC
to (Usenet) Message-ID: <2-300-400-12345AbC@fidonet.org>
to (Usenet) Message-ID: &lt;2-300-400-12345AbC@fidonet.org&gt;
(Fido) ^MSGID: 15:300/400.50@somenet abcd6789
to (Usenet) Message-ID: <15-300-400-50-somenet-abcd6789@fidonet.org>
to (Usenet) Message-ID: &lt;15-300-400-50-somenet-abcd6789@fidonet.org&gt;
(Fido) ^MSGID: Internet.Domain.org aBcD1234
to (Usenet) Message-ID: <Internet-Domain-org-aBcD1234@fidonet.org>
to (Usenet) Message-ID: &lt;Internet-Domain-org-aBcD1234@fidonet.org&gt;
(Fido) ^MSGID: "LZKkoe$1982 98a" 45678bcd
to (Usenet) Message-ID: <-LZKkoe-1982-98a--45678bcd@fidonet.org>
to (Usenet) Message-ID: &lt;-LZKkoe-1982-98a--45678bcd@fidonet.org&gt;
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

243
html/ftsc/fsc-0072.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>The HYDRA file transfer protocol.</TITLE>
</HEAD>
@ -203,7 +204,7 @@ Status of this document:
In formulas, "AND" means bitwise AND, "XOR" means bitwise Exclusive
OR, "NOT" is ones complement (i.e. all zeros become ones, all ones
become zeros). The ">>" is a shift operation to the right, "R >> 3"
become zeros). The "&gt;&gt;" is a shift operation to the right, "R &gt;&gt; 3"
means shift R three bits to the right.
@ -302,18 +303,18 @@ TXPKT (Sender)
| +-+----------------------------+--------------------------+----------+
| |3|else (no spc.pkt, 8bit link)|format = BINPKT |Format |
+--------+-+----------------------------+--------------------------+----------+
|Coding |1|escape all control chars & |format = UUEPKT |Format |
|Coding |1|escape all control chars &amp; |format = UUEPKT |Format |
| | |UUENCODED packets allowed | | |
| +-+----------------------------+--------------------------+----------+
| |2|ASCII packets allowed |format = ASCPKT |Format |
| +-+----------------------------+--------------------------+----------+
| |3|7 bit link & |format = HEXPKT |Format |
| | |escape all control chars & | | |
| |3|7 bit link &amp; |format = HEXPKT |Format |
| | |escape all control chars &amp; | | |
| | |UUE/ASC pkts not allowed | | |
+--------+-+----------------------------+--------------------------+----------+
|Format | |Append format byte to data|CRC |
+--------+-+----------------------------+--------------------------+----------+
|CRC |1|format != HEXPKT & |Calc CRC-32 (data,pkttype)|Encode |
|CRC |1|format != HEXPKT &amp; |Calc CRC-32 (data,pkttype)|Encode |
| | |CRC-32 allowed |Append one's complement of| |
| | | |CRC to data, lowbyte first| |
| +-+----------------------------+--------------------------+----------+
@ -343,7 +344,7 @@ TXPKT (Sender)
| | |Transmit encoded buffer | |
| | |Transmit H_DLE,pktend byte| |
+--------+-+----------------------------+--------------------------+----------+
|Suffix |1|pkttype != DATA & |Transmit CR,LF (ASC 13,10)|Done |
|Suffix |1|pkttype != DATA &amp; |Transmit CR,LF (ASC 13,10)|Done |
| | |pktformat != BINPKT | | |
| +-+----------------------------+--------------------------+----------+
| |2|else (pkttype == DATA or | |Done |
@ -378,19 +379,19 @@ RXPKT (Receiver)
+--------+-+----------------------------+--------------------------+----------+
|Process |1|c == H_DLE |increment rxdle |DLE |
| +-+----------------------------+--------------------------+----------+
| |2|Escape XON/XOFF & |Eat these |NextByte |
| |2|Escape XON/XOFF &amp; |Eat these |NextByte |
| | |n == XON or n == XOFF | | |
| +-+----------------------------+--------------------------+----------+
| |3|Escape all control chars & |Eat these |NextByte |
| | |n < 32 or n == 127 | | |
| |3|Escape all control chars &amp; |Eat these |NextByte |
| | |n &lt; 32 or n == 127 | | |
| +-+----------------------------+--------------------------+----------+
| |4|rxdle > 0 | |Escape |
| |4|rxdle &gt; 0 | |Escape |
| +-+----------------------------+--------------------------+----------+
| |5|else (no eating or escaping)| |Store |
+--------+-+----------------------------+--------------------------+----------+
|DLE |1|rxdle == 5 |Report remote wants abort |Abort |
| +-+----------------------------+--------------------------+----------+
| |2|else (rxdle < 5) | |NextByte |
| |2|else (rxdle &lt; 5) | |NextByte |
+--------+-+----------------------------+--------------------------+----------+
|Escape |1|c == PKTEND | |PktEnd |
| +-+----------------------------+--------------------------+----------+
@ -407,9 +408,9 @@ RXPKT (Receiver)
+--------+-+----------------------------+--------------------------+----------+
|Store |1|format == 0 |Garbage |NextByte |
| +-+----------------------------+--------------------------+----------+
| |2|pktlen >= maximum |Pkt too long / lost PKTEND|Reset |
| |2|pktlen &gt;= maximum |Pkt too long / lost PKTEND|Reset |
| +-+----------------------------+--------------------------+----------+
| |3|else (fmt > 0 & len < max) |Append c to databuffer |NextByte |
| |3|else (fmt &gt; 0 &amp; len &lt; max) |Append c to databuffer |NextByte |
| | | |increment pktlen | |
+--------+-+----------------------------+--------------------------+----------+
|PktStart| |rxdle = 0 |NextByte |
@ -429,7 +430,7 @@ RXPKT (Receiver)
| +-+----------------------------+--------------------------+----------+
| |2|else (errors in decoding) |Bad encoding, ignore pkt |Reset |
+--------+-+----------------------------+--------------------------+----------+
|CalcCRC |1|format != HEXPKT & |Calc CRC-32 over databuf |CheckCRC |
|CalcCRC |1|format != HEXPKT &amp; |Calc CRC-32 over databuf |CheckCRC |
| | |CRC-32 allowed |ok = (crc == 0xdebb20e3) | |
| | | |pktlen = pktlen - 4 | |
| +-+----------------------------+--------------------------+----------+
@ -472,15 +473,15 @@ BINPKT Escaping
|Escape |1|n == H_DLE |Output H_DLE |Output |
| | | |c = c XOR 0x40 | |
| +-+----------------------------+--------------------------+----------+
| |2|Escape XON/XOFF & |Output H_DLE |Output |
| |2|Escape XON/XOFF &amp; |Output H_DLE |Output |
| | |n == XON or n == XOFF |c = c XOR 0x40 | |
| +-+----------------------------+--------------------------+----------+
| |3|Escape Telenet & |Output H_DLE |Output |
| | |n == CR & |c = c XOR 0x40 | |
| |3|Escape Telenet &amp; |Output H_DLE |Output |
| | |n == CR &amp; |c = c XOR 0x40 | |
| | |txlasc == '@' | | |
| +-+----------------------------+--------------------------+----------+
| |4|Escape all control chars & |Output H_DLE |Output |
| | |n < 32 or n == 127 |c = c XOR 0x40 | |
| |4|Escape all control chars &amp; |Output H_DLE |Output |
| | |n &lt; 32 or n == 127 |c = c XOR 0x40 | |
| +-+----------------------------+--------------------------+----------+
| |5|else (any other character) | |Output |
+--------+-+----------------------------+--------------------------+----------+
@ -535,7 +536,7 @@ HEXPKT Encoding/Escaping
| | | |Output hexdigit(c bit 4-7)| |
| | | |Output hexdigit(c bit 0-3)| |
| +-+----------------------------+--------------------------+----------+
| |3|c < 32 or c == 127 |Output H_DLE | |
| |3|c &lt; 32 or c == 127 |Output H_DLE | |
| | | |Output (c XOR 0x40) | |
| +-+----------------------------+--------------------------+----------+
| |4|c == \ (backslash) |Output \ (backslash) | |
@ -565,7 +566,7 @@ HEXPKT Decoding
+--------+-+----------------------------+--------------------------+----------+
|NextHex |1|No more bytes to process |Premature end of data |Error |
| +-+----------------------------+--------------------------+----------+
| |2|c == lowercase hexdigit |Output (1st << 4 OR 2nd) |NextByte |
| |2|c == lowercase hexdigit |Output (1st &lt;&lt; 4 OR 2nd) |NextByte |
| +-+----------------------------+--------------------------+----------+
| |3|else (all other characters) |Invalid character |Error |
+--------+-+----------------------------+--------------------------+----------+
@ -604,16 +605,16 @@ ASCPKT Encoding/Escaping
+--------+-+----------------------------+--------------------------+----------+
|NextByte|1|No more bytes to process | |Flush |
| +-+----------------------------+--------------------------+----------+
| |2|else (more bytes to process)|n = n OR (c << bitshift) |Shift |
| | | |BINPKT escape (n & 0x7f) | |
| | | |n = n >> 7 | |
| |2|else (more bytes to process)|n = n OR (c &lt;&lt; bitshift) |Shift |
| | | |BINPKT escape (n &amp; 0x7f) | |
| | | |n = n &gt;&gt; 7 | |
| | | |increment bitshift | |
+--------+-+----------------------------+--------------------------+----------+
|Shift |1|bitshift == 7 |BINPKT escape (n & 0x7f) |Reset |
|Shift |1|bitshift == 7 |BINPKT escape (n &amp; 0x7f) |Reset |
| +-+----------------------------+--------------------------+----------+
| |2|else (bitshift < 7) | |NextByte |
| |2|else (bitshift &lt; 7) | |NextByte |
+--------+-+----------------------------+--------------------------+----------+
|Flush |1|bitshift > 0 |BINPKT escape (n & 0x7f) |Done |
|Flush |1|bitshift &gt; 0 |BINPKT escape (n &amp; 0x7f) |Done |
| +-+----------------------------+--------------------------+----------+
| |2|else (bitshift == 0) | |Done |
+--------+-+----------------------------+--------------------------+----------+
@ -628,14 +629,14 @@ ASCPKT Decoding
|NextByte|1|No more bytes to process | |Done OK |
| +-+----------------------------+--------------------------+----------+
| |2|else (more bytes to process)|c = c AND 0x7f |Shift |
| | | |n = n OR (c << bitshift) | |
| | | |n = n OR (c &lt;&lt; bitshift) | |
| | | |bitshift = bitshift + 7 | |
+--------+-+----------------------------+--------------------------+----------+
|Shift |1|bitshift >= 8 |Output (n AND 0xff) |NextByte |
| | | |n = n >> 8 | |
|Shift |1|bitshift &gt;= 8 |Output (n AND 0xff) |NextByte |
| | | |n = n &gt;&gt; 8 | |
| | | |bitshift = bitshift - 8 | |
| +-+----------------------------+--------------------------+----------+
| |2|else (bitshift < 8) | |NextByte |
| |2|else (bitshift &lt; 8) | |NextByte |
+--------+-+----------------------------+--------------------------+----------+
@ -669,20 +670,20 @@ UUEPKT Encoding
+--------+-+----------------------------+--------------------------+----------+
|NextByte|1|Less than three bytes left | |Flush |
| +-+----------------------------+--------------------------+----------+
| |2|else (three or more left) |UUE(in[0]>>2) | |
| | | |UUE(in[0]<<4 OR in[1]>>4) | |
| | | |UUE(in[1]<<2 OR in[2]>>6) | |
| |2|else (three or more left) |UUE(in[0]&gt;&gt;2) | |
| | | |UUE(in[0]&lt;&lt;4 OR in[1]&gt;&gt;4) | |
| | | |UUE(in[1]&lt;&lt;2 OR in[2]&gt;&gt;6) | |
| | | |UUE(in[2]) | |
| | | |(UUE: (c AND 0x3f) + '!') | |
+--------+-+----------------------------+--------------------------+----------+
|Flush |1|No more bytes left | |Done |
| +-+----------------------------+--------------------------+----------+
| |2|One byte left |UUE(in[0]>>2) |Done |
| | | |UUE(in[0]<<4) | |
| |2|One byte left |UUE(in[0]&gt;&gt;2) |Done |
| | | |UUE(in[0]&lt;&lt;4) | |
| +-+----------------------------+--------------------------+----------+
| |3|Two bytes left |UUE(in[0]>>2) |Done |
| | | |UUE(in[0]<<4 OR in[1]>>4) | |
| | | |UUE(in[1]<<2) | |
| |3|Two bytes left |UUE(in[0]&gt;&gt;2) |Done |
| | | |UUE(in[0]&lt;&lt;4 OR in[1]&gt;&gt;4) | |
| | | |UUE(in[1]&lt;&lt;2) | |
+--------+-+----------------------------+--------------------------+----------+
UUEPKT Decoding
@ -691,9 +692,9 @@ UUEPKT Decoding
+--------+-+----------------------------+--------------------------+----------+
|NextByte|1|Less than four bytes left | |Flush |
| +-+----------------------------+--------------------------+----------+
| |2|else (four or more left) & |UD(i[0])<<2 OR UD(i[1])>>4| |
| | |(c AND 0x7f) is in UUE range|UD(i[1])<<4 OR UD(i[2])>>2| |
| | | |UD(i[2])<<6 OR UD(i[3]) | |
| |2|else (four or more left) &amp; |UD(i[0])&lt;&lt;2 OR UD(i[1])&gt;&gt;4| |
| | |(c AND 0x7f) is in UUE range|UD(i[1])&lt;&lt;4 OR UD(i[2])&gt;&gt;2| |
| | | |UD(i[2])&lt;&lt;6 OR UD(i[3]) | |
| | | |(UD: (c - '!') AND 0x3f) | |
| +-+----------------------------+--------------------------+----------+
| |3|else (all other characters) |Invalid character(s) |Error |
@ -701,11 +702,11 @@ UUEPKT Decoding
|Flush |1|No bytes left or | |Done OK |
| | |Less than two bytes left | | |
| +-+----------------------------+--------------------------+----------+
| |2|Two bytes left & |UD(i[0])<<2 OR UD(i[1])>>4|Done OK |
| |2|Two bytes left &amp; |UD(i[0])&lt;&lt;2 OR UD(i[1])&gt;&gt;4|Done OK |
| | |(c AND 0x7f) is in UUE range| | |
| +-+----------------------------+--------------------------+----------+
| |3|Three bytes left & |UD(i[0])<<2 OR UD(i[1])>>4|Done OK |
| | |(c AND 0x7f) is in UUE range|UD(i[1])<<4 OR UD(i[2])>>2| |
| |3|Three bytes left &amp; |UD(i[0])&lt;&lt;2 OR UD(i[1])&gt;&gt;4|Done OK |
| | |(c AND 0x7f) is in UUE range|UD(i[1])&lt;&lt;4 OR UD(i[2])&gt;&gt;2| |
| +-+----------------------------+--------------------------+----------+
| |4|else (all other characters) |Invalid character(s) |Error |
+--------+-+----------------------------+--------------------------+----------+
@ -768,7 +769,7 @@ UUEPKT Decoding
document revision date, product name, product revision number, and
optionally the product serial number. The format of the string is:
<RevDate><ProductName><,><ProductRevision>[<,><ProductSerial#>]
&lt;RevDate&gt;&lt;ProductName&gt;&lt;,&gt;&lt;ProductRevision&gt;[&lt;,&gt;&lt;ProductSerial#&gt;]
RevDate is the UNIX timestamp (the hour, minute, and second portion
is assumed to be zero), in hexadecimal notation, of the HYDRA
@ -780,8 +781,8 @@ UUEPKT Decoding
Capability flags
XON Escape <XON> and <XOFF> characters.
TLN Escape the <CR>@<CR> sequence (Telenet escape).
XON Escape &lt;XON&gt; and &lt;XOFF&gt; characters.
TLN Escape the &lt;CR&gt;@&lt;CR&gt; sequence (Telenet escape).
CTL Escape ASCII characters 0-31 and 127.
HIC Escape above three with high bit set.
HI8 Escape ASCII characters 128-255 and strip the high bit.
@ -934,7 +935,7 @@ UUEPKT Decoding
options" of the receiver contains FPT. If the real filename field
contains a path, it may include any ASCII character in the range 32
(0x20) through 255 (0xff) with \ characters translated to /. A drive
specifier may be present in the <Drive>: (e.g. c:) format. If both
specifier may be present in the &lt;Drive&gt;: (e.g. c:) format. If both
the short and real filename fields are present, they are separated
by a NUL character. There is never more than one NUL character
terminating the packet.
@ -961,7 +962,7 @@ UUEPKT Decoding
+------+----------------------------------------------+
|Offset|Description |
+------+----------------------------------------------+
| >=0 |Seek to specified offset and start sending (1)|
| &gt;=0 |Seek to specified offset and start sending (1)|
| -1 |Already have file (2)|
| -2 |Send file during another batch (not now) |
+------+----------------------------------------------+
@ -1105,7 +1106,7 @@ UUEPKT Decoding
+------+-------------------------------------------+
|Offset|Description |
+------+-------------------------------------------+
| >=0 |Seek to specified offset and resume sending|
| &gt;=0 |Seek to specified offset and resume sending|
| -2 |Send file during another batch (not now) |
+------+-------------------------------------------+
@ -1156,7 +1157,7 @@ UUEPKT Decoding
+------+----------------------------------------+
|Offset|Description |
+------+----------------------------------------+
| >=0 |Final offset in file (size of file) |
| &gt;=0 |Final offset in file (size of file) |
| -2 |Send file during another batch (not now)|
+------+----------------------------------------+
@ -1301,19 +1302,19 @@ DEVICE sender (devtxstate HTD_...)
|Begin | |devtxid = 0 |DONE |
| | |reset devtxtimer | |
+--------+-+----------------------------+--------------------------+----------+
|DONE |1|wish to send device data & |increase devtxid |DATA |
|DONE |1|wish to send device data &amp; |increase devtxid |DATA |
| | |other side allows DEV pkts |devtxretries = 0 | |
| | | |reset devtxtimer | |
| +-+----------------------------+--------------------------+----------+
| |2|wish to send device data & |Tell calling function | |
| |2|wish to send device data &amp; |Tell calling function | |
| | |other doesn't allow DEV pkts|it's not on... | |
+--------+-+----------------------------+--------------------------+----------+
|DATA |1|devtxretries == 10 |Report too many errors |Abort |
| +-+----------------------------+--------------------------+----------+
| |2|else (devtxretries < 10) |txpkt DEVDATA(id,dev,data)|DACK |
| |2|else (devtxretries &lt; 10) |txpkt DEVDATA(id,dev,data)|DACK |
| | | |devtxtimer = timeout | |
+--------+-+----------------------------+--------------------------+----------+
|DACK |1|rxpkt DACK & |reset devtxtimer |DONE |
|DACK |1|rxpkt DACK &amp; |reset devtxtimer |DONE |
| | |DACK(id) == devtxid | | |
| +-+----------------------------+--------------------------+----------+
| |2|devtxtimer expired |Report devtx timeout |DATA |
@ -1336,7 +1337,7 @@ DEVICE RECEIVER
| +-+----------------------------+--------------------------+----------+
| |2|DEVDATA(dev) == CON |Output to user console |DONE |
| +-+----------------------------+--------------------------+----------+
| |3|DEVDATA(dev) == known&ok |Call processing routine |DONE |
| |3|DEVDATA(dev) == known&amp;ok |Call processing routine |DONE |
| +-+----------------------------+--------------------------+----------+
| |4|else (unknown/not-ok device)|One-way into bitbucket |DONE |
+--------+-+----------------------------+--------------------------+----------+
@ -1363,7 +1364,7 @@ DEVICE RECEIVER
| 300 bps| 256 bytes | 256 bytes |
| 1200 bps| 512 bytes | 256 bytes |
| 2400 bps| 1024 bytes | 512 bytes |
|>2400 bps| 2048 bytes | 512 bytes |
|&gt;2400 bps| 2048 bytes | 512 bytes |
+---------+------------------+-------------------+
The blocksize is initialized to the starting blocksize when a session
@ -1405,7 +1406,7 @@ DEVICE RECEIVER
| 300 bps|60 seconds|30 seconds|
| 1200 bps|34 seconds|17 seconds|
| 2400 bps|17 seconds| 8 seconds|
|>2400 bps|10 seconds| 5 seconds|
|&gt;2400 bps|10 seconds| 5 seconds|
+---------+----------+----------+
If the output buffer is empty, the timeout value is halved. In
@ -1452,7 +1453,7 @@ GENERAL sender (txstate HTX_...)
+--------+-+----------------------------+--------------------------+----------+
|START |1|txretries == 10 |Report too many errors |Abort |
| +-+----------------------------+--------------------------+----------+
| |2|else (txretries < 10) |txstr AutoStart |SWAIT |
| |2|else (txretries &lt; 10) |txstr AutoStart |SWAIT |
| | | |txpkt START | |
| | | |txtimer = 5 | |
+--------+-+----------------------------+--------------------------+----------+
@ -1465,7 +1466,7 @@ GENERAL sender (txstate HTX_...)
+--------+-+----------------------------+--------------------------+----------+
|INIT |1|txretries == 10 |Report too many errors |Abort |
| +-+----------------------------+--------------------------+----------+
| |2|else (txretries < 10) |txpkt INIT(linkinfo) |INITACK |
| |2|else (txretries &lt; 10) |txpkt INIT(linkinfo) |INITACK |
| | | |txtimer = timeout/2 | |
+--------+-+----------------------------+--------------------------+----------+
|INITACK |1|rxpkt INITACK |txretries = 0 |RINIT |
@ -1490,64 +1491,64 @@ GENERAL sender (txstate HTX_...)
+--------+-+----------------------------+--------------------------+----------+
|FINFO |1|txretries == 10 |Report too many errors |Abort |
| +-+----------------------------+--------------------------+----------+
| |2|txretries > 0 |txpkt FINFO(fileinfo) |FINFOACK |
| |2|txretries &gt; 0 |txpkt FINFO(fileinfo) |FINFOACK |
| | | |txtimer = timeout/2 | |
| +-+----------------------------+--------------------------+----------+
| |3|else (txretries == 0) |txpkt FINFO(fileinfo) |FINFOACK |
| | | |txtimer = timeout | |
+--------+-+----------------------------+--------------------------+----------+
|FINFOACK|1|NULL fname (end of batch) & |txtimer = idletimeout |REND |
|FINFOACK|1|NULL fname (end of batch) &amp; |txtimer = idletimeout |REND |
| | |rxpkt FINFOACK |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
| |2|rxpkt FINFOACK & |txpos = FINFOACK(pos) |DATA |
| | |FINFOACK(pos) >= 0 |txretries = 0 | |
| |2|rxpkt FINFOACK &amp; |txpos = FINFOACK(pos) |DATA |
| | |FINFOACK(pos) &gt;= 0 |txretries = 0 | |
| | | |txlastack = 0 | |
| | | |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
| |3|rxpkt FINFOACK & |They already have file |NextFile |
| |3|rxpkt FINFOACK &amp; |They already have file |NextFile |
| | |FINFOACK(pos) == -1) |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
| |4|rxpkt FINFOACK & |Skip this file for now |NextFile |
| |4|rxpkt FINFOACK &amp; |Skip this file for now |NextFile |
| | |FINFOACK(pos) == -2) |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
| |5|txtimer expired |Report tx timeout |FINFO |
| | | |inrease txretries | |
+--------+-+----------------------------+--------------------------+----------+
|DATA |1|rxstate != Done & |txtimer = idletimeout |XWAIT |
|DATA |1|rxstate != Done &amp; |txtimer = idletimeout |XWAIT |
| | |hdxlink == True | | |
| +-+----------------------------+--------------------------+----------+
| |2|rxpkt DATAACK & |txlastack = DATAACK(pos) | |
| | |DATAACK(pos) > txlastack | | |
| |2|rxpkt DATAACK &amp; |txlastack = DATAACK(pos) | |
| | |DATAACK(pos) &gt; txlastack | | |
| +-+----------------------------+--------------------------+----------+
| |3|rxpkt RPOS & |Skip this file for now |SkipFile |
| | |RPOS(pos) < 0 |braintimer = 120 | |
| |3|rxpkt RPOS &amp; |Skip this file for now |SkipFile |
| | |RPOS(pos) &lt; 0 |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
| |4|rxpkt RPOS & |Report too many errors |Abort |
| | |RPOS(id) == txsyncid & | | |
| |4|rxpkt RPOS &amp; |Report too many errors |Abort |
| | |RPOS(id) == txsyncid &amp; | | |
| | |inc txretries == 10 | | |
| +-+----------------------------+--------------------------+----------+
| |5|rxpkt RPOS & |txpos = RPOS(pos) | |
| | |RPOS(id) != txsyncid & |txsyncid = RPOS(id) | |
| | |RPOS(pos) >= 0 |txretries = 1 | |
| |5|rxpkt RPOS &amp; |txpos = RPOS(pos) | |
| | |RPOS(id) != txsyncid &amp; |txsyncid = RPOS(id) | |
| | |RPOS(pos) &gt;= 0 |txretries = 1 | |
| | | |blksize = RPOS(blksize) | |
| | | |goodbytes = 0 | |
| | | |inc goodneeded + 1024 | |
| | | |if (goodneeded > 8192) | |
| | | |if (goodneeded &gt; 8192) | |
| | | | goodneeded = 8192 | |
| | | |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
| |6|File seek/read error or |Skip this file for now |SkipFile |
| | |user wishes to skip file | | |
| +-+----------------------------+--------------------------+----------+
| |7|txwindow & |if (txretries > 0) |DATAACK |
| | |txpos >= txlastack+txwindow | txtimer = timeout/2 | |
| |7|txwindow &amp; |if (txretries &gt; 0) |DATAACK |
| | |txpos &gt;= txlastack+txwindow | txtimer = timeout/2 | |
| | | |else | |
| | | | txtimer = timeout | |
| +-+----------------------------+--------------------------+----------+
| |8|Enough room in output & |txpkt DATA(pos,data) | |
| |8|Enough room in output &amp; |txpkt DATA(pos,data) | |
| | |more filedata(blksize) to go|txpos += datalen | |
| | | |inc goodbytes + datalen | |
| | | |if goodbytes > goodneeded | |
| | | |if goodbytes &gt; goodneeded | |
| | | | Store txpos,blksize | |
| | | | blksize * 2 (max.2048) | |
| +-+----------------------------+--------------------------+----------+
@ -1558,9 +1559,9 @@ GENERAL sender (txstate HTX_...)
+--------+-+----------------------------+--------------------------+----------+
|DATAACK |1|txretries == 10 |Report too many errors |Abort |
| +-+----------------------------+--------------------------+----------+
| |2|rxpkt DATAACK & |txlastack = DATAACK(pos) |DATA |
| | |DATAACK(pos) > txlastack & |txretries = 0 | |
| | |txpos < DATAACK(pos) + txwin|reset txtimer | |
| |2|rxpkt DATAACK &amp; |txlastack = DATAACK(pos) |DATA |
| | |DATAACK(pos) &gt; txlastack &amp; |txretries = 0 | |
| | |txpos &lt; DATAACK(pos) + txwin|reset txtimer | |
| +-+----------------------------+--------------------------+----------+
| |3|rxpkt RPOS |Handle RPOS in state DATA | |
| | | |but stay in this state | |
@ -1570,8 +1571,8 @@ GENERAL sender (txstate HTX_...)
+--------+-+----------------------------+--------------------------+----------+
|XWAIT |1|rxstate == Done |reset txtimer |DATA |
| +-+----------------------------+--------------------------+----------+
| |2|rxpkt DATAACK & |txlastack = DATAACK(pos) | |
| | |DATAACK(pos) > txlastack | | |
| |2|rxpkt DATAACK &amp; |txlastack = DATAACK(pos) | |
| | |DATAACK(pos) &gt; txlastack | | |
| +-+----------------------------+--------------------------+----------+
| |3|rxpkt RPOS |Handle RPOS in state DATA | |
| | | |but stay in this state | |
@ -1584,7 +1585,7 @@ GENERAL sender (txstate HTX_...)
+--------+-+----------------------------+--------------------------+----------+
|EOF |1|txretries == 10 |Report too many errors |Abort |
| +-+----------------------------+--------------------------+----------+
| |2|txretries > 0 |txpkt EOF(txpos) |EOFACK |
| |2|txretries &gt; 0 |txpkt EOF(txpos) |EOFACK |
| | | |txtimer = timeout/2 | |
| +-+----------------------------+--------------------------+----------+
| |3|else (txretries == 0) |txpkt EOF(txpos) |EOFACK |
@ -1592,20 +1593,20 @@ GENERAL sender (txstate HTX_...)
+--------+-+----------------------------+--------------------------+----------+
|EOFACK |1|rxpkt EOFACK |braintimer = 120 |NextFile |
| +-+----------------------------+--------------------------+----------+
| |2|rxpkt DATAACK & |txlastack = DATAACK(pos) | |
| | |DATAACK(pos) > txlastack | | |
| |2|rxpkt DATAACK &amp; |txlastack = DATAACK(pos) | |
| | |DATAACK(pos) &gt; txlastack | | |
| +-+----------------------------+--------------------------+----------+
| |3|rxpkt RPOS & |rxpos == -2 |EOF |
| | |RPOS(pos) == -2 & | | |
| |3|rxpkt RPOS &amp; |rxpos == -2 |EOF |
| | |RPOS(pos) == -2 &amp; | | |
| | |rxpos != -2 | | |
| +-+----------------------------+--------------------------+----------+
| |4|rxpkt RPOS & |Handle as in state DATA |DATA |
| | |RPOS(pos) >= 0 | | |
| |4|rxpkt RPOS &amp; |Handle as in state DATA |DATA |
| | |RPOS(pos) &gt;= 0 | | |
| +-+----------------------------+--------------------------+----------+
| |5|txtimer expired |Report tx timeout |EOF |
| | | |increment txretries | |
+--------+-+----------------------------+--------------------------+----------+
|REND |1|rxstate == DONE & |txretries = 0 |END |
|REND |1|rxstate == DONE &amp; |txretries = 0 |END |
| | |devtxstate == DONE | | |
| +-+----------------------------+--------------------------+----------+
| |2|txtimer expired |txpkt IDLE | |
@ -1613,7 +1614,7 @@ GENERAL sender (txstate HTX_...)
+--------+-+----------------------------+--------------------------+----------+
|END |1|txretries == 10 | |Abort |
| +-+----------------------------+--------------------------+----------+
| |2|else (txretries < 10) |txpkt END (twice) |ENDACK |
| |2|else (txretries &lt; 10) |txpkt END (twice) |ENDACK |
| | | |txtimer = timeout/2 | |
+--------+-+----------------------------+--------------------------+----------+
|ENDACK |1|rxpkt END |txpkt END (thrice) |Done |
@ -1632,7 +1633,7 @@ GENERAL RECEIVER (rxstate HRX_...)
| | |lastrxdlen = startblksize | |
| | |(tx handles braintimer) | |
+--------+-+----------------------------+--------------------------+----------+
|INIT |1|rxpkt INIT & |txpkt INITACK |FINFO |
|INIT |1|rxpkt INIT &amp; |txpkt INITACK |FINFO |
| | |INIT(options) are compatible|Set options | |
| | | |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
@ -1640,22 +1641,22 @@ GENERAL RECEIVER (rxstate HRX_...)
+--------+-+----------------------------+--------------------------+----------+
|FINFO |1|rxpkt INIT (apparent dup) |txpkt INITACK | |
| +-+----------------------------+--------------------------+----------+
| |2|rxpkt FINFO & |Report end of batch | |
| |2|rxpkt FINFO &amp; |Report end of batch | |
| | |FINFO(fileinfo) == Empty |txpkt FINFOACK |DONE |
| | | |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
| |3|rxpkt FINFO & |do not want this file | |
| |3|rxpkt FINFO &amp; |do not want this file | |
| | |we already have file |txpkt FINFOACK(-1) | |
| | | |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
| |4|rxpkt FINFO & |Skip this file for now | |
| |4|rxpkt FINFO &amp; |Skip this file for now | |
| | |open/diskspace error |txpkt FINFOACK(-2) | |
| | | |braintimer = 120 | |
| +-+----------------------------+--------------------------+----------+
| |5|rxpkt FINFO & |rxpos = resume offset |ToData |
| |5|rxpkt FINFO &amp; |rxpos = resume offset |ToData |
| | |file we want to resume | | |
| +-+----------------------------+--------------------------+----------+
| |6|rxpkt FINFO & |rxpos = 0 |ToData |
| |6|rxpkt FINFO &amp; |rxpos = 0 |ToData |
| | |new file for us | | |
| +-+----------------------------+--------------------------+----------+
| |7|rxpkt EOF (apparent dup) |txpkt EOFACK | |
@ -1669,7 +1670,7 @@ GENERAL RECEIVER (rxstate HRX_...)
+--------+-+----------------------------+--------------------------+----------+
|DATA |1|rxpkt FINFO (apparent dup) |txpkt FINFOACK(rxpos) | |
| +-+----------------------------+--------------------------+----------+
| |2|rxpkt DATA & |Store data | |
| |2|rxpkt DATA &amp; |Store data | |
| | |DATA(pos) == rxpos |rxpos += datalen | |
| | | |rxretries = 0 | |
| | | |rxlastsync = rxpos | |
@ -1678,37 +1679,37 @@ GENERAL RECEIVER (rxstate HRX_...)
| | | |if (rxwindow) | |
| | | | txpkt DATAACK(rxpos) | |
| +-+----------------------------+--------------------------+----------+
| |3|rxpkt DATA & |Report bad rxpos |BadPos |
| |3|rxpkt DATA &amp; |Report bad rxpos |BadPos |
| | |DATA(pos) != rxpos | | |
| +-+----------------------------+--------------------------+----------+
| |4|rxpkt EOF & |Close file, received ok |OkEOF |
| |4|rxpkt EOF &amp; |Close file, received ok |OkEOF |
| | |EOF(pos) == rxpos | | |
| +-+----------------------------+--------------------------+----------+
| |5|rxpkt EOF & |Close, save for resume |OkEOF |
| |5|rxpkt EOF &amp; |Close, save for resume |OkEOF |
| | |EOF(pos) == -2 | | |
| +-+----------------------------+--------------------------+----------+
| |6|rxpkt EOF & |Report bad EOF |BadPos |
| |6|rxpkt EOF &amp; |Report bad EOF |BadPos |
| | |EOF(pos) != rxpos | | |
| +-+----------------------------+--------------------------+----------+
| |7|File write error or |Close, save for resume | |
| | |user wishes to skip file |rxpos = -2 | |
| +-+----------------------------+--------------------------+----------+
| |8|rxpkt IDLE & |braintimer = 120 | |
| |8|rxpkt IDLE &amp; |braintimer = 120 | |
| | |hdxlink == False | | |
+--------+-+----------------------------+--------------------------+----------+
|BadPos |1|DATA/EOF(pos) <= rxlastsync |rxretries = 0 |Timer |
|BadPos |1|DATA/EOF(pos) &lt;= rxlastsync |rxretries = 0 |Timer |
| | | |reset rxtimer | |
| | | |rxlastsync = pos | |
| +-+----------------------------+--------------------------+----------+
| |2|DATA/EOF(pos) > rxlastsync |rxlastsync = pos |Timer |
| |2|DATA/EOF(pos) &gt; rxlastsync |rxlastsync = pos |Timer |
+--------+-+----------------------------+--------------------------+----------+
|Timer |1|rxtimer expired | |HdxLink |
| +-+----------------------------+--------------------------+----------+
| |2|else (rxtimer not expired) | |DATA |
+--------+-+----------------------------+--------------------------+----------+
|HdxLink |1|rxretries > 4 & |hdxlink = True |Retries |
| | |txstate < REND & |rxretries = 0 | |
| | |originator == False & | | |
|HdxLink |1|rxretries &gt; 4 &amp; |hdxlink = True |Retries |
| | |txstate &lt; REND &amp; |rxretries = 0 | |
| | |originator == False &amp; | | |
| | |hdxlink == False | | |
| +-+----------------------------+--------------------------+----------+
| |2|else (above not the case) | |Retries |
@ -1717,7 +1718,7 @@ GENERAL RECEIVER (rxstate HRX_...)
| +-+----------------------------+--------------------------+----------+
| |2|rxretries == 1 |increase rxsyncid |RPos |
| +-+----------------------------+--------------------------+----------+
| |3|else (rxretries > 1) | |RPos |
| |3|else (rxretries &gt; 1) | |RPos |
+--------+-+----------------------------+--------------------------+----------+
|RPos | |lastrxdatalen/=2 (min.64) |DATA |
| | |txpkt RPOS (rxpos, | |
@ -1794,9 +1795,9 @@ GENERAL RECEIVER (rxstate HRX_...)
FOR (N=1 TO 8)
{
IF (CRC16 AND 1)
CRC16=(CRC16 >> 1) XOR 0x8408
CRC16=(CRC16 &gt;&gt; 1) XOR 0x8408
ELSE
CRC16=CRC16 >> 1
CRC16=CRC16 &gt;&gt; 1
}
CRC16TAB[i]=CRC16;
}
@ -1805,7 +1806,7 @@ GENERAL RECEIVER (rxstate HRX_...)
routine as follows (variable CRC stores the 16-bit CRC value/result,
C is the next 8-bit char):
CRC=CRC16TAB[(CRC XOR C) AND 0xff] XOR ((CRC>>8) AND 0x00ff)
CRC=CRC16TAB[(CRC XOR C) AND 0xff] XOR ((CRC&gt;&gt;8) AND 0x00ff)
CRC-32 error detection
@ -1835,9 +1836,9 @@ GENERAL RECEIVER (rxstate HRX_...)
FOR (N=1 TO 8)
{
IF (CRC32 AND 1)
CRC32 = (CRC32 >> 1) XOR 0xedb88320
CRC32 = (CRC32 &gt;&gt; 1) XOR 0xedb88320
ELSE
CRC32 = CRC32 >> 1
CRC32 = CRC32 &gt;&gt; 1
}
CRC32TAB[i] = CRC32;
}
@ -1846,7 +1847,7 @@ GENERAL RECEIVER (rxstate HRX_...)
routine as follows (variable CRC stores the 32-bit CRC value/result,
C is the next 8-bit character):
CRC=CRC32TAB[(CRC XOR C) AND 0xFF] XOR ((CRC>>8) AND 0x00ffffff)
CRC=CRC32TAB[(CRC XOR C) AND 0xFF] XOR ((CRC&gt;&gt;8) AND 0x00ffffff)
The authors
@ -1918,7 +1919,7 @@ GENERAL RECEIVER (rxstate HRX_...)
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fsc-0087.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>File Forwarding in Fidonet Technology Networks.</TITLE>
</HEAD>
@ -298,7 +299,7 @@
-to be continued-
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fsc-0088.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Compatibility and Link Qualifier Extensions for EMSI Sessions</TITLE>
</HEAD>
@ -319,7 +320,7 @@
Note that HXT,HRQ,HFE == HAT
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

9
html/ftsc/fsc-0091.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>ISDN nodelist flags (rev.002).</TITLE>
</HEAD>
@ -47,13 +48,13 @@ The proposed new information text in nodelist trailer is as follows:
Some to only V120L (still with 56k lines).
- Nodes in Europe currently use the ISDNA, ISDNB and ISDNC flags.
A simple translation will do the trick here.
ISDNA -> V110L
ISDNB -> V110H
ISDNC -> X75
ISDNA -&gt; V110L
ISDNB -&gt; V110H
ISDNC -&gt; X75
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

5
html/ftsc/fsc-0092.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>New control lines for forwarded messages.</TITLE>
</HEAD>
@ -207,7 +208,7 @@
@REPLY: 1:234/567 12345678
Text: Hi Joe!
JU> ...
JU&gt; ...
...
@ -236,7 +237,7 @@
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fsc-0093.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Reduced seen-by lines.</TITLE>
</HEAD>
@ -149,7 +150,7 @@
- eof -
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

7
html/ftsc/fsp-1001.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Timezone information in FTN messages.</TITLE>
</HEAD>
@ -87,9 +88,9 @@ Abstract
Messages which conform to this specification must add the kludge:
^aTZUTC: <current offset from UTC>
^aTZUTC: &lt;current offset from UTC&gt;
The offset has the format <[-]hhmm>, where hhmm is the number of
The offset has the format &lt;[-]hhmm&gt;, where hhmm is the number of
hours and minutes that local time is offset from UTC. If local time
is WEST of UTC (Greenwich), then the offset is NEGATIVE. See the
table below for typical offsets.
@ -203,7 +204,7 @@ C. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

9
html/ftsc/fsp-1002.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Numeric reply indication in FTN subject lines.</TITLE>
</HEAD>
@ -85,17 +86,17 @@ Abstract
"Re^n: ", put the string "Re: " in front of it. Don't use a
number here.
Example: "Hello world" -> "Re: Hello world"
Example: "Hello world" -&gt; "Re: Hello world"
2. If the original subject has a leading "Re: ", put the string
"Re^2: " in front of the subject.
Example: "Re: Hello world" -> "Re^2: Hello world"
Example: "Re: Hello world" -&gt; "Re^2: Hello world"
3. If the original subject has a leading "Re^n: ", increase the
number 'n' by one and modify the subject accordingly.
Example: "Re^4: Hello world" -> "Re^5: Hello world"
Example: "Re^4: Hello world" -&gt; "Re^5: Hello world"
Notes:
@ -133,7 +134,7 @@ B. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fsp-1003.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Suggested use of Nodelist Fields.</TITLE>
</HEAD>
@ -109,7 +110,7 @@ B. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

39
html/ftsc/fsp-1004.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Standard FidoNet Addressing.</TITLE>
</HEAD>
@ -87,12 +88,12 @@ Introduction
If '@DO' is missing then fidonet can be assumed.
The following are all valid examples:
1:234/5.6@fidonet (a '5D' address) => 1:234/5.6@fidonet
2:34/6.78 (a '4D' address) => 2:34/6.78@fidonet
4:610/34 (a '3D' address) => 4:610/34.0@fidonet
123/45 (a '2D' address) => 1:123/45.0@fidonet
955:95/2@othernet (another FTN) => 955:95/2.0@othernet
2:259/-1 (node application) => 2:259/-1.0@fidonet
1:234/5.6@fidonet (a '5D' address) =&gt; 1:234/5.6@fidonet
2:34/6.78 (a '4D' address) =&gt; 2:34/6.78@fidonet
4:610/34 (a '3D' address) =&gt; 4:610/34.0@fidonet
123/45 (a '2D' address) =&gt; 1:123/45.0@fidonet
955:95/2@othernet (another FTN) =&gt; 955:95/2.0@othernet
2:259/-1 (node application) =&gt; 2:259/-1.0@fidonet
The limits on each various part of the address are a result of
fts-0005 (zone, net, node, point), fsc-0045 (domain) and Policy 4
@ -103,7 +104,7 @@ Introduction
------------------------------
An internet user can send email/netmail to a fidonet user via one of
the fidonet->internet gateway systems (it's out-with the scope of
the fidonet-&gt;internet gateway systems (it's out-with the scope of
this document to describe the semantics of posting). The internet
user would send an email to a Fidonet user by using an email address
of the following syntax:
@ -134,19 +135,19 @@ Introduction
The following are all valid examples (assuming 'fidonet.org' is an
internet gateway):
joe.bloggs@p6.f5.n234.z1.fidonet.org => 1:234/5.6@fidonet
harry.cat@p78.f6.n34.z2.fidonet.org => 2:34/6.78@fidonet
i.be.jolly@f34.n610.z4.fidonet.org => 4:610/34.0@fidonet
joe.bloggs@p6.f5.n234.z1.fidonet.org =&gt; 1:234/5.6@fidonet
harry.cat@p78.f6.n34.z2.fidonet.org =&gt; 2:34/6.78@fidonet
i.be.jolly@f34.n610.z4.fidonet.org =&gt; 4:610/34.0@fidonet
and if 'foo.bar.org.uk' is a gateway for 'othernet':
louise.hat@f2.n95.z955.foo.bar.org.uk => 955:95/2.0@othernet
louise.hat@f2.n95.z955.foo.bar.org.uk =&gt; 955:95/2.0@othernet
3. Routing Address Syntax
-------------------------
The two previous address types (Fidonet and Internet->Fidonet
The two previous address types (Fidonet and Internet-&gt;Fidonet
gateway) are common practice, this however is a suggested standard
of addressing for routing tables. The routing address has the
following syntax:
@ -196,12 +197,12 @@ Introduction
Example fidonet addresses converted to routing addresses:
fidonet:2:25:259:0:7:0 => 2:259/7.0@fidonet, region 25, hub 0
fidonet:1:1:1:0:23:0 => 1:1/23.0@fidonet, zone 1 net
:955:9551:95:300:45:0 => 955:95/45.0, region 9551, hub 300
fidonet:2:25:25:0:0:0 => 2:25/0.0@fidonet, R25C
cnet:12:34:341:100:1:7 => 12:341/1.7@cnet, region 34, hub 100
:2:25:259:300:300:0 => 2:259/300.0, region 25, hub 300
fidonet:2:25:259:0:7:0 =&gt; 2:259/7.0@fidonet, region 25, hub 0
fidonet:1:1:1:0:23:0 =&gt; 1:1/23.0@fidonet, zone 1 net
:955:9551:95:300:45:0 =&gt; 955:95/45.0, region 9551, hub 300
fidonet:2:25:25:0:0:0 =&gt; 2:25/0.0@fidonet, R25C
cnet:12:34:341:100:1:7 =&gt; 12:341/1.7@cnet, region 34, hub 100
:2:25:259:300:300:0 =&gt; 2:259/300.0, region 25, hub 300
Example POSIX regular expression patterns on routing addresses:
@ -250,7 +251,7 @@ B. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

109
html/ftsc/fsp-1005.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Zone 2 nodelist flags.</TITLE>
</HEAD>
@ -48,11 +49,11 @@ Contents:
V32B or V42B is not more enforced. Currently new flags needed for
IP-connectivity are under test in zone 2 (only internally), e.g.
-> VM VModem, default port 3141, dummy country code 000-
-> IFC IFCico, default port 60179, dummy country code 000-
-> BND BinkP, default port 24544, dummy country code 000-
-> IP general IP connectivity, dummy country code 000-
-> TELN Telnet dummy country code 000-
-&gt; VM VModem, default port 3141, dummy country code 000-
-&gt; IFC IFCico, default port 60179, dummy country code 000-
-&gt; BND BinkP, default port 24544, dummy country code 000-
-&gt; IP general IP connectivity, dummy country code 000-
-&gt; TELN Telnet dummy country code 000-
2. FTS-0005 flags
@ -64,7 +65,7 @@ Contents:
LO Listed Only, node accepts calls only from listed
node numbers in the current FidoNet nodelist
-> V21 ITU-T V21 300 bps full duplex (obsolete)
-&gt; V21 ITU-T V21 300 bps full duplex (obsolete)
V22 ITU-T V22 1200 bps full duplex (obsolescent)
| In zone 2 the value 1200 in the baud rate field implies V22. Only
@ -74,7 +75,7 @@ Contents:
| FTS-0005 version.
V29 ITU-T V29 9600 bps half duplex (obsolescent)
-> V33 ITU-T V33 14400 bps half duplex (obsolete)
-&gt; V33 ITU-T V33 14400 bps half duplex (obsolete)
V33 cannot be used in connecting FidoNet nodes over public dial-up
lines and is most probably a historical error in FTS-0005. A very
@ -96,12 +97,12 @@ Contents:
H96 Hayes V9600
HST USR Courier HST up to 9600 (implies MNP)
H14 USR Courier HST up to 14400 (implies HST)
-> H16 USR Courier HST up to 16800 (implies H14 and V42b)
-&gt; H16 USR Courier HST up to 16800 (implies H14 and V42b)
MAX Microcom AX/96xx series (almost obsolete)
PEP Packet Ensemble Protocol
CSP Compucom Speedmodem
-> ZYX Zyxel series 16800 bps (implies V32b and V42b)
-> V32T V.32 Terbo 19200 bps (implies V32b)
-&gt; ZYX Zyxel series 16800 bps (implies V32b and V42b)
-&gt; V32T V.32 Terbo 19200 bps (implies V32b)
VFC V.Fast Class 28800 bps (should imply V32b and V42b)
If a flag directly or indirectly implies other flags, then these
@ -163,7 +164,7 @@ Contents:
#01 Zone 5 mail hour (01:00 - 02:00 UTC) w/ Bell 212A
#02 Zone 2 mail hour (02:30 - 03:30 UTC) w/ Bell 212A
-> #08 Zone 4 mail hour (08:00 - 09:00 UTC) w/ Bell 212A
-&gt; #08 Zone 4 mail hour (08:00 - 09:00 UTC) w/ Bell 212A
#09 Zone 1 mail hour (09:00 - 10:00 UTC) w/ Bell 212A
#18 Zone 3 mail hour (18:00 - 19:00 UTC) w/ Bell 212A
#20 Zone 6 mail hour (20:00 - 21:00 UTC) w/ Bell 212A
@ -235,7 +236,7 @@ Contents:
International Coordinator or the FTSC (i.e. user flags only used
experimentally or locally) are separated by a new pseudo flag U.
-> U pseudo flag to the left of at least one user flag
-&gt; U pseudo flag to the left of at least one user flag
All flags following this pseudo flag U are user flags, all flags
before this pseudo flag are "real" flags specified in FTS-0005 or
@ -252,19 +253,19 @@ Contents:
In zone 2 user flags have to be approved by the Zone Coordinator.
Currently the following zone 2 user flags exist:
-> V110L ITU-T V.110 19k2 async 'Low' (former ISDNA)
-> V110H ITU-T V.110 38k4 async 'High' (former ISDNB)
-> V120L ITU-T V.120 56k6 async, N1 = 259, W = 7, modulo 8
-> V120H ITU-T V.120 64k async, N1 = 259, W = 7, modulo 8
-> X75 ITU-T X.75 SLP (single link procedure),
-&gt; V110L ITU-T V.110 19k2 async 'Low' (former ISDNA)
-&gt; V110H ITU-T V.110 38k4 async 'High' (former ISDNB)
-&gt; V120L ITU-T V.120 56k6 async, N1 = 259, W = 7, modulo 8
-&gt; V120H ITU-T V.120 64k async, N1 = 259, W = 7, modulo 8
-&gt; X75 ITU-T X.75 SLP (single link procedure),
64kbit/s B channel; layer 2 max. framesize N1 = 2048,
window size W = 2, frame numbering modulo 8;
layer 3 transparent (no packet layer)
-> ISDN Other configuration, used only if none of above fits
-&gt; ISDN Other configuration, used only if none of above fits
These ISDN flags follow the specification in FSC-0091.
-> Tyz Online time flags as specified in FSC-0062
-&gt; Tyz Online time flags as specified in FSC-0062
The flag Tyz is used by non-CM nodes online not only during ZMH,
y is a letter indicating the start and z a letter indicating the
@ -281,16 +282,16 @@ Contents:
For example TuB shows an online period from 20:30 until 1:00 UTC.
-> Z19 Zyxel series 19200 bps (implies ZYX)
-> X2C x2 client w/ 56000 bps (should imply V34 and V42b)
-> X2S x2 server w/ 64000 bps (should imply V34 and V42b)
-&gt; Z19 Zyxel series 19200 bps (implies ZYX)
-&gt; X2C x2 client w/ 56000 bps (should imply V34 and V42b)
-&gt; X2S x2 server w/ 64000 bps (should imply V34 and V42b)
-> K12 Systems offering all educational K12-conferences
-> ENC The node accepts inbound encrypted mail
-&gt; K12 Systems offering all educational K12-conferences
-&gt; ENC The node accepts inbound encrypted mail
-> NC Network Coordinator (only if the NC is not the host)
-> NEC Net Echomail Coordinator (at most one per net)
-> REC Region Echomail Coordinator (at most one per region)
-&gt; NC Network Coordinator (only if the NC is not the host)
-&gt; NEC Net Echomail Coordinator (at most one per net)
-&gt; REC Region Echomail Coordinator (at most one per region)
Redundant AKAs used to indicate echomail coordination in zone 2
are no longer permitted. One *EC flag is valid for all AKAs of
@ -301,35 +302,35 @@ Contents:
--------------------
Flag implications directly or indirectly specified in FTS-0005:
HST => MNP
H14 => MNP HST
H16 => MNP HST H14
V42b => V42 (MNP ?)
V32b => V32
HST =&gt; MNP
H14 =&gt; MNP HST
H16 =&gt; MNP HST H14
V42b =&gt; V42 (MNP ?)
V32b =&gt; V32
Flag implications specified in the zone 2 nodelist epilogue:
HST => MNP
H14 => HST MNP
-> H16 => V42 MNP V42b H14 HST
-> V42b => V42 MNP
-> ZYX => V42 MNP V42b V32 V32b
-> Z19 => V42 MNP V42b V32 V32b ZYX
V32b => V32
-> V32T => V32 V32b
HST =&gt; MNP
H14 =&gt; HST MNP
-&gt; H16 =&gt; V42 MNP V42b H14 HST
-&gt; V42b =&gt; V42 MNP
-&gt; ZYX =&gt; V42 MNP V42b V32 V32b
-&gt; Z19 =&gt; V42 MNP V42b V32 V32b ZYX
V32b =&gt; V32
-&gt; V32T =&gt; V32 V32b
-> V110L => ISDN
-> V110H => ISDN
-> V120L => ISDN
-> V120H => ISDN
-> X75 => ISDN
-&gt; V110L =&gt; ISDN
-&gt; V110H =&gt; ISDN
-&gt; V120L =&gt; ISDN
-&gt; V120H =&gt; ISDN
-&gt; X75 =&gt; ISDN
The latter ISDN flag redundancies are a consequence of FSC-0091.
Maybe some of the following implications could be added in zone 2:
VFC => V32 V32b MNP V42 V42b
X2C => V34 MNP V42 V42b
X2S => V34 MNP V42 V42b
VFC =&gt; V32 V32b MNP V42 V42b
X2C =&gt; V34 MNP V42 V42b
X2S =&gt; V34 MNP V42 V42b
Flag implications (i.e. not listing redundant flags) have several
advantages: Some old nodelist tools are unable to handle too long
@ -344,11 +345,11 @@ Contents:
XA, XB, XC, XP, XR, XW, and XX. For flag checkers only supporting
implications a good approximation based on FTS-0005 definitions is
| XA => XW XR XP XB XC XX,
| XB => XW XR XP,
| XC => XW XR XX,
| XR => XW,
| XX => XW.
| XA =&gt; XW XR XP XB XC XX,
| XB =&gt; XW XR XP,
| XC =&gt; XW XR XX,
| XR =&gt; XW,
| XX =&gt; XW.
Further X2C cannot be combined with X2S, and FSC-62 Tyz-flags are
not possible with CM. Also Tyz with y = z is of course incorrect.
@ -443,7 +444,7 @@ Contents:
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

9
html/ftsc/fsp-1006.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Kludge for specifying addition e-mail reply addresses.</TITLE>
</HEAD>
@ -95,9 +96,9 @@ Abstract
with the name REPLYALSO can be inserted, each listing one possible
reply address.
@REPLYALSO <e-mail address>
@REPLYALSO &lt;e-mail address&gt;
Where <e-mail address> is in the form of
Where &lt;e-mail address&gt; is in the form of
ramon@wsd.wline.se
or
@ -124,7 +125,7 @@ Abstract
---------------------------------------
@INTL 1:320/42 1:320/42
@TOPT 46
@MSGID: wgmid$<123455@goldware.dk> 45AB23CD
@MSGID: wgmid$&lt;123455@goldware.dk&gt; 45AB23CD
@REPLYTO UUCP 1:320/42
@REPLYADDR odinn@goldware.dk
@REPLYALSO newftsc-l@brazerko.com
@ -152,7 +153,7 @@ B. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

11
html/ftsc/fsp-1007.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Multiple recipient address specification to gateway.</TITLE>
</HEAD>
@ -84,11 +85,11 @@ Abstract
lines can be inserted in the message. If a To: line is present, then
these lines follow the To: line.
GW-To: <e-mail address>[,<e-mail address>[...]]
GW-Cc: <e-mail address>[,<e-mail address>[...]]
GW-Bcc: <e-mail address>[,<e-mail address>[...]]
GW-To: &lt;e-mail address&gt;[,&lt;e-mail address&gt;[...]]
GW-Cc: &lt;e-mail address&gt;[,&lt;e-mail address&gt;[...]]
GW-Bcc: &lt;e-mail address&gt;[,&lt;e-mail address&gt;[...]]
Where <e-mail address> is in the form of
Where &lt;e-mail address&gt; is in the form of
ramon@wsd.wline.se
or
@ -155,7 +156,7 @@ B. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

5
html/ftsc/fsp-1008.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>New control lines for forwarding messages.</TITLE>
</HEAD>
@ -224,7 +225,7 @@ Abstract
@REPLY: 1:234/567 12345678
Text: Hi Joe!
JU> ...
JU&gt; ...
...
@ -268,7 +269,7 @@ B. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

5
html/ftsc/fsp-1009.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Year 2000 issues in FTN software.</TITLE>
</HEAD>
@ -102,7 +103,7 @@ Abstract
smaller than 80 can't mean "year 19xx", but can only mean "year
20xx". One algorithm for correct year number interpretation is:
if year_number < 80 then
if year_number &lt; 80 then
calendar_year = 2000 + year_number
else
calendar_year = 1900 + year_number
@ -135,7 +136,7 @@ B. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fsp-1010.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>FTSC Document FSP-1010, Revision 001</TITLE>
<BODY
@ -237,6 +238,6 @@ C. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>

15
html/ftsc/fsp-1011.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>FTSC Document FSP-1011, Revision 003</TITLE>
</HEAD>
@ -264,7 +265,7 @@ Table of contents
+-+-------+--------+--- ................ ---+
|T| SIZE | DATA |
+-+-------+--------+--- ................ ---+
|<- 2 octets ->|<- up to 32767 octets ->|
|&lt;- 2 octets -&gt;|&lt;- up to 32767 octets -&gt;|
(frame header) (frame data)
If T bit is 0, this is a data frame.
@ -366,7 +367,7 @@ Table of contents
filename = *pchar
pchar = unreserved | escape
unreserved = ALPHA | DIGIT | safe
safe = "@" | "&" | "=" | "+" | "%" | "$" | "-" | "_" |
safe = "@" | "&amp;" | "=" | "+" | "%" | "$" | "-" | "_" |
"." | "!" | "(" | ")" | "#" | "|"
escape = "\" HEX HEX
@ -1024,7 +1025,7 @@ Table of contents
|RxWriteD|Write data to|Write Failed |Report |RxDone |Failure |
| |file | |error | | |
| | |-------------+----------+--------+--------|
| | |File Pos > |Report |RxDone |Failure |
| | |File Pos &gt; |Report |RxDone |Failure |
| | |Reported |write | | |
| | | |beyond EOF| | |
| | |-------------+----------+--------+--------|
@ -1034,7 +1035,7 @@ Table of contents
| | | |File | | |
| | | |Received | | |
| | |-------------+----------+--------+--------|
| | |File Pos < |none |RxReceD |OK |
| | |File Pos &lt; |none |RxReceD |OK |
| | |Reported | | | |
|--------+-------------+-------------+----------+--------+--------|
|RxEOB |Get a frame |Didn't get a |none |RxEOB |OK |
@ -1118,12 +1119,12 @@ Table of contents
|-------+------------+--------------+------------+-------+--------|
|TxWLA |Check |TheQueue is |none |TxDone |OK |
| |TheQueue |empty and | | | |
| | |RxState >= | | | |
| | |RxState &gt;= | | | |
| | |RxEOB | | | |
| | |--------------+------------+-------+--------|
| | |TheQueue is |none |TxWLA |OK |
| | |empty and | | | |
| | |RxState < | | | |
| | |RxState &lt; | | | |
| | |RxEOB | | | |
| | |--------------+--------------------+--------|
| | |TheQueue is |call ProcessTheQueue|continue|
@ -1751,6 +1752,6 @@ B. History
* Minor edits throughout the document to improve
readability.
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>

3
html/ftsc/fta-1005.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>FTSC Product ID List.</TITLE>
</HEAD>
@ -261,7 +262,7 @@ C. History
**********************************************************************
</PRE>
<A HREF="./"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="./"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

31
html/ftsc/fts-0001.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>A Basic FidoNet(r) Technical Standard.</TITLE>
</HEAD>
@ -350,19 +351,19 @@ Status of this document:
If the first character of a physical line (e.g. the first character of
the message text, or the character immediately after a hard carriage
return (ignoring any linefeeds)) is a ^A (<control-A>, 01H), then that
return (ignoring any linefeeds)) is a ^A (&lt;control-A&gt;, 01H), then that
line is not displayed as it contains control information. The
convention for such control lines is:
o They begin with ^A
o They end at the end of the physical line (i.e. ignore soft <cr>s).
o They end at the end of the physical line (i.e. ignore soft &lt;cr&gt;s).
o They begin with a keyword followed by a colon.
o The keywords are uniquely assigned to applications.
o They keyword/colon pair is followed by application specific data.
Current ^A keyword assignments are:
| o TOPT <pt no> - destination point address
o FMPT <pt no> - origin point address
o INTL <dest z:n/n> <orig z:n/n> - used for inter-zone address
| o TOPT &lt;pt no&gt; - destination point address
o FMPT &lt;pt no&gt; - origin point address
o INTL &lt;dest z:n/n&gt; &lt;orig z:n/n&gt; - used for inter-zone address
File Specifications
@ -510,7 +511,7 @@ Status of this document:
| W1 | WindIdle | 1 incoming call | | W2 |
| | | 2 receive-only mode | | W0 |
| | | 3 send-only mode | | W3 |
| | | 4 60-180 secs & no call | | W3 |
| | | 4 60-180 secs &amp; no call | | W3 |
|-----+----------+-------------------------+-------------------------+-----|
| W2* | WindRecv | | (receive call R0) | W3 |
|-----+----------+-------------------------+-------------------------+-----|
@ -520,9 +521,9 @@ Status of this document:
| W4* | WindSend | | (make call S0) | W5 |
|-----+----------+-------------------------+-------------------------+-----|
| W5 | WindMark | 1 call successful | remove node fr call list| W0 |
| | | 2 no connect | remove if try cnt > lim | W0 |
| | | 2 no connect | remove if try cnt &gt; lim | W0 |
| | | 3 call failed | incr conn cnt, remove | W0 |
| | | | if con cnt > lim | |
| | | | if con cnt &gt; lim | |
`-----+----------+-------------------------+-------------------------+-----'
@ -956,7 +957,7 @@ Status of this document:
trailer *)
| TeLinkBlock (* TeLink File Descriptor Block *)
| ACK (* acknowledge data received ok *)
| NAK (* negative ACK & poll 1st block *)
| NAK (* negative ACK &amp; poll 1st block *)
| EOT (* end of xfer, after last block *)
| "C" (* 43H *)
@ -980,7 +981,7 @@ Status of this document:
Checksum (* error detect/correction code *)
ACK = 06H (* acknowledge data received ok *)
NAK = 15H (* negative ACK & poll 1st block *)
NAK = 15H (* negative ACK &amp; poll 1st block *)
SOH = 01H (* start of header, begins block *)
SYN = 16H (* start of TeLink file info blk *)
EOT = 04H (* end of xfer, after last block *)
@ -1069,8 +1070,8 @@ Status of this document:
| | | 2 want checksum mode | send NAK | XR1 |
|-----+----------+-------------------------+-------------------------+-----|
| XR1 | WaitFirst| 1 10 retries or 1 minute| report receive failure | exit|
| | | 2 > 3 retries or 30 secs| set want checksum mode | XR0 |
| | | 3 EOT received | delay < sec, purge input| exit|
| | | 2 &gt; 3 retries or 30 secs| set want checksum mode | XR0 |
| | | 3 EOT received | delay &lt; sec, purge input| exit|
| | | | send ACK, report no file| |
| | | 4 TeLink block recd | send ACK, set crc/cksm | XR2 |
| | | 5 data block recd | send ACK, set crc/cksm | XR2 |
@ -1115,7 +1116,7 @@ Status of this document:
| # | Name | | | St |
|-----+----------+-------------------------+-------------------------+-----|
| MS0 | WaitNak | 1 20 retries or 1 minute| filename send failed | exit|
| | | 2 NAK received | send ACK & 1st ch of fn | MS1 |
| | | 2 NAK received | send ACK &amp; 1st ch of fn | MS1 |
| | (note 1) | 3 C received | return fn skipped | exit|
|-----+----------+-------------------------+-------------------------+-----|
| MS1 | WaitChAck| 1 ACK rcd, fname done | send SUB = 1AH | MS2 |
@ -1139,7 +1140,7 @@ Status of this document:
|-----+----------+-------------------------+-------------------------+-----|
| MR1 | WaitAck | 1 rcd ACK | | MR2 |
| | | 2 rcd EOT | report no files remain | exit|
| | | 3 5 secs & no ACK/EOT | | MR0 |
| | | 3 5 secs &amp; no ACK/EOT | | MR0 |
|-----+----------+-------------------------+-------------------------+-----|
| MR2 | WaitChar | 1 recd EOT (can happen?)| report no files remain | exit|
| | | 2 recd SUB | send checksum byte | MR3 |
@ -1253,7 +1254,7 @@ Status of this document:
Messages generated by Fido 11w, SEAdog 3.8, and QMail 1.01
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

5
html/ftsc/fts-0004.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Echomail Specification.</TITLE>
</HEAD>
@ -149,7 +150,7 @@ research and advancement is allowed.
compatible control information to the message. The tear line
generated by Conference Mail looks like:
--- <a small product-specific banner>
--- &lt;a small product-specific banner&gt;
This field is optional for most Echomail compatible
processors, and is added by the Conference Mail System to
@ -407,7 +408,7 @@ research and advancement is allowed.
-30-
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

9
html/ftsc/fts-0005.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>The Distribution Nodelist.</TITLE>
</HEAD>
@ -470,11 +471,11 @@
There are three editing commands and all have the same format:
<command><number>
&lt;command&gt;&lt;number&gt;
<command> is a 1 letter command, one of A, C, or D.
&lt;command&gt; is a 1 letter command, one of A, C, or D.
<number> is a decimal number greater than zero, and defines the
&lt;number&gt; is a decimal number greater than zero, and defines the
number of lines to be operated on by the command. Each command
appears on a line by itself. The commands have the following
meanings:
@ -610,7 +611,7 @@
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

49
html/ftsc/fts-0006.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>YOOHOO and YOOHOO/2U2.</TITLE>
</HEAD>
@ -45,7 +46,7 @@ Status of this document:
LEGAL STUFF
-----------
@ -86,7 +87,7 @@ FTS-0001, describing the base FidoNet protocol, was created by Randy Bush.
FTS-0007, describing enhancement to FTS-0001 using SEAlink and/or SEAlink
Overdrive, was created by Phil Becker.
YooHoo and YooHoo/2u2 Page 2
Overview
@ -145,7 +146,7 @@ sees a TSYNC.
This simple method allows a mailer to take care of both the TSYNC and the
YOOHOO handshakes.
YooHoo and YooHoo/2u2 Page 3
WaZOO Protocols
@ -202,7 +203,7 @@ Currently there are four WaZOO methods in use:
* The same packet naming convention as ZedZap applies, allowing more
than one packet to be transmitted in a single session.
YooHoo and YooHoo/2u2 Page 4
WaZOO Protocols
@ -241,7 +242,7 @@ WaZOO Protocols
The protocol is documented elsewhere; it is beyond the scope of this
document to do so.
YooHoo and YooHoo/2u2 Page 5
Choosing WaZOO Methods
@ -274,7 +275,7 @@ choose as follows:
The capability highest on the list which both systems indicate ability to
execute should be the one employed.
YooHoo and YooHoo/2u2 Page 6
WaZOO Filename conventions
@ -314,7 +315,7 @@ WaZOO FILENAMES
In a Janus session, the .REQ file isn't actually sent. Janus has
a transaction system which sends the .REQ file one line at a time
and then accepts the file(s) which the request generates.
YooHoo and YooHoo/2u2 Page 7
Flow of a ZedZap or ZedZip Session
@ -356,7 +357,7 @@ Receiving system:
* If we sent a .REQ file in the preceding step, receive all files
in a single batch.
YooHoo and YooHoo/2u2 Page 8
WaZOO File Requests
@ -401,8 +402,8 @@ REQ file contents would have to change:
Transaction-level passwords (of 6 or fewer characters) follow the file name:
<filename><single-space-character>!<password><cr>
&lt;filename&gt;&lt;single-space-character&gt;!&lt;password&gt;&lt;cr&gt;
YooHoo and YooHoo/2u2 Page 9
WaZOO File Requests
@ -425,7 +426,7 @@ including the indicated time will be sent.
The complete format of an action line in an REQ file is, then:
<filename>[<space>!<password>][<space><+/-><time>]<cr>
&lt;filename&gt;[&lt;space&gt;!&lt;password&gt;][&lt;space&gt;&lt;+/-&gt;&lt;time&gt;]&lt;cr&gt;
@ -451,7 +452,7 @@ In the YooHoo packet, there's a bit that lets you know if the remote system
currently accepts .REQ files. This will be a clue as to whether a .REQ file
would be a waste of time or not. Procedurally, you just should not send a .REQ
file to a system which indicates that it won't process it.
YooHoo and YooHoo/2u2 Page 10
Structures and Definitions
@ -490,7 +491,7 @@ struct _Hello
/*------------------------------------------------------------------------*/
/* YOOHOO<tm> CAPABILITY VALUES */
/* YOOHOO&lt;tm&gt; CAPABILITY VALUES */
/*------------------------------------------------------------------------*/
#define Y_DIETIFNA 0x0001 /* Can do fast "FTS-0001" 0000 0000 0000 0001 */
#define FTB_USER 0x0002 /* Reserved by Opus-CBCS 0000 0000 0000 0010 */
@ -508,7 +509,7 @@ struct _Hello
#define Bit_d 0x2000 /* reserved by FTSC 0010 0000 0000 0000 */
#define DO_DOMAIN 0x4000 /* Packet contains domain 0100 0000 0000 0000 */
#define WZ_FREQ 0x8000 /* WZ file req. ok 1000 0000 0000 0000 */
YooHoo and YooHoo/2u2 Page 11
Domain addressing in Hello Packet
@ -548,7 +549,7 @@ hello.capabilities will contain the usual capabilities plus DO_DOMAIN.
A remote system receiving this packet should look past the null in
my_name to get the domain name.
YooHoo and YooHoo/2u2 Page 12
Caller State Tables
@ -592,18 +593,18 @@ system. It replaces state S3 in the FTS-0001 table.
| | | 4. NAK received | probable FTS-0001 | SS3 |
| | +-------------------------+-------------------------+-----|
| | | 5. Debris (might include| Reset NAK timer | |
| | | (YOOHOO|TSYNC) & 127)| if started | SS1 |
| | | (YOOHOO|TSYNC) &amp; 127)| if started | SS1 |
|-----+----------+-------------------------+-------------------------+-----|
| SS3 | NAKTmr | 1. Timer not expired | Zero NAK count | |
| | | or timer not started | Start .5 sec NAK timer | SS1 |
| | +-------------------------+-------------------------+-----|
| | | 2. Timer expired | Bump NAK count | SS4 |
|-----+----------+-------------------------+-------------------------+-----|
| SS4 | NAKCount | 1. Count >= 2? | assume FTS-0001 | exit|
| SS4 | NAKCount | 1. Count &gt;= 2? | assume FTS-0001 | exit|
| | +-------------------------+-------------------------+-----|
| | | 2. Count < 2 | Keep looking | SS1 |
| | | 2. Count &lt; 2 | Keep looking | SS1 |
`-----+----------+-------------------------+-------------------------+-----'
YooHoo and YooHoo/2u2 Page 13
Caller State Tables
@ -652,7 +653,7 @@ an FTS-0001 session.
If the packet exchange is successful, session method selection proceeds and
then the chosen session method should be employed to exchange mail and files.
YooHoo and YooHoo/2u2 Page 14
Called System State Tables
@ -711,7 +712,7 @@ table.
| | +-------------------------+-------------------------+-----|
| | | 2. Timer running | Two TSYNCS = FTS-0001 | exit|
`-----+----------+-------------------------+-------------------------+-----'
YooHoo and YooHoo/2u2 Page 15
Called System State Tables
@ -765,7 +766,7 @@ an FTS-0001 session.
If the packet exchange is successful, session method selection proceeds and
then the chosen session method should be employed to exchange mail and files.
YooHoo and YooHoo/2u2 Page 16
Packet Exchange State Tables
@ -802,7 +803,7 @@ from one system to its partner:
| | +- - - - - - - - - - - - -+- - - - - - - - - - - - -+- - -|
| | | other character recvd | Debris, keep watching | SH4 |
`-----+----------+-------------------------+-------------------------+-----'
YooHoo and YooHoo/2u2 Page 17
Packet Exchange State Tables
@ -863,7 +864,7 @@ to a system by its partner:
`-----+----------+-------------------------+-------------------------+-----'
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

258
html/ftsc/fts-0007.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>An Enhanced FidoNet(r) Technical Standard.</TITLE>
</HEAD>
@ -50,34 +51,6 @@ Status of this document:
Introduction
While the basic FTS-0001 protocol has become reasonably standardized, it
@ -127,22 +100,6 @@ Status of this document:
1
Table of Contents
@ -200,15 +157,6 @@ Status of this document:
2
The purpose of the SEAlink protocol
@ -454,7 +402,7 @@ Status of this document:
someName[.n] - field of n bits
someName(n) - Null terminated string allocated n chars (incl Null)
someName{max} - Null terminated string of up to max chars (incl Null)
someName<max> - String of up to max chars, NOT null terminated
someName&lt;max&gt; - String of up to max chars, NOT null terminated
(* punctuation *)
a b - one 'a' followed by one 'b'
@ -596,15 +544,6 @@ Status of this document:
8
Sender
@ -615,8 +554,8 @@ Status of this document:
| S0 | SendInit | | dial modem | S1 |
+-----+----------+-+-----------------------+-------------------------+-----+
| S1 | WaitCxD |1| carrier detected | delay 1-5 seconds | S2 |
| | (*1) | | | Set SLO if > 2400bps, | |
| | | | | Reset SLO if <= 2400bps | |
| | (*1) | | | Set SLO if &gt; 2400bps, | |
| | | | | Reset SLO if &lt;= 2400bps | |
| | +-+-----------------------+-------------------------+-----+
| | |2| busy, etc. | report no connection | exit|
| | +-+-----------------------+-------------------------+-----+
@ -663,14 +602,6 @@ Status of this document:
9
Receiver
@ -720,23 +651,6 @@ Status of this document:
10
F. Network Layer : the Network's View of the System, Routing and Packets
@ -782,25 +696,6 @@ Status of this document:
~ 3 bytes ~
| left adjusted blank filled |
`-----------------------------------------------'
11
@ -848,25 +743,6 @@ Status of this document:
*3 - When no files remain, the sender responds to the receiver's NAK with
an EOT. The EOT is not ACK/NAKed by the receiver.
12
@ -919,22 +795,6 @@ Status of this document:
13
G. Data Link Layer : Error-Free Data Transfer
@ -990,17 +850,6 @@ Status of this document:
`-----------------------------------------------'
14
XMODEM Data Block (Checksum mode)
Offset
@ -1141,9 +990,9 @@ Status of this document:
| TeLinkBlock (* TeLink File Descriptor Block *)
| ReSyncBlock (* SEAlink RESYNC request packet *)
| ACK (* acknowledge data received ok *)
| NAK (* negative ACK & poll 1st block *)
| NAK (* negative ACK &amp; poll 1st block *)
| SEAlinkACK (* acknowledge data received ok *)
| SEAlinkNAK (* negative ACK & poll 1st block *)
| SEAlinkNAK (* negative ACK &amp; poll 1st block *)
| EOT (* end of xfer, after last block *)
| "C" (* 43H *)
@ -1183,22 +1032,6 @@ Status of this document:
biSeconds[.2] (* 6 bits, seconds/2, 0-29 *)
17
Data Description Language definition of the block types added by this
extended protocol specification:
@ -1238,32 +1071,12 @@ Status of this document:
Definitions of Single byte Character values used in protocol:
ACK = 06H (* acknowledge data received ok *)
NAK = 15H (* negative ACK & poll 1st block *)
NAK = 15H (* negative ACK &amp; poll 1st block *)
SOH = 01H (* start of header, begins block *)
SYN = 16H (* start of TeLink file info blk *)
EOT = 04H (* end of xfer, after last block *)
ETX = 03H (* end of RESYNC request data field*)
18
Block Verification calculated values used by this protocol:
@ -1322,15 +1135,6 @@ Status of this document:
RET
19
2. Data Link Layer Protocol : XMODEM/TeLink/SEAlink Finite State Machines
@ -1383,20 +1187,6 @@ Status of this document:
these numbers. Good practice is to make file block numbers 32 bit values.
20
XMODEM/TeLink/SEAlink - Sender
@ -1422,7 +1212,7 @@ Status of this document:
+-----+----------+-------------------------+-------------------------+-----+
| XS1 | CheckACK | | (Check ACK/NAK AC0) | XS2 |
+-----+----------+-+-----------------------+-------------------------+-----+
| XS2 | SendBlk |1| NumNAK &gt; 4 & | If header = SEAlink | XS0T|
| XS2 | SendBlk |1| NumNAK &gt; 4 &amp; | If header = SEAlink | XS0T|
| | (*2) | | SendBLK = 0 +-------------------------+-----+
| | | | | If header = TeLink, | XS2 |
| | | | | NumNAK = 0, | |
@ -1440,7 +1230,7 @@ Status of this document:
| | |6| SendBLK = Last Blk+1 | Send EOT, Incr SendBLK, | XS1 |
| | | | | Set T1 to 30 seconds | |
| | +-+-----------------------+-------------------------+-----+
| | |7| SLO set & SEAlink set | Send SendBLK, (*3) | XS1 |
| | |7| SLO set &amp; SEAlink set | Send SendBLK, (*3) | XS1 |
| | | | | ACKBLK = SendBLK, | |
| | | | | Incr SendBLK, | |
| | | | | Set T1 to 60 seconds | |
@ -1479,7 +1269,7 @@ Status of this document:
| | |2| ACKST &lt;=2 | | AC6 |
+-----+----------+-+-----------------------+-------------------------+-----+
| AC2 | SLVerify |1| ARBLK8 = 1's comp(CHR)| ARBLK = SendBLK - | AC3 |
| | | | | ((SendBLK-ARBLK8)&0FFh) | |
| | | | | ((SendBLK-ARBLK8)&amp;0FFh) | |
| | +-+-----------------------+-------------------------+-----+
| | |2| ARBLK8 # 1's comp(CHR)| Reset SEAlink flag, | AC6 |
| | | | | WINDOW=1, | |
@ -1574,27 +1364,13 @@ Status of this document:
the SEAlink header block and add the following state to (AC7):
.-----+--------+---+-----------------------+-------------------------+-----.
| AC7 | |3.5| CHR = ^S (13H) & | Delay 10 seconds or | exit|
| | | | SEAlink set & | until ^Q (11H) rcvd | |
| AC7 | |3.5| CHR = ^S (13H) &amp; | Delay 10 seconds or | exit|
| | | | SEAlink set &amp; | until ^Q (11H) rcvd | |
| | | | ACKST = 0 | | |
`-----+--------+---+-----------------------+-------------------------+-----'
23
XMODEM/TeLink/SEAlink - Receiver
@ -1683,7 +1459,7 @@ Status of this document:
| | | | | (Send ACK SA0), | |
| | | | | reset retry cnt | |
| | +-+-----------------------+-------------------------+-----+
| | |5| SEAlink set & | Discard block - resync | XR3 |
| | |5| SEAlink set &amp; | Discard block - resync | XR3 |
| | | | expected block+1 to | in progress, | |
| | | | expected block+127 | Send Conditional NAK(*5)| |
| | +-+-----------------------+-------------------------+-----+
@ -1695,7 +1471,7 @@ Status of this document:
| | +-+-----------------------+-------------------------+-----+
| | |2| Want to resume an | WriteBLK = file restart| XR5 |
| | | | interrupted xfer | block number, | |
| | | | and RESYNC is set | blocknum=WriteBLK&0FFh,| |
| | | | and RESYNC is set | blocknum=WriteBLK&amp;0FFh,| |
| | | | | (Send NAK SN0) | |
+-----+----------+-+-----------------------+-------------------------+-----+
| XR5 | SetOvrdr | | Set SLO as indicated | XR3 |
@ -1805,7 +1581,7 @@ Status of this document:
+-----+----------+-+-----------------------+-------------------------+-----+
| MS0 | WaitNak |1| 20 retries or 1 minute| filename send failed | exit|
| | +-+-----------------------+-------------------------+-----+
| | |2| NAK received | send ACK & 1st ch of fn | MS1 |
| | |2| NAK received | send ACK &amp; 1st ch of fn | MS1 |
+-----+----------+-+-----------------------+-------------------------+-----+
| MS1 | WaitChAck|1| ACK rcd, fname done | send SUB = 1AH | MS2 |
| | +-+-----------------------+-------------------------+-----+
@ -1835,7 +1611,7 @@ Status of this document:
| | +-+-----------------------+-------------------------+-----+
| | |2| rcd EOT | report no files remain | exit|
| | +-+-----------------------+-------------------------+-----+
| | |3| 5 secs & no ACK/EOT | | MR0 |
| | |3| 5 secs &amp; no ACK/EOT | | MR0 |
+-----+----------+-+-----------------------+-------------------------+-----+
| MR2 | WaitChar |1| recd EOT (can happen?)| report no files remain | exit|
| | +-+-----------------------+-------------------------+-----+
@ -1862,7 +1638,7 @@ Status of this document:
27
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

48
html/ftsc/fts-0008.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Bark file-request protocol extension.</TITLE>
</HEAD>
@ -121,8 +122,10 @@ Status of this document:
A.4, one extra terminal used in this notation:
(* terminals *)
someName<max> - String of up to max chars, NOT null terminated
C. Performing File Requests
someName&lt;max&gt; - String of up to max chars, NOT null terminated
C. Performing File Requests
1. Introduction
@ -186,21 +189,22 @@ Status of this document:
*1 - CRC does not include the ACK or ETX and is
in the reverse byte order from the CRC in a
normal XMODEM data packet.
2. Data Description Notation of Bark Request Packet
2. Data Description Notation of Bark Request Packet
DataBlock (no password) = ACK
Filename<12>
Filename&lt;12&gt;
Space
Date<11>
Date&lt;11&gt;
ETX
CRC
DataBlock (with password) = ACK
Filename<12>
Filename&lt;12&gt;
Space
Date<11>
Date&lt;11&gt;
Space
Password<6|8>
Password&lt;6|8&gt;
ETX
CRC
@ -221,7 +225,8 @@ Status of this document:
CRCs. The CRC is calculated on
all data in the block between but
not including the ACK and the ETX *)
E. Session Layer Protocol:
E. Session Layer Protocol:
This section describes the modified FTS-0001 session layer protocol. This
is the only area of FTS-0001 which is modified to implement Bark style file
@ -244,7 +249,8 @@ Status of this document:
The following diagrams fully replace the Session Layer protocol state
tables in FTS-0001. No other changes to FTS-0001 are required to implement
the Bark File request feature.
Sender (Top level)
Sender (Top level)
.-----+----------+-------------------------+-------------------------+-----.
|State| State | Predicate(s) | Action(s) | Next|
@ -253,8 +259,8 @@ Status of this document:
| S0 | SendInit | | dial modem | S1 |
+-----+----------+-+-----------------------+-------------------------+-----+
| S1 | WaitCxD |1| carrier detected | delay 1-5 seconds | S2 |
| | (*1) | | | Set SLO if > 2400bps, | |
| | | | | Reset SLO if <= 2400bps | |
| | (*1) | | | Set SLO if &gt; 2400bps, | |
| | | | | Reset SLO if &lt;= 2400bps | |
| | +-+-----------------------+-------------------------+-----+
| | |2| busy, etc. | report no connection | exit|
| | +-+-----------------------+-------------------------+-----+
@ -263,11 +269,11 @@ Status of this document:
| | |4| carrier not detected | report no connection | exit|
| | | | within 60 seconds | | |
+-----+----------+-+-----------------------+-------------------------+-----+
| S2 | WhackCRs |1| over 30 seconds | report no response <cr> | exit|
| S2 | WhackCRs |1| over 30 seconds | report no response &lt;cr&gt; | exit|
| | +-+-----------------------+-------------------------+-----+
| | |2| ?? <cr>s received | delay 1 sec | S3 |
| | |2| ?? &lt;cr&gt;s received | delay 1 sec | S3 |
| | +-+-----------------------+-------------------------+-----+
| | |3| <cr>s not received | send <cr> <sp> <cr> <sp>| S2 |
| | |3| &lt;cr&gt;s not received | send &lt;cr&gt; &lt;sp&gt; &lt;cr&gt; &lt;sp&gt;| S2 |
| | | | | delay ??? secs | |
+-----+----------+-+-----------------------+-------------------------+-----+
| S3 | WaitClear|1| no input for 0.5 secs | send TSYNCH = AEH | S4 |
@ -299,7 +305,7 @@ Status of this document:
Note: Although the above shows the sender emitting only one TSYNCH, it is
recommended that a timeout of 5-20 seconds should initiate another TSYNCH.
The receiver should tolerate multiple TSYNCHs.
Receiver (Top Level)
Receiver (Top Level)
The receiving FSM is given an external timer, the expiration of which
will cause termination with a result of 'no calls' (R0.2).
@ -362,7 +368,7 @@ Status of this document:
| | |2| Disallow Requests | Hang Up | exit|
`-----+----------+-+-----------------------+-------------------------+-----'
*1 - Some implementations always do (R6.1) even if they have no requests.
Sender - Send Mail
Sender - Send Mail
.-----+----------+-------------------------+-------------------------+-----.
|State| State | Predicate(s) | Action(s) | Next|
@ -398,7 +404,7 @@ Status of this document:
+-----+----------+-+-----------------------+-------------------------+-----+
| SB2 | RcvFile |1| Rcv ACK | (Batch Receive BR0) | SB3 |
| | +-+-----------------------+-------------------------+-----+
| | |2| Tries > 5 | Send ETB, report failed | exit|
| | |2| Tries &gt; 5 | Send ETB, report failed | exit|
| | +-+-----------------------+-------------------------+-----+
| | |3| Rcv Other | Purge input, Incr tries | SB1 |
| | +-+-----------------------+-------------------------+-----+
@ -412,7 +418,7 @@ Status of this document:
| | +-+-----------------------+-------------------------+-----+
| | |4| 45 sec in SB3 | Hang up, report error | exit|
`-----+----------+-+-----------------------+-------------------------+-----'
Sender & Receiver - Receive Mail
Sender &amp; Receiver - Receive Mail
.-----+----------+-------------------------+-------------------------+-----.
|State| State | Predicate(s) | Action(s) | Next|
@ -433,7 +439,7 @@ Status of this document:
`-----+----------+-+-----------------------+-------------------------+-----'
Sender & Receiver - Receive Bark
Sender &amp; Receiver - Receive Bark
.-----+----------+-------------------------+-------------------------+-----.
|State| State | Predicate(s) | Action(s) | Next|
@ -478,7 +484,7 @@ Status of this document:
FTS-0001 session, but will not buy more time.
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fts-0009.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Message identification and reply linkage.</TITLE>
</HEAD>
@ -97,7 +98,7 @@ GENERAL
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fts-4001.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>Addessing Control Paragraphs.</TITLE>
</HEAD>
@ -185,7 +186,7 @@ A. History
**********************************************************************
</PRE>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fts-5000.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>The Distribution Nodelist.</TITLE>
</HEAD>
@ -446,7 +447,7 @@ C.&nbsp;History<BR>
<BR>
</TT>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/fts-5001.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>The Distribution Nodelist.</TITLE>
</HEAD>
@ -396,7 +397,7 @@ B.&nbsp;History<BR>
<BR>
</TT>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/ftscprod.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<TITLE>FTSC Product ID List.</TITLE>
</HEAD>
@ -304,7 +305,7 @@
0FFF,McMail,DOS,Mailer,Simon_Slater,2:443/777,20000102
</PRE>
<A HREF="./"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="./"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

3
html/ftsc/index.htm
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -94,7 +95,7 @@ Michiel Broek.
<HR>
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0" width="33" height="35">Back to Index</A>
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0">Back to Index</A>
</BLOCKQUOTE>
</BODY>
</HTML>