ANY

Dale S. Johnson (dsj at merit.edu) on December 14:
> As for the folks who use registries for config-file generators, they
> may still have need for queries like "I want to interpret the policy word
> `ANY' as a list of all net numbers registered in the IRR.  Please return
> all those nets". 

I think assigning another meaning to ANY is a mistake (two different
semantics for one syntactic term). Especially when there are
already defined alternatives.

We have an implicitly defined community "RIPE" which is the set of
routes with "source: RIPE" attribute. I think we should extend this to
all databases, i.e. RADB, CANET, MCI, ... communities to mean the set
of routes with "source: RADB", CANET, MCI, etc.

We can even define an IRR community to mean the set of routes that are
registered in a recognized database (note that each database will
contain a "registries" object with the names of the recognised
databases as discussed in the IRR meeting.)

We can also have implicit as macros, AS-RIPE, AS-RADB, AS-MCI to mean
all the AS's with "source: RIPE", RADB, MCI etc.

If someone wants the above unusual meaning of ANY, he would just type
IRR.

What do you guys think?

Cengiz

-- 
Cengiz Alaettinoglu       Information Sciences Institute
cengiz at isi.edu            University of Southern California




-------- Logged at  Mon Dec 19 18:05:42 MET 1994  ---------