A Case For Bundled Forwarding
As presented to the TPRS Fall Digital Symposium
Austin, Texas - October 23, 1993
A Case For Bundled Forwarding
by Charles Brabham N5PVL
The Bulletin Board Network
Despite what some would say, there is no real dividing line between packet BBS sysops and "networking guys".. If you run a BBS, you are part of the packet network; just as much as the guy who operates a node.
Many sysops operate nodes or node software such as G8BPQ. But even if you only operate BBS software and use somebody else's node to access the network, you are still a part of that network and your actions can have a major impact on how well it functions.
So as a BBS sysop, you have responsibilities that reach far beyond the confines of your BBS computer. Sysops who believe they are an "island", and have the attitude that it's "them and us" ( Networkers and Sysops ) are deluding themselves. Invariably, this delusion leads to a chaotic, inefficient network in places where it has become the accepted "wisdom".
There is only one way to separate your responsibility as a sysop from your responsibility as a networker..
Turn off your radios!
The dialogues between sysops concerning dupes, message compression, illegal messages, the newer message types, and routing standards are essentially network issues. We discuss what goes over the networks and weigh their effects, and in doing so we make descisions which affect the packet network on a local, regional, and worldwide basis.
As the main "users" ( by volume ) of the packet network, BBS sysops have a clear voice in how that network will run, and a clear responsibility.
Being A Networker
I think it's safe to say that all sysops take pride in what they do, and want to provide the best possible service to the amateur community. Many hours are put into tweaking software, scanning the incoming messages, and improving equipment. ( Many dollars too! )
But if you only expend your efforts on what goes on at your own station with no consideration of what goes on beyond it, you are only doing a half-way job. You are also a vital part of the packet network, and there is work to be done there too. Networking is a group effort involving all who are involved in it; Node operators, BBS sysops, and DX cluster sysops as well. We have to work TOGETHER in order to make it work efficiently.
The loudest carping voices, complaining about how lousy the packet network is, are invariably the "lone wolf" types. They expect everybody to co-operate except themselves. These guys, of course, have the least right to complain of all since they are most certainly "part of the problem".
What Networking Entails
When operating a BBS, you naturally want the packets to flow freely. You want to get your forwarding chores done rapidly and efficiently. When the network is very busy though, everything slows down. So what really concerns us as sysops is a thing called NETWORK LOADING.
We as sysops are probably as responsible for the level of network loading as any other group, if not more so. How we operate, and how we work together can have a major impact on network loading and largely determines how quickly the data flows over that network not only for ourselves, but for everyone else.
So what we should look for are ways to cut down on the network's load. The number of connections on the network effects that, but the greatest unnecessary load on the network related to BBS forwarding stems from redundant data.. The same information being transmitted again and again over the same section of the network.
How does this happen? Let's say the town of Centerville has three BBS's, and all three forward independently to three others in Nearville... All over the same string of nodes. In this situation, it's likely that each bulletin may be transmitted over the same network 3 times, and it could easily end up being sent back and forth twice that much! This is redundant data, the single greatest source of unnecessary network loading.
How can we cut down on all of this redundancy, and so improve throughput over those nodes by a factor of three to six?
Bundled Forwarding
Let's say that now the sysops of Centerville get together and elect one station as the Centerville HUB. The other two stations in Centerville now only forward with the new HUB station, leaving it to him to conduct all forwards with Nearville. He "bundles up" Centerville's traffic, and sends it all at once. And since he knows the Nearville stations can forward among themselves, he only forwards with one of them.
This has far-reaching consequences...
Now each bulletin goes out of Centerville onto the network ONCE instead of three to six times, and not nearly as much time is spent asking, " Do you need this message?". There is now only one connection going out over the path as opposed to the previous nine, and the network loading over that path takes a sudden drop!
Now what was a crowded path is MUCH clearer, and the result is greatly improved throughput. Instantly, and cheaply. All it took was three guys getting together and co-operating a little, and the result was that now ALL data; Bulletins, messages, NTS.. You name it. It ALL moves much faster.
Once Centerville has gotten it's act together it won't take long for the guys in Nearville to see the improvement in throughput over the network, and figure out how it was accomplished. If they get their act together too, they will be amazed at how good the previously "lousy" network can be.
It doesn't take a rocket scientist to figure out that two BBS's forwarding over a given path will generate almost no redundant data, while six or more will generate tons of it!
Having Centerville and Nearville take this enlightened approach to forwarding makes a big difference. When you consider that Farville is out there too, it's value becomes greater still. The larger the network is, the more towns and regions it will encompass, and the greater the difference bundled forwarding can make to that network's performance.
The same method pertaining to cities above can also be applied to regions of a state, or ( on HF ), regions of the country. Three or four regional hubs in a given state can distribute cross-state traffic from local hubs, and so cut down on the load on the long-haul networks. Any time we sysops can cut down on network loading, we are doing ourselves and everyone else a big favor, and doing our jobs much better.
The example above is kind of rough around the edges, but I think you can see from it how bundled forwarding works to cut down network loading, and how it can be of great benefit to all stations on that network. I think you can also see how we as BBS sysops really ARE an important part of that network, and how our actions undeniably affect it. We DO have a responsibility here, and we should be responsible!
Hub Stations
It's up to each local group of sysops to figure out which local station should be their HUB (and it's backup), but here's some things to consider...
The HUB should first have a good reliable path to the nodes involved, and to the other local BBS's. Since the HUB will be busy forwarding much of the time, it possibly should be the local BBS with the SMALLEST user-base.
A track record of good reliability should be considered, and this means being tolerant and even-tempered as well as having good equipment and software. A "lone wolf" type would be a very poor choice for a HUB station, since co-operation is so important here.
Since the HUB will be passing bulls and messages for everyone, he shouldn't be too particular about what kind of bulletins he accepts or passes on. A HUB should handle ALL legal message types, even if he thinks they are trivial or unnecessary.
It's More Than Just Networking
I haven't mentioned my favorite part about bundled forwarding yet. What I really like about it is how it means that more is accomplished by everybody doing less work! A tangle of complicated forwarding files becomes greatly simplified, while throughput over the network is greatly enhanced. Non-HUB stations enjoy the greatest benifit.
Yes, your messages may go through one more BBS than before in order to get to Farville, but they will going through a path which is suddenly much, much clearer. Overall, they will get there quicker and more reliably anyway, since they won't be having to wait so much for a bit of clear spectrum.
Take A Look
Monitor your local network. If you see yourself and several other stations competing for a chance to forward with several stations in "Farville", get together with the other local sysops and discuss bundled forwarding for your town.
The users will be impressed by the improved service, and it will make the packet community in your town look a lot smarter to the guys in the next 'burg.
Check it out!
Please send comments, suggestions to:
Charles Brabham N5PVL
E-MAIL: n5pvl@texoma.net
PACKET: N5PVL @ N5PVL.#NTX.TX.USA.NOAM