RFC 2755: Security Negotiation for WebNFS
In plain English — editorial summary, not part of the RFC
This document describes a protocol for a WebNFS client (RFC2054) to negotiate the desired security mechanism with a WebNFS server (RFC2055) before the WebNFS client falls back to the MOUNT v3 protocol (RFC1813). This document is provided so that people can write compatible implementations. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2755
- Published
- January 2000
- Authors
- A. Chiu; M. Eisler; B. Callaghan
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 3521Framework for Session Set-up with Media AuthorizationCurrent
April 2003
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
- RFC 5696Baseline Encoding and Transport of Pre-Congestion InformationObsoleted
November 2009
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
- RFC 7713Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and RequirementsCurrent
December 2015
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?