| |
PA2AGA > HDDIG 12.10.99 17:01l 192 Lines 7733 Bytes #-9721 (0) @ EU
BID : HD_99_257F
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/257F
Path: DB0AAB<DB0ZKA<DB0ABH<DB0SRS<DB0MW<DB0NHM<DB0SHG<DB0SM<PI8DAZ<PI8GCB<
PI8HGL<PE1NMB<EA7URC<PE0MAR<PI8VNW
Sent: 991012/1039Z @:PI8VNW.#ZH2.NLD.EU #:7523 [HvHolland] FBB7.00g $:HD_99_257
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21155 ; Tue, 12 Oct 99 09:53:32 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016351 ; Tue, 12 Oct 99 07:47:27 MET
Date: Tue, 12 Oct 99 07:44:24 MET
Message-Id: <hd_99_257F>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/257F
X-BBS-Msg-Type: B
"Articles" button, and go from there.
It describes an effective method (currently in use) to allow use of graphics
on low speed links for HTML/Packet Radio.
It works. There's a demo included. Check it out.
--
73 DE Charles Brabham, N5PVL
N5PVL @ N5PVL.#NTX.TX.USA.NOAM
http://www.texoma.net/~n5pvl
>.
------------------------------
Date: Sat, 9 Oct 1999 19:29:13 -0700
From: "Hank Oredson" <horedson@att.net>
Subject: The BBS network and tcp/ip.
A couple folks asked that I repost my specific suggestions
on how to migrate the existing BBS network to the model in
current use on the internet. Here they are again. Not well
organized, a bit of babble, but specific ideas. Would they
work in practice? I don't know (yet) but may implement some
of them and find out.
Each BBS network message type has an equivalent internet
application and protocol. For the BBS network to interoperate
with these applications and protocols we need some number
of "gateway" systems which do the appropriate translations.
1) Bulletins map to net news and the nntp protocol.
We need a set of newsgroups defined to map to/from the common
BBS network topics. One solution would be to use newsgroups
of the form alt.hamradio.<topic> where <topic> is the To:
field of the BBS message. Thus we would have, for example,
alt.hamradio.keps, alt.hamradio.sysop, alt.hamradio.all
The "gateway" servers would move messages both directions
using the obvious and simple mapping.
2) Personal messages map to standard email and the pop3/smtp protocols.
We can use the obvious address mapping. I've run this kind
of "gateway" server for years, using a version of JNOS.
It works fine, and is already available.
3) NTS messages are an intersting case. They probably need to map
to net news and the nntp protocol. We might use a newsgroup
such as alt.hamradio.nts-traffic for this purpose. In this
case the same "gateway" servers which handle 1) will suffice.
Ideas welcome from the NTS folks on how we might handle this.
Note that we do not need "permission" from NIS or anyone else to
begin to implement this capability. Everything exists within the
ham radio network and not within the internet per se. The model
is designed to be compatible with internet standards for the obvious
reason: those standards exist and are well tested. We should use them.
For some of the standards, file transfer protocols also exist. For
example email has pop3 and smtp as network data transfer standards,
and RFC-822 (and it's various updates) provide a guide to the
construction of a bulk transfer protocol. We already use this protocol
as import/export between BBS systems of various kinds. The needed
extensions to the standard set of headers are documented in the
BBS specification. For net news two standard transports exist. One is
a bulk file transport using the "ihave/iwant" scheme similar to
what is called "X forwarding" in the BBS network. The needed mappings
are obvious and should be simple to implement.
All the above would require only a small amount of fairly simple
programming effort on the part of the authors of the ham radio
tcp/ip programs, and very little effort on the part of the authors
of the ham radio BBS programs. The hard work is deciding on the
details of how the mappings will work, and setting up enough
gateway servers to attract users.
One advantage of this scheme is that we could use it to link
existing news groups in the internet directly to the ham radio
BBS network, with bidirectional exchange of messages. Some might
consider this a disadvantage because of the obvious possibility
of abuse by both hams and non-hams. This possibility should not
get in the way of creating and testing the technology.
There is an interesting technique we could use to do this integration.
If each "gateway" server ran a web server with a standard middleware
API to a local database, then the task of programming the needed
applications would be fairly simple. What applications are needed?
Those required for the administration of the "gateway" server itself,
for example, to maintain mappings, deal with exceptions, and all the
other "sysop" type of activities.
One could even consider creating a "regular ham radio BBS" using the
capabilities of the web server. This has in fact been done, several
times, by various hams. Perhaps those hams might consider making their
work available to others in the ham radio network as well as on the
internet. Doing so might help move the digital networking facet of
our hobby forward. i.e. "The folks using html on ham radio are headed
in the right direction."
Disclaimer: Yes, I know the above sounds a lot like the integration
of ham radio networking with the internet. That is exactly what it is.
I hope everyone can understand the difference between taking ideas
and techniques from the internet for use in ham radio, and replacing
ham radio with the internet itself. I propose the former, and not
the later.
... Hank - W0RLI
_^___^_
\\|// / 0 O \ __
(O O) <| V |> /..\
----oOO--(_)--OOo------o000o-U-o000o------oOO--(____)--OO---
http://home.horedson.att.net
>.
------------------------------
Date: Sun, 10 Oct 1999 14:04:42 GMT
From: nomail@pe1chl.demon.nl (Rob Janssen)
Subject: The BBS network and tcp/ip.
Hank Oredson <horedson@att.net> wrote:
>A couple folks asked that I repost my specific suggestions
>on how to migrate the existing BBS network to the model in
>current use on the internet. Here they are again. Not well
>organized, a bit of babble, but specific ideas. Would they
>work in practice? I don't know (yet) but may implement some
>of them and find out.
This has all been done already. As you write, mail gateways
have existed for a long time. Bulletin-to-News gateways also
exist. There has been one operating (on a Linux system) for
years in the area over here, and I have also seen these systems
in Germany. Most likely the system is available as free software.
It works like you describe: a separate news (sub)hierarchy is
created, with groups named after the SB xxxx field in the BBS
message.
Besides the usual startup problems (id's being scrambled and thus
messages being duplicated when more of these gateways appear and
they operate bidirectionally), it seems to work fine.
Maybe you should add it to your BBS too...
Rob
--
+----------------------------------+--------------------------------------+
| Rob Janssen pe1chl@amsat.org | WWWhome: http://www.pe1chl.demon.nl/ |
| AMPRnet: rob@pe1chl.ampr.org | AX.25 BBS: PE1CHL@PI8WNO.#UTR.NLD.EU |
+----------------------------------+--------------------------------------+
>.
------------------------------
Date: Sun, 10 Oct 1999 08:08:39 -0700
From: "Hank Oredson" <horedson@att.net>
Subject: The BBS network and tcp/ip.
Rob Janssen <nomail@pe1chl.demon.nl> wrote in message
news:slrn80177q.j02.nomail@linux.pe1chl.ampr.org...
> Hank Oredson <horedson@att.net> wrote:
> >A couple folks asked that I repost my specific suggestions
> >on how to migrate the existing BBS network to the model in
> >current use on the internet. Here they are again. Not well
> >organized, a bit of babble, but specific ideas. Would they
To be continued in digest: hd_99_257G
Read previous mail | Read next mail
| |
