Change of K-Root Instance in Frankfurt to a Global Node
Dear Colleagues, The RIPE NCC (AS25152) upgraded the k.root-servers.net instance in Frankfurt, Germany to a global node on 18 June 2009. This means that we are now announcing the prefix without the BGP no- export attribute. If you have been operating a peering session with us at DE-CIX, you will now see the prefix 193.0.14.0/23 instead of 193.0.14.0/24. Please adjust your filters if necessary. Anybody interested in peering with us can either use the DE-CIX route servers or contact <k-peerings@ripe.net> to set up a separate peering session. We also invite anybody who is willing to provide us with transit for this instance to contact us at <k-peerings@ripe.net>. Regards, Wolfgang Nagele DNS System Engineer, RIPE NCC
* Wolfgang Nagele:
This means that we are now announcing the prefix without the BGP no- export attribute. If you have been operating a peering session with us at DE-CIX, you will now see the prefix 193.0.14.0/23 instead of 193.0.14.0/24. Please adjust your filters if necessary.
Doesn't mean that the traffic flows to some local node which leaks globally? Or is this the intent?
On 19/6/09 20:12, Florian Weimer wrote: Hi Florian,
This means that we are now announcing the prefix without the BGP no- export attribute. If you have been operating a peering session with us at DE-CIX, you will now see the prefix 193.0.14.0/23 instead of 193.0.14.0/24. Please adjust your filters if necessary.
Doesn't mean that the traffic flows to some local node which leaks globally? Or is this the intent?
That's correct, and it is intentional. If a local node leaks the /24 prefix, the sudden surge in traffic should encourage them to quickly stop the leakage. -- Anand Buddhdev DNS Services Manager, RIPE NCC
participants (3)
-
Anand Buddhdev -
Florian Weimer -
Wolfgang Nagele