[nsp] 82/8 allocated to RIPE

[Stephen J. Wilcox]

I personally dont think its a good idea to filter a block because its
unallocated for this reason. With changing NOC staff, bankruptcies etc its too
easy to miss an important update like this and its the ISPs allocated from the
new blocks who suffer.

Is anything achieved by filtering unallocated? (Note I do not include
permanently reserved blocks in this comment eg rfc1918, 127/8 etc)

Steve

On Sat, 23 Nov 2002, Scott Granados wrote:

> 
> Of course on the - side people don't keep them current.  So although some
> filtering is good its quite costly and difficult when your holding on to a
> /20 or mores worth of ips which don't work.
> 
> Although complaints on the 69 block seem fewer and fewer now.  I also can
> say for the most part when the right people at carriers were notified they
> cleared up the issue very very quickly.  Its just the trick of finding the
> right person.  Thankfully Nanog exists.
> 
> ----- Original Message -----
> From: "Rob Thomas" <robt@cymru.com>
> To: "Cisco List" <cisco-nsp@puck.nether.net>
> Sent: Saturday, November 23, 2002 12:48 PM
> Subject: Re: [nsp] 82/8 allocated to RIPE
> 
> 
> > ] God help anyone who gets assigned from that block.  The 69 block was
> > ] allocated by arin what 4 5 months ago and it still doesn't work every:).
> >
> > Hehe!  Hopefully my copious spam will help avoid a repeat of that problem.
> > On the plus side, it was great to know that more and more folks are
> > filtering out bogons.
> >
> > --
> > Rob Thomas
> > http://www.cymru.com
> > ASSERT(coffee != empty);
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list  real_name)s@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> 
> _______________________________________________
> cisco-nsp mailing list  real_name)s@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>