[address-policy-wg] "Dirty" recycled network assigned

Dave and all,

  If customers of ISP's don't whine, as you put it to them, how
do they have an expectation of getting these situations addressed?
As you rightly say, the IANA doesn't want to address it, the RIR's
really don't either.  So whom?  Frankly again IMHO, either
ICANN/IANA has to address this directly, or the RIR's do.

Regards,

Spokesman for INEGroup LLA. - (Over 277k members/stakeholders strong!)
"Obedience of the law is the greatest freedom" -
   Abraham Lincoln

"Credit should go with the performance of duty and not with what is
very often the accident of glory" - Theodore Roosevelt

"If the probability be called P; the injury, L; and the burden, B;
liability depends upon whether B is less than L multiplied by
P: i.e., whether B is less than PL."
United States v. Carroll Towing  (159 F.2d 169 [2d Cir. 1947]
===============================================================
Updated 1/26/04
CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS.
div. of Information Network Eng.  INEG. INC.
ABA member in good standing member ID 01257402 E-Mail
jwkckid1 at ix.netcom.com
My Phone: 214-244-4827

David Conrad wrote:

> On 1/16/08 12:17 PM, "Randy Bush" <randy at psg.com> wrote:
> >> 2) Get all the folks who are running RBLs/DUNs to update their lists when
> >>    address status changes (slightly more realistic than (1)).
> > could arin help automate this?
>
> Personally, I would imagine a set of services could be offered:
>
> A) IANA announces unallocated blocks
> B) the RIRs announce the blocks they've been allocated by IANA but which are
> unassigned (either new or returned)
>
> RBL/DUN maintainers could then listen for those announcements (note I'm not
> specifying the form of announcement here, there are a lot of possible
> mechanisms and some would argue it is already done via the registry
> databases, but that's pull versus push).  The RPKI effort could address part
> or all of this (maybe).
>
> (of course, the last time I suggested IANA could offer a service like this,
> some people in the ops community yelled at me, so I'm not actually
> suggesting this).
>
> Problem is, we run again into the decentralized nature of the Internet.  At
> least in the past, the folks who maintain RBL/DUN lists were an ornery,
> individualistic bunch and trying to get them to do something required
> one-on-one negotiations that sometimes failed for, shall we say,
> non-technical reasons.  I haven't really been following the RBL/DUN world
> for a while -- maybe things have gotten more professional so getting (at
> least) the major players to buy into this sort of thing could be possible.
>
> However, none of this addresses Max's immediate concerns. In the near term,
> I figure the choices here are:
>
> 1) the RIRs accept "the prefix is on black lists" as a justification to
> accept a prefix in exchange for another.  This will work for a little while
> longer yet.
>
> 2) the RIRs tell folks you get what you get and force the end users who
> ultimately get the addresses to deal with the situation.  I suspect this
> will tend to result in the ISPs having to deal since they'll probably get
> tired of their customers whining at them.
>
> An icky situation.
>
> Regards,
> -drc