RE: [lir-wg] AS Number Policy
-----Original Message----- From: Christopher Sharp [mailto:ripe-lir-wg@chriss.net] Sent: Wednesday, July 10, 2002 11:32 AM To: lir-wg@ripe.net Cc: Lu, Ping Subject: Re: [lir-wg] AS Number Policy
On Wed, 10 Jul 2002 11:22:29 -0400, "Lu, Ping" <PLu@cw.net> wrote:
I don't think to blackholing traffic is a good idea, especially when bandwidth means money in today's internet.
I agree. Neither do I think the community should be paying to provide the bandwidth for such a service.
Encouraging people to filter out these netblocks/ASNs does make it very hard to re-allocate them in the short term. However, most people who maintain good bogon filters also update them frequently, so hopefully would remove any such filters in plenty of time for ASNs to be re-allocated after 12/24/36 months.
The major ISPs usually update these filters daily and if the tier-1 ISPs all have these filters then smaller ISPs don't have to filter them again.
RIRs should publish a list to include all the offending prefixes and the major ISPs will be more than happy to apply the prefix filter to block transit to those prefixes. There is already an IANA bogon filter floating around.
This was my suggestion in a nutshell. I believe the most commonly observed bogon list is maintained by Rob Thomas (http://www.cymru.com/Documents/bogon-list.html). draft-iana-special-ipv4-03 is IANA's most comprehensive list of special use netblocks (http://www.ietf.org/internet-drafts/draft-iana-special-ipv4-03.txt).
Maybe we can have an official filter-set object so people don't have to update these info manually.
RIPE NCC could add a filter-set object, let's say FLTR-RIPE-RESERVED-IPV4 and ARIN should have a FLTR-ARIN-RESERVED-IPV4 object, APNIC also should have a FLTR-APNIC-RESERVED-IPV4 object. Then all major ISPs could apply these filter to block transit traffic for these prefixes.
This sounds excellent but doesn't cover prefixes IANA have not yet allocated to an RIR. This is why I would encourage frequent sharing of this data with the networking community and especially the maintainers of public bogon lists on which many people filter.
In the IANA assigned RIR range, we still need RIRs to tell us what range under their authority are not allocated yet thus should be filtered.
Blocking is a better idea than blackholing....
C.
Ping Lu Cable & Wireless USA Network Tools and Analysis Group W: +1-703-292-2359 E: plu@cw.net
On Wed, 10 Jul 2002 11:57:29 -0400, "Lu, Ping" <PLu@cw.net> wrote:
-----Original Message----- From: Christopher Sharp [mailto:ripe-lir-wg@chriss.net] Sent: Wednesday, July 10, 2002 11:32 AM To: lir-wg@ripe.net Cc: Lu, Ping Subject: Re: [lir-wg] AS Number Policy
This was my suggestion in a nutshell. I believe the most commonly observed bogon list is maintained by Rob Thomas (http://www.cymru.com/Documents/bogon-list.html). [SNIP] Maybe we can have an official filter-set object so people don't have to update these info manually.
This sounds like an excellent idea.
In the IANA assigned RIR range, we still need RIRs to tell us what range under their authority are not allocated yet thus should be filtered.
Yes, this information should be well publicised though so that people can build bogon filters around it. RIPE (and sometimes ARIN) announce to NANOG when they start allocating from a new /8, I've yet to see APNIC do so. I've also yet to see any of the RIRs producing a definitive list of space assigned to them which is not yet allocated. Maybe I'm not looking in the right place? C.
On Wed, 10 Jul 2002, Christopher Sharp wrote:
On Wed, 10 Jul 2002 11:57:29 -0400, "Lu, Ping" <PLu@cw.net> wrote:
-----Original Message----- From: Christopher Sharp [mailto:ripe-lir-wg@chriss.net] Sent: Wednesday, July 10, 2002 11:32 AM To: lir-wg@ripe.net Cc: Lu, Ping Subject: Re: [lir-wg] AS Number Policy
This was my suggestion in a nutshell. I believe the most commonly observed bogon list is maintained by Rob Thomas (http://www.cymru.com/Documents/bogon-list.html). [SNIP] Maybe we can have an official filter-set object so people don't have to update these info manually.
This sounds like an excellent idea.
In the IANA assigned RIR range, we still need RIRs to tell us what range under their authority are not allocated yet thus should be filtered.
Yes, this information should be well publicised though so that people can build bogon filters around it. RIPE (and sometimes ARIN) announce to NANOG when they start allocating from a new /8, I've yet to see APNIC do so. I've also yet to see any of the RIRs producing a definitive list of space assigned to them which is not yet allocated. Maybe I'm not looking in the right place?
Thank you for pointing this out for us. We will certainly announce the new block in the future. For more information on the resources administered by APNIC, see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, see: http://www.apnic.net/db/min-alloc.html We don't have the information about unallocated address as it is hard to maintain upto date but we do provide statistic monthly on what we have allocated. Please see: http://ftp.apnic.net/stats/apnic/ Regards Son
participants (3)
-
Christopher Sharp
-
John Tran
-
Lu, Ping