# SR 2019 Network Requirements

**Please do not edit this spec without discussing with Delta V.**

## Layer 1

We will need the following ports in the following locations:

More information can be found on [our floorplans](https://github.com/srobo/comp-floorplans/tree/master/2019/templates)

### B42 Level 4

- 1 port for large video wall
- 1 port for score screen on entrace to bridge. (Dependent on SUSU permission to use this screen)

### B42 Level 3

- Cafe
- 2 ports for score screens, see floorplans
- Bar 3
- 1 port for score screen on Bar.
- 2 ports at end by UF office for SUSU TV Studio
- Tech Deck (Cube Balcony)
- SUSU uplink will be provided here.
- 1 port for SRCOMP-Mixtape
- 1 port for Chamsys Lighting Desk
- 1 port for Tyler
- 1 port for Non-synchronous music
- 1 port for SRComp Control
- 1 port linking to Cube Truss for Auto-photography Pi
- 5 spare ports for volunteer use
- These can be on the switch
- We also have some 4 way power / ethernet combo things

### B42 Level 2

- Bar 2
- Screen by Helpdesk (See floorplans)
- Screen at end of Bar 2
- The Cube
- 2 in corner for score entry
- 1 for shepherding screen
- 4 in arena corners for screens
- 1 by Cube Exit (Outside screen)

### B42 Level 1

- Clubs & Societies Room
- 1 for projector displaying livestream / scores

## Layer 2

- As simple as possible.
- No VLANs should be needed. A flat network should hopefully suffice.
- The exceptions to this are:
- One of the two ports for SUSUTV should **not** be on the competition network. Just an uplink will suffice.
- The port in the Clubs and Socs room doesn't need to be one on the comp network, although if it is, that is fine.

## Layer 3

- IPv4 only for simplicity
- No firewalling between things on the comp network.
- There must be excellent connectivity in the arena. We are running NTP.

From Peter for SRComp:

Protocols which MUST work (inwards, outwards and internally):

    SSH
    HTTP and HTTPS
    git://
    NTP
    ICMP (ping)

Hardwire is essential, WiFi very much a nice-to-have.

Everything wants to have DHCP issued addresses for ease of setup, though some of the addresses should be fixed in config.
Everything here needs to be able to establish and maintain communications with everything else (there's a subset of this which is actually the strict requirement -- the screens don't need to be able to talk to each other, but it very nearly amounts to the same thing).

This consists of:

- the compbox, which MUST HAVE a fixed IP and MAY HAVE a DNS entry (compbox-2019)
- the screen drivers (Pis), which MUST HAVE fixed IPs (ideally arranged such that their identifying number in the inventory maps directly into their IP, for example Pi number 3 being x.x.x.103, mostly for ease of debugging) and MAY HAVE DNS entries
- four or so volunteer machines

Whatever is hosting the network MUST NOT assume that it has complete control over the physical topology. Being able to add a switch where we realise we need it, either to extend cables or for diagnostic access is important. Similarly, deciding that we're going to bridge other stuff into the network has been important (though hopefully we'd do that in concert with the host situation rather than against it).

The screens around the venue need to be able to talk to a compbox like machine. Ideally that would be the in-venue one, over an in-venue-only link. There is no need for this link to be particularly secure as it is conveying public information. A fallback of using a public compbox (which would be secure as it would have TLS) is an option.