RFC 2822, "Internet Message Format", April 2001

Note: This RFC has been obsoleted by RFC 5322

Note: This RFC has been updated by RFC 5335, RFC 5336

Errata ID: 8155
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: 林博仁(Buo-ren Lin)
Date Reported: 2024-10-23
Rejected by: RFC Editor
Date Rejected: 2024-10-24

Section 2.1.1 says:

Again, even though this limitation is put on
   messages, it is encumbant upon implementations which display messages
   to handle an arbitrarily large number of characters in a line
   (certainly at least up to the 998 character limit) for the sake of
   robustness.

It should say:

Again, even though this limitation is put on 
   messages, it is incumbent upon implementations which display messages
   to handle an arbitrarily large number of characters in a line 
   (certainly at least up to the 998 character limit) for the sake of 
   robustness.

Notes:

"encumbant" seems to be a typo of "incumbent".
--VERIFIER NOTES--
RFC 2822 is obsoleted by RFC 5322, and this typo was corrected in RFC 5322. The RFC Editor is thus rejecting this erratum per #7 on the “IESG Processing of RFC Errata for the IETF Stream” (https://datatracker.ietf.org/doc/statement-iesg-iesg-processing-of-rfc-errata-for-the-ietf-stream-20210507/).

Report New Errata