hierarchical route objects, part 1

Joachim,

I like the idea that the maintainer of the autnum object can control
the route objects created with its as number as the origin. And agree
with Daniel, a notification is probably sufficient when the origins
ASes are different.

With respect to:
Joachim Schmitz (Schmitz at rus.uni-stuttgart.de) on January 8:
>  * Then for route-objects the same rules apply as for inetnum-objects with
>    respect to IP subranges: If a route-object contains a "mnt-lower" attri-
>    bute it controls all more specific route-objects immediately below.

I disagree that this is a good idea. If I register the following route
object (which actually exists):

route:       128.0.0.0/1
descr:       HALF-DEFAULT-ONE
origin:      AS1800
advisory:    AS690 1:1800 2:1239
mnt-by:      MAINT-AS1800
mnt-lower:   MAINT-AS1800

nobody else can register any route objects.

Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
(310) 822-1511                University of Southern California
http://www.isi.edu/~cengiz