Reclassification of RFC 1863 to Historic (RFC4223)
Original Publication Date: 2005-Oct-01
Included in the Prior Art Database: 2005-Oct-04
Internet Society Requests For Comment (RFCs)
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.
Network Working Group P.
Request for Comments: 4223 CSC/FUNET
Obsoletes: 1863 October 2005
Reclassification of RFC 1863 to Historic
Status of This Memo
provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright (C) The Internet Society (2005).
reclassifies RFC 1863, A BGP/IDRP Route Server alternative
to a full mesh routing, to Historic status. This memo also obsoletes
1. Reclassification of RFC 1863 to Historic
RFC 1863 
describes the use of route servers as an alternative to
BGP/IDRP full mesh routing.
In the context
of this document, the term "RFC 1863 route server" is
used to refer to a route server as specified in RFC 1863. Other uses
of the term "route server" are outside the scope of this document.
of RFC 1863 route servers do not exist and are not
used as an alternative to full mesh routing. Therefore, RFC 1863 is
reclassified to Historic status.
techniques that serve as an alternative to full mesh routing
include BGP Route Reflectors , BGP Confederedations , and the
use of private AS numbers. IDRP for IP has never been standardized
by the IETF and can be considered obsolete.
Other uses of
(non-RFC1863) route servers, rather than as an
alternative to full mesh routing as described by RFC 1863, are
expected to continue to be used for multiple purposes, but are out of
the scope of this memo.
Informational [Page 1]
RFC 4223 Reclassification of RFC 1863 to Historic October 2005
John Scudder, Paul Jakma, and Yakov Rekhter provided
useful background information for the creation of this memo. Scott
Bradner, Jeffrey Haas, and Yakov Rekhter provided substantial
feedback during the WG last call.
3. Security Considerations
Reclassifying RFC 1863 has no security considerations.
4.1. Normative References
 Haskin, D., "A BGP/IDRP Route Server
alternative to a full mesh
routing", RFC 1863, October 1995.
4.2. Informative References
 Bates, T., Chandra, R., and E. Chen,
"BGP Route Reflection - An
Alternative to Full Mesh IBGP", RFC 2796, April 2000.
 Traina, P., McPherson, D., and J. Scudder,