RFC 1965: Autonomous System Confederations for BGP
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3065.
Current document in this lineage: RFC 5065 — Autonomous System Confederations for BGP
In plain English — editorial summary, not part of the RFC
This document describes an extension to BGP which may be used to create a confederation of autonomous systems which is represented as one single autonomous system to BGP peers external to the confederation. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC1965
- Published
- June 1996
- Authors
- P. Traina
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 3065
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1965 (1996)
- RFC 3065 (2001)
- RFC 5065 (2007) ✓
Read the full history of Autonomous System Confederations for BGP →
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 1966BGP Route Reflection An alternative to full mesh IBGPObsoleted
June 1996
- RFC 1997BGP Communities AttributeUpdated
August 1996
- RFC 1998An Application of the BGP Community Attribute in Multi-home RoutingCurrent
August 1996
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
October 1995
- RFC 1773Experience with the BGP-4 protocolCurrent
March 1995
- RFC 1745BGP4/IDRP for IP---OSPF InteractionCurrent
December 1994
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
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?