[86470] in North American Network Operators' Group
Re: oh k can you see
daemon@ATHENA.MIT.EDU (Daniel Karrenberg)
Mon Nov 7 07:01:16 2005
Date: Mon, 7 Nov 2005 13:00:39 +0100
From: Daniel Karrenberg <daniel.karrenberg@ripe.net>
To: nanog@nanog.org
Cc: Randy Bush <randy@psg.com>
Mail-Followup-To: nanog@nanog.org, Randy Bush <randy@psg.com>
In-Reply-To: <17255.36005.689061.450930@roam.psg.com>
Errors-To: owner-nanog@merit.edu
--cvVnyQ+4j833TQvp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
We have considered the options carefully and decided to announce a
covering /23 to get around the problem spotted by Randy and the folks in
Oregon. We considered the /24+/25 soloution but decided against that
because it makes little sense when we are considering to eventually
remove as much of the BG cleverness as possible.
See the attached announcement for details.
Thanks to all people who took the time to make suggestions either
privately or on list(s).
This was both operational and useful. ;-)
Daniel
--cvVnyQ+4j833TQvp
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <dns-wg-admin@ripe.net>
Delivered-To: dfk@localhost.karrenberg.net
Received: from localhost (localhost [127.0.0.1])
by reifa.karrenberg.net (Postfix) with ESMTP id F325831ED31
for <dfk@localhost>; Mon, 7 Nov 2005 07:08:14 +0100 (CET)
X-Original-To: Daniel.Karrenberg@ripe.net
Delivered-To: Daniel.Karrenberg@ripe.net
Received: from 127.0.0.1 [127.0.0.1]
by localhost with POP3 (fetchmail-6.2.5)
for dfk@localhost (single-drop); Mon, 07 Nov 2005 07:08:15 +0100 (CET)
Received: from postboy.ripe.net (postboy.ripe.net [193.0.0.201])
by cod.ripe.net (Postfix) with ESMTP id 6C47D726B3;
Mon, 7 Nov 2005 07:08:06 +0100 (CET)
Received: from postboy.ripe.net (localhost [127.0.0.1])
by postboy.ripe.net (Postfix) with ESMTP id 5F48F6A10B;
Mon, 7 Nov 2005 07:08:03 +0100 (CET)
X-Original-To: dns-wg@lists.ripe.net
Delivered-To: dns-wg@lists.ripe.net
Received: by postboy.ripe.net (Postfix, from userid 4008)
id AF8166A10B; Mon, 7 Nov 2005 07:07:23 +0100 (CET)
Received: from cod.ripe.net (cod.ripe.net [193.0.1.202])
by postboy.ripe.net (Postfix) with ESMTP id 6E2DC6A107
for <dns-wg@lists.ripe.net>; Mon, 7 Nov 2005 07:07:05 +0100 (CET)
Received: from [127.0.0.1] (cow.ripe.net [193.0.1.239])
by cod.ripe.net (Postfix) with ESMTP id DB9FD726B3;
Mon, 7 Nov 2005 07:07:04 +0100 (CET)
Message-ID: <436EEEE6.7000809@ripe.net>
From: Andrei Robachevsky <andrei@ripe.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, ru
MIME-Version: 1.0
To: dns-wg@ripe.net
X-Enigmail-Version: 0.90.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level:
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000000 / -5.9
X-RIPE-Signature: 55d115ff0d35b52b77fbd98961b5ac14
Subject: [dns-wg] Announcing a covering prefix for the K-root server
Sender: dns-wg-admin@ripe.net
Errors-To: dns-wg-admin@ripe.net
X-BeenThere: dns-wg@ripe.net
X-Mailman-Version: 2.0.13
Precedence: bulk
List-Id: RIPE DNS Working Group <dns-wg.ripe.net>
List-Post: <mailto:dns-wg@ripe.net>
X-RIPE-Lists: RIPE DNS Working Group <dns-wg.ripe.net>
List-Subscribe: <http://www.ripe.net/mailman/listinfo/dns-wg>,
<mailto:dns-wg-request@ripe.net?subject=subscribe>
List-Unsubscribe: <http://www.ripe.net/mailman/listinfo/dns-wg>,
<mailto:dns-wg-request@ripe.net?subject=unsubscribe>
List-Help: <mailto:dns-wg-request@ripe.net?subject=help>
List-Archive: <http://www.ripe.net/mailman/private/dns-wg/>
Date: Mon, 07 Nov 2005 07:06:30 +0100
Dear Colleagues,
As you probably know, the RIPE NCC have been deploying two types of
anycast mirror instances of K-root server: global nodes and so-called
local nodes, intended to serve only a local ISP community. To limit
propagation of the K-root prefix for the local nodes we are using a
NO_EXPORT community.
Unfortunately this may lead to a situation when some of multihomed
networks don't see K-root prefix at all, even for a global node. For
more detailed description see
http://www.merit.edu/mail.archives/nanog/msg13358.html. Thank you,
Randy, for spotting this.
This is not specific to anycast and has never appeared to be
particularly widespread.
To remedy this problem we plan to start announcing a covering prefix
193.0.14.0/23 from AS25152 from our global node to our peers at AMS-IX
without the NO_EXPORT community.
We will announce the covering prefix at 10:00 UTC on Thursday, 10th
November 2005. In parallel we will be monitoring and measuring changes
in traffic distribution for further analysis. We will then proceed with
other global nodes.
Regards,
Andrei Robachevsky
RIPE NCC
--cvVnyQ+4j833TQvp--
