From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.rs.github.com (smtp1-ext.rs.github.com [207.97.227.250]) by huchra.bufferbloat.net (Postfix) with ESMTP id 631A6200BFD for ; Wed, 4 Apr 2012 16:30:28 -0700 (PDT) Received: from github.com (sh1.rs.github.com [172.17.1.41]) by smtp1.rs.github.com (Postfix) with ESMTP id DC9F24236B for ; Wed, 4 Apr 2012 16:30:26 -0700 (PDT) Date: Wed, 04 Apr 2012 16:30:26 -0700 From: GitHub To: cerowrt-commits@lists.bufferbloat.net Message-ID: <4f7cd992d4906_623a3fc1bb1eaafc29758@sh1.rs.github.com.mail> Subject: [dtaht/ceropackages] ef0d86: Relentless TCP Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_4f7cd992d1fa1_623a3fc1bb1eaafc2954"; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: cerowrt-commits@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list Reply-To: GitHub List-Id: Development commits for the cerowrt project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Apr 2012 23:30:28 -0000 ----==_mimepart_4f7cd992d1fa1_623a3fc1bb1eaafc2954 Date: Wed, 04 Apr 2012 16:30:26 -0700 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-ID: <4f7cd992d35ef_623a3fc1bb1eaafc29661@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/dtaht/ceropackages Commit: ef0d868425e5e6c01a356b3ffceafa67115b8129 https://github.com/dtaht/ceropackages/commit/ef0d868425e5e6c01a356b3ffceafa67115b8129 Author: Dave Taht Date: 2012-04-04 (Wed, 04 Apr 2012) Changed paths: A net/kmod-tcp-relentless/Makefile A net/kmod-tcp-relentless/patches/0001-updated-makefile-for-more-modern-boxes.patch Log Message: ----------- Relentless TCP Matt Mathis, 2008 Relentless TCP is designed to maintain a standing queue at some network bottleneck. It does so without regards to other traffic, and thus it is not generally fair to other network users. It MUST NOT be used unless the network is designed to actively control it to protect other flows and the Internet at large from its aggressiveness. To protect other flows, the network carring Relentless TCP traffic has to implement Scavenger Service, Fair Queuing, Approximate Fair Dropping, or some other capacity allocation algorithm. To protect the Internet at large the network carring Relentless TCP traffic has to be a physically or logically isolated from the rest of the Internet. Be espically warry of the potential for dynamic routing to choose an alternative path that can not adiquiately contol Relentless TCP. To minimize the risks associated with Relentless TCP, it has to be enabled on a per-connection basis. ----==_mimepart_4f7cd992d1fa1_623a3fc1bb1eaafc2954--