Re: [dhcwg] How to encode DNS labels in DHCP options

Josh Littlefield <> Thu, 06 September 2001 14:01 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id KAA27682; Thu, 6 Sep 2001 10:01:14 -0400 (EDT)
Received: from (localhost []) by (8.9.1a/8.9.1) with ESMTP id JAA23145; Thu, 6 Sep 2001 09:58:28 -0400 (EDT)
Received: from (odin []) by (8.9.1a/8.9.1) with ESMTP id JAA23118 for <>; Thu, 6 Sep 2001 09:58:23 -0400 (EDT)
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id JAA27548 for <>; Thu, 6 Sep 2001 09:56:56 -0400 (EDT)
Received: from ( []) by (8.8.5-Cisco.1/8.6.5) with ESMTP id JAA17118; Thu, 6 Sep 2001 09:57:44 -0400 (EDT)
Message-ID: <>
Date: Thu, 06 Sep 2001 09:56:47 -0400
From: Josh Littlefield <>
Organization: Cisco Systems
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bud Millwood <>
Subject: Re: [dhcwg] How to encode DNS labels in DHCP options
References: <Message of "Mon, 27 Aug 2001 21:12:05 EDT." <> <> <> <>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <>
Content-Transfer-Encoding: 7bit

Bud Millwood wrote:
> I'll admit I don't know much about the DNS binary name format, but I'm going
> to ask: why is it better to encode DNS names in binary than ASCII?

There are no special characters (such as ".", or a null terminator) in DNS
native format, so it requires no quoting characters (which would themselves
require quoting).  It is not intended to be directly printable, so character
set issues are transparent, or will be when IDN resolves questions about
localized, non-7-bit ASCII names.  The form is simply a series of counted
label strings, so no real parsing is involved in handling the names.

Josh Littlefield                                  Cisco Systems, Inc.                                      250 Apollo Drive
tel: 978-244-8378  fax: same               Chelmsford, MA  01824-3627

dhcwg mailing list