I should clarify that the real risk is this data leaving Colorado. A point to point connection isn't feasible, the data needs to traverse the internet, but do so only within the state of Colorado. If it crosses statelines it becomes a legal issue, not a technical one. Think about the way courts treat internet gambling (i.e. it falls under federal jurisdiction because the data crosses state lines even if both parties are in the same state). This gives you an idea of the reasoning, but no it's not gambling.
On Fri, May 31, 2013 at 1:27 AM, Gabriel Gunderson <[email protected]> wrote: > On Thu, May 30, 2013 at 11:27 PM, S. Dale Morrey <[email protected]> > wrote: > > Is keeping this data within the state feasible while using TCP/IP? > > It has little to do with TCP/IP and a lot to do with what network > you're using. If you're planning on using the Internet, you will have > packets going to Denver, LA or Chicago just to make it to a server > across town. > > The requirements seem to suggest that they're misinformed about what > the real risks are and how they can be sensibly addressed. > > > Best, > Gabe > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
