University of Oregon

Applications in RPSL

Dave Meyer

Table of Contents

Stan Barber's Notes

There is a draft that describes this work.

Regular expressions are important

Since RPSL is a super-set of RIPE-181, there are some features not yet available in GRR.

Setting local pref in aut-num is an RPSL feature and not part of RIPE-181

Dave would like to see an IRR security model and he thinks the DNS model is a good one to emulate. He thinks that every object in the database should be signed.

Most folks at this NANOG meeting appear to use the text tools. Very few use the graphical tools.

Dave suggests that everyone should use a standard naming convention for AS Macros (like ASXXX: AS-Customers for all customers of a particular AS).

route-set is an RPSL extension that is really useful for referencing a group of routes.

There appears to be some confusion over how as-in works in generating router configurations.

John Curran wonders why there is some confusion. Another person suggests that the syntax is overloaded.

Dave suggests that route filtering should be used with customers and as-path filtering with peers.

It appears that not many folks at this NANOG meeting use the tools to generate router configuration. Dave uses RtConfig.

Questions & Answers

Dave asks:

One person responds: For BayNetworks router, RtConfig does not help yet. Dave believes that will be fixed in a month. Some folks don't want to learn another tool and would rather diddle the configuration language directly.

RIPE-181 to RPSL transition


This page has been accessed times since .
Copyright © 1997 Stan Barber. Reproduction with attribution granted.
Academ Consulting Services
P.O. Box 300481
Houston, Texas 77230-0481
Comments via email to www@academ.com
Academ Consulting Services is a registered trademark.