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