Re: [tae] The internet architecture

Keith Moore <moore@network-heretics.com> Thu, 04 December 2008 22:11 UTC

Return-Path: <tae-bounces@ietf.org>
X-Original-To: tae-archive@ietf.org
Delivered-To: ietfarch-tae-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CE2828C15E; Thu, 4 Dec 2008 14:11:49 -0800 (PST)
X-Original-To: tae@core3.amsl.com
Delivered-To: tae@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 041B73A6B78 for <tae@core3.amsl.com>; Thu, 4 Dec 2008 13:51:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level:
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKUnhZvj6Yef for <tae@core3.amsl.com>; Thu, 4 Dec 2008 13:51:35 -0800 (PST)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id 4CED43A6B23 for <tae@ietf.org>; Thu, 4 Dec 2008 13:51:35 -0800 (PST)
Received: from lust.indecency.org ([72.242.14.237]) by m1.imap-partners.net (MOS 3.10.3-GA) with ESMTP id BFB42394 (AUTH admin@network-heretics.com) for tae@ietf.org; Thu, 4 Dec 2008 13:51:29 -0800 (PST)
Message-ID: <493850D8.7090908@network-heretics.com>
Date: Thu, 04 Dec 2008 16:51:20 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
References: <C15AE32B-E564-4C93-86FF-40EF203E673A@mpi-sws.org> <49382030.5020704@network-heretics.com> <2788466ED3E31C418E9ACC5C316615572FFBEF@mou1wnexmb09.vcorp.ad.vrsn.com> <49384BCF.2080600@network-heretics.com> <2788466ED3E31C418E9ACC5C316615572FFBF3@mou1wnexmb09.vcorp.ad.vrsn.com>
In-Reply-To: <2788466ED3E31C418E9ACC5C316615572FFBF3@mou1wnexmb09.vcorp.ad.vrsn.com>
X-Mailman-Approved-At: Thu, 04 Dec 2008 14:11:47 -0800
Cc: tae@ietf.org, ietf@ietf.org, Bryan Ford <brynosaurus@gmail.com>
Subject: Re: [tae] The internet architecture
X-BeenThere: tae@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Architecture Evolution <tae.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tae>, <mailto:tae-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tae>
List-Post: <mailto:tae@ietf.org>
List-Help: <mailto:tae-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tae>, <mailto:tae-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tae-bounces@ietf.org
Errors-To: tae-bounces@ietf.org

Hallam-Baker, Phillip wrote:
> You are wrong.

I often get the impression that the laws of physics do not apply on the
planet where you live...

> Take SMTP email. Imagine that a company has three mail servers at
> geographically dispersed locations with independent network connections.
> With MX records a local failure of IP connectivity does not need to mean
> total failure of IP connectivity.

You want to extrapolate to the whole Internet and all of its
applications from a single, somewhat hypothetical, data point - one that
you haven't even completely analyzed?

> In fact provided that core DNS is there, and BGP is not borked it is
> possible to contingency plan for pretty much any outage that does not
> result in a virtually complete loss of connectivity at the client end.

There's a big difference between what is possible and what is usually
true in practice.

There's also a big difference between the perspective of someone who
operates networks (and who can presumably fix the network if it's
broken), and application writers and users (who are forced to deal with
whatever brain-damage the network - including DNS in their view -
presents to them).

Not a week goes by when I'm not asked to figure out "why people can't
get to a web server" or "why email isn't working".  In about 70% of the
web server cases and 30% of the email cases, the answer turns out to be
DNS related.  IP failures, by contrast, are quite rare.  And the ones
that I see mostly consist of failures of the user's local wireless
access point.

Keith
_______________________________________________
tae mailing list
tae@ietf.org
https://www.ietf.org/mailman/listinfo/tae