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]/
[db-wg] Abuse-C/IRT
- Previous message (by thread): [db-wg] Specifying no routes
- Next message (by thread): [db-wg] Abuse-C/IRT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Thu May 6 12:05:31 CEST 2004
Hi, On Thu, May 06, 2004 at 12:00:36PM +0200, Pim van Pelt wrote: > I would have expected the IPv6 IRT usage to be much higher, because > SixXS uses IRT in our software (and we are accountable for 3000 or so of > the inet6num objects in the RIPE database). We only appear to use them > in the allocated (/40) blocks, rather than in the assigned space to > endusers. I've ammended the code so you can expect some 2800 or so > objects to contain an IRT reference after the next iteration of our > cronscript (once daily). > > Hopefully this sets an example for other IPv6 users. Ummm, isn't the whole point of the mnt-irt: that it works "downstream", so you don't *have* to put it on all 2800 inet6num entries, but just on the /32 or /40 allocations? But even so: compared to the total number of IPv6 addresses covered by the /32s allocated right now, your mnt-irt:s on a handful of /40s are a good start but won't make a big numerical impact... Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 60210 (58081) SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
- Previous message (by thread): [db-wg] Specifying no routes
- Next message (by thread): [db-wg] Abuse-C/IRT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]