[nos-bbs] Nos improvments, interfacing to Winlink...

[Bill Vodall]

> > It would be another big step if we could also use the F1B compression
> > that Winlink, and I'm guessing AIRMAIL, is using.
> 
> I've had a few people suggest to me that since the SCS PTC is already
> doing compression internally, is there really any benefit in compressing
> the data being sent to the TNC ? Will doing so actually bog down the
> effective throughput of the PTC ? I don't know off hand.

Multiple compressions, if of equal compression strength, will indeed cause
a net increase in data size.   Still if the external compression is better we'd
gain a bit.

My comments here and for the next are for general connectivity (packet and Internet),
not specific for the SCS modems.

Telpac and Paclink are the "packet" side of the Winlink system.   If we can
match their standards it'll be a good thing.

> >so we might be able to put telpack_node right in to NOS.
> 
> I'm not familiar with telpack_node. I've been meaning to see what
> it's about, but haven't had the time. My understanding is that NOS is
> already (in a way) a form of telpack_node, so why bother ?

It is, but having an interface that Paclink can directly connect to is a good
thing.   (Hmm.  Making NOS look like a Paclink Client to a telpac server
will be another good project.)

Having an Telpac_node in NOS would also provide a winlink standard interface
for basic packet users. Fitting the standard is a good thing.    Can't be too difficult
as the Linux executable for telpac_node is only 8K.


A real simple map of Winlink.

  With the SCS modems on HF:

    client using airmail (and now nos) -> Winlink Servers or other Airmail station

  For an legacy packet interface to the same Winlink servers:

  [ WinXP box ( Outlook/Eudora - Paclink) ]  (ax25)->  Telpac -> TCP -> Winlink Servers

   Telpac there can also be telpac_node on a Linux AX25 system.

73
Bill