RFC 4223: Reclassification of RFC 1863 to Historic
In plain English — editorial summary, not part of the RFC
This memo reclassifies RFC 1863, A BGP/IDRP Route Server alternative to a full mesh routing, to Historic status. This memo also obsoletes RFC 1863. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4223
- Published
- October 2005
- Authors
- P. Savola
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 3
- Also known as
- —
- Obsoletes:
- RFC 1863
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 1745BGP4/IDRP for IP---OSPF InteractionCurrent
December 1994
- RFC 3167Request to Move RFC 1745 to Historic StatusCurrent
August 2001
- RFC 1773Experience with the BGP-4 protocolCurrent
March 1995
- RFC 1656BGP-4 Protocol Document Roadmap and Implementation ExperienceObsoleted
July 1994
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 4456BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)Updated
April 2006
- RFC 2858Multiprotocol Extensions for BGP-4Obsoleted
June 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?