Re: [Tsvwg] ECN & PMTU

Kostas Pentikousis <kostas@cs.sunysb.edu> Tue, 16 April 2002 20:28 UTC

Date: Tue, 16 Apr 2002 16:28:24 -0400 (EDT)
From: Kostas Pentikousis <kostas@cs.sunysb.edu>
X-X-Sender: <kostas@compserv3>
To: Jacob Heitz <jheitz@lucent.com>
Cc: Arun Prasad <arun@netlab.hcltech.com>, tsvwg <tsvwg@ietf.org>, <tcp-impl@grc.nasa.gov>
Subject: Re: [Tsvwg] ECN & PMTU
In-Reply-To: <3CB2C285.FA4806AB@lucent.com>
Message-ID: <Pine.GSO.4.33.0204161612310.17719-100000@compserv3>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-tcp-impl@grc.nasa.gov
Precedence: bulk
Status: RO
Content-Length: 1235
Lines: 27

On Tue, 9 Apr 2002, Jacob Heitz wrote:

[...]
  | Source quenching was always controversial.
  | It is considered higher impact, because it adds
  | an extra packet to the network. Setting a CE
  | bit adds nothing that was not there before anyway,
  | so is considered to be safer, or lower impact.
  |
  | Yes, it's slower than having the congested router
  | send an ICMP.

I'm not sure that's really true. In fact, I've heard several times that Source
Quench (SQ) via ICMP is more expensive for current generation routers than
setting a bit. I remember reading that any packets needing "special" treatment
are placed in a separate (lower priority) queue and are dealt with when the
router load drops (a bit). Setting a bit is not considered "special" treatment
but creating a packet (setting source and destination addresses, etc.) is. If
this is true, and ECN was spec'ed so that the router would send an SQ ICMP
packet back to the sender instead of setting a bit (RFC 3168), then in most
cases the congestion notification would actually arrive later than an RTT.

Just my $0.02,

Kostas
______________________________________________________________________
Kostas Pentikousis @ CS Stony Brook @ http://www.cs.sunysb.edu/~kostas