"Representation of IP Routing Policies in the RIPE Database" paper.

Tony Bates <Tony.Bates@ripe.net> Mon, 22 February 1993 10:44 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12112; 22 Feb 93 5:44 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12108; 22 Feb 93 5:44 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa25384; 22 Feb 93 5:44 EST
Return-Path: <bgpd-owner@merit.edu>
Received: by merit.edu (5.65/1123-1.0) id AA16040; Mon, 22 Feb 93 05:19:52 -0500
Received: from ncc.ripe.net by merit.edu (5.65/1123-1.0) id AA16036; Mon, 22 Feb 93 05:19:45 -0500
Received: from mature.ripe.net by ncc.ripe.net with SMTP id AA04161 (5.65a/NCC-1.2); Mon, 22 Feb 1993 11:06:19 +0100
Message-Id: <9302221006.AA04161@ncc.ripe.net>
To: ripe-list@ripe.net
Subject: "Representation of IP Routing Policies in the RIPE Database" paper.
Cc: rs-imp@merit.edu, bgpd@merit.edu, orad-interest@ans.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tony Bates <Tony.Bates@ripe.net>
X-Organization: RIPE Network Coordination Centre
X-Phone: +31 20 592 5065
X-Fax: +31 20 592 5090
Date: Mon, 22 Feb 1993 11:06:18 +0100
X-Orig-Sender: tony@ripe.net

As discussed at the previous RIPE meeting I circulated the routing paper
draft to the RIPE routing group as proposed and have been folding in 
comments and additions for the last two weeks.

I have got a finished document that is felt complete enough
to be vented to a wider audience. The document is known as ripe-81.

Ref:           ripe-81
Title:         Representation of IP Routing Policies in the RIPE Database
Author:        Tony Bates, Jean-Michel Jouanigot, Daniel Karrenberg, Peter
               Lothberg, Marten Terpstra
Date:          22 February 1993
Format:        PS=151610 bytes TXT=73452 bytes
Obsoletes:
Obsoleted by:
Updates:
Updated by:
Old:

	The documents can be retrieved by anonymous ftp from

                ftp.RIPE.net

        in the directory 

                ripe/ripe-docs

	as the filenames
	
		ripe-81.txt (ascii based version)
		ripe-81.ps  (postscript version)


The document is specifically marked as "Work in progress" as we still need
it ratified at the next RIPE meeting. At this point if we reach consensus
it will be assigned a new ripe document number and this will be obseleted.

I encourage everyone to read this document. ALL COMMENTS ARE MOST WELCOME and
will be folded in as time permits for review at the next RIPE meeting.

As an update and also to perhaps help in reading as well. 

1)  We have a very basic prototype that can generate both cisco and gated 
accesslists from the database. A very small pilot has started and we here at 
the NCC are just generating access-lists derived from information from
a pseudo database using the proposed format. 

I will be contacting other potential partners in the pilot in due course. This 
will be done via the routing group list so as not to clutter the main list.

2) A very basic prototype of a "prtrace" type tool is also under way.

3) We have also started on a suite on "configurator" based tools
   to make life generally easier for network providers.

As I said all comments welcome. 
			

		Tony Bates, RIPE NCC