Network requirements for W3C meetings — checklist
To be completed by quoting venue networking engineers who
should also received fuller
explanation of requirements.
Physical checks
Networking
- Access points: number, position on the floor plan.
- Wired connections RJ45.
- Power plugs.
- TV/video.
- Shadow areas (mobile phone network, wifi).
- Connectivity elsewhere in the venue.
- 3G/4G reception.
- Wifi: interferences, saturation of the spectrum.
Wifi analyzer.
- The venue will be ready 7 days before the event.
- Possible to conduct a load test in advance.
- Local network admin contact available.
- Upstream provider contact available.
ITC checks
The basics
- Unique DHCP (keeps session between APs).
- WPA2 authentication preferrable.
- No login, or at least an easy one. Simple HTML preferred.
- If there's login: no JavaScript necessary; possible with Lynx or W3 browsers.
- If there's login: accesible (WAI-compliant).
- If there's login: all OSs; all browsers.
- If there's login: password cacheable by browser.
- If there's login: duration ≥ 12 h.
- Type of wifi (802.11 A-G-N-AC).
- DHCP leases ≥ 1 h.
- Unique ESSID; sample
W3C-TPAC2015
customized
per event.
- If there's password: known beforehand; location preferred, ie
Sapporo
.
- No device restrictions.
- Time to connect: ≤ 3 s.
Bandwidth / no. of connections and users
- Support at least 2.5 devices/participant.
- Maximum capacity per AP.
- Details about QoS, service interruptions, tolerance, and penalties to apply if not met.
- Load-balancing mechanisms in place.
- Download speed ≥ 200 Mb/s.
- Upload speed ≥ 75 Mb/s.
Services, QoS
- Multiple, load balanced lines from different carriers
- Bandwidth throttling per device
- IRC possible (TCP ports 6667 and 6697).
- VPN possible.
- SSH possible.
- IPSec possible.
- VoIP possible.
- Maintaining 90 Kb/s of UDP packets should be fine, not impact users.
- ≤ 2 interruptions of max 2 s, per hour (interruption: ≥ 20% users with no traffic).
- ¬ interruptions ≥ 10 s (interruption: ≥ 20% users with no traffic).
- DNS: resolving well-known domains ≤ 100 ms.
- Ability to block ports/protocols if necessary during the event.
ping
to irc.w3.org
(Cambridge) ≤ 150 ms; so no satellite connection admissible.
- ¬ proxies (HTTP nor IP).