YANG Model for Border Gateway Protocol (BGP-4)#

Mahesh Jethanandani, Keyur Patel (Arrcus), Susan Hares, Jeff Haas (HPE) — IDR WG

• Why: A standard YANG model for BGP config/ops matters to anyone building automated DC or WAN fabrics — today every vendor's BGP schema differs. Once published, this becomes the north-star schema for BGP automation.
• What: YANG data model for configuring and managing BGP — protocol, policy, and operational aspects including RIB — based on data center, carrier, and content provider requirements. The draft (presented at -19, now at -23) is modular: separate submodules for types, capabilities, common/neighbor state, multiprotocol AFI/SAFI, policy, RIB tables/attributes, and session security (key chains, TCP-AO), with IANA-maintained modules for capabilities, notification codes, AFI/SAFI types, and community types.
• How: Standard NETCONF/RESTCONF data-model machinery layered on ietf-routing, ietf-routing-policy, ietf-key-chain, ietf-tcp, and BFD types.
• Where applicable: BGP automation across DC, carrier, and enterprise; vendor-neutral intent for gNMI/NETCONF pipelines. Maturity: long-running WG draft (-23, updated the day before this digest), intended Proposed Standard, still clearing YANG validation errors — close to the end of a long road, not a finished RFC.