[dhcwg] DDNS-DHCP [1]: Use DHCID RR just for DHCP or extend for other update mechanisms?
Ralph Droms <rdroms@cisco.com> Thu, 05 June 2003 23:46 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22604 for <dhcwg-archive@odin.ietf.org>; Thu, 5 Jun 2003 19:46:37 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h55NkAd22613 for dhcwg-archive@odin.ietf.org; Thu, 5 Jun 2003 19:46:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55NkAB22610 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 5 Jun 2003 19:46:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22565 for <dhcwg-web-archive@ietf.org>; Thu, 5 Jun 2003 19:46:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19O4P2-0004fh-00 for dhcwg-web-archive@ietf.org; Thu, 05 Jun 2003 19:44:16 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19O4P1-0004fe-00 for dhcwg-web-archive@ietf.org; Thu, 05 Jun 2003 19:44:15 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55NilB22524; Thu, 5 Jun 2003 19:44:47 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55NgQB22230 for <dhcwg@optimus.ietf.org>; Thu, 5 Jun 2003 19:42:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22459 for <dhcwg@ietf.org>; Thu, 5 Jun 2003 19:42:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19O4LP-0004eO-00 for dhcwg@ietf.org; Thu, 05 Jun 2003 19:40:32 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by ietf-mx with esmtp (Exim 4.12) id 19O4LO-0004eF-00 for dhcwg@ietf.org; Thu, 05 Jun 2003 19:40:30 -0400
Received: from cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h55Nfk51016956; Thu, 5 Jun 2003 19:41:47 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (sjc-vpn1-278.cisco.com [10.21.97.22]) by cisco.com (8.8.5-Cisco.1/8.8.8) with ESMTP id TAA24637; Thu, 5 Jun 2003 19:41:43 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030605193716.03d40c28@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 05 Jun 2003 19:41:37 -0400
To: dhcwg@ietf.org, namedroppers@ops.ietf.org
From: Ralph Droms <rdroms@cisco.com>
Cc: olaf@ripe.net, Bernard Aboba <aboba@internaut.com>, Rob Austein <sra@hactrn.net>, Ralph Droms <rdroms@cisco.com>, Thomas Narten <narten@us.ibm.com>, Erik.Nordmark@eng.sun.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [dhcwg] DDNS-DHCP [1]: Use DHCID RR just for DHCP or extend for other update mechanisms?
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
DDNS-DHCP issue: The DHCID RR represents an advisory lock used by entities using DHCP to resolve conflicts in the use of DNS records. Is it limiting to restrict the RR to use by entities using DHCP, because there might be other scenarios in the future that could use the same advisory lock mechanism? Or, should the DHCID RR be reserved for use in conjunction with DHCP? _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] DDNS-DHCP [1]: Use DHCID RR just for DHCP… Ralph Droms
- [dhcwg] Re: DDNS-DHCP [1]: Use DHCID RR just for … Michael Richardson