nanog mailing list archives
Re: UUNET Routing issues
From: "Stephen Sprunk" <ssprunk () cisco com>
Date: Thu, 3 Oct 2002 17:32:32 -0500
Thus spake "Iljitsch van Beijnum" <iljitsch () muada com>
At 155 Mbps you need 32 MB worth of buffer space to arrive at a delay like this. I wouldn't put it past ATM vendors to think of this kind of over-enthusiastic buffering as a feature rather than a bug.
Traditionally, it's ATM switches that have tiny buffers and routers that have excessive buffers. ATM networks have closed-loop feedback and ingress policing mechanisms to handle this scenario; IP networks just throw buffers at the problem and hope it works.
Does anyone have any thoughts on optimum buffer sizes?
The "correct" amount of buffer space for a link is equal to its bandwidth-delay product. Unfortunately, this requires per-link testing and configuration on the part of the operator, which is extremely rare. S
Current thread:
- Re: UUNET is not the Internet (and neither is AOL), (continued)
- Re: UUNET is not the Internet (and neither is AOL) Dave Israel (Oct 07)
- Re: UUNET is not the Internet (and neither is AOL) Petri Helenius (Oct 07)
- Re: UUNET Routing issues Petri Helenius (Oct 04)
- Re: UUNET Routing issues Valdis . Kletnieks (Oct 04)
- Re: UUNET Routing issues Petri Helenius (Oct 04)
- Re: UUNET Routing issues Iljitsch van Beijnum (Oct 04)
- Re: UUNET Routing issues Rafi Sadowsky (Oct 05)
- Re: UUNET Routing issues Iljitsch van Beijnum (Oct 05)
- Re: UUNET Routing issues Marshall Eubanks (Oct 05)
- Re: UUNET Routing issues Petri Helenius (Oct 05)
- Re: UUNET Routing issues Stephen Sprunk (Oct 03)
- Re: UUNET Routing issues Scott Granados (Oct 06)