| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: NodelistGuide or FAQ |
*** Quoting Michael Grant from a message to Rick Van Ruth ***
RR> That is pretty clear to me then that the FTSC is the authority when it
RR> comes to nodelist flags.
MG> The Coordinators have /no/ say at all, eh...?
MG> The FTSC means /nothing/ if what they propose is not accepted by the *
MG> The *C's are the final authority on what will and will not be used as
MG> a flag in the nodelist, and what each flag means.
MG> The *C's have the power to make any nodelist changes they want to, and
MG> the FTSC is relegated to recording what has been accepted by them. If
MG> the FTSC ignores the wishes of the Coordinators, they become useless t
MG> this network.
Good points there. That was one of the things I learned too (although I
¨already knew it). The FTSC documents and clarifies existing standards.
They ¨also accept proposals for new ones but until in actual use someplace,
they stay ¨as 'proposals' (FSP).
Actually getting a new flag authorized for example, is done by asking
¨persmission of your own ZC. If your ZC responds favorably, then you can
try it ¨in your zone (or might be told a net or region to limit it to).
RVIA for ¨example started as a test limited to R13, then was allowed wider
spread. Later ¨the IC authorized it in the international nodelist trailer.
For an example of ¨a non-flag but similar, Z2 authorized testing of the
000- set for static IP's ¨and later Z1 took to it (after Z2 removed it I
think). Oh and lets not forget ¨RPK and NPK which Z2 needs.
All of these above would belong in an FTS document even if they arent used
by ¨every zone, because they are 'standards' and the FTSC just documents
those and ¨their correct usage. The C's actually were the ones that
started using them ¨and the FTSC just follows up.
There's a slightly bolder drive in the works just now, which is to do
further ¨clarification on which of the many IP type entry methods are 'most
preferred' ¨since obviously there are several ways to do this. I don't
think anyone would ¨mind if the IP listing portion came with a bit more on
what is the 'preffered' ¨method when there are several methods to chose
from.
While an FTS shouldnt reference an unofficial 'FAQ' there might be a way to
¨incorporate some of the base ideas from the one in the subject line. It's
been ¨posted enough for any to comment by now if there are errors in it's
¨methodology (or at least any gross errors and yes, I fixed the 154/157
¨confusion).
MG> FTSC may fancy itself some sort of "authority" based on
some perceived
MG> techno-geeky intellectual hierarchy (read bovine scatology) expressed
MG> through the FTSC nomination and election process, but in reality they
MG> are far less important in the decision making process than the Coordin
MG> or even the end nodes, if enough of them protest loudly enough for a c
Grin, they just document. Thats all.
xxcarol
--- Telegard v3.09.g2-sp4
* Origin: SHENK'S EXPRESS, Sasebo Japan 0956-25-2561 (6:757/1)SEEN-BY: 106/2000 120/544 123/500 140/1 633/260 262 267 270 285 634/383 SEEN-BY: 640/954 654/0 690/682 757/1 771/4020 774/605 2432/200 7105/1 @PATH: 757/1 140/1 106/2000 123/500 774/605 633/260 285 |
|
| 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™.