Subject: [ipcdn] Update on the DOCSIS DCI Suboption for the DHCP Relay Agent Information Option

From: Rich Woundy <[email-masked]>
Date: Fri, 08 Feb 2002 16:38:11 -0500

Folks,

The information in this email pertains to the following requirement in the 
DOCSIS 1.1 RFI, section 6.3.24:
"The CMTS MUST retain the device class information for use in the DHCP 
Process. The CMTS MUST create a DHCP Agent Option 82 tuple with the device 
class information and MUST insert this tuple in the DHCPDISCOVER from the 
corresponding CM before forwarding that DHCPDISCOVER to the DHCP server."

The DHCP DCI suboption draft 
<http://www.ietf.org/internet-drafts/draft-ietf-dhc-agentoptions-device-class-04.txt> 
is on the RFC editor's queue <http://www.rfc-editor.org/queue.html>. The 
RFC editor's queue is the final step before RFC publication; by publication 
time, the draft's suboption code (currently "TBD" in sections 2 and 4 of 
the draft) must be replaced with an official number from IANA.

I have recently received email from IANA that states that the suboption 
code has been assigned the value 4:

At 02:20 PM 2/6/2002 -0800, IANA wrote:
>Attn: Authors
>
>We are working on the IANA Actions for RFC-to-be
><draft-ietf-dhc-agentoptions-device-class-04.txt>.
>
>We have assigned the value 4 to DOCSIS Device Class
>Suboption.  Please see the following to view the
>assignment:
>
><http://www.iana.org/assignments/bootp-dhcp-parameters>
>
>Please let us know if this looks correct.  After
>we receive your response we will send a message to
>the RFC-Editor to let them know that the IANA has
>completed the IANA Actions for this document.
>
>Thank you for your time.
>
>Best regards,
>
>Michelle S. Cotton
>IANA Administrator

-- Rich

_______________________________________________
IPCDN mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ipcdn