RFC 1164: Application of the Border Gateway Protocol in the Internet
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1268.
Current document in this lineage: RFC 1772 — Application of the Border Gateway Protocol in the Internet
In plain English — editorial summary, not part of the RFC
This RFC, together with its companion RFC-1163, "A Border Gateway Protocol (BGP)", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1164
- Published
- June 1990
- Authors
- J.C. Honig; D. Katz; M. Mathis; Y. Rekhter; J.Y. Yu
- Status
- HISTORIC
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
- Obsoleted by:
- RFC 1268
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 1164 (1990)
- RFC 1268 (1991)
- RFC 1655 (1994)
- RFC 1772 (1995) ✓
Read the full history of Application of the Border Gateway Protocol in the Internet →
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 1163Border Gateway Protocol (BGP)Obsoleted
June 1990
- RFC 1397Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway ProtocolCurrent
January 1993
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 2385Protection of BGP Sessions via the TCP MD5 Signature OptionObsoleted
August 1998
- RFC 2439BGP Route Flap DampingCurrent
November 1998
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 2796BGP Route Reflection - An Alternative to Full Mesh IBGPObsoleted
April 2000
- RFC 2918Route Refresh Capability for BGP-4Updated
September 2000
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?