USC / Information Sciences Institute Cengiz Alaettinoglu, IETF July ?95

1 of 6
Syntax Options for RPSL Policy Terms

Cengiz Alaettinoglu

USC / Information Sciences Institute Cengiz Alaettinoglu, IETF July ?95

2 of 6
Current Ripe-181 Syntax

as-in: from AS1 5 accept <filter>
interas-in: from AS1 x.x.x.x/32 x.x.x.y/32 (pref=5) accept <filter>

as-out: to AS1 announce <filter>
interas-out: to AS1 x.x.x.x/32 x.x.x.y/32 (metric-out=5) announce <filter>

USC / Information Sciences Institute Cengiz Alaettinoglu, IETF July ?95

3 of 6
Option 1: New Syntax

export filter AS2 AS4
parameters AS2 * * action med = 1 parameters AS6 * * action ippm = 2;

import filter AS3
parameters AS2 l1 r1 action pref = 1 parameters AS2 l2 r2 action pref = 2 parameters AS6 * * action pref = 3;

Compatibility via a translater tool! USC / Information Sciences Institute Cengiz Alaettinoglu, IETF July ?95

4 of 6
Option 2: Ripe Compatible Syntax

get rid of interas-in/interas-out
extend as-in/as-out

as-in: from <interface> <action>
from <interface> <action>
. . .
accept <filter>

a special case:
as-in: from AS1 5 accept AS1

USC / Information Sciences Institute Cengiz Alaettinoglu, IETF July ?95

5 of 6
<interface>
* * *
AS1 * *
AS1
AS1 x.x.x.x *
AS1 x.x.x.x x.x.x.y
<action>
action ...
5 means ?action pref = 5;?
<filter>
with extensions

USC / Information Sciences Institute Cengiz Alaettinoglu, IETF July ?95

6 of 6
Comparison

compatibility tool
development readability

new thru a tool clean syntax elegant ripe ext yes hack 2 syntaxes