All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim Fleming" <jfleming@anet.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: further CBQ/tc documentation ds9a.nl/lartc/manpages
Date: Mon, 10 Dec 2001 13:42:40 +0000	[thread overview]
Message-ID: <marc-lartc-100799102730950@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100785524509147@msgid-missing>

----- Original Message ----- 
From: "bert hubert" <ahu@ds9a.nl>
To: "Henrik Nordstrom" <hno@marasystems.com>
Cc: "Martin Devera" <devik@cdi.cz>; "jamal" <hadi@cyberus.ca>; <lartc@mailman.ds9a.nl>
Sent: Monday, December 10, 2001 6:14 AM
Subject: Re: [LARTC] Re: further CBQ/tc documentation ds9a.nl/lartc/manpages


> On Mon, Dec 10, 2001 at 10:59:38AM +0100, Henrik Nordstrom wrote:
> 
> > TCP is generally too smart to be delayed proper by "randomly" dropped packets 
> > without any signs in RTT. Especially when the RTT is small.
> 
> Richard Stevens disagrees with you. 
> 

I assume you mean the late Richard Stevens, who passed away at an early age
after helping to document the BSD Internet Protocol software in great detail.

BTW, while on the subject of TCP, Qs, etc. It seems rather odd that people
engrossed in protocols, would not consider the long history of making sure that
layers are preserved or at least considered. You may have heard of Layer 2
(Network) and Layer 3 (Transport). It would seem that much of the work on
Queues and the shaping of flows would most properly be located in Layer 3.
The additions we are making to Layer 2, focus on extending the addressing
and other functionality of Layer 2. It seems that Layer 2 will not have enough
bits to accommodate all of the ideas that people are pouring into it.

This may help...
http://www.dot-biz.com/IPv4/Tutorial/

Jim Fleming
http://www.IPv8.info
IPv16....One Better !!


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2001-12-10 13:42 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-08 20:43 [LARTC] Re: further CBQ/tc documentation ds9a.nl/lartc/manpages jamal
2001-12-08 21:30 ` bert hubert
2001-12-08 21:56 ` jamal
2001-12-08 23:08 ` bert hubert
2001-12-08 23:29 ` jamal
2001-12-08 23:30 ` jamal
2001-12-08 23:45 ` Henrik Nordstrom
2001-12-08 23:54 ` bert hubert
2001-12-09  1:19 ` jamal
2001-12-09  1:35 ` bert hubert
2001-12-09  2:11 ` jamal
2001-12-09  2:30 ` jamal
2001-12-09 11:38 ` Henrik Nordstrom
2001-12-09 14:40 ` bert hubert
2001-12-09 14:49 ` jamal
2001-12-09 15:01 ` jamal
2001-12-09 15:49 ` Henrik Nordstrom
2001-12-09 16:45 ` Henrik Nordstrom
2001-12-09 21:41 ` jamal
2001-12-09 22:33 ` Michael T. Babcock
2001-12-09 22:36 ` Michael T. Babcock
2001-12-10  1:12 ` Cédric Rivard
2001-12-10  7:53 ` Don Cohen
2001-12-10  8:38 ` Martin Devera
2001-12-10  8:41 ` Henrik Nordstrom
2001-12-10  9:59 ` Henrik Nordstrom
2001-12-10 11:35 ` Martin Devera
2001-12-10 11:59 ` Martin Devera
2001-12-10 12:00 ` Henrik Nordstrom
2001-12-10 12:14 ` bert hubert
2001-12-10 12:25 ` Henrik Nordstrom
2001-12-10 12:52 ` Martin Devera
2001-12-10 13:29 ` jamal
2001-12-10 13:40 ` Martin Devera
2001-12-10 13:42 ` Jim Fleming [this message]
2001-12-10 13:52 ` Michael T. Babcock
2001-12-10 13:54 ` Michael T. Babcock
2001-12-10 13:56 ` Gerry Creager N5JXS
2001-12-10 13:58 ` Michael T. Babcock
2001-12-10 14:02 ` Martin Devera
2001-12-10 14:51 ` Jim Fleming

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=marc-lartc-100799102730950@msgid-missing \
    --to=jfleming@anet.com \
    --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.