RFC Errata
Found 3 records.
Status: Verified (1)
RFC 5797, "FTP Command and Extension Registry", March 2010
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 2581
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: VicTor Smirnoff
Date Reported: 2010-10-19
Verifier Name: Peter Saint-Andre
Date Verified: 2011-11-12
Section 3 says:
| STOU | base | Store Unique | a | o | 959, 1123 |
It should say:
| STOU | base | Store Unique | s | o | 959, 1123 |
Notes:
RFC0959 has defined STOU as FTP (S)ervice command, but not (A)ccess Control command
Status: Reported (1)
RFC 5797, "FTP Command and Extension Registry", March 2010
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 5748
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Eugene Adell
Date Reported: 2019-06-08
Section 3 says:
| RNTO | base | Rename From | s | m | 959 |
It should say:
| RNTO | base | Rename To | s | m | 959 |
Notes:
Obviously RNTO = Rename To as defined in RFC 959
Status: Rejected (1)
RFC 5797, "FTP Command and Extension Registry", March 2010
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 3471
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alun Jones
Date Reported: 2013-01-27
Rejected by: Pete Resnick
Date Rejected: 2013-01-28
Section 5 says:
Notes:
Section 5 states that the IANA has set up the registry, but does not give any hints as to how to find it. A link to its location would be handy. I presume the correct location is http://www.iana.org/assignments/ftp-commands-extensions/ftp-commands-extensions.xml
--VERIFIER NOTES--
A a practice, we do not put URLs for registries into RFCs. Not an appropriate use of the errata system, in any event.