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

Tulip Rasputin <tulip_rasputin@yahoo.ca> Tue, 04 May 2004 14:40 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 KAA05130 for <idr-archive@ietf.org>; Tue, 4 May 2004 10:40:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL15q-0006jJ-IM for idr-archive@ietf.org; Tue, 04 May 2004 10:40:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL14f-0006Ya-00 for idr-archive@ietf.org; Tue, 04 May 2004 10:39:10 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BL13p-0006R9-00; Tue, 04 May 2004 10:38:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL0yk-00054U-84; Tue, 04 May 2004 10:33:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKyRY-0004wA-IY for idr@optimus.ietf.org; Tue, 04 May 2004 07:50:36 -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 HAA25709 for <idr@ietf.org>; Tue, 4 May 2004 07:50:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKyRX-0003fD-M8 for idr@ietf.org; Tue, 04 May 2004 07:50:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKyQb-0003TB-00 for idr@ietf.org; Tue, 04 May 2004 07:49:38 -0400
Received: from web60704.mail.yahoo.com ([216.109.117.227]) by ietf-mx with smtp (Exim 4.12) id 1BKyQK-0003GN-00 for idr@ietf.org; Tue, 04 May 2004 07:49:20 -0400
Message-ID: <20040504114849.230.qmail@web60704.mail.yahoo.com>
Received: from [202.144.106.186] by web60704.mail.yahoo.com via HTTP; Tue, 04 May 2004 07:48:49 EDT
From: Tulip Rasputin <tulip_rasputin@yahoo.ca>
Subject: Re: RFC1863 to historic? [Re: [Idr] Last Call on draft-ietf-idr-rfc2796bis-00.txt (fwd)]
To: idr@ietf.org
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 07:48:49 -0400
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

Jeff,

[..] 
> 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).

> > The 
> > fact that they did not get a wide vendor support is bug not a feature. 
> 
> Please note that RFC 1863 doesn't so much define a route server as
> it does a route-reflector style mechanism for route servers.  This is
> the bit that didn't get wide deployment.

Am sure IXPs would love to have better ways to implement route servers. If there are any IXPs
here, they could probably second me!

> IMO, 1863 is a bit more complicated than what we would want these
> days given modern route reflection techniques.  If a need exists to
> allow multiple views to be passed around in BGP there are better ways
> to go about it.

Like how?

Rasputin.


______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca

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