RFC 7948: Internet Exchange BGP Route Server Operations
In plain English — editorial summary, not part of the RFC
The popularity of Internet Exchange Points (IXPs) brings new challenges to interconnecting networks. While bilateral External BGP (EBGP) sessions between exchange participants were historically the most common means of exchanging reachability information over an IXP, the overhead associated with this interconnection method causes serious operational and administrative scaling problems for IXP participants. Multilateral interconnection using Internet route servers can dramatically reduce the administrative and operational overhead associated with connecting to IXPs; in some cases, route servers are used by IXP participants as their preferred means of exchanging routing information. This document describes operational considerations for multilateral interconnections at IXPs.
Document record
- Document ID
- RFC7948
- Published
- September 2016
- Authors
- N. Hilliard; E. Jasinska; R. Raszuk; N. Bakker
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7854BGP Monitoring Protocol (BMP)Updated
June 2016
- RFC 9736The BGP Monitoring Protocol (BMP) Peer Up Message NamespaceCurrent
March 2025
- RFC 9972Advanced BGP Monitoring Protocol (BMP) Statistics TypesCurrent
May 2026
- RFC 7950The YANG 1.1 Data Modeling LanguageUpdated
August 2016
- RFC 7951JSON Encoding of Data Modeled with YANGCurrent
August 2016
- RFC 7944Diameter Routing Message PriorityCurrent
August 2016
- RFC 7952Defining and Using Metadata with YANGCurrent
August 2016
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
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?