[128619] in North American Network Operators' Group
Re: Lightly used IP addresses
daemon@ATHENA.MIT.EDU (John Curran)
Fri Aug 13 15:18:00 2010
From: John Curran <jcurran@arin.net>
To: Ken Chase <ken@sizone.org>
Date: Fri, 13 Aug 2010 15:17:50 -0400
In-Reply-To: <20100813183143.GV2582@sizone.org>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Aug 13, 2010, at 2:31 PM, Ken Chase wrote:
> ...
> Right, and Im answering my own question here, for (8) about the reclaimin=
g -=20
> what upstream is going to stop carrying prefixes from a downstream that's
> 'illegally' announcing them? Is this upstream going to cut that customer =
off and
> lose the revenue, just to satisfy ARIN's bleating? From what I gather, al=
l that
> ARIN can do is remove the NS records for the i-a.a reverse zone for the o=
ffending
> block, making SMTP a little trickier from the block, but not much else.
>=20
> Unless I didnt see the other large sticks ARIN's carrying? I've never see=
n them
> send hired goons to anyone's door... yet?
Ken -=20
=20
ARIN maintains the WHOIS based on what the community develops for=20
policies; what's happens in routing tables is entirely up to the=20
ISP community. No "bleating" or "large sticks" here, just turning
the policy crank and managing address space accordingly. =20
ARIN pulls the address space, and then (after holddown) reissues it
to another provider. WHOIS reflects this change, as does in-addr. =20
Whether an ISP respect the information in WHOIS is likely to always
be a "local decision"; ARIN's responsibility is to make sure that
the information contained therein matches the community's policy
not some hypothetical routing enforcement.
There will be an ISP attempting to make use of that reassigned=20
address space, and one could imagine that party being let down=20
if the community says one thing in policy but does another when
it comes to routing.
/John
John Curran
President and CEO
ARIN
