RFC 1745: BGP4/IDRP for IP---OSPF Interaction
In plain English — editorial summary, not part of the RFC
This memo defines the various criteria to be used when designing an Autonomous System Border Router (ASBR) that will run either BGP4 or IDRP for IP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1745
- Published
- December 1994
- Authors
- K. Varadhan; S. Hares; Y. Rekhter
- Status
- HISTORIC
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3167Request to Move RFC 1745 to Historic StatusCurrent
August 2001
- RFC 1364BGP OSPF InteractionObsoleted
September 1992
- RFC 1587The OSPF NSSA OptionObsoleted
March 1994
- RFC 1850OSPF Version 2 Management Information BaseObsoleted
November 1995
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
October 1995
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 2178OSPF Version 2Obsoleted
July 1997
- RFC 4223Reclassification of RFC 1863 to HistoricCurrent
October 2005
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?