Kantronics KPC-9612, Getting Started And Reference Manual

Page: 48 / 81

KPC-9612 Version 5.2 July 19, 1994
48
R:931012/1107 27268@WK5M.SNEKS.KS.USA.NOAM
R:931012/1025 16433@N0LLY.#NEKS.KS.USA.NOAM
R:931011/2021 928@N0OER.#NEKS.KS.USA.NA
R:931008/1814 20728@N0OBM.#NCKS.KS.USA.NA
R:931008/2003 195208NX0R.#NKS.KS.USA.NA
R:931008/1153 3079@AG0N.#WNE.NE.USA.NA
R:931007/1147 35B50@N7MMC.#SEWY.WY.USA.NA
R:931007/1712 49403@KT0H.#NECO.CO.USA
R:931007/1639 63792@KA0WIN.#SECO.CO.USA.NA
R:931004/1529 46383@N5IST.#WTX.TX.USA.NOAM
By examining this list from the bottom up, we may see that the message entered the system on
October 4, 1993 at 15:29 (
R:931004/1529
). It was message number
46383
on the N5IST BBS
(
@N5IST
) which is located in West Texas (
#WTX
), which is in Texas (
TX
), which is in the United
States (
USA
) which is in North America (
NOAM
). From this station, it was relayed on October 7 at
16:39 to the KA0WIN BBS in Southeastern Colorado. By following this information it is possible to
determine where the message traveled and when it was relayed from each station. The informa-
tion following the ©BBS callsign is called the hierarchical routing information (in this case
#WTX.TX.USA.NOAM
).
When you connect to your local BBS and send a message, that BBS automatically generates an
R:
line. As the message is sent to its destination, each BBS adds its own
R:
line to the message. Be-
sides the requirement of the FGC, the
R:
line provides a method for any user, anywhere in the
world, to send a reply or respond to your message. As the message is passed through the many
BBSs, each BBS will add you into its White Pages - a directory of packet users. Each BBS makes
note that you (the originator of the message) sent the message, and that you entered the mes-
sage at the BBS listed in the last
R:
line in the message.
Because of this, a distant user can simply send a reply using the send reply (SR) command of his
local BBS. That BBS will then address the message to you using the @BBS and hierarchical routing
information in the last
R:
line of the message you sent. A user may also simply use the send pri-
vate command (SP) to send a message to you. If the user does not enter complete addressing on
his SP command, the BBS will attempt to look up your call in its White Pages and add the routing
automatically. However, if the user supplied complete addressing information, the BBS would nor-
mally assume it is correct and not check the White Pages.
BBSs use this hierarchical information to send the message back to you. The message someone
sent to you (using the above example) would be addressed to
URCALL@N5IST.#WTX.TX.USA.
NOAM
. As the message passes through the BBS system for forwarding, the BBS first looks at the
callsign of the addressee (
URCALL
). If that BBS doesn't know how to forward the message to you,
it then looks at the ©BBS field (
N5IST
). If it doesn't have any information on how to forward to
N5IST, it looks at the first part of the hierarchical address (
#WTX
), not knowing that, it would then
look at the next part of the hierarchical address (
TX
). Assuming this BBS is in the United States, it
knows TX means Texas and knows that this message needs to be relayed to a station in that area.
Once the message reaches the first BBS in Texas, that system must use the previous field for for-
warding (
#WTX
). Once it reaches a system in West Texas, the forwarding occurs based on the
©BBS.
When the message reaches the BBS specified in the @BBS field, it can forward the message direct-
ly to you, since you are using that system as your HOME BBS.
When you enter a message into your Kantronics PBBS and supply the routing information, that
message may be forwarded automatically to another BBS. When the message is forwarded from
your Kantronics mailbox, an
R:
line is included as the originating BBS. This line includes the same