bgp nlri mup

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

Mobile User Plane SAFI for IPv4 (AFI 1 / SAFI 85) and IPv6 (AFI 2 / SAFI 85). The family is decoded, encoded, and originated through the plugin NLRI pipeline, not the legacy core path.

Category

Address families.

Configuration

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

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

Behaviour

MUP is the control plane for 5G Mobile User Plane integration with BGP. The plugin encodes and decodes MUP NLRIs for both address families. Routes carry user plane information that routers in the path use to direct mobile traffic.

MUP is a specialised family. Most deployments do not need it. Enable it when you are integrating Ze into a 5G mobile user plane setup.

Plugin pipeline

The bgp-nlri-mup plugin registers four in-process callbacks: InProcessNLRIDecoder, InProcessNLRIEncoder, InProcessRouteEncoder, and InProcessConfigRouteParser. Decode, encode, route origination, and config parsing all live in the plugin, so the RIB, filter chain, and central config code need no MUP-specific knowledge. JSON output is rendered through the attribute JSON registry with ExaBGP-compatible key ordering.

Interactions

• Supports both encode and decode.
• Independent of the other address family plugins.

Source

main/internal/component/bgp/plugins/nlri/mup/

See also

• Address Families for the full family list.
• SR-Policy NLRI for the SAFI 73 policy family.
• Plugins for the plugin catalogue.

Adapted from the mup plugin source code (draft-mpmz-bess-mup-safi).