RFC 1359: Connecting to the Internet - What Connecting Institutions Should Anticipate
In plain English — editorial summary, not part of the RFC
This FYI RFC outlines the major issues an institution should consider in the decision and implementation of a campus connection to the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1359
- Published
- August 1992
- Authors
- ACM SIGUCCS
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 25
- Also known as
- FYI16
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2060Internet Message Access Protocol - Version 4rev1Obsoleted
December 1996
- RFC 2061IMAP4 Compatibility with IMAP2bisCurrent
December 1996
- RFC 2086IMAP4 ACL extensionObsoleted
January 1997
- RFC 2087IMAP4 QUOTA extensionObsoleted
January 1997
- RFC 2088IMAP4 non-synchronizing literalsObsoleted
January 1997
- RFC 2095IMAP/POP AUTHorize Extension for Simple Challenge/ResponseObsoleted
January 1997
- RFC 2180IMAP4 Multi-Accessed Mailbox PracticeCurrent
July 1997
- RFC 2192IMAP URL SchemeObsoleted
September 1997
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?