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/address-policy-wg@ripe.net/
[address-policy-wg] "Dirty" recycled network assigned
- Previous message (by thread): [address-policy-wg] "Dirty" recycled network assigned
- Next message (by thread): [address-policy-wg] "Dirty" recycled network assigned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Conrad
david.conrad at icann.org
Wed Jan 16 22:07:26 CET 2008
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
- Previous message (by thread): [address-policy-wg] "Dirty" recycled network assigned
- Next message (by thread): [address-policy-wg] "Dirty" recycled network assigned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]