North American Network Operators Group
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Re: IPv6 internet broken, Verizon route prefix length policy
- From: Nathan Ward
- Date: Tue Oct 13 03:44:37 2009
On 13/10/2009, at 5:46 PM, Kevin Loch wrote:
I think he was pointing out that extra routes due to "slow start"
policies should not be a factor in v6. My guess is that is about
half of the "extra" routes announced today, the other half being
TE routes.
You can pretty easily figure out how many advertised prefixes are
intentional de-aggregates, and you can get a fairly good idea as to
how many of them are for TE as well I expect, by looking for different
AS paths.
Someone mentioned some slides earlier in this thread by Vince Fuller
at APRICOT early '07 that from memory have pretty good data on this.
--
Nathan Ward
- References:
- IPv6 internet broken, cogent/telia/hurricane not peering Igor Ybema
- Re: IPv6 internet broken, cogent/telia/hurricane not peering Seth Mattinen
- Re: IPv6 internet broken, Verizon route prefix length policy Jeff McAdams
- Re: IPv6 internet broken, Verizon route prefix length policy Mark Andrews
- Re: IPv6 internet broken, Verizon route prefix length policy David Conrad
- Re: IPv6 internet broken, Verizon route prefix length policy Owen DeLong
- Re: IPv6 internet broken, Verizon route prefix length policy David Conrad
- Re: IPv6 internet broken, Verizon route prefix length policy Valdis.Kletnieks
- Re: IPv6 internet broken, Verizon route prefix length policy Adrian Chadd
- Re: IPv6 internet broken, Verizon route prefix length policy Kevin Loch
|