Re: [tae] The internet architecture

Keith Moore <moore@network-heretics.com> Fri, 05 December 2008 16:16 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 DD7EF3A682D; Fri, 5 Dec 2008 08:16:30 -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 E6C473A68DE for <tae@core3.amsl.com>; Fri, 5 Dec 2008 08:16:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level:
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 1mhlIlE1-2J8 for <tae@core3.amsl.com>; Fri, 5 Dec 2008 08:16:28 -0800 (PST)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id 325533A63D3 for <tae@ietf.org>; Fri, 5 Dec 2008 08:16:28 -0800 (PST)
Received: from lust.indecency.org (adsl-242-100-137.tys.bellsouth.net [74.242.100.137]) by m1.imap-partners.net (MOS 3.10.3-GA) with ESMTP id BFC32658 (AUTH admin@network-heretics.com) for tae@ietf.org; Fri, 5 Dec 2008 08:16:22 -0800 (PST)
Message-ID: <493953D4.3020601@network-heretics.com>
Date: Fri, 05 Dec 2008 11:16:20 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.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> <200812051435.mB5EZFNp007644@cichlid.raleigh.ibm.com>
In-Reply-To: <200812051435.mB5EZFNp007644@cichlid.raleigh.ibm.com>
Cc: tae@ietf.org, "Hallam-Baker, Phillip" <pbaker@verisign.com>, 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

Thomas Narten wrote:
> Keith Moore <moore@network-heretics.com> writes:
> 
>> So it's not a question of whether DNS is less reliable than IP (it is),
>> or even whether the reliability of DNS + IP is less than that of IP
>> alone (it is).  It's a question of whether increasing reliance on DNS by
>> trying to get apps and other things to use DNS names exclusively, makes
>> those apps and other things less reliable.
> 
> No. Your argument seems to be "because relying even more on DNS than
> we do today makes things more brittle, BAD, BAD BAD, we cannot go
> there."

My argument is that if you really want that sort of approach to work you
need to concentrate on making DNS more reliable and better suited to
this kind of approach, and on getting people to think of DNS differently
than they do now - rather than just talking in terms of changing the
API, which is the easy part.

> The more relevant engineering question is whether the benefits of such
> an approach outweigh the downsides. Sure there are downsides. But
> there are also real potential benefits. 

Mumble.  Years ago, I worked out details of how to build a very scalable
distributed system (called SNIPE) using a DNS-like service (but a lot
more flexible in several ways) to name endpoints and associate the names
with metadata about those endpoints, including their locations.  So I
don't need to be convinced that there are potential benefits.  But that
exercise also gave me an appreciation for the difficulties involved.
And for that exercise I allowed myself the luxury of defining my own
naming service rather than constraining myself to use DNS.  It would
have been much more difficult, though perhaps not impossible, to make
that kind of system work with DNS.

> But the only way to answer such questions in a
> productive manner is to look pretty closely at a complete
> architecture/solution together with experience from real
> implementation/usage.

You certainly need a more complete architecture before you can evaluate
it at all.

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