IETF Logo Mail Archive

Re: [v6ops] Net Neutrality question

Barry Raveendran Greene <bgreene@senki.org> Thu, 19 November 2015 05:25 UTC

Return-Path: <bgreene@senki.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D97671A8833 for <v6ops@ietfa.amsl.com>; Wed, 18 Nov 2015 21:25:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level:
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g1diGL_gSnT0 for <v6ops@ietfa.amsl.com>; Wed, 18 Nov 2015 21:25:06 -0800 (PST)
Received: from smtp109.ord1c.emailsrvr.com (smtp109.ord1c.emailsrvr.com [108.166.43.109]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3E0F1A882E for <v6ops@ietf.org>; Wed, 18 Nov 2015 21:25:06 -0800 (PST)
Received: from smtp22.relay.ord1c.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp22.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id F2DEB180390; Thu, 19 Nov 2015 00:25:05 -0500 (EST)
X-Auth-ID: bgreene@senki.org
Received: by smtp22.relay.ord1c.emailsrvr.com (Authenticated sender: bgreene-AT-senki.org) with ESMTPSA id 061A618037E; Thu, 19 Nov 2015 00:25:04 -0500 (EST)
X-Sender-Id: bgreene@senki.org
Received: from [172.20.10.4] (amx-tls2.starhub.net.sg [203.116.164.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.5.4); Thu, 19 Nov 2015 00:25:05 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: Barry Raveendran Greene <bgreene@senki.org>
In-Reply-To: <4E9C6C1B-9F9C-4AD7-9822-DFFC8E406F86@cisco.com>
Date: Thu, 19 Nov 2015 13:25:00 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <93BAB56C-060D-4EBD-8A17-22CE55DD4CF6@senki.org>
References: <4E9C6C1B-9F9C-4AD7-9822-DFFC8E406F86@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/BNglXtBbqVszOjWVf20A1ZaReps>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Net Neutrality question
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2015 05:25:08 -0000

> Comcast went through this, using DPI to trap BitTorrent. They got into a scrap with the FCC. There were two outcomes: LEDBAT (BitTorrent now uses a different transport in order to maximize throughput while minimizing latency, loss, and impact on competing traffic) and RFC 6057 (a Cable Network procedure designed to apply a relatively gentle pushback on a top talker so that everyone gets a turn to communicate without having to identify a subscriber or application, or drop traffic).

Too complicated and the engineers + vendors who give them free consulting don’t the depth of engineering options available. It is easier for a DPI box to be placed into the network thinking that it is going to work. In most cases, it does not work (people find ways around it). Scaling the DPI also becomes a problem. For now, the “magic DPI box” is the quick fix.

v2.23.0 | Report a Bug | By Email