Re: [dhcwg] How to encode DNS labels in DHCP options
Thomas Narten <narten@raleigh.ibm.com> Wed, 05 September 2001 17:52 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 NAA12481; Wed, 5 Sep 2001 13:52:23 -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 NAA18236; Wed, 5 Sep 2001 13:49:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18213 for <dhcwg@ns.ietf.org>; Wed, 5 Sep 2001 13:49:56 -0400 (EDT)
Received: from hygro.adsl.duke.edu (cichlid.adsl.duke.edu [152.16.64.203]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12279 for <dhcwg@ietf.org>; Wed, 5 Sep 2001 13:48:29 -0400 (EDT)
Received: from hygro.adsl.duke.edu (narten@localhost) by hygro.adsl.duke.edu (8.11.2/8.9.3) with ESMTP id f85HlTZ03658; Wed, 5 Sep 2001 13:47:29 -0400
Message-Id: <200109051747.f85HlTZ03658@hygro.adsl.duke.edu>
To: Mark Stapp <mjs@cisco.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] How to encode DNS labels in DHCP options
In-Reply-To: Message from "Tue, 04 Sep 2001 17:27:19 EDT." <4.3.2.7.2.20010904170432.02ac0330@funnel.cisco.com>
Date: Wed, 05 Sep 2001 13:47:28 -0400
From: Thomas Narten <narten@raleigh.ibm.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
Hi Mark. > As Bernie noted, there's a historical problem in this case that makes it > unusually painful to remove text about the ASCII behavior entirely. We > don't want new clients to implement the deprecated behavior, but we need to > describe it for the benefit of new server implementations which will > encounter old clients for a long time to come. Makes sense to me. > This is the revised text from section 4.1, describing the use of the "E" flag: > The data in the Domain Name field SHOULD appear in DNS-style binary > encoding (without compression, of course), as described in > RFC1035[3]. A client which sends the FQDN option SHOULD use this > encoding. The client MUST set the "E" bit when the data in the > Domain Name field is in DNS binary encoding. If a server receives an > FQDN option from a client, and intends to include an FQDN option in > its reply, it MUST use the same encoding that the client used, and > MUST set the "E" bit accordingly. My only quibble with the above is the SHOULD. Why not a MUST? If you want clients that implement *this* spec to implement the binary encoding, seems like it should be a MUST (i.e., no wiggle room). Saying SHOULD allows them to implement the ascii flavor and be compliant. That wouldn't seem to be the goal here. > 4.3 The Domain Name Field > The Domain Name part of the option carries all or part of the FQDN > of a DHCP client. The data in the Domain Name field SHOULD appear in > uncompressed DNS encoding as specified in RFC1035[3]. If the DHCP > client uses DNS encoding, it MUST set the third bit in the Flags > field (the "E" bit). A client may be configured with a > fully-qualified domain name, or with a partial name that is not > fully-qualified. If a client knows only part of its name, it MAY > send a name that is not fully-qualified, indicating that it knows > part of the name but does not necessarily know the zone in which the > name is to be embedded. Might be good to say that "not fully-qualified" really means a single label. > Does this help? Is this too much change, or the right amount? Is there > anything that's still unclear after these changes? Overall, this seems much better to me. Thanks, Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org http://www1.ietf.org/mailman/listinfo/dhcwg
- RE: [dhcwg] How to encode DNS labels in DHCP opti… Bernie Volz (EUD)
- Re: [dhcwg] How to encode DNS labels in DHCP opti… Mark Stapp
- Re: [dhcwg] How to encode DNS labels in DHCP opti… Ted Lemon
- Re: [dhcwg] How to encode DNS labels in DHCP opti… Thomas Narten
- RE: [dhcwg] How to encode DNS labels in DHCP opti… Bernie Volz (EUD)
- Re: [dhcwg] How to encode DNS labels in DHCP opti… Thomas Narten
- Re: [dhcwg] How to encode DNS labels in DHCP opti… Bud Millwood
- Re: [dhcwg] How to encode DNS labels in DHCP opti… Josh Littlefield
- Re: [dhcwg] How to encode DNS labels in DHCP opti… Ted Lemon
- Re: [dhcwg] How to encode DNS labels in DHCP opti… unixos
- Re: [dhcwg] How to encode DNS labels in DHCP opti… Henning G. Schulzrinne
- Re: [dhcwg] How to encode DNS labels in DHCP opti… Ted Lemon
- Re: [dhcwg] Incorporation of WG last call comment… Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-csr-05.txt Ted Lemon
- Re: [dhcwg] IPR disclosure and <draft-ietf-dhc-su… Naiming Shen
- Re: [dhcwg] IPR disclosure and <draft-ietf-dhc-su… Ted Lemon
- Re: [dhcwg] IPR disclosure and <draft-ietf-dhc-su… Bud Millwood