IETF Logo Mail Archive

Re: [rrg] IPv4 & IPv6 routing scaling problems

HeinerHummel@aol.com Sun, 14 February 2010 20:37 UTC

Return-Path: <HeinerHummel@aol.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 804203A7A56 for <rrg@core3.amsl.com>; Sun, 14 Feb 2010 12:37:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level:
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.259, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvEJMDwHC7ms for <rrg@core3.amsl.com>; Sun, 14 Feb 2010 12:37:50 -0800 (PST)
Received: from imr-da01.mx.aol.com (imr-da01.mx.aol.com [205.188.105.143]) by core3.amsl.com (Postfix) with ESMTP id 920AF3A7A51 for <rrg@irtf.org>; Sun, 14 Feb 2010 12:37:50 -0800 (PST)
Received: from imo-ma02.mx.aol.com (imo-ma02.mx.aol.com [64.12.78.137]) by imr-da01.mx.aol.com (8.14.1/8.14.1) with ESMTP id o1EKd0ej022076; Sun, 14 Feb 2010 15:39:00 -0500
Received: from HeinerHummel@aol.com by imo-ma02.mx.aol.com (mail_out_v42.9.) id o.ce0.5fb30079 (43972); Sun, 14 Feb 2010 15:38:56 -0500 (EST)
Received: from magic-m21.mail.aol.com (magic-m21.mail.aol.com [172.20.22.194]) by cia-dd03.mx.aol.com (v127.7) with ESMTP id MAILCIADD035-abc44b785f5dc6; Sun, 14 Feb 2010 15:38:53 -0500
From: HeinerHummel@aol.com
Message-ID: <20696.13f4eda4.38a9b95d@aol.com>
Date: Sun, 14 Feb 2010 15:38:53 -0500
To: morrowc.lists@gmail.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_20696.13f4eda4.38a9b95d_boundary"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-ORIG-IP: 95.91.134.11
X-AOL-IP: 172.20.22.194
X-AOL-SENDER: HeinerHummel@aol.com
Cc: rrg@irtf.org
Subject: Re: [rrg] IPv4 & IPv6 routing scaling problems
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Feb 2010 20:37:51 -0000

 
In einer eMail vom 14.02.2010 21:25:40 Westeuropäische Normalzeit schreibt  
morrowc.lists@gmail.com:

> a  T1600 has 8 slots of 4 PIC's each, you can get 1x10G for each PIC.
> a  CRS1 (full-height) chassis has 16 slots, 4x10G on each I  believe?
>
> you can get this sort of info, as an approximation of  connectedness of
> a node from every vendor's website.

oops,  keeping in mind that's physical interfaces, with some MPLS
schemes the  'dfz' router could be connected to each DFZ router in the
same ASN over a  logical link (LSP), so... a single DFZ router could
have (in the case of a  moderate network, with US only coverage)
something like 80+ neighbors over  these logical paths.

-chris


Thanks Chris,
 
80+ neighbors, that's a whopper
 
Wouldn't you favor a solution where you can exploit that densitiy rather  
than  be frightened by it ?
 
Heiner
 
 
 
 
Heiner

v2.23.0 | Report a Bug | By Email