RFC 1787: Routing in a Multi-provider Internet
In plain English — editorial summary, not part of the RFC
This document presents some of the issues related to network layer routing in a multi-provider Internet, and specifically to the unicast routing. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1787
- Published
- April 1995
- Authors
- Y. Rekhter
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1788ICMP Domain Name MessagesObsoleted
April 1995
- RFC 1814Unique Addresses are GoodCurrent
June 1995
- RFC 1753IPng Technical Requirements Of the Nimrod Routing and Addressing ArchitectureCurrent
December 1994
- RFC 1822A Grant of Rights to Use a Specific IBM patent with PhoturisCurrent
August 1995
- RFC 1744Observations on the Management of the Internet Address SpaceCurrent
December 1994
- RFC 1726Technical Criteria for Choosing IP The Next Generation (IPng)Current
December 1994
- RFC 1719A Direction for IPngCurrent
December 1994
- RFC 1858Security Considerations for IP Fragment FilteringUpdated
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?