mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J.D. Bakker" <bakker@thorgal.et.tudelft.nl>
To: Pete Zaitcev <zaitcev@metabyte.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Maxwell strikes the heart (ECN: Clearing the air)
Date: Tue, 30 Jan 2001 01:28:25 +0100	[thread overview]
Message-ID: <a05010403b69bb854d7de@[130.161.115.44]> (raw)
In-Reply-To: <3A75F4D7.D7957633@metabyte.com>
In-Reply-To: <3A75F4D7.D7957633@metabyte.com>

At 14:55 -0800 29-01-2001, Pete Zaitcev wrote:
>So far I fail to see how a repainted NAK, kludged into a NAKless protocol,
>would improve stability of the Internet. If anything, it is going to
>exaggerate traffic oscillations.

If anything RED will *reduce* oscillations by alleviating retransmit 
synchronization.

>  I would appreciate couple of links
>to reputable studies or discussions on the subject.

See

http://www.aciri.org/floyd/ecn.html
http://www.aciri.org/floyd/red.html

(I particularly like ftp://ftp.ee.lbl.gov/talks/vj-nanog-red.pdf)

RED and ECN can be considered independently (although they do work 
together quite well). You can see ECN as a way of the network telling 
the endpoints "Normally I would have dropped this datagram, but I'll 
let you get away with it this time". TCP behavior on reception of an 
ECN should be the same as when a datagram is dropped, but without the 
latency (and jitter) that is the result of a lost datagram.

JDB.
[using RED/ECN-like protocols for latency sensitive video 
communications over a wireless link]
-- 
LART. 250 MIPS under one Watt. Free hardware design files.
http://www.lart.tudelft.nl/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-30  0:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29 22:55 Pete Zaitcev
2001-01-30  0:28 ` J.D. Bakker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='a05010403b69bb854d7de@[130.161.115.44]' \
    --to=bakker@thorgal.et.tudelft.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@metabyte.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®