Re: [dhcwg] Incorporation of WG last call comments in draft-aboba-dhc-domsearch-06.txt

Bernard Aboba <aboba@internaut.com> Wed, 26 September 2001 14:14 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 KAA19759; Wed, 26 Sep 2001 10:14:17 -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 KAA00443; Wed, 26 Sep 2001 10:13:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00418 for <dhcwg@optimus.ietf.org>; Wed, 26 Sep 2001 10:13:19 -0400 (EDT)
Received: from internaut.com ([64.38.134.99]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19715 for <dhcwg@ietf.org>; Wed, 26 Sep 2001 10:13:15 -0400 (EDT)
Received: from localhost (aboba@localhost) by internaut.com (8.9.3/8.9.3) with ESMTP id HAA25805; Wed, 26 Sep 2001 07:00:14 -0700 (PDT) (envelope-from aboba@internaut.com)
Date: Wed, 26 Sep 2001 07:00:14 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: Thomas Narten <narten@raleigh.ibm.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Incorporation of WG last call comments in draft-aboba-dhc-domsearch-06.txt
In-Reply-To: <200109261102.f8QB27P04976@hygro.adsl.duke.edu>
Message-ID: <Pine.BSF.4.21.0109260657550.25790-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

> Main item is that it has a normative reference to
> 
> > [7]  Lemon, T., "Encoding Long DHCP Options", Internet draft (work in
> >      progress), draft-ietf-dhc-concat-01.txt, July 2001.
> 
> so these two document should go together.

Not sure the reference is normative. This option can use the long option
encoding if available, but doesn't require it. 

> 
> Some minor wording nits (these can be dealt with later):
> 
> > the domain search list.  This document defines a new DHCP option which
> > is passed from the DHCP Server to the DHCP Client to specify the domain
> > search list when resolving hostnames.
> 
> Is the option allowed to be included in client messages? I would
> assume so. Indeed, isn't it the case that clients can include any
> option if to signal a desire to the server to get such an option
> returned? If so, I guess this isn't really an issue.

Yes, that's my understanding.

> 
> > In this scheme, an entire domain name or a  list of labels at the end of
> > a domain name is replaced with a pointer to a prior occurrence of the
> 
> s/is replaced/can be replaced/
> 
> > same name.  Despite its complexity, this technique is valuable since the
> 
> Thomas
> 


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