| |
K0CQ > HELP 16.10.04 11:02l 31 Lines 1445 Bytes #999 (0) @ WW
BID : 23402_W0AK
Read: GUEST
Subj: Re: Help with white pages pse.
Path: DB0FHN<DB0MRW<DB0WUE<DK0WUE<GB7FCR<ON0AR<IK1ZNW<VA2HAR<N1UAN<WB1CHU<
W1GMF<W1ON<W1ON-5<K1UOL<WB3DTG<N0RVX<W0AK
Sent: 041014/1640 23402@W0AK.#CIA.IA.USA.NOAM $:23402_W0AK
From: K0CQ@W0AK.#CIA.IA.USA.NOAM
To : HELP@WW
The details of white pages hierarchical addressing have been worked out by
agreement between sysops of forwarding BBS. Often the substate (begin with #)
segments are based on available BBS and forwarding paths rather than strictly
on geography. Sometimes in the past mountains interfered with forwarding by
zip code or grid.
These forwarding details are properly cared for in individual BBS forwarding
configuration files.
There probably is some listing of the known hroutes gathered somewhere on
tapr.org.
Many sysops, especially those using internet have neglected using hroutes
preferring to splatter messages hither and thither and neglecting to keep up
message and bulletin identifications so that duplicates and massive losses
occur.
Properly used Hroutes cause bulletins to go to neighboring forwarding partners
working from the country entry, then the state entry, then the subdivisions
within the state. That way global forwarders need only know their local
details and the country forwarding partners. Their local forwarding isn't
needed by the rest of the world. State forwarders only know their connections
to the world and to their state bbs and probably don't have to consider local
forwarding paths to adjacent states providing the adjacent state has a
forwarding gateway.
73, Jerry, K0CQ @ W0AK.#CIA.IA.USA
Read previous mail | Read next mail
| |
