Re: [dhcwg] Option 119 (Domain Search Option) and Option 15 (Domain Name Option)

Alfred Hönes <ah@TR-Sys.de> Wed, 01 December 2010 23:04 UTC

Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00E973A680B for <dhcwg@core3.amsl.com>; Wed, 1 Dec 2010 15:04:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.409
X-Spam-Level:
X-Spam-Status: No, score=-98.409 tagged_above=-999 required=5 tests=[AWL=0.340, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, 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 8Ks5I6hd6oPD for <dhcwg@core3.amsl.com>; Wed, 1 Dec 2010 15:04:26 -0800 (PST)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id BAA063A680A for <dhcwg@ietf.org>; Wed, 1 Dec 2010 15:04:24 -0800 (PST)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA025844717; Thu, 2 Dec 2010 00:05:17 +0100
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id AAA08195; Thu, 2 Dec 2010 00:05:16 +0100 (MEZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201012012305.AAA08195@TR-Sys.de>
To: dhankins@google.com
Date: Thu, 2 Dec 2010 00:05:15 +0100 (MEZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Option 119 (Domain Search Option) and Option 15 (Domain Name Option)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 23:04:27 -0000

David,
in response to my last message, you wrote:

>>  I guess everybody once saw RFC 3397 as a functional replacement
>>  for option 15, since the DSL (#119) allows a compact representation
>>  of multiple domain names by making use of domain name compression
>>  as in the DNS protocol.  (This pretty much matches your previous
>>  comment on space conservation.)
>
> Not precisely.  There is some value in informing some clients of
> their 'domain name', as being separate from their domain-search
> list.  ...

Yes, there's indeed value in that (iff it is clear that the DHCP
client is configured with a bare host name), and I initially also
believed to recall that #15 served this purpose.

But looking for #15 in RFC 2132, I found in Section 3.17:

|  This option specifies the domain name that client should use when
|  resolving hostnames via the Domain Name System.

It says "resolving hostnames", not "configuring the local domain name".

The domain search list is discussed in RFC 1034, which clearly
predates RFC 1533, the predecessor of RFC 2132.  Therefore, I assume
that the authors were aware of the function of the search list and
supplied a simple mechanism to fill in a single entry.

> Although at one time these two were one in the same (and in time,
> people began to identify with it only for domain search behavior),
> the domain name can actually feed other behaviors, and is useful
> to some clients separately from their domain-search configuration.

Indeed:

Digging deeper into history, I found that #15 initially was defined
in RFC 1395 with exactly the "configuring the local domain name"
semantics: "Specifies the domain name of the client ...".
This has been copied literally in the successor of RFC 1395, RFC 1497.

But clearly the description has changed in a significant way in the
next update step of the scpecification, from RFC 1497 to RFC 1395.

So the semantical shift you describe has been documented, and it looks
like we are now in a position where it is questionable to interpret
#15 as a method to set the local domain name for hosts only configured
with a relative domain name, as also described in RFC 1034.


Regarding the other points in my message: That was a strawman
collection of things that would need to be specified in the
update to RFC 3397 that Ted Lemon had suggested in his primary
response to the #15 vs. #119 question.

If requirements I had listed are seen as sufficiently specified
(otherwise/in general), a precise pointer to that specification
would serve the purpose, of course.

If, on the other hand, a requirement deemed useful cannot be
expected to be supported directly by DHCP server implementations,
but by proper configuration, it could easily be carried forward
in that manner, as a caveat to server admins, in a potential update
to RFC 3397.


Based on your words on #15, it now seems worth to _first_ clarify
its role unambiguously.  Without this clarification, an improved
specification for #119 cannot be conceived.
If #15 really is back to RFC 1395 semantics (local domain of DHCP
client, to be appended to his bare host name), no overlap with #119
exists, and RFC 3397 might be precise enough.

Kind regards,
  Alfred.