From: Marlin Cremers Date: Fri, 14 Jan 2022 17:50:22 +0000 (+0100) Subject: docs(bgp): refer to rfc9136 instead of draft X-Git-Tag: base_8.2~47^2 X-Git-Url: https://git.puffer.fish/?a=commitdiff_plain;h=refs%2Fpull%2F10342%2Fhead;p=mirror%2Ffrr.git docs(bgp): refer to rfc9136 instead of draft Instead of referring to the draft of IP Prefix Advertisement in Ethernet VPN let's point to the recently published RFC9136. Signed-off-by: Marlin Cremers --- diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst index ada14b4fa1..0fb5fa8482 100644 --- a/doc/user/bgp.rst +++ b/doc/user/bgp.rst @@ -2832,9 +2832,8 @@ at the same time. EVPN Overlay Index Gateway IP ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Draft https://tools.ietf.org/html/draft-ietf-bess-evpn-prefix-advertisement-11 -explains the use of overlay indexes for recursive route resolution for EVPN -type-5 route. +RFC https://datatracker.ietf.org/doc/html/rfc9136 explains the use of overlay +indexes for recursive route resolution for EVPN type-5 route. We support gateway IP overlay index. A gateway IP, advertised with EVPN prefix route, is used to find an EVPN MAC/IP