Re: [dhcwg] "client identifier" in server replies

Ted Lemon <mellon@fugue.com> Tue, 08 July 2003 12:51 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 IAA19903; Tue, 8 Jul 2003 08:51:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zrvx-0008R4-JT; Tue, 08 Jul 2003 08:51:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zkto-0001dP-N0 for dhcwg@optimus.ietf.org; Tue, 08 Jul 2003 01:20:20 -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 BAA27353 for <dhcwg@ietf.org>; Tue, 8 Jul 2003 01:20:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zktl-0006Lj-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 01:20:17 -0400
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 19Zktk-0006Lg-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 01:20:16 -0400
Received: from depa.dmes.org (dsl093-187-232.chi2.dsl.speakeasy.net [66.93.187.232]) by toccata.fugue.com (Postfix) with ESMTP id 2D1AF1B21EC; Tue, 8 Jul 2003 00:15:37 -0500 (CDT)
From: Ted Lemon <mellon@fugue.com>
To: narasimha.nelakuditi@nokia.com, tmh@whitefang.com
Subject: Re: [dhcwg] "client identifier" in server replies
Date: Tue, 08 Jul 2003 00:20:12 -0500
User-Agent: KMail/1.5
Cc: dhcwg@ietf.org
References: <79A2DB53BC51BD448F0D19A86FB1DB637F1FF6@siebe002.apac.nokia.com>
In-Reply-To: <79A2DB53BC51BD448F0D19A86FB1DB637F1FF6@siebe002.apac.nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200307080020.12116.mellon@fugue.com>
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit

On Monday 07 July 2003 23:39, narasimha.nelakuditi@nokia.com wrote:
> Coming back to 'xid', I think checking 'xid' alone is not a good idea,
> considering erroneous servers, multiple clients using same xids etc.

That's right.   We hacked the ISC DHCP client to check chaddr in the reply 
because someone was in fact getting broadcast replies in high-traffic 
environments that were caused by xid collisions.   The problem is that a 
really good random number generator for xid generation is difficult to write 
in a portable way, and so we wind up using a fairly crappy one, which does 
the trick but certainly wouldn't be appropriate for doing crypto.   More to 
the point, in some environments I would expect collisions to be pretty much 
inevitable.   Collisions are a pretty serious problem, so I think the point 
that is being raised here is a serious one.


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