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

Theodore Tso <tytso@mit.edu> Tue, 18 December 2007 23:38 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 1J4m1V-0002gP-NE; Tue, 18 Dec 2007 18:38:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4m1T-0002gF-TO for ietf@ietf.org; Tue, 18 Dec 2007 18:38:51 -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 1J4m1T-0002vQ-Bw for ietf@ietf.org; Tue, 18 Dec 2007 18:38:51 -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 1J4mCT-0002Ei-Lb; Tue, 18 Dec 2007 18:50:13 -0500
Received: from tytso by closure.thunk.org with local (Exim 4.67) (envelope-from <tytso@thunk.org>) id 1J4m1P-0001RE-6U; Tue, 18 Dec 2007 18:38:47 -0500
Date: Tue, 18 Dec 2007 18:38:47 -0500
From: Theodore Tso <tytso@mit.edu>
To: Bill Manning <bmanning@ISI.EDU>
Bcc: tytso@mit.edu
Message-ID: <20071218233847.GB7070@thunk.org>
References: <20071218203617.GA2167@boreas.isi.edu> <fk9cus$bju$1@ger.gmane.org> <20071218220505.GA28386@boreas.isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20071218220505.GA28386@boreas.isi.edu>
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: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>, ietf@ietf.org
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 Tue, Dec 18, 2007 at 02:05:05PM -0800, Bill Manning wrote:
> 	my appologies to Ted, you happend to be the nearest 
> 	lighting rod.

Heh.  I hadn't realized how sensitive people are to the whole concept
of "hijacking the root".  To me, I was thinking merely of taking the
official root zone data and making it available on an IPv6 visible
host, on site at the IETF meeting if that's what's necessary to make
things work.  I don't think of that as being particularly
controversial, just an engineering expediency.  What I had in mind is
very different from taking the official root zone data and then adding
or subtracting root entries, quite a different idea of "hijacking the
root".  Perhaps that's what you had in mind?

In any case, I did some more looking into it, and it seems that 5 of
the 13 official root name servers have IPv6 addresses, and while that
doesn't necessarily mean global connectivity (some of them may only
have very limited service to a small IPv6 island), it shouldn't be
*that* hard for the IETF network ops to arrange a one or more
tunnel(s) to root servers with IPv6 addresses.  But in any case, the
point is let's come up with the appropriate engineering solutions so
that an IPv6-only network at an IETF meeting is in fact a viable and
productive resource to the attendees.  And if people continue to
insist that it's not possible, what does that say about IPv6?

As far as my having any authority as an official spokesmodel by virtue
of my Sargeant-at-Arms role, I just got a great big chuckle out of
that.  That title and two dollars will get me a small coffee at
Starbucks!

						- Ted

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