Re: [address-policy-wg] 2008-01 New Policy Proposal (Assigning IPv6 PI to Every Inetnum Holder)

[Marco Hogewoning marcoh@localhost]

On Jan 16, 2008, at 3:24 PM, <michael.dillon@localhost <michael.dillon@localhost 
> wrote:
> > And how many get cancelled each year because they are not
> > being paid for, and if they do it's much easier to remove a
> > domain name from the internet. Unless there would be an
> > active system with signatures it's very hard to make sure
> > cancelled PI/PA blocks will disappear from the DFZ.
> First of all, if a PI block is not paid for it will disappear
> from RIPE's DB. I would expect many ISPs to have an internal
> process for IPv6 Peering customers to regularly check the DB.
>
> Also, there are a number of groups which regularly analyze BGP
> announcements looking for things like bogons and ghost-routes.
> I would expect one or more of those groups to include unregistered
> PI blocks in their reporting. A greater number of ISPs will
> probably track these reports to make sure that they are
> following best practices.
Next to the fact there is a limit on how many routes a forwardingtable  
will hold, there is an equal set of limitations on how big a route-map  
can grow. There is a big contrast as most of the current IPv4 bogon  
filters simply filter /8's which are either flagged for special use or  
not allocated yet.
You are talking about a set of filters with a resolution of /48 and  
maybe even /56 in a large chunk of what in the end will become swamp6,  
the only way to maintain would be if you can trust everybody to check  
all annoucements from all networks who you are providing transit for.
In a perfect world this could happen, but being a bit pessimistic I  
expect somewhere somebody will bend over, accept the money and forget  
about standards,policies and the rest of the world. For a working real  
world example of this mechanism, please check your spamfilter  
statistics.
So, unless I can have my box auto check some signature on prefixes and  
act accoordingly, I don't see myself configuring a route-map with  
possibly over 65000 entries to check on a /48 boundry if that prefix  
is still being paid for.
Grt,

--
MarcoH