From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lpp01m010-f43.google.com (mail-lpp01m010-f43.google.com [209.85.215.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id E3919200B1B for ; Sun, 3 Jun 2012 18:32:52 -0700 (PDT) Received: by lahg1 with SMTP id g1so6065303lah.16 for ; Sun, 03 Jun 2012 18:32:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=fTwu0QMw4X6ltt2UU41YDSv/in91zzocZZoeRgCe1rI=; b=sQQD3Hq0nur2PVYiPembyX0XcePpxkseOUOqnsVnFbRanCPjPtgJwxUN3AVibB3sRx SFfBRMTxEBV/FaKNUVLws3QZ4iVyVMV5JA/07mpUhcZS/DIynxkkrcYfKhdewj/24vVx Mpxe3nZfYhVrrxr128JR7Z9prDsbRAIrwG78uNKtIWEjII30+LXUq0WaT3KCbkEWX2tZ 9DrIW6KakX/XgUdRvZDNm9S4DAkCvuTcW+uyEud5f/ahxSbw3N2Cadn4iApubXtHVWTu RLCHRp2aXgQRArnuSnNEQO5zRB/fqOcNgW+1P3kGavhCgihhRHNVaisOilB2feEBDHx+ JFHg== MIME-Version: 1.0 Received: by 10.112.54.40 with SMTP id g8mr5275344lbp.1.1338773569997; Sun, 03 Jun 2012 18:32:49 -0700 (PDT) Received: by 10.112.113.135 with HTTP; Sun, 3 Jun 2012 18:32:49 -0700 (PDT) Date: Sun, 3 Jun 2012 18:32:49 -0700 Message-ID: From: Haiqing Jiang To: Eric Dumazet , Dave Taht Content-Type: multipart/alternative; boundary=bcaec5555556130cc604c19b83ad Cc: bloat@lists.bufferbloat.net Subject: [Bloat] Tackling bufferbloat in 3G/4G networks: A receiver-based TCP solution. X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 01:32:53 -0000 --bcaec5555556130cc604c19b83ad Content-Type: text/plain; charset=ISO-8859-1 Hi, All, Recently the researchers from Networking Research Group of North Carolina State University (NCSU) have proposed an interesting receiver-based TCP solution to tackle bufferbloat in 3g/4g networks. They conducted extensive measurements in four major carriers in US and the largest carrier in Korea to verify the severe bufferbloat problem in currently commercial cellular networks. They cited the work from Bufferbloat group and further extended the work to cellular networks. Furthermore, they revealed the untold implementation of TCP, an ad-hoc solution to mitigate bufferbloat, in smartphone's network stack (Android platform). The ad-hoc solution is sub-optimal in many scenarios. Actually it merely mitigate bufferbloat problem in some scenarios. Therefore, the guys from NCSU propose a "Dynamic Receive Window Adjustment" scheme to tackle bufferbloat problem. The extensive experiment results prove that the scheme is efficient and light-weight. It's really excited to find the new direction to tackle bufferbloat, on TCP layer instead of routers (like AQM). The bufferbloat problem actually seems to be the most prominent, comparing with other networks. Therefore, we suggest the more efforts to tackling bufferbloat problem in cellular networks and seeking a good solution in TCP layer space. The link is attached: ftp://ftp.ncsu.edu/pub/unity/lockers/ftp/csc_anon/tech/2012/TR-2012-6.pdf Thanks, -- ----------------------------------- --bcaec5555556130cc604c19b83ad Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi, All,

Recently the resea= rchers from Networking Research Group of North Carolina State University (N= CSU) have proposed an interesting receiver-based TCP solution to tackle buf= ferbloat in 3g/4g networks.=A0

They conducted extensive measurements in fo= ur major carriers in US and the largest carrier in Korea to verify the seve= re bufferbloat problem in currently commercial cellular networks. They cite= d the=A0
work from Bufferbloat group and further extended the work to cel= lular networks. Furthermore, they revealed the untold implementation of TCP= , an ad-hoc solution to mitigate bufferbloat, in smartphone's network s= tack (Android platform). The ad-hoc solution is sub-optimal in many scenari= os. Actually it merely mitigate bufferbloat problem in some scenarios. Ther= efore, the guys from NCSU propose a "Dynamic Receive Window Adjustment= " scheme to tackle bufferbloat problem. The extensive experiment resul= ts prove that the scheme is efficient and light-weight.=A0

It's really excited to find the new dir= ection to tackle bufferbloat, on TCP layer instead of routers (like AQM). T= he bufferbloat problem actually seems to be the most prominent, comparing w= ith other networks.=A0
Therefore, we suggest the more efforts to tackling bufferbloat p= roblem in cellular networks and seeking a good solution in TCP layer space.=


Thanks, =A0

--
-----------------------------------


--bcaec5555556130cc604c19b83ad--