Re: [dhcwg] RFC 3256 on The DOCSIS Device Class DHCP
Bud Millwood <budm@weird-solutions.com> Fri, 19 April 2002 08:46 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 EAA13671 for <dhcwg-archive@odin.ietf.org>; Fri, 19 Apr 2002 04:46:42 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id EAA23784 for dhcwg-archive@odin.ietf.org; Fri, 19 Apr 2002 04:46:44 -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 EAA23649; Fri, 19 Apr 2002 04:44:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA23632 for <dhcwg@ns.ietf.org>; Fri, 19 Apr 2002 04:44:41 -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 EAA13629 for <dhcwg@ietf.org>; Fri, 19 Apr 2002 04:44:32 -0400 (EDT)
Received: from there ([193.12.201.10]) by fep01-svc.swip.net with SMTP id <20020419084404.GXUB72.fep01-svc.swip.net@there> for <dhcwg@ietf.org>; Fri, 19 Apr 2002 10:44: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: Fri, 19 Apr 2002 10:50:13 +0200
X-Mailer: KMail [version 1.3.2]
References: <200204182259.g3IMxXm13524@gamma.isi.edu>
In-Reply-To: <200204182259.g3IMxXm13524@gamma.isi.edu>
MIME-Version: 1.0
Message-Id: <20020419084404.GXUB72.fep01-svc.swip.net@there>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA23633
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
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