Skip to content

bgp nlri rtc

Thomas Mangin edited this page May 30, 2026 · 3 revisions

Pre-Alpha. This page describes behavior that may change.

Route Target Constrain (RFC 4684). IPv4 only (AFI 1 / SAFI 132). Decode-only: Ze parses received RTC NLRI. Encoding is not implemented.

Category

Address families.

Configuration

plugin {
    internal nlri-rtc { use bgp-nlri-rtc }
}

bgp {
    peer upstream {
        family {
            ipv4/rtc { prefix { maximum 10000; } }
        }
    }
}

Behaviour

RTC is the mechanism route reflectors use to advertise which Route Targets each client is interested in, so the reflector can filter VPN routes efficiently. The plugin decodes received RTC NLRIs.

Encoding is not implemented. Ze can participate as a passive receiver of RTC information but cannot advertise its own RT memberships.

Interactions

  • Decode-only.
  • Designed to compose with bgp-nlri-vpn in a route reflector deployment, though the encode half is the missing piece.

Source

main/internal/component/bgp/plugins/nlri/rtc/

Home

About

First Steps

Configuration

Operation

Interfaces

Plugins

Plugin Development

Chaos Testing

Blueprints

Development

Reference

Clone this wiki locally