Re: hierarchical route objects, part 1
Dear Cengiz,
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.
This can be prevented by this object route: 0.0.0.0/0 descr: for authorisation purposes origin: AS0 mnt-lower: MAINT-INTERNIC etc. Internic (or whatever else) may delegate maintainer rights as well as allocates address ranges. Gabor
Gabor, For a second lets assume that all the address registries did maintainer delegation. It still does not work. Gabor Kiss (kissg@sztaki.hu) on January 9:
This can be prevented by this object route: 0.0.0.0/0 descr: for authorisation purposes origin: AS0 mnt-lower: MAINT-INTERNIC etc.
Internic (or whatever else) may delegate maintainer rights as well as allocates address ranges.
Say, I have 128.8/16, internic delegates me as the maintainer. You have 128.9/16 and are delegated for it. Foo aggregates 128.9/16 and 128.8/16 into 128.8/15. But no entity allocated 128.8/15, so foo is not delegated as the maintainer. You and I can not delegate foo either since aggregation is a local foo matter. 0.0.0.0/0 route object will prevent foo from registering 128.8/15. Cengiz -- Cengiz Alaettinoglu Information Sciences Institute (310) 822-1511 University of Southern California http://www.isi.edu/~cengiz
participants (2)
-
Cengiz Alaettinoglu -
Gabor Kiss