Re: [dhcwg] Re: Last call for <draft-ietf-dhc-ddns-resolution-02.txt>

Mark Stapp <mjs@cisco.com> Mon, 27 August 2001 22:29 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 SAA03101; Mon, 27 Aug 2001 18:29:58 -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 SAA10107; Mon, 27 Aug 2001 18:27: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 SAA10081 for <dhcwg@ns.ietf.org>; Mon, 27 Aug 2001 18:26:59 -0400 (EDT)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.131.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02989 for <dhcwg@ietf.org>; Mon, 27 Aug 2001 18:25:37 -0400 (EDT)
Received: from MJS-W2K.cisco.com (dhcp-161-44-149-89.cisco.com [161.44.149.89]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id SAA00704; Mon, 27 Aug 2001 18:26:25 -0400 (EDT)
Message-Id: <4.3.2.7.2.20010827181455.03837030@funnel.cisco.com>
X-Sender: mjs@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 27 Aug 2001 18:27:03 -0400
To: Stuart Cheshire <cheshire@apple.com>
From: Mark Stapp <mjs@cisco.com>
Subject: Re: [dhcwg] Re: Last call for <draft-ietf-dhc-ddns-resolution-02.txt>
Cc: <dhcwg@ietf.org>
In-Reply-To: <200108272105.OAA01923@scv1.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

Stuart,

My anecdotal needs aren't the motivation for this specification. It is a 
common practice in many organizations to provide matching A and PTR RRs for 
each active host. Manually configuring those RRs and keeping them up to 
date is inefficient in DHCP environments. Dns updates are a very good 
solution to that problem. That's a different problem in some ways from your 
'roving host' situation, but it's a common problem. As you may know, Win 2k 
deployments for example don't work well without dns updates. In many 
networks, hosts don't go a-roving much, but administrators still derive a 
significant benefit from dns updates that are integrated into the dhcp 
exchange. Some form of that integration is offered by all the DHCP server 
vendors that I know of. A number of issues have arisen over time as DHCP 
and DNS updates have been deployed together, and those issues are the ones 
that motivated these specifications.

As I've written repeatedly, what's specified isn't intended to and doesn't 
prevent you from configuring your host as you have.

-- Mark

At 02:05 PM 8/27/2001 -0700, Stuart Cheshire wrote:
> >Personally, I don't particularly care whether my laptop can be 'reached'
> >using a stable dns name
>
>Now I'm really confused about why you're writing this draft.
>
>What is the point of doing dynamic DNS updates, if not so that your
>machine has a constant DNS name by which other hosts can refer to it?
>
>Stuart Cheshire <cheshire@apple.com>
>  * Wizard Without Portfolio, Apple Computer
>  * Chairman, IETF ZEROCONF
>  * www.stuartcheshire.org


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