Skip to content

Commit c297a8a

Browse files
committed
TLS for BGP
1 parent f6ac5e8 commit c297a8a

File tree

1 file changed

+34
-2
lines changed

1 file changed

+34
-2
lines changed

infra.rst

Lines changed: 34 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -112,9 +112,37 @@ algorithm). It also lacks dynamic key management and the ability to update the
112112
cryptographic algorithm, so it is now deprecated in favor of a more
113113
general TCP authentication option which is described in RFC 5925.
114114

115-
RFC 5925
115+
It might seem somewhat counter-intuitive that BGP does not currently run
116+
over TLS, given the maturity and widespread adoption of that
117+
technology today. The explanation for this comes down to a combination
118+
of factors including history, intertia, and the different operational
119+
model of running BGP versus connecting to a remote website. For
120+
example, BGP sessions often run between directly connected routers at
121+
a peering point or internet exchange points (IXPs) which allows for a
122+
simple TTL-based method to prevent spoofing. Privacy of BGP updates is
123+
considerably less important than autheniticity. And as we shall see,
124+
there is a lot more to establishing the authenticitiy of a BGP
125+
advertisement that just authenticating the messages from a peer.
126+
127+
When BGP was being
128+
developed in the 1980s and 1990s, TLS was still far in the future, and
129+
packet encryption and decryption operations were generally quite
130+
computationally expensive. So it made sense that the initial focus was
131+
on authenticating messages rather than providing the greater
132+
protection of encryption that TLS offers.
133+
134+
With this background, the idea of running BGP over TLS is an area of
135+
current research, and would offer potential benefits beyond simply
136+
adding privacy to BGP advertisements. Most notably, certificate
137+
management for TLS is now highly automated, which contrasts with the
138+
manual provisioning that must be performed when using MD5
139+
or TCP-based authentication for BGP. The paper below on secure
140+
transport for BGP outlines this approach and suggests further
141+
enhancements that might further improve the securiy of BGP. However,
142+
in terms of the current state of the Internet, the recommended best
143+
practice for BGP sessions (described in RFC 7454) does not extend to
144+
TLS.
116145

117-
RFC 7454
118146

119147
.. _reading_BGPTLS:
120148
.. admonition:: Further Reading
@@ -123,6 +151,10 @@ RFC 7454
123151
Bonaventure. `The Multiple Benefits of Secure Transport for BGP <https://conferences.sigcomm.org/co-next/2024/files/papers/p186.pdf/>`__.
124152
ACM Conext, December 2024.
125153

154+
J. Durand, I. Pepelnjak and G. Dorering. `BGP Operations and
155+
Security <https://www.rfc-editor.org/info/rfc7454>`__. RFC 7454,
156+
February 2015.
157+
126158
.. _reading_rpki:
127159
.. admonition:: Further Reading
128160

0 commit comments

Comments
 (0)