[lir-wg] AS Number Policy

> -----Original Message-----
> From: Christopher Sharp [mailto:ripe-lir-wg at chriss.net]
> Sent: Wednesday, July 10, 2002 11:32 AM
> To: lir-wg at ripe.net
> Cc: Lu, Ping
> Subject: Re: [lir-wg] AS Number Policy
> 
> 
> On Wed, 10 Jul 2002 11:22:29 -0400, "Lu, Ping" <PLu at 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 at cw.net