Re: [dnsext] Question on characters in DNS lookups?
Edward Lewis <Ed.Lewis@neustar.biz> Sat, 05 March 2011 15:46 UTC
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 645153A6A8A for <dnsext@core3.amsl.com>; Sat, 5 Mar 2011 07:46:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level:
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 AuPum0fQziGB for <dnsext@core3.amsl.com>; Sat, 5 Mar 2011 07:46:02 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 28B8F3A6A78 for <dnsext@ietf.org>; Sat, 5 Mar 2011 07:46:02 -0800 (PST)
Received: from Work-Laptop-2.local (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p25Fl4Yt004457; Sat, 5 Mar 2011 10:47:04 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [192.168.1.103] by Work-Laptop-2.local (PGP Universal service); Sat, 05 Mar 2011 10:47:11 -0500
X-PGP-Universal: processed; by Work-Laptop-2.local on Sat, 05 Mar 2011 10:47:11 -0500
Mime-Version: 1.0
Message-Id: <a06240800c9980906d20e@[10.31.200.123]>
In-Reply-To: <20110304220531.4F9BBBAA5ED@drugs.dv.isc.org>
References: <ACD95DD2-6FBA-42F1-84E6-7C8D798FF1C1@icsi.berkeley.edu><20110304154257.GA 27387@nic.fr> <20110304220531.4F9BBBAA5ED@drugs.dv.isc.org>
Date: Sat, 05 Mar 2011 10:45:54 -0500
To: dnsext List <dnsext@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: multipart/alternative; boundary="============_-912782471==_ma============"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: ed.lewis@neustar.biz
Subject: Re: [dnsext] Question on characters in DNS lookups?
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Mar 2011 15:46:03 -0000
At 9:05 +1100 3/5/11, Mark Andrews wrote: >More correctly the DNS does not place restrictions. The DNS is >a storage device. The users of the DNS may place restrictions. > >Hostnames have restrictions RFC 952. >Mail domains have restrictions RFC 822 and its successors. Mark, What's your take on this: In some places an RR's RDATA needs a domain name and in some places it calls for a host name. The value of CNAME record is a domain name. The value of an NS record is a host name. The "target" of an MX record is a host name. The difference in these three cases is - in a CNAME the target is a location in the tree, not a host. For a NS, the target is a host but one that is being accessed by DNS implementations. For the latter, the MX, the target is a host to be contacted by a SMTP implementation - which seem to be quite finicky things when it comes to host syntax. In light of this, I choose to limit the RDATA of MX records to host name rules, and NS too for convenience but let the CNAME be any 8-bit value. The original question mentioned questions - the owner name in a question (and all sections) can have any 8-bit value. I'm asking if you think there should be restrictions on what's in RDATA. I checked STD 13 and found this, this is where I got my idea years ago: # CNAME a domain name. # # MX a 16 bit preference value (lower is # better) followed by a host name willing # to act as a mail exchange for the owner # domain. # # NS a host name. In this case, the NS is said to be a host, not domain, name. From that, I would say that the DNS does place restrictions - but only within some RDATA specifications. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis NeuStar You can leave a voice message at +1-571-434-5468 Me to infant son: "Waah! Waah! Is that all you can say? Waah?" Son: "Waah!"
- [dnsext] Question on characters in DNS lookups? Nicholas Weaver
- Re: [dnsext] Question on characters in DNS lookup… Stephane Bortzmeyer
- Re: [dnsext] Question on characters in DNS lookup… Mark Andrews
- Re: [dnsext] Question on characters in DNS lookup… Edward Lewis
- Re: [dnsext] Question on characters in DNS lookup… Masataka Ohta
- Re: [dnsext] Question on characters in DNS lookup… Edward Lewis
- Re: [dnsext] Question on characters in DNS lookup… Edward Lewis