RFC 1746: Ways to Define User Expectations
In plain English — editorial summary, not part of the RFC
This paper covers basic fundamentals that must be understood when one defines, interprets, or implements methods to control user expectations on or over the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1746
- Published
- December 1994
- Authors
- B. Manning; D. Perkins
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- usv
- Pages
- 18
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1729Using the Z39.50 Information Retrieval ProtocolCurrent
December 1994
- RFC 1728Resource TranspondersCurrent
December 1994
- RFC 1727A Vision of an Integrated Internet Information ServiceCurrent
December 1994
- RFC 1709K-12 Internetworking GuidelinesCurrent
November 1994
- RFC 1689A Status Report on Networked Information Retrieval: Tools and GroupsCurrent
August 1994
- RFC 1834Whois and Network Information Lookup Service, Whois++Current
August 1995
- RFC 1835Architecture of the WHOIS++ serviceCurrent
August 1995
- RFC 1855Netiquette GuidelinesCurrent
October 1995
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?