RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 4 records.

Status: Verified (1)

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

Source of RFC: dhc (int)

Errata ID: 3954
Status: Verified
Type: Editorial

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).

Status: Reported (3)

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

Source of RFC: dhc (int)

Errata ID: 5424
Status: Reported
Type: Editorial

Reported By: Nikolai Malykh
Date Reported: 2018-07-16

Section 3 says:

   DHCPv4 clients and servers that are implemented according to this
   document should be implemented as if the changes specified in
   sections 6.3 and 6.4 have been made to RFC 2131 and RFC 2132.  DHCPv4
   clients should, in addition, follow the behavior specified in section
   6.1.  DHCPv6 clients should follow the behavior specified in section
   6.2.  DHCPv4 servers should additionally follow the behavior
   specified in section 6.3.

It should say:

   DHCPv4 clients and servers that are implemented according to this
   document should be implemented as if the changes specified in
   sections 6.4 and 6.5 have been made to RFC 2131 and RFC 2132.  DHCPv4
   clients should, in addition, follow the behavior specified in section
   6.1.  DHCPv6 clients should follow the behavior specified in section
   6.2.  DHCPv4 servers should additionally follow the behavior
   specified in section 6.3.

Notes:

Incorrect links to sections of this document.

Errata ID: 5425
Status: Reported
Type: Editorial

Reported By: Nikolai Malykh
Date Reported: 2018-07-16

Section 5 says:

   - DHCPv4 servers that do conform to this specification must
     interoperate correctly with DHCPv4 clients that do not conform to
     this specification, except that when configuring such clients,
     behaviors such as those described in section 2 may occur.

It should say:

   - DHCPv4 servers that do conform to this specification must
     interoperate correctly with DHCPv4 clients that do not conform to
     this specification, except that when configuring such clients,
     behaviors such as those described in section 4.2 may occur.

Notes:

Incorrect referenct to section 2.

Errata ID: 5426
Status: Reported
Type: Editorial

Reported By: Nikolai Malykh
Date Reported: 2018-07-16

Section 6 says:

   Here we specify changes to the behavior of DHCPv4 clients and
   servers.  We also specify changes to the wording in RFC 2131 and RFC
   2132.  DHCPv4 clients, servers, and relay agents that conform to this
   specification must implement RFC 2131 and RFC 2132 with the wording
   changes specified in sections 6.3 and 6.4.

It should say:

   Here we specify changes to the behavior of DHCPv4 clients and
   servers.  We also specify changes to the wording in RFC 2131 and RFC
   2132.  DHCPv4 clients, servers, and relay agents that conform to this
   specification must implement RFC 2131 and RFC 2132 with the wording
   changes specified in sections 6.4 and 6.5.

Notes:

Incorrect references to sections of this document.

Report New Errata