sub-allocations or something similar
- Previous message (by thread): Non-unique nic-hdl in RIPE database
- Next message (by thread): sub-allocations or something similar
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dmitry Morozovsky
marck at rinet.ru
Wed Jul 18 12:57:48 CEST 2001
Hello there colleagues, for some last years I'm working with RIPE DB I think it would be useful to have some kind of "sub-allocation" inetnum objects. Brief example in our current situation: there is downstream provider behind us, currently without its own address block, so I've assigned /21 for them. All that space was of course well-documented, with ripe-141's covering all the nets, and appropriate inetnum objects have been created. But, for aggregating purposes, I suppose aggregating inetnum for the whole /21 would be useful and self-documenting. I can create such object, but such object is considered as overlapped. I think about explicit route-object also, but size behind current minimum allocation size (/19 for 195/8 or /20 for newer) somewhat stops me :) Your (both community and especially RIPE NCC people) suggestions are strongly expected ;-) Thank you. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru *** ------------------------------------------------------------------------
- Previous message (by thread): Non-unique nic-hdl in RIPE database
- Next message (by thread): sub-allocations or something similar
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]