Biggest mistake for IPv6: It's not backwards compatible, developers admit

[Martin List-Petersen]

Brandon Butterworth wrote:
>> you can always reject de-aggregated prefixes based on LIR
>> allocations with filters. That's entirely up to yourself.
> 
> I've seen this done with v4, it doesn't work. The deaggregators
> often won't advertise an aggregate. Customers complain and you
> end up making exceptions or the customers go away. Loads of hassle
> either way


It's simple. We're very much straight up with our customers and engage
people doing things like that. If they don't fix it, we'll advise our
customers not to deal with'em :)


>> Any sane
>> network person will send both the allocated full prefix on top of the
>> de-aggregated prefixes.
> 
> The ones that cause the problem aren't sane, they make it your problem


They just can't get to us then. Their choice. We'll approach them on it
though.


>> The choice of table-size is yours. Don't prohibit others from diversity
>> and redundancy.
> 
> That is the problem, while most accept the insane routes you have to
> accept them too. The only way to have sanity is for there either to be
> no way for it to happen or everyone agrees to not let it happen. With
> the latter there's always someone willing to accept insanity to make more
> money at everyone elses expense.
> 
> I think, more so with v6 PI now possible, the loss of deagg TE may
> be a price we have to pay.


The more networks, that start doing IRR based filtering, the more we'll
be getting rid of insanity like that. It's because autonomous networks
don't challenge it often enough, that we've got to live with the insanity.

Hey, I know of a tier1 carrier that doesn't route anything smaller than
a v6 /32, be it allocated by a RIR or not. Their table definatly won't
see too much of a growth due to de-aggregation.

Kind regards,
Martin List-Petersen
-- 
Airwire - Ag Nascadh Pobail an Iarthair
http://www.airwire.ie
Phone: 091-865 968