[dhcwg] RFC 3256 on The DOCSIS Device Class DHCP

RFC Editor <rfc-ed@ISI.EDU> Fri, 19 April 2002 00:13 UTC

Message-Id: <200204182259.g3IMxXm13524@gamma.isi.edu>
To: IETF-Announce:;
Cc: rfc-editor@rfc-editor.org, dhcwg@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 18 Apr 2002 15:59:33 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
Subject: [dhcwg] RFC 3256 on The DOCSIS Device Class DHCP
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
Precedence: bulk

A new Request for Comments is now available in online RFC libraries.


        RFC 3256

        Title:	    The DOCSIS (Data-Over-Cable Service Interface
                    Specifications) Device Class DHCP (Dynamic Host
                    Configuration Protocol) Relay Agent Information
                    Sub-option 
        Author(s):  D. Jones, R. Woundy
        Status:     Standards Track
	Date:       April 2002
        Mailbox:    doug@yas.com, rwoundy@broadband.att.com
        Pages:      5
        Characters: 8551
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dhc-agentoptions-device-class-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3256.txt


This document proposes a new sub-option to the DHCP (Dynamic Host
Configuration Protocol) Relay Agent Information Option.  This new
sub-option is for use with DOCSIS (Data-Over-Cable Service Interface
Specifications) cable modems and describes a "device class" to which
the cable modem belongs.  The cable modem signals its device class
information to the Relay Agent using DOCSIS signaling, and the Relay
Agent forwards the device class information to the DHCP Server which
can then make a policy decision based on it.

This document is a product of the Dynamic Host Configuration Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3256.txt"><ftp://ftp.isi.edu/in-notes/rfc3256.txt>

[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