Re: Transport requirements for DNS-like protocols

Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> Fri, 28 June 2002 14:27 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00D046U9CD@eListX.com> (original mail from brunner@nic-naa.net); Fri, 28 Jun 2002 10:27:46 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00D016U9CB@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 28 Jun 2002 10:27:45 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00D016U9CA@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 28 Jun 2002 10:27:45 -0400 (EDT)
Received: from nic-naa.net (216-220-241-233.midmaine.com [216.220.241.233]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GYF00ALG6U8L1@eListX.com> for ietf-irnss@lists.elistx.com; Fri, 28 Jun 2002 10:27:45 -0400 (EDT)
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.12.4/8.11.6) with ESMTP id g5SEPCBZ015708; Fri, 28 Jun 2002 10:25:12 -0400 (EDT envelope-from brunner@nic-naa.net)
Date: Fri, 28 Jun 2002 10:25:12 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Subject: Re: Transport requirements for DNS-like protocols
In-reply-to: "Your message of Thu, 27 Jun 2002 23:41:33 EDT." <20020628034133.D50C518AC@thrintun.hactrn.net>
To: Rob Austein <sra@hactrn.net>
Cc: ietf-irnss@lists.elistx.com, brunner@nic-naa.net
Message-id: <200206281425.g5SEPCBZ015708@nic-naa.net>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-irnss-help@lists.elistx.com>
List-Post: <mailto:ietf-irnss@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-irnss/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-irnss-request@lists.elistx.com?body=help>
List-Id: <ietf-irnss.lists.elistx.com>

> It could be construed as off-topic for ...

I wouldn't say its off topic. Then again, there may be several topics that
resemble "transport requirements".

An epp domain check (xml-over-tcp) runs to half-a-K-bytes before adding the
sld and tld strings and any transaction id strings.

The reply is close to 1K-bytes before getting cluttered up with data.

Since an existence check is a staggeringly large fraction of what passes for
"responsible use" of the dns provisioning infrastructure (see "cute names",
"flat namespaces"), putting it into udp-friendly-form is odd in its absence.

Eric