Hello Vladimir.

Please forgive the late reply... my ISP was down for a few days.

14 Oct 04 19:03, you wrote to me:

 VD>>> Policy (4.07) use both expression "node" and
"system"...
 VD>>> In first case not clearly purpose of ZMH - this sample imitated
 VD>>> claim, and may (must) to be remove.
 MG>> All zone mail hour requires is that during that time, all nodes be able
 MG>> to

 VD> "Nodes"? Not "systems"?
 VD> You use term "node", but I ask you to explain it!

A system is a computer or set of computers performing a task or tasks,
usually but not always run by one person.

A node is an address space in Fidonet, as listed in the Fidonet nodelist. A
system is associated with the node address, configured as indicated by the
contact and flag information listed with the node listing. A single person,
who is the official sysop (system operator) of that system is also
associated with the node address.

Every node represents a system, and a sysop. Not every system and sysop
that participates in Fidonet is a node of this network, however; but for
the purposes of Fidonet policy, only nodes which are officially listed in
the Fidonet nodelist as released by the ZC's/IC are considered a part of
this network.

 MG>> Policy does not specify that a node must receive /direct/ netmail from
 MG>> every other node in the zone, it just specifies that the node must
 MG>> accept netmail during that time. Therefore, ZMH can be defined as a
 MG>> routed netmail event.

 VD> Without ZMH - what member of FIDO must to do with netmail? He must
 VD> transfer it to another systems or no? If "no" - what he
is "node"?
 VD> He is only "end system", and he must receive mail in any
suitable time
 VD> (he is not annoying any other systems - he not connected with them, only
 VD> 1 uplink, analogue "point")! And different between
"node" and "point" in
 VD> this case only on responsible for own traffic.

He is still a node. Nodes are not required to be mail hubs. End nodes are
still valid members of this network. The difference is exactly what you
describe; a node is responsible for everything that enters this network
from his system, whereas a point is not. A point's only responsibilities
are those expected of him by his boss node. His boss node takes the
responsibility for what enters the network through his system from his
point, and his boss node controls the point's access to this network.

 VD>>> But for second case system must not only receive netmail but to
 VD>>> transfer it beyond (so systems without any downlinks must be remove
 VD>>> from nodelist)...

That is not a requirement of the nodes of this network under Fidonet
policy. Only *C's and officially nodelisted Hubs are required by policy to
even handle netmail, and they are only required to route netmail. The
actual transfer is left up to mutual agreements between the *C's and Hubs,
and the nodes they serve. Whatever transfer method or transfer times are
mutually agreeable to them are acceptable under policy.

 VD> As I write previos - same question: is it "node" or
"end system" at
 VD> netmail route? "Node" must distribute mail to another
systems, "end
 VD> system" must only receive mail and not send it beyond.

Fidonet nodes are not defined as being required to distribute mail to other
systems, and never have been. The only reason the word "nodes"
was used was that in the beginning, the network was built around BBSes, and
each node had dial-up users. This is very much like dial-up ISP's which
have users and are nodes on the internet, while the dial-up users
themselves are generally connected through the node via PPP or Slip/Slurp
connections, and while online, are not considered true internet nodes.

The models are very similar, and that is because Fidonet and the Internet
grew up alongside each other, and many of the same people were involved in
both types of networking. The main difference is the levels of hardware and
software automation of the Internet, mainly brought on by commercial
interest in development, while Fidonet being strictly non-commercial, still
relies heavily on human interaction.


--- GoldED/W32 3.0.1