RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Verified (1)

RFC 5531, "RPC: Remote Procedure Call Protocol Specification Version 2", May 2009

Note: This RFC has been updated by RFC 9289

Source of RFC: nfsv4 (wit)

Errata ID: 4849
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: RFC Editor
Date Reported: 2016-10-31
Verifier Name: RFC Editor
Date Verified: 2016-10-31

Appendix C says:

   RPCSEC_GSS      6               /* GSS-based RPC security for auth,
                                      integrity and privacy, RPC 5403 */

It should say:

   RPCSEC_GSS      6               /* GSS-based RPC security for auth,
                                      integrity and privacy, RFC 5403 */

Notes:

"RPC 5403" should be "RFC 5403".

Status: Reported (1)

RFC 5531, "RPC: Remote Procedure Call Protocol Specification Version 2", May 2009

Note: This RFC has been updated by RFC 9289

Source of RFC: nfsv4 (wit)

Errata ID: 6255
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Ed Schouten
Date Reported: 2020-08-12

Section 9 says:

         union reply_body switch (reply_stat stat) {
         case MSG_ACCEPTED:
            accepted_reply areply;
         case MSG_DENIED:
            rejected_reply rreply;
         } reply;

It should say:

         union reply_body switch (reply_stat stat) {
         case MSG_ACCEPTED:
            accepted_reply areply;
         case MSG_DENIED:
            rejected_reply rreply;
         };

Notes:

The XDR grammar doesn't allow stating this:

union type_name switch (...) { ...} member_name;

You only have these two forms:

union type_name switch (...) { ...};
union switch (...) { ...} member_name;

Status: Rejected (1)

RFC 5531, "RPC: Remote Procedure Call Protocol Specification Version 2", May 2009

Note: This RFC has been updated by RFC 9289

Source of RFC: nfsv4 (wit)

Errata ID: 4099
Status: Rejected
Type: Technical
Publication Format(s) : TEXT

Reported By: anatoly techtonik
Date Reported: 2014-09-05
Rejected by: Martin Stiemerling
Date Rejected: 2015-12-16

Throughout the document, when it says:

This document describes the Open Network Computing (ONC) Remote
Procedure Call (RPC) version 2 protocol as it is currently deployed
and accepted.

Notes:

The document doesn't describe UDP and TCP port number 111, which is used to make initial connection for RCP services discovery and port mapping. Port mapping is an essential part of protocol without which ONC RPC services can't work.

RFC doesn't describe 111 is hardcoded number or can be changed. Doesn't say that servers typically listen on both UDP and TCP 111 (Linux nfs-kernel-server).
--VERIFIER NOTES--
This RFC is solely describing the RPC protocol and not the underlying transport that might be used.

Report New Errata



Advanced Search