idnits 2.17.1 draft-ietf-dhc-agentoptions-device-class-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3256 5 Title: The DOCSIS (Data-Over-Cable Service Interface 6 Specifications) Device Class DHCP (Dynamic Host 7 Configuration Protocol) Relay Agent Information 8 Sub-option 9 Author(s): D. Jones, R. Woundy 10 Status: Standards Track 11 Date: April 2002 12 Mailbox: doug@yas.com, rwoundy@broadband.att.com 13 Pages: 5 14 Characters: 8551 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-dhc-agentoptions-device-class-04.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3256.txt 21 This document proposes a new sub-option to the DHCP (Dynamic Host 22 Configuration Protocol) Relay Agent Information Option. This new 23 sub-option is for use with DOCSIS (Data-Over-Cable Service Interface 24 Specifications) cable modems and describes a "device class" to which 25 the cable modem belongs. The cable modem signals its device class 26 information to the Relay Agent using DOCSIS signaling, and the Relay 27 Agent forwards the device class information to the DHCP Server which 28 can then make a policy decision based on it. 30 This document is a product of the Dynamic Host Configuration Working 31 Group of the IETF. 33 This is now a Proposed Standard Protocol. 35 This document specifies an Internet standards track protocol for the 36 Internet community, and requests discussion and suggestions for 37 improvements. Please refer to the current edition of the "Internet 38 Official Protocol Standards" (STD 1) for the standardization state and 39 status of this protocol. Distribution of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.