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

Erik Guttman <Erik.Guttman@sun.com> Thu, 18 July 2002 22: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 SAA14196 for <dhcwg-archive@odin.ietf.org>; Thu, 18 Jul 2002 18:34:25 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id SAA16491 for dhcwg-archive@odin.ietf.org; Thu, 18 Jul 2002 18:35:22 -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 SAA16447; Thu, 18 Jul 2002 18:33:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12466 for <dhcwg@optimus.ietf.org>; Wed, 17 Jul 2002 10:07:11 -0400 (EDT)
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17075 for <dhcwg@ietf.org>; Wed, 17 Jul 2002 10:06:11 -0400 (EDT)
Received: from hs-ehdb03-01.Germany.Sun.COM ([129.157.142.201]) by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA07436; Wed, 17 Jul 2002 08:07:06 -0600 (MDT)
Received: from field (field [129.157.142.146]) by hs-ehdb03-01.Germany.Sun.COM (8.10.2+Sun/8.10.2/ENSMAIL,v2.2) with SMTP id g6HE73b03037; Wed, 17 Jul 2002 16:07:03 +0200 (MEST)
Date: Wed, 17 Jul 2002 16:06:22 +0200
From: Erik Guttman <Erik.Guttman@sun.com>
X-Sender: erikg@field
To: John Schnizlein <jschnizl@cisco.com>
cc: Erik Guttman <Erik.Guttman@sun.com>, DHCP discussion list <dhcwg@ietf.org>, Stuart Cheshire <cheshire@apple.com>
Subject: Re: [dhcwg] Review of Service-Discovery-Type options in DHCP
In-Reply-To: <4.3.2.7.2.20020717094514.01a2eb20@wells.cisco.com>
Message-ID: <Pine.SOL.3.96.1020717154904.25889C-100000@field>
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

> >Proposal:
> >
> >Many working groups create DHCP options for service discovery.
> >Others are specifying use of DNS SRV RRs.  What if we specify a
> >simple mapping between the two and create a registration process:
> >
> >  IETF Standards Track Service => DHCP Option # and DNS SRV Name

On Wed, 17 Jul 2002, John Schnizlein wrote:
> What is the problem your proposal intends to solve?

Rather than consider 'which is better' I believe DHCP and DNS are 
pretty equivalent for this function.  Why not facilitate this
equivalence and provide for making responses from DHCP consistent
with those from DNS?

It would be nice if dhcp option numbers assigned could be paired
with well known names to be used in DNS SRV records.  This would
facilitate DNS and DHCP giving out the same information.  This will
be particularly useful if stateless DHCPv6 and multicast DNS become
pervasive.  A stateless DHCP and multicast DNS server might use the 
same database to answer a request for a particular service type.

Erik




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