RFC 1397: Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol
In plain English — editorial summary, not part of the RFC
This document speficies the recommendation of the BGP Working Group on default route advertisement support in BGP2 [1] and BGP3 [2] versions of the Border Gateway Protocol. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1397
- Published
- January 1993
- Authors
- D. Haskin
- Status
- HISTORIC
- Stream
- IETF
- Area
- rtg
- Pages
- 2
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1164Application of the Border Gateway Protocol in the InternetObsoleted
June 1990
- RFC 1163Border Gateway Protocol (BGP)Obsoleted
June 1990
- 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?