How to Report Errata
The following instructions apply to the use of the RFC Errata page.
- Prior to filing a report, note that:
- Errata reports should only be filed for issues that would have been considered errors at the time the RFC was published. Alternate approaches to the topic, URLs that have changed over time, and new personal contact information are examples of issues that errata reports should not be used to address.
- Reports of broken links in the HTML versions of RFCs 1-8649 may be reported as issues with rfc2html, which was used to HTMLize the original text.
- Reports of broken links in the HTML versions of RFCs 8650+ may be reported via errata with publication formats “HTML” and “PDF” selected.
- Enter the RFC number under “Report New Errata”, and click the button.
- Read through the errata that have already been reported for that RFC (if any) to verify that the error you plan to report has not already been reported. If you have uncovered a new erratum, click the button at the end of the page to proceed. Again: note that to report an error in an existing erratum, please contact the RFC Editor.
- Complete the report form as follows:
- this field is filled automatically with the current date
- your name
- your email address (This address will be used to send you the emails described in further steps.)
- select the type of error:
- Editorial – spelling, grammar, punctuation, or syntax error that does not affect the technical meaning
- Technical – error in the technical content (Note that changes in the usage of keywords defined in BCP 14 (RFCs 2119 and 8174) are considered technical.)
Tip: If you are uncertain which type to choose, select Technical, and add your concern to the Notes.
- the section where the error appears
Tip: If the error appears throughout the text, enter GLOBAL for Section.
Tip: If the error appears outside of a numbered section (e.g., in the Abstract), you can enter the location. Note that this will appear as “Section Abstract says” until later corrected by the verifier.
- Publication format(s):
- indicate which format contains the error if the RFC was published in multiple formats (TEXT, PDF, and HTML). This is present only for RFC 8650 and beyond.
- Original Text:
- the text exactly as it appears in the RFC as available from rfc-editor.org: we recommend copy & paste.
- Corrected Text:
- the text as you think it should appear
- any notes or rationale that are relevant to this report. Tip: it is helpful to point out what the update is if it is easy to miss on first read.
- Click Preview to review the report. Then choose Edit, Submit, Submit and Start Another Errata Report (for the same RFC), or Cancel.
- Upon submission, this errata report will be posted online with its status set to “Reported”, and an email (Subject: [Technical Errata Reported] or [Editorial Errata Reported]) will be sent to the submitter, the authors of the RFC, and the verifying party. The verifying party is determined by the stream that produced the RFC (i.e., IETF, IAB, IRTF, Independent Submissions, and Editorial). If the RFC was the product of a working group, the email will be sent to the relevant Area Directors, WG chairs, and WG mailing list.
- Participate in discussion of the errata over email (if any). If you find an error in your report, please contact the RFC Editor. You will receive an email notification when the status of your report is changed by the verifying party (to Verified, Rejected, or Held for Document Update).
Go to the RFC Errata page.