| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | P4 Draft (ver. 5) |
Hello Thom! WD>> there are allways cases which are not completely defined by the policies WD>> and where the *C in charge has to interpret the written policy or decide WD>> completely on his/her own. TL> Correct, and that's always an area that demands very careful scrutiny. Indeed. On the one side, there should be means to get rid of a *C badly doing wrong. On the other side, an *C needs enough elbow room. If he is so narrowed that he cannot do wrong, he as well cannot do good. WD>> Not directly but via their NCs, RCs and ZCs. TL> I wish it were that direct.... That depends. TL> but the NC's have no direct path to the RCs... Here the nodes and the NCs have according to our Regional Policy. TL> so it's not always that easy for a lower level to rectify a problem at a TL> higher level...and I believe that's by intent. As I told above. It should not be too easy to act against some *C, but as well not too difficult. As it is now, in general it works well. greetings, Werner --- GED 3.0.1-dam3* Origin: Among our weaponry there are such things as: (2:2487/9504) SEEN-BY: 10/3 17/1 67 106/2000 6018 109/568 114/59 128/148 187 139/625 140/0 SEEN-BY: 140/1 2 16 31 153/307 7715 221/0 236/150 244/1111 250/501 252/171 SEEN-BY: 270/1000 292/100 854 297/11 342/5 348/105 633/267 270 757/1 772/1 SEEN-BY: 772/10 30 2613/118 3828/7 @PATH: 2487/0 3000 2476/418 2432/200 774/605 123/500 106/2000 140/1 772/1 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.