World of Ham Radio 1994 January/AMSOFT_1994.iso/packet/docs/pd198704.doc

Text File | 1993-12-31 | 79.9 KB | 1,723 lines

1-Apr-87 04:06:48-EST,1197;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 1 Apr 87 04:06-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 31 Mar 87 23:34:35 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 31 Mar 87 23:34:20 EST
Message-Id: <[e-mail]>
Received: from UNCAEDU(BLINGARD) by MITVMA (Mailer X1.23) id 7504;
      Tue, 31 Mar 87 23:22:46 EST
Date:     Tue, 31 Mar 87 21:24 MST
From: <[e-mail]>
Subject:    INFO REQUEST!
To: [e-mail]
X-Original-To:  [e-mail], BLINGARD

HI!
I AM INTERESTED IN GETTING INTO PACKET RADIO AND WOULD LIKE TO
KNOW IF ANYONE OTHERE HAS USED BRAILLE OR
VOICE OUTPUT TERMINALS BEFORE ON PAPCKET.
I WILL BE USING TELEVIDEO 801 64K Z80 CP/M 2.22
COMPUTER WITH A BRAILINK BRAILLE OUTPUT TERMINAL.
MAY BE GETTING SPEECH SYNTHESIZER IN FUTURE.
ANY INFO YOU CAN SUPPLY MOST APPRECIATED.
THANKS AND 73
BRIAN K LINGARD VE3YI
ELECTRONIC ADDRESS: BLINGARD@UNCAEDU ON BITNET
PO BOX 5798 STATION A
TORONTO ONT CANADA M5W 1P2
PSE COMMUNICATE OVER THIS SYSTEM, INK-PRINT, BRAILLE OR STANDARD CASSETTE.
 1-Apr-87 09:35:26-EST,995;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 1 Apr 87 09:35-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 1 Apr 87 08:36:33 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 1 Apr 87 08:36:21 EST
Message-Id: <[e-mail]>
Posted-From: The MITRE Corp., Bedford, MA
To: [e-mail]
Cc: [e-mail], [e-mail]
Subject: Re: INFO REQUEST!
In-Reply-To: Your message of Tue, 31 Mar 87 21:24:00 -0700.
         <[e-mail]>
Date: Wed, 01 Apr 87 08:32:56 EST
From: [e-mail]

The good thing about most of the TNCs that are ot there is that they
connect a radio to an RS-232.  Then you can run the RS-232 cable into
whatever you want, including a speech synthesizer computer, a
terminal, or whatever....


                Peter Baldwin, WA1SNH
                ([e-mail])
 3-Apr-87 08:41:21-EST,1443;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 3 Apr 87 08:41-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 3 Apr 87 07:32:12 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 3 Apr 87 07:32:02 EST
Received: from unido.UUCP by seismo.CSS.GOV (5.54/1.14) with UUCP
    id AA13934; Fri, 3 Apr 87 07:30:31 EST
Received: by unido.uucp with uucp;
      Fri, 3 Apr 87 14:07:43 +0100
Received: by gmdzi.UUCP id AA03505; Fri, 3 Apr 87 12:36:00 -0100
Date: Fri, 3 Apr 87 12:36:00 -0100
From: "gunter" <unido!gmdzi!rz.informatik.uni-hamburg.dbp.de![e-mail]>
To: [e-mail]
Message-Id: <61:[e-mail]&de>
Subject: Higher Levels TNC Software

Our Packet/Radio Project here in Hamburg is delivering thre different
Packet Radio boards: standalone board (similar to TNC-board), add-on board
for Z80-systems using Eurocard-bus and IBM-PC add-on board.
All boards are containing the identical TNC software, totally written in
TURBO-PASCAL.
Out software group is ready for adding higher level protocols and/or
mail forwarding software. We are highly interested in receiving a copy of
the TCP/IP package developed by Phil Karn. Unfortunately we do not have access
to the ARPAnet by anonymous FTP. Who can help us by sending the software
via electronic mail or on diskette ?

Gunter, DL2VO
 5-Apr-87 04:34:41-EDT,1624;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 5 Apr 87 04:34-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 5 Apr 87 03:56:02 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 5 Apr 87 03:55:53 EDT
Message-Id: <[e-mail]>
Received: from relay2.cs.net by RELAY.CS.NET id aa06217; 5 Apr 87 3:53 EDT
Received: from cgi.com by RELAY.CS.NET id aa00111; 5 Apr 87 2:51 EST
Date:     Sun, 5 Apr 87 01:12 EST
From: [e-mail]
To: [e-mail]
Subject:  Phil Karn's Software via Simtel
X-Vms-To: IN%"[e-mail]"


To Gunter and others:

For those of you who lack FTP access, SIMTEL20 offers an automated mail-based
file server which will allow you to get the KA9Q software via E-mail (as
well as hundreds of good PD programs.)  If you missed the earlier series
of related messages, just send a message to ARCHIVE-REQUEST@SIMTEL20
which contains the following as its message body:

SEND INFO

The subject line is ignored.  Phil's software should be in the MSDOS directory.
You may instruct SIMTEL to encode the file in a number of ways, including
squeezing, ARCing, UUENCODEing and a number of other popular compression/
librarian formats.

We are going to see a real struggle this year for the dominant high level
protocol.  TCP/IP gets my vote.  The best way to get it established is
to DISTRIBUTE PHIL'S SOFTWARE!

P.S.  I saw an earlier mention of KA9Q port to the Amiga.  Having any
luck with that whoever that was?

- Kurt
 5-Apr-87 17:40:52-EDT,1994;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 5 Apr 87 17:40-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 5 Apr 87 15:37:43 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 5 Apr 87 15:37:13 EDT
Date:     Sun, 5 Apr 87 14:30:47 EST
From: [e-mail]
To: [e-mail]
Subject:  [H. Craig McKee:  Layer 2 muxing on ISDN]
Message-Id:  <[e-mail]>

You may observe that AX.25 is in reality a frame-relay mechanism, but with
TEI replaced by callsign. It might be suggested to the CCITT that the
amatuer community maybe got there first and, further, that ISDN might
consider frame-level routing like in AX.25. I would very much like to be
present if/when these potatoes land on a rapporteur's desk!

Dave

----- Forwarded message # 1:

Received: from sri-nic.arpa by Huey.UDEL.EDU id a011020; 5 Apr 87 13:47 EST
Received: from mitre.ARPA by SRI-NIC.ARPA with TCP; Sat 4 Apr 87 07:56:34-PST
Full-Name: Hugh Mckee
Message-Id: <[e-mail]>
Organization: The MITRE Corp., Washington, D.C.
To: [e-mail]
Cc: [e-mail], [e-mail], [e-mail]
Subject: Layer 2 muxing on ISDN
In-Reply-To: Your message of 01 Apr 87 21:28:00 -0500.
         <[A.ISI.EDU] 1-Apr-87 21:28:17.CERF>
Date: Sat, 04 Apr 87 10:40:32 EST
From: "H. Craig McKee" <[e-mail]>


The proposed Frame Relay service of ISDN does do layer 2 multiplexing.
In LAPD, there is a 2 byte address containing a 6 bit SAPI and a 7 bit TEI
(Terminal Equipment Identifier).  These 2 fields are combined into a
13 bit DLCI (Data Link Connection Identifier) which would be handled
similarly to the LCN in X.25.  It would be mapped and set in each node as a
frame progressed through the network.  Then a new CRC would be calculated
and inserted.
*
*        Steve


----- End of forwarded messages
 6-Apr-87 23:27:52-EDT,1012;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 6 Apr 87 23:27-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 6 Apr 87 21:47:22 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 6 Apr 87 21:46:24 EDT
Message-Id: <[e-mail]>
Received: From Usc-Isi.ARPA by AMC-HQ via smtp;  6 Apr 87 21:40 EST
Date:  6 Apr 1987 22:37:16 EDT
Subject: re: Request for Help
From: Franklin Antonio <[e-mail]>
To: [e-mail]
Cc: [e-mail]

Glad you decided to put your USA-PKT file on compuserve Hamnet.
That's a great place for it.  HOWEVER, your file is VERY large.
It's gonna cost people an arm and a leg to download it.
I strongly suggest you break it into reasonable sized chunks (perhaps
by state? or even smaller in the large states?).  Otherwise, the download
cost is just gonna be prohibitive for 99% of all users.
-------
 7-Apr-87 06:41:50-EDT,1139;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 7 Apr 87 06:41-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 7 Apr 87 05:51:32 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 7 Apr 87 05:51:16 EDT
Received: from unido.UUCP by seismo.CSS.GOV (5.54/1.14) with UUCP
    id AA17023; Tue, 7 Apr 87 05:49:45 EDT
Received: by unido.uucp with uucp;
      Tue, 7 Apr 87 11:28:08 +0100
Received: by gmdzi.UUCP id AA03069; Tue, 7 Apr 87 10:48:01 -0100
Date: Tue, 7 Apr 87 10:48:01 -0100
From: "gunter" <unido!gmdzi!rz.informatik.uni-hamburg.dbp.de![e-mail]>
To: [e-mail]
Message-Id: <65:[e-mail]&de>
Subject: SIMTEL20 download

The notice of Kurt <[e-mail]> about using ARCHIVE-REQUEST@SIMTEL20
seems not to be operable, if you access the host via UUCP mail.
My request was refused by SIMTEL20 because of the costs using UUCP.
So I have to ask the operator again to prepare the files for me.

Networking is hard, because there are many holes in the net.

Gunter, DL2VO
 7-Apr-87 13:46:56-EDT,1474;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 7 Apr 87 13:46-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 7 Apr 87 09:15:30 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 7 Apr 87 09:12:55 EDT
Date: Tue, 7 Apr 1987  07:09 MDT
Message-Id: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To: gunter <unido!gmdzi!rz.informatik.uni-hamburg.dbp.de![e-mail]>
Cc: [e-mail], unido![e-mail],
    [e-mail], [e-mail],
    [e-mail], [e-mail]
Subject: SIMTEL20 download refusals
In-Reply-To: Msg of Tue 7 Apr 87 10:48:01 -0100 from gunter <unido!gmdzi!rz.informatik.uni-hamburg.dbp.de!hille at seismo.CSS.GOV>

SIMTEL20 does not refuse download requests.  The refusal came from
SEISMO, which has blocked ALL mail originating from ARCHIVE-REQUEST at
SIMTEL20.  Seismo is the only link between Arpanet and Usenet for some
people.  The answer is for those who are affected to send mail to the
postmaster at the last host before seismo, asking that they consider
discontinue the use of seismo and pick up a different backbone host.
Frankly, I don't believe any host that is classed as a "backbone"
should be allowed to remain a backbone if they refuse ANY mail.

--Keith Petersen
 8-Apr-87 14:56:33-EDT,2755;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 8 Apr 87 14:55-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 8 Apr 87 11:29:23 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 8 Apr 87 11:28:50 EST
Message-Id: <[e-mail]>
Received: by AMC-HQ via xmm1;  8 Apr 87 12:13 EST
Date:     8 Apr 87 12:05:24-EST (Wed)
From: Dbennett@xmm-plexus01
To: packet-radio%eddie.mit.edu@Amc-Hq, info-hams%simtel20.arpa@Amc-Hq
Subject:  Request for Packet Information

               Update Form for USA-PKT File
            Send information to  K4NGC @ K4NGC


Please use the following form when sending updates to me for the USA-PKT
File.  Also please place this form on all PBBS's that you know of. The
greater distribution of this form the better chance I will have of getting
the necessary updates.

Call Sign of Digipeater/PBBS       ____________________________________

SSID (e.g., -1, -2, -3, etc.)      ____________________________________

Aliases use for Layer 3/4          ____________________________________

Actual Location of Digi/PBBS       ____________________________________

Nearest City                       ____________________________________

State Digi/PBBS Located            ____________________________________

Frequency it operates on           ____________________________________

Grid where located                 ____________________________________

Type Activity                      [ ] Digipeater  [ ] PBBS  [ ] TCP/IP

Layer Protocol operating under     [ ]  Layer 1          [ ]  Layer 2
                   [ ]  Layer 3          [ ]  Layer 4
                   [ ]  Layer 5          [ ]  Layer 6
                   [ ]  Layer 7

Remarks/Comments : ____________________________________________________
           ____________________________________________________


Make sure you fill in one form for each frequency you are using.  If you
are using one transceiver but scanning more than one frequency please
indicate this in the above remarks/comments section. Please let me know
of any corrections,  deletions or  additions  to  any  of the USA-PKT
File. Send them to me. K4NGC @ K4NGC via one of the EASTNET PBBS mailboxes
or to one of the following -

         Donald H. Bennett
         15016 Carlsbad Road
         Woodbridge, Va 22193
         (Home)   703-670-4773
         (Office) 703-274-9355/56
         (AMRAD BBS) 703-734-1387
         (ARPANET) dbennett@amc-hq
         (CompuServe) 72310,263
10-Apr-87 13:34:27-EDT,4086;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 10 Apr 87 13:34-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 10:34:57 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 9 Apr 87 17:36:35 EST
Message-Id: <[e-mail]>
Received: by AMC-HQ via xmm1;  9 Apr 87 8:40 EST
Date:     9 Apr 87 8:16:23-EST (Thu)
From: Dbennett@xmm-plexus01
To: [e-mail],
    [e-mail]
Subject:  Frequency Coordination on Packet (DO WE NEED IT!!!!!)

TO:   All Packet Users in Maryland, Virginia, and DC.
INFO: To anyone else having the same problem.


I am having a problem which I am at a loss on how to resolve.  I knowTCP/IP
is  what Packet will be in the days to come.  What I want to know is why it
is being forced on us before we need it or want it.  There  are  a  lot  of
hams  out  there who have invested a lot of money in antenna, cable, TNC's,
transceivers and computer/terminals.  They are now being TOLD to get rid of
their  C64,  V20,  TRS80,  etc  and  get a computer that is compatible with
TCP/IP.  I for one am getting sick and tired of dishing out  money  because
some one comes up with new ideas to push packet along at the expense of the
user.  Lets slow down darn it.  We don't have to have all Layers  now.  Let
the people who have AX.25 L2V1 and AX.25 L2V2 have some fun first and enjoy
their hobby.  Let the Hams use NetROM or what every comes on line.  The Ham
community is not a race to see who has the best or latest.

     In addition I see a lot of people out there getting tired of  fighting
with  Packet Bulletin Boards, Digipeaters, TCP/IP, LOOOONG Beacons, and the
likes.  I have tried to set up a Packet Radio  Frequency  Allocation  Table
which  will  list  the  authorized TMARC and CVRA-SERA frequencies and show
recommendations of what type of activity should be used  on  them.  I  have
been told by some that they dont intend to use it.  That they plan on doing
what they want.  Let me suggest that these people do not have the  interest
of  the  ENTIRE  PACKET  or HAM COMMUNITY.  They are only thinking of their
personnel needs or likes.  I have suggested (which will be published soon I
HOPE)  a  list  of  the  145, 220, 440 and 900 Mhz frequencies showing what
frequencies PBBs, Digipeaters, TCP/IP, R&D, and Keyboard/Keyboard should be
operating  on.  Now  if  someone  wants  to talk to joe-blow two miles away
he/she will have a simplex frequency available  for  keyboard  to  keyboard
operation (NO PBBS's or TCP/IP to screw him up).

     The trend seems to be D.. him I am going to transmit anyway.  This  is
the  Death  Wish  for  Packet.  I  think its about time we all talked.  Its
about time we all bent backwards a little.  Its about time we  compramised.
Its  about  time  we  stop fighting to see who gets what.  If we dont do it
then someone else will do it for us.  The more we  fight  over  the  Packet
Frequencies   the  more  ammunition  the  Corps.  will  have  to  take  our
frequencies away from us.  I hope the remarks THAT WILL COME BACK  will  be
in favor of all working together.  BUT I know there will be a fue out there
who wont care.  The recommendations I am making  for  frequency  allocation
are  not  locked  in  iron.  They  can and will be changed in the fature to
serve ALL.  I am one of the OLD HAMS who cares about  where  Ham  Radio  is
going.  Lets set aside frequencies for BBS's, let set aside frequencies for
TCP/IP, Lets set aside frequencies for the user only.  Dont put  everything
on the same frequencies.  It just wont work.

     I am sorry for taking up your time  but  i  felt  it  was  about  time
someone  talked  about  it.  If  anyone wants a copy of my recommendations,
which will go to TMARC and CVRA-SERA, let me know.  Once all  comments  are
in I will make copies available to anyone who wants it.

     73's Thanks for listening Don Bennett (K4NGC)


10-Apr-87 14:49:15-EDT,813;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 10 Apr 87 14:49-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 12:17:10 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 12:15:55 EST
Date: 10 Apr 1987 12:50-EDT
From: [e-mail]
To: Alan Larson <[e-mail]>
Cc: packet-radio@mit-eddie
Subject: Re: tcp/ip for mac (CMU MacIP package)
Message-Id: <545071803/[e-mail]>
In-Reply-To: Alan Larson's mail message of Thu 9 Apr 87 22:54:21-PDT

Look in c.cs.cmu.edu::<applebus.programs> rather than simply <anonymous>.
The files are named MacIP.shar[1-10].  The contain Lisa Pascal source code
for an implementation of TCP/IP for the Mac.

                    - Ralph
10-Apr-87 19:33:43-EDT,1726;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 10 Apr 87 19:33-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 17:23:10 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 17:22:32 EST
Received: by jade.berkeley.edu (5.54 (CFC 4.22.3)/1.16.12)
    id AA28085; Fri, 10 Apr 87 15:20:31 PDT
Message-Id: <[e-mail]>
Return-Path: [e-mail]
Received: by DTUZDV1 (Mailer X1.23) id 5365; Fri, 10 Apr 87 23:25:30 CET
Date:         Fri, 10 Apr 87 22:47 CET
From: Ralf D. Kloth <[e-mail]>
Subject:      TCP/IP
To: <[e-mail]>

After downloading the KA9Q NET.EXE software from SIMTEL20 and burning the
new EPROM (with a non-INTEL EPROMer) for downloading KISS to the TNC2,
DJ7KA and me (DL4TA) have made some first tests today. It works great!
I use TCP/IP on mainframes, and its a nice feeling to work with it on
packet radio now.
However, the overall acceptance of TCP/IP in our local area doesn't seem
to be as great ...
The level-2 users complain about the garbage they see in the TCP/IP-
packets. One OM pointed out " ... I don't understand this, and I even
don't want to understand, ... the level 2 is good enough for me, I don't
need any others ...". Sigh.
However, we will continue with local tests and will encourage others here
to do the same ...
Thanx to KA9Q and N3EUA for donating their programs to the public,
and to K.Petersen for keeping them on SIMTEL20 for downloading.

73, Ralf (DL4TA)  <[e-mail]>
Acknowledge-To: Ralf D. Kloth <ZRKL001@DTUZDV1>
10-Apr-87 21:56:34-EDT,1556;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 10 Apr 87 21:56-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 20:06:12 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 9 Apr 87 23:45:46 EST
Message-Id: <[e-mail]>
Received: from USU(BOBW) by MITVMA (Mailer X1.23) id 2156;
      Thu, 09 Apr 87 16:22:33 EDT
Date:     Thu, 9 Apr 87 14:26 MST
From: <[e-mail]> (BOB WOOD WA7MXZ)
Subject:  TNC-1 development update from TAPR
To: [e-mail]
X-Original-To:  [e-mail], BOBW

     There is a rumor floating around that TAPR is allocating $5000 for
upgrading the TNC-1 firmware to TNC-2 specifications. Has anyone else
heard about this or does anyone have information on who is doing this
upgrade or where the money is being spent. WA7MBL and I (WA7MXZ) offered
to do the upgrade for free ($0000) to Lyle Johnsen last summer after the
WIMU hamfest. Lyle told us that Harold was still working on the project and
was unwilling to accept ANY offer of assistance on the project. We made Lyle
a standing offer at that point that if HArold ever gave up the TNC-1 project
we would pick it up. We heard that Harold had given up the TNC-1 project some
time back but we never heard from Lyle or TAPR about our offer. Does anyone
have further information in regards to this latest development on the TNC-1
software upgrade??
Bob Wood WA7MXZ   BOBW@USU    CHEM::BOBW via SPAN
11-Apr-87 00:00:25-EDT,2647;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 00:00-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 22:09:30 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 15:55:43 EST
Message-Id: <[e-mail]>
Received: from relay2.cs.net by RELAY.CS.NET id ac14099; 10 Apr 87 16:41 EDT
Received: from cgi.com by RELAY.CS.NET id af07685; 10 Apr 87 16:35 AST
Date:     Fri, 10 Apr 87 16:13 EST
From: [e-mail]
To: [e-mail]
Subject:  Re: Racing for Latest and Greatest
X-Vms-To: IN%"[e-mail]"

>I am having a problem which I am at a loss on how to resolve.  I knowTCP/IP
>is  what Packet will be in the days to come.  What I want to know is why it
>is being forced on us before we need it or want it.  There  are  a  lot  of
>hams  out  there who have invested a lot of money in antenna, cable, TNC's,
>transceivers and computer/terminals.  They are now being TOLD to get rid of
>their  C64,  V20,  TRS80,  etc  and  get a computer that is compatible with
>TCP/IP.  I for one am getting sick and tired of dishing out  money  because
>some one comes up with new ideas to push packet along at the expense of the
>user.  Lets slow down darn it.  We don't have to have all Layers  now.  Let

I don't see TCP/IP as "pushing expensive equipment" or "racing to have the
latest and greatest." In fact, we are doing just the opposite.  We are racing
to set a standard to AVOID the chaos of thousands different and incompatible
high level networks.  I think that it should be obvious TCP/IP does not
require different radios/antennas, etc.  Installing chips in your TNC is not
that bad.  ESPECIALLY IF IT IS A UNIFIED STANDARD.  As for "expensive
machines", that is just because TCP/IP STARTED on expensive machines.  It is
not too tough a process to be handled by common home machines.  It is only a
matter of porting the software.  This would require knowledge of the
conventions of the protocol as well as an experienced assembly programmer,
but it can and will be done.  There is nothing wrong about taking it slow,
but you will have 500 protocols emerging all around you anyway.  By spreading
a standard, we are simply getting ONE established.

Is TCP/IP the divine choice?  Maybe not.  What I DO know is that this
protocol has not only proven itself (you're reading this, aren't you)
but there is a lot of experience and software around it which can make
the process of establishing it as a radio medium more painless.
11-Apr-87 05:13:16-EDT,1323;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 05:13-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 16:07:56 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 16:07:16 EST
Message-Id: <[e-mail]>
Received: from UREGINA1(MAILER) by MITVMA (Mailer X1.23) id 5918;
      Fri, 10 Apr 87 16:31:39 EDT
Received: by UREGINA1 (Mailer X1.23b) id 6855; Fri, 10 Apr 87 14:27:50 CST
Date:         Fri, 10 Apr 87 14:21:44 CST
From: Perry Brandiezs <BRANDIEZ@UREGINA1>
To: [e-mail]

Our ham radio club received a request from a local BBS operator to consider
the possibility of having his computer phone up a packet station which would
then forward information over the air to another packet station, back into
the phone lines.

My question is, does anybody have any information on software, or how
to have the packet station answer the phone, forward the information
received from the modem over the air, etc.?  Is this legal (in Canada)?

Any and all information provided would be greatly appreciated, since
packet radio is still in its infancy around here.

73's
Perry Brandiezs VE5AGA
Regina, Saskatchewan.

[e-mail]
11-Apr-87 05:15:51-EDT,835;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 05:15-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 12:23:46 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 12:19:35 EST
Date: 10 Apr 1987 12:50-EDT
From: [e-mail]
To: Alan Larson <[e-mail]>
Cc: [e-mail]
Subject: Re: tcp/ip for mac (CMU MacIP package)
Message-Id: <545071803/[e-mail]>
In-Reply-To: Alan Larson's mail message of Thu 9 Apr 87 22:54:21-PDT

Look in c.cs.cmu.edu::<applebus.programs> rather than simply <anonymous>.
The files are named MacIP.shar[1-10].  The contain Lisa Pascal source code
for an implementation of TCP/IP for the Mac.

                    - Ralph
11-Apr-87 07:27:43-EDT,745;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 07:27-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 21:28:23 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 10 Apr 87 21:28:02 EST
Date:     Fri, 10 Apr 87 21:19:23 EST
From: [e-mail]
To: "Ralf D. Kloth" <[e-mail]>
Cc: [e-mail]
Subject:  Re:  TCP/IP
Message-Id:  <[e-mail]>

Ralf,

You might suggest to the onlookers as their screens go bonkers that you
are experimenting in graphics and if they get this great new TCP/IP
their screens will glow beautifully again.

Dave, W3HCF
11-Apr-87 14:39:53-EDT,608;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 14:39-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 12:21:11 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 12:20:50 EST
Message-Id: <[e-mail]>
Date: Sat, 11 Apr 87 13:19:23 EDT
From: [e-mail]
To: [e-mail]
Subject: Correction: re: pathname for CMU MacIP source

Look in c.cs.cmu.edu::<appletalk.programs>.
The directory name changed recently.

                    - Ralph
11-Apr-87 14:57:37-EDT,862;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 14:57-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 13:03:31 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 13:03:21 EST
Date:     Sat, 11 Apr 87 12:53:31 EST
From: [e-mail]
To: [e-mail]
Message-Id:  <[e-mail]>

Perry,

Personally, I would be very wary of using amateur facilities on a regular
basis for non-amateur services and am fairly certain the FCC would pounce
on it in this country. Why don't you put the question directly to the
DOT and report their response here? I would very much like to know what
if any differences exist in their philosphical approach to these issues
vis a vis the FCC.

Dae
Dave W3HCF
11-Apr-87 18:32:04-EDT,1584;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 18:32-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 16:46:31 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 16:46:18 EST
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA16748; Sat, 11 Apr 87 13:44:57 PST
From: rutgers!princeton!allegra!ulysses!faline![e-mail]
Return-Path: <rutgers!princeton!allegra!ulysses!faline![e-mail]>
Newsgroups: rec.ham-radio.packet
Subject: Re: Higher Levels TNC Software [TCP/IP for packet radio]
Summary: A better way to get my code
Message-Id: <[e-mail]>
Date: 9 Apr 87 01:50:29 GMT
To: [e-mail]
References: <[e-mail]>
Organization: Bell Communications Research, Inc
Lines: 16
Posted: Wed Apr  8 20:50:29 1987

For those of you interested in my TCP/IP packet radio software but
aren't on the ARPANET, I strongly suggest that you get it by ordinary
mail by sending $5 for costs to

Brian Lloyd, WB6RQN
19200 Tilford Way
Germantown, MD 20874

Brian doesn't want people sending him their own floppies; he says they
often arrive damaged because they were improperly packaged, and he has
to provide a new disk out of his own pocket. This certainly agrees with
my own past experiences.  If you are ready to spend several tens of
dollars of somebody else's money on phone bills to get my stuff, you can
certainly afford to part with the $5 to get it from Brian instead.

Phil


11-Apr-87 18:52:23-EDT,2723;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 18:52-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 16:57:33 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 16:57:25 EST
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA16975; Sat, 11 Apr 87 13:56:05 PST
Return-Path: <rutgers!seismo!rochester!kodak![e-mail]>
From: rutgers!seismo!rochester!kodak![e-mail] (barry ornitz)
Subject: Inexpensive Megabit Packet Radio System
Keywords: packet radio, TNC, IP/TCP, NTIS
Message-Id: <[e-mail]>
Date: 6 Apr 87 14:39:52 GMT
To: [e-mail]
Organization: Eastman Kodak Co., Rochester, NY
Lines: 37

In the March 1 issue of Government Report Announcements and Index, I noticed
the following report was available.  I thought members of the packet radio
community might be interested.  It may be obtained from the National Technical
Information Service (NTIS), U.S. Department of Commerce, 5285 Port Royal Road,
Springfield, VA  22161.  The cost of a paper copy is $9.95 and a microfiche
copy is $6.50.

     AD-A174 378/0/GAR                             707,429
     Information Sciences Institute, Marina Del Ray, CA

     Inexpensive Megabit Packet Radio System

     Richard Bisbey, II, Robert Parker and Randy Cole
     Oct. 1986, 10p, Rept. No. ISI/RS-86-166
     Contract MDA903-81-C-0335

     Although packet radio is relatively new to the amateur radio community,
     there are now over 10,000 amateur packet radio units in service. These
     units cost between $500 and $800, including the controller and radio,
     and generally operate at 1200 baud.  An effort to improve performance
     significantly while keeping costs reasonable has resulted in a packet
     radio system that can operate at data rates of up to one megabit per
     second, yet costs less than $1000 for the controller and radio. [!]
     The controller can also be used to develop its own software.  The radio
     is digitally synthesized and operates in the 400 MHz region. The system
     uses DoD Internet IP/TCP datagrams, and has been used in the amateur
     radio service at the maximum legal rate of 56 Kbps.

 -----------------                    73,  WA4VZQ
|  ___  ________  |
| |  / /        | |  Barry L. Ornitz       UUCP:...!rochester!kodak!ornitz
| | / /         | |  Eastman Kodak Company
| |< < K O D A K| |  Eastman Chemicals Division Research Laboratories
| | \ \         | |  P. O. Box 1972
| |__\ \________| |  Kingsport, TN  37662       615/229-4904
|                 |
 -----------------


11-Apr-87 19:27:35-EDT,1273;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 19:27-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 17:38:46 EST
Received: by EDDIE.MIT.EDU with UUCP with smail2.3 with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 17:38:38 EST
Received: from unido.UUCP by seismo.CSS.GOV (5.54/1.14) with UUCP
    id AA08650; Sat, 11 Apr 87 18:28:30 EDT
Received: by unido.uucp;
      Sun, 12 Apr 87 00:05:38 +0100
Message-Id: <[e-mail]>
To: [e-mail]
Date: Sat, 11 Apr 87 23:57:44 MET
From: "Walter Doerr" <seismo!unido!rmi![e-mail]>
Subject: TCP/IP on ATARI???
X-Mailer: ELM [version 1.2a]


Hello net-hams.

Has anyone ported Phil Karn's TCP/IP package to the Atari ST (or is
doing so at the moment)?

I have heard of a version for the Amiga, so I am pretty sure that someone
out there is busy working on an Atari version.

It doesn't have to be ready to run code. Some hints on what changes are
required to make Phil's program run on the Atari would be sufficient
(although a finished program would be better).


73s
Walter, DG2KK
UUCP: {...!seismo}!unido!rmi!hikaru
  or:          ...!unido!altger!hikaru



11-Apr-87 22:20:09-EDT,1327;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 11 Apr 87 22:20-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 19:45:56 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 11 Apr 87 19:45:43 EST
Message-Id: <[e-mail]>
Received: from ECNCDC(MISS014) by MITVMA (Mailer X1.23) id 8458;
      Sat, 11 Apr 87 20:32:49 EDT
Date:     Sat 11 Apr 1987 18:56 CDT
From: Thomas Churchill <[e-mail]>
Subject:  Crunch;
To: <[e-mail]>

crunch, gobble, gobble...
Our computer ate a message before I got a chance to get the adress of of it;
would the fellow who was interested in the multi-user/single TNC pbbs system
I am writing for the Mac please respond to me at this address.

In addition, since our mainframe doesn't have access to the MacIP source; if
someone could be so kind as to fetch it and forward them to me, I'd really
appreciate it, and post it locally so it would be available on our net, as
well.  TNX,

   ____  ____           -- Thomas Churchill
  /__   /      /  /    Educational Computing Network @ WIU/Illinois
 /     /      /  /     BITNET:   MISS014@ECNCDC
/___  /____  /  /      INTERNET: [e-mail]
13-Apr-87 01:14:54-EDT,1463;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Apr 87 01:14-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 12 Apr 87 23:17:05 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 12 Apr 87 23:16:53 EST
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA05581; Sun, 12 Apr 87 19:15:43 PST
From: rutgers!princeton!allegra!ulysses!faline![e-mail]
Return-Path: <rutgers!princeton!allegra!ulysses!faline![e-mail]>
Newsgroups: rec.ham-radio.packet
Subject: Re: TNC-1 development update from TAPR
Message-Id: <[e-mail]>
Date: 12 Apr 87 23:38:40 GMT
References: <[e-mail]>
Organization: Bell Communications Research, Inc
Lines: 13
Posted: Sun Apr 12 18:38:40 1987
Apparently-To: [e-mail]

I can't say much about what's actually going on, but at the
TAPR annual meeting a couple of the TAPR software guys asked me
if it'd be alright if they ported the AX.25 code I wrote in C for the
Xerox 820 several years ago over to the TNC-1.  This is the last
I've heard from this particular group.

I should point out that Marc Kaufman, WB6ECE, has just finished his
first version of a KISS TNC implementation for the TNC-1, allowing
it to be used with my TCP/IP package.  This seems a more worthwhile
use for those venerable old boxes than running yet another version of
AX.25.

Phil


13-Apr-87 08:33:46-EDT,987;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Apr 87 08:33-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 06:58:19 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 06:58:06 EST
Date:  Mon, 13 Apr 87 07:55 EDT
From: [e-mail]
To: [e-mail]
In-Reply-To:  Message of 10 Apr 87 16:21 EDT from "Perry Brandiezs"
Message-Id:  <[e-mail]>

Perry,,

You may run into a problem with the FCC in doing what you suggest.  It
falls very close to the "phone patch" and FCC has hard rules regarding
this.

Our club does have packet in our building and we have a connection from
our mainframe to it.  We can access the mainframe via phone from home
etc, but thats as far as we go.  We do not have it "de-routed" back to
phone.  It's really running packet from a remote location.

73's..  Walt KA1MVM
13-Apr-87 13:03:04-EDT,1697;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Apr 87 13:03-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 10:47:18 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 10:47:00 EST
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA13067; Mon, 13 Apr 87 07:28:54 PST
Return-Path: <rutgers!sri-unix![e-mail]>
Message-Id: <[e-mail]>
Date: 13 Apr 87 07:51:36 GMT
From: rutgers!sri-unix![e-mail] (Alan Larson)
To: [e-mail]
Subject: Re: TNC-1 development update from TAPR
Summary: I asked, also
References: <[e-mail]> <[e-mail]>

[ Some discussion of the rumored tapr version 4.0 for tnc-1 from years past. ]

I recently sent a note or two to Harold via W6IXU.  He was on the
system that night when I sent the message.  I never got a reply.
I wanted to re-work it, add version 2, KISS, etc., if they were
never going to finish.  I don't know what their plans are.

By the way, I have had a similar (but slightly incompatible) front-end
system for the TNC-1 going for some time now.  Unfortunately, it is
NOT KISS protocol.  I have not had the time to convert it.  Mine is
deposited into the ROM space with the debugger, and uses the tapr code
for some routines.  There are NO hardware mods required.  How does the
KISS code mentioned here get installed?  (Same way, or did he make use
of some of the extra ROM space, or what?)

Oh well, perhaps I should send Harold another note.  (Now that the NET/ROM
link south seems working again.)

    Alan


13-Apr-87 14:34:29-EDT,1023;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Apr 87 14:34-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 12:10:23 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 12:09:49 EST
Posted-Date: Mon 13 Apr 87 10:08:11-PDT
Received: by venera.isi.edu (5.54/5.51)
    id AA09904; Mon, 13 Apr 87 10:08:12 PDT
Date: Mon 13 Apr 87 10:08:11-PDT
From: Richard Bisbey <[e-mail]>
Subject: Re: Inexpensive Megabit Packet Radio System
To: [e-mail]
Message-Id: <[e-mail]>
Mail-System-Version: <VAX-MM(205)+TOPSLIB(126)@VENERA.ISI.EDU>


"An Inexpensive Megabit Packet Radio System" mentioned in Barry Ornitz's
message appeared in IEEE Compcon Spring 86.  If you can't locate the
proceedings, send a message with your mailing address to
[e-mail], and Diane will mail you one of our few remaining
reprints.

Richard
ng6q
-------
13-Apr-87 15:16:25-EDT,6000;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Apr 87 15:16-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 12:29:11 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 12:28:55 EST
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA18253; Mon, 13 Apr 87 09:27:38 PST
Return-Path: <winfree![e-mail]>
Date: 13 Apr 87 07:15:03 GMT
From: winfree![e-mail] (Bdale Garbee)
To: [e-mail]
Subject: new release 870412.0 of KA9Q Internet Package
Message-Id: <[e-mail]>
Reply-To: winfree![e-mail] (Bdale Garbee)
Distribution: world
Organization: Bdale's Berkeley Box, Colorado Springs
Lines: 137


Announcing an update to the KA9Q release of 870227.0, bringing the current
release date up to 870412.0.  This update adds new features, and fixes bugs.
I STRONGLY suggest everyone upgrade to this revision.

The changes:
    - KISS for the TAPR TNC1 by Marc Kaufman at Stanford!  We now have a
      "debug monitor" with S-record download capabilities, KISS, and a
      calibration routine...  Be sure to let Marc know if you appreciate
      his efforts!

    - A minor hack from John Hays at Apollo to add a timestamp to the FTP
      server banner, in addition to some Apollo-specific changes:

        net> ftp kd7uw
        Using address: 44.32.0.10
        SYN sent
        Established
        220 kd7uw.ampr (Sun Apr  5 21:27:13 1987) FTP Ready
        quit
        221 Goodbye!

    - a new release of KISS for the TNC2 from Mike Chepponis K3MC, which
      includes full duplex operation, an indication that the download
      or power up was successful, and a ROM-able version allowing a KISS-
      only TNC2 that can handle power outages.  Please be sure to report
      any difficulties encountered with this new KISS.

    - A new version of BM from yours truly, that allows message creation
      using your favorite editor, and includes some internal restructuring
      in preparation for added functionality.  Make sure to update your
      \bm.rc file!  Also, please forward back to me any changes that you
      make to BM... improvements are ALWAYS welcome!

    - A fair amount of internal reorganization of NET by Phil, greatly
      in response from people working on ports to machines other than
      the PC.

    - A smattering of bug fixes I didn't do a very good job of
      documenting...

Things I hope will be in the next release (in a month or so):

    - code for the Amiga
    - further improvment of BM
    - completely rewritten and restructured documentation for the entire
      package, including better novice user instructions.

How to obtain the KA9Q Internet software:

-       Via uucp, the files are on winfree in tar archives as:

      /usr/spool/uucppublic/pub/ka9q_all.tar.Z      16 bit Compress 4.0
      /usr/spool/uucppublic/pub/ka9q_all.t12.Z      12 bit Compress 4.0

    Direct UUCP connection to winfree is available to those who request
    it for polling to get new versions.  Inquire via mail to one of the
    addresses below.

    A reasonable command to issue to pick up the 12-bit distribution
    would be

        uucp winfree!~/pub/ka9q_all.t12.Z /usr/spool/uucppublic


-       Via Opus, log in to my BBS and download from the appropriate files
    area.  There are several .ARC files for the full distribution, one
    for each of the directories.  SeaDog file requests are ok.

    I have configured my BBS to allow first time users ample resources to
    download the full distribtuion at 1200 baud.  The phone number is
    303/593-0766.

    If you have any trouble downloading from the BBS, please let me know.
    Speeds that are supported include 300, 1200, and 2400.

-       Via US Snail, Brian Lloyd WB6RQN has agreed to make floppy copies.
    To get a copy from him, send $5 to:

        Brian Lloyd, WB6RQN
        19200 Tilford Way
        Germantown, MD  20874

    I update Brian directly via UUCP, so he should have relatively
    current code.  I also understand that Brian can provide ROM's for
    KISS TNC1 or TNC2, for $10/each.  Contact him for more details.

    In Canada, contact:

        Michael A. Shiels
        426 Hazel St. #9
        Waterloo Ontario, Canada
        N2L 3P8

    Send him $5 Canadian for a copy of the current distribution on
    disk.  I will be updaing Michael via a uucp/mail hack, so he should
    stay very up to date.

-       Within a day or two of a new release, the code should also be available
    from the following additional secondary distribution points:

        from Dan Taylor, WB6FIU
            ARC files available on BBS @ 805/947-4357, 2400 baud
        from Doug KD4NC in Atlanta, GA
            uucp: winfree!kd4nc!dug
        from Bob Hoffman N3CVL in Pittsburgh, PA
            arpa: [e-mail]
            uucp: pitt!hoffman
        from Wally Linstrugh WA6JPR in Santa Barbara, CA
            arpa: [e-mail]
        from Brian Kantor at UCSD.  (via anonymous FTP?)
            arpa: [e-mail]
            uucp: sdcsvax!tcp-group-request

    Unreleased (read: under development) versions are often available
    on louie.udel.edu, caveat emptor...

If anyone has any trouble getting hold of a copy of the code, please let me
know!

How to contact me:

    Bdale Garbee, N3EUA
    1433 Territory Trail
    Colorado Springs, CO  80919
    303/590-2868w, 303/593-9828h

uucp: {bellcore,crash,hp-lsd,nnc,pitt,vixie}!winfree!bdale
arpa: [e-mail]
      pitt!winfree![e-mail]
fido: Bdale Garbee at 128/19, 303/593-0766, 300/1200/2400 baud, 24hrs
packet: n3eua @ k0hoa
--

Bdale Garbee, N3EUA             phone: [phone] h, 303/590-2868 w
uucp: {bellcore,crash,hp-lsd,hpcsma,ncc,pitt,usafa,vixie}!winfree!bdale
fido: sysop of 128/19           packet: n3eua @ k0hoa, Colorado Springs


13-Apr-87 17:14:58-EDT,538;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Apr 87 17:14-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 12:45:08 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 12:44:48 EST
Message-Id: <[e-mail]>
To: [e-mail]
Subject: please remove
Date: 13 Apr 87 11:27:21 EST (Mon)
From: [e-mail]


Please remove me from this mailing list.

Thanks,

Dan Kalin
13-Apr-87 20:27:37-EDT,1174;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Apr 87 20:27-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 17:47:21 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 17:46:56 EST
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA28901; Mon, 13 Apr 87 14:21:52 PST
Return-Path: <genrad!decvax!decwrl!spar![e-mail]>
From: genrad!decvax!decwrl!spar![e-mail] (Doug Faunt)
To: [e-mail]
Subject: TNC recomendations?
Message-Id: <[e-mail]>
Date: 13 Apr 87 19:38:20 GMT
Distribution: na
Organization: Schlumberger Palo Alto Research - CASLAB
Lines: 9

Can somebody give reccomendations for TNC's for various people:
A person who doesn't tend to build stuff, but would like to
set up a packet station for himself, and kids, all licensed.
He has a Commodore 64.

A person who listens (doesn't have a license currently), and would
like RTTY, CW, and packet capability. Technically competent.  Might
get a license if interested enough.  Has terminals, and IBM-PC type
computers.


13-Apr-87 20:49:36-EDT,715;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Apr 87 20:49-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 17:01:10 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 13 Apr 87 17:00:35 EST
Received: by marlin.nosc.mil (5.54/1.14)
    id AA21548; Mon, 13 Apr 87 14:00:06 PST
Date: Mon, 13 Apr 87 14:00:06 PST
From: [e-mail] (Danny R. Major)
Message-Id: <[e-mail]>
To: [e-mail]
Cc: [e-mail]
Subject: Mail deletion

-------

Please delete this station from your mailing list.

    Thank You,

    Danny Major
    N6BCC
-------

15-Apr-87 15:14:12-EDT,1029;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 15 Apr 87 15:14-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 15 Apr 87 12:03:39 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 15 Apr 87 12:02:41 EDT
Message-Id: <[e-mail]>
Date: 15 Apr 1987 12:00:18 EDT
From: [e-mail]
Subject: Amateur PR work
To: [e-mail]
Cc: [e-mail], [e-mail]


Folks,

I am very interested in catching up on the amateur PR work, because of
my responsibilities with the Army in DoD applications of PR technology.

Please add me to any mailing lists and feel free to contact me
with info. I am also chairing a session at the upcoming IEEE MILCOM 87
in Washington, DC on "Applications of PR Technology" and would love
to have a paper representing the Ham work in this area. Any takers?

Paul Sass
WB2HQW
US Army CECOM
AMSEL-RD-COM-AC-B
Fort Monmouth, NJ 07703
-------
16-Apr-87 10:36:06-EDT,909;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 16 Apr 87 10:36-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 16 Apr 87 08:26:25 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 16 Apr 87 08:26:09 EDT
Message-Id: <[e-mail]>
Posted-From: The MITRE Corp., Bedford, MA
To: [e-mail]
Cc: [e-mail], [e-mail], [e-mail]
Subject: Re: Amateur PR work
In-Reply-To: Your message of 15 Apr 87 12:00:18 -0400.
         <[e-mail]>
Date: Thu, 16 Apr 87 08:25:26 EST
From: [e-mail]

This may be a dumb queston, but what is it that you are talking about?
Does "PR" stand for "public relations", "packet radio", or something
else?

                Peter Baldwin, WA1SNH
                ([e-mail])
16-Apr-87 15:39:26-EDT,783;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 16 Apr 87 15:39-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 16 Apr 87 12:36:38 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 16 Apr 87 12:36:08 EDT
Message-Id: <[e-mail]>
Date: 16 Apr 1987 11:16:28 EDT
From: [e-mail]
Subject: Re: Amateur PR work
To: [e-mail]
Cc: [e-mail], [e-mail]
Cc: [e-mail]

In response to your message sent  Thu, 16 Apr 87 08:25:26 EST

Peter,

Sorry for the confusion . I thought the "community" understood
PR to mean Packet Radio.

I guess we need better PR Public Relations!

Paul Sass WB2HQW

-------
16-Apr-87 22:08:54-EDT,3012;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 16 Apr 87 22:08-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 16 Apr 87 19:50:43 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 16 Apr 87 19:50:28 EDT
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA22111; Thu, 16 Apr 87 06:50:36 PST
Return-Path: <koning.dec.com![e-mail]>
From: koning.dec.com![e-mail] (Paul Koning -- DS architecture)
To: [e-mail]
Subject: Re: Packet Addressing Schemes
Message-Id: <[e-mail]>
Date: 16 Apr 87 02:55:45 GMT
Sender: [e-mail]
Organization: Digital Equipment Corporation
Lines: 38

Comment on the notes from KB7UV and K4NGC about area codes as addresses:

Grid squares indeed are geometric rather than population oriented.  But
I think that's actually more appropriate.  The point is that in routing,
you need addresses that specify location, since the intent is to identify
the packet switch near the ultimate destination.  Given that the switching
network is VHF/UHF based (or should be), it has limited range, so
semi-uniform geographical areas are better than telephone areas that
potentially are far larger than a repeater's coverage.

As for grid square being hard to determine, not so: there's a trivial
conversion from latitude/longitude, and those you can get from a USGS
topo map (or, probably close enough, from town hall).  Also, I expect that
geographical routing merely requires you to be "close enough" (i.e. so
you end up at a packet switch that the destination can hear, anything
more precise is overkill) so if you look up a person in the call book, find
the grid square for that town (to 4 characters, perhaps) and use that, you'd
be all set...

Grid squares are a worldwide system; area codes aren't.  Also, in most of
the world area codes are variable length (for example in England where they
vary between 1 and 5 digits) which complicates matters.

As for call signs as addresses: call signs aren't addresses, they are names.
A call sign contains no information whatsoever that indicates the location
of the station.  (You might think it tells you at least the country but
given reciprocal operating permits it doesn't even do that.)  For routing,
an ADDRESS must have the property that you can efficiently derive some sort
of location information from it.  Grid squares, lat/long pairs both do that;
telephone areas also but not as well; zip codes even less.  The only way
that calls alone will suffice is if the network looks up the call in a
name service (aka. electronic call book) and converts it to a location
behind your back.  Yes, that would be useful.  I'd view it as a function
of the sending station, or some nearby server, rather than of the switching
network, though.  In any case, it belongs above layer 3 and should be
considered separately.

    paul  ni1d


17-Apr-87 03:14:31-EDT,1043;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 17 Apr 87 03:14-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 00:20:40 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 00:20:27 EDT
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA16768; Thu, 16 Apr 87 19:49:27 PST
Return-Path: <ulysses!faline![e-mail]>
Date: 16 Apr 87 00:02:54 GMT
From: ulysses!faline![e-mail] (Phil R. Karn)
Subject: Re: new release 870412.0 of KA9Q Internet Package
To: [e-mail]
Summary: It's up and available
Message-Id: <[e-mail]>
References: <[e-mail]>
Organization: Bell Communications Research, Inc
Lines: 7

> Would it be possible to get the 870412 version via the internet??  Can you
> slap a copy on louie.udel.edu?  -thanks.

Done. It's /pub/ka9q_all.tar.Z, with a link to /pub/870412.tar.Z, both
available by anonymous ftp to louie.udel.edu.

Phil


17-Apr-87 08:14:53-EDT,1014;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 17 Apr 87 08:14-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 07:29:32 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 07:29:13 EDT
Message-Id: <[e-mail]>
Received: by AMC-HQ via xmm1;  17 Apr 87 6:06 EST
Date:     17 Apr 87 6:56:15-EST (Fri)
From: Dbennett@xmm-plexus01
To: [e-mail]
Subject:  Re: Packet Addressing Schemes

Reference Pauls comments about packet switching address's I am in favor
of using the Grid and the Call sign combination. If you will notice the
USA-PKT listing I publish contains the Grid when the operator is able to
give it to me. The Grid will get you into the ball park while the call
sign will get you your front row seat.  All Amateur Packet address
should be as follows (FM18ioK4NGC). That will get you into my area
and right to my door step.
17-Apr-87 09:40:55-EDT,2434;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 17 Apr 87 09:40-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 08:45:45 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 08:45:33 EDT
Received: from enea.UUCP by seismo.CSS.GOV (5.54/1.14) with UUCP
    id AA14504; Fri, 17 Apr 87 08:44:10 EDT
Received: by enea.se (5.51/1.31)
    id AA09976; Fri, 17 Apr 87 14:37:26 +0200 (MET)
Received: by kuling.UUCP; Fri, 17 Apr 87 14:27:23 -0100
Message-Id: <[e-mail]>
To: [e-mail]
Subject: RFC822 for W0RLI/WA7MBL systems
Date: 17 Apr 87 14:27:20 N (Fri)
From: Anders Klemets <enea!kuling![e-mail]>

The W0RLI and WA7MBL mailbox systems are getting more and more uncompatible
with each other. There are not only different commands but also different
methods of forwarding messages between systems. The former has implemented
a "Cc:" field, the latter has a "Bulletin ID:". I think the original intent
was to have a standard that all packet BBS'es would follow.
Then why not stick to RFC822? That would have several advantages:
compatibility with the TCP/IP packet package, compatibility with other
networks like USENET, mail could be processed with other existing programs,
and so on. Introducing subdomains would facilitate routing. Mailing
lists could be used or even better: News style header lines could be
used, making it a real distributed conferencing system.

The main disadvantage of RFC822 header lines is that they are quite lenghty.
But when people are reading mail they could be presented with just a
few brief lines. The rest of the header lines would be for "debugging
purposes" and for following the standard.
I think that if a lot of header lines, e.g. "Received:" would be abbreviated
or even ignored it would still be compatible with the standard.
When BBS'es forward to each other time could be saved by sending the
messages in a compressed format. Or at least a simple protocol to
compress the size of the header lines could be used.

Or should we perhpas implement X.400 instead and use a program to
translate the header lines when we want to forward messages to networks
using RFC822?

--
    [e-mail]
    Anders Klemets, Sikvagen 51, S-135 41 Tyreso, Sweden
    Phone: [phone]
    Packet: SM0RGV @ SK0TM
17-Apr-87 14:18:10-EDT,5385;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 17 Apr 87 14:18-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 12:21:58 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 12:21:42 EDT
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA26075; Fri, 17 Apr 87 07:48:07 PST
Return-Path: <gatech!gt-eedsp![e-mail]>
Date: 17 Apr 87 13:05:19 GMT
From: gatech!gt-eedsp![e-mail] (Owen Adair)
To: [e-mail]
Subject: Hot Stuff!
Keywords: Wow!
Message-Id: <[e-mail]>
Distribution: na
Organization: School of Electrical Engineering, Ga. Tech, Atlanta, GA  30332
Lines: 109




Subject: Where oh WHERE is my high speed DIGITAL???
           (with apologies to WB4JFI)

Reported by: Doug, KD4NC, GRAPES (Georgia)

On April 11,1987 at 5 p.m. the first (as far as we know) Amateur Packet Radio
QSO at 56KB was completed between WA4DSY and KD4NC over a path of 17 miles
on 430 Mhz. The QSO was error free.

The R.F. Modem was designed and built by Dale (WA4DSY) over the last
18 months.  The R.F. gear has been working for some time, the biggest problem
was in obtaining useful packet digital signals at the modem's rated speed.

Here are some specifics on the modem.

       WA4DSY 56 Kilobaud RF Modem Specifications


Frequency       Determined by crystal in Modem and Transverter
      type used.
      At present Microwave Modules MMt 432/28S transverters
      are being used during our trials. 220 MHZ transverters
      have been used with equally good success.
      144Mhz transverters are available, 902 Mhz should be available
      from the manufacturer at a later date.


Output power   6 watts

Bandwidth       70 Khz  (can be easily changed to 9600 baud
      at a lower bandwidth for LAN use)

Modulation       Bandwidth limited MSK
         Generated by digital state machine
         Frequency shift = 14 KHZ  (1/4 baud rate)
         Phase shift = +/- 90 degrees for each bit
         Amplitude variations = 3 DB

Transmitter      Exciter operates at 29 Mhz and 1 milliwatt
         Crystal controlled carrier is modulated by
           two double balanced modulators (1496).
         Bandwidth limited modulation waveforms generated
            by Digital state machine.
         MMT 432/28 transverter used to convert 29 Mhz
              to 433 Mhz.

Receiver         Sensitivity 1 uV with low error rate
         1st IF 29 Mhz
         2nd IF 10.7 Mhz
         3rd IF 455 Khz
         uses custom L-C 70 Khz wide 455 Khz IF filter
         Demodulation by MC3359 quadrature detector chip


Data format     synchronous

Scrambler     X =  X^-17 + X^-5 + 1  (17 Bit shift register
                       with taps at 17 & 5 )

Interface TTL/CMOS       1.   -RTS    Request to send (PTT)
             2.    RXD    Received data
             3.    RXC    Receiver clock
  9 pin D connector      4.    TXC    Transmitter clock
   on test units         5.    TXD    Transmit data
             6.    GND    Ground
             8.   -CD     Carrier detect

The connection was carried out between two computers running
KA9Q Internet software using the K3MC KISS code running in a TNC-2 clone
as modified by WA4DSY. The changes were necessary to increase the
throughput from the design max of 19200
(as designed by Mike) to handle 56KB on the radio link.

The async KISS connection to the P.C. was operated at 19200 due to
limitations in the host code (fixable) and the bit rates available in the
TNC clone. This is still quite useful since several network nodes
"see" the shared 56KB channel as a non-shared 19200 channel.

Work continues on a board to replace the TNC entirely, since the design
uses very few of the TNC's features, this board with changes in the
Internet code should allow us to speed up the KISS connection to the host.

Work also continues on the 8530 driver and several 8530 boards to allow
connection of the modem directly to the P.C.

The modem is implemented on three (soon to be four when the processor board is
done) double sided P.C. boards. The 432 transverter costs $300 and parts
cost for the remainder of the circuit is estimated at $200 bringing
the total cost of a 56KB terminal to $500+.
The circuit boards are not yet available. An announcement will
be made when arrangements have been completed.

GRAPES (Georgia Radio Amateur Packet Enthusiasts) will install a test
link using Dale's modems between the two IP switches planned for
Atlanta Metro District East and West Atlanta LAN sites.


****************************************
I will accept responses to this posting.
See .signature....
****************************************
--
Owen Adair, Digital Signal Processing Lab, Ga. Institute of Technology
uucp ... !{akgua,allegra,hplabs,ihnp4,seismo,ulysses}!gatech!gt-eedsp!owen
Disclaimer: My employer is not responsible for, nor does it care, what I
        say here or anywhere else.


17-Apr-87 14:32:28-EDT,2116;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 17 Apr 87 14:32-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 12:51:20 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 12:51:01 EDT
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA26852; Fri, 17 Apr 87 08:14:08 PST
Return-Path: <somewhere![e-mail]>
Date: 17 Apr 87 14:21:53 GMT
From: [e-mail] (Louis A. Mamakos)
To: [e-mail]
Subject: Re: (none) [mixing landlines & packet radio]
Message-Id: <[e-mail]>
References: <[e-mail]> <[e-mail]>
Reply-To: [e-mail] (Louis A. Mamakos)
Organization: University of Maryland, College Park
Lines: 28

In article <[e-mail]> [e-mail] (Ralph Hyre) writes:

>What about the reverse? (using non-amateur facilities for amateur services)
>Suppose I run a packet BBS which needs to get a message out, and the local
>digipeater is down.
>
>1) Would it be OK to call another packet station using a modem?
>2) How about allowing users (licensed amateurs) to dial up and send/receive
> messages which may go over packet?
>
>(I assume that remote sysops calling up are OK, since it's like a repeater
>control link or something which there is precedent for.)
>--
>                                       - Ralph W. Hyre, Jr.
>

The so-called "wormhole" between the San Francisco, CA and Washington, DC
area (WB6FFC-1, WA3YMH-1) uses a (donated) commercial satellite channel.  I
didn't see any problems with this as the channel in use is run by a Common
Carrier.  Is this any different than have remote receivers for a repeater
linked with telephone lines?

I think that we would be stupid to overlook obvious solutions (like $20/mo
for a telephone) line and use elaborate RF techniques when they're really
not warranted.  Save it for the hard/expensive case.

Louis A. Mamakos  WA3YMH    Internet: [e-mail]
University of Maryland, Computer Science Center - Systems Programming


17-Apr-87 18:25:37-EDT,1819;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 17 Apr 87 18:25-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 16:55:06 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 16:54:48 EDT
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA26944; Fri, 17 Apr 87 08:15:32 PST
Return-Path: <somewhere![e-mail]>
Message-Id: <[e-mail]>
Date: 17 Apr 87 14:24:47 GMT
From: [e-mail] (Louis A. Mamakos)
To: [e-mail]
Subject: Re: Packet Addressing Schemes
References: <[e-mail]>
Reply-To: [e-mail] (Louis A. Mamakos)

In article <[e-mail]> Dbennett@xmm-plexus01 writes:
>Reference Pauls comments about packet switching address's I am in favor
>of using the Grid and the Call sign combination. If you will notice the
>USA-PKT listing I publish contains the Grid when the operator is able to
>give it to me. The Grid will get you into the ball park while the call
>sign will get you your front row seat.  All Amateur Packet address
>should be as follows (FM18ioK4NGC). That will get you into my area
>and right to my door step.

How does this work when I drive to the moutains or the beach for a couple of
weeks during the summer for my vacation?  How about mobile operation?  I
don't want to have multiple call signs.

I think, that eventually, you will need a combination of dynamic address
assignment for the "LAN" that you are currently in, along with a
distributed name server to resolve your call to it's current address.


Louis A. Mamakos  WA3YMH    Internet: [e-mail]
University of Maryland, Computer Science Center - Systems Programming


17-Apr-87 21:33:45-EDT,1068;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 17 Apr 87 21:33-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 20:45:22 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 17 Apr 87 20:45:06 EDT
Received: by umix.cc.umich.edu (5.54/umix-2.0)
    id AA13032; Fri, 17 Apr 87 20:46:12 EDT
Date: Fri, 17 Apr 87 20:37:36 EDT
From: [e-mail]
X-Notice: Our machine name has changed to UM.CC.UMICH.EDU from UMich-MTS.Mailnet
To: [e-mail]
Message-Id: <[e-mail]>
Subject: Re: Packet Addressing Schemes

Why not treat callsigns as arbitrary 'host' names...  Completely
uninvolved in the addressing, except on those machines capable
of looking the name up somewhere (perhaps another machine?)
If you'd like, perhaps have a <callsign>:<grid> form, for making an
initial routing decision, but don't force the location to be part of the
routing address.

--- Richard Conto
    [e-mail]
18-Apr-87 13:38:14-EDT,2507;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 18 Apr 87 13:38-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 18 Apr 87 12:41:35 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 18 Apr 87 12:41:25 EDT
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA21405; Sat, 18 Apr 87 09:40:11 PDT
Return-Path: <esosun!ucsdhub!jack!man!sdiris1![e-mail]>
Message-Id: <[e-mail]>
Date: 18 Apr 87 05:17:52 GMT
From: esosun!ucsdhub!jack!man!sdiris1![e-mail] (Robert Sanders)
To: [e-mail]
Subject: Re: (none) [mixing landlines & packet radio]
Summary: interties...
References: <[e-mail]> <[e-mail]>

In article <[e-mail]>, [e-mail] (Ralph Hyre) writes:
> What about the reverse? (using non-amateur facilities for amateur services)
> Suppose I run a packet BBS which needs to get a message out, and the local
> digipeater is down.
> 1) Would it be OK to call another packet station using a modem?
> 2) How about allowing users (licensed amateurs) to dial up and send/receive
>  messages which may go over packet?
> (I assume that remote sysops calling up are OK, since it's like a repeater
> control link or something which there is precedent for.)
>                                       - Ralph W. Hyre, Jr.
> Copyright (c) 1987 by Ralph W. Hyre, Jr.
The FCC rules on this situation are a result of the Autopatch systems
which used "reverse-patch" to let phone callers activate the repeaters..
  FCC says that UNDER NO CIRCUMSTANCES may a NON amateur do ANYTHING which
will result in a signal on-air unless a ham first examines the input.

That is, for packet, if your system is accessable by modem, it MUST be
used only by hams, with password access or some other protection against
non ham use.

FCC has not to my knowledge ever cared about ham comms being relayed via
common carriers, so use of a modem inter-bbs link should be fine, as long
as it cannot be used to insert data by a non-ham.

The rules on relay of phoneline bbs messages to a ham calling via packet
are unclear, but the control operator of the bbs radio is responsible for
the content, as thus, legally, would be wise to allow only screened data
to be accessable on-air. (probably the FCC will require this, if not already)

--
Skip Sanders :  sdcsvax!ucsdhub!jack!man!sdiris1!res
Phone : [phone] (evenings)


18-Apr-87 14:15:17-EDT,2507;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 18 Apr 87 14:15-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 18 Apr 87 12:41:35 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 18 Apr 87 12:41:25 EDT
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA21405; Sat, 18 Apr 87 09:40:11 PDT
Return-Path: <esosun!ucsdhub!jack!man!sdiris1![e-mail]>
Message-Id: <[e-mail]>
Date: 18 Apr 87 05:17:52 GMT
From: esosun!ucsdhub!jack!man!sdiris1![e-mail] (Robert Sanders)
To: [e-mail]
Subject: Re: (none) [mixing landlines & packet radio]
Summary: interties...
References: <[e-mail]> <[e-mail]>

In article <[e-mail]>, [e-mail] (Ralph Hyre) writes:
> What about the reverse? (using non-amateur facilities for amateur services)
> Suppose I run a packet BBS which needs to get a message out, and the local
> digipeater is down.
> 1) Would it be OK to call another packet station using a modem?
> 2) How about allowing users (licensed amateurs) to dial up and send/receive
>  messages which may go over packet?
> (I assume that remote sysops calling up are OK, since it's like a repeater
> control link or something which there is precedent for.)
>                                       - Ralph W. Hyre, Jr.
> Copyright (c) 1987 by Ralph W. Hyre, Jr.
The FCC rules on this situation are a result of the Autopatch systems
which used "reverse-patch" to let phone callers activate the repeaters..
  FCC says that UNDER NO CIRCUMSTANCES may a NON amateur do ANYTHING which
will result in a signal on-air unless a ham first examines the input.

That is, for packet, if your system is accessable by modem, it MUST be
used only by hams, with password access or some other protection against
non ham use.

FCC has not to my knowledge ever cared about ham comms being relayed via
common carriers, so use of a modem inter-bbs link should be fine, as long
as it cannot be used to insert data by a non-ham.

The rules on relay of phoneline bbs messages to a ham calling via packet
are unclear, but the control operator of the bbs radio is responsible for
the content, as thus, legally, would be wise to allow only screened data
to be accessable on-air. (probably the FCC will require this, if not already)

--
Skip Sanders :  sdcsvax!ucsdhub!jack!man!sdiris1!res
Phone : [phone] (evenings)


19-Apr-87 17:07:55-EDT,1743;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 19 Apr 87 17:07-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 19 Apr 87 16:07:39 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 19 Apr 87 16:07:26 EDT
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA16376; Sun, 19 Apr 87 13:06:00 PDT
Date: Sun, 19 Apr 87 13:06:00 PDT
From: [e-mail] (Clifford Neuman)
Return-Path: <[e-mail]>
Message-Id: <[e-mail]>
To: [e-mail]
In-Reply-To: [e-mail]'s message of 10 Apr 87 18:37:28 GMT
Cc: [e-mail]
Subject: Frequency Coordination on Packet (DO WE NEED IT!!!!!)

    Date: 10 Apr 87 18:37:28 GMT
    From: [e-mail]  (Ralph Hyre)
    Subject: Re: Frequency Coordination on Packet (DO WE NEED IT!!!!!)
    To: [e-mail] [Intentionally moved to packet-radio]
    ...
    I also hope there will translating 'gateways' between the AX25/Net-ROM and
    TCP/IP portions of the network, particularly for BBS systems.  Existing
    networks like the MIT internet have this to translate between Chaosnet
    Protocols and TCP/IP.

I don't know if there is much of a need for direct translation.  It
seems that it would be acceptable for certain BBSs to continue to
support the existing AX25 level 2 connects.  Once connected, the user
is then on a host that can also support the IP based protocols.  Thus,
by logging into the BBS, the user is able to use IP based protocols
for sending mail, and even for further connects to remote hosts that
only support IP based protocols.

    ~ Cliff

22-Apr-87 00:44:05-EDT,1810;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 22 Apr 87 00:44-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 21 Apr 87 23:06:37 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 21 Apr 87 22:23:32 EDT
Received: by june.cs.washington.edu (5.52.1/6.2)
    id AA13901; Tue, 21 Apr 87 19:22:16 PDT
Return-Path: <pyramid!bigbang!crash!winfree![e-mail]>
Message-Id: <[e-mail]>
Date: 20 Apr 87 14:32:35 GMT
From: pyramid!bigbang!crash!winfree![e-mail] (Bdale Garbee)
To: [e-mail]
Subject: KA9Q Software updated on SIMTEL20

With many thanks to Keith Petersen, the 870412 release of NET.EXE and
associated stuff (the full source distribution) is now available on
SIMTEL20 on the Arpanet.  Here's the information that Keith sent me:

- - - - - - - - - -
Bdale, I got the tar files from udel and made ARCs for SIMTEL20.  This
is the entire 870412 release.  Thought you'd like to know so they
could be announced to the packet-radio newsgroup.

Filename                        Type     Bytes   CRC

Directory PD:<MSDOS.PACKET>
870412.ANN.1                    ASCII     5001  8F2CH
KA9QREAD.ME.2                   ASCII     4287  999DH
KA9Q_BM.ARC.2                   BINARY    5255  9728H
KA9Q_DOC.ARC.2                  BINARY   40202  9576H
KA9Q_EXE.ARC.2                  BINARY   61952  5010H
KA9Q_SRC.ARC.2                  BINARY  177503  3B24H
KA9Q_TNC.ARC.2                  BINARY  131397  C494H
- - - - - - - - - -

Now, does anyone have any good ideas about BITNET access?  That's a bit
out of my experience, and lots of folks are asking...
--

Bdale Garbee, N3EUA             phone: [phone] h, 303/590-2868 w
uucp: {bellcore,crash,hp-lsd,hpcsma,ncc,pitt,usafa,vixie}!winfree!bdale
fido: sysop of 128/19           packet: n3eua @ k0hoa, Colorado Springs


22-Apr-87 14:56:35-EDT,648;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 22 Apr 87 14:56-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 22 Apr 87 13:55:00 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 22 Apr 87 13:54:46 EDT
Received: from CheninBlanc.ms by ArpaGateway.ms ; 22 APR 87 10:51:33 PDT
Date: 22 Apr 87 10:51:23 PDT (Wednesday)
Subject: MYazdy.es,
To: [e-mail]
From: [e-mail]
Cc: [e-mail]
Message-Id: <870422-105133-3687@Xerox>

Please delete this station from your mailing list.

    Thank You,
    MYazdy
22-Apr-87 18:51:05-EDT,962;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 22 Apr 87 18:50-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 22 Apr 87 15:15:40 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 22 Apr 87 15:14:49 EDT
Message-Id: <[e-mail]>
Received: by AMC-HQ via xmm1;  22 Apr 87 15:01 EST
Date:     20 Apr 87 6:56:54-EST (Mon)
From: Dbennett@xmm-plexus01
To: [e-mail]
Subject:  Re: Packet Addressing Schemes

Dont know why the <Callsign>:<Grid> concept wont work. Gator Digis in
Fla are using <AreaCode>:<3 digit city code> 703WOD would be Woodbridge,
Va.  As for CallSign and Grid all you would have to do is type in
C K4NGC via FM18ioK4NGC. The Packet switch would know where that location
would be.  There has to be a look up table at the Packet Switches so that
they know how to route the connect.