[arin-ppml] IPv6 Non-connected networks

[Owen DeLong]

Well, if you look in Verizon's routing table, you'll find that the following
route is missing from their perspective on the DFZ:


	2620:0:930::/48

There are many others, as well... Roughly 20% of the IPv6 routing table
seen by other providers and their customers.

The point is that ARIN does not dictate routing policy.  Yes, so far, most
ISPs choose to route most or all of what ARIN registers, but, there is nothing
in ARIN policy compelling them to do so and they are free to change that
decision at any time.

Owen

On Feb 4, 2010, at 9:23 AM, Michael Richardson wrote:

> 
> Can you give me an example of a piece of address space (IPv4 or IPv6)
> that ARIN has issued that turned out to not be routable on the DFZ?
> 
> The only example I can see are some of the 69/8 and 70/8 (if I got those
> prefixes right), which many people had bogon filters for, and it took a
> few months for those filters to get completely removed.
> 
> (Please ignore micro-allocations for IXs, which are often intended not
> to be routable, but often turn out to be easily routed)
> 
> I understand covering-your-ass legalize in the document, but really,
> let's be pragmatic here.
> 
> -- 
> ]       He who is tired of Weird Al is tired of life!           |  firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
> ] mcr at sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
>   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
> 	               then sign the petition. 
> 
> 
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.