IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Thu, 18 July 2002 01:45 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 VAA06059 for <dhcwg-archive@odin.ietf.org>; Wed, 17 Jul 2002 21:45:03 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id VAA16055 for dhcwg-archive@odin.ietf.org; Wed, 17 Jul 2002 21:46:00 -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 VAA15923; Wed, 17 Jul 2002 21:41:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA15898 for <dhcwg@ns.ietf.org>; Wed, 17 Jul 2002 21:41:28 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05940 for <dhcwg@ietf.org>; Wed, 17 Jul 2002 21:40:24 -0400 (EDT)
Received: from green.bisbee.fugue.com (dechen.dyn.ietf54.wide.ad.jp [133.93.74.182]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id g6I1eSd10083; Thu, 18 Jul 2002 01:40:28 GMT
Received: from dechen (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.12.2/8.6.11) with ESMTP id g6I1eeXU002532; Thu, 18 Jul 2002 10:40:40 +0900 (JST)
Date: Thu, 18 Jul 2002 10:40:40 +0900
Subject: Re: [dhcwg] Review of Service-Discovery-Type options in DHCP
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v482)
Cc: DHCP discussion list <dhcwg@ietf.org>, Stuart Cheshire <cheshire@apple.com>
To: Chris Pearson <chris.pearson@infocus.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <EEBC1981C362D311AA230008C7E627BA07D8EB74@toccata>
Message-Id: <5DA9C5D3-99EF-11D6-8431-00039317663C@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

> RFC2131 para. 3.2 shows DHCPREQUEST for address reuse being broadcast.  
> That
> may just be the example chosen, but it's certainly misleading.

Right, this happens once when you power on your computer, not every time 
the lease is renewed.

> Also, DNS dynamic update offers the potential to track low-frequency
> changes in service availability -- how would DHCP support that?

It's true that DHCP provides no way to do this without operator 
intervention, but you are ignoring the key management problem with DNS.   
You can't do ad-hoc service registration with DNS using dynamic updates, 
because the thing that's registering has no security association with the 
DNS server.

:'/


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

v2.23.0 | Report a Bug | By Email