IETF Logo Mail Archive

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

Pekka Savola <pekkas@netcore.fi> Tue, 04 May 2004 15:12 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 LAA07361 for <idr-archive@ietf.org>; Tue, 4 May 2004 11:12: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 1BL1az-0001oT-Q5 for idr-archive@ietf.org; Tue, 04 May 2004 11:12:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL1a1-0001iQ-00 for idr-archive@ietf.org; Tue, 04 May 2004 11:11:34 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BL1Z3-0001cD-00; Tue, 04 May 2004 11:10:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL1Vd-0006cA-AH; Tue, 04 May 2004 11:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL1PX-0004wl-8P for idr@optimus.ietf.org; Tue, 04 May 2004 11:00:43 -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 LAA06658 for <idr@ietf.org>; Tue, 4 May 2004 11:00:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL1PU-0000mJ-N2 for idr@ietf.org; Tue, 04 May 2004 11:00:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL1Oe-0000hp-00 for idr@ietf.org; Tue, 04 May 2004 10:59:49 -0400
Received: from netcore.fi ([193.94.160.1]) by ietf-mx with esmtp (Exim 4.12) id 1BL1Nf-0000aT-00 for idr@ietf.org; Tue, 04 May 2004 10:58:47 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id i44EwBN04384; Tue, 4 May 2004 17:58:11 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Tulip Rasputin <tulip_rasputin@yahoo.ca>
cc: idr@ietf.org
Subject: Re: RFC1863 to historic? [Re: [Idr] Last Call on draft-ietf-idr-rfc2796bis-00.txt (fwd)]
In-Reply-To: <20040504114849.230.qmail@web60704.mail.yahoo.com>
Message-ID: <Pine.LNX.4.44.0405041757060.4273-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
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: Tue, 04 May 2004 17:58:11 +0300
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=AWL autolearn=no version=2.60

On Tue, 4 May 2004, Tulip Rasputin wrote:
> [..] 
> > All of this said, there are other small exchanges that are said to
> > be deploying route servers, but it sounds like these are small regionals.
> 
> I would not agree to this! There is this european internet exchange association (euro-ix) where
> europe's leading ISPs connect to permit the exchange of network information. I am aware of most of
> them using route servers (though not the ones like defined in 1863).

Route collectors or route servers used for other debugging purposes 
are an entirely different thing from route servers used to replace 
iBGP mesh, right?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


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

v2.23.0 | Report a Bug | By Email