Re: Comments surrounding draft-iab-dns-applications-01

"John Levine" <johnl@iecc.com> Fri, 29 April 2011 02:36 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16434E0713 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 19:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.12
X-Spam-Level:
X-Spam-Status: No, score=-109.12 tagged_above=-999 required=5 tests=[AWL=2.079, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7SC0VBQNOflk for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 19:36:54 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id B9378E0684 for <ietf@ietf.org>; Thu, 28 Apr 2011 19:36:53 -0700 (PDT)
Received: (qmail 61464 invoked from network); 29 Apr 2011 02:36:52 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 29 Apr 2011 02:36:52 -0000
Date: Fri, 29 Apr 2011 02:36:30 -0000
Message-ID: <20110429023630.46187.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <a06240800c9df29c0bf75@[10.31.203.186]>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Cc: Ed.Lewis@neustar.biz
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2011 02:36:55 -0000

>It's hard to make comments on a document whose mission is not at all 
>clear.  The problem I have is that the document has a faulty baseline 
>and incorrectly assesses extensions and variations. ...

My experience with the DNS is nowhere near as deep as Ed's but having
done my share of DNS hackery (production special purpose DNS servers
written in perl), I have to agree with him.  This document starts by
conflating the DNS and applications built on top of the DNS, and goes
downhill from there.  I agree that there have been some pretty crufty
applications built on top of the DNS, but that cruftitude doesn't
affect the simple query and answer that the DNS does underneath.

The two points that do seem to apply to the DNS are, as Ed said,
larger responses and split horizon DNS.  Both of those have been
around for at least a decade without causing the world to collapse,
and neither is going away, particularly as DNSSEC becomes real, so
I don't understand what problem is to be solved.

So my advice would be to back up and write down in one or two
sentences what problem this document is supposed to fix or at least
describe, and then see how much of the rest of it might be salvaged.

This might be also a good time to write a DNS architecture document
analogous to Dave Crocker's mail architecture, that shows the layering
of the queries to authoritative servers, queries to caches, and the
applications built on top of them such as locating mail servers and
doing whatever NAPTR and DDNS do.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly