RFC - 4361
Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)
| Original: | ftp://ftp.isi.edu/in-notes/rfc4361.txt |
|---|---|
| Authors: | T. Lemon [Nominum], B. Sommerfield [Sun Microsystems] |
| Date: | February 2006 |
| Category: | Proposed Standard |
| Updates: | |
|---|---|
| RFC-3315prop | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (Updated by RFC-4361prop) |
| RFC-2132draft | DHCP Options and BOOTP Vendor Extensions (Updated by RFC-4833prop, RFC-4361prop, RFC-3442prop, RFC-3942prop) |
| RFC-2131draft | Dynamic Host Configuration Protocol (Updated by RFC-4361prop, RFC-3396prop) |
| Referred by: | 4 RFC |
| Refers to: | 5 RFC |
Status
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.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document specifies the format that is to be used for encoding Dynamic Host Configuration Protocol Version Four (DHCPv4) client identifiers, so that those identifiers will be interchangeable with identifiers used in the DHCPv6 protocol. This document also addresses and corrects some problems in RFC 2131 and RFC 2132 with respect to the handling of DHCP client identifiers.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry