routing-com:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
routing-com:start [2018/03/13 02:32]
ellenor2000
routing-com:start [2019/02/26 00:27] (current)
ellenor2000
Line 13: Line 13:
   * A cluster is defined as a grouping of servers.   * A cluster is defined as a grouping of servers.
   * A server, for the purpose of a link application is defined as a grouping of servers that are either in non-disparate physical locations, or is a clan of one.   * A server, for the purpose of a link application is defined as a grouping of servers that are either in non-disparate physical locations, or is a clan of one.
-  * A server, for the purpose of "a grouping of servers,"​ is an instance of [[:​software:​chatd|ircd-chatd]] that is listening on an address suitable for the target audience.+  * A server, for the purpose of "a grouping of servers,"​ is an instance of [[:​software:​irca|irca]] that is listening on an address suitable for the target audience.
   * A target audience may be a company or project (Ronsor has this target audience - his server is allowed to be completely unreachable from the outside as long as it can connect to the designated hub), a regional public (in which case a server may have a limited I:line and may use a more severely restricted *@* I:line), a global public (in which case a server must have at least 10 Mbps of global bandwidth bidirectionally and must have a generally open *@* I:line), or a special public (like a darknet; your most general I:line must be open to the public you are serving)   * A target audience may be a company or project (Ronsor has this target audience - his server is allowed to be completely unreachable from the outside as long as it can connect to the designated hub), a regional public (in which case a server may have a limited I:line and may use a more severely restricted *@* I:line), a global public (in which case a server must have at least 10 Mbps of global bandwidth bidirectionally and must have a generally open *@* I:line), or a special public (like a darknet; your most general I:line must be open to the public you are serving)
  
Line 22: Line 22:
   * If a server passes test-link while on behavioural probation, it remains on behavioural probation and may not have any opers whatsoever (No-Op by OperServ).   * If a server passes test-link while on behavioural probation, it remains on behavioural probation and may not have any opers whatsoever (No-Op by OperServ).
   * Servers passing test-link on behavioural probation will be L:lined for all hosts and will be H:lined only in their locale.   * Servers passing test-link on behavioural probation will be L:lined for all hosts and will be H:lined only in their locale.
-  * Servers passing test-link with satisfactory behaviour will be H:lined for the locales nearest them and L:lined for hosts outside of their region that they do not expect to hub for. Hubs are exempt, however, care must be taken to prevent NA->​EU->​NA tracks, or, for an actually very annoying example that is currently happening on the live network:+  * Servers passing test-link with satisfactory behaviour will be H:lined for the locales nearest them and L:lined for hosts outside of their region that they do not expect to hub for. Hubs are exempt, however, care must be taken to prevent NA->​EU->​NA tracks, or, for an actually very annoying example that happened once when we had Claritas linked to us:
     * Server in Illinois (claritas.il.us.*) is on behavioural probation and is in its testlink phase. Due to the NACD's personality disorder, which earned him a suspension from the RNAC, it is expected that the server will not leave behavioural probation.     * Server in Illinois (claritas.il.us.*) is on behavioural probation and is in its testlink phase. Due to the NACD's personality disorder, which earned him a suspension from the RNAC, it is expected that the server will not leave behavioural probation.
     * Server in Georgia (ronsor*.onion.ga.us.*) passed its test-link. It's a permanent fixture on the network. Its closest theoretical hub is in Illinois, and it's equidistant with the Illinois server from the North Pacific Rim hub (invictus.wa.us.*),​ but due to the Illinois server'​s behavioural probation, it connects into the rest of the network via invictus.wa.us.*,​ rather than via claritas.il.us.*. Additionally,​ r*.onion.ga.us.* is a leaf, due to the inability of the first among equals to add link blocks to the server in a timely manner (administrator is absentee and FAE has not received shell credentials).     * Server in Georgia (ronsor*.onion.ga.us.*) passed its test-link. It's a permanent fixture on the network. Its closest theoretical hub is in Illinois, and it's equidistant with the Illinois server from the North Pacific Rim hub (invictus.wa.us.*),​ but due to the Illinois server'​s behavioural probation, it connects into the rest of the network via invictus.wa.us.*,​ rather than via claritas.il.us.*. Additionally,​ r*.onion.ga.us.* is a leaf, due to the inability of the first among equals to add link blocks to the server in a timely manner (administrator is absentee and FAE has not received shell credentials).
Line 35: Line 35:
  
 ^  **Email everyone in this list** ​ ^^^^ ^  **Email everyone in this list** ​ ^^^^
-| ellenor@umbrellix.net | zack@apertron.net or zack@apertron.com ​| <coming soon> | <coming soon> |+| ellenor@umbrellix.net | ronsor@ronsor.pw | <coming soon> | <coming soon> |
  
 === Meanings of invalid TLDs === === Meanings of invalid TLDs ===
Line 41: Line 41:
 ^ TLD ^ Meaning ^ ^ TLD ^ Meaning ^
 | .h | Hyperboria, e.g. invictus.wa.us.umbrellix.h would mean a server named invictus in Washington state that is only available over Hyperboria | | .h | Hyperboria, e.g. invictus.wa.us.umbrellix.h would mean a server named invictus in Washington state that is only available over Hyperboria |
 +| .y | Yggdrasil, e.g. invictus.wa.us.umbrellix.y would mean a server named invictus in Washington state that is only available over Yggdrasil |
 | .x | Hidden hubs (x represents a crisscrossing of links - hubs are usually the centre of a bit of crisscrossing) - these are usually H:lined open so that they may hub for any part of the network, though the admin may elect to restrict the scope of their H:line. | | .x | Hidden hubs (x represents a crisscrossing of links - hubs are usually the centre of a bit of crisscrossing) - these are usually H:lined open so that they may hub for any part of the network, though the admin may elect to restrict the scope of their H:line. |
 | .l | Hidden leaves (for companies and projects that wish to have an internal IRC server linked to Umbrellix - the second level domain must be the name of the organisation,​ e.g. "​google-com.l"​ if Google wished to have an internal IRC server linked in. Such a server would be H:lined "​*.google-com.l"​) - these need not necessarily be private, but may have not gone through the usual competency checks | | .l | Hidden leaves (for companies and projects that wish to have an internal IRC server linked to Umbrellix - the second level domain must be the name of the organisation,​ e.g. "​google-com.l"​ if Google wished to have an internal IRC server linked in. Such a server would be H:lined "​*.google-com.l"​) - these need not necessarily be private, but may have not gone through the usual competency checks |
Line 59: Line 60:
  
 {{page>:​routing-com:​sponsorlist}} {{page>:​routing-com:​sponsorlist}}
 +
 +<nspages -h1 -subns -exclude:​start>​
  • routing-com/start.1520908325.txt.gz
  • Last modified: 2018/03/13 02:32
  • by ellenor2000