Sign in
Version 5.13.0, 2015-03-25
Report a bug

ONC Remote Procedure Call (oncrpc)
(concluded WG)

Note: The data for concluded WGs is occasionally incorrect.
Name: ONC Remote Procedure Call
Area:Transport Area (tsv)
State: Concluded
Charter: charter-ietf-oncrpc-01 (Approved)
Chairs: Stephen Nahm <>
Theodore Ts'o <>
Mailing List

Charter for Working Group

The Open Network Computing Remote Procedure Call Working Group was
originally formed to update the RFCs that describe ONC RPC to reflect
the current state of the deployed and accepted technology, and submit
them for Internet standardization. RFCs have been submitted for the
three core ONC technologies: RPC (RFC1831), RPC Binding (RFC 1833)
and XDR (RFC1832).

During this work, IESG identified the area of security as requiring
improvement prior to standardizing the core RPC technologies (RPC and
RPC Binding). Therefore, the Working Group shall develop and define
a security mechanism for ONC RPC which shall, at the minimum, allow
for strong authentication of client and server principals. The core
RPC technologies will be unblocked from the standards track once
such a mechanism is approved as a Proposed Standard, provided
that its design does not require changes to the core RPC technologies.

The basis for the work will be the RPCSEC_GSS Protocol Specification,

The document editor will be Michael Eisler.


ONC RPC is a Remote Procedure Call technology that originated in Sun
Microsystems in the early 1980s. ONC RPC was modelled on Xerox's
Courier RPC protocols. It has been widely deployed on platforms from
most major workstation vendors. It has been implemented on MS-DOS,
Microsoft Windows, Microsoft Windows NT, Mac, VMS, MVS, and
practically all flavors of UNIX, among others. Sun Microsystems has
delegated change control for the ONC RPC protocols for the purposes
of making an Internet Standard to the IETF (see RFC 1790).


Post RPC: Remote Procedure Call Protocol Specification Version 2 (update of RFC 1057) as an Internet-Draft.
Post XDR: External Data Representation Standard (an update of RFC 1014) as an Internet-Draft.
Submit XDR document to IESG for consideration as a Proposed Standard.
Submit RPC document to IESG for consideration as a Proposed Standard.
Feb 1997
Submit strong security mechanism for ONC RPC to IESG for consideration as a Proposed Standard.
Mar 1997
Submit core RPC documents to IESG for consideration as Draft Standards.
Mar 1997
Conclude working group, leaving mailing list in place for pursuit of the subseqent standards stages.
Apr 1997
submit XDR to IESG for consideration as Internet Standards.
Aug 1997
Submit Strong security mechanism to IESG for consideration as a Draft Standard.
Jun 2000
Conduct final Interoperability tests
Mar 2001
Conduct full Interoperability tests for all NFSv4 features
Apr 2001
Submit RPC (RFC 1831), Binding Protocols for RPC (RFC 1833), and RFCSEC_GSS Protocol Specification (RFC 2203) to IESGtion (RFC 2203) to IESG
Apr 2001
Submit NFS version 4 to IESG with changes reflecting results of Interoperability tests for recycling as Proposed Standard
Nov 2001
Submit NFS version 4 to IESG for consideration as a Draft Standard.