| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Current P5 draft |
On 13 Sep 02 08:42:40, Philip Lozier said the following to Bob Short: > Can you be more specific on the parts to which disagree? PL> The main part I disagree with is the very small percentage required on PL> the (vote) to make an ammendment be "ratified". OK. and answered in my last message. PL> I also think there should be a top level down requirement that notification PL> -IS- given on a proposal, not a best attempt made... those not responding PL> such a notification are not doing their jobs, and should be treated PL> accoridingly. How do you suppose we do that? Can you suggest how to ensure a netmail is delivered to a system which is down, or is otherwise unreachable? De we expect the IC to incur the LD costs of crash netmail to each and every RC? IF not, what happens if routed netmail gets lost or is undeliverable for some reason? Would this then invalidate the process? PL> Any *C being sent notification should be -required- to respond... putting PL> place this new system for policy updates should also include the -requireme PL> that -all- *C's participate, lest they be replaced... no replacement found, PL> their underlings be absorbed into another region/net that complies. That was discussed here, and we thought better of makeing such radical changes. This sort of change was attempted before, and resulted in dismal failure. This isn't to say that we might not get something to that effect passed in the future... just not at this time. PL> Allowing for policy changes to be effected in such a manner should not be t PL> lightly, and the days of the lazy SysOp/Node/*C should come to an end with PL> as well. I believe there are more appropriate ways of dealing with such issues outside of (yet referred to by) Policy. What a *C does/doesn't do, and the repercussions, are best left to local policies (IMHO). Bob --- GEcho 1.00* Origin: BS BBS - Get yer BS here... (1:105/38) 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: 105/38 360 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™.