doc/user/overview.rst

   1 .. _overview:
   2
   3 ********
   4 Overview
   5 ********
   6
   7 `FRR`_ is a fully featured, high performance, free software IP routing suite.
   8
   9 FRR implements all standard routing protocols such as BGP, RIP, OSPF, IS-IS and
  10 more (see :ref:`feature-matrix`), as well as many of their extensions.
  11
  12 FRR is a high performance suite written primarily in C. It can easily handle
  13 full Internet routing tables and is suitable for use on hardware ranging from
  14 cheap SBCs to commercial grade routers. It is actively used in production by
  15 hundreds of companies, universities, research labs and governments.
  16
  17 FRR is distributed under GPLv2, with development modeled after the Linux
  18 kernel. Anyone may contribute features, bug fixes, tools, documentation
  19 updates, or anything else.
  20
  21 FRR is a fork of `Quagga <http://www.quagga.net/>`_.
  22
  23 .. _how-to-get-frr:
  24
  25 How to get FRR
  26 ==============
  27
  28 The official FRR website is located at |PACKAGE_URL| and contains further
  29 information, as well as links to additional resources.
  30
  31 Several distributions provide packages for FRR. Check your distribution's
  32 repositories to find out if a suitable version is available.
  33
  34 Up-to-date Debian & Redhat packages are available at https://deb.frrouting.org/
  35 & https://rpm.frrouting.org/ respectively.
  36
  37 For instructions on installing from source, refer to the
  38 `developer documentation <http://docs.frrouting.org/projects/dev-guide/en/latest/>`_.
  39
  40
  41 .. _about-frr:
  42
  43 About FRR
  44 =========
  45
  46 FRR provides IP routing services. Its role in a networking stack is to exchange
  47 routing information with other routers, make routing and policy decisions, and
  48 inform other layers of these decisions. In the most common scenario, FRR
  49 installs routing decisions into the OS kernel, allowing the kernel networking
  50 stack to make the corresponding forwarding decisions.
  51
  52 In addition to dynamic routing FRR supports the full range of L3 configuration,
  53 including static routes, addresses, router advertisements etc. It has some
  54 light L2 functionality as well, but this is mostly left to the platform. This
  55 makes it suitable for deployments ranging from small home networks with static
  56 routes to Internet exchanges running full Internet tables.
  57
  58 FRR runs on all modern \*NIX operating systems, including Linux and the BSDs.
  59 Feature support varies by platform; see the :ref:`feature-matrix`.
  60
  61
  62 System Architecture
  63 -------------------
  64
  65 .. index:: System architecture
  66 .. index:: Software architecture
  67 .. index:: Software internals
  68
  69 Traditional routing software is made as a one process program which provides
  70 all of the routing protocol functionalities. FRR takes a different approach.
  71 FRR is a suite of daemons that work together to build the routing table. Each
  72 major protocol is implemented in its own daemon, and these daemons talk to a
  73 middleman daemon (*zebra*), which is responsible for coordinating routing
  74 decisions and talking to the dataplane.
  75
  76 This architecture allows for high resiliency, since an error, crash or exploit
  77 in one protocol daemon will generally not affect the others. It is also
  78 flexible and extensible since the modularity makes it easy to implement new
  79 protocols and tie them into the suite. Additionally, each daemon implements a
  80 plugin system allowing new functionality to be loaded at runtime.
  81
  82 An illustration of the large scale architecture is given below.
  83
  84 ::
  85
  86    +----+  +----+  +-----+  +----+  +----+  +----+  +-----+
  87    |bgpd|  |ripd|  |ospfd|  |ldpd|  |pbrd|  |pimd|  |.....|
  88    +----+  +----+  +-----+  +----+  +----+  +----+  +-----+
  89         |       |        |       |       |       |        |
  90    +----v-------v--------v-------v-------v-------v--------v
  91    |                                                      |
  92    |                         Zebra                        |
  93    |                                                      |
  94    +------------------------------------------------------+
  95           |                    |                   |
  96           |                    |                   |
  97    +------v------+   +---------v--------+   +------v------+
  98    |             |   |                  |   |             |
  99    | *NIX Kernel |   | Remote dataplane |   | ........... |
 100    |             |   |                  |   |             |
 101    +-------------+   +------------------+   +-------------+
 102
 103
 104 All of the FRR daemons can be managed through a single integrated user
 105 interface shell called *vtysh*. *vtysh* connects to each daemon through a UNIX
 106 domain socket and then works as a proxy for user input. In addition to a
 107 unified frontend, *vtysh* also provides the ability to configure all the
 108 daemons using a single configuration file through the integrated configuration
 109 mode. This avoids the overhead of maintaining a separate configuration file for
 110 each daemon.
 111
 112 FRR is currently currently implementing a new internal configuration system
 113 based on YANG data models. When this work is completed, FRR will be a fully
 114 programmable routing stack.
 115
 116
 117 .. _supported-platforms:
 118
 119 Supported Platforms
 120 -------------------
 121
 122 .. index:: Supported platforms
 123 .. index:: FRR on other systems
 124 .. index:: Compatibility with other systems
 125 .. index:: Operating systems that support FRR
 126
 127 Currently FRR supports GNU/Linux and BSD. Porting FRR to other platforms is not
 128 too difficult as platform dependent code should be mostly limited to the
 129 *Zebra* daemon. Protocol daemons are largely platform independent. Please let
 130 us know if you can get FRR to run on a platform which is not listed below:
 131
 132 - GNU/Linux
 133 - FreeBSD
 134 - NetBSD
 135 - OpenBSD
 136
 137 Versions of these platforms that are older than around 2 years from the point
 138 of their original release (in case of GNU/Linux, this is since the kernel's
 139 release on https://kernel.org/) may need some work. Similarly, the following
 140 platforms may work with some effort:
 141
 142 - MacOS
 143
 144 Recent versions of the following compilers are well tested:
 145
 146 - GNU's GCC
 147 - LLVM's Clang
 148 - Intel's ICC
 149
 150 .. _unsupported-platforms:
 151
 152 UnSupported Platforms
 153 ---------------------
 154
 155 .. index:: UnSupported platforms
 156
 157 In General if the platform you are attempting to use is not listed above then
 158 FRR does not support being run on that platform.  The only caveat here is that
 159 version 7.5 and before Solaris was supported in a limited fashion.
 160
 161 .. _feature-matrix:
 162
 163 Feature Matrix
 164 ^^^^^^^^^^^^^^
 165
 166 The following table lists all protocols cross-referenced to all operating
 167 systems that have at least CI build tests. Note that for features, only
 168 features with system dependencies are included here; if you don't see the
 169 feature you're interested in, it should be supported on your platform.
 170
 171 .. role:: mark
 172
 173 .. comment - the :mark:`X` pieces mesh with a little bit of JavaScript and
 174    CSS in _static/overrides.{js,css} respectively.  The JS code looks at the
 175    presence of the 'Y' 'N' '≥' '†' or 'CP' strings.  This seemed to be the
 176    best / least intrusive way of getting a nice table in HTML.  The table
 177    will look somewhat shoddy on other sphinx targets like PDF or info (but
 178    should still be readable.)
 179
 180 +-----------------------------------+----------------+--------------+------------+------------+
 181 | Daemon / Feature                  | Linux          | OpenBSD      | FreeBSD    | NetBSD     |
 182 +===================================+================+==============+============+============+
 183 | **FRR Core**                      |                |              |            |            |
 184 +-----------------------------------+----------------+--------------+------------+------------+
 185 | `zebra`                           | :mark:`Y`      | :mark:`Y`    | :mark:`Y`  | :mark:`Y`  |
 186 +-----------------------------------+----------------+--------------+------------+------------+
 187 |    VRF                            | :mark:`≥4.8`   | :mark:`N`    | :mark:`N`  | :mark:`N`  |
 188 +-----------------------------------+----------------+--------------+------------+------------+
 189 |    MPLS                           | :mark:`≥4.5`   | :mark:`Y`    | :mark:`N`  | :mark:`N`  |
 190 +-----------------------------------+----------------+--------------+------------+------------+
 191 | `pbrd` (Policy Routing)           | :mark:`Y`      | :mark:`N`    | :mark:`N`  | :mark:`N`  |
 192 +-----------------------------------+----------------+--------------+------------+------------+
 193 | **WAN / Carrier protocols**       |                |              |            |            |
 194 +-----------------------------------+----------------+--------------+------------+------------+
 195 | `bgpd` (BGP)                      | :mark:`Y`      | :mark:`Y`    | :mark:`Y`  | :mark:`Y`  |
 196 +-----------------------------------+----------------+--------------+------------+------------+
 197 |    VRF / L3VPN                    | :mark:`≥4.8`   | :mark:`CP`   | :mark:`CP` | :mark:`CP` |
 198 |                                   | :mark:`†4.3`   |              |            |            |
 199 +-----------------------------------+----------------+--------------+------------+------------+
 200 |    EVPN                           | :mark:`≥4.18`  | :mark:`CP`   | :mark:`CP` | :mark:`CP` |
 201 |                                   | :mark:`†4.9`   |              |            |            |
 202 +-----------------------------------+----------------+--------------+------------+------------+
 203 |    VNC (Virtual Network Control)  | :mark:`CP`     | :mark:`CP`   | :mark:`CP` | :mark:`CP` |
 204 +-----------------------------------+----------------+--------------+------------+------------+
 205 |    Flowspec                       | :mark:`CP`     | :mark:`CP`   | :mark:`CP` | :mark:`CP` |
 206 +-----------------------------------+----------------+--------------+------------+------------+
 207 | `ldpd` (LDP)                      | :mark:`≥4.5`   | :mark:`Y`    | :mark:`N`  | :mark:`N`  |
 208 +-----------------------------------+----------------+--------------+------------+------------+
 209 |    VPWS / PW                      | :mark:`N`      | :mark:`≥5.8` | :mark:`N`  | :mark:`N`  |
 210 +-----------------------------------+----------------+--------------+------------+------------+
 211 |    VPLS                           | :mark:`N`      | :mark:`≥5.8` | :mark:`N`  | :mark:`N`  |
 212 +-----------------------------------+----------------+--------------+------------+------------+
 213 | `nhrpd` (NHRP)                    | :mark:`Y`      | :mark:`N`    | :mark:`N`  | :mark:`N`  |
 214 +-----------------------------------+----------------+--------------+------------+------------+
 215 | **Link-State Routing**            |                |              |            |            |
 216 +-----------------------------------+----------------+--------------+------------+------------+
 217 | `ospfd` (OSPFv2)                  | :mark:`Y`      | :mark:`Y`    | :mark:`Y`  | :mark:`Y`  |
 218 +-----------------------------------+----------------+--------------+------------+------------+
 219 |    Segment Routing                | :mark:`≥4.12`  | :mark:`N`    | :mark:`N`  | :mark:`N`  |
 220 +-----------------------------------+----------------+--------------+------------+------------+
 221 | `ospf6d` (OSPFv3)                 | :mark:`Y`      | :mark:`Y`    | :mark:`Y`  | :mark:`Y`  |
 222 +-----------------------------------+----------------+--------------+------------+------------+
 223 | `isisd` (IS-IS)                   | :mark:`Y`      | :mark:`Y`    | :mark:`Y`  | :mark:`Y`  |
 224 +-----------------------------------+----------------+--------------+------------+------------+
 225 | **Distance-Vector Routing**       |                |              |            |            |
 226 +-----------------------------------+----------------+--------------+------------+------------+
 227 | `ripd` (RIPv2)                    | :mark:`Y`      | :mark:`Y`    | :mark:`Y`  | :mark:`Y`  |
 228 +-----------------------------------+----------------+--------------+------------+------------+
 229 | `ripngd` (RIPng)                  | :mark:`Y`      | :mark:`Y`    | :mark:`Y`  | :mark:`Y`  |
 230 +-----------------------------------+----------------+--------------+------------+------------+
 231 | `babeld` (BABEL)                  | :mark:`Y`      | :mark:`Y`    | :mark:`Y`  | :mark:`Y`  |
 232 +-----------------------------------+----------------+--------------+------------+------------+
 233 | `eigrpd` (EIGRP)                  | :mark:`Y`      | :mark:`Y`    | :mark:`Y`  | :mark:`Y`  |
 234 +-----------------------------------+----------------+--------------+------------+------------+
 235 | **Multicast Routing**             |                |              |            |            |
 236 +-----------------------------------+----------------+--------------+------------+------------+
 237 | `pimd` (PIM)                      | :mark:`≥4.18`  | :mark:`N`    | :mark:`Y`  | :mark:`Y`  |
 238 +-----------------------------------+----------------+--------------+------------+------------+
 239 |    SSM (Source Specific)          | :mark:`Y`      | :mark:`N`    | :mark:`Y`  | :mark:`Y`  |
 240 +-----------------------------------+----------------+--------------+------------+------------+
 241 |    ASM (Any Source)               | :mark:`Y`      | :mark:`N`    | :mark:`N`  | :mark:`N`  |
 242 +-----------------------------------+----------------+--------------+------------+------------+
 243 |    EVPN BUM Forwarding            | :mark:`≥5.0`   | :mark:`N`    | :mark:`N`  | :mark:`N`  |
 244 +-----------------------------------+----------------+--------------+------------+------------+
 245 | `vrrpd` (VRRP)                    | :mark:`≥5.1`   | :mark:`N`    | :mark:`N`  | :mark:`N`  |
 246 +-----------------------------------+----------------+--------------+------------+------------+
 247
 248 The indicators have the following semantics:
 249
 250 * :mark:`Y` - daemon/feature fully functional
 251 * :mark:`≥X.X` - fully functional with kernel version X.X or newer
 252 * :mark:`†X.X` - restricted functionality or impaired performance with kernel version X.X or newer
 253 * :mark:`CP` - control plane only (i.e. BGP route server / route reflector)
 254 * :mark:`N` - daemon/feature not supported by operating system
 255
 256
 257 Known Kernel Issues
 258 -------------------
 259
 260 - Linux < 4.11
 261
 262   v6 Route Replacement - Linux kernels before 4.11 can cause issues with v6
 263   route deletion when you have ECMP routes installed into the kernel. This
 264   especially becomes apparent if the route is being transformed from one ECMP
 265   path to another.
 266
 267 .. _supported-rfcs:
 268
 269 Supported RFCs
 270 --------------
 271
 272 FRR implements the following RFCs:
 273
 274 .. note:: This list is incomplete.
 275
 276 BGP
 277 ----
 278
 279 - :rfc:`1771`
 280   :t:`A Border Gateway Protocol 4 (BGP-4). Y. Rekhter & T. Li. March 1995.`
 281 - :rfc:`1965`
 282   :t:`Autonomous System Confederations for BGP. P. Traina. June 1996.`
 283 - :rfc:`1997`
 284   :t:`BGP Communities Attribute. R. Chandra, P. Traina & T. Li. August 1996.`
 285 - :rfc:`2439`
 286   :t:`BGP Route Flap Damping. C. Villamizar, R. Chandra, R. Govindan. November 1998.`
 287 - :rfc:`2545`
 288   :t:`Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing. P.
 289   Marques, F. Dupont. March 1999.`
 290 - :rfc:`2796`
 291   :t:`BGP Route Reflection An alternative to full mesh IBGP. T. Bates & R. Chandrasekeran. June 1996.`
 292 - :rfc:`2842`
 293   :t:`Capabilities Advertisement with BGP-4. R. Chandra, J. Scudder. May 2000.`
 294 - :rfc:`2858`
 295   :t:`Multiprotocol Extensions for BGP-4. T. Bates, Y. Rekhter, R. Chandra, D.`
 296 - :rfc:`3107`
 297   :t:`Carrying Label Information in BGP-4. Y. Rekhter & E. Rosen. May 2001.`
 298 - :rfc:`3765`
 299   :t:`NOPEER Community for Border Gateway Protocol (BGP) Route Scope Control. G.Huston, April 2001.`
 300 - :rfc:`4271`
 301   :t:`A Border Gateway Protocol 4 (BGP-4). Updates RFC1771. Y. Rekhter, T. Li & S. Hares. January 2006.`
 302 - :rfc:`4364`
 303   :t:`BGP/MPLS IP Virtual Private Networks (VPNs). Y. Rekhter. Feb 2006.`
 304 - :rfc:`4486`
 305   :t:`Subcodes for BGP Cease Notification Message. E. Chen, V. Gillet. April 2006.`
 306 - :rfc:`4659`
 307   :t:`BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN. J. De Clercq, D. Ooms, M. Carugi, F. Le Faucheur. September 2006.`
 308 - :rfc:`4893`
 309   :t:`BGP Support for Four-octet AS Number Space. Q. Vohra, E. Chen May 2007.`
 310 - :rfc:`5004`
 311   :t:`Avoid BGP Best Path Transitions from One External to Another. E. Chen & S. Sangli. September 2007 (Partial support).`
 312 - :rfc:`5082`
 313   :t:`The Generalized TTL Security Mechanism (GTSM). V. Gill, J. Heasley, D. Meyer, P. Savola, C. Pingnataro. October 2007.`
 314 - :rfc:`5575`
 315   :t:`Dissemination of Flow Specification Rules. P. Marques, N. Sheth, R. Raszuk, B. Greene, J. Mauch, D. McPherson. August 2009`
 316 - :rfc:`6286`
 317   :t:`Autonomous-System-Wide Unique BGP Identifier for BGP-4. E. Chen, J. Yuan, June 2011.`
 318 - :rfc:`6608`
 319   :t:`Subcodes for BGP Finite State Machine Error. J. Dong, M. Chen, Huawei Technologies, A. Suryanarayana, Cisco Systems. May 2012.`
 320 - :rfc:`6810`
 321   :t:`The Resource Public Key Infrastructure (RPKI) to Router Protocol. R. Bush, R. Austein. January 2013.`
 322 - :rfc:`6811`
 323   :t:`BGP Prefix Origin Validation. P. Mohapatra, J. Scudder, D. Ward, R. Bush, R. Austein. January 2013.`
 324 - :rfc:`7606`
 325   :t:`Revised Error Handling for BGP UPDATE Messages. E. Chen, J. Scudder, P. Mohapatra, K. Patel. August 2015.`
 326 - :rfc:`7607`
 327   :t:`Codification of AS 0 Processing. W. Kumari, R. Bush, H. Schiller, K. Patel. August 2015.`
 328 - :rfc:`7611`
 329   :t:`BGP ACCEPT_OWN Community Attribute. J. Uttaro, P. Mohapatra, D. Smith, R. Raszuk, J. Scudder. August 2015.`
 330 - :rfc:`7999`
 331   :t:`BLACKHOLE Community. T. King, C. Dietzel, J. Snijders, G. Doering, G. Hankins. Oct 2016.`
 332 - :rfc:`8092`
 333   :t:`BGP Large Communities Attribute. J. Heitz, Ed., J. Snijders, Ed, K. Patel, I. Bagdonas, N. Hilliard. February 2017`
 334 - :rfc:`8195`
 335   :t:`Use of BGP Large Communities. J. Snijders, J. Heasley, M. Schmidt, June 2017`
 336 - :rfc:`8203`
 337   :t:`BGP Administrative Shutdown Communication. J. Snijders, J. Heitz, J. Scudder. July 2017.`
 338 - :rfc:`8212`
 339   :t:`Default External BGP (EBGP) Route Propagation Behavior without Policies. J. Mauch, J. Snijders, G. Hankins. July 2017`
 340 - :rfc:`8277`
 341   :t:`Using BGP to Bind MPLS Labels to Address Prefixes. E. Rosen. October 2017`
 342
 343
 344 OSPF
 345 ----
 346
 347 - :rfc:`2328`
 348   :t:`OSPF Version 2. J. Moy. April 1998.`
 349 - :rfc:`2370`
 350   :t:`The OSPF Opaque LSA Option R. Coltun. July 1998.`
 351 - :rfc:`3101`
 352   :t:`The OSPF Not-So-Stubby Area (NSSA) Option P. Murphy. January 2003.`
 353 - :rfc:`2740`
 354   :t:`OSPF for IPv6. R. Coltun, D. Ferguson, J. Moy. December 1999.`
 355 - :rfc:`3137`
 356   :t:`OSPF Stub Router Advertisement, A. Retana, L. Nguyen, R. White, A. Zinin, D. McPherson. June 2001`
 357
 358 ISIS
 359 ----
 360
 361 RIP
 362 ----
 363
 364 - :rfc:`1058`
 365   :t:`Routing Information Protocol. C.L. Hedrick. Jun-01-1988.`
 366 - :rfc:`2082`
 367   :t:`RIP-2 MD5 Authentication. F. Baker, R. Atkinson. January 1997.`
 368 - :rfc:`2453`
 369   :t:`RIP Version 2. G. Malkin. November 1998.`
 370 - :rfc:`2080`
 371   :t:`RIPng for IPv6. G. Malkin, R. Minnear. January 1997.`
 372
 373 PIM
 374 ----
 375
 376 BFD
 377 ----
 378 - :rfc:`5880`
 379   :t:`Bidirectional Forwarding Detection (BFD), D. Katz, D. Ward. June 2010`
 380 - :rfc:`5881`
 381   :t:`Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop), D. Katz, D. Ward. June 2010`
 382 - :rfc:`5883`
 383   :t:`Bidirectional Forwarding Detection (BFD) for Multihop Paths, D. Katz, D. Ward. June 2010`
 384
 385 MPLS
 386 ----
 387
 388 - :rfc:`2858`
 389   :t:`Multiprotocol Extensions for BGP-4. T. Bates, Y. Rekhter, R. Chandra, D. Katz. June 2000.`
 390 - :rfc:`4364`
 391   :t:`BGP/MPLS IP Virtual Private Networks (VPNs). Y. Rekhter. Feb 2006.`
 392 - :rfc:`4447`
 393   :t:`Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP), L. Martini, E. Rosen, N. El-Aawar, T. Smith, and G. Heron. April 2006.`
 394 - :rfc:`4659`
 395   :t:`BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN. J. De Clercq, D. Ooms, M. Carugi, F. Le Faucheur. September 2006`
 396 - :rfc:`4762`
 397   :t:`Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling, M. Lasserre and V. Kompella. January 2007.`
 398 - :rfc:`5036`
 399   :t:`LDP Specification, L. Andersson, I. Minei, and B. Thomas. October 2007.`
 400 - :rfc:`5561`
 401   :t:`LDP Capabilities, B. Thomas, K. Raza, S. Aggarwal, R. Aggarwal, and JL. Le Roux. July 2009.`
 402 - :rfc:`5918`
 403   :t:`Label Distribution Protocol (LDP) 'Typed Wildcard' Forward Equivalence Class (FEC), R. Asati, I. Minei, and B. Thomas. August 2010.`
 404 - :rfc:`5919`
 405   :t:`Signaling LDP Label Advertisement Completion, R. Asati, P. Mohapatra, E. Chen, and B. Thomas. August 2010.`
 406 - :rfc:`6667`
 407   :t:`LDP 'Typed Wildcard' Forwarding Equivalence Class (FEC) for PWid and Generalized PWid FEC Elements, K. Raza, S. Boutros, and C. Pignataro. July 2012.`
 408 - :rfc:`6720`
 409   :t:`The Generalized TTL Security Mechanism (GTSM) for the Label Distribution Protocol (LDP), C. Pignataro and R. Asati. August 2012.`
 410 - :rfc:`7552`
 411   :t:`Updates to LDP for IPv6, R. Asati, C. Pignataro, K. Raza, V. Manral, and R. Papneja. June 2015.`
 412
 413 VRRP
 414 ----
 415
 416 - :rfc:`3768`
 417   :t:`Virtual Router Redundancy Protocol (VRRP). R. Hinden. April 2004.`
 418 - :rfc:`5798`
 419   :t:`Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6. S. Nadas. June 2000.`
 420
 421 SNMP
 422 ----
 423
 424 **When SNMP support is enabled, the following RFCs are also supported:**
 425
 426 - :rfc:`1227`
 427   :t:`SNMP MUX protocol and MIB. M.T. Rose. May-01-1991.`
 428 - :rfc:`1657`
 429   :t:`Definitions of Managed Objects for the Fourth Version of the Border
 430   Gateway Protocol (BGP-4) using SMIv2. S. Willis, J. Burruss, J. Chu, Editor.
 431   July 1994.`
 432 - :rfc:`1724`
 433   :t:`RIP Version 2 MIB Extension. G. Malkin & F. Baker. November 1994.`
 434 - :rfc:`1850`
 435   :t:`OSPF Version 2 Management Information Base. F. Baker, R. Coltun.
 436   November 1995.`
 437 - :rfc:`2741`
 438   :t:`Agent Extensibility (AgentX) Protocol. M. Daniele, B. Wijnen. January 2000.`
 439
 440 Mailing Lists
 441 =============
 442
 443 .. index:: How to get in touch with FRR
 444 .. index:: Contact information
 445 .. index:: Mailing lists
 446
 447
 448 Italicized lists are private.
 449
 450 +--------------------------------+------------------------------+
 451 | Topic                          | List                         |
 452 +================================+==============================+
 453 | Development                    | dev@lists.frrouting.org      |
 454 +--------------------------------+------------------------------+
 455 | Users & Operators              | frog@lists.frrouting.org     |
 456 +--------------------------------+------------------------------+
 457 | Announcements                  | announce@lists.frrouting.org |
 458 +--------------------------------+------------------------------+
 459 | *Security*                     | security@lists.frrouting.org |
 460 +--------------------------------+------------------------------+
 461 | *Technical Steering Committee* | tsc@lists.frrouting.org      |
 462 +--------------------------------+------------------------------+
 463
 464 The Development list is used to discuss and document general issues related to
 465 project development and governance. The public `Slack`_ instance and weekly
 466 technical meetings provide a higher bandwidth channel for discussions. The
 467 results of such discussions are reflected in updates, as appropriate, to code
 468 (i.e., merges), `GitHub issues`_ tracked issues, and for governance or process
 469 changes, updates to the Development list and either this file or information
 470 posted at `FRR`_.
 471
 472 Bug Reports
 473 ===========
 474
 475 For information on reporting bugs, please see :ref:`bug-reports`.
 476
 477 .. _frr: |package-url|
 478 .. _github: https://github.com/frrouting/frr/
 479 .. _github issues: https://github.com/frrouting/frr/issues
 480 .. _slack: https://frrouting.org/#participate