IETF Logo Mail Archive

Re: [dhcwg] RFC 3256 on The DOCSIS Device Class DHCP

Bud Millwood <budm@weird-solutions.com> Mon, 22 April 2002 10:47 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 GAA20974 for <dhcwg-archive@odin.ietf.org>; Mon, 22 Apr 2002 06:47:14 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA05416 for dhcwg-archive@odin.ietf.org; Mon, 22 Apr 2002 06:47:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA05328; Mon, 22 Apr 2002 06:45:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA05302 for <dhcwg@optimus.ietf.org>; Mon, 22 Apr 2002 06:45:36 -0400 (EDT)
Received: from fep01-svc.swip.net (fep01.swip.net [130.244.199.129]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20932 for <dhcwg@ietf.org>; Mon, 22 Apr 2002 06:45:33 -0400 (EDT)
Received: from there ([193.12.201.10]) by fep01-svc.swip.net with SMTP id <20020422104504.NEKJ26263.fep01-svc.swip.net@there> for <dhcwg@ietf.org>; Mon, 22 Apr 2002 12:45:04 +0200
Content-Type: text/plain; charset="iso-8859-1"
From: Bud Millwood <budm@weird-solutions.com>
Reply-To: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] RFC 3256 on The DOCSIS Device Class DHCP
Date: Mon, 22 Apr 2002 12:51:14 +0200
X-Mailer: KMail [version 1.3.2]
References: <4FB49E60CFBA724E88867317DAA3D1984956B9@homer.incognito.com.>
In-Reply-To: <4FB49E60CFBA724E88867317DAA3D1984956B9@homer.incognito.com.>
MIME-Version: 1.0
Message-Id: <20020422104504.NEKJ26263.fep01-svc.swip.net@there>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id GAA05303
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 8bit

Andre Kostur wrote:
> You could simply configure your DHCP server to ignore requests which don't
> have option 82....

Yep, on provider networks, but on most corporate networks the average relay 
agent doesn't support option 82. I was just pointing out that providers are 
using a decent mechanism for limiting DoS attacks, and maybe this technique 
could be implemented in more networks if the average relay agent provided 
support for this 82 (specifically RID, in the format of the 'htype'-'chaddr' 
field would be sufficient).

But as Richard Woundy pointed out, not all relay agents have info about the 
CPE, so you couldn't really make it a requirement.

Thanks for the links, Richard.

Bud Millwood
Weird Solutions, Inc.
http://www.weird-solutions.com
tel: +46 70 566 7803
fax: +46 8 758 3687
mailto:budm@weird-solutions.com

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

v2.23.0 | Report a Bug | By Email