Re: [76attendees] A Net Neutrality comment

Jason Livingood <jason_livingood@cable.comcast.com> Mon, 09 November 2009 05:09 UTC

Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: 76attendees@core3.amsl.com
Delivered-To: 76attendees@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFEAE3A6932 for <76attendees@core3.amsl.com>; Sun, 8 Nov 2009 21:09:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.396
X-Spam-Level:
X-Spam-Status: No, score=-6.396 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wzh5YcC1cxBc for <76attendees@core3.amsl.com>; Sun, 8 Nov 2009 21:09:25 -0800 (PST)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id AD0343A68FA for <76attendees@ietf.org>; Sun, 8 Nov 2009 21:09:25 -0800 (PST)
Received: from ([10.52.116.30]) by pacdcimo01.cable.comcast.com with ESMTP id 5503620.60078819; Mon, 09 Nov 2009 00:09:47 -0500
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 00:09:47 -0500
Received: from 133.93.17.128 ([133.93.17.128]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Mon, 9 Nov 2009 05:09:46 +0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Mon, 09 Nov 2009 14:09:44 +0900
From: Jason Livingood <jason_livingood@cable.comcast.com>
To: Richard Barnes <richard.barnes@gmail.com>, Fred Baker <fred@cisco.com>
Message-ID: <C71DD328.165A0%jason_livingood@cable.comcast.com>
Thread-Topic: [76attendees] A Net Neutrality comment
Thread-Index: Acpg+tl2Ad+g1wDPEEWWr2ASbztVsw==
In-Reply-To: <88ac5c710911081621j59316bbfi16567c241f51a7b2@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 09 Nov 2009 05:09:47.0560 (UTC) FILETIME=[DB95D280:01CA60FA]
Cc: 76attendees@ietf.org
Subject: Re: [76attendees] A Net Neutrality comment
X-BeenThere: 76attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <76attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/76attendees>, <mailto:76attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/76attendees>
List-Post: <mailto:76attendees@ietf.org>
List-Help: <mailto:76attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/76attendees>, <mailto:76attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2009 05:09:26 -0000

+1 on this being an interesting study.

As for Richard's comment, speaking from personal experience, involvement in
application throttling at any level of scale and customer diversity can at
best be described as "problematic."  ;-)

Jason

On 11/9/09 9:21 AM, "Richard Barnes" <richard.barnes@gmail.com> wrote:

> Hey Fred,
> 
> Thanks for this little study.  Note that this doesn't necessarily
> argue for *application* throttling, as much as for *user* throttling.
> The network might want to prevent the bittorrent user from interfering
> with you, but the he can be left free to shut down his own VPN if he
> wants to.
> 
> --Richard
> 
> 
> 
> On Mon, Nov 9, 2009 at 9:05 AM, Fred Baker <fred@cisco.com> wrote:
>> A remark to those who take a militant libertarian view of Net Neutrality,
>> and those of ledbat and tcpm who have difficulty understanding why
>> transports should tune to the knee (just enough of data outstanding, aka
>> cwnd, to maintain the maximum goodput) as opposed to the cliff (the knee
>> plus the maximum depth of the bottleneck queue, at which point throughput
>> has not increased but loss has increased).
>> 
>> Saturday night, as I do many nights that I spend at hotels, I ran a ping
>> study to characterize the network. It was obviously massively
>> overprovisioned - it was difficult to register RTT variance in excess of a
>> millisecond trans-pacific between Japan and the US. I did this again last
>> night. The network behavior as measured from my room was equally stable
>> until about 11:58 PM; at that point, someone fired up something huge, my
>> guess being something that uses bittorrent, delay dramatically increased,
>> and my VPN went down within a couple of minutes. When this happens,
>> customers call ISPs and ISPs start throttling applications, because the
>> applications are doing horrible things to the ISPs' customers.
>> 
>> The attached are a case in point.