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 ]

Gabor Kiss kissg at sztaki.hu
Thu Jan 9 11:28:52 CET 1997

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

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 ]