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

Stuart Cheshire <cheshire@apple.com> Tue, 16 July 2002 09:59 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 FAA15603 for <dhcwg-archive@odin.ietf.org>; Tue, 16 Jul 2002 05:59:48 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA18007 for dhcwg-archive@odin.ietf.org; Tue, 16 Jul 2002 06:00:44 -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 FAA17484; Tue, 16 Jul 2002 05:54:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA17456 for <dhcwg@optimus.ietf.org>; Tue, 16 Jul 2002 05:54:54 -0400 (EDT)
Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15476 for <dhcwg@ietf.org>; Tue, 16 Jul 2002 05:53:56 -0400 (EDT)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id g6G9sqA17396 for <dhcwg@ietf.org>; Tue, 16 Jul 2002 02:54:52 -0700 (PDT)
Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5c1dbfa8ea118164e162c@mailgate2.apple.com> for <dhcwg@ietf.org>; Tue, 16 Jul 2002 02:54:51 -0700
Received: from [133.93.77.116] (vpn-gh-566.apple.com [17.254.138.53]) by scv3.apple.com (8.11.3/8.11.3) with SMTP id g6G9soT18321 for <dhcwg@ietf.org>; Tue, 16 Jul 2002 02:54:50 -0700 (PDT)
Message-Id: <200207160954.g6G9soT18321@scv3.apple.com>
Date: Tue, 16 Jul 2002 02:54:50 -0700
x-sender: cheshire@mail.apple.com
x-mailer: Claris Emailer 2.0v3, January 22, 1998
From: Stuart Cheshire <cheshire@apple.com>
To: DHCP discussion list <dhcwg@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Subject: [dhcwg] Review of Service-Discovery-Type options in DHCP
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

At the Yokohama meeting I pointed out that many DHCP options carry 
information that might be better served via an explicit service discovery 
mechanism.

Thomas Narten pointed out that the IETF community has not arrived at an 
undisputed consensus about how to do service discovery.

I agree with this in the broad sense, but for simple service discovery 
the world does seem to have arrived at an ad-hoc) solution -- functional 
hostnames in DNS.

Common practice is that most companies have a hostname of the form 
"www.company.com." which resolves to the address of the company's web 
server.

Similar examples are:

ntp.company.com.     (NTP Time Server)
mail.company.com.    (Incoming mail)
smtp.company.com.    (SMTP relay for outgoing mail)
pop.company.com.     (POP mailbox host)
imap.company.com.    (IMAP mail access)

This is an ugly solution for two reasons:
1. It is a misuse of DNS host names to name things that are logical 
services, not hosts.
2. The names are not standardized --
is it "ntp.company.com.", or "time.company.com." ?

Fortunately, DNS already has a solution that addresses these two 
deficiencies: SRV records

1. SRV records explicitly names services, not hosts, and
2. SRV records have a formalized naming convention -- the name of the SRV
   record for NTP service at "company.com." is "_ntp._udp.company.com."

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:

1. A time server by looking up SRV record "_ntp._udp.apple.com."
2. An SMTP relay by looking up SRV record "_smtp._tcp.apple.com."

The people at the Apple offices in Europe get a DHCP "Domain Name" option 
which says, "euro.apple.com.", and they find services by looking up names 
like: "_ntp._udp.euro.apple.com." and "_smtp._tcp.euro.apple.com."

If not the existing "Domain Name" option, perhaps the "Domain Search 
List", or something like it, is the right answer. That way, a single DHCP 
option points you to the place in the DNS name space where all your SRV 
records can be found, instead of every service having to have 
yet-another-separate-option-of-its-own in DHCP.

Stuart Cheshire <cheshire@apple.com>
 * Wizard Without Portfolio, Apple Computer
 * Chairman, IETF ZEROCONF
 * www.stuartcheshire.org



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