| |
N1URO > FBB 23.12.20 01:00l 90 Lines 4620 Bytes #999 (0) @ WW
BID : 56780_N1URO
Read: GUEST
Subj: Routing - Was > Re: Change HR for VE2PKT
Path: IW8PGT<LU4ECL<I0OJJ<GB7CIP<N1URO
Sent: 201222/2042Z @:N1URO.#CCT.CT.USA.NOAM #:56780 [Unionville] $:56780_N1URO
I0OJJ said:
> In this moment the *networked* PBBS are 394.
F1OYP maintains the global BBS list which I see he just released today.
According to his counts, he lists 1,178 BBS of various software types.
Here alone I have *4* with LinFBB as my primary BBS. My others include
MFNOS, JNOS2, and MSYS. 3 of the 4 softwares I run I either have or I
continue to supply code for. Of course I don't need to run any of these
additional softwares but since I'm often called upon to give support it
helps to have working systems to read off of. Looks like you both were
quite off on your counts :) Of course, there may be some SKs in his
list too, I don't know I didn't go through it. I'm pretty sure that
his list omits some of those I run.
> For the other stupidities, after 20 years, I'm tired to explain
> always the same things to a people who don't understand and
> don't want to understand :(
About 5 years ago, I called for developers to gather and discuss a global
standard for BBS code/protocols/etc. The only one who replied at that time
was Maiko who was too busy to get involved. More recently he emailed me
and wished we actually did all discuss this.
Having had voice conversations via landline with W0RLI before he became SK
(for those who don't know, Hank was one of the founding fathers of the
BBS world) he'd be rolling in his grave if he saw half of some of these
threads and the only @?? we'd need would be his old @LLL group since he'd
probably rewrite them all to there :) Hank was funny like that. The remaining
village elders will remember.
Also back in the day, forwarding via axip/axudp/telnet was a shameful thing to
do. Sometimes you could get budlisted for doing such depending on how much of
a radio purist a particular sysop was - or in Hank case you made it to his
"Hall of Shame" the infamous @LLL so you either forwarded 100% via RF or
you did not forward at all. Some of us were also fortunate enough to have
a BBS on a satgate or used Pactor that we could reach or relay to so that
we could get global mail out - again 100% via RF. One positive from this was
that you could always feel safe that your country's regulations were being
followed. Another thing was that if you follow the Hierarchical addressing
it always had a very consistant flow. A message from me to someone in say
Delaware would go:
CT -> CENY -> SENY -> NNJ -> CNJ -> SNJ -> DE
Now it may go:
CT -> EU -> AF -> SA -> CA -> TX -> ME -> ... and so on. Why? If forwarding
to begin with was kept on RF as much as possible this could get restored.
We also didn't have the volume of partners either as they not only were not
necessary, we didn't need redundancy a dozen layers deep. Too much of a good
thing spoils it all. Our forwarding always went:
- RF
- *only* to our direct RF neighbors
- a single exception to a Pactor or Satgate, pref relayed via a direct
neighbor.
After all, if a Pactor or Satgate can't get mail out, then RF as a means of
transport is a failure to begin with... and that's why we all have licenses to
make best use of our RF privs.
The logic behind the final proposals for heirarchical addressing by W0RLI
(and accepted by TAPR) was to define the following and I'll use mine as
an example:
N1URO.#CCT.CT.USA.NOAM
^ ^ ^ ^ ^
1 2 3 4 5
1 - SysOp's callsign - self explanitory
2 - a specific locator similar to a GeoIP on the internet. For me it
identifies me as Central Connecticut.
3 - State/province identifier
4 - Country identifier
5 - Continent identifier not to cross over with any internet domain.
For North America, *.NA = nambia, a domain located in Africa which is
the other side of the globe. United Nations identifiers did not apply
in this schema.
By default xNOS will attempt to forward any mails ending in .na via the
global internet because it's MTA is an SMTP server not a PBBS mail server and
going to a 4-letter schema helped to protect against a default routing system
in xNOS and other systems that may also engage an SMTP server within it. The
xNOS rewrite function helps to translate SMTP mail into a PBBS mail format
which is why if you monitor sequence.seq for 1 message it uses 2 MIDs...
one for the SMTP mail and one for the PBBS conversion.
Whether a country or a continent fails to adopt or accept standards or a sysop
decides to ignore standards set by our own gentleman's agreements only
opens doors for a system to fail. Another thing to remember at least here in
the states - if you don't use your RF, Uncle Joe will insure that they take
bands away.
73 and Happiest of Holidays!
---
SendBBS v1.1 by N1URO for LinFBB
Read previous mail | Read next mail
| |
