Re: eating our own dogfood...Re: IPv4 Outage

Theodore Tso <tytso@mit.edu> Wed, 19 December 2007 05:05 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4r7s-0005DJ-Jb; Wed, 19 Dec 2007 00:05:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4r7q-00056L-Nr for ietf@ietf.org; Wed, 19 Dec 2007 00:05:46 -0500
Received: from [2002:4519:c427:1:220:edff:fe18:5794] (helo=thunker.thunk.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4r7o-0001ZM-Cl for ietf@ietf.org; Wed, 19 Dec 2007 00:05:46 -0500
Received: from root (helo=closure.thunk.org) by thunker.thunk.org with local-esmtps (tls_cipher TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50 #1 (Debian)) id 1J4rIl-00050S-Be; Wed, 19 Dec 2007 00:17:03 -0500
Received: from tytso by closure.thunk.org with local (Exim 4.67) (envelope-from <tytso@thunk.org>) id 1J4r7g-0003Cn-HG; Wed, 19 Dec 2007 00:05:36 -0500
Date: Wed, 19 Dec 2007 00:05:36 -0500
From: Theodore Tso <tytso@mit.edu>
To: Mark Andrews <Mark_Andrews@isc.org>
Bcc: tytso@mit.edu
Message-ID: <20071219050536.GH7070@thunk.org>
References: <20071219020600.GF7070@thunk.org> <200712190320.lBJ3KWT4099846@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200712190320.lBJ3KWT4099846@drugs.dv.isc.org>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false
X-Spam-Score: -0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>, ietf@ietf.org, Bill Manning <bmanning@ISI.EDU>
Subject: Re: eating our own dogfood...Re: IPv4 Outage
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

On Wed, Dec 19, 2007 at 02:20:32PM +1100, Mark Andrews wrote:
> 
> > On Wed, Dec 19, 2007 at 11:36:34AM +1100, Mark Andrews wrote:
> > > 	The problem is getting the AAAA records for them published.
> > > 	A local copy of "root-servers.net" with the AAAA records
> > > 	added will suffice.  "www.root-servers.org" will supply
> > > 	you with the necessary information to construct such a
> > > 	zone.
> > 
> > Ok, so I'm sure this is a REALLY dumb question, but what has prevented
> > anyone from taking the informatoin from www.root-servers.org and
> > creating a named.boot file with both the A and AAAA records for the
> > root nameservers, and started telling people to install it?
> 
> 	named.boot is not used after the priming succeeds.

Ah, right.  So that's why we would need to hijack the root zone
information --- so we can add the AAAA records to the root zones.

OK, next stupid question?  Why aren't the AAAA records being published
in the official root zone today?  Is there some good reason, like say
the size of the records returned for the root zone being too big?  And
is something being done to address whatever reasons might exist,
whether they are at the technical or political layer?

						- Ted

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf