RFC 4361, "Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)", February 2006

Note: This RFC has been updated by RFC 5494

Errata ID: 3954
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Samir Sawhney
Date Reported: 2014-04-09
Verifier Name: Ted Lemon
Date Verified: 2014-04-09

Section 7 says:

"Some DHCP servers work around this problem for the common case where
the boot Programmable Read Only Memory (PROM) presents no client
identifier, and the operating system DHCP client presents a client
identifier constructed from the Message Authentication Code (MAC)
address of the network interface..."

It should say:

"Some DHCP servers work around this problem for the common case where
the boot Programmable Read Only Memory (PROM) presents no client
identifier, and the operating system DHCP client presents a client
identifier constructed from the Media Access Control (MAC)
address of the network interface..."

Notes:

The sentence (included above) from Section 7 of RFC 4361 provides an incorrect
expansion of the MAC acronym (Message Authentication Code).

Report New Errata