This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[dns-wg] Re: Change of K-Root Instance in Frankfurt to a Global Node

Previous message (by thread): [dns-wg] Change of K-Root Instance in Frankfurt to a Global Node
Next message (by thread): [dns-wg] RIPE NCC and ICANN Commit to Ongoing DNS Root Name Service Coordination

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Anand Buddhdev anandb at ripe.net
Fri Jun 19 21:54:40 CEST 2009

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

Previous message (by thread): [dns-wg] Change of K-Root Instance in Frankfurt to a Global Node
Next message (by thread): [dns-wg] RIPE NCC and ICANN Commit to Ongoing DNS Root Name Service Coordination

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]