Here, for example, is a list of 147 errata reports that IMHO could be closed
(rejected) today. They are either reports on RFCs that are dead in one way or
another (Legacy, Historic, Obsoleted or Unknown), or editorial reports on
pre-2020 RFCs.
Erratum 2019 on RFC5664 (old editorial)
Erratum 3755 on RFC1818 (dead RFC)
Erratum 3820 on RFC4556 (old editorial)
Erratum 3987 on RFC6655 (old editorial)
Erratum 3990 on RFC6655 (old editorial)
Erratum 4104 on RFC6347 (dead RFC)
Erratum 4105 on RFC6347 (dead RFC)
Erratum 4112 on RFC6287 (old editorial)
Erratum 4113 on RFC6287 (old editorial)
Erratum 4115 on RFC6287 (old editorial)
Erratum 4116 on RFC6287 (old editorial)
Erratum 4117 on RFC6287 (old editorial)
Erratum 4170 on RFC5480 (old editorial)
Erratum 4254 on RFC7027 (old editorial)
Erratum 4286 on RFC6962 (dead RFC)
Erratum 4345 on RFC7044 (old editorial)
Erratum 4401 on RFC6287 (old editorial)
Erratum 4447 on RFC7315 (old editorial)
Erratum 4448 on RFC7315 (old editorial)
Erratum 4545 on RFC5570 (old editorial)
Erratum 4610 on RFC6352 (old editorial)
Erratum 4642 on RFC6347 (dead RFC)
Erratum 4697 on RFC6749 (old editorial)
Erratum 4775 on RFC5272 (old editorial)
Erratum 4802 on RFC7520 (old editorial)
Erratum 4828 on RFC7530 (old editorial)
Erratum 4832 on RFC7292 (old editorial)
Erratum 4841 on RFC7208 (old editorial)
Erratum 4859 on RFC7483 (dead RFC)
Erratum 4862 on RFC7265 (old editorial)
Erratum 4881 on RFC6238 (old editorial)
Erratum 4918 on RFC1071 (dead RFC)
Erratum 4929 on RFC5954 (old editorial)
Erratum 4934 on RFC7530 (old editorial)
Erratum 4945 on RFC6749 (old editorial)
Erratum 4967 on RFC5424 (old editorial)
Erratum 5013 on RFC7250 (old editorial)
Erratum 5026 on RFC6347 (dead RFC)
Erratum 5034 on RFC6030 (old editorial)
Erratum 5062 on RFC7848 (old editorial)
Erratum 5133 on RFC6287 (old editorial)
Erratum 5161 on RFC5869 (old editorial)
Erratum 5168 on RFC8288 (old editorial)
Erratum 5169 on RFC8288 (old editorial)
Erratum 5195 on RFC8276 (old editorial)
Erratum 5198 on RFC8275 (old editorial)
Erratum 5210 on RFC8259 (old editorial)
Erratum 5217 on RFC3091 (old editorial)
Erratum 5230 on RFC8291 (old editorial)
Erratum 5233 on RFC5116 (old editorial)
Erratum 5240 on RFC6234 (old editorial)
Erratum 5288 on RFC6455 (old editorial)
Erratum 5308 on RFC6787 (old editorial)
Erratum 5313 on RFC6787 (old editorial)
Erratum 5315 on RFC6787 (old editorial)
Erratum 5318 on RFC8259 (old editorial)
Erratum 5379 on RFC6749 (old editorial)
Erratum 5381 on RFC1912 (dead RFC)
Erratum 5779 on RFC7030 (old editorial)
Erratum 5446 on RFC5965 (old editorial)
Erratum 5518 on RFC6265 (old editorial)
Erratum 5580 on RFC5802 (old editorial)
Erratum 5614 on RFC6545 (old editorial)
Erratum 5613 on RFC0002 (dead RFC)
Erratum 5655 on RFC0270 (dead RFC)
Erratum 5666 on RFC7483 (dead RFC)
Erratum 5673 on RFC6125 (dead RFC)
Erratum 5678 on RFC7729 (old editorial)
Erratum 5705 on RFC7659 (old editorial)
Erratum 5706 on RFC7659 (old editorial)
Erratum 5745 on RFC6901 (old editorial)
Erratum 5764 on RFC5903 (old editorial)
Erratum 5885 on RFC0304 (dead RFC)
Erratum 5903 on RFC6347 (dead RFC)
Erratum 5934 on RFC8659 (old editorial)
Erratum 5985 on RFC8225 (old editorial)
Erratum 5998 on RFC7464 (old editorial)
Erratum 6005 on RFC7643 (old editorial)
Erratum 6018 on RFC7516 (old editorial)
Erratum 6093 on RFC6265 (old editorial)
Erratum 6161 on RFC6750 (old editorial)
Erratum 6213 on RFC7996 (old editorial)
Erratum 6325 on RFC6125 (dead RFC)
Erratum 6249 on RFC4948 (old editorial)
Erratum 6255 on RFC5531 (old editorial)
Erratum 6329 on RFC6090 (old editorial)
Erratum 6367 on RFC8650 (old editorial)
Erratum 6433 on RFC7208 (old editorial)
Erratum 6501 on RFC8089 (old editorial)
Erratum 6502 on RFC6270 (old editorial)
Erratum 6525 on RFC8461 (old editorial)
Erratum 6523 on RFC6234 (old editorial)
Erratum 6574 on RFC7991 (old editorial)
Erratum 6614 on RFC6749 (old editorial)
Erratum 6615 on RFC6749 (old editorial)
Erratum 6647 on RFC5424 (old editorial)
Erratum 6704 on RFC7616 (old editorial)
Erratum 6708 on RFC8484 (old editorial)
Erratum 6709 on RFC4862 (old editorial)
Erratum 6715 on RFC6844 (dead RFC)
Erratum 6727 on RFC7643 (old editorial)
Erratum 7808 on RFC7997 (old editorial)
Erratum 6978 on RFC8148 (old editorial)
Erratum 7004 on RFC8276 (old editorial)
Erratum 7006 on RFC6030 (old editorial)
Erratum 7140 on RFC6637 (dead RFC)
Erratum 7377 on RFC0865 (dead RFC)
Erratum 7526 on RFC8445 (old editorial)
Erratum 7918 on RFC1741 (dead RFC)
Erratum 7907 on RFC6787 (old editorial)
Erratum 7950 on RFC6386 (old editorial)
Erratum 8075 on RFC3227 (old editorial)
Erratum 8121 on RFC6908 (old editorial)
Erratum 4570 on RFC7700 (dead RFC)
Erratum 3888 on RFC4402 (dead RFC)
Erratum 3917 on RFC6347 (dead RFC)
Erratum 4103 on RFC6347 (dead RFC)
Erratum 4204 on RFC6962 (dead RFC)
Erratum 4273 on RFC5751 (dead RFC)
Erratum 4568 on RFC7564 (dead RFC)
Erratum 4800 on RFC5077 (dead RFC)
Erratum 4882 on RFC6961 (dead RFC)
Erratum 5186 on RFC6347 (dead RFC)
Erratum 5330 on RFC2183 (dead RFC)
Erratum 5359 on RFC2638 (dead RFC)
Erratum 5435 on RFC7601 (dead RFC)
Erratum 5482 on RFC1557 (dead RFC)
Erratum 5515 on RFC7807 (dead RFC)
Erratum 5595 on RFC4566 (dead RFC)
Erratum 5654 on RFC6125 (dead RFC)
Erratum 5667 on RFC7483 (dead RFC)
Erratum 5701 on RFC2231 (dead RFC)
Erratum 5923 on RFC2397 (dead RFC)
Erratum 6022 on RFC4566 (dead RFC)
Erratum 6225 on RFC4122 (dead RFC)
Erratum 6597 on RFC8152 (dead RFC)
Erratum 6637 on RFC3501 (dead RFC)
Erratum 6706 on RFC1288 (dead RFC)
Erratum 6824 on RFC0823 (dead RFC)
Erratum 6909 on RFC8152 (dead RFC)
Erratum 7321 on RFC0916 (dead RFC)
Erratum 7622 on RFC3720 (dead RFC)
Erratum 7764 on RFC1951 (dead RFC)
Erratum 7913 on RFC4770 (dead RFC)
Erratum 7923 on RFC2126 (dead RFC)
Erratum 7970 on RFC4880 (dead RFC)
Erratum 8089 on RFC6347 (dead RFC)
Regards
Brian Carpenter
On 20-Dec-24 09:07, Brian E Carpenter wrote:
On 20-Dec-24 04:46, Jean Mahoney wrote:
...
To deal with the backlog, should we just close reports that have been
open for a long time?
I know this is tempting but who's to say that a report from 5 years ago wrong?
One suggestion (and it doesn't need a new process) is to send an email to
the reporter of each open report >N years old, saying "Is this still valid?
Unless you reply within one month, we will close it."
The definition of "long time" would need to be
determined.
There are currently the following open reports:
2010: 4
2013: 5
2014: 17
2015: 30
2016: 45
2017: 50
2018: 65
2019: 59
2020: 77
2021: 62
2022: 81
2023: 69
2024: 149
Total: 713
Here's a suggested plan:
- Arbitrarily close all reports on Legacy stream and Historic or Obsoleted
or Unknown RFCs. (And don't allow them in future.)
For all reports before 2020:
- Close all editorial reports.
- Send "Is this still valid?" messages for the rest, and close them a month
later if no reply.
Or should the RPC host a hackathon at an upcoming IETF
meeting where verifiers work through as many open reports as possible?
We could bring pizza :-)
Something like that for the reports since 2020; or launch an online hackathon.
Regards
Brian
Thanks!
Jean
We should chuck
it out and replace it entirely.
Cheers,
S.
--
rswg mailing list -- rswg@rfc-editor.org
To unsubscribe send an email to rswg-le...@rfc-editor.org
