From: Greg Stark <gsstark@mit.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: how flexible is ingress traffic policing to bandwidth limit?
Date: Wed, 09 Jun 2004 20:09:57 +0000 [thread overview]
Message-ID: <87ekoov6ga.fsf@stark.xeocode.com> (raw)
In-Reply-To: <87wu2hwp8e.fsf@stark.xeocode.com>
Sanjay Arora <skpobox@gawab.com> writes:
> Sorry to interrupt the flow, especially being a newbie, but won´t the
> sender just retransmit the dropped packets at the same rate?
no.
> I am not so thorogh with TCP/IP, but is there something in the protocol that
> speeds or slows the transmission.
yes.
> Please do explain in the TCP/IP for complete idiots terminology ;-))
You could do worse than this:
http://www.thinkingsecure.com/docs/TCPIP-Illustrated-1/tcp_time.htm#21_0
--
greg
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-09 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 0:26 [LARTC] Re: how flexible is ingress traffic policing to bandwidth limit? Greg Stark
2004-06-09 0:52 ` Damion de Soto
2004-06-09 3:33 ` Greg Stark
2004-06-09 4:01 ` Jason Boxman
2004-06-09 8:47 ` Greg Stark
2004-06-09 19:46 ` [LARTC] Re: how flexible is ingress traffic policing to Sanjay Arora
2004-06-09 20:09 ` Greg Stark [this message]
2004-06-09 21:06 ` [LARTC] Re: how flexible is ingress traffic policing to bandwidth limit? Jason Boxman
2004-06-11 0:17 ` [LARTC] Re: how flexible is ingress traffic policing to bandwidth Andy Furniss
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=87ekoov6ga.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.