It certainly appears that Congress needs to address the definition of what internet traffic actually is for regulatory purposes, if only to spare business and the public the expense of arguments over how that traffic is regulated. The FCC variously invoked its existing authority to regulate broadcast, telephony and the provision of infrastructural access to ISPs, but since none of these things are properly definitive of IP packets the existing authority isn't applicable, and so they had no right to order Comcast to submit its load-balancing methodology to the FCC for approval.
Put another way, it seems as if the FCC has the authority to regulate the creation of infrastructure but not the manner in which it is operated, and the origination and transmission of data over that infrastructure are not protected from interference by network operators. It's as if anyone is entitled to set up a railway terminal and have access to the track network, but no customers of a given terminal are entitled to any assurances about how fast their shipping containers will be delivered, if at all.
All the existing regulation seems to be built on the premise the communication takes place over a limited swathe of electromagnetic spectrum or physical wires, with fixed geographic points of signal origination or relay as a unifying characteristic. The fundamentally diffuse and ephemeral nature of data itself (which might be collated from multiple different sources over temporary ad-hoc networks that are neither physical nor persistent) isn't explicitly treated by any existing regulation that I know about. For example, if HN is run on a virtualized server spread across multiple slices running on computers in a variety of data centers, it becomes hard, or perhaps even meaningless, to talk about 'where' this discussion is taking place - it may not exist in any single physical location.
The sheer abstraction involved might be a problem for Congress (as exemplified by former Senator Ted Stevens' flailing attempts to explain the internet as a 'series of tubes'). Then again, we manage OK with a shared agreement about the contents of the US Constitution, without the necessity of running off to the National Archives every time wish to refer to it, and are able to exchange money in the economy without needing to correlate every transaction against the gold stored in fort Knox. I hope this ambiguity will be resolved by Congress rather than by being appealed up to the Supreme Court.
Comments
It certainly appears that Congress needs to address the definition of what internet traffic actually is for regulatory purposes, if only to spare business and the public the expense of arguments over how that traffic is regulated. The FCC variously invoked its existing authority to regulate broadcast, telephony and the provision of infrastructural access to ISPs, but since none of these things are properly definitive of IP packets the existing authority isn't applicable, and so they had no right to order Comcast to submit its load-balancing methodology to the FCC for approval.
Put another way, it seems as if the FCC has the authority to regulate the creation of infrastructure but not the manner in which it is operated, and the origination and transmission of data over that infrastructure are not protected from interference by network operators. It's as if anyone is entitled to set up a railway terminal and have access to the track network, but no customers of a given terminal are entitled to any assurances about how fast their shipping containers will be delivered, if at all.
All the existing regulation seems to be built on the premise the communication takes place over a limited swathe of electromagnetic spectrum or physical wires, with fixed geographic points of signal origination or relay as a unifying characteristic. The fundamentally diffuse and ephemeral nature of data itself (which might be collated from multiple different sources over temporary ad-hoc networks that are neither physical nor persistent) isn't explicitly treated by any existing regulation that I know about. For example, if HN is run on a virtualized server spread across multiple slices running on computers in a variety of data centers, it becomes hard, or perhaps even meaningless, to talk about 'where' this discussion is taking place - it may not exist in any single physical location.
The sheer abstraction involved might be a problem for Congress (as exemplified by former Senator Ted Stevens' flailing attempts to explain the internet as a 'series of tubes'). Then again, we manage OK with a shared agreement about the contents of the US Constitution, without the necessity of running off to the National Archives every time wish to refer to it, and are able to exchange money in the economy without needing to correlate every transaction against the gold stored in fort Knox. I hope this ambiguity will be resolved by Congress rather than by being appealed up to the Supreme Court.