This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
hierarchical route objects, part 1
- Previous message (by thread): hierarchical route objects, part 1
- Next message (by thread): hierarchical route objects, part 1
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cengiz Alaettinoglu
cengiz at ISI.EDU
Thu Jan 9 18:25:34 CET 1997
Gabor, For a second lets assume that all the address registries did maintainer delegation. It still does not work. Gabor Kiss (kissg at 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
- Previous message (by thread): hierarchical route objects, part 1
- Next message (by thread): hierarchical route objects, part 1
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]