Re: RFC1863 to historic? [Re: [Idr] Last Call on draft-ietf-idr-rfc2796bis-00.txt (fwd)]
Kurt Erik Lindqvist <kurtis@kurtis.pp.se> Tue, 04 May 2004 15:29 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 LAA08349 for <idr-archive@ietf.org>; Tue, 4 May 2004 11:29:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL1rX-0003Hk-9o for idr-archive@ietf.org; Tue, 04 May 2004 11:29:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL1qX-0003BA-00 for idr-archive@ietf.org; Tue, 04 May 2004 11:28:38 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BL1pY-00034N-00; Tue, 04 May 2004 11:27:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL1m5-0002V1-1K; Tue, 04 May 2004 11:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL1eB-0000f4-2y for idr@optimus.ietf.org; Tue, 04 May 2004 11:15:51 -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 LAA07627 for <idr@ietf.org>; Tue, 4 May 2004 11:15:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL1eA-00027D-5Z for idr@ietf.org; Tue, 04 May 2004 11:15:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL1dI-00022S-00 for idr@ietf.org; Tue, 04 May 2004 11:14:56 -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 1BL1ca-0001xB-00 for idr@ietf.org; Tue, 04 May 2004 11:14:12 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1]) by laptop2.kurtis.pp.se (Postfix) with ESMTP id B94113DFD70; Tue, 4 May 2004 17:14:10 +0200 (CEST)
In-Reply-To: <20040504114849.230.qmail@web60704.mail.yahoo.com>
References: <20040504114849.230.qmail@web60704.mail.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset="US-ASCII"; format="fixed"
Message-Id: <AEBC7D56-9DDD-11D8-A821-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: 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: Tulip Rasputin <tulip_rasputin@yahoo.ca>
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: Tue, 04 May 2004 17:14:05 +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 >> 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). As the current chair of Euro-IX... yes there is a lot of interest in route servers and I think the two most widely used are at two out of the four largest IXPs in Europe. >> 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! I think 'it depends'. I don't think IXPs per se care, the customers of the IXPs do and the IXPs try to serve them as best as possible. And I do think there is need for it, and also a need for updated documentation. - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQJezQKarNKXTPFCVEQIqggCdG+mYAze2an1maM1Q+BagZ9jh3iUAoLzg QWBWTgN/8AGN1pCxAVZaSDsV =Uz3Z -----END PGP SIGNATURE----- _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- RFC1863 to historic? [Re: [Idr] Last Call on draf… Pekka Savola
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Jeffrey Haas
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Robert Raszuk
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Jeffrey Haas
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Tulip Rasputin
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Jeffrey Haas
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Pekka Savola
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Kurt Erik Lindqvist
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Jeffrey Haas
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … John G. Scudder
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Howard C. Berkowitz
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Howard C. Berkowitz
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Jeffrey Haas
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Curtis Villamizar
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Paul Jakma
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Kurt Erik Lindqvist
- Re: RFC1863 to historic? [Re: [Idr] Last Call on … Kurt Erik Lindqvist