Summary
I'd like to suggest adding OpenConfig BGP YANG model support to the TransLib layer. This would provide a standardized, OpenConfig-compliant API for BGP configuration and state management, complementing the existing SONiC native BGP support.
Current State
The sonic-mgmt-common framework currently has BGP support at the SONiC native YANG level (sonic-bgp-global.yang), which is used for CVL validation and testing. However, there isn't currently an OpenConfig BGP interface available through TransLib.
Initial Scope Suggestion
A phased approach could start with:
- BGP global configuration (AS number, router ID, graceful restart)
- BGP neighbor configuration
- BGP peer groups
- Address family configuration
Summary
I'd like to suggest adding OpenConfig BGP YANG model support to the TransLib layer. This would provide a standardized, OpenConfig-compliant API for BGP configuration and state management, complementing the existing SONiC native BGP support.
Current State
The sonic-mgmt-common framework currently has BGP support at the SONiC native YANG level (sonic-bgp-global.yang), which is used for CVL validation and testing. However, there isn't currently an OpenConfig BGP interface available through TransLib.
Initial Scope Suggestion
A phased approach could start with: