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: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 IAA09978 for <idr-archive@ietf.org>; Wed, 5 May 2004 08:29:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLLWk-00031l-30 for idr-archive@ietf.org; Wed, 05 May 2004 08:29:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLLVl-0002np-00 for idr-archive@ietf.org; Wed, 05 May 2004 08:28:30 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLLUp-0002af-00; Wed, 05 May 2004 08:27:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLLRR-0003K7-L3; Wed, 05 May 2004 08: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 1BLLNH-0002Je-3N for idr@optimus.ietf.org; Wed, 05 May 2004 08:19:48 -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 IAA09725 for <idr@ietf.org>; Wed, 5 May 2004 08:19:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLLNG-0000sL-1C for idr@ietf.org; Wed, 05 May 2004 08:19:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLLMK-0000ep-00 for idr@ietf.org; Wed, 05 May 2004 08:18:44 -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 1BLLLf-0000RP-00 for idr@ietf.org; Wed, 05 May 2004 08:18:04 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1]) by laptop2.kurtis.pp.se (Postfix) with ESMTP id C21123E60E4; Wed, 5 May 2004 14:18:00 +0200 (CEST)
In-Reply-To: <p05100311bcbd5c8b9ee8@[192.168.0.2]>
References: <20040504114849.230.qmail@web60704.mail.yahoo.com> <p05100311bcbd5c8b9ee8@[192.168.0.2]>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset="US-ASCII"; format="fixed"
Message-Id: <3CEBBC1F-9E8E-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: "Howard C. Berkowitz" <hcb@gettcomm.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:17:55 +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


On 2004-05-04, at 20.04, Howard C. Berkowitz wrote:

> At 7:48 AM -0400 5/4/04, Tulip Rasputin wrote:
>> 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).
>
> Does Euro-IX have any documentation on the route servers it does use?

Euro-IX is an association of exchange points. Euro-IX does not operate 
either route servers or exchage points.

>
> It sounds to me as if 1863 itself may need to be made Historic, but 
> there may be a need for several new, more focused documents:
>
>     1. Use of route servers for information collection.  This might 
> actually
>        be a subset of 1863, but perhaps with updates or 
> crossreferences to
>        such things as the new data collection communities.

Agreed.

>
>     2. BCP for production use such as Euro-IX.

Sitting in the EIX meeting at the current RIPE meeting, I will bring 
this up. A lot of the Euro-IX memebers that use route-servers are 
there. I will drop the idea in here to see if there is any interest.

> As an aside, this does get into the increasingly blurred area about 
> how much the IETF RFC process is appropriate for principally 
> operational documents. There have been a number of 
> suggestions/volunteers that NANOG might provide a document function, 
> but it seems reasonably clear that the Merit people don't have room on 
> their plate for this.  Whether Euro-IX, RIPE, or RIPE-NCC are possible 
> sponsors for operational documents, or if there needs to be a specific 
> group spun off for this, is another question. Obviously, IDR alone 
> can't answer that question, but I mention it here because many 
> relevant people see this discussion.

The EIX WG at RIPE is in the process of updating the "switch wishlist" 
and Euro-IX is working on a BCP. Perhaps those are better forums for 
BCPs on route servers.

- - kurtis -

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

iQA/AwUBQJjbd6arNKXTPFCVEQLopQCfVtyd9MOxIy70XeSwnl13EbTCKfgAn0Gi
lNW8EU4x2risKTLYK1BFO8nD
=yTTy
-----END PGP SIGNATURE-----


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