# IX Servers & Links
## Overview
Currently, Undernet has ***1*** hub server and ***8*** client servers on IX infrastructure.
This infrastructure is managed by a small team of trusted and experienced routing team members originally from another network. On Undernet, the administrative members currently consist of ***1 x voting*** admin (*deckard*) and ***4 x non-voting*** admin-reps: *ahnberg, RuneB, Arfie, and msofty*
Given the anycast routing with these servers, it is important to not only ensure that DDoS packets are distributed but also that users can actually connect to a server within this infrastructure. Routing changes can necessitate new server links-- without which, some users cannot connect.
To improve the existing IX infrastructure and connectivity for its users, some 4-5 new IX servers could be linked now, with the likelihood of changes or additions in future.
Efficiently implementing such changes necessitates a more dynamic approach to managing these servers (with links and delinks), without the normal and lengthy vote processes for standard server links.
The single vote currently granted to this IX infrastructure team is not representative of the significant investment in time and resources provided by the group, who also wish to have more contribution in the network they sponsor.
---
## Call For Vote
This CFV is split into two parts to address both aspects of the above. Voting admins should **vote on both parts**, treated independent of each other.
---
### Part 1 - IX & Hub Links
Introduce an additional section in the Routing Committee Procedures (*committees/routing.md*), as per below:
```
## Hubs and IX Servers
Routing-Com is responsible for granting newlinks of IX and Hub servers as required.
Where these server links do not introduce new server admins or votes, permlinks are granted and delinks initiated without the need for Undernet Admins vote.
Such Routing-Com initiated links & delinks will be notified to the AB via the Undernet Admins mailing list prior to connectivity changes.
If the new server link results in any new admins or votes, normal procedures are followed as per ***Testlinks*** and ***Server Permlink Procedure***, as with any resulting delinks as per ***Server Delink Procedures***.
```
Failure to pass Part 1 will require the standard processes with CFVs for testlink, and permlink ratification, for every new IX server.
| Vote | Description |
|------|-------------|
| **Yes** | Approve the Routing-Com policy ammendment for IX servers & hubs |
| **No** | Reject the proposed Routing-Com policy ammendment |
| **Abstain** | Abstain from voting Yes or No |
---
### Part 2 - IX Server Admins
Acknowledge the contribution from the sponsored IX infrastructure team by granting voting rights to ***all 5 x members***, with ***msofty*** being replaced by ***Kobi_S*** due to availability constraints.
This vote will grant ***4 x additional*** votes to the admins: *ahnberg, RuneB, Arfie, and Kobi_S* (with *Kobi_S* becoming a new AB member).
| Vote | Description |
|------|-------------|
| **Yes** | Approve the 4 x additional IX infrastructure voting members, with *Kobi_S* replacing *msofty* |
| **No** | Reject the proposal for additional voting members |
| **Abstain** | Abstain from voting Yes or No |
---
Sign in with Wallet
Connect another wallet