[dhcwg] Re: [Ipoverib] IP over IB DHCP draft last call
Thomas Narten <narten@us.ibm.com> Wed, 16 March 2005 18:40 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20545 for <dhcwg-web-archive@ietf.org>; Wed, 16 Mar 2005 13:40:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBdVW-0005Zp-BT for dhcwg-web-archive@ietf.org; Wed, 16 Mar 2005 13:44:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DBdQR-00058p-H4; Wed, 16 Mar 2005 13:39:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DBdQO-00058h-RY; Wed, 16 Mar 2005 13:39:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20360; Wed, 16 Mar 2005 13:39:17 -0500 (EST)
Received: from e31.co.us.ibm.com ([32.97.110.129]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBdUS-0005W7-Kx; Wed, 16 Mar 2005 13:43:34 -0500
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e31.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j2GId8ua351282; Wed, 16 Mar 2005 13:39:08 -0500
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j2GId7V8196614; Wed, 16 Mar 2005 11:39:08 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j2GId7vx014618; Wed, 16 Mar 2005 11:39:07 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.37.211.15]) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j2GId6d7014533; Wed, 16 Mar 2005 11:39:06 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id j2GIaXLL005071; Wed, 16 Mar 2005 13:36:38 -0500
Message-Id: <200503161836.j2GIaXLL005071@rotala.raleigh.ibm.com>
To: bill@strahm.net
In-Reply-To: Message from bill@strahm.net of "Mon, 14 Feb 2005 11:59:38 MST." <20050214185938.16613.qmail@webmail01.mesa1.secureserver.net>
Date: Wed, 16 Mar 2005 13:36:33 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ipoverib@ietf.org, dhcwg@ietf.org
Subject: [dhcwg] Re: [Ipoverib] IP over IB DHCP draft last call
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
FWIW, and speaking as a regular WG member now, and having gone reviewed both draft-ietf-dhc-3315id-for-v4-04.txt and draft-ietf-ipoib-dhcp-over-infiniband-09.txt, and having gone and reviewed some previous the threads on this topic... The current document says: According to [RFC2132] the "client-identifier" option may consist of any data that uniquely identifies the interface. Examples of suitable "client-identifier" values are the link-layer address, fully qualified domain name (FQDN) or, an EUI-64 value associated with the interface. In other words, any valid client-identifier can be used. I see no reason why the IB document needs to do anything different than just follow the recommendation in the 3315id. If there is any reason why some other variant should be allowed, I'd like to hear it. Leaving it up to the implementor to decide just creates confusion and unecessary variation that serves little purpose (at least as far as I can tell). Morever, the motivations for using a 3315id-style client-identifier are compelling. So, unless there is a good reason why IB can't use 3315-id, I'd suggest replacing the above paragraph with something like: When using DHCP over an Infiniband interface, a client-identifier as described in [draft-ietf-dhc-3315id-for-v4-04.txt] MUST be used. Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] IP over IB DHCP draft last call bill
- [dhcwg] Re: [Ipoverib] IP over IB DHCP draft last… Thomas Narten
- [dhcwg] Re: [Ipoverib] IP over IB DHCP draft last… Vivek Kashyap
- [dhcwg] Re: [Ipoverib] IP over IB DHCP draft last… Vivek Kashyap