RFC 985: Requirements for Internet gateways - draft
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1009.
Current document in this lineage: RFC 1812 — Requirements for IP Version 4 Routers
In plain English — editorial summary, not part of the RFC
This RFC summarizes the requirements for gateways to be used on networks supporting the DARPA Internet protocols. While it applies specifically to National Science Foundation research programs, the requirements are stated in a general context and are believed applicable throughout the Internet community. The purpose of this document is to present guidance for vendors offering products that might be used or adapted for use in an Internet application. It enumerates the protocols required and gives references to RFCs and other documents describing the current specification.
Document record
- Document ID
- RFC985
- Published
- May 1986
- Authors
- National Science Foundation; Network Technical Advisory Group
- Status
- UNKNOWN
- Stream
- Legacy
- Area
- —
- Pages
- 23
- Also known as
- —
- Obsoleted by:
- RFC 1009
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 985 (1986)
- RFC 1009 (1987)
- RFC 1716 (1994)
- RFC 1812 (1995) ✓
Read the full history of Requirements for IP Version 4 Routers →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 988Host extensions for IP multicastingObsoleted
July 1986
- RFC 1087Ethics and the InternetCurrent
January 1989
- RFC 1290There's Gold in them thar Networks! or Searching for Treasure in all the Wrong PlacesObsoleted
December 1991
- RFC 1335A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space ExhaustionCurrent
May 1992
- RFC 1358Charter of the Internet Architecture Board (IAB)Obsoleted
August 1992
- RFC 1359Connecting to the Internet - What Connecting Institutions Should AnticipateCurrent
August 1992
- RFC 1636Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994Current
June 1994
- RFC 1641Using Unicode with MIMECurrent
July 1994
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?