IETF Logo Mail Archive

Re: [RAM] Number of DFZ routers

"Chris L. Morrow" <christopher.morrow@verizonbusiness.com> Tue, 29 May 2007 21:47 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ht9Xb-0000JW-2p; Tue, 29 May 2007 17:47:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ht9XZ-0000JP-Pg for ram@iab.org; Tue, 29 May 2007 17:47:41 -0400
Received: from pmesmtp01.wcom.com ([199.249.20.1] helo=pmesmtp01.mci.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ht9XY-0000Ta-HZ for ram@iab.org; Tue, 29 May 2007 17:47:41 -0400
Received: from dgismtp06.wcomnet.com ([166.38.58.89]) by firewall.mci.com (Iplanet MTA 5.2) with ESMTP id <0JIT00K0OOJBV4@firewall.mci.com> for ram@iab.org; Tue, 29 May 2007 21:47:35 +0000 (GMT)
Received: from dgismtp06.wcomnet.com ([127.0.0.1]) by dgismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08 (built Sep 22 2005)) with SMTP id <0JIT00MP1OJBNX@dgismtp06.mcilink.com> for ram@iab.org; Tue, 29 May 2007 21:47:35 +0000 (GMT)
Received: from marvin.argfrp.us.uu.net ([153.39.56.19]) by dgismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08 (built Sep 22 2005)) with ESMTP id <0JIT00N73OJA1I@dgismtp06.mcilink.com> for ram@iab.org; Tue, 29 May 2007 21:47:35 +0000 (GMT)
Date: Tue, 29 May 2007 21:47:34 +0000 (GMT)
From: "Chris L. Morrow" <christopher.morrow@verizonbusiness.com>
Subject: Re: [RAM] Number of DFZ routers
In-reply-to: <aahcpvgvh6.fsf@switch.ch>
X-X-Sender: cmorrow@marvin.argfrp.us.uu.net
To: Simon Leinen <simon.leinen@switch.ch>
Message-id: <Pine.GSO.4.58.0705292146090.11314@marvin.argfrp.us.uu.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
References: <c46.14c54f20.338bf215@aol.com> <Pine.GSO.4.58.0705281534520.11314@marvin.argfrp.us.uu.net> <465AFCE4.9040401@cisco.com> <aahcpvgvh6.fsf@switch.ch>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: HeinerHummel@aol.com, rw@firstpr.com.au, ram@iab.org
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org


On Tue, 29 May 2007, Simon Leinen wrote:

> I think Robin's question was about *operational* routers, i.e.,
> configuration of routers in actual use in the Internet, not about
> hardware/software limits:

there was a reason I quoted the idb limits... on a SP network more ports
(logical and physical) you can stick in a rack the better you are. SP's
are always driving for more ports in less face-plate-space. The IDB limit
is probably a good start for today, and tomorrow I'd expect SP's to drive
that higher...

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram

v2.8.7 | Report a Bug | By Email