BakeAThon and ConnectAThon requirements

Local ethernet network for testing

Should be firewalled from host site's intranet
- incoming to protect attendees
- outgoing to protect host
Should be firewalled from incoming traffic from internet
- if external access is necessary, use ssh keys to control
- outbound traffic should
  - allow all ports by default
  - block ones that are considered harmful
Unfiltered outgoing connections to the internet
- this may be contrary to host's policy
  - not all attendees use vpn
  - following are minimal services necessary
    - http, https
    - ssh
    - git
    - vpn protocols
    - imap, pop
  - someone onsite with the authority and ability to permit additional access as requested by attendees
- Any NAT must support multiple VPN connections to external sites
- Should be responsive under load
  - Vague, but the host will be constantly reminded when the internet connection resembles a wet straw
- Both wired and wireless networks need this access
Wireless access to test network
- preferred, not a hard requirement
4 static ip per person
- minimum requirement, should poll for more
- this acknowledges that a lot of testing is on virtual machines
- must include IPv4 and IPv6 addresses
  - event provided IPv6 addresses must not be link-local
- global IPv6 routing should be provided by the host, not mandated
DHCP for both networks
static DNS entries (for servers)
- new sub-domains must be easy to create for some testing scenarios
- FedFS is driving the need to make adjustments
- all ip must be resolvable (IPv4 and IPv6)
- there must be a domain name
  - nfsv4bat.org
  - should also be the NFSv4 domain name
    - with a TXT record
- DNS server should also provide global DNS
krb5 server
- not always used, but should be available
ldap/nis service with some test identities
ntp server on the test network sync'ed to the outside world
immediate access to all firewall, router, dhcp, dns, etc. configuration by someone with ability and authority to fix problems

Physical needs

2 network ports and cables per person
2 power outlets per person
- Might need more, gather requirements
- Might need electrician the first day
2'x3' working space per person
Separate room for discussions
- No presentations in testing room
- No other distractions (cough, World Cup, cough)
Separate machine room for noisy equipment
- Must be able to have machines on same network
- Fast connection between rooms
- Will need AC
- Attendees will need access to machine room OR RPB (remote power boot) and console
Printed copy of network configuration at each station
- email copy is nice, but not sufficient
Small conference room for conversation and conference calls
Adequate and secure parking

Security

Minimal access is from 8am to 8pm
Must be able to leave equipment (i.e., laptops) in testing room
Host must not touch arriving equipment.
- May only be opened/powered if owner is present
I.e., security is to not only protect the interests of the host but the visitors
Attendees must be able to easily get from test room to exterior
- Cell phone calls

Hotels

It is not the responsibility of the host to organize a hotel block.
I.e., social tools can be used to do this.
However, the hotel bars should not require ice be added to all liquor drinks.

NDA

Not always a requirement
Please base off of http://www.connectathon.org/cthon_liability_2010.pdf
Cameras
- Even if no NDA, must ask permission before taking pictures of equipment
- It is nice to take pictures of attendees, but please make sure you ask first and do not capture any screen shots
One benefit of hosting is to bring in people who normally would not attend
- No competitive analysis

NDA vs Open talks

If presentations are being made and there is a desire to share the notes with people outside the event
- Hold the talks in a separate venue than the testing room
- Pre-announce the talks are open to the public
- Before each talk, make an announcement similar to the IETF Note Well Agreement - http://www.ietf.org/NOTEWELL.html