RFC 1403: BGP 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 Routers (ASBR) that will run BGP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1403
- Published
- January 1993
- Authors
- K. Varadhan
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 17
- Also known as
- —
- Obsoletes:
- RFC 1364
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3166Request to Move RFC 1403 to Historic StatusCurrent
August 2001
- RFC 2385Protection of BGP Sessions via the TCP MD5 Signature OptionObsoleted
August 1998
- RFC 2439BGP Route Flap DampingCurrent
November 1998
- RFC 2545Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain RoutingCurrent
March 1999
- RFC 2796BGP Route Reflection - An Alternative to Full Mesh IBGPObsoleted
April 2000
- RFC 2918Route Refresh Capability for BGP-4Updated
September 2000
- RFC 3065Autonomous System Confederations for BGPObsoleted
February 2001
- RFC 3107Carrying Label Information in BGP-4Obsoleted
May 2001
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?