Re: [aqm] 答复: [iccrg] [tcpm] ECN support and usage on the Internet

"Scheffenegger, Richard" <rs@netapp.com> Wed, 20 March 2013 16:14 UTC

Return-Path: <rs@netapp.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7BD21F842A; Wed, 20 Mar 2013 09:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.015
X-Spam-Level:
X-Spam-Status: No, score=-10.015 tagged_above=-999 required=5 tests=[AWL=-0.095, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, SARE_SUB_ENC_UTF8=0.152, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rwoYnAKiDFs6; Wed, 20 Mar 2013 09:14:07 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 70A7821F8415; Wed, 20 Mar 2013 09:14:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,879,1355126400"; d="scan'208";a="32372231"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 20 Mar 2013 09:14:05 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r2KGE4l3029309; Wed, 20 Mar 2013 09:14:04 -0700 (PDT)
Received: from SACEXCMBX02-PRD.hq.netapp.com ([169.254.1.222]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0342.003; Wed, 20 Mar 2013 09:14:03 -0700
From: "Scheffenegger, Richard" <rs@netapp.com>
To: Simon Barber <simon@superduper.net>, Jim Gettys <jg@freedesktop.org>
Thread-Topic: [aqm] 答复: [iccrg] [tcpm] ECN support and usage on the Internet
Thread-Index: AQHOJPuQ4YV4mgvTF0iHLgehV1ZAsZiuv+6Q
Date: Wed, 20 Mar 2013 16:14:03 +0000
Message-ID: <012C3117EDDB3C4781FD802A8C27DD4F24AC06F7@SACEXCMBX02-PRD.hq.netapp.com>
References: <201303190904.32180.mkuehle@ikr.uni-stuttgart.de> <alpine.DEB.2.00.1303191014021.2309@uplift.swm.pp.se> <51487A27.7010904@hp.com> <CAGhGL2D=qncZZ0YG2jLfXwJLXLrXj4dXns_u66qPNBEVH2ZR4A@mail.gmail.com> <B2CE202A35DFDD4A904DA7497D7D2B9830F98A@CNHZ-EXMAIL-10.ali.com> <CAGhGL2AbSUvm-XcgH6y2gRy_hYj4mc4YU+u7LeuiCp0DzfsRDg@mail.gmail.com> <5148F80F.5000401@superduper.net>
In-Reply-To: <5148F80F.5000401@superduper.net>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.106.53.53]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "tcpm@ietf.org" <tcpm@ietf.org>, Rick Jones <rick.jones2@hp.com>, "iccrg@irtf.org" <iccrg@irtf.org>, 天澜 <tianlan.lhh@alibaba-inc.com>, "aqm@ietf.org" <aqm@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [aqm] 答复: [iccrg] [tcpm] ECN support and usage on the Internet
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 16:14:08 -0000

Hi Simon,


For one, throughput is the one metric, that should NOT be influenced by ECN, actually. So if that is "in the noise", that is a very good sign; 

The more interesting metrics, that are addressed with ECN are latency ("page load times") and network efficiency (fewer packets are needlessly processed in initial hops, just to be dropped by the penultimate hop; that bandwidth can be allocated to other flows etc).

Other schemes that reduce latency usually do so by trading a good share of bandwidth... (credit allocation scheme used in FC, anyone?)


ECN hat a huge issue of deployability issues, that had nothing to do with the mechanism itself, but with misbehaving equipment on the signaling - and the institutional memory still remembers those albeit any new signaling scheme could run into similar issues (independent of the mechanisms).


Ie. some people still haven't got the Memo that IPv4 TOS was deprecated quite some time ago (now DiffServ/ECN),

Regards,

Richard Scheffenegger



> -----Original Message-----
> From: aqm-bounces@ietf.org [mailto:aqm-bounces@ietf.org] On Behalf Of
> Simon Barber
> Sent: Mittwoch, 20. März 2013 00:43
> To: Jim Gettys
> Cc: Rick Jones; iccrg@irtf.org; tcpm@ietf.org; 天澜; aqm@ietf.org; Mikael
> Abrahamsson
> Subject: Re: [aqm] 答复: [iccrg] [tcpm] ECN support and usage on the
> Internet
> 
> I'm not sure why people are so obsessed with ECN - the little data I've
> seen about it showed that it's effect on system throughput was in the
> noise. Sure, wireless guys don't like to waste precious wireless
> bandwidth, but they're not dropping packets that have used up the precious
> wireless bandwidth. They get dropped before the wireless link.
> 
> Simon
>