Re: Transport requirements for DNS-like protocols

Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> Sat, 29 June 2002 22:53 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYH00104OWRIN@eListX.com> (original mail from brunner@nic-naa.net); Sat, 29 Jun 2002 18:53:15 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYH00101OWRIL@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Sat, 29 Jun 2002 18:53:15 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYH00101OWRIK@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Sat, 29 Jun 2002 18:53:15 -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 <0GYH00JINOWPCZ@eListX.com> for ietf-irnss@lists.elistx.com; Sat, 29 Jun 2002 18:53:15 -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 g5TETwBZ021792; Sat, 29 Jun 2002 10:29:58 -0400 (EDT envelope-from brunner@nic-naa.net)
Date: Sat, 29 Jun 2002 10:29:58 -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 Sat, 29 Jun 2002 10:11:15 +0200." <17823168.1025345475@localhost>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
Cc: Nicolas Popp <nico@realnames.com>, 'Michael Mealling' <michael@neonym.net>, John C Klensin <klensin@jck.com>, Rob Austein <sra@hactrn.net>, ietf-irnss@lists.elistx.com, brunner@nic-naa.net
Message-id: <200206291429.g5TETwBZ021792@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>

Granted, this mess began with shady characters, but that isn't the exclusive
scope of a blob-o-gop-in-dns-record-out thing-above-transport. Besides, I've
been warned off of attempting to improve characters as that is a well-solved
problem.

Here is one representation of spatial data. It contains in-fix dots, and
three characters not in the LDH set, and there are applications that can
benefit from inexact match. Here "o" serves for U+00B0, "degree", UTC3.0,
and the leading tab is for clarity.

	29o46'59.63940"N
	95o34'46.23606"W
	-11.380m

Here is another representation of spatial data, this time from iso6709,
again with a leading tab for clairity. Altitude is the (optional) 3rd datum.

	+40-075/
	+401213.1-0750015.1+2.79/
	+40.20361-075.00417/

Again, in-fix dots, and two characters not in the LDH repitoire.

So, blob-o-glop is a coordinate system reference, e.g., the weather
sensor complex at 44o16'N, 71o18'W, 2,000m, (Mt. Washington, NH, US),
and "fuzzy" has some algorithmic expression e.g., 1'/1'/Km.




What I'd like, is for a something-above-dns not to be over-constrained
to be "language", nor harmed by non-generic problem domain issues.

The LDH limit exists, extensions to it can be mapped to it, and lookups,
as well as searches, may be attempted using the LDH-mapped thingee that
isn't LDH-constrained.

Personally, I'd go for adding "+" to LDH, but I lost my sense of humor
some time earlier.

Cheers,
Eric