[149146] in North American Network Operators' Group
Re: pontification bloat (was 10GE TOR port buffers (was Re: 10G
daemon@ATHENA.MIT.EDU (Jared Mauch)
Sun Jan 29 15:40:46 2012
In-Reply-To: <596B74B410EE6B4CA8A30C3AF1A155EA09C967EB@RWC-MBX1.corp.seven.com>
From: Jared Mauch <jared@puck.nether.net>
Date: Sun, 29 Jan 2012 15:40:11 -0500
To: George Bonser <gbonser@seven.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
See below
Jared Mauch
On Jan 27, 2012, at 9:13 PM, George Bonser <gbonser@seven.com> wrote:
>> Router(config)# policy-map pol1
>> Router(config-pmap)# class class-default
>> Router(config-pmap-c)# bandwidth per 70
>> Router(config-pmap-c)# random-detect
>> Router(config-pmap-c)# random-detect ecn
>>=20
>> Requires other bits in the network to be ECN aware, but if they are,
>> good stuff.
>>=20
>> --
>=20
> +1
>=20
> There is no excuse these days for stuff not to be ECN aware. That GREATLY=
mitigates things as it makes hosts aware pretty much immediately that there=
is congestion and they don't have to wait for a lost packet to time out. I=
brought it up to a Brocade engineer once asking for the option to set ECN r=
ather than drop the packet and he said "nobody uses it". I told him nobody u=
ses it because you don't have the feature available. How can anyone use it i=
f you don't have the feature?
>=20
>=20
>=20
This sounds a lot like most peoples ipv6 rationale as well.=20
I'm still feeling some scars from last time Ecn was enabled in my hosts. Man=
y firewalls would eat packets with. Ecn enabled.=20=
