IETF Logo Mail Archive

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

Ted Lemon <mellon@nominum.com> Sat, 08 September 2001 20:47 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29481; Sat, 8 Sep 2001 16:47:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02522; Sat, 8 Sep 2001 16:47:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02497 for <dhcwg@optimus.ietf.org>; Sat, 8 Sep 2001 16:47:03 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29464 for <dhcwg@ietf.org>; Sat, 8 Sep 2001 16:45:35 -0400 (EDT)
Received: from grosse.bisbee.fugue.com (205-140-116-228.ip.theriver.com [205.140.116.228]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id f88Kkqf03863; Sat, 8 Sep 2001 13:46:53 -0700 (PDT)
Received: from grosse.bisbee.fugue.com (localhost [127.0.0.1]) by grosse.bisbee.fugue.com (8.11.3/8.6.11) with ESMTP id f88KiLA01840; Sat, 8 Sep 2001 13:44:21 -0700 (MST)
Message-Id: <200109082044.f88KiLA01840@grosse.bisbee.fugue.com>
To: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
cc: Thomas Narten <narten@raleigh.ibm.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] How to encode DNS labels in DHCP options
In-Reply-To: Message from "Henning G. Schulzrinne" <hgs@cs.columbia.edu> of "Sat, 08 Sep 2001 12:58:59 -0400." <3B9A4E53.710796E0@cs.columbia.edu>
Date: Sat, 08 Sep 2001 13:44:21 -0700
From: Ted Lemon <mellon@nominum.com>
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

> I think in practice, this only moves the problem around. It seems
> unlikely that configuration files for DHCP servers would force users to
> enter RFC 1035 notation. Among other things, it is rather likely to
> cause errors. (Forget to update the count byte when you change a label
> and you've introduced some rather strange results.) 

Of course the DHCP server doesn't have to force the user to enter
protocol level information directly.  And you are right that this
moves the problem around.   It moves it to where it can be
appropriately handled - the application's user interface.

The protocol has to be *able* to encode IDN when/if IDN materializes.
We do not need to say how an application presents this to the user.
We can safely leave that to the IDN people.

			       _MelloN_

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
http://www1.ietf.org/mailman/listinfo/dhcwg

v2.14.0 | Report a Bug | By Email