RFC 1716: Towards Requirements for IP Routers
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1812.
Current document in this lineage: RFC 1812 — Requirements for IP Version 4 Routers
In plain English — editorial summary, not part of the RFC
The goal of this work is to replace RFC-1009, Requirements for Internet Gateways ([INTRO:1]) with a new document. It defines and discusses requirements for devices which perform the network layer forwarding function of the Internet protocol suite. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1716
- Published
- November 1994
- Authors
- P. Almquist; F. Kastenholz
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 192
- Also known as
- —
- Obsoleted by:
- RFC 1812
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 1745BGP4/IDRP for IP---OSPF InteractionCurrent
December 1994
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 2588IP Multicast and FirewallsCurrent
May 1999
- RFC 2871A Framework for Telephony Routing over IPCurrent
June 2000
- RFC 1773Experience with the BGP-4 protocolCurrent
March 1995
- RFC 1656BGP-4 Protocol Document Roadmap and Implementation ExperienceObsoleted
July 1994
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
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?