IETF Logo Mail Archive

Re: [dhcwg] Review of Service-Discovery-Type options in DHCP

Ralph Droms <rdroms@cisco.com> Wed, 17 July 2002 00:34 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 UAA05080 for <dhcwg-archive@odin.ietf.org>; Tue, 16 Jul 2002 20:34:20 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id UAA02797 for dhcwg-archive@odin.ietf.org; Tue, 16 Jul 2002 20:35: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 UAA02723; Tue, 16 Jul 2002 20:34:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA02700 for <dhcwg@optimus.ietf.org>; Tue, 16 Jul 2002 20:33:58 -0400 (EDT)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04989 for <dhcwg@ietf.org>; Tue, 16 Jul 2002 20:33:00 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (rtp-vpn2-697.cisco.com [10.82.242.185]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id UAA24832; Tue, 16 Jul 2002 20:33:19 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020716202112.0396d470@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 16 Jul 2002 20:33:12 -0400
To: Stuart Cheshire <cheshire@apple.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Review of Service-Discovery-Type options in DHCP
Cc: DHCP discussion list <dhcwg@ietf.org>
In-Reply-To: <200207160954.g6G9soT18321@scv3.apple.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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'm going to pick a small item out of the middle of Stuart's message that 
caught my attention...

At 02:54 AM 7/16/2002 -0700, Stuart Cheshire wrote:
>The only missing piece of information that the client need to learn is
>the "company.com." component of the service names it should be looking up.
>
>Perhaps the existing DHCP "Domain Name" option (option code 15) meets
>this need.
>
>If you bring your laptop to Apple, and boot it using DHCP, then the DHCP
>"Domain Name" option will say, "apple.com.", and you can find:

I have always thought of the "Domain Name" option as specifying the domain 
name that the client should attach to its hostname to form its 
FQDN.  Stuart suggests a somewhat different definition - the "Domain Name" 
option simply identifies the domain name for the network to which the 
client is attached.  The client can then use that information in any way it 
wants: to form an FQDN if it needs one, to form service names.

- Ralph



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

v2.23.0 | Report a Bug | By Email