Akamai's 2a02:26f0::/32

Jeroen Massar jeroen at unfix.org
Tue Jul 17 10:48:10 CEST 2012

On 2012-07-17 07:18, Patrick W. Gilmore wrote:
> Everyone:
> First, thanx to Bernhard for bringing this to our attention.  The
> 2a02:26f0::/32 "anchor" (as we call it) is supposed to be announced.
> Let me be clear, and lay to rest any conspiracy theories: This was
> not intentional.  We have three /32s, it is trivial to verify the
> other two are being announced.  The fact this one is missing from the
> global table was simply an error - one that has already been
> corrected on our side.  Although we would like networks to not filter
> on PI boundaries, we also believe you should be allowed to run your
> network as you please.  As such, we announce the aggregate from an
> Akamai-owned location with paid full transit to attract any wayward
> packets and get them turned back onto the correct path.

Thank you for be open and accepting of other networks policies and
wishes! Rock on!


More information about the ipv6-ops mailing list