RFC 2695: Authentication Mechanisms for ONC RPC
In plain English — editorial summary, not part of the RFC
This document describes two authentication mechanisms created by Sun Microsystems that are commonly used in conjunction with the ONC Remote Procedure Call (ONC RPC Version 2) protocol. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2695
- Published
- September 1999
- Authors
- A. Chiu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2203RPCSEC_GSS Protocol SpecificationUpdated
September 1997
- RFC 1833Binding Protocols for ONC RPC Version 2Updated
August 1995
- RFC 1832XDR: External Data Representation StandardObsoleted
August 1995
- RFC 1831RPC: Remote Procedure Call Protocol Specification Version 2Obsoleted
August 1995
- RFC 2378The CCSO Nameserver (Ph) ArchitectureCurrent
September 1998
- RFC 4139Requirements for Generalized MPLS (GMPLS) Signaling Usage and Extensions for Automatically Switched Optical Network (ASON)Current
July 2005
- RFC 7840A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) ProtocolCurrent
May 2016
- RFC 8147Next-Generation Pan-European eCallCurrent
May 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?