RE: [dhcwg] RFC 3256 on The DOCSIS Device Class DHCP
"Kostur, Andre" <Andre@incognito.com> Fri, 19 April 2002 15:26 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 LAA23672 for <dhcwg-archive@odin.ietf.org>; Fri, 19 Apr 2002 11:26:52 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA18836 for dhcwg-archive@odin.ietf.org; Fri, 19 Apr 2002 11:26:54 -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 LAA18326; Fri, 19 Apr 2002 11:22:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18303 for <dhcwg@ns.ietf.org>; Fri, 19 Apr 2002 11:22:04 -0400 (EDT)
Received: from portal.incognito.com (PORTAL.INCOGNITO.COM [207.102.214.30]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23401 for <dhcwg@ietf.org>; Fri, 19 Apr 2002 11:22:00 -0400 (EDT)
Received: from homerdmz.incognito.com ([207.102.214.106] helo=homer.incognito.com.) by portal.incognito.com with smtp (Exim 3.33 #1) id 16ya9D-00032N-00; Fri, 19 Apr 2002 08:18:03 -0700
Received: by homer.incognito.com. with Internet Mail Service (5.5.2653.19) id <2ZV8RM2P>; Fri, 19 Apr 2002 08:28:24 -0700
Message-ID: <4FB49E60CFBA724E88867317DAA3D1984956B9@homer.incognito.com.>
From: "Kostur, Andre" <Andre@incognito.com>
To: 'Bud Millwood' <budm@weird-solutions.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] RFC 3256 on The DOCSIS Device Class DHCP
Date: Fri, 19 Apr 2002 08:28:22 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1E7B6.D76E9FE0"
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
You could simply configure your DHCP server to ignore requests which don't have option 82.... > -----Original Message----- > From: Bud Millwood [mailto:budm@weird-solutions.com] > Sent: Friday, April 19, 2002 1:50 AM > To: dhcwg@ietf.org > Subject: Re: [dhcwg] RFC 3256 on The DOCSIS Device Class DHCP > > > We have at least one customer making policy decisions on the > server based on > the Class Identifier (option 60) value. Apparently, it's > always "docsis1.0" > for a DOCSIS cable-modem. (Not sure about docsis 1.1). > > But even though this method appears to work fine in practice, > I welcome this > new draft because of the security aspect, as well as the > possibility for > future expansion using the reserved bits. > > I think it's important to let a trusted device give us as > much information as > possible about the clients we're servicing. So important, in > fact, that I > have wondered about the possibility of *requiring* *any* kind > of relay agent > (DOCSIS or not) to insert option 82, with information about > the originating > machine (hwtype-mac, for example). The premise being that even in > corporations, most routers are trusted equipment, usually > locked away in a > basement somewhere. > > 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 >
- [dhcwg] RFC 3256 on The DOCSIS Device Class DHCP RFC Editor
- Re: [dhcwg] RFC 3256 on The DOCSIS Device Class D… Bud Millwood
- RE: [dhcwg] RFC 3256 on The DOCSIS Device Class D… Kostur, Andre
- RE: [dhcwg] RFC 3256 on The DOCSIS Device Class D… Woundy, Richard
- Re: [dhcwg] RFC 3256 on The DOCSIS Device Class D… Bud Millwood