[ NNSquad ] Internet User's Bill of Rights [was: Google Hijacked -- Major ISP to Intercept and Modify Web Pages

[John Bartas <jbartas@speakeasy.net>]

	Thanks Rob. You've pretty well shown that the ISPs can do their job without violating the most basic RFCs. Even better, your final line pretty well nails the whole issue of this group:

"To me it's even simpler: What am I paying my ISP to do?"

	I'd like to propose an answer, in two parts:

1) I'm paying my ISP to move a stream of packets between my site and other internet sites. They are not to edit, drop, reorder, examine, modify or add to the packets other than the minimal RFC-compliant header changes required for forwarding the packets. 

2) They must handle all packets in FIFO order except by mutual pre-argeement. For example, If I consent to delaying my bit-torrent traffic to improve timing of my RTP streams, then they may do so; but not without my prior informed consent. 

	Maybe this group could define a "Internet User's Bill of Rights" and ask the ISPs to sign it. It should leave no wiggle room for ISPs like Rodgers to claim they didn't think they were violating their customers rights. 

-JB-


    [ An "Internet User's Bill of Rights" is a frequently discussed idea that
      at this point would probably be mainly of academic use (that is, not
      likely to be "enforced") given the current political climate, though
      specifically noting presumed "rights" can still be helpful to
      policymakers in the long run.
      
      However, this would be out of scope for the NNSquad project.

                                     -- Lauren Weinstein
                                        NNSquad Moderator ]

 - - -

Robb Topolski wrote:
>  > Unlike the postal system and the telephone system which have developed
>  > many ways to add additional information, the Internet is severly lacking.
>
> Allow me to disagree, as there are plenty of messages available for use.
>
>  > The post office adds stamp to letters with all sorts of messages about
>  > postage due,
>
> ICMP TTL or timer expired enroute -- or whatever mechanism currently
> used to notify users of bills due
>
>  > return to sender,
>
> ICMP no route to host
>
>  > disaster area - no forwarding address,
>
> ICMP restricted by cut-off
>
>  > and even cute "advertising-like" cancellations.
>
> Like ads inserted at the bottom of Yahoo Mail, Organization: headers
>
>  > The telephone system has
>  > multiple types of busy signals
>
> TCP RST in response to SYN
>
>  > and special information messages about all
>  > circuits are busy,
>
> ICMP No route to host, ICMP Source Quench, ICMP Timer expired, TCP ECN
> or just drop the TCP packet
>
>  > line restricted to only emergency calls, due to an
>  > earthquake in the area please wait and try your call later.
>
> ICMP cut-off in effect, no route to host, or drop the SYN packet and
> let the connection attempt time out.
>
> There often are two or three methods in the standards for the same
> purposes.  And if something isn't covered, then there is The Internet
> Society and the IETF and a whole RFC process that should be followed
> before unleashing something new.
>
> To torture this Post Office metaphor a bit more, it's not just about
> the contents.  Nobody should have the right to tear away my "First
> Class" stamp and relabel it as "Bulk" because that classification
> tends to satisfy their own purposes.
>
> To me it's even simpler: What am I paying my ISP to do?
>
>