Internet Exchange BGP Route Server
RFC 7947
Internet Engineering Task Force (IETF) E. Jasinska
Request for Comments: 7947 BigWave IT
Category: Standards Track N. Hilliard
ISSN: 2070-1721 INEX
R. Raszuk
Bloomberg LP
N. Bakker
Akamai Technologies B.V.
September 2016
Internet Exchange BGP Route Server
Abstract
This document outlines a specification for multilateral
interconnections at Internet Exchange Points (IXPs). Multilateral
interconnection is a method of exchanging routing information among
three or more External BGP (EBGP) speakers using a single
intermediate broker system, referred to as a route server. Route
servers are typically used on shared access media networks, such as
IXPs, to facilitate simplified interconnection among multiple
Internet routers.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7947.
Jasinska, et al. Standards Track [Page 1]
RFC 7947 IXP BGP Route Server September 2016
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction to Multilateral Interconnection . . . . . . . . 3
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3
2. Technical Considerations for Route Server Implementations . . 4
2.1. Client UPDATE Messages . . . . . . . . . . . . . . . . . 4
2.2. Attribute Transparency . . . . . . . . . . . . . . . . . 4
2.2.1. NEXT_HOP Attribute . . . . . . . . . . . . . . . . . 4
2.2.2. AS_PATH Attribute . . . . . . . . . . . . . . . . . . 5
2.2.2.1. Route Server AS_PATH Management . . . . . . . . . 5
2.2.2.2. Route Server client AS_PATH Management . . . . . 5
2.2.3. MULTI_EXIT_DISC Attribute . . . . . . . . . . . . . . 5
2.2.4. Communities Attributes . . . . . . . . . . . . . . . 5
2.3. Per-Client Policy Control in Multilateral Interconnection 6
2.3.1. Path Hiding on a Route Server . . . . . . . . . . . . 6
2.3.2. Mitigation of Path Hiding . . . . . . . . . . . . . . 7
2.3.2.1. Multiple Route Server RIBs . . . . . . . . . . . 7
2.3.2.2. Advertising Multiple Paths . . . . . . . . . . . 8
2.3.3. Implementation Suggestions . . . . . . . . . . . . . 9
3. Security Considerations . . . . . . . . . . . . . . . . . . . 9
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1. Normative References . . . . . . . . . . . . . . . . . . 10
4.2. Informative References . . . . . . . . . . . . . . . . . 10
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
Jasinska, et al. Standards Track [Page 2]
RFC 7947 IXP BGP Route Server September 2016
1. Introduction to Multilateral Interconnection
Internet Exchange Points (IXPs) provide IP data interconnection
facilities for their participants, typically using shared Layer 2
networking media such as Ethernet. The Border Gateway Protocol (BGP)
[RFC4271], an inter-Autonomous System (inter-AS) routing protocol, is
commonly used to facilitate exchange of network reachability
information over such media.
While bilateral EBGP sessions between exchange participants were
Show full document text