[78825] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: 72/8 friendly reminder

daemon@ATHENA.MIT.EDU (Alex Bligh)
Wed Mar 23 14:14:00 2005

Date: Wed, 23 Mar 2005 19:12:01 +0000
From: Alex Bligh <alex@alex.org.uk>
Reply-To: Alex Bligh <alex@alex.org.uk>
To: Randy Bush <randy@psg.com>, nanog@merit.edu
Cc: Alex Bligh <alex@alex.org.uk>
In-Reply-To: <16961.47792.567033.407015@roam.psg.com>
Errors-To: owner-nanog@merit.edu




--On 23 March 2005 10:51 -0800 Randy Bush <randy@psg.com> wrote:

> a bit more coffee made me realize that what might best occur would
> be for the rir, some weeks BEFORE assigning from a new block issued
> by the iana, put up a pingable for that space and announce it on
> the lists so we can all test BEFORE someone uses space from that
> block.

Hmmm.. or, if the RIRs are going to advertize the block anyway between IANA
issue and space assignment (which would appear to be a necessary
precondition for what you suggest to work), why not ping "a large
collection of targets" using the new block, and various other IP addresses
as source addresses, and see which addresses responded from the old
block(s), but not from the new block. Sort by AS, and that would give you a
list (correct to heuristic level) of AS's that need to update their filters.
Then stick it on a web page.

RIPE could (for instance) generate it's "large collection of targets" using
a tiny sample of host-count data. (clearly RIPE needs to ping addresses
from all RIRs, ditto ARIN, APNIC etc.)

Alex

home help back first fref pref prev next nref lref last post