RE: [dhcwg] RFC 3256 on The DOCSIS Device Class DHCP
"Woundy, Richard" <RWoundy@broadband.att.com> Fri, 19 April 2002 19:25 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 PAA22317 for <dhcwg-archive@odin.ietf.org>; Fri, 19 Apr 2002 15:25:39 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA04917 for dhcwg-archive@odin.ietf.org; Fri, 19 Apr 2002 15:25:41 -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 PAA04805; Fri, 19 Apr 2002 15:23:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04779 for <dhcwg@ns.ietf.org>; Fri, 19 Apr 2002 15:22:58 -0400 (EDT)
Received: from snowmass.tci.com (coral.tci.com [198.178.8.81]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21864 for <dhcwg@ietf.org>; Fri, 19 Apr 2002 15:22:55 -0400 (EDT)
Received: from wsimc08.broadband.att.com (wsimc08.tci.com [147.191.89.205]) by snowmass.tci.com (8.12.2/8.12.2) with SMTP id g3JIZejX013233; Fri, 19 Apr 2002 13:22:56 -0600 (MDT)
Received: from 147.191.89.203 by wsimc08.broadband.att.com with SMTP ( Tumbleweed MMS SMTP Relay (MMS v4.7);); Fri, 19 Apr 2002 13:22:55 -0600
X-Server-Uuid: cda7734f-06b2-11d3-bc59-00805fbb2b22
Received: by entexchimc01.tci.com with Internet Mail Service ( 5.5.2653.19) id <D0W8AXY4>; Fri, 19 Apr 2002 13:22:54 -0600
Message-ID: <518E23226CAFD211858C0008C7F9548E185A38B0@neexch01.broadband.att.com>
From: "Woundy, Richard" <RWoundy@broadband.att.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 13:22:45 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-WSS-ID: 10DEB105162530-01-01
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit
Bud, According to the DOCSIS specifications, a DOCSIS 1.0 CM may include the value "docsis1.0" in DHCP option 60, and a DOCSIS 1.1 CM must include the value "docsis1.1" (followed by additional data in the string). See: <http://www.scte.org/standards/pdf/webdocs/SP-RFI-C01-011119.pdf> appendix C.1.1, and <http://www.cablemodem.com/Specs/SP-RFIv1.1-I08-020301.pdf> appendix D.1.1. Note that some relay agents (e.g. broadband aggregation routers acting as ATM VC aggregators for DSLAMs) may not have as much information about the subscriber premise equipment as DOCSIS CMTSs... -- Rich -----Original Message----- From: Bud Millwood [mailto:budm@weird-solutions.com] Sent: Friday, April 19, 2002 4: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 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