RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

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

Source of RFC: nfsv4 (tsv)

Errata ID: 4849

Status: Verified
Type: Editorial

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: Rejected (1)

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

Source of RFC: nfsv4 (tsv)

Errata ID: 4099

Status: Rejected
Type: Technical

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