roadmap: features required for initial release

[jimmyl02]

hard feature requirements:

• linux source based routing
• heartbeat from client to control plane
  • including reaping of stale connections (last heartbeat over 5 minutes old)
• support for only serving specific subnets (metadata)
• clients must add specific route for control plane ws to use default interface
  • if not done, tcp socket connection will die
• auth jrpc call from control plane to client instead of immediately sending from client
• overall polish
  • clean up routes
  • TODOs in the code
  • locking for synchronization
  • etc.
• re-enable target server aliveness check
• proper AuthZ on the control plane for client and serve connections
• verbose error messages to client when something goes wrong
  • daemon should never fatally error (this is going to be a huge refactor)
  • server should never fatally error
• validate elevation
• frontend implementation

hard release requirements:

• macos client (homebrew? or installation script)
  • if mac client is not feasible in timely manner, spend more effort on UI to add other devices and connections
• windows installer (WiX)
• linux installer (installation script)

[jimmyl02]

should route to control plane also be whitelisted? motivation is because network may get interrupted due to packets suddenly going through a new interface. this should be experimented with to see if it improves stability.