Pinging RIPE

[James Aldridge]

--On 25 November 2009 10:27:04 +0100 Emanuele Balla <balla at staff.spin.it> 
wrote:

> I'm having problem reaching www.ipv6.ripe.net from my network
> (2a02:9a8::/32).
>
> Can someone from RIPE contact me offlist to analyze the problem?

The RIPE NCC currently has a /42 IPv6 assignment from Surfnet's /32 
allocation.
One peer was leaking the RIPE NCC's prefix to the world despite having it 
clearly
tagged "no-export" in the announcement.  The BGP sessions with this peer 
have
been disabled for the time being so IPv6 traffic from those networks not 
directly
peering with the RIPE NCC at the AMS-IX should now flow via Surfnet as 
intended.

With the implementation of policies which permit the RIPE NCC to assign 
resources
to itself, there are plans to renumber the RIPE NCC into its own IPv6 PI
assignment in the coming months.

Regards,
James

-- 
James Aldridge, Senior Systems & Network Engineer, RIPE NCC