RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Held for Document Update (1)

RFC 8174, "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", May 2017

Source of RFC: IETF - NON WORKING GROUP

Errata ID: 5022
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Xiaoyin Liu
Date Reported: 2017-05-19
Held for Document Update by: Ben Campbell
Date Held: 2017-05-22

Throughout the document, when it says:

by clarifying that only UPPERCASE usage of the key words have the
defined special meanings.

It should say:

by clarifying that only UPPERCASE usage of the key words has the
defined special meanings.

Notes:

The text appears in both "Abstract" and Section 1. The verb should be "has" because "usage" is a singular noun.

Status: Rejected (1)

RFC 8174, "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", May 2017

Source of RFC: IETF - NON WORKING GROUP

Errata ID: 6878
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT

Reported By: Boris
Date Reported: 2022-03-10
Rejected by: RFC Editor
Date Rejected: 2022-04-05

Throughout the document, when it says:

http://www.rfc-editor.org/info/rfc8174
http://trustee.ietf.org/license-info
http://www.rfc-editor.org/info/rfc2119
http://internetmessagingtechnology.org

It should say:

https://www.rfc-editor.org/info/rfc8174
https://trustee.ietf.org/documents/trust-legal-provisions
https://www.rfc-editor.org/info/rfc2119
https://internetmessagingtechnology.org

Notes:

The URLs should be using HTTPS instead of HTTP and should be updated.
--VERIFIER NOTES--
This is how the URLs were presented when the RFC was published.

Report New Errata



Advanced Search