Routing Policy System Working Group of IETF

Cengiz Alaettinoglu

USC Information Sciences Institute

With assistance from:

Daniel Karrenberg

RIPE-NCC

This page is not yet complete.
Table of Contents

Stan Barber's Notes

Routing Policy Specification Language (RPSL)

It should model the decision process on the router, however it should be more abstract.

More domains are simple, but a few are very complex.

A variety of protocols should be supported.

It should be vendor independent.

RPSL should be able integrated into tools that are in use and new tools.

RPSL should be compatible to RIPE-181.

RPSL must support more policy filters than RIPE-181.

To make the language extensible, RPSL would have a dictionary object.

The Distributed Registry Model suffers from data conflicts between registries. Another talk at the May 1995 NANOG discussed this.

Synchonization and Atomicity are problems.

Tools are available to do some of this.

Mailling list is rps@isi.edu. Mailling to rps-request@isi.edu to join.
Copyright © 1995 Stan Barber. Reproduction with attribution granted.
Academ Consulting Services
P.O. Box 300481
Houston, Texas 77230-0481
Comments via email to www@academ.com