IETF Logo Mail Archive

Re: RFC1863 to historic? [Re: [Idr] Last Call on draft-ietf-idr-rfc2796bis-00.txt (fwd)]

Kurt Erik Lindqvist <kurtis@kurtis.pp.se> Wed, 05 May 2004 12:33 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10140 for <idr-archive@ietf.org>; Wed, 5 May 2004 08:33:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLLaf-0003vZ-Ln for idr-archive@ietf.org; Wed, 05 May 2004 08:33:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLLZe-0003Zo-00 for idr-archive@ietf.org; Wed, 05 May 2004 08:32:31 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLLYD-0003Hi-00; Wed, 05 May 2004 08:31:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLLWH-0004ub-K7; Wed, 05 May 2004 08:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLLSw-0003ZN-Lw for idr@optimus.ietf.org; Wed, 05 May 2004 08:25:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09863 for <idr@ietf.org>; Wed, 5 May 2004 08:25:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLLSv-0002A6-Dh for idr@ietf.org; Wed, 05 May 2004 08:25:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLLRz-0001xf-00 for idr@ietf.org; Wed, 05 May 2004 08:24:36 -0400
Received: from dhcp-9-56.ripemtg.ripe.net ([193.0.9.56] helo=laptop2.kurtis.pp.se) by ietf-mx with esmtp (Exim 4.12) id 1BLLRn-0001l0-00 for idr@ietf.org; Wed, 05 May 2004 08:24:23 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1]) by laptop2.kurtis.pp.se (Postfix) with ESMTP id 032013E6479; Wed, 5 May 2004 14:24:19 +0200 (CEST)
In-Reply-To: <20040504145218.G4638@nexthop.com>
References: <20040504114849.230.qmail@web60704.mail.yahoo.com> <Pine.LNX.4.44.0405041757060.4273-100000@netcore.fi> <20040504111830.C4638@nexthop.com> <p05100318bcbd8be8bfa0@[192.168.0.2]> <20040504145218.G4638@nexthop.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset="US-ASCII"; format="fixed"
Message-Id: <1F728B00-9E8F-11D8-A821-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: "Howard C. Berkowitz" <hcb@gettcomm.com>, idr@ietf.org
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: RFC1863 to historic? [Re: [Idr] Last Call on draft-ietf-idr-rfc2796bis-00.txt (fwd)]
To: Jeffrey Haas <jhaas@nexthop.com>
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: idr-admin@ietf.org
Errors-To: idr-admin@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/idr/>
Date: Wed, 05 May 2004 14:24:15 +0200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


(I think we are getting off-topic here)

On 2004-05-04, at 20.52, Jeffrey Haas wrote:

> When routers were deployed that could handle the number of eBGP views
> at a typical exchange point, the route servers were only useful
> (for route reduction purposes) for protecting smaller boxes.  I think
> it is likely today that most exchange points will typically find boxes
> deployed that are capable of handling the relevant full or partial
> mesh that the business model that XP operates under can use.


I think route-servers are in use at IXPs simply to simplify the process 
of setting up peers. If you look look at AMS-IX/Linx type of exchanges 
with 150-200 members, and you have an open peering policy, you will 
have quite a lot of work with just configuring the peers.


But, maybe this is more a topic for grow or RIPE / Nanog etc.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQJjc8aarNKXTPFCVEQJAPQCfb23uuffqN86QZ0F1BokC+CTDI9YAoIes
8LyB4JU4is6WnZO7yPa9nhyQ
=oyZK
-----END PGP SIGNATURE-----


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email