RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (1)

RFC 2322, "Management of IP numbers by peg-dhcp", April 1998

Source of RFC: Legacy

Errata ID: 5213
Status: Reported
Type: Editorial

Reported By: Junxiao Shi
Date Reported: 2017-12-23

Section Issuing IP says:

   If someone could apply for a networkrange, and he net-extension isn't
   used, coat-hangers can be prepared with sets of pegs attached to
   them.

It should say:

   If someone could apply for a networkrange, and the net-extension
   isn't used, coat-hangers can be prepared with sets of pegs attached
   to them.

Notes:

typo “he”

Status: Held for Document Update (1)

RFC 2322, "Management of IP numbers by peg-dhcp", April 1998

Source of RFC: Legacy

Errata ID: 5753
Status: Held for Document Update
Type: Editorial

Reported By: Adam Schumacher
Date Reported: 2019-06-14
Held for Document Update by: Warren Kumari (Ops AD)
Date Held: 2019-06-14

Section Security says:

But, once the peg is attached to a network cable, 
the chance to loose the peg is minimized.

It should say:

But, once the peg is attached to a network cable, 
the chance to lose the peg is minimized.

Notes:

Although there is a possibility that the author intended to use the verb form of "loose", implying that there would be a chance to unbind the peg to go about its own business, it's more likely that they intended to refer to the situation where the peg is lost, rather than simply released.

Report New Errata