RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 9225, "Software Defects Considered Harmful", April 2022

Source of RFC: INDEPENDENT

Errata ID: 6911
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML

Reported By: Kyoung-Hwan Yun
Date Reported: 2022-04-01
Verifier Name: RFC Editor
Date Verified: 2022-04-06

Section 4 says:

4. Best Current Practises

It should say:

4. Best Current Practices

Notes:

These rest of the document uses the US spelling "practice". The reported text is inconsistent by using a British variant spelling.

--VERIFIER NOTES--
This entry has been updated from its original submission to show the correct information. Instances of "practice" should be "practise" for consistency with the British spelling used throughout.

Status: Reported (1)

RFC 9225, "Software Defects Considered Harmful", April 2022

Source of RFC: INDEPENDENT

Errata ID: 6910
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Joe Klein
Date Reported: 2022-04-01

Section 4. Best Current says:

6. In fact, assume all internal inputs also are the result of bugs.

It should say:

6. In fact, assume all internal inputs also are the result of bugs.

7. If the bug population increases after each subsequent software 
release, it is generally RECOMMENDED to deploy a Software Bug [BOMbs],
and return when the air has cleared.

[BOMbs] National Telecommunications and Information Administration,
United States Department of Commerce, 2021, https://ntia.gov/SBOM

Notes:

Extend the RFC to include another best practice, associated with BOMbs.

Report New Errata



Advanced Search