Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) by bugs.isc.org (Postfix) with ESMTP id 941C220EE26D; Sat, 23 Apr 2011 15:39:55 +0000 (UTC)
Received: from mail-ww0-f45.google.com (mail-ww0-f45.google.com [74.125.82.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 098D0C941E; Sat, 23 Apr 2011 15:39:52 +0000 (UTC) (envelope-from hal@dev.mellanox.co.il)
Received: by wwi36 with SMTP id 36so1131616wwi.26 for <multiple recipients>; Sat, 23 Apr 2011 08:39:50 -0700 (PDT)
Received: by 10.227.207.65 with SMTP id fx1mr2168537wbb.119.1303573190808; Sat, 23 Apr 2011 08:39:50 -0700 (PDT)
Received: from [192.168.1.100] (c-71-192-10-85.hsd1.ma.comcast.net [71.192.10.85]) by mx.google.com with ESMTPS id p5sm2318134wbg.11.2011.04.23.08.39.48 (version=SSLv3 cipher=OTHER); Sat, 23 Apr 2011 08:39:49 -0700 (PDT)
Delivered-To: dhcp-bugs@bugs.isc.org
Subject: [PATCH 0/2] Add support for DHCP over IPoIB per IETF RFC 4390
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
Return-Path: <hal@dev.mellanox.co.il>
X-Original-To: dhcp-bugs@bugs.isc.org
Date: Sat, 23 Apr 2011 11:39:45 -0400
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mx.pao1.isc.org
content-type: text/plain; charset="utf-8"
Message-ID: <4DB2F2C1.5030306@dev.mellanox.co.il>
To: dhcp-bugs@isc.org, dhcp-suggest@isc.org
Content-Transfer-Encoding: 7bit
From: Hal Rosenstock <hal@dev.mellanox.co.il>
X-RT-Original-Encoding: ISO-8859-1
Content-Length: 548

The following patch series adds Dynamic Host Configuration Protocol
(DHCP) over InfiniBand per IETF standard RFC 4390.

The two main complexities with this are:
1. IPoIB client hardware address is 20 bytes so it doesn't fit into
client hardware address (limited to 16 bytes) so DHCP client identifier
is used.
2. The client must set the BROADCAST flag in both DHCPDISCOVER and
DHCPREQUEST messages to ensure that the server broadcasts it's reply to
the client.

Note these changes are for Linux (LPF) and are against the 4.2.1-P1
version of DHCP.