[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: draft-iab-dns-choices-02.txt comments
- To: "IETF DNSEXT WG" <namedroppers@ops.ietf.org>
- Subject: Re: draft-iab-dns-choices-02.txt comments
- From: David MacQuigg <dmquigg-lists@yahoo.com>
- Date: Thu, 09 Jun 2005 09:03:24 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Message-Id:X-Sender:X-Mailer:Date:To:From:Subject:In-Reply-To:Mime-Version:Content-Type; b=lGrhe6G7alDRqz9JkQfjyDNnZH7/hIwlH4PrNXTDC+BAFP/nU5nmgFPAoRdESLN0X7SiNIdfKviQ8I4rb7+WsQUg1SwWWyckUFQtqac4eI6/7NlzaoGVpNNIbMtUrntup6MUCpPuGkLrg54vm44+2Z/G18hiKlRQDsOZaT9BN0s= ;
- In-reply-to: <x4u0k8e46z.fsf@footbone.schlitt.net>
At 07:58 PM 6/8/2005 -0500, wayne wrote:
<...>
I believe what needs to be done is to allocate say, 100 new DNS RRs as
clones of TXT records (say, TXT0-TXT99). There are tens of thousands
of RR numbers sitting totally unused.
This seems like a halfway step, like the old DOS database I used in the
late 80's to run my business. It had a scripting language, but no
variables!! After enough users screamed, they gave us a small number of
variables with fixed names, like the above. It seems very odd that the
design of DNS allowed records to have a "class" attribute, but not a much
more useful "name" attribute. I don't like forcing the "type" attribute to
serve as a "name".
My current plans are to prepend the necessary record names to the domain
name, like CSV is doing with _client._smtp.<domain>. TXT type is adequate
for anything I will need. As I understand it, the only problem is that I
can't use wildcards at the same time. So I can't have
_client._smtp.*.<domain>. That is a limitation I can live with, but
something that might be nice for a future extension of DNS.
<...>
The only
problem with TXT is that their space is limited, but that can be fixed
as easily as it would take to create one single other new RR type.
Sorry for a dumb question, but what will it take to raise the 512-byte
limit, without a fallback to TCP, which would negate the UDP speed
advantage, and make me want to use the more versatile HTTP for general
queries? Even if we had to wait 10 years for some old machines to die, it
would be a nice improvement in DNS. Meanwhile, we can continue to use
multiple queries to linked records for anything over 512 bytes, and when
the Internet is ready, make a smooth transition to a single, more
streamlined record.
--
Dave
************************************************************ *
* David MacQuigg, PhD email: david_macquigg at yahoo.com * *
* IC Design Engineer phone: USA 520-721-4583 * * *
* Analog Design Methodologies * * *
* 9320 East Mikelyn Lane * * *
* VRS Consulting, P.C. Tucson, Arizona 85710 *
************************************************************ *
--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>