[158868] in North American Network Operators' Group
=?utf-8?Q?Re:_Advisory_=E2=80=94_D-root_is_changing_it?=
daemon@ATHENA.MIT.EDU (Walter Keen)
Fri Dec 14 12:17:50 2012
Date: Fri, 14 Dec 2012 09:12:00 -0800 (PST)
From: Walter Keen <walter.keen@rainierconnect.net>
To: Michael Thomas <mike@mtcc.com>
In-Reply-To: <50CB5AE7.8070709@mtcc.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
If I had to guess, I would guess that renumbering is likely required to get=
it into a more portable address assignment from a multi-homing perspective=
. Look at the whois information below
If I were hosting a root server or something similar, I would certainly wan=
t it segregated enough that I could manage multi-homing for that address pr=
efix outside of my other networks. =20
In this case, I'd assume UMDNET-1 may have monetary or administrative polic=
ies regarding the ability to be multi-homed and the degree to which it can =
be, however providing multiple links to UMD-ROOTD-NET is likely much easier=
because those decisions (or cost of connections) don't necessarily need to=
affect UMDNET-1
NetRange: 128.8.0.0 - 128.8.255.255
CIDR: 128.8.0.0/16
OriginAS: AS27
NetName: UMDNET-1
NetHandle: NET-128-8-0-0-1
Parent: NET-128-0-0-0-0
NetType: Direct Assignment
RegDate: 1984-08-01
Updated: 2011-05-03
Ref: http://whois.arin.net/rest/net/NET-128-8-0-0-1
NetRange: 199.7.91.0 - 199.7.91.255
CIDR: 199.7.91.0/24
OriginAS: AS6059, AS27, AS10886
NetName: UMD-ROOTD-NET
NetHandle: NET-199-7-91-0-1
Parent: NET-199-0-0-0-0
NetType: Direct Assignment
RegDate: 2007-12-07
Updated: 2012-03-20
Ref: http://whois.arin.net/rest/net/NET-199-7-91-0-1
----- Original Message -----=20
From: "Michael Thomas" <mike@mtcc.com>=20
To: "Matthew Newton" <mcn4@leicester.ac.uk>=20
Cc: nanog@nanog.org=20
Sent: Friday, December 14, 2012 8:59:19 AM=20
Subject: Re: Advisory =E2=80=94 D-root is changing its IPv4 address on the =
3rd of January.=20
Matthew Newton wrote:=20
> On Fri, Dec 14, 2012 at 04:42:46PM +0000, Nick Hilliard wrote:=20
>> On 13/12/2012 22:54, Jason Castonguay wrote:=20
>>> Advisory =E2=80=94 D-root is changing its IPv4 address on the 3rd of Ja=
nuary.=20
>> You've just given 3 weeks notice for a component change in one of the fe=
w=20
>> critical part of the Internet's infrastructure, at a time when most=20
>=20
> I think that /was/ the advance notification - you've got 6 months :)=20
>=20
> "The old address will continue to work for at least six months=20
> after the transition, but will ultimately be retired from=20
> service."=20
So really stupid question, and hopefully it's just me, do I need to do some=
thing=20
on my servers?=20
Second question: I know that renumbering is important in the abstract, but =
is there=20
really an overwhelming reason why renumbering the root servers is critical?=
Shouldn't=20
they all be in PI space for starters?=20
Mike