From: jamal <hadi@cyberus.ca>
To: linux-kernel@vger.rutgers.edu
Subject: Re: my broken TCP is faster on broken networks
Date: Fri, 11 Sep 1998 20:39:46 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.3.96.980911203117.13283B-100000@shell> (raw)
Theodore Y. Ts'o (tytso@MIT.EDU) Fri, 11 Sep 1998 18:36:43 -0400
>I don't normally follow the TCP implementor's working group (*), so I
>don't know if they actually followed through on his suggestion;
>Matthais's note seems to indicate that they did.
I think it is just considered good practise to punish misbehaving users
at the moment. Not sure if any vendor has implemented anything yet.
There is an informational RFC out:
http://info.internet.isi.edu:80/in-notes/rfc/files/rfc2309.txt
Unfortunately, they dont mention remedies for misbehaving flows. They do
suggest RED; however, there are variants of RED that exist with specific
intention of punishing misbehaving users.
A really interesting pointer page is at:
http://www-nrg.ee.lbl.gov/floyd/tcp_unfriendly.html
cheers,
jamal
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html
reply other threads:[~1998-09-11 22:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.GSO.3.96.980911203117.13283B-100000@shell \
--to=hadi@cyberus.ca \
--cc=linux-kernel@vger.rutgers.edu \
/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®