[dhcwg] Question about 3315id-for-v4
Ralph Droms <rdroms@cisco.com> Tue, 20 April 2004 17:29 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06562 for <dhcwg-archive@odin.ietf.org>; Tue, 20 Apr 2004 13:29:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFys7-000208-Ae for dhcwg-archive@odin.ietf.org; Tue, 20 Apr 2004 13:17:23 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KHHNNx007685 for dhcwg-archive@odin.ietf.org; Tue, 20 Apr 2004 13:17:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFyY1-0000xL-Be for dhcwg-web-archive@optimus.ietf.org; Tue, 20 Apr 2004 12:56:37 -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 MAA03921 for <dhcwg-web-archive@ietf.org>; Tue, 20 Apr 2004 12:56:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFyXz-0006lF-Ga for dhcwg-web-archive@ietf.org; Tue, 20 Apr 2004 12:56:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFyX5-0006TE-00 for dhcwg-web-archive@ietf.org; Tue, 20 Apr 2004 12:55:39 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFyW3-0006AC-00 for dhcwg-web-archive@ietf.org; Tue, 20 Apr 2004 12:54:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFyGz-00019N-Ns; Tue, 20 Apr 2004 12:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFxhZ-00009n-Cw for dhcwg@optimus.ietf.org; Tue, 20 Apr 2004 12:02:25 -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 MAA29048 for <dhcwg@ietf.org>; Tue, 20 Apr 2004 12:02:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFxhY-00062n-4p for dhcwg@ietf.org; Tue, 20 Apr 2004 12:02:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFxfh-0005Ow-00 for dhcwg@ietf.org; Tue, 20 Apr 2004 12:00:29 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BFxem-0004yF-00 for dhcwg@ietf.org; Tue, 20 Apr 2004 11:59:32 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 20 Apr 2004 08:10:34 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i3KFwx8k012929 for <dhcwg@ietf.org>; Tue, 20 Apr 2004 08:59:00 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-1-104.cisco.com [10.86.240.104]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHS59855; Tue, 20 Apr 2004 11:58:58 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040420115100.01f91588@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 20 Apr 2004 11:58:56 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] Question about 3315id-for-v4
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
It seems one of the motivations for draft-ietf-dhc-3315id-for-v4 is to specify a way in which a dual-stack host can use the same identifier in DHCPv4 and in DHCPv6. A uniform identifier for both versions of DHCP would be useful in the DHCID RR when detecting and reconciling DNS name clashes. So, is there consensus that draft-ietf-dhc-3315id-for-v4 should be designed to support the consistent identification of a host in a DHCID RR regardless of whether the host uses DHCPv4 or DHCPv6? If the answer is yes, how can that consistent identification be achieved? I think the identifier in the latest revision of draft-ietf-dhc-3315id-for-v4 could be used, if the DHCP server and the client agree to use only the DUID in the DHCID RR. However, I think it would be better to avoid requiring the DHCPv4 server to parse the 3315id-for-v4 client identifier for use in the DHCID RR. Is there some other way in which the use of the DHCID RR can be defined to avoid requiring the parsing of any client identification (either DHCpv4 or DHCPv6)? - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Question about 3315id-for-v4 Ralph Droms
- RE: [dhcwg] Question about 3315id-for-v4 Situ, Kevin
- Re: [dhcwg] Question about 3315id-for-v4 Ted Lemon
- Re: [dhcwg] Question about 3315id-for-v4 Ralph Droms
- FW: [dhcwg] Question about 3315id-for-v4 Richard Barr Hibbs