Articles

• Souvestre and Frezberg
• Musings & Meanderings
• No Confidence Called Against ZEC by RECC

Souvestre and Frezberg

[EDITOR'S NOTE:

The following was a message posted by John Souvestre in the Z1C Echo, and as noted, the request to publish this in the FidoNews is within.

However, since articles and messages are generally sent through the FIDONEWS echo or by one of the regular mail services, it was not noted in time for last week's issue.

In the interest of balance, the response to this message is also included.

- Editor]

* Original In : Z1C
* Original To : Zorch Frezberg, 1:205/1701
* Original From: John Souvestre, 1:396/1
* Original Date: May 31 04:51

Hello Zorch (aka Snoopy).

JS> So you contend that the content of the message is what allows a
JS> routing hub to disclose it. I don't see anything like that in
JS> P4.

ZF> Then on what grounds did you try to excommunicte Roger
ZF> Etheredge, ...

It had nothing to do with the CONTENT of a message.

JS> It's clear why Bob Kohl made you a RHub. He wanted to have
JS> access to the mail which would be routed through your system.

ZF> Which would make what difference compared to _your_
ZF> interference ...

Yes, you and Bob Kohl have long told lies about my system. Now we see that it is you and Bob Kohl who read and disclose in-transit netmail. The truth comes out finally.

Print this in FidoNews, why don't you? Tell the world that Bob Kohl, NC/RC/NEC/REC/ZEC, has been show to disclose in-transit routed netmail on two recent occasions. Tell the world how you, his RHub, support him in these actions.

John

-!- Squish/386 v1.11
* Origin: Southern Star - sstar.com - V.32b/V.34+ - 504-885-5928 - (1:396/1)

### 30 ###

* Original In : Z1C
* Original To : John Souvestre, 1:396/1
* Original From: Zorch Frezberg, 1:205/1701
* Original Date: May 31 19:39

In a msg on <May 31 04:51>, John Souvestre of 1:396/1 writes to Zorch Frezberg:

JS>> So you contend that the content of the message is what
JS>> allows a routing hub to disclose it. I don't see anything
JS>> like that in P4.
ZF>> Then on what grounds did you try to excommunicte Roger
ZF>> Etheredge, ...
JS> It had nothing to do with the CONTENT of a message.

On the contrary, John. Or did you lose your copy of the Policy Complaint that you filed over this?

JS>> It's clear why Bob Kohl made you a RHub. He wanted to have
JS>> access to the mail which would be routed through your
JS>> system.
ZF>> Which would make what difference compared to _your_
ZF>> interference ...
JS> Yes, you and Bob Kohl have long told lies about my system.

And what lies are these, John? Or are you focusing _everyone_else's_ comments about your system and trying to blame myself and Bob Kohl over them?

If you did not interfere with the distribution of FLAME, then who did?

If you have proof that Brent Hamm 'crashed' the Gateway, where is it?

If you have no interest in Regional administration, why did you fight so hard to keep the Region 10 echoes flowing _through_ your system?

JS> Now we see that it is you and Bob Kohl who read and disclose
JS> in-transit netmail. The truth comes out finally.

I'll expect you to present proof of your claim that I am reading and disclosing in-transit netmail, John.

JS> Print this in FidoNews, why don't you? Tell the world that Bob
JS> Kohl, NC/RC/NEC/REC/ZEC, has been show to disclose in-transit
JS> routed netmail on two recent occasions. Tell the world how you,
JS> his RHub, support him in these actions.

A little late, John...it will have to go in next week's issue, though you may wish to re-write it to sound a little less petulant.

-zf-

-!- msgedsq 2.1
* Origin: Fido Bites It's Masters...What Next? 209-251-7529 (1:205/1701)

### 30 ###

Musings & Meanderings
by Lisa Gronke, 1:105/9
lisa@psg.com

IDEAS FOR FIDONET IN ROTARY ORGANIZATION?

Last weekend Ed and I attended the Rotary District 5100 conference in Pendleton, OR.

Rotary is an international organization, larger and more extensive than FidoNet, which operates almost entirely with unpaid elected official who serve for ONE year (there is a salaried secretary-general and small staff in the international headquarters in Evanston, IL). The entire Rotary administration, worldwide, turns over on 01-July each year. This has always amazed me. How can Rotary achive continuity?

Primarily by electing the key official at each level a year in advance.

Rotary is organized geographically (although individuals can join any club).

Club            District           International
Club President  District Governor  Governor General

Each Rotary Club level has a BOD consisting of the officials above (serving for the current year), the elected officials, President-Elect & Governors-Elect (who will serve the following year), the past President or Governor, plus the usual VP, Secretary, Treasurer and committee chairmen. It is, more or less, eighteen months from the vote for a President-Elect until he or she takes office as Club President on the first of July. Past Presidents are only on the BOD for one year, although they continue to be honored in various ways (Rotary is big on ribbons <g>).

NODELIST

There is an interesting change occurring in the "Net" 1:1 section of the nodelist. For years, the Zone 1 RECs have had redundant 1:1/21x nodelistings. For example, Bob Seaborn, REC of Region 17, was 1:1/217. Now only 1:1/212, 214, 215 & 219 are left. The R10EC position is currently vacant and the others are using redundant entries in the regional segments. For example, Bob Seaborn is 1:17/1. IMHO, it is best to use the REC's "real" node number which can be found in backstat.na.

Once upon a time the regional SDS (file echo) distributors had 1:1/31x nodelistings, but those were dropped many years ago.

ASIA

The Zone 6 segment of the nodelist continues to be a disaster area.

There have been nodelist changes in Region 62 (Taiwan), Region 63 (Japan) and Region 64 (Philippines), including a new R62C, Chinian Wang (replacing Philip Jones) and a new R63C, Shinji Nishikawa (replacing Bill English), so I am assuming those regional segments are current.

A new Net (6:759, Pakistan) has been added in Region 64 (Philippines)!!!

There have been no changes in Region 60 (Singapore, Malasia, Thailand, India), Region 61 (Hong Kong & Macau), Region 65 (China) or Region 66 (Korea) for AT LEAST five months and probably much longer.

I can only assume that these four RCs are MIA.

Region,60,ASEAN_Region,SINGAPORE,Wing_Lee,65-2410418
Region,61,REGION_61_COORDINATOR,HONG_KONG_&_MACAU,R61C,852-2505-2499
Region,65,Fido_Mainland_China,Beijing,Roy_Luo,886-2-727-6059
Region,66,FidoNet_Korea,Seoul_(Yongsan),Bill_Harms,82-2-7918-7032,9600

In the case of India (Net 6:606, Region 60), there are "new" nodes who were assigned node numbers by their NC *MORE THAN A YEAR AGO* who are not yet in the international FidoNet nodelist. Some of these nodes are echomail participants, getting feedS from Zone 1, and can be reached via routed netmail.

The Zone 6 nodelist became a controversial issue last November when Maulvi Bakar, a returning node in Malaysia, after extensive efforts to obtain a node number in Zone 6, obtained a node number in Net 1:163. Maulvi called ALL of the sysops in the 6:609 (Malaysia_Net) nodelist segment and did not find a single FidoNet mailer answering the phone. The R60C, Wing Lee, was answering FAX. Maulvi Bakar's BBS is offline, probably a victim of the Asian financial crisis; the 6:609/xxx nodes are still in nodelist.156 :-(

I don't see how anyone can initiate Policy4 amendments without resolving the Zone 6 nodelist problems first. Yo, Bob Satti! What needs to be done? I'd guess it might be cheaper to dial some of those areas from the US than from Japan. If $$$ are needed to pay for calls to establish which nodes are "on the air," I am willing to coordinate a voluntary fund raising effort for that purpose.

NODELIST TRIVIA

At least two of the 50 USA states (Montana and Alaska) have no FidoNet Nets. Montana has no FidoNet nodes; Alaska has two regional independent nodes.

DA BROKEN BIRD

On Tuesday evening, 21-Apr-98, the Galaxy 4 satellite abruptly stopped functioning. The Planet Connect 19200 C-Band and Ku-band broadcasts were both carried on that bird, yet the sattelite failure went almost unnoticed in FidoNet. Why was that? Well, the Planet Connect topology, which once accounted for 70-80% of backbone echomail traffic, now only represents about 9%. And Planet Systems Inc. seems to have responded promptly. During the first days after the G4 failure, echomail bundles were freely available for anonymous ftp from Planet Connect's Internet site. The Planet Connect broadcasts are now available from Galaxy 6, although I am not sure what someone who was setup to receive from Galaxy 4 has to do to receive from Galaxy 6.

THIS 'N THAT

On 05-Jun-98, Adrian Walker, Echolist Coordinator, etc., announced:

• that the June Elist would come out this weekend, Jun 6-7th
• that the June Elist would be the last he would publish
• that he (Adrian) would be pulling the plug on FidoNet in the next week or two

• Looks like Adrian's "backbone robot" and "backstat robot" functions will be taken over by John Souvestre.
• Looks like Adrian's RHub functions will be parted out among the other Region 17 RHubs.
• Dunno what will be happening to Adrian's Elist functions.

You done good with the Elist, Adrian!

Without fanfare, James Ray replaced Bruce Bodger as R19C a few weeks ago. I believe Region 19 has an annual RC election. I dunno who else ran, but incumbent Bruce Bodger was not a candidate (citing additional travel demands of his job).

BOFAQ Q21 says:

"The term of the present OBO is 1 year and expires on June 10, 1998." Butch Walker is the present OBO, and if there is an OBO election going on, it is a well kept secret.

OFF TO CHICAGO

Not one, not two, but three family members in Chicago have narrowly escaped the clutches of the grim reaper. Now that the Metro election is over (Ed lost; cf http://www.co.clackamas.or.us, click on Election Results), we're leaving Tuesday for 10 days in the city of my birth.

Posted in RGN17, Z1_BACKBONE, Z1C, FN_SYSOP; Submitted to FidoNews. Echomail replies may expire before I return, so forward a netmail carbon copy.

Lisa

### 30 ###

No Confidence Called
Against ZEC by RECC
submitted by Ben Hamilton, R19EC

[EDITOR'S NOTE: The following was submitted without title or any other information. While it is believed to be from the legitimate source, it was not presented as an 'official' statement by the RECC, nor was it signed by them.
-Editor]

> If the RECC concludes that the ZEC is not active, ineffective
> in his/her job or is just not taking care his/her
> responsibilities; they may take a vote of no-confidence. If
> the vote of no-confidence passes with a 2/3rds majority, the
> RECC will refer this issue to the ZC for mediation or action
> as the Z1C sees fit.

After consulting with the sysops in their regions, the RECC recently conducted a vote on the above. The following REC's voted NO CONFIDENCE: 12, 13, 14, 15, 16, 17, 18, and 19.

That is a total of eight of the RECs, far more than a 2/3rds majority.

I will not go into the reasons for the necessity of the vote at this time. Suffice it to say that they are many.

Therefore, as stated in the ZEC duties which were recently written by Bob Kohl, this situation has been brought to the attention of the Z1C, Bob Satti, so that he can decide on the best course of action.

-Ben Hamilton, R19EC
Internet email:
sysop@compconn.net

### 30 ###